Use the redundancy feature to enable the system to detect and recover from the failure of signaling links on a TX 5000E board, the failure of a signaling node, or the failure of the TX 5000E board itself.
In a redundant configuration, each pair of TX boards is connected through a private Ethernet connection. If other devices are connected to the private Ethernet link, avoid overloading the link. Packets can be lost between the redundant TX boards if the connection is overloaded.
The Ethernet 3 connector of a TX 5000E board is reserved for redundancy connectivity.
This topic describes dual-node redundant signaling and single-node redundant signaling for the following types of configurations:
Note: TX 5000E boards support redundancy with other TX 5000E boards. A redundant configuration between a TX 5000E board and a TX 4000 Series board is not supported.
To connect a TX 5000E board to its redundant mate in a TDM configuration, connect Ethernet 3 on the primary board to Ethernet 3 on the backup board using a Category 5 shielded twisted pair (STP) Ethernet cable.
You must specify the IP address of the TX board’s redundant mate using the mate command in the txconfig utility. For more information, refer to the Dialogic® NaturalAccess™ Signaling Software Configuration Manual.
The following illustration shows how to set up two TX 5000E boards based on a dual-node redundant signaling server in a TDM configuration. The boards are located in two separate chassis to ensure board-level and system-level redundancy.
The following illustration shows how to set up two TX 5000E boards based on the single-node signaling server in a TDM configuration. The boards are located in the same chassis to ensure board-level redundancy.
To connect a TX 5000E board to its redundant mate in an IP network configuration, connect Ethernet 3 on the primary board to Ethernet 3 on the backup board using a Category 5 shielded twisted pair (STP) Ethernet crossover cable. Then connect the Ethernet 1 and Ethernet 2 connectors on both boards to the IP network connectors using standard Ethernet cables.
Note: Dialogic recommends using a private Ethernet link to connect the redundant boards to avoid loss or delay of vital checkpoint messages. However, if each board in the redundant pair requires a multi-homing configuration in which each board provides three separate network connections, then you can use Ethernet 3 for both the redundant pathway and for SIGTRAN network access. In this configuration, the Ethernet 3 on each board is connected to what is shown as an IP network cloud in the illustrations that follow (just as the Ethernet 1 and 2 connectors are). Be aware that this greatly increases the chance of lost or delayed checkpoint messages which can result in the backup having outdated information.
You must specify the IP address of the TX board’s redundant mate using the mate command in the txconfig utility. You must also specify the IP address and network mask of Ethernet interface 3 using the ifcreate command in the txconfig utility. For more information, refer to the Dialogic® NaturalAccess™ Signaling Software Configuration Manual.
The following illustration shows how to set up two TX 5000E boards based on a dual-node redundant signaling server in an IP network configuration. The boards are located in two separate chassis to ensure board-level and system-level redundancy.
The following illustration shows how to set up two TX 5000E boards based on a single-node signaling server in an IP network configuration. The boards are located in the same chassis to ensure board-level redundancy.
For more information on SS7 redundancy, refer to the Dialogic® TX Series SS7 Boards Health Management Developer's Reference Manual.