Adding a Route Containing an IPGWx Linkset

This procedure is used to add a route to the database containing an IPGWx linkset using the ent-rte command. Routes that do not contain IPGWx linksets are configured in these procedures.

The ent-rte command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination 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 and for a definition of the different formats that can be used for ITU national point codes.

: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 Destination Point Code. The DPC of the route can be a private point code, but does not have to be.
Linkset – see the “Configuring an IPGWx Linkset” procedure in Database Administration - IP7 User's Guide.
Link – see the “Adding an IPGWx Signaling Link” procedure in Database Administration - IP7 User's Guide.

The linkset assigned to this route must have an adjacent point code (APC) in the SS7 domain and must contain the ipgwapc=yes parameter value. The domain of the DPC is shown in the DMN field in the output of the rtrv-dstn command. The ipgwapc parameter value is shown in the output of the rtrv-ls:lsn=<linkset name> command.

The DPC of the route must be the APC of the linkset, or the SAPC assigned to the linkset. The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, a routes containing ANSI DPC must have a linkset with an ANSI APC; a route containing an ITU-I DPC must have a linkset with an ITU-I APC; a route containing a 14-bit ITU-N DPC must have a linkset with a 14-bit ITU-N APC; a route containing a 24-bit ITU-N DPC must have a linkset with a 24-bit ITU-N APC. The DPC of the route must be defined as a true point code in the rtrv-dstn output. Cluster point codes, network routing point codes, 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. The DPC of the route cannot be a proxy point code. A proxy point code or secondary point code cannot be assigned to the DPC of the route. A secondary point code cannot be assigned to the linkset.

For a linkset with an ITU APC, if that linkset has an SAPC assigned to it, the SAPC of that linkset can be specified as the DPC of the route. The format of the SAPC can be different from the APC of the linkset. For example, an IPGWx linkset has an ITU-I APC and an ITU-N SAPC is assigned to the linkset. The DPC of the route can be either the ITU-I APC of the linkset or the ITU-N SAPC assigned to the linkset.

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.

The route containing an IPGWx linkset can contain only one linkset.

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 member of a cluster point code, and the nested cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no, then the route to the DPC must be the same as the route to the cluster point code. If the nested cluster allowed indicator is set to yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code. For more information, see the Nested Cluster Routing section.

For routes containing 14-bit ITU National DPCs with group codes, if the linkset assigned to the route has the MULTGC value set to yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the MULTGC value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route.

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 Commands User's Guide.

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
 p-004-004-004 ----------    11-12-10-3    ---------- --    -----------
                                               RTX:No  CLLI=-----------
   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 destination point code of the route being added in this procedure is not shown in the rtrv-rte output, perform the Adding a Destination Point Code procedure and add the destination point code of the route to the destination point code table. This point code can be a private point code, but does not have to be a private point code. The DPC of the route cannot be a proxy point code. A proxy point code or secondary point code cannot be assigned to the DPC of the route. After the point code is added, continue the procedure with 3.

If the point code that will be assigned to the route is shown in the rtrv-rte output, but has a route assigned to it, that point code cannot be used as the DPC of the route being added in this procedure. Choose another point code and repeat this step.

If the RC, LSN, and APC columns in the rtrv-rte output contain dashes for the given point code, a route is not assigned to the point code.

If the point code that will be assigned to the route is shown in the rtrv-rte output, but does not have a route assigned to it, continue the procedure with 2.

Note:

If cluster point codes are not shown in 1, or if the DPC of the route being added is not a member of the cluster point code, continue the procedure with 4.

Enter the rtrv-dstn command with the DPC of the route. For this example, enter this command.
rtrv-dstn:dpca=004-004-004

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
   004-004-004   ----------- no  --- ----------      --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   010-010-010  ---- no      none   off   none     no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (2 of 10) 20% full
```
The DPC of the route cannot be a proxy point code. A proxy point code or secondary point code cannot be assigned to the DPC of the route. If any of these conditions are shown in the rtrv-dstn output, either choose another point code shown in 1 and repeat this procedure, or perform the Adding a Destination Point Code procedure and add the destination point code of the route to the destination point code table. This point code can be a private point code, but does not have to be a private point code. The DPC of the route cannot be a proxy point code. A proxy point code or secondary point code cannot be assigned to the DPC of the route.

Note:
If cluster point codes are not shown in 1, or if the DPC of the route being added is not a member of the cluster point code, continue the procedure with 4.
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
```
If the ncai parameter value of the cluster point code is no, and you wish to change the ncai parameter value to yes, perform the Changing the Attributes of a Cluster Point Code procedure. If the ncai parameter value of the cluster point code is no, and you do not wish to change the ncai parameter value to yes, add a new DPC for the route by performing the Adding a Destination Point Code procedure. The DPC of the route cannot be a proxy point code. A proxy point code or secondary point code cannot be assigned to the DPC of the route.

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
lsn4        p-004-004-004   none 1   1   no  A   6    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
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 (11 of 1024) 1% full.

