High Availability - Revision history

Allyntree at 15:38, 30 March 2022

2022-03-30T15:38:18Z

← Older revision		Revision as of 11:38, 30 March 2022
Line 1:		Line 1:
	((DISPLAYTITLE:High Availability}}		{{DISPLAYTITLE:High Availability}}
	(Click here for [[FreeSBC:1%2B1_Configuration\|ProSBC High Availability and 1+1]])		(Click here for [[FreeSBC:1%2B1_Configuration\|ProSBC High Availability and 1+1]])

Allyntree at 15:38, 30 March 2022

2022-03-30T15:38:00Z

← Older revision		Revision as of 11:38, 30 March 2022
Line 1:		Line 1:
			((DISPLAYTITLE:High Availability}}
	(Click here for [[FreeSBC:1%2B1_Configuration\|ProSBC High Availability and 1+1]])		(Click here for [[FreeSBC:1%2B1_Configuration\|ProSBC High Availability and 1+1]])

Luc Morissette: removed "known limitiations"

2022-03-30T14:04:28Z

removed "known limitiations"

← Older revision		Revision as of 10:04, 30 March 2022
Line 112:		Line 112:
	*You are able to add/ remove / modify gateway routes (this requires a configuration reload)		*You are able to add/ remove / modify gateway routes (this requires a configuration reload)
	*You are able to add / remove / modify gateway accounts (this requires a configuration reload)		*You are able to add / remove / modify gateway accounts (this requires a configuration reload)


	~~=== Known limitations ===~~
	~~We have identified the following limitations with the enhanced high availability support available in Toolpack v2.3.~~
	*It is not always possible to recover from a double fault. For example, should both configuration databases go offline, any telephony applications that use these databases will cease to function correctly.

	== References ==		== References ==

Harry Wakefield at 15:45, 14 September 2020

2020-09-14T15:45:53Z

← Older revision		Revision as of 11:45, 14 September 2020
Line 1:		Line 1:
			(Click here for [[FreeSBC:1%2B1_Configuration\|ProSBC High Availability and 1+1]])

	High availability refers to the design of a system as well as its ability to continue operating following one or more component faults. Concepts that are associated with high availability include:		High availability refers to the design of a system as well as its ability to continue operating following one or more component faults. Concepts that are associated with high availability include:

Luc Morissette: /* Automatic protection mechanism on the TMedia */

2018-10-04T15:06:51Z

Automatic protection mechanism on the TMedia

← Older revision		Revision as of 11:06, 4 October 2018
Line 33:		Line 33:

	==== Automatic protection mechanism on the TMedia ====		==== Automatic protection mechanism on the TMedia ====
	On board process monitoring: dead-lock or crashed processes are automatically detected and the ~~adaptor~~ is rebooted to ensure minimal downtime.		On board process monitoring: dead-lock or crashed processes are automatically detected and the unit is rebooted to ensure minimal downtime.
	HW watch dog: When a Toolpack system is active, the TMedia unit is polled continuously by the System Manager. If this polling stops, it means the TMedia lost contact with the Toolpack applications and it will reboot automatically if communication is not restored in a timely manner.		HW watch dog: When a Toolpack system is active, the TMedia unit is polled continuously by the System Manager. If this polling stops, it means the TMedia lost contact with the Toolpack applications and it will reboot automatically if communication is not restored in a timely manner.

William Wong: /* IP Network (SIP Signaling) (1+1) */

2018-10-04T07:30:36Z

IP Network (SIP Signaling) (1+1)

