Configuring SS7 Redundant Nodes

The procedure below configures one 2020 IMG as the Active SS7 node and a second 2020 IMG as the standby or peer SS7 node. Both nodes are configured under one Logical Node Group. After configuring the redundant SS7 nodes, the ISUP Groups and CICs will be configured.

 

Note: 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:

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

  1. If the BDN EMS loses communication with any of the SS7 server nodes the system will remain up and will pass traffic. However, switchovers will -NOT- occur since all redundant information is passed between the Active and Standby 2020 IMG through RCOMM signaling.

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

 

Procedure

Follow procedure below to configure SS7 redundancy between a Primary/Active and Secondary/Standby nodes.

 

Initial Configuration

Before configuring the SS7 objects, the basic objects must first be configured. Refer to the Basic Configurations topic for information on configuring the initial functionality needed for most configurations.

 

Create Primary/Active and Secondary/Standby SS7 nodes

  1. Create the Signaling entry object. Right click on the Physical Node that will be the Primary SS7 node and select New Signaling. A signaling object will get created. The signaling object created is a parent object to multiple signaling protocols and no configuration is needed here. Refer to the Signaling topic for more information on this topic.
  2. Right click on the Signaling object created and select New SS7. An SS7 signaling pane will appear. In the Redundancy Configuration field select Primary from drop down menu since this will be the Active SS7 node.
  3. In the Peer Logical Node ID field select from the drop down menu, the ID of the node that will be the Secondary/Standby node. See the screen capture below.

SC_SS7_Primary_Peer_Select.png

  1. Create the SS7 signaling stacks. Right click on the SS7 Primary object and select New SS7 Stack. In the OPC field, enter the point code that will be assigned to the SS7 stack being created. For more information on configuring the SS7 object pane, refer to the SS7 Stack topic.

  2. Configure the SS7 Link Set under the stack created by right clicking on the stack and select New SS7 Link Set. Enter the point code of the adjacent SS7 stack that this stack will be communicating with. Refer to the SS7 Link Set topic for more information on configuring the individual fields.

  3. Configure an SS7 Link by right clicking on the SS7 Link Set just created and select New SS7 Link. Select Node and Span/Channel that the link will reside on. See screen capture below. For more information refer to the SS7 Link topic.

SC_SS7_Redundant_Config_Link.png

  1. Right click on the SS7 Link Set created and select New SS7 Route. Refer to the SS7 Route topic for information on configuring the individual fields.

Configure an ISUP Group with SS7 CIC's

The next step is to create channel groups along with CIC's associated with those channel groups.

  1. Right click on the IMG EMS object and select New Routing Configuration. There is no configuration completed in this object. Refer to the Routing Configuration topic for more information on this object.
  2. Right click on Routing Configuration object and select New Channel Groups. The Channel Group main object will get created. Under this object, multiple channel groups can be created. Refer to the Channel Groups topic for more information on this object.
  3. Right click on Channel Groups object and select New Channel Group. Enter a name for this Channel Group and verify SS7 signaling is displayed in the "Signaling Type" field. For more information on configuring this object, refer to the Channel Group topic.
  4. Right click on the Channel Group just created and select New ISUP Group. An ISUP Group Pane will get created. In the ISUP Group Pane is an OPC-DPC field. This field has a drop down menu that will display all the SS7 stacks created. Select one of the SS7 Stack from the SS7 server node created earlier. See screen capture below displaying the OPC-DPC field.

SC_SS7_Redundant_Config_ISUPGrp.png

For more information on configuring this object, refer to one of the ISUP Group topics below.

ISUP Group - ANSI

ISUP Group - ITU

ISUP Group - JTISUP

  1. Create the CIC's that will be controlled by the stack selected in previous step by right clicking on the ISUP group created and select New Circuits. A Circuits Pane will appear as shown below.

SC_SS7_Redundant_Config_CICs.png

Refer to the CIC Group topic for more information on configuring this object.

 

At this point, a Primary and Secondary SS7 node has been created. An SS7 Stack, SS7 Link Set, SS7 Route and SS7 Link have been created on the Primary Node. The SS7 CICs have been created and are being controlled by the SS7 stack on the primary node. If at any time, a failure occurs on the Primary SS7 Node, the Secondary node will take over all SS7 processes. Below is screen capture of the Object tree after completing this feature.

SC_SS7_Redundant_Config_ObjTree.png