IMG 1010 - Configuring SS7 Redundancy - 10.5.1
Overview:
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.
When configuring SS7 Redundancy, each node (Primary, Secondary, or Remote Node) that will terminate links must have an SS7 Link license created for that node. Also each node that will have CIC's configured on it must have an SS7_ISUP license created for it.
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.
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.
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:
The SS7 server node will reset itself.
The SS7 server standby/peer node will take over all communications.
The SS7 server node will not be able to re-configure since it cannot communicate with the GCEMS. Therefore redundancy cannot be restored until communication between the SS7 server node and GCEMS server is restored. This reset is accomplished so that there can never be a scenario where both SS7 server nodes get into an Active/Active situation.
Pre-requisite to Configuring SS7 Redundancy:
Create the IMG 1010 - Logical IMG to which the SS7 nodes will be assigned.
Create the two IMG 1010 - Physical IMG that will be the Primary and Secondary SS7 nodes.
Add IMG 1010 - Configuring T1 or E1 Bearer Spans - 10.5.x to each IMG.
See IMG 1010 - Configuring SS7 Signaling - 10.5.1 for the general procedure, setting specific fields in panes as noted below.
Configure Redundant SS7 Signaling on the Primary IMG
The first step to creating SS7 Signaling etc is to configure a signaling entry. The signaling entry will enable you to configure different types of signaling protocols such as SS7, SIP, ISDN, and H.323. To create the Signaling entry, right-click on the Physical IMG object (IMG Name) and select New Signaling. A Signaling object will get created. Commit the current object.
Create an SS7 Signaling Entry. Right Click on Signaling Entry created and select New SS7. An SS7 Signaling Pane will appear. See screen capture below.
In the Redundancy Configuration field select Primary from drop down menu
In the Peer Logical Node ID field select the ID of the IMG which will be the Secondary SS7 server node. All the IMG's ID's configured will be in a drop down menu. See screen capture below.
Under the SS7 Primary object is where the SS7 signaling stack objects will be created. Right-click SS7 Primary object and select New SS7 Stack. See IMG 1010 - SS7 Stack for more information on how to configure the SS7 Stack Pane. Commit this object
Create an SS7 Link Set by right clicking on SS7 Stack Object and selecting New SS7 Link Set. See IMG 1010 - SS7 Link Set for more information on how to configure the SS7 Link Set Pane. Commit this object
Create an SS7 Link by right clicking on SS7 Link Set object and selecting New SS7 Link. Select from drop down list in the IMG field which IMG the link will be associated with. See screen capture below. See IMG 1010 - SS7 Link for more information on how to configure this object. You can configure up to 64 links per Logical Node Group.
Create an SS7 Route by right clicking on SS7 Link Set and selecting New SS7 Route. You can configure up to 512 routes per IMG. See IMG 1010 - SS7 Route for more information on how to configure the SS7 Route Pane. Commit this object.
SS7 Redundancy with Stacks, Links, Link Sets, and Routes have been accomplished. The Primary and Secondary servers are configured. If the Primary server were to go down then the Secondary would take over and continue processing calls etc.