The SN10100 1+1 system is made of:

-  A standard SN10100 unit

-  A +1 SN10100 unit

-  One or two 1+1 patch panels

In case of failure of the active unit, the exact configuration will transfer onto the standby unit. The standby unit is then automatically activated, and continues to route the calls. 

Network connection between units of the SN10100 1+1 system: 

All units of the SN10100 1+1 system need to be connected together using two Ethernet networks. These two networks must be:

-  Independent Ethernet networks

• two for redundancy
• independent to avoid interferences between them

-  Private (No up-link to the LAN)

• to avoid interferences with other equipments
• to isolate multiple SN10100 1+1 systems from each other

Networking configuration for SN10100 1+1 system:

Each unit of the SN10100 1+1 system has only two Ethernet interfaces (named voip0 and voip1). They must be shared for network communication with external world (SIP, RTP, Sigtran, H.248), and with private communication between the two SN10100 units of the system. 

Two private VLans must be created to establish private and redundant network communication path between the two units:

-  VLan IDs are provided to SN10100 units upon initial configuration through Web Portal

-  VLans configuration in the Ethernet switches that the SN10100 units are connected to must be

• Done before starting the SN10100 units for the first time by network operator
• Must be private to ONLY the two ports the SN10100 units are connected to

How to configure units of the SN10100 1+1 system:

Initial configuration:

The first time a SN10100 unit is started, it's not yet ready to connect to other units of a SN10100 1+1 system.
It must be told what role it will occupy (standalone unit, primary/secondary unit of a 1+1 system):

-  Make sure that the unit is properly connected to the network (as described above)

-  Make sure that the VLans are properly configured in the Ethernet switches that the units are connected to (SN10100 only)

-  Connect to the Web Portal of that SN10100 unit (http://[serial_number_of_your_unit]:12358)

-  Answer the questions:

• Role (standalone, new primary, replacement primary, or secondary unit)
• VLan IDs (for SN10100 only)

-  Wait for the SN10100 unit to configure itself

• Enable eth0/eth1 interfaces
• Detect other SN10100 unit of the 1+1 system
• Synchronize with other unit of the 1+1 system, if required

-  You should then be redirected to the "standard" SN10100 Web Portal where you can configure stacks and other functionalities of the SN10100

Return unit to initial configuration:

It may be required to return a SN10100 unit to its initial state, for example:

-  A SN10100 Standard unit was used as a standalone unit, now needs to be used as part of a 1+1 system

-  A SN10100 Spare unit was used as a replacement in a 1+1 system, and must now be removed in order to insert back the repaired unit

To return the unit to its "initial" state (disconnected from other units, waiting to be told if it's standalone, primary or secondary):

-  Connect to the unit's Web Portal (http://[serial_number_of_your_unit]:12358)

-  Click on "Hosts" on the left menu of the Web Portal

-  Click on "Status" tab

-  Click on the status of the SN10100 unit to return to "initial" state

-  Select "Reset Host Role" action from the popup menu

-  Click "Apply"

-  Wait 15-30 seconds, and re-connect to the Web Portal. You should now be in the "Initial configuration" web portal of that SN10100 unit

Web Portal configuration for the SN10100 1+1 system:

The configuration of the SN10100 1+1 system is almost identical to the configuration of a standalone SN10100 unit.

Differences are:

-  A 1+1 Group is defined to bind the two units into a redundant group

-  Two "Hardware" are present

• One for each SN10100 unit of the 1+1 system
• Only the primary unit has a "configuration" that can be modified (TDM Line Interfaces, protocol stacks)
• Each has its own status (status of Line Interfaces and protocol stacks only visible for the unit that's actually active)

-  Two "Hosts" are present

• One for each SN10100 unit of the 1+1 system
• Each has its own status (disk usage, CPU usage, ...)
• Each has its list of applications running on them (identical list of applications on both units)

-  The configuration of the ISUP stack is made redundant on the two units

• The ISUP stack provides "no loss of active call" redundancy by already running as a standby on the secondary unit even when it's not activated. This is not (yet) possible for other protocol stacks.

How redundancy is achieved:

The SN10100 system contains

-  Host server, running call control applications, web portal, and other OAM-related applications

-  Telecommunication unit, running protocol stacks, and having hardware resources to process voice (TDM, or VOIP)

Notes:

-  The SN10100 unit contains both the host server and the Telecommunication unit in the same box.

Redundancy of the applications:

-  The applications running on the host server are redundant by having one copy of each application running on each unit.

-  In case of failure of an application, the corresponding application on the other unit is activated to replace the failed application.

-  In case the whole host server unit fails, all applications on the other unit are activated.

Redundancy of the Telecommunication units:

-  Telecommunications units used in pairs (1+1)

-  Both are connected to the TDM network, and to the IP network

• One is active (driving the signal on the TDM network, assigned an IP address on the VOIP network)
• One is standby (not driving the TDM network, no IP assigned on the VOIP network)

-  When one unit fails

• the other unit is activated with the exact same configuration as the primary units
• the other unit starts driving the TDM network
• the other unit is assigned the IP address (moved from the primary) on the VOIP network)