FreeSBC:1+1 Configuration - Revision history

William Wong: /* ProSBC 1+1 Initial Configuration */

2020-02-12T09:44:42Z

ProSBC 1+1 Initial Configuration

← Older revision		Revision as of 05:44, 12 February 2020
Line 27:		Line 27:
	== ProSBC 1+1 Initial Configuration ==		== ProSBC 1+1 Initial Configuration ==

	After finishing ProSBC software installation by following installation guide in [[ProSBC]], at ProSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/~~parimary~~ ProSBC instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same ProSBC Initial Configuration for secondary unit, and select secondary for the secondary ProSBC instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other VLAN IDs not conflicting with management and voip networks.		After finishing ProSBC software installation by following installation guide in [[ProSBC]], at ProSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/primary ProSBC instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same ProSBC Initial Configuration for secondary unit, and select secondary for the secondary ProSBC instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other VLAN IDs not conflicting with management and voip networks.

	== Network device discovery ==		== Network device discovery ==

Luc Morissette: Changed from FreeSBC to ProSBC (1+1 is only available on ProSBC)

2019-07-12T15:31:33Z

Changed from FreeSBC to ProSBC (1+1 is only available on ProSBC)

← Older revision		Revision as of 11:31, 12 July 2019
Line 1:		Line 1:
	{{DISPLAYTITLE:~~FreeSBC~~:1+1 Configuration}}		{{DISPLAYTITLE:ProSBC:1+1 Configuration}}

	== Requirements ==		== Requirements ==

	~~FreeSBC~~ 1+1 requires a second hardware unit/instance to provide high availability and redundancy support in active/standby configuration mode. For virtual machines setup, this can be a second instance on the system, while baremetal setup requires a separate hardware unit, that acting as the secondary unit ideally with the same resource as the primary unit to provide same performance during active/standby failover. The secondary ~~FreeSBC~~ unit must have the same network devices configuration as the primary ~~FreeSBC~~ unit. See [[~~FreeSBC~~]] for different installation guides for the same requirement of secondary ~~FreeSBC~~ setup.		ProSBC 1+1 requires a second hardware unit/instance to provide high availability and redundancy support in active/standby configuration mode. For virtual machines setup, this can be a second instance on the system, while baremetal setup requires a separate hardware unit, that acting as the secondary unit ideally with the same resource as the primary unit to provide same performance during active/standby failover. The secondary ProSBC unit must have the same network devices configuration as the primary ProSBC unit. See [[ProSBC]] for different installation guides for the same requirement of secondary ProSBC setup.

	~~FreeSBC~~ 1+1 requires a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ~~FreeSBC~~ will process. The third network will be used as a control interface connecting to another host in ~~FreeSBC~~ 1+1 configuration for control purpose.		ProSBC 1+1 requires a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration for control purpose.


