Adding a Routing Key Containing an Application Server

This procedure is used to add a routing key containing an application server to the database using the ent-appl-rtkey command.

A routing key defines a filter that checks the specified values in an incoming SS7 MSU to determine which, if any, association receives the MSU. For more information about static routing keys, see Understanding Routing for SS7IPGW and IPGWI Applications.

The ent-appl-rtkey command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code value that is used to filter incoming MSUs. This parameter must not specify a cluster route. The destination point code of the routing key cannot be the APC of an IPGWx linkset or the SAPC assigned to an IPGWx linkset.

: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 is valid only 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-12 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-12 Service Indicator Text String Values

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

: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. When specified with cice, cics identifies the start of the range of circuit identification codes. The cics parameter is valid only 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. When specified with cics, cice identifies the end of the range of circuit identification codes. The cice parameter is valid only when the si parameter value is set to 4, 5, or 13. The cice is required if si=4, 5, or 13 and type=full.

:type – The routing key type – Identifies the type of routing key that is being entered and used to route message signaling units (MSUs). One of three values, full/partial/default, can be specified for the type parameter (see Table 4-13). If type is not explicitly specified, type=full is assumed.

:asname – Application server (AS) name.

:rcontext – The routing context parameter, which has two functions:

Provides an index of the application server traffic that the sending application server is configured or registered to receive.
Identifies the SS7 network context for the message. The routing context parameter implicitly defines the SS7 point code format used, the SS7 network indicator value, and the SCCP protocol type/variant/version used.

Application server names are shown in the rtrv-as output.

Only one application server can be assigned to a routing key. There is a maximum of 2500 routing keys allowed per EAGLE. The application server names in each routing key must be unique.

The number of static routing keys is limited by the srkq parameter that was specified on the chg-sg-opts command.

Routing keys are associated only with the ss7ipgw or ipgwi application.

Group codes are required for 14-bit ITU-N point codes (DPCN/OPCN) when the Duplicate Point Code feature is enabled.

The starting circuit identification code must be less than or equal to the ending circuit identification code.

The ISUP routing over IP feature must be on in order to enter a routing key with these parameters: dpc, si, opc, cics, and cice. The IPISUP field in the rtrv-feat command output shows whether or not this feature is on.

The parameter combinations used by the ent-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-13.

Table 4-13 Routing Key Parameter Combinations for Adding a Routing Key Containing an Application Server

Full Routing Key - SI = 3 (SCCP)	Partial Routing Key - SI = 3 (SCCP)	Full Routing Key - SI=4 (TUP), 5 (ISUP), 13 (QBICC)	Partial Routing Key - SI=4 (TUP), 5 (ISUP), 13 (QBICC)	Full Routing Key - Other SI Values	Partial Routing Key - Other SI Values	Default Routing Key
dpc (See Notes 1, 2, and 11)	type=partial	dpc (See Notes 1 and 2)	type=partial	dpc (See Notes 1 and 2)	type=partial	type=default
si=3 (See Notes 4 and 11)	dpc (See Notes 1, 2, and 3)	si=4, 5, 13 (See Note 4)	dpc (See Notes 1, 2, and 3)	si=value other than 3, 4, 5, 13 (See Note 4)	dpc (See Notes 1, 2, and 3)	asname (See Note 10)
ssn (See Note 11)	si=3 (See Notes 3 and 4)	opc (See Notes 1 and 2)	si=4, 5, 13 (See Notes 3, 4, and 10)	type=full	si=value other than 3, 4, 5, 13 (See Notes 3, 4, and 10)	rcontext (See Note 10)
type=full	asname (See Note 10)	cics (See Notes 5, 6, 7, 8, and 9)	opc (See Notes 1, 2, and 3)	asname (See Note 10)	asname (See Note 10)
asname (See Note 10)	rcontext (See Note 10)	cice (See Notes 5, 6, 7, 8, and 9)	asname (See Note 10)	rcontext (See Note 10)	rcontext (See Note 10)
rcontext (See Note 10)		type=full	rcontext (See Note 10)
		asname (See Note 10)
		rcontext (See Note 10)
