Related articles:

When the DSC - SP2000 is configured as an STP, you can add virtual PCs to register a point code at the NA that differs from the Local Point Code (LPC). You may need a virtual PC if you use an alias PC, for example Global Title Translation (GTT) MTP3-User Adaptation Layer (M3UA), and SCCP User Adaptation Layer (SUA). For information about GTT, M3UA, and (SUA), refer to the appropriate section in the SS7 Application Guide 2.

The following figure shows an example of a mated STP pair configuration with VNodes. In this example, STP NA A has a C-Link connecting it with its mate STP NA B in a mated pair configuration. An ASP on the IP network is configured to register with both STP NAs using the VNode 001.002.023. For the ASP to register with both STPs using the VPC 001.002.023, you must configure each STP to have a VNode 001.002.023. To the SS7 network, VNode 001.002.023 has a single appearance on the network, but load sharing of the ASP traffic destined for VPC 001.002.023 is now possible between the mated pair of STPs.


Note

When VNodes are created and configured on both STPs for an M3UA or SUA Application Server, it is recommended to create a member routeset on each STP to the VNode point code. The only route required in the routeset of a VNode point code is the C-link route to the mate STP. Direct VNode will always take priority to the routeset for traffic. The routeset will only be used if the vnode registration has gone down. For example, an ASP has dropped or gone Inactive making the Application Server unavailable for traffic.


You can have multiple VNodes configured in the NA. In the following figure, STP NA A has two VNodes: VNode 100.010.110 and VNode 001.002.023. An additional Application Server Process (ASP) cannot register with STP NA B using point code 100.010.110. STP NA B only has VNode 001.002.023.

Note

To follow M3UA and SUA terminology, for the rest of this section, a user application is referred to as an ASP.

Multiple VNodes Configured at the NA


  • No labels