Adding a Route Containing a Cluster Point Code

This procedure is used to add a route to the database containing a cluster point code as the DPC of the route using the ent-rte command. Routes that do not contain a cluster point code as the DPC of the route are configured in these procedures:

The ent-rte command uses these parameters.

:dpc/dpca – The destination point code (cluster point code) of the node that the traffic is being sent to.

Note:

See Point Code Formats for a definition of the point code types that are used on the EAGLE 5 ISS.

:lsn – The name of the linkset that will carry the traffic to the node specified by the destination point code.

:rc – The relative cost (priority) for this route.

:force – This parameter allows a route to be added to the database even if the linkset to be assigned to the route does not have any signaling links in it.

These items must be configured in the database before a route can be added:

Destination point code (DPC) – see Adding a Cluster Point Code
Linkset – see Adding an SS7 Linkset
Link – see Adding an SS7 Signaling Link

The linkset assigned to this route must have an adjacent point code (APC) in the SS7 domain. The domain of the DPC is shown in the DMN field in the output of the rtrv-dstn command.

The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, routes containing ANSI DPCs must have linksets with ANSI APCs; routes containing ITU-I DPCs must have linksets with ITU-I APCs; routes containing 14-bit ITU-N DPCs must have linksets with 14-bit ITU-N APCs; routes containing 24-bit ITU-N DPCs must have linksets with 24-bit ITU-N APCs. The DPC of the route must be defined as a true point code in the rtrv-dstn output. Alias point codes and secondary point codes cannot be used. True point codes are shown in the output of the rtrv-dstn command in the DPCA, DPCI, DPCN, or DPCN24 fields. Private point codes cannot be used as the DPC of a route in this procedure. Routes that have private point codes as the DPC of a route can contain only IPGWx linksets. Perform the Adding a Route Containing an IPGWx Linkset procedure to add routes containing IPGWx linksets.

The DPC of the route is the destination point code to be reached by the route and is shown in the output of the rtrv-rte command in the DPCA, DPCI, DPCN, or DPCN24 fields.

The APCA, APCI, APCN, and APCN24 fields in the output of the rtrv-rte command show the point code of the node that is directly adjacent to the node in the route.

A linkset can only be entered once as a route for each DPC.

A maximum of six routes can be defined for each DPC.

If the 6-Way Loadsharing on Routesets feature is enabled and turned on, a maximum of six routes in the routeset can be assigned the same relative cost value. It is recommended that the routeset be provisioned with a group of four routes that have the same relative cost value and another group of two routes that have the same relative cost value. Three or five routes in the routeset that have the same relative cost value can be provisioned, but the odd number makes it more difficult to distribute the route traffic evenly. Six routes in the routeset that have the same relative cost value can be provisioned, but this does not allow for any backup routes and also offers the worst chance for congestion and queuing issues during network failures. If the 6-Way Loadsharing on Routesets feature is not enabled or not turned on, a maximum of two linksets can be assigned the same relative cost value. The relative cost value of the route is defined by the rc parameter of the ent-rte command and is shown in the RC field in the output of the rtrv-rte command.

The force=yes parameter must be specified if the specified linkset has no signaling links assigned to it. Otherwise, each linkset must have at least one signaling link assigned to it.

If the DPC of the route is a cluster point code, only linksets whose linkset type is either B, C, or D can be assigned to the route. The linkset type is shown in the LST field of the rtrv-ls command output. If the linkset type of the desired linkset is either A, E, or PRX, one of three actions must be taken.

Choose another linkset with the linkset type B, C, or D.
Change the linkset type of an existing linkset – perform the Changing an SS7 Linkset procedure.
Add a new linkset to the database with the necessary signaling links and the linkset type B, C, or D.
1. Perform the Adding an SS7 Linkset procedure to add the linkset.
2. If the necessary signaling links are not in the database, perform the Adding an SS7 Signaling Link procedure to add the signaling links to the database.

Canceling the RTRV-LS, RTRV-DSTN, and RTRV-RTE Commands