Line 12:		Line 12:
	== Network setup ==		== Network setup ==

	~~FreeSBC~~ in protected (1+1) system configuration requires additional network requirement as depicted in below network configuration.		ProSBC in protected (1+1) system configuration requires additional network requirement as depicted in below network configuration.

	==== 1+1 setup ====		==== 1+1 setup ====

	In addition to the regular networks required for management and VoIP networks, the two ~~FreeSBC~~ instances need access to two control separate networks allowing to exchange check-pointing information. These networks are private to the ~~FreeSBC~~ and should never be shared or be visible to non-TelcoBridges ~~FreeSBC~~ equipment.		In addition to the regular networks required for management and VoIP networks, the two ProSBC instances need access to two control separate networks allowing to exchange check-pointing information. These networks are private to the ProSBC and should never be shared or be visible to non-TelcoBridges ProSBC equipment.

	Although a single control network is sufficient to achieve the 1+1 function, it is not recommended by TelcoBridges ~~FreeSBC~~ unless the operator fully controls all network segments and can guarantee it can never fail at both the physical/virtual and routing (IP) layer. In most cases, having two separate control networks going through independent network devices, switches and routers is the only way to ensure 'no single point of failure'.		Although a single control network is sufficient to achieve the 1+1 function, it is not recommended by TelcoBridges ProSBC unless the operator fully controls all network segments and can guarantee it can never fail at both the physical/virtual and routing (IP) layer. In most cases, having two separate control networks going through independent network devices, switches and routers is the only way to ensure 'no single point of failure'.

	Combining the redundant network requirements for redundancy need, the deployment of a ~~FreeSBC~~ 1+1 system requires multiple networks as depicted below:		Combining the redundant network requirements for redundancy need, the deployment of a ProSBC 1+1 system requires multiple networks as depicted below:


	[[File:Tsbc-sw-1p1.png‎‎]]		[[File:Tsbc-sw-1p1.png‎‎]]

	== ~~FreeSBc~~ 1+1 Initial Configuration ==		== ProSBC 1+1 Initial Configuration ==

	After finishing ~~FreeSBC~~ software installation by following installation guide in [[~~FreeSBC~~]], at ~~FreeSBC~~ Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/parimary ~~FreeSBC~~ instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same ~~FreeSBC~~ Initial Configuration for secondary unit, and select secondary for the secondary ~~FreeSBC~~ instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other VLAN IDs not conflicting with management and voip networks.		After finishing ProSBC software installation by following installation guide in [[ProSBC]], at ProSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/parimary ProSBC instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same ProSBC Initial Configuration for secondary unit, and select secondary for the secondary ProSBC instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other VLAN IDs not conflicting with management and voip networks.

	== Network device discovery ==		== Network device discovery ==

	Once all networks have been physically (or virtually) connected to the ~~FreeSBC~~ instance, the system can be started. Upon first bootup at ~~FreeSBC~~ Initial Configuration (see [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration]]) with indication for requirment to connect secondary ~~FreeSBC~~ unit to the ~~FreeSBC~~ system (or after an operator initiated 'network device role' reset), the ~~FreeSBC~~ web portal will show a network device assignation page. This page is used to identify the role of each detected devices. As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN). Once the role is selected, the operator can enter a name for each. In case of ~~FreeSBc~~ 1+1 setup, 'ctrl0'/'ctr1' role assignment is required to be done on one or two network device. Every configured/detected network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.		Once all networks have been physically (or virtually) connected to the ProSBC instance, the system can be started. Upon first bootup at ProSBC Initial Configuration (see [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration]]) with indication for requirment to connect secondary ProSBC unit to the ProSBC system (or after an operator initiated 'network device role' reset), the ProSBC web portal will show a network device assignation page. This page is used to identify the role of each detected devices. As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN). Once the role is selected, the operator can enter a name for each. In case of ProSBC 1+1 setup, 'ctrl0'/'ctr1' role assignment is required to be done on one or two network device. Every configured/detected network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.

	The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).		The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).
Line 38:		Line 38:
	[[File:TSBC_SW_choose_LAN_interface_role_1.png\|600px]]		[[File:TSBC_SW_choose_LAN_interface_role_1.png\|600px]]

	== ~~FreeSBC~~ +1 License ==		== ProSBC +1 License ==

	When retrieving SBC license, it is required to retrieve the +1 ~~FreeSBC~~ license for the secondarfy ~~FreeSBC~~ unit. This would be the same procedure for obtaining the normal license for ~~FreeSBC~~ with host name, product activation key, and license seed in 'get and rectrieve license' from 'package and maintenance' page. See [[Toolpack:Retreiving_a_License_TSBC_A\|Retrieving a License for SBC Units]].		When retrieving SBC license, it is required to retrieve the +1 ProSBC license for the secondarfy ProSBC unit. This would be the same procedure for obtaining the normal license for ProSBC with host name, product activation key, and license seed in 'get and rectrieve license' from 'package and maintenance' page. See [[Toolpack:Retreiving_a_License_TSBC_A\|Retrieving a License for SBC Units]].

	== Configuring ~~FreeSBC~~ ==		== Configuring ProSBC ==

	For configuring ~~FreeSBC~~ 1+1, it is required only to configure the primary ~~FreeSBC~~. The same main configuration will be pushed to secondary ~~FreeSBC~~ unit, while two instances will have two different management interfaces, and VOIP interface(s) will be automatically setup across primary and secondary ~~FreeSBC~~ instances in such a way that protection/redundancy on this interface will be triggered should active/standby failover is taking place. See [[Sbc_Tutorial_Guide_v3.0\|configure the ~~FreeSBC~~]]		For configuring ProSBC 1+1, it is required only to configure the primary ProSBC. The same main configuration will be pushed to secondary ProSBC unit, while two instances will have two different management interfaces, and VOIP interface(s) will be automatically setup across primary and secondary ProSBC instances in such a way that protection/redundancy on this interface will be triggered should active/standby failover is taking place. See [[Sbc_Tutorial_Guide_v3.0\|configure the ProSBC]]

