High Availability:Hardware:Networking - Revision history

Allyntree: Needs revising edit

2018-04-05T19:26:25Z

Needs revising edit

← Older revision		Revision as of 15:26, 5 April 2018
Line 52:		Line 52:

	[[Image:Tms_Network_Ha_connection.png\|widthpx\| ]]		[[Image:Tms_Network_Ha_connection.png\|widthpx\| ]]

	~~[[category:Needs revising]]~~

Allyntree: /* Ethernet Network */

2018-04-05T19:26:04Z

Ethernet Network

← Older revision		Revision as of 15:26, 5 April 2018
Line 3:		Line 3:

	== Ethernet Network ==		== Ethernet Network ==
	TelcoBridges ~~recommend~~ the following ~~characteristics~~ when setting up a Ethernet network:		TelcoBridges recommends the following when setting up a Ethernet network:
	* The ~~whole~~ network should be running at 1 Gb/s (~~means~~ all Ethernet switches, Ethernet cards and Ethernet cables).		* The entire network should be running at 1 Gb/s (all Ethernet switches, Ethernet cards and Ethernet cables).
	* Use 2 Managed Ethernet Switches.		* Use 2 Managed Ethernet Switches.
	* Use different subnet for each control ~~networks~~ and each voip ~~networks~~.		* Use different subnet for each control network and each voip network.
	* Use VLAN from the Managed Switches to separate traffic (1 VLAN for the control network, 1 VLAN for the voip network per Ethernet switch).		* Use VLAN from the Managed Switches to separate traffic (1 VLAN for the control network, 1 VLAN for the voip network per Ethernet switch).

	'''Warning'''		'''Warning'''
	[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure ~~won't~~ be able to control [[Tdev]] devices.		[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure will not be able to control [[Tdev]] devices.

	=== <u>Control Network</u> ===		=== <u>Control Network</u> ===

Luc Morissette: Should describe TMG7800, tmp7900 is not existing anymore.

2013-06-06T12:15:10Z

Should describe TMG7800, tmp7900 is not existing anymore.

← Older revision		Revision as of 08:15, 6 June 2013
Line 52:		Line 52:

	[[Image:Tms_Network_Ha_connection.png\|widthpx\| ]]		[[Image:Tms_Network_Ha_connection.png\|widthpx\| ]]

			[[category:Needs revising]]

Cbilodeau: replace tmedia with tdev

2011-02-15T16:59:12Z

replace tmedia with tdev

← Older revision		Revision as of 12:59, 15 February 2011
Line 10:		Line 10:

	'''Warning'''		'''Warning'''
	[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure won't be able to control ~~a Tmedia~~.		[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure won't be able to control [[Tdev]] devices.

	=== <u>Control Network</u> ===		=== <u>Control Network</u> ===

	The control network is the Ethernet network used by Toolpack to control the Toolpack applications and the ~~Tmedia~~ hardware products. TelcoBridges provides 2 control ports on all its ~~TMPx~~ (except TMP800)~~. TMGx products (like TMG3200) do not requires the customer setup a control network since it is included in the product itself~~.		The control network is the Ethernet network used by Toolpack to control the Toolpack applications and the [[Tdev]] hardware products. TelcoBridges provides 2 control ports on all its [[Tdev]] (except TMP800).

	The redundancy of the control network is done by using 2 independent network (1 for each control ports).		The redundancy of the control network is done by using 2 independent network (1 for each control ports).
Line 28:		Line 28:
	=== <u>Voip Network</u> ===		=== <u>Voip Network</u> ===

	The voip network are secured interfaces that are use to send signaling and data over Ip networks (i.e. Sip, Sigtran). They are considered secured because it is not possible to control the ~~Tmedia~~ through those interfaces. TelcoBridges provides 2 voip ports on all its ~~Tmedia~~ products (except TMP800).		The voip network are secured interfaces that are use to send signaling and data over Ip networks (i.e. Sip, Sigtran). They are considered secured because it is not possible to control the [[Tdev]] through those interfaces. TelcoBridges provides 2 voip ports on all its [[Tdev]] products (except TMP800).

	The redundancy of the voip network is done by using 2 independent network (1 for each voip ports).		The redundancy of the voip network is done by using 2 independent network (1 for each voip ports).
Line 42:		Line 42:
	== TMS Network ==		== TMS Network ==

	The TMS network is use to connect the multiple TMP6400 together. It allows a TMP6400 to bridges an incoming call leg to another TMP6400 using the TMS network instead of wasting tdm or voip resources to connect. It is possible to expand a system from ~~2000~~ non-blocking bridges (1 TMP6400) up to ~~32000~~ non-blocking bridges (16 TMP6400) with the TMS network.		The TMS network is use to connect the multiple [[TMP6400]] or [[TMP7900]] telecom units together. It allows a [[TMP6400]] to bridges an incoming call leg to another [[TMP6400]] using the TMS network instead of wasting tdm or voip resources to connect. It is possible to expand a system from 2016 non-blocking bridges (1 TMP6400) up to 32768 non-blocking bridges (16 TMP6400) with the TMS network.

	The TMS network redundancy is achieved by using 2 TMS1600 and connecting each TMP6400 to both TMS1600. The TMP6400 has 2 TMS port called (TMS-1 and TMS-2). The TMS connection requires a very specific type of cable see [[Media:TMP6400_Installation_Guide_Issue2.2.pdf\| installation guides section 2.6 (Connecting the TMP6400s to the TMS1600)for more info ]]		The TMS network redundancy is achieved by using 2 TMS1600 and connecting each TMP6400 to both TMS1600. The TMP6400 has 2 TMS port called (TMS-1 and TMS-2). The TMS connection requires a very specific type of cable see [[Media:TMP6400_Installation_Guide_Issue2.2.pdf\| installation guides section 2.6 (Connecting the TMP6400s to the TMS1600)for more info ]]

Cbilodeau: fix format

2009-12-28T22:10:15Z

fix format

← Older revision		Revision as of 18:10, 28 December 2009
Line 12:		Line 12:
	[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure won't be able to control a Tmedia.		[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure won't be able to control a Tmedia.

	=== Control Network ===		=== <u>Control Network</u> ===

	The control network is the Ethernet network used by Toolpack to control the Toolpack applications and the Tmedia hardware products. TelcoBridges provides 2 control ports on all its TMPx (except TMP800). TMGx products (like TMG3200) do not requires the customer setup a control network since it is included in the product itself.		The control network is the Ethernet network used by Toolpack to control the Toolpack applications and the Tmedia hardware products. TelcoBridges provides 2 control ports on all its TMPx (except TMP800). TMGx products (like TMG3200) do not requires the customer setup a control network since it is included in the product itself.
Line 20:		Line 20:


	==== Recommended Setup ====		==== <u>Recommended Setup</u> ====

	Here is a schematic of the recommended control network connection for a high availability system:		Here is a schematic of the recommended control network connection for a high availability system:
Line 26:		Line 26:
	[[Image:Control_Network_Ha_connection.png\|widthpx\| ]]		[[Image:Control_Network_Ha_connection.png\|widthpx\| ]]

	=== Voip Network ===		=== <u>Voip Network</u> ===

	The voip network are secured interfaces that are use to send signaling and data over Ip networks (i.e. Sip, Sigtran). They are considered secured because it is not possible to control the Tmedia through those interfaces. TelcoBridges provides 2 voip ports on all its Tmedia products (except TMP800).		The voip network are secured interfaces that are use to send signaling and data over Ip networks (i.e. Sip, Sigtran). They are considered secured because it is not possible to control the Tmedia through those interfaces. TelcoBridges provides 2 voip ports on all its Tmedia products (except TMP800).
Line 34:		Line 34:


	==== Recommended Setup ====		==== <u>Recommended Setup</u> ====

	Here is a schematic of the recommended voip network connection for a high availability system:		Here is a schematic of the recommended voip network connection for a high availability system:

Cbilodeau: Add voip network and tms network

2009-12-28T21:49:14Z

Add voip network and tms network

← Older revision		Revision as of 17:49, 28 December 2009
Line 1:		Line 1:
	Networking is a critical section of the system that is sometimes overlooked. An adequate network will avoid problems like congestion ~~and~~ disconnection.		Networking is a critical section of the system that is sometimes overlooked. An adequate network will avoid problems like congestion or disconnection.

	~~== Control Network ==~~

	~~The control network is the~~ Ethernet network used by Toolpack to control the Toolpack applications and the Tmedia hardware products. TelcoBridges provides 2 control ports on all its TMPx (except TMP800). TMGx products (like TMG3200) do not requires the customer setup a control network since it is included in the product itself.		== Ethernet Network ==
			TelcoBridges recommend the following characteristics when setting up a Ethernet network:
	~~The redundancy of the control network is done by using 2 independant network (1 for each control ports).~~		* The whole network should be running at 1 Gb/s (means all Ethernet switches, Ethernet cards and Ethernet cables).

	TelcoBridges recommend the following characteristics when setting up a ~~Control Network~~:
	* The whole network should be running at 1 GB/s (means all Ethernet switches and Ethernet ~~cards~~).
	* Use 2 Managed Ethernet Switches.		* Use 2 Managed Ethernet Switches.
	* Use different subnet for each control networks and each voip networks.		* Use different subnet for each control networks and each voip networks.
	* Use VLAN from the Managed Switches to separate traffic (1 VLAN for the control network, 1 VLAN for the voip network per Ethernet switch).		* Use VLAN from the Managed Switches to separate traffic (1 VLAN for the control network, 1 VLAN for the voip network per Ethernet switch).

			'''Warning'''
			[[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]] is not recommended. A host with Ip teaming configure won't be able to control a Tmedia.

			=== Control Network ===

			The control network is the Ethernet network used by Toolpack to control the Toolpack applications and the Tmedia hardware products. TelcoBridges provides 2 control ports on all its TMPx (except TMP800). TMGx products (like TMG3200) do not requires the customer setup a control network since it is included in the product itself.

			The redundancy of the control network is done by using 2 independent network (1 for each control ports).

	~~'''Warning'''~~
	~~TelcoBridges hardware doesn't support [[Ip_Teaming/Ip_Bonding \| Ip teaming or Ip bonding]]. A host with Ip teaming configure won't be able to control a Tmedia.~~


	=== Recommended Setup ===		==== Recommended Setup ====

	Here is a schematic of the recommended control network connection for a high availability system:		Here is a schematic of the recommended control network connection for a high availability system:
Line 24:		Line 26:
	[[Image:Control_Network_Ha_connection.png\|widthpx\| ]]		[[Image:Control_Network_Ha_connection.png\|widthpx\| ]]

	== Voip Network ==		=== Voip Network ===

			The voip network are secured interfaces that are use to send signaling and data over Ip networks (i.e. Sip, Sigtran). They are considered secured because it is not possible to control the Tmedia through those interfaces. TelcoBridges provides 2 voip ports on all its Tmedia products (except TMP800).

			The redundancy of the voip network is done by using 2 independent network (1 for each voip ports).



			==== Recommended Setup ====

			Here is a schematic of the recommended voip network connection for a high availability system:

			[[Image:Voip_Network_Ha_connection.png\|widthpx\| ]]

	== TMS Network ==		== TMS Network ==

			The TMS network is use to connect the multiple TMP6400 together. It allows a TMP6400 to bridges an incoming call leg to another TMP6400 using the TMS network instead of wasting tdm or voip resources to connect. It is possible to expand a system from 2000 non-blocking bridges (1 TMP6400) up to 32000 non-blocking bridges (16 TMP6400) with the TMS network.

			The TMS network redundancy is achieved by using 2 TMS1600 and connecting each TMP6400 to both TMS1600. The TMP6400 has 2 TMS port called (TMS-1 and TMS-2). The TMS connection requires a very specific type of cable see [[Media:TMP6400_Installation_Guide_Issue2.2.pdf\| installation guides section 2.6 (Connecting the TMP6400s to the TMS1600)for more info ]]


			==== Recommended Setup ====

			Here is a schematic of the recommended TMS network connection for a high availability system:

	~~To do~~		[[Image:Tms_Network_Ha_connection.png\|widthpx\| ]]
	*1 GB
	*VLAN
	*ip teaming
	*switch redundancy

Cbilodeau: add control network information

2009-12-28T20:17:05Z

add control network information

@@ Line 1: / Line 1: @@
 == Control Network ==
 == Voip Network ==
@@ Line 10: / Line 32: @@
 To do
 *VLAN
 *ip teaming
 *switch redundancy

Cbilodeau: Creation

2009-12-23T21:47:23Z

Creation

New page

== Control Network ==

== Voip Network ==

== TMS Network ==

To do
*VLAN
*ip teaming
*switch redundancy