← Older revision		Revision as of 03:30, 4 October 2018
Line 18:		Line 18:

	==== IP Network (SIP Signaling) (1+1) ====		==== IP Network (SIP Signaling) (1+1) ====
	For outgoing calls, the system can be configured such that you can use alternate addresses to reach the SIP Proxy, so if one network path is down, it will use the other one. For incoming calls, you can configure SIP stacks on two separate IP interfaces so that if one is not reachable by a peer, the second can be reached. Tmedia and FreeSBC also offer mechanisms such as virtual port/VLAN with associated IP interface and address, meaning many virtual ports/VLANs can be created one physical port (or in case of Tmedia, two physical in bonding configuration) that each virtual port/VLAN can have its own IP address. Therefore, for outgoing and incoming SIP calls, different IP paths can act as redundancy on one physical interface as well as two physical interfaces with bonding ~~that~~ Tmedia can provide internal ports protection when one physical port is down. Should all voip ports are down on one unit, it requires the whole unit to be detected down before a failover to the other unit is taking place that ~~taking~~ the same IP interfaces/~~address~~ and resuming the call traffic.		For outgoing calls, the system can be configured such that you can use alternate addresses to reach the SIP Proxy, so if one network path is down, it will use the other one. For incoming calls, you can configure SIP stacks on two separate IP interfaces so that if one is not reachable by a peer, the second can be reached. Tmedia and FreeSBC also offer mechanisms such as virtual port/VLAN with associated IP interface and address, meaning many virtual ports/VLANs can be created on one physical port (or in case of Tmedia, two physical ports in bonding configuration) that each virtual port/VLAN can have its own IP address. Therefore, for outgoing and incoming SIP calls, different IP paths can act as redundancy on one physical interface as well as on two physical interfaces with bonding which Tmedia can further provide internal ports protection when one physical port is down. Should all voip ports are down on one unit, it requires the whole unit to be detected down before a failover to the other unit is taking place that replacing the same IP interfaces/addresses onto another unit and resuming the call traffic.

	==== IP Network (Voice Path) (1+1) ====		==== IP Network (Voice Path) (1+1) ====

William Wong: /* Prerequisites */

2018-10-04T07:06:47Z

Prerequisites

← Older revision		Revision as of 03:06, 4 October 2018
Line 44:		Line 44:

	=== Prerequisites ===		=== Prerequisites ===

			In case of two external hosts,

	The first prerequisite for enabling HA database functionality is to have a secondary server available running the MySQL database software. To configure that secondary server you would follow the same prerequisites for a normal installation of Toolpack on that machine. One thing to note with this change is that the IP address for the primary, as well as the secondary server, must now be made explicit (using ‘localhost’ or ‘127.0.0.1’ is no longer permitted). You will also want to activate database replication functionality using MySQL’s procedures for achieving this.		The first prerequisite for enabling HA database functionality is to have a secondary server available running the MySQL database software. To configure that secondary server you would follow the same prerequisites for a normal installation of Toolpack on that machine. One thing to note with this change is that the IP address for the primary, as well as the secondary server, must now be made explicit (using ‘localhost’ or ‘127.0.0.1’ is no longer permitted). You will also want to activate database replication functionality using MySQL’s procedures for achieving this.

Line 50:		Line 53:

	:[[Image:Enhanced-HA-overview.jpg]]		:[[Image:Enhanced-HA-overview.jpg]]


	=== Testing this feature ===		=== Testing this feature ===

William Wong: /* IP Network (SIP Signaling) (1+1) */

2018-10-04T07:01:02Z

IP Network (SIP Signaling) (1+1)

← Older revision		Revision as of 03:01, 4 October 2018
Line 18:		Line 18:

	==== IP Network (SIP Signaling) (1+1) ====		==== IP Network (SIP Signaling) (1+1) ====
	For outgoing calls, the system can be configured such that you can use alternate addresses to reach the SIP Proxy, so if one network path is down, it will use the other one. For incoming calls, you can configure SIP stacks on two separate IP interfaces so that if one is not reachable by a peer, the second can be reached. Tmedia and FreeSBC also offer mechanisms such as virtual port/VLAN with associated IP interface and address, meaning many virtual ports/VLANs can be created one physical port (or in case of Tmedia, two physical in bonding configuration) that each virtual port/VLAN can have its own IP address. Therefore, for outgoing and incoming SIP calls, different IP paths can act as redundancy on one physical interface as well as two physical interfaces with bonding that Tmedia can provide internal ports protection when one physical port is down. Should all voip ports are down on one unit, it requires the whole unit to be detected down before a failover to the other unit is taking place that taking the same IP interfaces/address and resuming the traffic.		For outgoing calls, the system can be configured such that you can use alternate addresses to reach the SIP Proxy, so if one network path is down, it will use the other one. For incoming calls, you can configure SIP stacks on two separate IP interfaces so that if one is not reachable by a peer, the second can be reached. Tmedia and FreeSBC also offer mechanisms such as virtual port/VLAN with associated IP interface and address, meaning many virtual ports/VLANs can be created one physical port (or in case of Tmedia, two physical in bonding configuration) that each virtual port/VLAN can have its own IP address. Therefore, for outgoing and incoming SIP calls, different IP paths can act as redundancy on one physical interface as well as two physical interfaces with bonding that Tmedia can provide internal ports protection when one physical port is down. Should all voip ports are down on one unit, it requires the whole unit to be detected down before a failover to the other unit is taking place that taking the same IP interfaces/address and resuming the call traffic.

	==== IP Network (Voice Path) (1+1) ====		==== IP Network (Voice Path) (1+1) ====