William Wong: /* Network device discovery */

2018-09-26T06:17:53Z

Network device discovery

← Older revision		Revision as of 02:17, 26 September 2018
Line 34:		Line 34:

	The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).		The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).


	[[File:TSBC_SW_choose_LAN_interface_role_1.png\|600px]]		[[File:TSBC_SW_choose_LAN_interface_role_1.png\|600px]]

William Wong: /* 1+1 setup */

2018-09-26T06:17:24Z

1+1 setup

← Older revision		Revision as of 02:17, 26 September 2018
Line 21:		Line 21:

	Combining the redundant network requirements for redundancy need, the deployment of a FreeSBC 1+1 system requires multiple networks as depicted below:		Combining the redundant network requirements for redundancy need, the deployment of a FreeSBC 1+1 system requires multiple networks as depicted below:


	[[File:Tsbc-sw-1p1.png‎‎]]		[[File:Tsbc-sw-1p1.png‎‎]]

William Wong: /* Requirements */

2018-09-26T06:17:07Z

Requirements

← Older revision		Revision as of 02:17, 26 September 2018
Line 3:		Line 3:
	== Requirements ==		== Requirements ==

	FreeSBC 1+1 requires a second hardware unit/instance to provide high availability and redundancy support in active/standby configuration mode. For virtual machines setup, this can be a second instance on the system, while baremetal setup requires a separate hardware unit, that acting as the secondary unit ideally with the same resource as the primary unit to provide same performance during active/standby failover. See [[FreeSBC]] for different installation guides for the same requirement of secondary FreeSBC setup.		FreeSBC 1+1 requires a second hardware unit/instance to provide high availability and redundancy support in active/standby configuration mode. For virtual machines setup, this can be a second instance on the system, while baremetal setup requires a separate hardware unit, that acting as the secondary unit ideally with the same resource as the primary unit to provide same performance during active/standby failover. The secondary FreeSBC unit must have the same network devices configuration as the primary FreeSBC unit. See [[FreeSBC]] for different installation guides for the same requirement of secondary FreeSBC setup.

	FreeSBC 1+1 requires a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration for control purpose.		FreeSBC 1+1 requires a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration for control purpose.

William Wong: /* FreeSBc 1+1 Initial Configuration */

2018-09-26T06:11:53Z

FreeSBc 1+1 Initial Configuration

← Older revision		Revision as of 02:11, 26 September 2018
Line 26:		Line 26:
	== FreeSBc 1+1 Initial Configuration ==		== FreeSBc 1+1 Initial Configuration ==

	After finishing FreeSBC software installation by following installation guide in [[FreeSBC]], at FreeSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/parimary FreeSBC instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same FreeSBC Initial Configuration for secondary unit, and select secondary for the secondary FreeSBC instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other ~~VLANs~~ not conflicting with management and voip networks.		After finishing FreeSBC software installation by following installation guide in [[FreeSBC]], at FreeSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/parimary FreeSBC instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same FreeSBC Initial Configuration for secondary unit, and select secondary for the secondary FreeSBC instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other VLAN IDs not conflicting with management and voip networks.

	== Network device discovery ==		== Network device discovery ==

William Wong: /* FreeSBc 1+1 Initial Configuration */

2018-09-26T06:11:18Z

FreeSBc 1+1 Initial Configuration

← Older revision		Revision as of 02:11, 26 September 2018
Line 26:		Line 26:
	== FreeSBc 1+1 Initial Configuration ==		== FreeSBc 1+1 Initial Configuration ==

	After finishing FreeSBC software installation by following installation guide in [[FreeSBC]], at FreeSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/parimary FreeSBC instance. Do the same FreeSBC Initial Configuration for secondary unit, and select secondary for the secondary FreeSBC instance.		After finishing FreeSBC software installation by following installation guide in [[FreeSBC]], at FreeSBC Initial Configuration section, when asked to choose SBC configuration, select 'As part of a redundanct system' and 'primary' for main/parimary FreeSBC instance, and not getting configuration from secondary unit, then follow the instructions to complete the configuration. Do the same FreeSBC Initial Configuration for secondary unit, and select secondary for the secondary FreeSBC instance, with configuration from primary unit. Choose VLANs 710 and 711 for Ctrl0 and Ctrl1 networks respectively, or any other VLANs not conflicting with management and voip networks.

	== Network device discovery ==		== Network device discovery ==

William Wong: /* FreeSBC +1 License */

