Related articles:


After configuring the attributes for the links, you can establish the routesets and routes to the necessary destinations in the network. For each routeset, a set of routes must be specified, each corresponding to an existing linkset. A routeset is a set of distinct signaling routes from a node to the same destination point. Each route corresponds to an existing linkset which connects a node to a destination point code through an adjacent node. Routes in a routeset are assigned a relative cost that is used to determine which routes are selected for use within a routeset. The route with the lowest cost, if AVAILABLE, is used.

Note

Routesets should be established for all destinations that a DSC - SP2000 Platform has to access. To facilitate change-over procedures, the adjacent node PCs must also be established as routesets, even if they are not used as final destinations.

The SP2000 Platform supports up to 4000 routesets and up to 8000 routes per platform. Each routeset can support up to eight routes. Within a routeset, no more than two routes can have the same relative cost.

The DSC Platform supports up to 4,000 routesets and up to 24,000 routes per platform. Each routeset can support up to eight routes. Within a routeset, no more than two routes can have the same relative cost.

Note

For DSC special ITU configurations (change Loadshare mode to Enhanced SLS), up to four routes of the same cost may exist within a routeset.

Caution

The distribution of the routes in the routesets can be as required, provided that the maximum number of routes in each routeset does not exceed eight and the maximum number of routesets in each DSC Platform does not exceed 4,000.

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.

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 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.