William Wong: /* IP Network (Voice Path) (1+1) */

2018-10-04T07:00:40Z

IP Network (Voice Path) (1+1)

← Older revision		Revision as of 03:00, 4 October 2018
Line 21:		Line 21:

	==== IP Network (Voice Path) (1+1) ====		==== IP Network (Voice Path) (1+1) ====
	We support redundant voice path for SIP calls. If one path is down, the other one will be selected for all new calls. If both paths are up, they can be used in load sharing. Note however, that if a path is lost, the active calls currently using that path will not be switched automatically to the other path (this would require sending a SIP re-INVITE because the IP address of the second interface is not the same as the address of the first interface. Tmedia also offers IP bonding that a virtual IP can be created on two physical interface thus protecting against any interface down while still using the same IP address.		We support redundant voice path for SIP calls. If one path is down, the other one will be selected for all new calls. If both paths are up, they can be used in load sharing. Note however, that if a path is lost, the active calls currently using that path will not be switched automatically to the other path (this would require sending a SIP re-INVITE because the IP address of the second interface is not the same as the address of the first interface. Tmedia also offers IP bonding that a virtual IP can be created on two physical interface thus protecting against any interface down while still using the same IP address. The resuming of call traffic should all voip ports are down follow the same mechanism as described in IP Network (SIP signalling)(1+1) above.

	==== SS7 Redundancy (N+1) ====		==== SS7 Redundancy (N+1) ====

William Wong: /* IP Network (SIP Signaling) (1+1) */

2018-10-04T06:58:33Z

IP Network (SIP Signaling) (1+1)

← Older revision		Revision as of 02:58, 4 October 2018
Line 18:		Line 18:

	==== IP Network (SIP Signaling) (1+1) ====		==== IP Network (SIP Signaling) (1+1) ====
	For outgoing calls, the system can be configured such that you can use alternate addresses to reach the SIP Proxy, so if one network path is down, it will use the other one. For incoming calls, you can configure SIP stacks on two separate IP interfaces so that if one is not reachable by a peer, the second can be reached. Tmedia and FreeSBC also offer mechanisms such as virtual port/VLAN with associated IP interface and address, meaning many virtual ports/VLANs can be created one physical port (or in case of Tmedia, two physical in bonding configuration) that each virtual port/VLAN can have its own IP address. Therefore, for outgoing and incoming SIP calls, different IP paths can act as redundancy on one physical interface as well as two physical interfaces with bonding that Tmedia can provide internal ports protection when one physical port is down.		For outgoing calls, the system can be configured such that you can use alternate addresses to reach the SIP Proxy, so if one network path is down, it will use the other one. For incoming calls, you can configure SIP stacks on two separate IP interfaces so that if one is not reachable by a peer, the second can be reached. Tmedia and FreeSBC also offer mechanisms such as virtual port/VLAN with associated IP interface and address, meaning many virtual ports/VLANs can be created one physical port (or in case of Tmedia, two physical in bonding configuration) that each virtual port/VLAN can have its own IP address. Therefore, for outgoing and incoming SIP calls, different IP paths can act as redundancy on one physical interface as well as two physical interfaces with bonding that Tmedia can provide internal ports protection when one physical port is down. Should all voip ports are down on one unit, it requires the whole unit to be detected down before a failover to the other unit is taking place that taking the same IP interfaces/address and resuming the traffic.

	==== IP Network (Voice Path) (1+1) ====		==== IP Network (Voice Path) (1+1) ====