High Availability:Hardware:Hosts - Revision history

Allyntree: Needs revising edit: Modified all images

2018-04-05T18:25:44Z

Needs revising edit: Modified all images

← Older revision		Revision as of 14:25, 5 April 2018
Line 55:		Line 55:
	*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support [[Ip_Teaming/Ip_Bonding \| IP Teaming (Ip Bonding)]]. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.		*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support [[Ip_Teaming/Ip_Bonding \| IP Teaming (Ip Bonding)]]. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.
	*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.		*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.

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

Allyntree: /* Recommended Hardware */

2018-03-15T17:16:11Z

Recommended Hardware

← Older revision		Revision as of 13:16, 15 March 2018
Line 47:		Line 47:
	=== Recommended Hardware ===		=== Recommended Hardware ===

	*Use TelcoBridges servers [[TMG7800\|TMG7800-CTRL]],[FreeSBC\|TSBC-HW-SRV]]		*Use TelcoBridges servers [[TMG7800\|TMG7800-CTRL]], [[FreeSBC\|TSBC-HW-SRV]]
	*Having dual power supplies is a plus		*Having dual power supplies is a plus
	*The number of network interface needed by a system is application specific, but for TelcoBridges products at least two independent network interfaces are needed for controlling [[Tmedia]] and another one to connect to the management network.		*The number of network interface needed by a system is application specific, but for TelcoBridges products at least two independent network interfaces are needed for controlling [[Tmedia]] and another one to connect to the management network.

Allyntree: /* Recommended Hardware */

2018-03-15T17:15:41Z

Recommended Hardware

← Older revision		Revision as of 13:15, 15 March 2018
Line 47:		Line 47:
	=== Recommended Hardware ===		=== Recommended Hardware ===

	*Use TelcoBridges servers [[~~TMP7900~~-CTRL]]		*Use TelcoBridges servers [[TMG7800\|TMG7800-CTRL]],[FreeSBC\|TSBC-HW-SRV]]
	*~~Dual~~ power supplies is a ~~huge~~ plus		*Having dual power supplies is a plus
	*The number of network interface needed by a system is application specific, but for TelcoBridges products at least 2 independent network interfaces is needed for controlling ~~the~~ [[~~Tdev~~]] and another one to connect to the management network.		*The number of network interface needed by a system is application specific, but for TelcoBridges products at least two independent network interfaces are needed for controlling [[Tmedia]] and another one to connect to the management network.

	=== Warnings ===		=== Warnings ===

Lucas Trottier at 16:38, 9 May 2016

2016-05-09T16:38:26Z

← Older revision		Revision as of 12:38, 9 May 2016
Line 55:		Line 55:
	*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support [[Ip_Teaming/Ip_Bonding \| IP Teaming (Ip Bonding)]]. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.		*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support [[Ip_Teaming/Ip_Bonding \| IP Teaming (Ip Bonding)]]. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.
	*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.		*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.

			[[category:Needs revising]]

Cbilodeau: update text to new product

2011-02-15T18:48:27Z

update text to new product

← Older revision		Revision as of 14:48, 15 February 2011
Line 47:		Line 47:
	=== Recommended Hardware ===		=== Recommended Hardware ===

	*~~Recommended host hardware components~~ [[~~media:FINAL~~ - ~~DATA SHEET TMP7950.pdf\|TMP7950 data sheet~~]].		*Use TelcoBridges servers [[TMP7900-CTRL]]
	*Dual power supplies is a huge plus		*Dual power supplies is a huge plus
	*The number of network interface needed by a system is application specific, but for TelcoBridges products at least 2 independent network interfaces is needed for controlling the ~~Tmedias~~ and another one to connect to the management network.		*The number of network interface needed by a system is application specific, but for TelcoBridges products at least 2 independent network interfaces is needed for controlling the [[Tdev]] and another one to connect to the management network.

	=== Warnings ===		=== Warnings ===