Notes: 1. The `dpc` and `opc` parameters can be either an ANSI point code (`dpca`, `opca`), ITU-I point code or ITU-I spare point code (`dpci`, `opci`), 14-bit ITU-N point code or 14-bit ITU-N spare point code (`dpcn`, `opcn`), or 24-bit ITU-N point code (`dpcn24`, `opcn24`). If the `dpc` and `opc` parameters are specified, the `dpc` and `opc` must be the same type of point code. For example, if the `dpca` parameter is specified, the OPC is specified with the `opca` parameter. If either point code value is a spare point code, the other point code value must be a spare point code on the same type. For example, if the `dpc` value is an ITU-I spare point code, the `opc` value must be an ITU-I spare point code. 2. If the ITU National Duplicate Point Code feature is on, the values for the `dpcn` and `opcn` parameters must have group codes assigned to them. The field `ITUDUPPC` in the `rtrv-feat` command output shows whether or not the ITU National Duplicate Point Code feature is on. If group codes are specified for ITU-N DPC and OPC, the groups codes must be the same. 3. These parameters are optional for partial routing keys, but at least one these parameters must be specified with the `ent-appl-rtkey` command. 4. Text strings can be used in place of some numerical service indicator values. See Table 4-12 for a list of these text strings. 5. When the service indicator parameter value equals `4` and an ANSI dpc is specified, the `opc`, `cics`, and `cice` parameters cannot be used. If the service indicator parameter value equals `4` and an ITU dpc is specified, the `opc`, `cics`, and `cice` parameters are required. 6. If the service indicator parameter (`si`) value is `4`, the values of the `cics` and `cice` parameters is from `0` to `4095`. 7. If the service indicator parameter (`si`) value is `5` and the point code in the routing key is either an ITU-I, 14-bit ITU-N, or 24-bit ITU-N point code, the values of the `cics` and `cice` parameters is from `0` to `4095`. If the point code in the routing key is an ANSI point code, the values of the `cics` and `cice` parameters is from `0` to `16383`. 8. If the service indicator parameter value is `13`, the values of the `cics` and `cice` parameters is from `0` to `4294967295`. 9. The CIC range, defined by the `cics` and `cice` parameters, cannot overlap the CIC range in an existing routing key. 10. The following rules apply to using the `rcontext` parameter. The value of the `rcontext` parameter is from `0` to `4294967295`. The `rcontext` parameter is required for a routing key containing an SUA application server. The `rcontext` parameter is optional for a routing key containing an M3UA application server. The `rcontext` parameter value must be unique in the database. Multiple routing keys cannot have the same `rcontext` value assigned. An application server can be assigned to only one routing key containing a routing context value. If the application server being assigned to the new routing key is assigned to other routing keys that do not contain `rcontext` parameter values, the `rcontext` parameter cannot be specified for the new routing key. An application server can be assigned to multiple routing keys if those routing keys do not contain a routing context value. An application server can be assigned to either a routing key containing a routing context value, or to routing keys that do not contain a routing context value, but the application server cannot be assigned to both types of routing keys. In order for an M3UA or SUA association to be assigned to multiple routing keys with a routing context value, the M3UA or SUA association must be assigned to multiple application servers and then each application server must be assigned to a routing key containing a routing context value. 11. To communicate the status changes of remote IP subsystems (defined by the DPC and SSN specified in a full SCCP routing key), the DPC and SSN specified for a full SCCP routing key must be provisioned in the mated application table. Perform one of the mated application procedures in Database Administration - GTT User's Guide to provision a mated application with the DPC and SSN specified for a full SCCP routing key.

Canceling the RTRV-AS and RTRV-APPL-RTKEY Commands

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

Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-appl-rtkey commands were entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-appl-rtkey commands were entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as and rtrv-appl-rtkey commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-appl-rtkey 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 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   as12             FULL
----------  005-005-001   5  M3UA   as9              FULL
----------  005-005-001   5  M3UA   as9              FULL
2500        006-006-001   5  SUA    as10             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  SUA    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   as11             DEFAULT

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