If the point code chosen in 1 is not shown as the APC of a linkset, perform the “Configuring an IPGWx Linkset” procedure in Database Administration - IP7 User's Guide and add the IPGWx linkset to the database. After the IPGWx linkset has been added, continue the procedure with 7.

If the point code chosen in 1 is shown as the APC of a linkset, continue the procedure with 5.

Display each linkset being assigned to the route to verify the multgc and ipgwapc parameter values with the rtrv-ls command, specifying the name of the linkset that will be assigned to the route.
If the multgc linkset parameter value is yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the multgc value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route. The multgc value is shown in the MULTGC field of the rtrv-ls output.

If the ipgwapc parameter value for the linkset is yes, continue the procedure with 6.

If the ipgwapc parameter value for the linkset is no, the linkset and point code cannot be assigned to the route. Either select another point code and repeat this procedure from 1, or add the desired linkset by perform the “Configuring an IPGWx Linkset” procedure in the Database Administration Manual - IP⁷ Secure Gateway and add the IPGWx linkset to the database. After the IPGWx linkset has been added, continue the procedure with 7.

For this example, enter the following commands.

rtrv-ls:lsn=lsn4

This is an example of the possible output.
```
rlghncxa03w 06-10-11 11:06:27 GMT EAGLE5 36.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsn4        p-004-004-004   none 1   1   no  A   6    off off off no    off

           CLLI         TFATCABMLQ MTPRSE ASL8
           -----------  3          no     no

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 100   100    % 80      % CdPA

           LOC  PORT SLC TYPE
           1107 A     0  SS7IPGW
           1205 A     1  SS7IPGW
           1305 A     2  SS7IPGW
           1303 A     3  SS7IPGW
           1307 A     4  SS7IPGW
           1311 A     5  SS7IPGW


Link set table is (16 of 1024) 1% full.
```
Only one linkset can be assigned to a route containing an IPGWx linkset.
Verify that the linkset that will be assigned to the route is not assigned to any existing routes. Enter the rtrv-rte command with the name of the linkset that you wish to assign to the route. For this example, enter this command.

rtrv-rte:lsn=lsn4

If the linkset is not assigned to a route, no entries are displayed in the rtrv-rte output as shown in the following output example.
```
rlghncxa03w 06-10-11 11:06:27 GMT EAGLE5 36.0.0
LSN           DPC           RC
```
If the linkset is assigned to a route, add the desired linkset by perform the “Configuring an IPGWx Linkset” procedure in Database Administration - IP7 User's Guide and add the IPGWx linkset to the database. After the IPGWx linkset has been added, continue the procedure with 7.

If the linkset is not assigned to a route, continue the procedure with 7.
Add the route using the ent-rte command with the IPGWx linkset.
These are the rules that apply to adding a route.
- The force=yes parameter must be specified if the linkset being assigned to the route has no signaling links assigned to it. Otherwise, each linkset must have at least one signaling link assigned to it.
- A route can contain only one linkset.
- If the DPC of the route is a member of a cluster point code, and the nested cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no, then the route to the DPC must be the same as the route to the cluster point code. If the nested cluster allowed indicator is set to yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code.
- For routes containing 14-bit ITU National DPCs with group codes, if the linkset assigned to the route has the MULTGC value set to yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the MULTGC value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route.
- The DPC of the route must be the APC of the linkset, or the SAPC assigned to the linkset. The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, a route containing an ANSI DPC must have a linkset with an ANSI APC; a route containing an ITU-I DPC must have a linkset with an ITU-I APC; a route containing a 14-bit ITU-N DPC must have a linkset with a 14-bit ITU-N APC; a route containing a 24-bit ITU-N DPC must have a linkset with a 24-bit ITU-N APC. The DPC of the route must be defined as a true point code in the rtrv-dstn output. Cluster point codes, network routing point codes, alias point codes, secondary point codes, and proxy 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. For a linkset with an ITU APC, if that linkset has an SAPC assigned to it, the DPC of the route can be either the APC of the linkset or the SAPC assigned to the linkset. The format of the SAPC can be different from the APC of the linkset. For a linkset with an ITU APC, if that linkset does not have an SAPC assigned to it, the DPC of the route must be the APC of the linkset.
- Private point codes can be specified as the DPC of a route only if the linkset assigned to the route is an IPGWx linkset (a linkset that has the ipgwapc=yes parameter assigned to it).
ent-rte:dpca=p-004-004-004:lsn=lsn4: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 this command.

rtrv-rte:dpca=p-004-004-004

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
  DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
p-004-004-004 ----------    11-12-10-3    lsn4       10  p-004-004-004
                                              RTX:No  CLLI=-----------

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-20 Adding a Route Containing an IPGWx Linkset

Sheet 1 of 4

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4