H.248 Network Redundancy - Revision history

Luc Morissette at 11:02, 4 April 2012

2012-04-04T11:02:14Z

← Older revision		Revision as of 07:02, 4 April 2012
Line 53:		Line 53:

	#VLAN Id		#VLAN Id
	#IP ~~confiuration~~		#IP configuration
	#Physical ports to use		#Physical ports to use
	#Polling params		#Polling params

Luc Morissette: Added upgrade to Centos 5.7 if using vlans

2012-04-03T19:24:13Z

Added upgrade to Centos 5.7 if using vlans

← Older revision		Revision as of 15:24, 3 April 2012
Line 1:		Line 1:
	Network redundancy is achieved when the H.248 stack can be reached by at least two physical networks ports on the TMG. On the TMG800/3200, usually H.248 uses the mgmt port, but with the network redundancy feature it is possible to use the VOIP0/1 and ETH0/1 port combinations. For example if we use a VOIP0/1 combination, initially the traffic will go through VOIP0 and if a failure is detected then it will switch to using the VOIP1 port. The switch will be transparent for the MGC, in fact only the Ethernet switch will see the difference and it should adapt very quickly.		Network redundancy is achieved when the H.248 stack can be reached by at least two physical networks ports on the TMG. On the TMG800/3200, usually H.248 uses the mgmt port, but with the network redundancy feature it is possible to use the VOIP0/1 and ETH0/1 port combinations. For example if we use a VOIP0/1 combination, initially the traffic will go through VOIP0 and if a failure is detected then it will switch to using the VOIP1 port. The switch will be transparent for the MGC, in fact only the Ethernet switch will see the difference and it should adapt very quickly.

	== Technically speaking ==		== Technically speaking ==
	When using the network redundancy feature, the H.248 stack will bind itself to a special VLAN tagged (802.1Q) interface that is routed (level 2 routing) to a physical port. The [[TMG-CONTROL]] software will monitor the link:
	~~# Ethernet link~~
	~~# Ping (ICMP echo) requests on a specified IP address~~
	When either of the monitoring techniques finds a failure the routing will change to the next available physical port specified in the configuration. When a routing change occurs ARP broadcasts are sent on the new physical port so that the Ethernet switch adapts to the change.

	~~Some additional steps are necessary in order~~ to ~~use this feature~~:		When using the network redundancy feature, the H.248 stack will bind itself to a special VLAN tagged (802.1Q) interface that is routed (level 2 routing) to a physical port. The [[TMG-CONTROL]] software will monitor the link:

	~~== Installing vconfig~~ on ~~the TMG Host ==~~		#Ethernet link
	~~This is only needed for TMG800/3200 that were bought before the H.248 network redundancy was advertised. You do not need to do this otherwise and you should skip this step.~~		#Ping (ICMP echo) requests on a specified IP address

	~~You can check if you need~~ to ~~install~~ the ~~required package by typing~~ the ~~following in~~ a ~~terminal~~ on the ~~TMG host:~~		When either of the monitoring techniques finds a failure the routing will change to the next available physical port specified in the configuration. When a routing change occurs ARP broadcasts are sent on the new physical port so that the Ethernet switch adapts to the change.
	~~<blockquote><code>~~
	~~yum list installed vconfig~~
	~~</code></blockquote>~~

	~~If the output is similar~~ to ~~the any of the following lines then you do not need to install the package since it is already installed~~:		Some additional steps are necessary in order to use this feature:
	~~<blockquote><code>~~
	~~vconfig.x86_64 1.9-3 installed~~
	~~</code></blockquote>~~
	~~<blockquote><code>~~
	~~vconfig.ppc 1.9-6.tb1 @/vconfig-1.9-6.tb1.ppc~~
	~~</code></blockquote>~~

	In the ~~case you do not see this output, the host is missing a package for the feature to work correctly so we need to install it.~~		== Installing vconfig on the TMG Host ==

	~~=== TMG has internet access ===~~		This is only needed for TMG800/3200 that were bought before the H.248 network redundancy was advertised. You do not need to do this otherwise and you should skip this step.
	~~# Install the package on~~ the ~~TMG unit:~~
	~~<blockquote><code>~~
	~~yum install vconfig~~
	~~</code></blockquote>~~

	~~===~~ TMG ~~has NO internet access ===~~		You can check if you need to install the required package by typing the following in a terminal on the TMG host:
	~~# Download package from telcobridges (http:~~//~~download.distribution.telcobridges.com/TBLinux/updates/1/os/vconfig-1.9-6.tb1.ppc.rpm)~~		<blockquote><code>yum list installed vconfig</code></blockquote>
	~~# Upload package~~ to the ~~TMG unit. You can use Winscp to~~ do ~~a file transfer~~ to the ~~tmg~~.		If the output is similar to the any of the following lines then you do not need to install the package since it is already installed:
	~~# Install the package on the TMG unit~~.		<blockquote><code>vconfig.x86_64 1.9-3 installed</code></blockquote> <blockquote><code>vconfig.ppc 1.9-6.tb1 @/vconfig-1.9-6.tb1.ppc</code></blockquote>
	<blockquote><code>		In the case you do not see this output, the host is missing a package for the feature to work correctly so we need to install it.
	~~yum localinstall~~ vconfig-1.9-6.tb1.ppc~~.rpm~~
	</code></blockquote>

	== ~~Configuring the Switch~~ ==		=== TMG has internet access ===
	Since the network redundancy feature requires VLAN tagging, the switches where the physical ports are connected to need to be configured for H.248 network redundancy. Usually the switch configuration for VLANs is to specify which ports are part of the VLAN but it could also be to specify untagged ports (if the H.248 traffic needs to be untagged for the MGC).

	== ~~Configuring System Virtual IP Interfaces~~ ==		#Install the package on the TMG unit:
	The next step is to configure a virtual IP interface that will encompass two physical ports. This is done in the web portal menu item: "System Virtual IP Interfaces". From there you can create a virtual IP interface for H.248 and specify:		<blockquote><code>yum install vconfig</code></blockquote>
	~~# VLAN Id~~		=== TMG has NO internet access ===
	~~# IP confiuration~~
	~~# Physical ports to use~~
	~~# Polling params~~

			#Download package from telcobridges (http://download.distribution.telcobridges.com/TBLinux/updates/1/os/vconfig-1.9-6.tb1.ppc.rpm)
			#Upload package to the TMG unit. You can use Winscp to do a file transfer to the tmg.
			#Install the package on the TMG unit.
			<blockquote><code>yum localinstall vconfig-1.9-6.tb1.ppc.rpm</code></blockquote>
			== Upgrade to Centos 5.7 ==

	~~== Configuring H.248 ==~~		Check the version of Centos currently running on the unit:
	~~Now in~~ the ~~H.248 configuration you need to set~~ the ~~local IP field to the system virtual IP interface that was created for H.248. Then you just need to apply the configuration to complete the configuration.~~

	== Related Articles ==		cat /etc/redhat-release
	[[TMG:~~Add_persistent_static_route~~\|Adding a persistent route]]
			If you see:

			CentOS release 5.7 (Final)

			You do not need to upgrade. Otherwise, follow the procedure here: [[Toolpack prerequisite CentOS5 2-5]], or contact TelcoBridges support.

			== Configuring the Switch ==

			Since the network redundancy feature requires VLAN tagging, the switches where the physical ports are connected to need to be configured for H.248 network redundancy. Usually the switch configuration for VLANs is to specify which ports are part of the VLAN but it could also be to specify untagged ports (if the H.248 traffic needs to be untagged for the MGC).

			== Configuring System Virtual IP Interfaces ==

			The next step is to configure a virtual IP interface that will encompass two physical ports. This is done in the web portal menu item: "System Virtual IP Interfaces". From there you can create a virtual IP interface for H.248 and specify:

			#VLAN Id
			#IP confiuration
			#Physical ports to use
			#Polling params

			<br>

			== Configuring H.248 ==

			Now in the H.248 configuration you need to set the local IP field to the system virtual IP interface that was created for H.248. Then you just need to apply the configuration to complete the configuration.

			== Related Articles ==

			[[TMG:Add persistent static route\|Adding a persistent route]]

