Removing a Routing Key Containing an Application Server

This procedure is used remove a static key from the database using the dlt-appl-rtkey command. For more information about static and dynamic routing keys, see Understanding Routing for SS7IPGW and IPGWI Applications.

The dlt-appl-rtkey command uses these parameters.

:dpc/dpca/dpci/dpcn/dpca24 – The destination point code value that is used to filter incoming MSUs.

:opc/opca/opci/opcn/opcn24 - The originating point code value that is used to filter incoming MSUs. This parameter must not specify a cluster route. This parameter must not specify a cluster route. This parameter is only valid when the si parameter value is set to 4, 5, or 13. This parameter is required if si=4, 5, or 13 and type=full.

Note:

See the “Point Code Formats” section in Database Administration - SS7 User's Guide 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.

:si – The service indicator value that is used to filter incoming MSUs. The range of values for the service indicator parameter (si) can be a numerical value from 0 to 15, or for selected service indicator values, a text string can be used instead of numbers. Table 4-14 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-14 Service Indicator Text String Values

Service Indicator Value	Text String	Service Indicator Value	Text String
0	snm	4	tup
1	regtest	5	isup
2	spltst	13	qbicc
3	sccp

:ssn – The subsystem value that is used to filter incoming MSUs. The ssn parameter is only valid when the si parameter value is set to 3 or sccp.

:cics - The starting circuit identification code that is used to filter incoming MSUs. Specify with cice to delete routing keys with the circuit identification code or range of circuit identification codes. The cics parameter is only valid when the si parameter value is set to 4, 5, or 13. The cics is required if si=4, 5, or 13 and type=full.

:cice - The ending circuit identification code that is used to filter incoming MSUs. Specify with cics to delete routing keys with the circuit identification code or range of circuit identification codes. The cice parameter is only valid when the si parameter value is set to 4, 5, or 13. The cics is required if si=4, 5, or 13 and type=full.

:type - Identifies the type of routing key that is being deleted. One of three values, type = full/partial/default. If type is not explicitly specified, type = full is assumed.

:asname - Application server (AS) name.

:rcontext – The routing context parameter value assigned to the routing key.

The parameter combinations used by the dlt-appl-rtkey command are based on the type of routing key and the service indicator value in the routing key. The parameter combinations are shown in Table 4-15 .

Table 4-15 Routing Key Parameter Combinations for Removing Routing Keys

Full Routing Key SI=3 (SCCP) (See Notes 1, 3, and 4)	Partial Routing Key SI=3 (SCCP) (See Notes 1, 3, and 4)	Full Routing Key SI=4 (TUP), 5 (ISUP), 13 (QBICC) (See Notes 1, 3, and 4)	Partial Routing Key SI=4 (TUP), 5 (ISUP), 13 (QBICC) (See Notes 1, 3, and 4)	Full Routing Key Other SI Values (See Notes 1, 3, and 4)	Partial Routing Key Other SI Values (See Notes 1, 3, and 4)	Default Routing Key (See Notes 1, 3, and 4)
dpc	type=partial	dpc	type=partial	dpc	type=partial	type=default
si=3 (See Note 1)	dpc (See Note 2)	si=4, 5, 13 (See Note 1)	dpc (See Note 2)	si=value other than 3, 4, 5, 13 (See Note 1)	dpc (See Note 2)	asname
ssn	si=3 (See Notes 1 and 2)	opc	si=4, 5, 13 (See Notes 1 and 2)	type=full	si=value other than 3, 4, 5, 13 (See Notes 1 and 2)	rcontext (See Notes 3 and 4)
type=full	asname	cics	opc (See Note 2)	asname	asname
asname	rcontext (See Notes 3 and 4)	cice	asname	rcontext (See Notes 3 and 4)	rcontext (See Notes 3 and 4)
rcontext (See Notes 3 and 4)		type=full	rcontext (See Notes 3 and 4)
		asname
		rcontext (See Notes 3 and 4)
Notes: 1. The values for these parameters must be entered exactly as shown in the `rtrv-appl-rtkey` command output for the routing key being removed. However, text strings can be used in place of some numerical service indicator values. See Table 4-14 for a list of these text strings. 2. These parameters are optional for partial routing keys, but at least one these parameters must be specified with the `dlt-appl-rtkey` command. 3. If the routing key contains a numerical value in the `RCONTEXT` column in the `rtrv-appl-rtkey` output, the `dlt-appl-rtkey` command can be specified with only the `rcontext` parameter and value instead of the `dpc`, `si`, `ssn`, `opc`, `cics`, `cice`, or `type` parameters and values to remove the routing key. 4. If the routing key contains dashes in the `RCONTEXT` column in the `rtrv-appl-rtkey` output, the `dpc`, `si`, `ssn`, `opc`, `cics`, `cice`, or `type` parameters and values must be used with the `dlt-appl-rtkey` command to remove the routing key.

Canceling the RTRV-APPL-RTKEY Command

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

Press the F9 function key on the keyboard at the terminal where the rtrv-appl-rtkey command was entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-appl-rtkey command was entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-appl-rtkey commands were entered, from another terminal other that the terminal where the rtrv-appl-rtkey command was 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 routing key information in the database by entering the rtrv-appl-rtkey command.