The database can contain only one default routing key. If the rtrv-appl-rtkey output contains a default routing key, a default routing key cannot be added in this procedure. Continue the procedure with 2 to add either a full or partial routing key with the desired application server.

Display the current application server information in the database by entering the rtrv-as command.

The following is an example of the possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7

as3               LOADSHARE   10      assoc8
                                      assoc9

as4               LOADSHARE   10      assoc10
                                      assoc11

as5               LOADSHARE   10      assoc12
                                      assoc13

as6               LOADSHARE   10      assoc14
                                      assoc15

as7               LOADSHARE   10      assoc16
                                      assoc17

as8               LOADSHARE   10      assoc18
                                      assoc19

as9               LOADSHARE   10      assoc20
                                      assoc21

as10              LOADSHARE   10      assoc22
                                      assoc23

as12              LOADSHARE   10      assoc24
                                      assoc25
AS Table is (11 of 250) 4% full

If the required application server is not in the database, perform one of these procedures to add the application server:

If the rcontext parameter will not be specified for the routing key, make sure that the adapter parameter value for the associations assigned to the new application server is M3UA.

If the rcontext parameter will be specified for the routing key, make sure that the open parameter value of the associations is set to no. The adapter parameter value of these associations can be either SUA or M3UA.

SUA associations, and their corresponding application server, can be assigned to only these types of routing keys:

Full routing key – DPC/SI=3/SSN
Partial routing key – DPC/SI=3
Partial routing key – DPC only
Partial routing key – SI=3 only
Default routing key.

After the new application server is added to the database, continue the procedure with 4.

Display the routing keys containing the application server being used in this procedure by entering the rtrv-appl-rtkey command with the application server name and the display=all parameter.
For this example, enter these commands.
rtrv-appl-rtkey:asname=as4:display=all

The following 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-024-7      5 ---   1-057-4      150        175

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as4    
                                         
    ANAMES
    assoc11          assoc12

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE       LOC
----------   2-100-7      6 --- -----------    ---------- ---------- ----

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as4    
                                         
    ANAMES
    assoc11          assoc12

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
```
rtrv-appl-rtkey:asname=as5:display=all

The following 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
225          4-035-7      5 ---   3-200-4      200        300

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as5    
                                         
    ANAMES
    assoc15          assoc16


STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
```
If the application server is not assigned to any routing keys, the rcontext parameter can be specified for the new routing key using this application server. Continue the procedure with 4.

An application server can be assigned to only one routing key containing a routing context value. If the application server is assigned to other routing keys, the rcontext parameter cannot be specified for the new routing key being added in this procedure. If you wish to use the rcontext parameter for the new routing key, perform one of these procedures to add the application server:
After the new application server is added, continue the procedure with 6.

If the application server is assigned to other routing keys, and these routing keys do not contain rcontext parameter values, the application server can be assigned to the new routing key in this procedure, but the rcontext parameter cannot be specified for the new routing key.

If you do not wish to use the rcontext parameter for the new routing key, continue the procedure with 6.

Display the associations assigned to the application server displayed in 3, to verify the open parameter value of the association, using the rtrv-assoc command with the association names shown in 2.

For this example, enter these commands.

rtrv-assoc:aname=assoc11

This is an example of possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc11
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw110.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      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
      
      ASNAMES
      as4

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

rtrv-assoc:aname=assoc12

This is an example of possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc12
      LOC      1204          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw200.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    2564          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
      
      ASNAMES
      as4

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

rtrv-assoc:aname=assoc15

This is an example of possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc15
      LOC      1207          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw150.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    1500          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
      
      ASNAMES
      as5

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

rtrv-assoc:aname=assoc16

This is an example of possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc16
      LOC      1211          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw160.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    3571          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
      
      ASNAMES
      as5

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