Cbilodeau: add persisten route link

2011-08-04T18:54:54Z

add persisten route link

← Older revision		Revision as of 14:54, 4 August 2011
Line 50:		Line 50:
	# Physical ports to use		# Physical ports to use
	# Polling params		# Polling params


	== Configuring H.248 ==		== Configuring H.248 ==
	Now in the H.248 configuration you need to set the local IP field to the system virtual IP interface that was created for H.248. Then you just need to apply the configuration to complete the configuration.		Now in the H.248 configuration you need to set the local IP field to the system virtual IP interface that was created for H.248. Then you just need to apply the configuration to complete the configuration.

			== Related Articles ==
			[[TMG:Add_persistent_static_route\|Adding a persistent route]]

Jcharest at 20:29, 20 July 2011

2011-07-20T20:29:14Z

← Older revision		Revision as of 16:29, 20 July 2011
Line 25:		Line 25:
	</code></blockquote>		</code></blockquote>

	In the case you do not see this output, the host is missing a package for the feature to work correctly so we need to install it:		In the case you do not see this output, the host is missing a package for the feature to work correctly so we need to install it.
	# Download package from telcobridges
	# Upload package to the TMG unit.		=== TMG has internet access ===
			# Install the package on the TMG unit:
			<blockquote><code>
			yum install vconfig
			</code></blockquote>

			=== TMG has NO internet access ===
			# Download package from telcobridges (http://download.distribution.telcobridges.com/TBLinux/updates/1/os/vconfig-1.9-6.tb1.ppc.rpm)
			# Upload package to the TMG unit. You can use Winscp to do a file transfer to the tmg.
	# Install the package on the TMG unit.		# Install the package on the TMG unit.
			<blockquote><code>
			yum localinstall vconfig-1.9-6.tb1.ppc.rpm
			</code></blockquote>

	== Configuring the Switch ==		== Configuring the Switch ==