2018-09-26T05:16:37Z

FreeSBC +1 License

← Older revision		Revision as of 01:16, 26 September 2018
Line 38:		Line 38:
	== FreeSBC +1 License ==		== FreeSBC +1 License ==

	When retrieving SBC license, it is required to retrieve the +1 FreeSBC license for the secondarfy FreeSBC unit. This would be the same procedure for obtaining the normal license for FreeSBC with host name, product key, and license seed in "get and rectrieve license" from "package and maintenance" page. See [[Toolpack:Retreiving_a_License_TSBC_A\|Retrieving a License for SBC Units]].		When retrieving SBC license, it is required to retrieve the +1 FreeSBC license for the secondarfy FreeSBC unit. This would be the same procedure for obtaining the normal license for FreeSBC with host name, product activation key, and license seed in 'get and rectrieve license' from 'package and maintenance' page. See [[Toolpack:Retreiving_a_License_TSBC_A\|Retrieving a License for SBC Units]].

	== Configuring FreeSBC ==		== Configuring FreeSBC ==

	For configuring FreeSBC 1+1, it is required only to configure the primary FreeSBC. The same main configuration will be pushed to secondary FreeSBC unit, while two instances will have two different management interfaces, and VOIP interface(s) will be automatically setup across primary and secondary FreeSBC instances in such a way that protection/redundancy on this interface will be triggered should active/standby failover is taking place. See [[Sbc_Tutorial_Guide_v3.0\|configure the FreeSBC]]		For configuring FreeSBC 1+1, it is required only to configure the primary FreeSBC. The same main configuration will be pushed to secondary FreeSBC unit, while two instances will have two different management interfaces, and VOIP interface(s) will be automatically setup across primary and secondary FreeSBC instances in such a way that protection/redundancy on this interface will be triggered should active/standby failover is taking place. See [[Sbc_Tutorial_Guide_v3.0\|configure the FreeSBC]]

William Wong: /* Configuring FreeSBC */

2018-09-26T05:15:57Z

Configuring FreeSBC

← Older revision		Revision as of 01:15, 26 September 2018
Line 42:		Line 42:
	== Configuring FreeSBC ==		== Configuring FreeSBC ==

	For configuring FreeSBC 1+1, it is required only to configure the primary FreeSBC. The same main configuration will be pushed to secondary FreeSBC unit, while two instances will have two different management interfaces, and VOIP interface(s) will be automatically setup across primary and secondary FreeSBC instances such that a protection/redundancy on this interface will be triggered should active/standby failover is taking place. See [[Sbc_Tutorial_Guide_v3.0\|configure the FreeSBC]]		For configuring FreeSBC 1+1, it is required only to configure the primary FreeSBC. The same main configuration will be pushed to secondary FreeSBC unit, while two instances will have two different management interfaces, and VOIP interface(s) will be automatically setup across primary and secondary FreeSBC instances in such a way that protection/redundancy on this interface will be triggered should active/standby failover is taking place. See [[Sbc_Tutorial_Guide_v3.0\|configure the FreeSBC]]

William Wong: /* Network device discovery */

2018-09-26T05:12:22Z

Network device discovery

← Older revision		Revision as of 01:12, 26 September 2018
Line 30:		Line 30:
	== Network device discovery ==		== Network device discovery ==

	Once all networks have been physically (or virtually) connected to the FreeSBC instance, the system can be started. Upon first bootup at FreeSBC Initial Configuration with indication for requirment to connect secondary FreeSBC unit to the FreeSBC system (or after an operator initiated 'network device role' reset), the FreeSBC web portal will show a network device assignation page. This page is used to identify the role of each detected devices. As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN). Once the role is selected, the operator can enter a name for each. In case of FreeSBc 1+1 setup, 'ctrl0'/'ctr1' role assignment is required to be done on one or two network device. Every configured/detected network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.		Once all networks have been physically (or virtually) connected to the FreeSBC instance, the system can be started. Upon first bootup at FreeSBC Initial Configuration (see [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration]]) with indication for requirment to connect secondary FreeSBC unit to the FreeSBC system (or after an operator initiated 'network device role' reset), the FreeSBC web portal will show a network device assignation page. This page is used to identify the role of each detected devices. As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN). Once the role is selected, the operator can enter a name for each. In case of FreeSBc 1+1 setup, 'ctrl0'/'ctr1' role assignment is required to be done on one or two network device. Every configured/detected network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.

	The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).		The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).