Because the rtrv-ls, rtrv-dstn, and rtrv-rte commands used in this procedure can output information for a long period of time, the rtrv-ls, rtrv-dstn, and rtrv-rte commands can be canceled and the output to the terminal stopped. There are three ways that the rtrv-ls, rtrv-dstn, and rtrv-rte commands can be canceled.

Press the F9 function key on the keyboard at the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered, from another terminal other that the terminal where the rtrv-ls, rtrv-dstn, or rtrv-rte commands were entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to the Commands Manual.

Display the current route configuration using the rtrv-rte command.

This is an example of the possible output.

rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   140-012-004    1-111-1    10-13-12-1    ls000001   10    240-012-002
                                           ls000002   10    240-012-002
                                           ls000003   20    240-012-002
                                           ls000004   30    240-012-002
                                           ls000005   40    240-012-002
                                           ls000006   50    240-012-002
                                               RTX:No  CLLI=dp1
   140-012-005 1-111-2 10-13-12-2          ls000001   10    240-012-002
                                           ls000002   10    240-012-002
                                           ls000003   20    240-012-002
                                           ls000004   30    240-012-002
                                           ls000005   40    240-012-002
                                           ls000006   50    240-012-002
                                               RTX:No  CLLI=dp2
   DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
   2-234-5    11-13-3-3       240-111-111  ls100001   10    1-234-5
                                           ls100002   10    1-234-6
                                           ls100003   20    1-234-7
                                           ls100004   30    1-234-1
                                           ls100005   40    1-234-2
                                           ls100006   50    1-234-3
                                               RTX:No  CLLI=idp1
   DPCN             ALIASA         ALIASI  LSN        RC    APC
   12-12-13-3       011-222-111    0-001-1 ls200001   10    10-13-9-3
                                           ls200002   10    10-13-10-0
                                           ls200003   20    10-13-10-1
                                           ls200004   30    10-13-10-2
                                           ls200005   40    10-13-10-3
                                           ls200006   50    10-13-11-0
                                               RTX:No  CLLI=ndp1
   DPCN24           ALIASA         ALIASI  LSN        RC    APC

If the cluster point code of the route being added in this procedure is not shown in the rtrv-rte output, perform the Adding a Cluster Point Code procedure and add the cluster point code. Continue the procedure with 3.

If the cluster point code of the route being added in this procedure is shown in the rtrv-rte output, continue the procedure with 2.

Display the ncai parameter value assigned to the cluster point code using the rtrv-dstn command and specifying the cluster point code. If the ncai parameter value is no, then the route to the DPC must be the same as the route to the cluster point code. If the ncai parameter value is yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code. The ncai value is shown in the NCAI field of the rtrv-dstn output. For this example, enter this command.
rtrv-dstn:dpca=111-011-*

This is an example of the possible output.
```
rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN

   111-011-*     rlghncbb000 yes yes ----------      --------------   SS7

   SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  yes          none   off   none     no     no    none

Destination table is (12 of 2000) 1% full
Alias table is (18 of 8000) 1% full
```

Verify that the required linkset for the route is in the database by displaying the linksets in the database with the rtrv-ls command.

This is an example of the possible output.

rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
e1e2          001-207-000   none 1   1   no  B   6    off off off no    off
ls1305        000-005-000   none 1   1   no  A   1    off off off no    off
ls1307        000-007-000   none 1   1   no  A   1    off off off no    off
lsn7          002-002-002   none 1   1   no  C   8    off off off no    off
e1m1s1        001-001-001   none 1   1   no  A   7    off off off no    off
e1m1s2        001-001-002   none 1   1   no  A   7    off off off no    off

                                 L3T SLT              GWS GWS GWS
LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
e1e2i         1-207-0       none 1   1   no  B   4    off off off ---   on
ls1315        0-015-0       none 1   1   no  A   1    off off off ---   off
ls1317        0-017-0       none 1   1   no  A   1    off off off ---   on
ls7890        7-089-0       none 1   2   no  B   1    off off off ---   off
e1m2s1        1-011-1       none 1   1   no  A   7    off off off ---   off
e1m2s2        1-011-2       none 1   1   no  A   7    off off off ---   off

