In this section:
Overview
This section provides you with information about working with routesets, including creation, configuration, activation/deactivation, and deletion.
Routesets are used in processing traffic. Creating, configuring, activating/deactivating, and deleting routesets have an immediate impact on traffic handling and should be performed with caution on a live system.
The routesets to adjacent destinations (with RoutesetDPC equal to some LinksetAPC) are special and are required for proper execution of MTP Management procedures. Such routesets to adjacent destinations should be created immediately after the Linkset is created, populated with correct routes, activated, and then should be left as configured while the Linkset is in use (refer to Configuring Linksets and Links). In particular, you cannot simulate unavailability of an adjacent point code by deactivating the routeset to that destination or deleting routes.
Immediately after creation, a routeset is in the INACTIVE state. Routes may be added and then the routeset may be activated. At this point, the routeset is in a normal operating mode, route traffic, and react to SS7 network events according to MTP3 SS7 standards. The proper sequence of events for creating a routeset is as follows:
- Create the routeset (see Creating a Routeset)
- Configure routeset attributes (optional; see Configuring a Routeset)
- Create routes (refer to Configuring Routes)
- Activate the routeset (Activating and Deactivating a Routeset)
Routeset activation and deactivation is intended as a short term state used only during the creation or deletion of a routeset. Deactivating a routeset should not be performed on a destination that is in use.
Deactivating a routeset does not produce the same effect as the destination becoming inaccessible. If you want to force a non-adjacent destination to be permanently inaccessible, activate a routeset to that destination, then delete all routes within the routeset. To make the destination accessible again, provision new routes. Routesets to adjacent destinations are special, and, therefore, you cannot simulate unavailability of an adjacent point code by deactivating the routeset to that destination or deleting routes.
Do not add, modify or delete routes in an Inactive (deactivated) routeset. After a routeset has been created, configured and activated, changes in that routeset will only take effect when performed while the routeset is in an Active state. A routeset should only be deactivated when the intent is to delete that routeset.
If you deactivate a routeset, this routeset’s destination state (see To configure a routeset details) is set to MANUALLY BLOCKED and the routeset state is set to INACTIVE whether the destination state is accessible or inaccessible.
Creating a Routeset
The following procedure provides you with instructions to create a routeset.
To create a routeset
Configuring a Routeset
The following procedure provides you with instructions to configure a routeset.
To configure the routeset details
Activating and Deactivating a Routeset
Make sure that you review the Overview section on this page before executing the procedures in this section.
If you deactivate a routeset, this routeset’s destination state (see Configuring a Routeset) is set to MANUALLY BLOCKED and the routeset state is set to INACTIVE whether the destination state is accessible or inaccessible.
Deactivating a routeset can affect the routing of traffic.
To activate or deactivate a routeset
Deleting a Routeset
Make sure that you review the Overview section on this page before executing the procedures in this section.
To prevent the accidental deletion of a routeset, a routeset must be deactivated before it is deleted. The accepted sequence of operations to delete a routeset is as follows:
- Deactivate the routeset (see Activating and Deactivating a Routeset)
- Delete all routes (refer to Deleting a Route)
- Delete the routeset (see Delete a routeset)