Cbilodeau: add secondary host switchover example

2010-09-09T18:30:17Z

add secondary host switchover example

← Older revision		Revision as of 14:30, 9 September 2010
Line 1:		Line 1:
	The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.		The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.

	Here is ~~an example~~ of a redundancy host setup:		=== Primary switchover ===

			Let's see the consequences of losing the [[Primary/Secondary\|primary]] host. Here is the state of a redundancy host setup after an installation:

	[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]		[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]
Line 14:		Line 16:


	When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.		When the [[Primary/Secondary\|primary]] host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the [[Primary/Secondary\|secondary]] host.

	[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]		[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]


			=== Secondary switchover ===

			Let's see the consequences of losing the [[Primary/Secondary\|secondary]] host. Here is the state of a redundancy host setup after an installation:

			[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]


			If the [[Primary/Secondary\|secondary]] host is lost there are no effect on the system, since the [[Active/Standby\|active]] Toolpack system was already running the [[Primary/Secondary\|primary]] host.

			[[Image:host_redundancy_secondary_lost.png\|widthpx\|Host redundancy state after losing the secondary host]]


			When the [[Primary/Secondary\|secondary]] host is recovered, the system returns to its original state (just like after the installation).

			[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after the recover of the secondary host]]

Cbilodeau: reformat to be more pleasant to the eye

2010-09-09T18:11:19Z

reformat to be more pleasant to the eye

← Older revision		Revision as of 14:11, 9 September 2010
Line 5:		Line 5:
	[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]		[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]

	If the primary host is lost, two high availability mechanisms will be ~~activate. First the~~ [[Active/Standby\|standby]] Toolpack will become [[Active/Standby\|active]]~~, second the~~ [[Master/Slave\|slave]] database will become [[Master/Slave\|master]]. This will allow the system to keep functioning without manual operation (note that [[Transient Calls\| transient calls]] will be lost during the switchover), as illustrated in the following picture.
			If the primary host is lost, two high availability mechanisms will be activated:
			* [[Active/Standby\|standby]] Toolpack will become [[Active/Standby\|active]]
			* [[Master/Slave\|slave]] database will become [[Master/Slave\|master]].
			This will allow the system to keep functioning without manual operation (note that [[Transient Calls\| transient calls]] will be lost during the switchover), as illustrated in the following picture.

	[[Image:host_redundancy_primary_lost.png\|widthpx\|Host redundancy state after losing the primary host]]		[[Image:host_redundancy_primary_lost.png\|widthpx\|Host redundancy state after losing the primary host]]


	When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.		When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.

	[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]		[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]


	NOTE: The database and host redundancy mechanism are two separate features, meaning that a database switchover will not necessarily cause a host switchover as well.		NOTE: The database and host redundancy mechanism are two separate features, meaning that a database switchover will not necessarily cause a host switchover as well.

Cbilodeau: add pictures to explain the host redundancy feature

2010-09-09T18:09:45Z

add pictures to explain the host redundancy feature

← Older revision		Revision as of 14:09, 9 September 2010
Line 1:		Line 1:
	The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.		The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.

			Here is an example of a redundancy host setup:

			[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]

			If the primary host is lost, two high availability mechanisms will be activate. First the [[Active/Standby\|standby]] Toolpack will become [[Active/Standby\|active]], second the [[Master/Slave\|slave]] database will become [[Master/Slave\|master]]. This will allow the system to keep functioning without manual operation (note that [[Transient Calls\| transient calls]] will be lost during the switchover), as illustrated in the following picture.

			[[Image:host_redundancy_primary_lost.png\|widthpx\|Host redundancy state after losing the primary host]]

			When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.

			[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]

			NOTE: The database and host redundancy mechanism are two separate features, meaning that a database switchover will not necessarily cause a host switchover as well.

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

Cbilodeau: add ip teaming hotlink

2009-12-28T19:36:52Z

add ip teaming hotlink