Link set table is (12 of 1024) 1% full.

The route containing a cluster point code can have only linksets with the linkset types B, C, or D assigned to it. If the required linkset is not in the database, perform the Adding an SS7 Linkset procedure to add the linkset to the database with the ipgwapc=no parameter value and with the linkset types B, C, or D. The APC of the linkset cannot be a private point code. Continue the procedure with 5.

If the linkset that will be added to the route is shown in the rtrv-ls output and is a B-, C-, or D-type linkset, continue the procedure with 4.

Display each linkset being assigned to the route to verify the ipgwapc parameter values with the rtrv-ls command, specifying the name of the linkset that will be assigned to the route.

The ipgwapc linkset parameter value is yes, the DPC of the route cannot be a cluster point code. The ipgwapc value is shown in the IPGWAPC field of the rtrv-ls output.

If the linkset displayed in this step contains the ipgwapc=yes parameter, repeat this step with another linkset shown in 3. If all the linksets have been displayed, and the ipgwapc value for all the linksets is yes, add the desired linkset by performing the Adding an SS7 Linkset procedure with the ipgwapc=no parameter value and with the linkset types B, C, or D. The APC of the linkset cannot be a private point code.

For this example, enter the following command.

rtrv-ls:lsn=lsn7

This is an example of the possible output.

rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsn7          002-002-002   none 1   1   no  C   8    off off off no    off

           CLLI         TFATCABMLQ MTPRSE ASL8
           -----------  4          ---    no

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           no      ---------- ---   ---      ---       CdPA

                                  L2T               PCR  PCR
           LOC  PORT SLC TYPE     SET  BPS    ECM   N1   N2
           1211 A     0  LIMDS0   1    56000  BASIC ---  -----
           1211 B     1  LIMDS0   1    56000  BASIC ---  -----
           1211 A1    2  LIMDS0   1    56000  BASIC ---  -----
           1211 A2    3  LIMDS0   1    56000  BASIC ---  -----
           1211 B2    4  LIMDS0   1    56000  BASIC ---  -----
           1211 B1    5  LIMDS0   1    56000  BASIC ---  -----
           1211 B3    6  LIMDS0   1    56000  BASIC ---  -----
           1211 A3    7  LIMDS0   1    56000  BASIC ---  -----

Link set table is (12 of 1024) 1% full.

For a routeset to have more than two routes with the same relative cost value, the 6-Way Loadsharing on Routesets feature must be enabled and turned on.
To verify the status of the 6-Way Loadsharing on Routesets feature, enter this command.

rtrv-ctrl-feat:partnum=893019801

The following is an example of the possible output.
```
rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
6-Way LS on Routesets     893019801  on      ----

The following features have been temporarily enabled:

Feature Name              Partnum   Status  Quantity     Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.
```
If the 6-Way Loadsharing on Routesets feature is not enabled or not turned on, perform Activating the 6-Way Loadsharing on Routesets Feature to enable and turn on the 6-Way Loadsharing on Routesets feature.

After the 6-Way Loadsharing on Routesets feature has been enabled and turned on, or if the rtrv-ctrl-feat output shows that the 6-Way Loadsharing on Routesets feature is enabled and turned on, continue this procedure with 6.
Add the route using the ent-rte command specifying the cluster point code as the DPC of the route.
For this example, enter this command.

ent-rte:dpca=111-011-*:lsn=lsn7:rc=10

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
ENT-RTE: MASP A - COMPLTD
```

Verify the changes using the rtrv-rte command, specifying the destination point code of the route.

For this example, enter these commands.

rtrv-rte:dpca=111-011-*

This is an example of the possible output.

rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0

   DPCA             ALIASI           ALIASN/N24    RTX   CLLI
                                  LSN           RC    APCA
111-011-*     --------------   --------------   No    -----------
                                  lsn7          10    002-002-002

Back up the new changes using the chg-db:action=backup:dest=fixed command.

These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.

BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-19 Adding a Route Containing a Cluster Point Code

Sheet 1 of 3

Sheet 2 of 3

Sheet 3 of 3