Related articles:

For detailed information about the appropriate description of the various supported CPUs and VMs, refer to Terminology.

When a node is configured, linksets to all adjacent point codes that the node is directly connected to must be defined.

A linkset is the set of all signaling links connecting a given node to the same adjacent node on the SS7 network. There can be only one linkset between two adjacent signaling points. You must configure linksets before configuring any signaling links.

Most DSC - SP2000 Platform default settings for linksets and links do not require changing and should work for most configurations. However, all linksets and link defaults adjust according to the SS7 Variant you set for the node. Therefore, if you have linksets configured for an existing node and must change the node SS7 Variant, you must remove all linksets at the node and remove any routes that reference these linksets before you can change the node SS7 Variant.
 

Caution

Before you can remove a linkset, you must

  • deactivate all links within this linkset
  • delete all links within this linkset
  • deactivate this linkset

Proceed with caution when performing these actions, because on a live system they can be service affecting.


Therefore, it is recommended that you define the SS7 Variant for your system before configuring linksets and links (refer to Configuring Network Appearances).

The DSC - SP2000 Platform supports MTP3B messages. The maximum number of bytes allowed, including routing label and SIO, for an MSU in this NA ranges from 273 to 4092 bytes. This feature is disabled by default. MTP3B message are forwarded to destinations that also support this MSU length. If a particular destination is not supported, then applicable alarms are raised (displayed in the Alarm Dashboard) and SNMP traps are sent (refer to Configuring MTP3B Support).

The DSC - SP2000 Platform allows the rebalance of high-speed links. However, it is recommended that this feature is only used for link management (refer to DRE Loading Manager).

If your system is licensed for Integrated Monitoring Feed (IMF), you may enable or disable this feature when configuring a linkset (refer to Configuring Linksets).

The Process Event feature that appears in the UI, but is not described in this guide, provides an alarm type which ensures that the applications in all slots function as expected. With this feature, each application defines its own concept of functioning as expected, which means that the configuration/database files are synchronized and loaded, inter-peer connections are correctly established, and the peer applications are ready to process traffic.

Note

On the Web UI, the Rx MSU Count and Tx MSU Count provide an almost real-time view of traffic. The MSUs are counted at the routing CPU, which are then averaged based on a per second count at the end of a five-second interval and rounded up. 

This feature is enabled by default and is auto-refreshed every five seconds, except where indicated.

If the application and its peer does not function as expected, an alarm is raised that is visible on the system's alarm panel. For more information about alarms, refer to the appropriate section in the DSC Alarms Guide.

In accordance with GR-82-Core, Signaling Transfer Point (STP) Generic Requirements (A Module of FR-CCS-18), Issue 10, December 2006, the DSC - SP2000 Platform supports Memory Space Accounting (MSA). For more information about how this feature applies to Message Transfer Part Level 3 (MTP3), refer to the appropriate section in the DSC - SP2000 Platform Manager User Guide.

 

 

  • No labels