← Older revision		Revision as of 15:36, 28 December 2009
Line 15:		Line 15:
	=== Warnings ===		=== Warnings ===

	*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support IP Teaming. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.		*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support [[Ip_Teaming/Ip_Bonding \| IP Teaming (Ip Bonding)]]. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.
	*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.		*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.

Cbilodeau: Creation

2009-12-23T20:32:22Z

Creation

New page

The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.

== Recommended Setup ==

=== Recommended Hardware ===

*Recommended host hardware components [[media:FINAL - DATA SHEET TMP7950.pdf|TMP7950 data sheet]].
*Dual power supplies is a huge plus
*The number of network interface needed by a system is application specific, but for TelcoBridges products at least 2 independent network interfaces is needed for controlling the Tmedias and another one to connect to the management network.

=== Warnings ===

*IP Teaming/ IP Bonding - TelcoBridges Hardware '''doesn't''' support IP Teaming. TelcoBridges products '''can't''' work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.
*RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.

← Older revision		Revision as of 14:30, 9 September 2010
Line 1:		Line 1:
	The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.		The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.

	Here is ~~an example~~ of a redundancy host setup:		=== Primary switchover ===

			Let's see the consequences of losing the [[Primary/Secondary\|primary]] host. Here is the state of a redundancy host setup after an installation:

	[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]		[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]
Line 14:		Line 16:


	When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.		When the [[Primary/Secondary\|primary]] host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the [[Primary/Secondary\|secondary]] host.

	[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]		[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]


			=== Secondary switchover ===

			Let's see the consequences of losing the [[Primary/Secondary\|secondary]] host. Here is the state of a redundancy host setup after an installation:

			[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]


			If the [[Primary/Secondary\|secondary]] host is lost there are no effect on the system, since the [[Active/Standby\|active]] Toolpack system was already running the [[Primary/Secondary\|primary]] host.

			[[Image:host_redundancy_secondary_lost.png\|widthpx\|Host redundancy state after losing the secondary host]]


			When the [[Primary/Secondary\|secondary]] host is recovered, the system returns to its original state (just like after the installation).

			[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after the recover of the secondary host]]

← Older revision		Revision as of 14:11, 9 September 2010
Line 5:		Line 5:
	[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]		[[Image:host_redundancy_original.png\|widthpx\|Host redundancy original state after a new installation]]

	If the primary host is lost, two high availability mechanisms will be ~~activate. First the~~ [[Active/Standby\|standby]] Toolpack will become [[Active/Standby\|active]]~~, second the~~ [[Master/Slave\|slave]] database will become [[Master/Slave\|master]]. This will allow the system to keep functioning without manual operation (note that [[Transient Calls\| transient calls]] will be lost during the switchover), as illustrated in the following picture.
			If the primary host is lost, two high availability mechanisms will be activated:
			* [[Active/Standby\|standby]] Toolpack will become [[Active/Standby\|active]]
			* [[Master/Slave\|slave]] database will become [[Master/Slave\|master]].
			This will allow the system to keep functioning without manual operation (note that [[Transient Calls\| transient calls]] will be lost during the switchover), as illustrated in the following picture.

	[[Image:host_redundancy_primary_lost.png\|widthpx\|Host redundancy state after losing the primary host]]		[[Image:host_redundancy_primary_lost.png\|widthpx\|Host redundancy state after losing the primary host]]


	When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.		When the primary host is recovered, the [[Active/Standby\|active]] Toolpack system and the [[Master/Slave\|master]] database will stay on the secondary host.

	[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]		[[Image:host_redundancy_primary_recover.png\|widthpx\|Host redundancy state after the recover of the primary host]]


	NOTE: The database and host redundancy mechanism are two separate features, meaning that a database switchover will not necessarily cause a host switchover as well.		NOTE: The database and host redundancy mechanism are two separate features, meaning that a database switchover will not necessarily cause a host switchover as well.