Repeat this step for each association name displayed in 3 to verify the open parameter of each association assigned to the application server.

If a new application server was added in 2, continue the procedure with 6.

If the rcontext parameter is not being specified in this procedure, continue the procedure with 6.

If the open parameter value for all the associations assigned to the application server is no (shown in this step), continue the procedure with 6.

Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.
For this example, enter this command.
chg-assoc:aname=assoc11:open=no

chg-assoc:aname=assoc12:open=no

chg-assoc:aname=assoc15:open=no

chg-assoc:aname=assoc16:open=no

chg-assoc:aname=assoc20:open=no

When each of these commands have successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 09:12:36 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 assigned to the application server that have the open=yes parameter value.

If a default routing key with an application server name is being added in this procedure, continue the procedure with 11.

If ITU-I or 14-bit ITU-N spare point codes are not being assigned to the routing key, or if ITU-I or 14-bit ITU-N spare point codes are shown in any routing keys shown in the rtrv-app-rtkey output in 1, continue the procedure with 7.
Display the status of the ITU National and International Spare Point Code Support feature by entering the rtrv-ctrl-feat command with the ITU National and International Spare Point Code Support feature part number.
Enter this command.
rtrv-ctrl-feat:partnum=893013601

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

Feature Name              Partnum    Status  Quantity
Spare Point Code Support  893013601  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 ITU National and International Spare Point Code Support feature is not enabled, perform the “Activating the ITU National and International Spare Point Code Support feature” procedure in Database Administration - SS7 User's Guide and enable and turn on the ITU National and International Spare Point Code Support feature.

The DPC of the routing key cannot be the APC of an IPGWx linkset or an SAPC assigned to an IPGWx linkset.

Display the names of the IPGWx linksets by entering the rept-stat-iptps command. This is an example of the possible output.


rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0
IP TPS USAGE REPORT

           THRESH  CONFIG/  CONFIG/         TPS   PEAK      PEAKTIMESTAMP
                      RSVD      MAX
---------------------------------------------------------------------------
LSN
lsgw1201      80%     ----    10000  TX:   7200     7600  05-02-10 11:40:04
                                    RCV:   7200     7600  05-02-10 11:40:04
lsgw1204      80%     ----    10000  TX:   6700     7600  05-02-10 11:40:04
                                    RCV:   6500     7600  05-02-10 11:40:04
lsgw1207      80%     ----    10000  TX:   7300     7450  05-02-10 11:40:04
                                    RCV:   7300     7450  05-02-10 11:40:04
lsgw1211      80%      ----   10000  TX:   7400     7450  05-02-10 11:40:04
                                    RCV:   7400     7450  05-02-10 11:40:04 
---------------------------------------------------------------------------

Command Completed.

Display the IPGWx linksets shown in the rept-stat-iptps output in 7 using the rtrv-ls command and specifying the name of the linkset shown in 7.

For this example, enter these commands.

rtrv-ls:lsn=lsgw1201

This is an example of the possible output.


rlghncxa03w 08-04-28 16:31:35 GMT EAGLE5 38.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1201     240-020-000   scr1  1   1   yes A   1    off off off yes   off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE     IPLIML2

           LOC  LINK SLC TYPE
           1201 A    0   SS7IPGW

Link set table is (14 of 1024)  1% full

rtrv-ls:lsn=lsgw1204

This is an example of the possible output.


rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCN   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1204     2968          none  1   1   no  A   1    off off off ---   off

           CLLI         TFATCABMLQ  MTPRSE  ASL8  SLSRSB  MULTGC  ITUTFR
           -----------  1           ---     ---   1       no      off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1204 A    0   IPGWI

           SAPCI
           1-010-1

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

rtrv-ls:lsn=lsgw1207

This is an example of the possible output.


rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCI   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1207     2-154-0       none  1   1   no  A   1    off off off ---   off

           CLLI         TFATCABMLQ  MTPRSE  ASL8  SLSRSB  MULTGC  ITUTFR
           -----------  1           ---     ---   1       no      off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1207 A    0   IPGWI

           SAPCN
           5823

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

rtrv-ls:lsn=lsgw1211

This is an example of the possible output.


rlghncxa03w 08-04-28 16:31:35 GMT EAGLE5 38.0.0
                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1211     010-130-057   scr1  1   1   yes A   1    off off off yes   off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1211 A    0   SS7IPGW

Link set table is (14 of 1024)  1% full

If the DPC of the routing key is shown in the rtrv-ls outputs in this step, choose another DPC value for the routing key that is not shown in the rtrv-ls outputs in this step.

Note:

If theSI value of the routing key being added is a value other than 4, 5, or 13, continue the procedure with11.

Verify that the ISUP Routing over IP feature is on, by entering the rtrv-feat command.
If the ISUP Routing over IP feature is on, the IPISUP field should be set to on. For this example, the ISUP Routing over IP feature is off.

Note:
Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, see thertrv-feat command description in theCommands Manual.

If the ISUP Routing over IP feature is on, continue the procedure with 11.
Turn the ISUP Routing over IP feature on by entering this command.
chg-feat:ipisup=on

Note:
Once theISUP Routing overIP feature is turned on with thechg-feat command, it cannot be turned off.
The ISUP Routing over IP feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the ISUP Routing over IP feature, contact your Oracle Sales Representative or Account Representative.

When the chg-feat has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 11:43:04 GMT EAGLE5 36.0.0
CHG-FEAT: MASP A - COMPLTD
```
Add a routing key entry to the database by entering the ent-appl-rtkey command.
The parameters required for the ent-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-13 for the parameter combinations that can be used for the type of routing key being added to the database. For this example, enter these commands.
ent-appl-rtkey:dpci=3-009-3:si=5:opci=4-100-3:cics=100 :cice=500:asname=as3:type=full

ent-appl-rtkey:dpci=1-050-2:si=5:opci=6-077-7:cics=200 :cice=300:asname=as20:type=full:rcontext=2000

Note:
A routing key cannot be added with the application serveras4, displayed in3, because application serveras4 is assigned to a routing key containing a routing context value. Only one application server can be assigned to a routing key containing a routing context value.

When each of these commands have successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-APPL-RTKEY: MASP A - COMPLTD
```

Verify the new routing key information in the database by entering the rtrv-appl-rtkey command with the routing key parameters specified in 11 (dpc, si, opc, cics, cice, ssn, asname, type, and rcontext, as applicable) with the display=all parameter.

For this example, enter these commands.

rtrv-appl-rtkey:dpci=3-009-3:si=5:opci=4-100-3:cics=100 :cice=500:asname=as3:type=full:display=all

The following 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
----------   3-009-3      5 ---   4-100-3      100        500

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as3    
                                         
    ANAMES
    assoc11          assoc12

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

rtrv-appl-rtkey:dpci=1-050-2:si=5:opci=6-077-7:cics=200 :cice=300:asname=as20:type=full:rcontext=2000:display=all

The following 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
2000         1-050-2      5 ---   6-077-7      200        300

    ADPTR  TYPE      ASNAME             
    SUA    FULL      as20   
                                         
    ANAMES
    assoc20

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

Note:

If theopen parameter value of the associations assigned to the routing key added in this procedure was not changed (5was not performed), continue the procedure with14.

Change the value of the open parameter of the associations that were changed in 5 to yes by specifying the chg-assoc command with the open=yes parameter.
For this example, enter these commands.
chg-assoc:aname=assoc11:open=yes

chg-assoc:aname=assoc12:open=yes

chg-assoc:aname=assoc15:open=yes

chg-assoc:aname=assoc16:open=yes

chg-assoc:aname=assoc20:open=yes

When each of these commands have successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
```
Repeat this step for all the associations that were changed in 5.

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-23 Adding a Routing Key Containing an Application Server

Sheet 1 of 5

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5