Jcharest at 14:24, 19 July 2011

2011-07-19T14:24:16Z

← Older revision		Revision as of 10:24, 19 July 2011
Line 25:		Line 25:
	</code></blockquote>		</code></blockquote>

	In ~~these cases~~ the host is missing a package for the feature to work correctly so we need to install it:		In the case you do not see this output, the host is missing a package for the feature to work correctly so we need to install it:
	# Download package from telcobridges		# Download package from telcobridges
	# Upload package to the TMG unit.		# Upload package to the TMG unit.

Jcharest at 14:23, 19 July 2011

2011-07-19T14:23:33Z

@@ Line 11: / Line 11: @@
 == Installing vconfig on the TMG Host ==
 This is only needed for TMG800/3200 that were bought before the H.248 network redundancy was advertised. You do not need to do this otherwise and you should skip this step.
 In these cases the host is missing a package for the feature to work correctly so we need to install it:

Jcharest at 13:43, 19 July 2011

2011-07-19T13:43:06Z

← Older revision		Revision as of 09:43, 19 July 2011
Line 16:		Line 16:
	# Upload package to the TMG unit.		# Upload package to the TMG unit.
	# Install the package on the TMG unit.		# Install the package on the TMG unit.

			== Configuring the Switch ==
			Since the network redundancy feature requires VLAN tagging, the switches where the physical ports are connected to need to be configured for H.248 network redundancy. Usually the switch configuration for VLANs is to specify which ports are part of the VLAN but it could also be to specify untagged ports (if the H.248 traffic needs to be untagged for the MGC).

	== Configuring System Virtual IP Interfaces ==		== Configuring System Virtual IP Interfaces ==
Line 25:		Line 28:

	== Configuring H.248 ==		== Configuring H.248 ==
	Now in the H.248 configuration you need to set the local ip field to the system virtual IP ~~interfaces~~ that was created for H.248. Then you just need to apply the configuration to complete the configuration.		Now in the H.248 configuration you need to set the local IP field to the system virtual IP interface that was created for H.248. Then you just need to apply the configuration to complete the configuration.

