Configuring SS7 Redundancy - 10.5.0


Configure two Physical IMGs in the same Logical IMG group to be a redundant pair for SS7 signaling. All subsequent IMG's added to this Logical IMG Group are automatically considered Remote SS7 Nodes whose CIC's are controlled by the Primary and Secondary nodes.


Important Notes on SS7 Redundancy:

GCEMS is the administrator when SS7 redundancy is configured. A loss of ethernet communications between the GCEMS server and IMG configured as a server node could have an impact on service. Below are a few examples of what would happen in the case of losing GCEMS communication.


  1. If GCEMS loses communication with SS7 server nodes the system will remain up and will pass traffic. Switchovers will -NOT- occur since all redundant information is passed between the Redundant and Standby IMG through RCOMM signaling.

  2. If communication is lost between the GCEMS server and the SS7 server node --and-- communication is lost between the Redundant and Standby SS7 server nodes (Loss of RCOMM signaling) then the following will happen:


Pre-requisite to Configuring SS7 Redundancy:

  1. Create the Logical IMG to which the SS7 nodes will be assigned.

  2. Create the two Physical IMGs that will be the Primary and Secondary SS7 nodes.

  3. Add facilities to each IMG.


Configure Redundant SS7 Signaling on the Primary IMG

See Configuring SS7 Signaling for the general procedure, setting specific fields in panes as noted below.


  1. SS7 Signaling (See Creating_an_SS7_Signaling_Entry)

  1. Primary SS7 Links (See  Configuring_SS7_Signaling_Links.)

  1. Secondary SS7 Links (See  Configuring_SS7_Signaling_Links.) Note: The configuration of these links are done in ClientView on the Primary IMG as the SS7 Stack is configured on the primary IMG only.