The following is an example of the possible output.


rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  123-234-123   5  M3UA   as9              FULL
----------  123-234-123   5  M3UA   as9              FULL
1000        005-005-001   5  SUA    as10             FULL
2000        005-005-001   5  SUA    as10             FULL
----------  006-006-001   5  M3UA   as11             FULL
----------  006-006-001   5  M3UA   as11             FULL

RCONTEXT    DPCI         SI  ADPTR  ASNAME           TYPE
----------    2-100-7     6  M3UA   as4              FULL
100           3-137-6     6  SUA    as1              FULL
225           4-035-7     5  M3UA   as7              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-8     3  M3UA   as3              FULL
----------    6-006-8     5  M3UA   as5              FULL
----------    6-024-7     5  M3UA   as4              FULL
----------    6-024-7     5  M3UA   as4              FULL
300           7-008-7     6  SUA    as6              FULL

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  ***********  **  M3UA   as123            DEFAULT

STATIC Route Key table is (15 of 2000) 1% full
STATIC Route Key Socket Association table is (15 of 32000) 1% full

If a routing context value is not assigned to the the routing key being removed in this procedure, continue the procedure with 3.

Display the specific routing key information for the routing key being removed from the database by entering the rtrv-appl-rtkey command with the display=all parameter and the RCONTEXT values shown in the rtrv-appl-rtkey output in 1 for the routing key being removed.

For this example, enter this command.

rtrv-appl-rtkey:rcontext=225

This is an example of the possible output.


rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   2-007-3      2000       3000

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as7    
                                         
    ANAMES
    assoc15

STATIC Route Key table is (15 of 2000) 1% full
STATIC Route Key Socket Association table is (15 of 32000) 1% full

After this step is performed, continue the procedure with 4.

Display the specific routing key information for the routing key being removed from the database by entering the rtrv-appl-rtkey command with the display=all parameter and the DPC, SI, andTYPE values shown in the rtrv-appl-rtkey output in 1 for the routing key being removed. For this example, enter this command.

rtrv-appl-rtkey:dpci=6-006-6:si=3:display=all:type=full

This is an example of the possible output.


rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
----------   6-006-6      3 170 -----------    ---------- ----------

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as2    
                                         
    ANAMES
    assoc1

STATIC Route Key table is (15 of 2000) 1% full
STATIC Route Key Socket Association table is (15 of 32000) 1% full

Display the associations assigned to the routing key by entering the rtrv-assoc parameter with the association name shown in either 2 or 3. For this example, enter these commands.

rtrv-assoc:aname=assoc1

This is an example of possible output.


rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as2

IP Appl Sock table is (8 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

rtrv-assoc:aname=assoc15

This is an example of possible output.


rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc15
      LOC      1205          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw115.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    2000          RPORT       2000
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as7

IP Appl Sock table is (8 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

Repeat this step for all the associations shown in 2 or 3.

Change the open parameter value of the association to no by using the chg-assoc command.
Note:
If theopen parameter value of all the associations shown in4isno, continue the procedure with6.

For example, enter these commands.

chg-assoc:aname=assoc1:open=no

chg-assoc:aname=assoc15:open=no

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD
```
Caution:
TheIP connections using the associations specified in this step will not be able to carry any traffic when theopen parameter is changed tono.

Repeat this step for all the associations shown in 4 that contain the open=yes parameter value.
Remove the routing key information from the database by entering the dlt-appl-rtkey command.
The parameters required for the dlt-appl-rtkey command are determined by the type of routing key being added and the service indicator value in the routing key. See Table 4-15 for the parameter combinations that can be used for the type of routing key being added to the database. For example, enter these commands.
dlt-appl-rtkey:dpci=6-006-6:si=3:ssn=170:asname=as2

dlt-appl-rtkey:rcontext=225

When each of these commands have successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
DLT-APPL-RTKEY: MASP A - COMPLTD
```
Verify the changes by entering the rtrv-appl-rtkey command with the routing key parameters specified in 6 (dpc, si, opc, cics, cice, ssn, asname, and type, and loc, as applicable). For this example, enter these commands.
rtrv-appl-rtkey:dpci=6-006-6:si=3:ssn=170:asname=as2

The following is an example of the possible output.
```
rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0

No matching entries found

STATIC Route Key table is (12 of 2000) 1% full
STATIC Route Key Socket Association table is (6 of 32000) 1% full
```
rtrv-appl-rtkey:rcontext=225

The following is an example of the possible output.
```
rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0

No matching entries found

STATIC Route Key table is (12 of 2000) 1% full
STATIC Route Key Socket Association table is (6 of 32000) 1% full
```
Note:
If5was not performed, continue the procedure with9.
Change the open parameter value of the associations that were changed in 5 to yes by using the chg-assoc command.
For example, enter these commands.
chg-assoc:aname=assoc1:open=yes

chg-assoc:aname=assoc15:open=yes

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD
```
Repeat this step for all the associations that were changed in 9.

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 4-33 Removing a Routing Key Containing an Application Server

Sheet 1 of 2

Sheet 2 of 2