Jcharest at 13:36, 19 July 2011

2011-07-19T13:36:46Z

← Older revision		Revision as of 09:36, 19 July 2011
Line 9:		Line 9:
	Some additional steps are necessary in order to use this feature:		Some additional steps are necessary in order to use this feature:

	== Installing vconfig on the TMG ~~host~~ ==		== Installing vconfig on the TMG Host ==
	This is only needed for TMG800/3200 that were bought before the H.248 network redundancy was advertised. You do not need to do this otherwise and you should skip this step.		This is only needed for TMG800/3200 that were bought before the H.248 network redundancy was advertised. You do not need to do this otherwise and you should skip this step.

Line 17:		Line 17:
	# Install the package on the TMG unit.		# Install the package on the TMG unit.

	== Configuring ~~system virtual~~ IP ~~interfaces~~ ==		== Configuring System Virtual IP Interfaces ==
	The next step is to configure a virtual IP interface that will encompass two physical ports. This is done in the web portal menu item: "System Virtual IP Interfaces". From there you can create a virtual IP interface for H.248 and specify:		The next step is to configure a virtual IP interface that will encompass two physical ports. This is done in the web portal menu item: "System Virtual IP Interfaces". From there you can create a virtual IP interface for H.248 and specify:
	# VLAN Id		# VLAN Id
Line 23:		Line 23:
	# Physical ports to use		# Physical ports to use
	# Polling params		# Polling params

			== Configuring H.248 ==
			Now in the H.248 configuration you need to set the local ip field to the system virtual IP interfaces that was created for H.248. Then you just need to apply the configuration to complete the configuration.

Jcharest at 13:34, 19 July 2011

2011-07-19T13:34:30Z

← Older revision		Revision as of 09:34, 19 July 2011
Line 5:		Line 5:
	# Ethernet link		# Ethernet link
	# Ping (ICMP echo) requests on a specified IP address		# Ping (ICMP echo) requests on a specified IP address
	When either of the monitoring techniques finds a failure the routing will change to the next available physical port specified in the configuration. When a routing change occurs ARP broadcasts are sent on the new physical port so that the ~~Ehternet~~ switch adapts to the change.		When either of the monitoring techniques finds a failure the routing will change to the next available physical port specified in the configuration. When a routing change occurs ARP broadcasts are sent on the new physical port so that the Ethernet switch adapts to the change.

	Some additional steps are necessary in order to use this feature:		Some additional steps are necessary in order to use this feature:
Line 13:		Line 13:

	In these cases the host is missing a package for the feature to work correctly so we need to install it:		In these cases the host is missing a package for the feature to work correctly so we need to install it:
			# Download package from telcobridges
			# Upload package to the TMG unit.
			# Install the package on the TMG unit.

	== Configuring system virtual IP interfaces ==		== Configuring system virtual IP interfaces ==

Jcharest at 13:32, 19 July 2011

2011-07-19T13:32:53Z

← Older revision		Revision as of 09:32, 19 July 2011
Line 4:		Line 4:
	When using the network redundancy feature, the H.248 stack will bind itself to a special VLAN tagged (802.1Q) interface that is routed (level 2 routing) to a physical port. The [[TMG-CONTROL]] software will monitor the link:		When using the network redundancy feature, the H.248 stack will bind itself to a special VLAN tagged (802.1Q) interface that is routed (level 2 routing) to a physical port. The [[TMG-CONTROL]] software will monitor the link:
	# Ethernet link		# Ethernet link
	# Ping requests on a specified IP address		# Ping (ICMP echo) requests on a specified IP address
	When either of the monitoring techniques finds a failure the routing will change to the next available physical port specified in the configuration.		When either of the monitoring techniques finds a failure the routing will change to the next available physical port specified in the configuration. When a routing change occurs ARP broadcasts are sent on the new physical port so that the Ehternet switch adapts to the change.

	Some additional steps are necessary in order to use this feature:		Some additional steps are necessary in order to use this feature: