The SS7 network configuration for the EAGLE requires linksets and routes. These entities use point codes, and these point codes must be defined in the destination point code table of the database. A destination is a node in any network that is uniquely identified by a point code in conjunction with a network indicator. The destination is always the node’s true point code.

The EAGLE supports three types of networks and nodes to carry SS7 traffic, using TCP/IP technology:

• ANSI
• ITU International (ITU-I)
• ITU National (ITU-N)

When nodes in different networks wish to communicate, each node must have its own true point code and an alternate point code for each of the network types involved. For example, if node 1 in an ANSI network, node 2 in an ITU-N network, and node 3 in an ITU-I network wish to communicate with each other, node 1 must have an ANSI true point code and one alternate point code each for the ITU-N and ITU-I network. Node 2 must have an ITU-N true point code and one alternate point code each for the ANSI and ITU-I network. Node 3 must have an ITU-I true point code and one alternate point code each for the ANSI and ITU-N network.

Figure 2-1 shows an example of a mixed network with ANSI, ITU-I, and ITU-N nodes. Each node has one true point code and two alternate point codes.

Figure 2-1 Mixed Network with ANSI, ITU-I, and ITU-N Nodes

The node’s true point code is also called the destination point code.

This chapter discusses the method for configuring destination point codes (DPCs) in the database of the EAGLE. Destination point codes can be one of five types:

• Full point codes used for SS7 routing. A full point code is a point code containing numbers in each portion of the point code, for example, 111-011-100. The full point code can be in one of three formats, ANSI, ITU international, or ITU national. See the Point Code Formats section for more information on the point code formats. The EAGLE must have a full point code for each network type (ANSI, ITU-N, ITU-I) it is connected to.
• Secondary point codes, used by the Multiple Point Code Support feature. A secondary point code is a point code assigned to a full point code and used as if they were the actual EAGLE point code. Secondary point codes can be in one of three formats: ANSI, ITU international, or ITU national. The format of the secondary point code must be the same as the format of the full destination point code. See the Multiple Point Code Support section for more information on secondary point codes.
• Cluster destination point codes, used by the cluster routing and management (CRMD) feature and nested cluster routing feature. A cluster point code is an ANSI point code containing numbers in the network identifier and network cluster portions of the point code, and an asterisk (*) in the network cluster member field of the point code, for example, 111-011-*. See the Cluster Routing and Management Diversity (CRMD) section and the Nested Cluster Routing section for more information on cluster point codes.
• Network routing point codes, used by the network routing feature. A network routing point code is an ANSI point code containing a number in the network identifier portion of the point code, and asterisks (*) in the network cluster and network cluster member portions of the point code, for example, 111-*-*. See the Network Routing section for information on network routing point codes.
• Proxy point codes, used by the Proxy Point Code feature. A proxy point code is a point code that assumes the point code of another node in order to ease the migration of deploying an STP in a network with direct-connect links into other networks. See the Proxy Point Codes section for more information about proxy point codes.

The Cluster Routing and Management Diversity (CRMD) feature, the nested cluster routing feature, the multiple point code support feature, and the network routing features are also discussed in this section.

In order to complete the definition of linksets and routes, destination point codes are required to be in the database. Even though linksets use adjacent point codes, the adjacent point code of a linkset must be defined in the destination point code table of the database.

The procedures shown in this chapter use a variety of commands. If more information on these commands is needed, go to Commands User's Guide to find the required information.

The EAGLE supports three different point code formats:

• ANSI point codes
• ITU International point codes
• ITU National point codes (both 14-bit ITU-N point codes and 24-bit ITU-N point codes).

rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
    DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
    020-002-045   rlghncbb100 no  --- ----------      --------------   SS7
    020-002-050   rlghncbb100 no  --- ----------      --------------   SS7

Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full

rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   020-002-045 ---------- --------------   lsn1       15    020-002-045
                                           lsn2       20    020-003-036
                                           lsn3       25    001-001-002
                                               RTX:No  CLLI=-----------
   020-002-050 ---------- --------------   lsn4       15    020-002-050
                                           lsn3       20    001-001-002
                                           lsn2       25    020-003-036
                                               RTX:No  CLLI=-----------

rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
    DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
    021-002-045   rlghncbb101 no  --- ----------      --------------   SS7
    021-002-050   rlghncbb101 no  --- ----------      --------------   SS7

Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full

rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   021-002-045 ---------- --------------   lsn10      15    021-002-045
                                           lsn20      20    021-003-036
                                           lsn30      25    010-001-002
                                               RTX:No  CLLI=-----------
   021-002-050 ---------- --------------   lsn40      15    021-002-050
                                           lsn30      20    010-001-002
                                           lsn20      25    021-003-036
                                               RTX:No  CLLI=-----------
   021-005-*   ---------- --------------   lsn40      15    021-002-050
                                           lsn30      20    010-001-002
                                           lsn20      25    021-003-036
                                               RTX:No  CLLI=-----------

rlghncxa03w 09-05-17 16:00:32 GMT  EAGLE5 41.0.0
    DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
    020-002-*     rlghncbb000 no  --- ----------      --------------   SS7
    020-002-045   rlghncbb100 no  --- ----------      --------------   SS7
    020-002-050   rlghncbb100 no  --- ----------      --------------   SS7

Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full

rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0

   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   020-002-045 ---------- --------------   lsn1       15    020-002-045
                                           lsn2       20    020-003-036
                                           lsn3       25    001-001-002
                                               RTX:No  CLLI=-----------
   020-002-050 ---------- --------------   lsn4       15    020-002-050
                                           lsn3       20    001-001-002
                                           lsn2       25    020-003-036
                                               RTX:No  CLLI=-----------
   020-002-*   ---------- --------------   lsn4       15    020-002-050
                                           lsn3       20    001-001-002
                                           lsn2       25    020-003-036
                                               RTX:No  CLLI=-----------

rlghncxa03w 09-05-17 16:00:32 GMT  EAGLE5 41.0.0
    DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
    021-*-*       rlghncbb001 yes yes ----------      --------------   SS7
    021-002-045   rlghncbb101 no  --- ----------      --------------   SS7
    021-002-050   rlghncbb101 no  --- ----------      --------------   SS7

Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full

rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0

   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   021-002-045 ---------- --------------   lsn10      15    021-002-045
                                           lsn20      20    021-003-036
                                           lsn30      25    010-001-002
                                               RTX:No  CLLI=-----------
   021-002-050 ---------- --------------   lsn40      15    021-002-050
                                           lsn30      20    010-001-002
                                           lsn20      25    021-003-036
                                               RTX:No  CLLI=-----------
   021-005-*   ---------- --------------   lsn40      15    021-002-050
                                           lsn30      20    010-001-002
                                           lsn20      25    021-003-036
                                               RTX:No  CLLI=-----------
   021-*-*     ---------- --------------   lsn30      20    010-001-002
                                           lsn20      25    021-003-036
                                           lsn40      35    021-002-050
                                               RTX:No  CLLI=-----------

The format of a 14-bit ITU national point code is defined by the npcfmti parameter of the chg-stpopts command. This parameter defines how the 14-bit ITU national point code is entered into the database, and how it is displayed in any EAGLE outputs (command outputs or unsolicited outputs).

The 14-bit ITU national point code can be either a single number, up to five digits, or two, three, or four numbers separated by dashes. The 14-bit ITU national point code is a 14-bit integer. The values used by the npcfmti parameter of the chg-stpopts command defines the number of bits that make up each part of the point code format, if the 14-bit ITU national point code is made up of two, three, or four numbers.

If the 14-bit ITU national point code format has less than four numbers, the parts of the point code format not being used must be specified as zero (0). All four parts of the point code format must be specified with the npcfmti parameter, no matter how many numbers the point code format will contain, and the sum of the values of all four parts of the point code format must be 14 (for example, NPCFMTI=7-7-0-0, NPCFMTI=0-6-8-0, NPCFMTI=0-0-4-10, NPCFMTI=3-8-3-0, NPCFMTI=14-0-0-0).

If the database contains 14-bit ITU national point codes of a particular format, and the format is changed with the npcfmti parameter of the chg-stpopts command, the format of the 14-bit ITU national point codes in the database will be changed to the new format.

The values of the parts of the 14-bit ITU national point code are defined in Table 2-2.

A 14-bit ITU national point code containing all zeros is a valid point code and can be entered into the database.

When the EAGLE is delivered to the user, the format of the 14-bit ITU national point code is set to 14-0-0-0 (a single number containing up to five digits). If the 14-bit ITU national point code is a single number, the value of the point code is from 1 to 16383.

To change the format of a 14-bit ITU national point code, perform Changing the Format of 14-Bit ITU National Point Codes. The example used in this procedure changes the format of the 14-bit ITU national point code from 14-0-0-0 to 4-4-4-2.

This feature allows an EAGLE mated pair to route traffic for two or more countries that may have overlapping point code values. For example, in the network shown in Figure 2-3, both Country 1 and Country 2 have SSPs with a PC value of 2047.

Figure 2-3 Network Example #1

C Linksets

For each group defined, a separate C-linkset must be defined. This C-linkset is used as the alternate route for point codes in the group.

For example, in Figure 2-4, LSC1 is used for point codes in Group fr. Its adjacent point code is 6201-fr, and is used as the alternate route for 6217-fr, 6218-fr, and 6223-fr.

LSC2 is used for point codes in Group ge. Its adjacent point code is group 4169-ge, and is used as the alternate route for 6200-ge, 6209-ge, and 6217-ge.

Figure 2-4 Network Example #2

For example, to provision the EAGLE for the network shown in Figure 2-5, the user would enter these commands:

ent-dstn:dpcn=6201-fr (Mate's true PC)

ent-dstn:dpcn=4169-ge (Mate's secondary PC)

ent-dstn:dpcn=6217-fr (Group fr destinations)

ent-dstn:dpcn=6218-fr

ent-dstn:dpcn=6223-fr

ent-dstn:dpcn=6200-ge (Group ge destinations)

ent-dstn:dpcn=6217-ge

ent-dstn:dpcn=6209-ge

ent-ls:lsn=LSC1:apcn=6201-fr:lst=C (C linkset used by Group fr)

ent-ls:lsn=LSC2:apcn=4169-ge:lst=C (C linkset used by Group ge)

ent-ls:lsn=LSB1:apcn=6217-fr:lst=B

ent-ls:lsn=LSB2:apcn=6200-ge:lst=B

ent-rte:dpcn=6217-fr:lsn=LSB1:rc=10 (primary route for a Group fr destination)

ent-rte:dpcn=6217-fr:lsn=LSC1:rc=20 (alternate route for a Group fr destination)

ent-rte:dpcn=6217-ge:lsn=LSB2:rc=10 (primary route for a Group ge destination)

ent-rte:dpcn=6217-ge:lsn=LSC2:rc=20 (alternate route for a Group ge destination)

Conversion between ITU-N and ITU-I or ANSI

Each ITU-N destination and group code can have its own ITU-I or ANSI alias PC. Each ITU-I or ANSI node can be assigned one ITU-N destination. For conversion from ITU-I or ANSI to ITU-N to succeed, the ITU-N alias of the sending node must have the same group code as the destination's group code. So each ITU-I or ANSI node can only send and receive messages from one ITU-N group.

Figure 2-5 Network for Conversion

In Figure 2-5, SSP-N1 (2045-bd) is assigned ITU-I alias 1-6-1, and SSP-N2 (2045-xy) is assigned ITU-I alias 1-7-1. SSP-I1 is assigned ITU-N alias 2130-bd and SSP-I2 is assigned ITU-N alias 2131-xy. In this example, SSP-I1 can exchange traffic with nodes in group bd, but not nodes in group xy. SSP-I2 can exchange traffic with nodes in group xy, but not nodes in group bd.

SSP-I1 (1-5-1) can send to SSP-N1 by using the ITU-I alias 1-6-1, But if SSP-I1 tries to send to 2045-xy by using the ITU-I alias 1-7-1, conversion will fail, and the EAGLE will generate UIM 1091 (Indicating OPC conversion failed).

SSP-N1 can send traffic to SSP-I1, but SSP-N2 cannot send traffic to SSP-I1. SSP-N1 sends an ITU-N MSU with DPC set to 2130. The EAGLE assigns a group code of bd to the MSU based on the incoming linkset. The EAGLE then looks up 2130-bd, determines that this is an alias for ITU-I 1-5-1, and routes the MSU to SSP-I1.

If SSP-N2 sends an ITU-N MSU with DPC set to 2130, the EAGLE assigns a group code of xy to the MSU based on the incoming linkset. The EAGLE then looks up 2130-xy, does not find a match, and discards the MSU.

To provision the SSP-N1, SSP-N2, SSP-I1, and SSP-I2 in the network shown in Figure 2-5, the following commands are used:

ent-dstn:dpcn=2045-bd:aliasi=1-6-1

ent-dstn:dpcn=2045-xy:aliasi=1-7-1

ent-dstn:dpci=1-5-1:aliasn=2130-bd

ent-dstn:dpci=1-5-2:aliasn=2131-xy

ent-rte:dpcn=2045-bd:lsn=LSB1:rc=10

ent-rte:dpcn=2045-xy:lsn=LSB2:rc=10

ent-rte:dpci=1-5-1:lsn=LSB3:rc=10

ent-rte:dpci=1-5-2:lsn=LSB3:rc=10

The Proxy Point Code feature allows the EAGLE to assume the point codes of other nodes in order to ease the migration of deploying an STP in a network with direct-connect links into other networks. For example, if a foreign network SS7 node is directly connected to an SS7 node in the home network, an EAGLE can be deployed so that the transition is transparent to the foreign node. The foreign node can still behave as if it is connected to the original node in the home network. EAGLE will provide routing connectivity in the home network to the foreign node and will allow the foreign node to connect to the home network.

In the examples in Figure 2-6, foreign network Node A connects to home network Node B. Normally, STP C would connect between them, requiring both Node A and Node B to use STP C as the APC. With this feature, Node A does not require any modifications, as STP C provides a proxy point code B. The configuration in this example assume that the self point code of the STP is C.

Figure 2-6 Context of the Proxy Point Code in the Network

A proxy point code can be any of these types of point codes:

• ANSI
• ITU-I
• ITU-I Spare
• 14-bit ITU-N
• 14-bit ITU-N Spare
• 24-bit ITU-N

A proxy point code must be a full point code and cannot be a cluster point code or a network routing point code. Private point codes and secondary point codes cannot be used as a proxy point code.

The following types of signaling links can be assigned to a linkset whose adjacent point code is a proxy point code:

• LSL
• ATM-HSL (LIM-ATM and E1-ATM are supported)
• SE-HSL
• M2PA.

Feature Provisioning Requirements

Once a proxy point code quantity has been enable, the quantity cannot be decreased.

A temporary feature access key cannot be used to enabled a proxy point code quantity.

Once a proxy point code quantity has been enabled, the proxy point codes are provisioned in the database with the ent-dstn command and the prx parameter. Other point codes can use a proxy point code that is already provisioned in the database. These point codes are provisioned with the ent-dstn command and the ppc parameter.

After the proxy point code has been provisioned in the database, a linkset using the proxy point code can be provisioned in the database. This linkset, referred to as a proxy linkset, is provisioned using the ent-ls command with the adjacent point code of the linkset, the lst=prx parameter, and the ppc parameter. The ppc parameter value is the proxy point code provisioned with the ent-dstn command.

A proxy linkset has the same characteristics as an A linkset.

A proxy point code can be assigned to a maximum of 10 linksets.

Secondary adjacent point codes are not supported on a proxy linkset.

A proxy point code cannot be used as the adjacent point code of an IPGWx linkset.

To provision the Proxy Point Code feature, perform these procedures.

1. Enable a proxy point code quantity using the enable-ctrl-feat command. Perform Changing the Proxy Point Code Quantity. Once a proxy point code quantity is enabled, the Proxy Point Code feature is enabled and turned on. The chg-ctrl-feat command cannot be used to turn the Proxy Point Code feature on.
2. Provision the proxy point code using the ent-dstn command with the prx and ppc parameters. Perform Adding a Destination Point Code.
3. Provision the proxy linkset using the ent-ls command with the lst=prx and ppc parameters. Perform Adding an SS7 Linkset .

1. Display the features that are enabled by entering the rtrv-ctrl-featcommand.

   The following is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   Command Class Management  893005801  on      ----
   LNP Short Message Service 893006601  on      ----
   Intermed GTT Load Sharing 893006901  on      ----
   XGTT Table Expansion      893006101  on      4000000
   XMAP Table Expansion      893007710  on      3000
   Large System # Links      893005901  on      1500
   Routesets                 893006401  on      6000
   HC-MIM SLK Capacity       893012707  on      64
   
   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 a proxy point code quantity is shown in the rtrv-ctrl-feat output, continue the procedure with Oracle.

   If the rtrv-ctrl-feat output in 1 shows any controlled features, continue the procedure with Oracle. If the rtrv-ctrl-feat output shows only the HC-MIM SLK Capacity feature with a quantity of 64, 2 through 5 must be performed.

   If a proxy point code quantity is not shown in the rtrv-ctrl-feat output, continue the procedure with 2.

2. Display the serial number in the database with the rtrv-serial-num command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   System serial number = nt00001231
   System serial number is not locked.
   rlghncxa03w 07-10-28 21:15:37 GMT EAGLE5 37.0.0
   Command Completed
   

   Note:

   If the serial number is correct and locked, continue the procedure with Oracle. If the serial number is correct but not locked, continue the procedure with 5. If the serial number is not correct, but is locked, a proxy point code quantity cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer to My Oracle Support (MOS) for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
3. Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.

   For this example, enter this command.

   ent-serial-num:serial=<EAGLE’s correct serial number>

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENT-SERIAL-NUM:  MASP A - COMPLTD
   

4. Verify that the serial number entered into 3 was entered correctly using the rtrv-serial-num command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   System serial number = nt00001231
   System serial number is not locked.
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   Command Completed
   

   If the serial number was not entered correctly, repeat 3 and 4 and re-enter the correct serial number.

5. Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in 2 , if the serial number shown in 2 is correct, or with the serial number shown in 4 , if the serial number was changed in 3 , and with the lock=yes parameter.

   For this example, enter this command.

   ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENT-SERIAL-NUM:  MASP A - COMPLTD
   

6. Enable a proxy point code quantity with the enable-ctrl-feat command specifying the part number for the proxy point code quantity and the feature access key.

   For this example, enter this command.

   enable-ctrl-feat:partnum=893018703:fak=<30 proxy point codes feature access key>

   Note:

   A temporary feature access key cannot be specified to enable the proxy point code quantity.

   Note:

   The values for the feature access key (thefakparameter) are provided by Oracle. If you do not have the feature access key for the proxy point code quantity you wish to enable, contact your Oracle Sales Representative or Account Representative.

   When the enable-ctrl-feat command has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENABLE-CTRL-FEAT: MASP B - COMPLTD
   

7. Verify the changes by entering the rtrv-ctrl-featcommand with the proxy point code quantity part number specified in Oracle .

   For this example, enter this command.

   rtrv-ctrl-feat:partnum=893018703

   The following is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   Proxy Point Code          893018703  on      30
   
   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.
   

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

   The following 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.
   

rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
Destination table is (10 of 8000) 1% full
Alias table is (8 of 8000) 1% full
RTRV-DSTN: MASP A - COMPLTD

rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
DESTINATION ENTRIES ALLOCATED:   8000
    FULL DPC(s):                    9
    EXCEPTION DPC(s):               0
    NETWORK DPC(s):                 0
    CLUSTER DPC(s):                 1
    TOTAL DPC(s):                  10
    CAPACITY (% FULL):             1%
ALIASES ALLOCATED:               8000
    ALIASES USED:                   8
    CAPACITY (% FULL):             1%
X-LIST ENTRIES ALLOCATED:         500
RTRV-DSTN: MASP A - COMPLTD

1. Display the DPC quantity currently allowed in the EAGLE by entering the rtrv-stpopts command.

   The DPC quantity is displayed in the MTPDPCQ field of the output. This is an example of the possible output.

   
   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   STP OPTIONS
   -----------------------
   MTPDPCQ           1750
   

   Note:

   The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in Commands User's Guide.

   The MTPDPCQ value cannot exceed one of these totals depending on the features that are enabled or turned on.

   • 2000 – if the 5000 Routes feature is not on, and 6000, 7000, 8000, or 10,000 routesets are not enabled.
   • 5000 – if the 5000 Routes feature is on, and 6000, 7000, 8000, or 10,000 routesets are not enabled.
   • 6000 – if 6000 routesets are enabled.
   • 7000 – if 7000 routesets are enabled.
   • 8000 – if 8000 routesets are enabled.
   • 10,000 – if 10,000 routesets are enabled.

   If the Cluster Routing and Management Diversity feature is on, the MTPXLQ field will be shown in the rtrv-stpopts command output. The MTPXLQ field shows the maximum number of entries the exception list (x-list) can contain. The sum of the MTPDPCQ and MTPXLQ values cannot exceed one of these totals depending on the features that are enabled or turned on.

   • 2500 – if the 5000 Routes feature is not on, and 6000, 7000, 8000, or 10,000 routesets are not enabled.
   • 5500 – if the 5000 Routes feature is on, and 6000, 7000, 8000, or 10,000 routesets are not enabled.
   • 6500 – if 6000 routesets are enabled.
   • 7500 – if 7000 routesets are enabled.
   • 8500 – if 8000 routesets are enabled.
   • 10,500 – if 10,000 routesets are enabled.

   For more information on the Cluster Routing and Management Diversity feature, see the Cluster Routing and Management Diversity (CRMD) section.

   Perform one of the following steps based on the MTPDPCQ value (or MTPDPCQ and MTPXLQ values) shown in the rtrv-stpopts output. The values shown in parentheses are the sum of the MTPDPCQ and MTPXLQ values.

   • 8001 - 10,000 (8501 - 10,500) – 10,000 routesets are enabled. The only action that can be performed is to change the DPC quantity using the chg-stpopts command. This is the maximum number of routesets the EAGLE can have. Continue the procedure with 14 to change the DPC quantity. If you do not wish to change the DPC quantity, this procedure is finished.
   • 7001 - 8000 (7501 - 8500) – 8000 routesets are enabled. To enable the 10,000 routeset quantity, continue the procedure with 11. If you wish to change the DPC quantity and not enable 10,000 routesets, continue the procedure with 14. If you do not wish to enable 10,000 routesets or change the DPC quantity, this procedure is finished.
   • 6001 - 7000 (6501 - 7500) – 7000 routesets are enabled. To enable the 8000 routeset quantity, continue the procedure with Oracle. To enable the 10,000 routeset quantity, continue the procedure with 11. If you wish to change the DPC quantity and not enable 8000 or 10,000 routesets, continue the procedure with 14. If you do not wish to enable 8000 or 10,000 routesets or change the DPC quantity, this procedure is finished.
   • 5001 - 6000 (5501 - 6500) – 6000 routesets are enabled. To enable 7000, or 8000, 10,000 routesets, continue the procedure with 10. To enable the 10,000 routeset quantity, continue the procedure with 11. If you wish to change the DPC quantity and not enable 7000, 8000, or 10,000 routesets, continue the procedure with 14. If you do not wish to enable 7000, 8000, or 10,000 routesets or change the DPC quantity, this procedure is finished.
   • 2001 - 5000 (2501 - 5500) – The 5000 Routes feature is on. To enable 6000, 7000, 8000, or 10,000 routesets, perform 2. If you wish to change the DPC quantity and not enable 6000, 7000, 8000, or 10,000 routesets, continue the procedure with 14. If you do not wish to enable 6000, 7000, 8000, or 10,000 routesets or change the DPC quantity, this procedure is finished.
   • 2000 or less (2500 or less) – Continue the procedure with 2.
2. Verify that 6000, 7000, 8000, or 10,000 routesets are enabled by entering the rtrv-ctrl-featcommand.

   The following is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   Command Class Management  893005801  on      ----
   LNP Short Message Service 893006601  on      ----
   Intermed GTT Load Sharing 893006901  on      ----
   XGTT Table Expansion      893006101  on      4000000
   XMAP Table Expansion      893007710  on      3000
   Large System # Links      893005901  on      1500
   Routesets                 893006401  on      6000
   HC-MIM SLK Capacity       893012707  on      64
   
   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 10,000 routesets are enabled, the Routesets row appears in the rtrv-ctrl-feat output with a quantity of 10,000. The only action that can be performed is to change the DPC quantity using the chg-stpopts command. This is the maximum number of routesets the EAGLE can have. Continue the procedure with 14 to change the DPC quantity. If you do not wish to change the DPC quantity, this procedure is finished.

   If 8000 routesets are enabled, the Routesets row appears in the rtrv-ctrl-feat output with a quantity of 8000. To enable 10,000 routesets, continue the procedure with 11. If you wish to change the DPC quantity and not enable 10,000 routesets, continue the procedure with 14. If you do not wish to enable 10,000 routesets or change the DPC quantity, this procedure is finished.

   If 7000 routesets are enabled, the Routesets row appears in the rtrv-ctrl-feat output with a quantity of 7000. To enable 8000 routesets, continue the procedure with Oracle. To enable 10,000 routesets, continue the procedure with 11. If you wish to change the DPC quantity and not enable 8000 or 10,000 routesets, continue the procedure with 14. If you do not wish to enable 8000 or 10,000 routesets or change the DPC quantity, this procedure is finished.

   If 6000 routesets are enabled, the Routesets row appears in the rtrv-ctrl-feat output with a quantity of 6000. To enable 7000 or 8000, 8000, or 10,000 routesets, continue the procedure with 10. To enable 10,000 routesets, continue the procedure with 11. If you wish to change the DPC quantity and not enable 7000, 8000, or 10,000 routesets, continue the procedure with 14. If you do not wish to enable 7000, 8000, or 10,000 routesets or change the DPC quantity, this procedure is finished.

   If 6000, 7000, 8000, or 10,000 routesets are not enabled, continue the procedure with 3.

3. Enter the rtrv-feat command to verify that the 5000 Routes feature is turned on.

   If the 5000 Routes feature is on, the DSTN5000 = on entry appears in the output.

   Note:

   The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in the Commands Manual.

   If the 5000 Routes feature is not on, and you do not wish to turn the 5000 Routes feature on, or enable 6000, 7000, 8000, or 10,000 routesets, the only action that can be performed is to change the DPC quantity using the chg-stpopts command. However the DPC quantity can be no greater than 2000 DPCs (2500 DPCs if the rtrv-stpopts output in 1 contains the MTPDPCQ and MTPXLQ parameters). Continue the procedure with 14 to change the DPC quantity. If you do not wish to change the DPC quantity, this procedure is finished.

   If the 5000 Routes feature is not on, and you wish to turn the 5000 Routes feature on, or enable 6000, 7000, 8000, or 10,000 routesets, continue the procedure with 4.

   If the 5000 Routes feature is on, continue the procedure with 6.

4. Turn the 5000 Routes feature on by entering this command.

   chg-feat:DSTN5000=on

   Note:

   Once the 5000 Routes feature is turned on with the chg-feat command, it cannot be turned off.

   The 5000 Routes 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 5000 Routes feature, contact your Oracle Sales Representative or Account Representative.

   When the chg-feat has successfully completed, this message appears.

   
   rlghncxa03w 07-05-28 11:43:04 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

5. Verify that the 5000 Routes feature is turned on, by entering the rtrv-feat command.

   If the 5000 Routes feature is on, the DSTN5000 = on appears in the command output.

   Note:

   The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in Commands User's Guide.

   If 6000, 7000, 8000, or 10,000 routesets are not being enabled, the only action that can be performed is to change the DPC quantity. If you wish to change the DPC quantity and not enable 6000, 7000, 8000, or 10,000 routesets, continue the procedure with 14. If you do not wish to enable 6000, 7000, 8000, or 10,000 routesets or change the DPC quantity, this procedure is finished.

   If 6000, 7000, 8000, or 10,000 routesets are being enabled, go to 6.

   Note:

   If the rtrv-ctrl-feat output in 1 shows any controlled features, continue the procedure 10. If the rtrv-ctrl-feat output shows only the HC-MIM SLK Capacity feature with a quantity of 64, 6 through 9 must be performed.

   If 6000, 7000, 8000, or 10,000 routesets are being enabled, the serial number of the EAGLE must be in the database and the serial number must be locked. If the rtrv-ctrl-feat output in 2 shows any features in addition to the HC-MIM SLK Capacity feature with a quantity of 64, the serial number is in the database and it is locked. Continue the procedure by performing one of these steps.

   • If 6000 routesets are being enabled, continue the procedure with Oracle.
   • If 7000, 8000, or 10,000 routesets are being enabled, continue the procedure with 10.

   The HC-MIM SLK Capacity feature with a quantity of 64 is shown in the rtrv-ctrl-feat output in 2 whether or not the serial number of the EAGLE is in the database or whether or not the serial number is locked. If the rtrv-ctrl-feat output shows only the HC-MIM SLK Capacity feature with a quantity of 64, the status of the serial number must be verified. Continue the procedure with 6.

6. Display the serial number in the database with the rtrv-serial-num command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   System serial number = nt00001231
   System serial number is not locked.
   rlghncxa03w 07-10-28 21:15:37 GMT EAGLE5 37.0.0
   Command Completed
   

   Note:

   If the serial number is correct and locked, continue the procedure with Oracle if 6000 routesets are being enabled. Continue the procedure with 10 if 7000, 8000, or 10,000 routesets are being enabled. If the serial number is correct but not locked, continue the procedure with 9. If the serial number is not correct, but is locked, 6000, 7000, 8000, or 10,000 routesets cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer to the My Oracle Support (MOS) section for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
7. Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.

   For this example, enter this command.

   ent-serial-num:serial=<EAGLE’s correct serial number>

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENT-SERIAL-NUM:  MASP A - COMPLTD
   

8. Verify that the serial number entered in 7 was entered correctly using the rtrv-serial-num command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   System serial number = nt00001231
   System serial number is not locked.
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   Command Completed
   

   If the serial number was not entered correctly, repeat 7 and 8 and re-enter the correct serial number.

9. Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in 6, if the serial number shown in 6 is correct, or with the serial number shown in 8, if the serial number was changed in 7, and with the lock=yes parameter.

   For this example, enter this command.

   ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENT-SERIAL-NUM:  MASP A - COMPLTD
   

   If 6000 routesets are not being enabled, continue the procedure with Oracle.

   If 7000, 8000, or 10,000 routesets are not being enabled, continue the procedure with Oracle.

   If 7000 routesets are currently enabled, and 8000 or 10,000 routesets are being enabled, continue the procedure with Oracle.

   If 5000 or 6000 routesets are currently enabled and 7000, 8000, or 10,000 routesets are being enabled, continue the procedure with 10.

10. Verify the number of alias point codes configured in the EAGLE by entering the rtrv-dstn command with the msar=only parameter.

    To enable 7000 or 8000 routesets, the EAGLE can have no more than 8000 alias point codes.

    To enable 10,000 routesets, the EAGLE can have no more than 10,000 alias point codes.

    The msar=only parameter displays only the maximum numbers of different types of point codes the EAGLE can have and the actual numbers of the different types of point codes that are configured in the EAGLE.

    rtrv-dstn:msar=only

    One of two types of outputs are displayed, depending on whether or not the Cluster Routing and Management Diversity feature is on or off.

    If the Cluster Routing and Management Diversity feature is off:

    
    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    Destination table is (10 of 8000) 1% full
    Alias table is (8 of 8000) 1% full
    RTRV-DSTN: MASP A - COMPLTD
    

    If the Cluster Routing and Management Diversity feature is on:

    
    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    DESTINATION ENTRIES ALLOCATED:   8000
        FULL DPC(s):                    9
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  10
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                   8
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    If 7000 or 8000 routesets are being enabled and the EAGLE contains more than 8000 alias point codes, perform the Changing a Destination Point Code procedure to reduce the number of alias point codes to an amount below 8000.

    If 10,000 routesets are being enabled and the EAGLE contains more than 10,000 alias point codes, perform the Changing a Destination Point Code procedure to reduce the number of alias point codes to an amount below 10,000.

    When this step has been completed, continue the procedure by performing one of these steps.

    • If 7000 or 8000 routesets are being enabled, continue the procedure with Oracle.
    • If 10,000 routesets are being enabled, continue the procedure with 11.
11. Display the control cards in the EAGLE by entering this command.

    rtrv-stp:gpl=oamhc

    This is an example of the possible output.

    
    rlghncxa03w 10-12-01 16:07:48 GMT  EAGLE5 43.0.0
    
    Card  Part Number  Rev Serial Number  Type     DB     APPL     GPL Version
    ----  -----------  --- -------------  ----     --     ----     -----------
    1113  870-2903-01  C   10206255064    E5MCAP   1024M  OAMHC    132-018-000
    1115  870-2903-01  C   10206255165    E5MCAP   1024M  OAMHC    132-018-000
    
    Command Completed.
    

    To enable 10,000 routesets, E5-MCAP cards must be installed in card locations 1113 and 1115. If E5-MCAP cards are not shown in either card location 1113 or 1115, install the E5-MCAP cards in card locations 1113 or 1115 as required. Contact the Customer Care Center before installing the E5-MCAP cards. Refer to the My Oracle Support (MOS) section for the contact information.

    After the E5-MCAP cards have been installed, or if E5-MCAP cards are shown in card locations 1113 and 1115 in the rtrv-stp output, continue the procedure with Oracle.

12. Enable the routeset quantity with the enable-ctrl-feat command specifying the part number for the routeset quantity and the feature access key.
    • To enable 6000 routesets, enter this command.

      enable-ctrl-feat:partnum=893006401:fak=<6000 Routesets feature access key>

    • To enable 7000 routesets, enter this command.

      enable-ctrl-feat:partnum=893006402:fak=<7000 Routesets feature access key>

    • To enable 8000 routesets, enter this command.

      enable-ctrl-feat:partnum=893006403:fak=<8000 Routesets feature access key>

    • To enable 10,000 routesets, enter this command.

      enable-ctrl-feat:partnum=893006405:fak=<10,000 Routesets feature access key>

    Note:

    A temporary feature access key cannot be specified to enable the routeset quantity.

    Note:

    The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the routeset quantity you wish to enable, contact your Oracle Sales Representative or Account Representative.

    When the enable-ctrl-feat command has successfully completed, this message should appear.

    
    rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
    ENABLE-CTRL-FEAT: MASP B - COMPLTD
    

13. Verify the changes by entering the rtrv-ctrl-featcommand with the routeset quantity part number specified in Oracle.
    • If 6000 routesets was enabled, enter this command.

      rtrv-ctrl-feat:partnum=893006401

      The following is an example of the possible output.

      
      rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
      The following features have been permanently enabled:
      
      Feature Name              Partnum    Status  Quantity
      Routesets                 893006401  on      6000
      
      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 7000 routesets was enabled, enter this command.

      rtrv-ctrl-feat:partnum=893006402

      The following is an example of the possible output.

      
      rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
      The following features have been permanently enabled:
      
      Feature Name              Partnum    Status  Quantity
      Routesets                 893006402  on      7000
      
      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 8000 routesets was enabled, enter this command.

      rtrv-ctrl-feat:partnum=893006403

      The following is an example of the possible output.

      
      rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
      The following features have been permanently enabled:
      
      Feature Name              Partnum    Status  Quantity
      Routesets                 893006403  on      8000
      
      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 10,000 routesets was enabled, enter this command.

      rtrv-ctrl-feat:partnum=893006405

      The following is an example of the possible output.

      
      rlghncxa03w 10-12-28 21:15:37 GMT EAGLE5 42.0.0
      The following features have been permanently enabled:
      
      Feature Name              Partnum    Status  Quantity
      Routesets                 893006405  on      10000
      
      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.
      

    Continue the procedure by performing one of these steps.

    • If the DPC quantity or exception list quantity are not being changed, continue the procedure with 16.
    • If the DPC quantity or exception list quantity are being changed, continue the procedure with 14.
14. Change the maximum number of destination point codes that the EAGLE can contain by entering the chg-stpopts command with the mtpdpcq parameter.
    The values that can be specified with the mtpdpcq parameter is shown in the following list.

    • 500 to 2000 – if the 5000 Routes feature is not on, and 6000, 7000, 8000, or 10,000 routesets are not enabled.
    • 500 to 5000 – if the 5000 Routes feature is on, and 6000, 7000, 8000, or 10,000 routesets are not enabled.
    • 500 to 6000 – if 6000 routesets are enabled.
    • 500 to 7000 – if 7000 routesets are enabled.
    • 500 to 8000 – if 8000 routesets are enabled.
    • 500 to 10000 – if 10000 routesets are enabled.

    For this example, enter this command.

    chg-stpopts:mtpdpcq=7350

    When this command has successfully completed, this message should appear.

    
    rlghncxa03w 07-05-07 00:22:57 GMT  EAGLE5 37.0.0
    CHG-STPOPTS: MASP A - COMPLTD
    

    If the MTPXLQ field (the exception list quantity) is shown in the rtrv-stpopts output in 1, and you wish to change only the MTPXLQ value, enter the chg-stpopts command with the mtpxlq parameter. For example, if you wish to change the exception list quantity to 1000 point codes, enter this command.chg-stpopts:mtpxlq=1000.

    Both the exception list quantity and the maximum of destination point codes can be changed, by entering the chg-stpopts command with both the mptdpcq and mptxlq parameters. For example, if you wish to change the exception list quantity to 1000 point codes and the maximum number of point codes to 6200, enter this command.

    chg-stpopts:mtpxlq=1000:mtpdpcq=6750

    When specifying the mtpxlq parameter with the chg-stpopts command, the resulting sum of the MTPDPCQ and MTPXLQ values cannot be greater than the values shown in the following list.

    • 2500 – if the 5000 Routes feature is not on, and 6000, 7000, 8000, or 10,000 routesets are not enabled. The range of values for the mtpdpcq and mtpxlq parameters is from 500 to 2000.
    • 5500 – if the 5000 Routes feature is on, and 6000, 7000, 8000, or 10,000 routesets are not enabled. The range of values for the mtpdpcq and mtpxlq parameters is from 500 to 5000.
    • 6500 – if 6000 routesets are enabled. The range of values for the mtpdpcq and mtpxlq parameters is from 500 to 6000.
    • 7500 – if 7000 routesets are enabled. The range of values for the mtpdpcq parameter is from 500 to 7000. The range of values for the mtpxlq parameters is from 500 to 6000.
    • 8500 – if 8000 routesets are is enabled. The range of values for the mtpdpcq parameter is from 500 to 8000. The range of values for the mtpxlq parameters is from 500 to 6000.
    • 10500500 to 10500 – if 10000 routesets are enabled. The range of values for the mtpdpcq and mtpxlq parameters is from 500 to 10,000.
15. Verify the changes using the rtrv-stpopts command.

    This is an example of the possible output.

    
    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    STP OPTIONS
    -----------------------
    MTPDPCQ           7350
    

    Note:

    The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in the Commands Manual.

    If the mtpxlq parameter was specified in 14, the mtpxlq parameter value will be shown in the MTPXLQ field of the rtrv-stpopts command output.

16. 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.
    

1. Display the controlled features in the database by entering the rtrv-ctrl-feat command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 11:43:04 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   SCCP Conversion           893012001  on      ----
   EIR                       893012301  on      ----
   GSM Map Screening (GMS)   893013201  on      ----
   HC-MIM SLK Capacity       893012707  on      64
   
   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 enabled, the entry Spare Point Code Support is shown in the permanently enabled section of the rtrv-ctrl-feat output. If the status of the ITU National and International Spare Point Code Support feature is on, no further action can be performed.

   If the ITU National and International Spare Point Code Support is enabled but not turned on (shown by the entry off in the Status column), continue the procedure with 7.

   If the ITU National and International Spare Point Code Support is not enabled, continue the procedure with 2 .

2. Display the serial number in the database with the rtrv-serial-num command.

   Note:

   If the rtrv-ctrl-feat output in 1 shows any controlled features, continue the procedure with 6. If the rtrv-ctrl-feat output shows only the HC-MIMSLK Capacity feature with a quantity of 64, 2 through 5 must be performed.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   System serial number = nt00001231
   
   System serial number is not locked.
   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   Command Completed
   

   Note:

   If the serial number is correct and locked, continue the procedure with 6. If the serial number is correct but not locked, continue the procedure with 5. If the serial number is not correct, but is locked, this feature cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer to My Oracle Support (MOS) for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
3. Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.

   For this example, enter this command.

   ent-serial-num:serial=<EAGLE’s correct serial number>

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENT-SERIAL-NUM:  MASP A - COMPLTD
   

4. Verify that the serial number entered into 3 was entered correctly using the rtrv-serial-num command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   System serial number = nt00001231
   
   System serial number is not locked.
   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   Command Completed
   

   If the serial number was not entered correctly, repeat 3 and 4 and re-enter the correct serial number.
5. Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in 2, if the serial number shown in 2 is correct, or with the serial number shown in 4, if the serial number was changed in 3, and with the lock=yes parameter.

   For this example, enter this command.

   ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENT-SERIAL-NUM:  MASP A - COMPLTD
   

6. Enable the ITU National and International Spare Point Code Support feature by entering the enable-ctrl-feat command.

   For this example, enter this command.

   enable-ctrl-feat:partnum=893013601:fak=<ITU National and International Spare Point Code Support feature access key>

   Note:

   The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the ITU National and International Spare Point Code Support feature, contact your Oracle Sales Representative or Account Representative.

   When the enable-crtl-feat command has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   ENABLE-CTRL-FEAT: MASP A - COMPLTD
   

7. Turn the ITU National and International Spare Point Code Support feature on by entering the chg-ctrl-feat command with the part number used in 6 and the status=on parameter.

   Caution:

   Once the ITU National and International Spare Point Code Support feature is turned on, it cannot be turned off.

   For this example, enter this command.

   chg-ctrl-feat:partnum=893013601:status=on

   When this command has successfully completed, the following message should appear.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   CHG-CTRL-FEAT: MASP A - COMPLTD
   

8. Verify the changes by entering the rtrv-ctrl-featcommand.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.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.
   

9. Back up the new changes, using the chg-db:action=backup:dest=fixed command.
   The following 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.
   

10. To begin adding ITU-I or 14-bit ITU-N spare point codes, perform the Adding a Point Code to the Self-Identification of the EAGLE procedure.

    Note:

    Before executing this procedure, make sure you have purchased the ITU National and International Spare Point Code Support feature. If you are not sure if you have purchased the ITU National and International Spare Point Code Support feature, contact your Oracle Sales Representative or Account Representative.

Currently, the EAGLE supports six true point codes:

• ANSI point code
• ITU international point code
• ITU international spare point code
• 14-bit ITU national point code
• 14-bit ITU national spare point code
• 24-bit ITU national point code.

  Note:

  The ITU national point code can be either 14-bit ITU national - spare and non-spare - or 24-bit ITU national. Both 14-bit ITU national and 24-bit national point codes cannot be present in the EAGLE at the same time.

In addition, the EAGLE supports up to 96 capability point codes, each of which can be designated as either ANSI, ITU-I (spare and non-spare), 14-bit ITU-N (spare and non-spare), or 24-bit ITU-N. Each capability point code defined on an EAGLE node can be used for routing messages to that node. For various reasons, customers might need the EAGLE to support more than one true point code in a particular domain.

There are three main reasons driving this feature:

• Some customers desire to collapse multiple existing STP's into one EAGLE. This can present problems in that end offices and other nodes may not be controlled by the carrier making reprovisioning of these network elements difficult. Multiple Point Code (MPC) support is designed to allow the EAGLE to assume more than one point code for SS7 routing. MPC support is different in concept from capability point codes in that provisioning and routing will use secondary point codes as if they were the actual point code of the EAGLE.
• Several customers in the international market want to deploy a single STP pair in multiple national (ITU-N) networks. This may not be possible without the MPC feature, as these operators are often forced to use a unique point code assigned by each national regulator of these target countries.
• Customers may require additional links between two nodes beyond the number of links permitted by the protocol. For example, the maximum number of links between two nodes in an ITU network is 16. The MPC feature can allow for additional linksets between these nodes, increasing the number of links that can be used.

  This feature adds the ability to support Secondary Point Codes (SPCs) in addition to the true point codes used by the EAGLE in any of the three domains ANSI, ITU-N (14-bit or 24-bit) and ITU-I. Secondary point codes are used by provisioning and routing as if they are the true point code of the EAGLE. SPCs are supported for any type of link (A, B, C, D, etc.). There is no effect on provisioning capability point codes as a result of this feature.

  In addition to the one True Point Code (TPC) already supported for each of the ANSI, ITU-N (14-bit or 24-bit) and ITU-I domains, the EAGLE support a pool of 40 Secondary Point Codes (SPC), each of which may be assigned as either ANSI, ITU-I, 14-bit ITU-N, or 24-bit ITU-N (not to exceed a total of 40 in one EAGLE). SPCs can be used in the same ways that true PCs are used.

Replacing Two STP Pairs with One Pair

The following example shows how an EAGLE pair can replace two existing STP pairs. In this example, each EAGLE in the pair uses one true point code and one secondary point code.

As shown in Figure 2-14, a new EAGLE first replaces one existing STP pair. In this case, EAGLE's true point code is set to the true point code of the old STP. The adjacent nodes are cut over to the EAGLE pair. The adjacent nodes do not need to be reconfigured.

Figure 2-14 Replacing the First STP Pair

Next, a second STP pair is replaced with the EAGLE pair. As shown in Figure 2-15, an SSP and an STP are being “re-homed” from an old STP pair to a new EAGLE pair. In this example, the STP (003-003-003) is reconfigured with new routes to recognize that it is now connected to EAGLE 1 and EAGLE 2 instead of 001-001-001 and 001-001-002. STP 003-003-003, if not an EAGLE with Multiple Point Codes, may not be able to support more than one linkset to the same point code. See Multiple Linksets between Two Nodes section for a description of this capability. The interconnecting device (STP or SSP) can use either the TPC or SPC as the device requires.

At EAGLE 1, the user would configure the secondary point code 001-001-001, using the ent-spc command. The user would also configure a route to 001-001-002 over the C-linkset. The user would then configure point code 004-004-004 in the EAGLE's database to indicate that this point code uses the secondary point code 001-001-001, instead of the EAGLE's true point code (chg-dstn:dpc=004-004-004:spc=001-001-001. This last step would be repeated for all other adjacent SSPs and SCPs that are re-homed from the old STP Pair to the new EAGLE Pair.

Similarly, at EAGLE 2, the user would configure the secondary point code 001-001-002, and configure a route over the C-link to 001-001-001. The user would also configure point code 004-004-004 in EAGLE 2's database to indicate that this point code uses the secondary point code 001-001-002, instead of the EAGLE's true point code.

When EAGLE 1 receives a message from the SSP destined for 001-001-001, the EAGLE 5 ISS processes the message as if the message was sent to the EAGLE's true point code.

When EAGLE 1 generates a message (for example, network management, link test messages, or GTT messages) that is destined for 004-004-004, EAGLE 1 puts the OPC 001-001-001 in the message. When EAGLE 5 ISS 1 generates a message that is destined for 003-003-003 or 005-005-005, it puts the OPC 002-002-001 in the message. When EAGLE 1 generates GTT and SCMG messages that are destined for non-adjacent point codes, it includes the OPC 002-002-001 in the message.

Figure 2-15 Replacing a Second STP Pair

Multiple Linksets between Two Nodes

With this feature, it is possible to configure multiple linksets between two nodes, if the adjacent node also supports Multiple Point Codes. The EAGLE continues to enforce the rule that each linkset must have a different adjacent point code.

One reason for provisioning multiple linksets between two nodes is to increase the number of links that can be configured between STP pairs. For example, in Figure 2-16, the EAGLE is connected to an STP pair that supports multiple point codes. Without this feature, only 16 ITU links can be configured between the EAGLE and the STP pair (8 links in LS1 and 8 links in LS2). In this example, two linksets are added, increasing the number of links to 32 (8 links in each of LS1, LS2, LS3, and LS4).

Figure 2-16 Multiple Linkset Example

In this example, the adjacent point code (APC) for LS1 is 4-1-0 and the APC for LS2 is 4-1-1. 4-1-1 is assigned an SPC of 3-1-1. So adjacent, Adj Node1 sees LS1 as having an APC of 3-1-0, and LS2 as having an APC of 3-1-1.

To load balance over these 4 linksets, half the destinations that use the STP pair can be assigned LS1 and LS3 as a combined linkset. The other half of the destinations can be assigned LS2 and LS4 as a combined linkset.

The commands to provision EAGLE1 for the network shown in Figure 2-16 are:

chg-sid:pc=3-1-0

ent-spc=3-1-1

ent-dstn:dpc=4-1-0

ent-dstn:dpc=4-1-1:spc=3-1-1

ent-dstn:dpc=4-1-5

ent-dstn:dpc=4-1-6:spc=3-1-1

ent-dstn:dpc=5-5-1

ent-dstn:dpc=5-5-5

ent-ls:lsn=ls1:apc=4-1-0

ent-ls:lsn=ls2:apc=4-1-1

ent-ls: lsn=ls3:apc=4-1-5

ent-ls: lsn=ls4:apc=4-1-6

ent-rte:dpc=4-1-0:lsn=ls1:rc=10

ent-rte:dpc=4-1-1:lsn=ls2:rc=10

ent-rte:dpc=4-1-5:lsn=ls3:rc=10

ent-rte:dpc=4-1-6:lsn=ls4:rc=10

ent-rte:dpc=5-5-1:lsn=ls1:rc=10

ent-rte:dpc=5-5-1:lsn=ls3:rc=10

ent-rte:dpc=5-5-5:lsn=ls2:rc=10

ent-rte:dpc=5-5-5:lsn=ls4:rc=10

1. Display the current secondary point codes, using the rtrv-spc command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   SPC (Secondary Point Codes)
   
   SPCA
        001-010-010
        002-010-010
        003-010-010
   
   SPC-I
            1-253-5
            2-254-6
            3-255-7
   
   SPC-N
           10-01-11-1
           13-02-12-0
   
   SPC-N24
   
   none
   
   Secondary Point Code table is (8 of 40) 20% full
   

   If the secondary point code table is full, shown by the entry Secondary Point Code table is (40 of 40) 100% full, go to the Removing a Secondary Point Code procedure and remove a secondary point code from the database.

   If error message E3867 Cmd Rej: MPC feature must be enabled is displayed, the EAGLE has detected that the multiple point code support feature is off and the rtrv-spc command will not display any data. Continue the procedure with 2 to verify that the multiple point code support feature is off.

2. Verify whether or not the multiple point code support feature is on, by entering the rtrv-feat command.

   If the multiple point code support feature is on, the MPC field should be set to on. For this example, the multiple point code support feature is off.

   Note:

   The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in Commands User's Guide.

   If the multiple point code support feature is on, continue the procedure with 4.

   If the rtrv-feat command output shows that the multiple point code support feature is on, but error message E3867 was displayed when the rtrv-spc command was entered, contact the Customer Care Center. Refer to My Oracle Support (MOS) for the contact information.

   If group codes are to be assigned to the ITU-N secondary point code, and none are currently displayed in the rtrv-spc command output, the ITU National Duplicate Point Code feature must be on. This is shown by the entry ITUDUPPC = on in the rtrv-feat command output.

3. Turn the multiple point code support feature on by entering this command.
   chg-feat:mpc=on

   Note:

   Once the multiple point code support feature is turned on with the chg-feat command, it cannot be turned off.

   The multiple point code support 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 multiple point code support feature, contact your Oracle Sales Representative or Account Representative.

   When the chg-feat has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-07 00:57:31 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

   Note:

   If group codes are shown for the 14-bit ITU-N secondary point codes in the rtrv-spc command output, if 24-bit ITU-N secondary point codes are being configured, or the ITU National Duplicate Point Code feature is on, continue the procedure with 5.
4. Turn the ITU National Duplicate Point Code feature on by entering this command.
   chg-feat:ituduppc=on

   Note:

   Once the ITU National Duplicate Point Code feature is turned on with the chg-feat command, it cannot be turned off.

   The ITU National Duplicate Point Code 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 ITU National Duplicate Point Code feature, contact your Oracle Sales Representative or Account Representative.

   When the chg-feat has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-07 00:57:31 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

5. Display the self-identification of the EAGLE using the rtrv-sid command to verify the point code values in the self-identification of the EAGLE, and to verify the point code types defined in the EAGLE.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-10 11:43:04 GMT  EAGLE5 37.0.0
      PCA             PCI          PCN                CLLI              PCTYPE
      100-100-100     3-75-7       7-9-8-1            rlghncxa03w       OTHER
      
      CPCA
      002-002-002       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
      
      CPCA (LNP)
      005-005-002       005-005-004       005-005-005
      
      CPCI
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
      
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1
   

   To enter an ANSI secondary code with the ent-spc command, a point code must be shown in the PCA field of the rtrv-sid command output.

   To enter an ITU-I secondary point code with the ent-spc command, a point code must be shown in the PCI field of the rtrv-sid command output.

   To enter a 14-bit ITU-N secondary point code with the ent-spc command, a point code must be shown in the PCN field of the rtrv-sid command output.

   To enter a 24-bit ITU-N secondary point code with the ent-spc command, a point code must be shown in the PCN24 field of the rtrv-sid command output.

   If the required type of point code is shown in the rtrv-spc output in 1 or is shown in the rtrv-sid output in this step, continue the procedure with 6.

   If the required type of point code is not shown in the PCA, PCI, PCN, or PCN24 fields of the rtrv-sid command output, go to the Adding a Point Code to the Self-Identification of the EAGLE procedure and add the required point codes.

6. Display the current destination point codes using the rtrv-dstn 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          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      030-045-*     rlghncbb010 yes yes ----------      --------------   SS7
      111-011-*     rlghncbb000 yes yes ----------      --------------   SS7
      240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3     SS7
      240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
      240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1    SS7
      240-012-008   --------    yes ---    1-113-5         10-13-10-2    SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
      2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1     SS7
      2-131-2       --------    no  ---    222-211-001     11-11-8-2     SS7
      2-131-3       --------    no  ---    222-211-002     11-11-8-3     SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
      10-15-2-3     rlghncbb013 no  ---    222-200-200     2-121-1       SS7
      10-15-3-0     rlghncbb013 no  ---    222-200-201     2-121-2       SS7
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                    9
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  11
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  18
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   Note:

   If the spcn parameter is not being used in this procedure, continue the procedure with 9.
7. Display the PCT entries by entering the rtrv-pct command.

   This is an example of the possible output.

   
   rlghncxa03w 10-12-17 16:02:05 GMT  EAGLE5 43.0.0
   
       EPCA             FILTPCA          REALPCA      SI  SSN  RELCAUSE
       001-001-001      *                240-012-006   5  ---  10
   
       ECICS = 10          ECICE = 20
       RCICS = 30          RCICE = 40
   
       EPCI             FILTPCI          REALPCI      SI  SSN  RELCAUSE
       1-001-2          2-131-2          2-131-3       3   10  ---
   
       ECICS = ----------  ECICE = ----------
       RCICS = ----------  RCICE = ----------
   
       EPCN             FILTPCN          REALPCN      SI  SSN  RELCAUSE
       13-11-14-1       *                10-15-2-3     *  ---  ---
   
       ECICS = ----------  ECICE = ----------
       RCICS = ----------  RCICE = ----------
   
   
    Unique EPC    is 3 of 250
    Unique RealPC is 3 of 250
   
   PCT table is (3 of 1000) 1% full.
   

   Note:

   If the spcn parameter is not being used in this procedure, continue the procedure with 9.
8. Display the existing values for the npcfmti parameter by entering the rtrv-stpopts command.

   The value for the npcfmti parameter is shown in the NPCFMTI field. This is an example of the possible output.

   
   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   STP OPTIONS
   -----------------------
   NPCFMTI        4-4-4-2
   

   Note:

   The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in Commands User's Guide.

   If you wish to change the format of the 14-bit ITU national point codes, go to the 14-Bit ITU National Point Code Formats section. Changing the formats of the 14-bit ITU national point codes will change how any existing 14-bit ITU national point codes are displayed in the database.

9. Add the secondary point code, using the ent-spc command.

   The secondary point code being added in this procedure cannot match any of the point code values shown in the rtrv-sid output in 5, and any of the DPC or alias point code values shown in the rtrv-dstn output in 6.

   The secondary point code being added in this procedure cannot match the EPC (emulated point code) value shown in the rtrv-pct output in 7.

   For this example, enter these commands.

   ent-spc:spca=010-100-010

   ent-spc:spci=4-100-1

   ent-spc:spcn=14-15-12-1

   When each of these commands has successfully completed, this is an example of the message that should appear.

   
   rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
   Destination table is (11 of 40) 28% full
   ENT-SPC: MASP A - COMPLTD
   

10. Verify the changes using the rtrv-spc command.

    This is an example of the possible output.

    
    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    SPC (Secondary Point Codes)
    
    SPCA
         001-010-010
         002-010-010
         003-010-010
         010-100-010
    
    SPC-I
             1-253-5
             2-254-6
             3-255-7
             4-100-1
    
    SPC-N
            10-01-11-1
            13-02-12-0
            14-15-12-1
    
    SPC-N24
    
    none
    
    Secondary Point Code table is (11 of 40) 28% full
    

11. 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.
    

1. Display the secondary point codes in the database, using the rtrv-spc command. This is an example of the possible output.

   
   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   SPC (Secondary Point Codes)
   
   SPCA
        001-010-010
        002-010-010
        003-010-010
        010-100-010
   
   SPC-I
            1-253-5
            2-254-6
            3-255-7
            4-100-1
   
   SPC-N
           10-01-11-1
           13-02-12-0
           14-15-12-1
   
   SPC-N24
   
   none
   
   Secondary Point Code table is (11 of 40) 28% full
   

2. Display the destination point codes that reference the secondary point code being removed from the database using the rtrv-dstn command with either the spca, spci, or spcn parameters.

   For this example, enter this command.

   rtrv-dstn:spca=010-100-010

   This is an example of the possible output.

   
   rlghncxa03w 09-05-17 16:02:05 GMT  EAGLE5 41.0.0
   
   SPCA   =    010-100-010
   
      DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3     SS7
   
      240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
   
   Destination table is (16 of 2000) 1% full 
   Alias table is (9 of 8000) 1% full
   RTRV-DSTN: MASP A - COMPLTD
   

   • If no DPCs are shown in this step, skip step 3 and go to step 4.
   • If DPCs are shown in this step, continue the procedure with step 3.
3. Remove the reference to the secondary point code using the chg-dstn command and specifying the destination point codes shown in step 2 with either the dpca, dpci, or dpcn parameters, and with either the spca=none, spci=none, or spcn=none parameters, depending on the type of point codes being used. For this example, enter these commands.

   chg-dstn:dpca=240-012-004:spca=none

   chg-dstn:dpca=240-012-005:spca=none

   When this command has successfully completed, and the cluster routing and management diversity feature is turned off (CRMD = off in the rtrv-feat command output), this message should appear.

   
   rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
   Destination table is (16 of 2000) 1% full
   CHG-DSTN: MASP A - COMPLTD
   

   If the cluster routing and management diversity feature is turned on (CRMD = on in the rtrv-feat command output), this message should appear when each command has successfully completed.

   
   rlghncxa03w 07-5-17 15:35:05 GMT EAGLE5 37.0.0
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   14
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  16
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                   8
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   CHG-DSTN: MASP A - COMPLTD
   

   After this step has been performed,.skip steps 4 and 5 and go to step 6.

4. Display the status of the Multiple Linksets to Single APC feature by entering this command.

   rtrv-ctrl-feat:partnum=893019701

   This is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   Multiple Linkset to APC   893019701  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 Multiple Linksets to Single APC feature is enabled and turned on, continue the procedure with step 5.

   If the Multiple Linksets to Single APC feature is not enabled or turned on, skip step 5 and go to step 6.

5. Display the linksets that reference the secondary point code that is being removed by entering the rtrv-ls command with the secondary point code value.

   For this example, enter this command.

   rtrv-ls:spca=010-100-010

   This is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   
   SPCA   =    010-100-010
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn1          002-002-002   none 1   1   no  A   2    off off off no    off
   lsn2          003-003-003   none 1   1   no  A   3    off off off no    off
   
   
   Link set table is (12 of 1024) 1% full.

   If linksets are shown in this step, these linksets must be removed before the secondary point code can be removed. Perform the Removing a Linkset Containing SS7 Signaling Links procedure to remove the linksets. After the linksets have been removed, continue the procedure with step 6.

   If no linksets are shown in this step, continue the procedure with step 6.

6. Remove the secondary point code, using the dlt-spc command. For this example, enter this command.

   dlt-spc:spca=010-100-010

   When this command has successfully completed, this is an example of the message that should appear.

   
   rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
   Destination table is (10 of 40) 25% full
   DLT-SPC: MASP A - COMPLTD
   

7. Verify the changes using the rtrv-spc command specifying the secondary point code specified in step 6.

   For this example, enter this command.

   rtrv-spc:spca=010-100-010

   When this command has successfully completed, this is an example of the message that should appear.

   
   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   SPC (Secondary Point Codes)
   
   Secondary Point Code specified is not provisioned
   
   Secondary Point Code table is (10 of 40) 25% full
   

8. 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.
   

1. Display the self-identification of the EAGLE using the rtrv-sid command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-10 11:43:04 GMT  EAGLE5 37.0.0
      PCA             PCI          PCN                CLLI              PCTYPE
      001-001-001     1-200-6      10-13-9-3          rlghncxa03w       OTHER
   
      CPCA
      002-002-002       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
      CPCA (LNP)
      005-005-002       005-005-004       005-005-005
   
      CPCI
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
     
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1
   

   If the network type of the point code being added in this procedure matches the network types of the point codes shown in the PCA, PCI, PCN, or PCN24 columns, this procedure cannot be performed. Perform the Changing the Self-Identification of the EAGLE procedure to change the point codes shown in these columns.

   Note:

   If an ITU-I or 14-bit ITU-N spare point code is displayed in the rtrv-sid output in step 1, or if an ITU-I or 14-bit ITU-N spare point code is not being added in this procedure, skip step 2 and go to step 3.
2. Verify whether or not the ITU National and International Spare Point Code Support feature is enabled by entering the rtrv-ctrl-featcommand with the part number of this feature.

   Enter this command.

   rtrv-ctrl-feat:partnum=893013601

   This is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.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 to enable the ITU National and International Spare Point Code Support feature.

   Note:

   If the pcn parameter is not being used in this procedure, skip this step and step 4, and go to step 5.
3. Display the existing values for the npcfmti parameter, by entering the rtrv-stpopts command.

   The value for the npcfmti parameter is shown in the NPCFMTI field. This is an example of the possible output.

   
   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   STP OPTIONS
   -----------------------
   NPCFMTI        4-4-4-2
   

   Note:

   The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in Commands User's Guide.

   Note:

   If the rtrv-sid output in step 1 shows group codes assigned to the 14-bit ITU-N point codes, then a group code must be assigned to the pcn parameter value specified in this procedure. This group code must be shown in either the rtrv-sid output or the rtrv-spc output. If the group code being assigned to the pcn parameter value is shown in the rtrv-sid output, skip step 4 and go to step 5.
4. Display the secondary point codes in the database, using the rtrv-spc command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
   SPC (Secondary Point Codes)
   
   SPCA
        001-010-010
        002-010-010
        003-010-010
        010-100-010
   
   SPC-I
            1-253-5
            2-254-6
            3-255-7
            4-100-1
   
   SPC-N
           10-01-11-1
           13-02-12-0
           14-15-12-1
   
   SPC-N24
   
   none
   

5. Verify whether or not the point code being added in this procedure is a DPC value in the DPC table by entering the rtrv-dstn command and specifying the point code value that is being added in this procedure. For this example, enter these commands.

   rtrv-dstn:dpci=s-3-75-7

   rtrv-dstn:dpcn=s-7-9-8-1

   When each of these commands have been executed, the following output is displayed showing that the specified point code is not in the DPC table.

   
   rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
   
   No destinations meeting the requested criteria were found
   
   Destination table is (22 of 2000) 1% full
   Alias table is (18 of 8000) 1% full
   

6. Verify whether or not the point code being added in this procedure is an alias point code in the DPC table by entering the rtrv-dstn command and specifying the point code value that is being added in this procedure. For this example, enter these commands.

   rtrv-dstn:aliasi=s-3-75-7

   rtrv-dstn:aliasn=s-7-9-8-1

   When each of these commands have been executed, the following output is displayed showing that the specified point code is not an alias point code in the DPC table.

   
   rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
   
   No destinations meeting the requested criteria were found
   
   Destination table is (22 of 2000) 1% full
   Alias table is (18 of 8000) 1% full
   

   If the point code specified in steps 5 and 6 is shown in the DPC table, choose another point code to add to the self-identification and repeat steps 5 and 6.

   If the point code specified in steps 5 and 6 is not shown in the DPC table, go to step 7.

7. Add the point code to the self-identification of the EAGLE using the ent-sid command with the pca, pci, pcn, or pcn24 parameters and according to these rules.
   • If the pcn parameter is specified with the ent-sid command, the pcn24 parameter cannot be specified.

   • If the pcn24 parameter is specified with the ent-sid command, the pcn parameter cannot be specified.

   • For pcn parameter values, the format of the point code must match the format defined by the NPCFMTI parameter of the rtrv-stpopts output. If group codes are shown in the rtrv-sid output in step 1, a group code must be assigned to the pcn parameter value being added in this procedure. This group code must be shown either in the rtrv-sid or rtrv-spc output.

   • The point code values must be full point codes.

   • The ITU National and International Spare Point Code Support feature must be enabled to specify an ITU-I or 14-bit ITU-N spare point code.

   • The point code specified in this procedure cannot be defined as a capability point code.

   • See "ANSI Point Codes" in the Point Code Formats section for information about entering ANSI point codes.

   For this example, enter this command.

   ent-sid:pci=s-3-75-7:pcn=s-7-9-8-1

   When this command has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-07 09:17:40 GMT  EAGLE5 37.0.0
   ENT-SID: MASP A - COMPLTD
   

8. Verify the changes using the rtrv-sid command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-10 11:43:04 GMT  EAGLE5 37.0.0
      PCA             PCI          PCN                CLLI              PCTYPE
      001-001-001     1-200-6      10-13-9-3          rlghncxa03w       OTHER
                    s-3-75-7     s-7-9-8-1
      CPCA
      002-002-002       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
   
      CPCA (LNP)
      005-005-002       005-005-004       005-005-005      006-006-006
   
      CPCI
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
   
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1
   

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.
   

1. Display the self-identification of the EAGLE using the rtrv-sid command.

   This is an example of the possible output.

   
   rlghncxa03w 08-09-10 11:43:04 GMT  EAGLE5 39.2.0
      PCA             PCI          PCN                CLLI              PCTYPE
      001-001-001     1-200-6      10-13-9-3          rlghncxa03w       OTHER
   
      CPCA
      002-002-002       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
   
      CPCA (LNP)
      005-005-002       005-005-004       005-005-005
   
      CPCI
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
   
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1
   

   Continue the procedure by performing one of these steps.

   • If only the CLLI or CLLI and PCTYPE values are being changed, continue the procedure with 11.
   • If only the PCTYPE value is being changed, continue the procedure with 19.
   • If point codes will be specified in this procedure, continue the procedure by performing one of these steps.
     • If 14-bit or 24-bit ITU-N point codes will be specified, continue the procedure with 2.
     • If 14-bit or 24-bit ITU-N point codes will not be specified, continue the procedure with 5.
2. If you wish to specify the pcn24 parameter with the chg-sid command and the rtrv-sid output shows the PCN field, the 14-bit ITU-N point code value, shown in the PCN field must be removed with the npcn=none parameter before the pcn24 parameter value can be specified by the chg-sid command.

   Before the npcn=none parameter can be specified, any ITU-N point codes shown in the rtrv-dstn output must be removed. If no value is shown in the PCN field, then performing this step is not necessary. If the PCN field contains a point code, perform the Removing a Destination Point Code procedure to remove the ITU-N point codes. After the ITU-N point codes have been removed, enter this command.

   chg-sid:pcn=<current PCN value>:npcn=none

   If the PCN field contains both spare and non-spare point code values, both the spare and non-spare 14-bit ITU-N point code values must be removed from the rtrv-dstn and rtrv-sid outputs before the pcn24 parameter can be specified.

   After the PCN value has been removed, continue the procedure with 6.

   If you wish to specify the pcn parameter with the chg-sid command and the rtrv-sid output shows the PCN24 field, the 24-bit ITU-N point code value, shown in the PCN24 field must be removed with the pcn24=none parameter before the pcn parameter value can be specified by the chg-sid command.

   Before the pcn24=none parameter can be specified, any ITU-N24 point codes shown in the rtrv-dstn output must be removed. If no value is shown in the PCN24 field, then performing this step is not necessary. If the PCN24 field contains a point code, perform the Removing a Destination Point Code procedure to remove the ITU-N24 point codes. After the ITU-N24 point codes have been removed, enter this command.

   chg-sid:pcn24=none

   After the PCN24 value has been removed, continue the procedure with 3.

   When the chg-sid command has successfully completed, this message should appear.

   
   rlghncxa03w 06-05-07 09:17:40 GMT  EAGLE5 39.2.0
   CHG-SID: MASP A - COMPLTD
   

   A caution message is displayed indicating that the EAGLE needs to be reinitialized.

   
   CAUTION: SYSTEM SITE ID HAS BEEN CHANGED, MANUAL RE-INITIALIZATION IS NEEDED
   

3. Display the existing values for the npcfmti parameter, by entering the rtrv-stpopts command.

   The value for the npcfmtiparameter is shown in the NPCFMTI field. This is an example of the possible output.

   
   rlghncxa03w 08-09-17 16:02:05 GMT  EAGLE5 39.2.0
   STP OPTIONS
   -----------------------
   NPCFMTI        4-4-4-2
   

   Note:

   The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in Commands User's Guide.

   If you wish to change the format of the 14-bit ITU national point codes, go to the 14-Bit ITU National Point Code Formats section. Changing the formats of the 14-bit ITU national point codes will change how any existing 14-bit ITU national point codes are displayed in the database.

   After this step has been performed, continue the procedure by performing one of these steps.

   • If group codes are shown in the rtrv-sid output, continue the procedure with 5.
   • If group codes are not shown in the rtrv-sid output, and group codes will not be specified with the 14-bit ITU-N point codes, continue the procedure with 5.
   • If group codes are not shown in the rtrv-sid output, and group codes will be specified with the 14-bit ITU-N point codes, continue the procedure with 4.
4. Enter the rtrv-feat command to verify that the Multiple Point Code Support and ITU Duplicate Point Code Support features are on.

   If the Multiple Point Code Support feature is on, the MPC field should be set to on. If the ITU Duplicate Point CodeSupport feature is on, the ITUDUPPC field should be set to on. For this example, these features are off.

   Note:

   The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in Commands User's Guide.

   If the ITU Duplicate Point Code Support feature is off and the Multiple Point Code feature is on, enter this command.

   chg-feat:ituduppc=on
   If both features are off, enter this command.
   chg-feat:mpc=on:ituduppc=on

   When the chg-feat has successfully completed, this message should appear.

   
   rlghncxa03w 08-09-07 00:57:31 GMT EAGLE5 39.2.0
   CHG-FEAT: MASP A - COMPLTD
   

5. If spare point codes are being specified in this procedure, the ITU National and International Spare Point Code Support feature must be enabled.

   Note:

   If an ITU-I or 14-bit ITU-Nspare point code is displayed in the rtrv-sid output in 1, or if an ITU-I or 14-bit ITU-N spare point code is not being specified in this procedure, continue the procedure with 6. The rtrv-ctrl-feat command shows the status of the ITU National and International Spare Point Code Support feature.

   Enter the rtrv-ctrl-feat command with the part number of this feature.

   Enter this command.

   rtrv-ctrl-feat:partnum=893013601

   This is an example of the possible output.

   
   rlghncxa03w 08-09-28 21:15:37 GMT EAGLE5 39.2.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 to enable the ITU National and International Spare Point Code Support feature.

6. The point codes specified in this procedure cannot be shown in the rtrv-dstn command output.

   Display the point codes in the destination point code table by using the rtrv-dstn 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          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      001-002-003   ls04clli    yes --- ----------      --------------   SS7
      002-002-002   ls01clli    no  --- ----------      --------------   SS7
      002-007-008   ls06clli    yes --- ----------      --------------   SS7
      003-003-003   ls03clli    yes --- ----------      --------------   SS7
      004-004-004   ls02clli    yes --- ----------      --------------   SS7
      179-100-087   ----------- yes --- ----------      --------------   SS7
      200-050-176   ----------- yes --- ----------      --------------   SS7
      240-007-000   ----------- yes --- ----------      --------------   SS7
      240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3     SS7
      240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
      240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1    SS7
      240-012-008   ----------- yes ---    1-113-5         10-13-10-2    SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
      2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1     SS7
      2-131-2       ----------- no  ---    222-211-001     11-11-8-2     SS7
      2-131-3       ----------- no  ---    222-211-002     11-11-8-3     SS7
      3-150-4       lsi7clli    yes --- --------------  --------------   SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
      10-6-15-1     lsn5clli    yes --- --------------  ----------       SS7
      10-15-2-3     rlghncbb013 no  ---    222-200-200     2-121-1       SS7
      10-15-3-0     rlghncbb013 no  ---    222-200-201     2-121-2       SS7
      
   Destination table is (19 of 2000) 1% full
   Alias table is (18 of 8000) 1% full
   

   Continue the procedure by performing one of these steps.

   • If the pc/pca/pci/pcn/pcn24 parameter value is not being changed, continue the procedure with 10.
   • If the pc/pca/pci/pcn/pcn24 parameter value is being changed to another point code value, continue the procedure with 9.
   • If the pc/pca/pci/pcn/pcn24 parameter value is being removed, continue the procedure with 8.
7. The point codes specified in this procedure cannot be shown in the rtrv-pct output as an emulated point code (EPC). Display the PCT entries by entering the rtrv-pct command.

   This is an example of the possible output.

   
   rlghncxa03w 10-12-17 16:02:05 GMT  EAGLE5 43.0.0
   
       EPCA             FILTPCA          REALPCA      SI  SSN  RELCAUSE
       001-001-001      *                240-012-006   5  ---  10
   
       ECICS = 10          ECICE = 20
       RCICS = 30          RCICE = 40
   
       EPCI             FILTPCI          REALPCI      SI  SSN  RELCAUSE
       1-001-2          2-131-2          2-131-3       3   10  ---
   
       ECICS = ----------  ECICE = ----------
       RCICS = ----------  RCICE = ----------
   
       EPCN             FILTPCN          REALPCN      SI  SSN  RELCAUSE
       13-11-14-1       *                10-15-2-3     *  ---  ---
   
       ECICS = ----------  ECICE = ----------
       RCICS = ----------  RCICE = ----------
   
   
    Unique EPC    is 3 of 250
    Unique RealPC is 3 of 250
   
   PCT table is (3 of 1000) 1% full.
   

   Continue the procedure by performing one of these steps.

   • If the pc/pca/pci/pcn/pcn24 parameter value is not being changed, continue the procedure with 10.
   • If the pc/pca/pci/pcn/pcn24 parameter value is being changed to another point code value, continue the procedure with 9.
   • If the pc/pca/pci/pcn/pcn24 parameter value is being removed, continue the procedure with 8.
8. For the EAGLE to have point codes of a particular network type (ANSI, ITU-I, or ITU-N), a point code of that same type must be defined by the pc/pca/pci/pcn/pcn24 parameter of the chg-sid command.

   To remove a point code defined by the pc/pca/pci/pcn/pcn24parameter, all point codes of the same network type as the point code being removed in this procedure must be removed from the database.

   If the rtrv-dstn output in 6 shows that there are no point codes of the same network type as the point code being removed, continue the procedure with 11.

   If the rtrv-dstn output in 6 shows that there are point codes of the same network type as the point code being removed, perform the Removing a Destination Point Code procedure and remove the point codes shown in the rtrv-dstn output in 6 that are the same network type as the point code being removed in this procedure.

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

9. Display the mated applications in the database, using the rtrv-map command.

   This is an example of the possible output.

   
   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
      PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
      255-001-000               250 10  SOL *N  *N  GRP01    ON
   
      255-001-000               251 10  SHR *Y  *Y  GRP01    OFF
                   253-001-002  254 10  SHR *Y  *Y  GRP01    OFF
   
      255-001-000               252 10  SOL *Y  *Y  GRP01    ON
   
      255-001-000               253 10  SHR *N  *N  GRP01    OFF
                   253-001-004  254 10  SHR *N  *N  GRP01    OFF
   
      255-001-001               255 10  DOM YES YES GRP01    ON
                   253-001-005  254 20  DOM YES YES GRP01    ON
   
      255-001-001               250 10  DOM YES YES GRP01    OFF
                   253-001-001  254 20  DOM YES YES GRP01    OFF
   
      255-001-002               251 10  SHR *Y  *Y  GRP01    OFF
                   255-001-002  254 10  SHR *Y  *Y  GRP01    OFF
   
      255-001-002               252 10  DOM YES YES GRP01    ON
                   255-001-003  254 20  DOM YES YES GRP01    ON
   
      255-001-002               253 10  SHR *Y  *Y  GRP01    ON
                   255-001-004  254 10  SHR *Y  *Y  GRP01    ON
   
   
   PCI             Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
   2-001-2                      255 10  DOM NO  NO  GRP03    OFF
                   2-001-1      254 20  DOM NO  NO  GRP03    OFF
   
   
   PCN             Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
   0-5-6-3                      253 10  SHR NO  *Y  GRP05    OFF
                   1-5-10-3     254 10  SHR NO  *N  GRP05    OFF
   
   MAP TABLE IS (20 of 1024)  2 % FULL
   

   If the EAGLE’s point code is shown in the rtrv-map command output (in the PCA, PCI, PCN, PCN24, MPCA, MPCI, MCPN, or MPCN24 fields), perform the Removing a Mated Application procedure in the Database Administration - GTT User's Guide, and remove the EAGLE’s point code from the mated application table.

10. Display the secondary point codes in the database, using the rtrv-spc command.

    This is an example of the possible output.

    
    rlghncxa03w 08-09-07 11:43:04 GMT  EAGLE5 39.2.0
    SPC (Secondary Point Codes)
    SPCA
         001-010-010
         002-010-010
         003-010-010
         010-100-010
    SPC-I
             1-253-5
             2-254-6
             3-255-7
             4-100-1
    SPC-N
            10-01-11-1
            13-02-12-0
            14-15-12-1
    SPC-N24
    none
    Secondary Point Code table is (11 of 40) 28% full
    

    If the EAGLE’s point code or capability point code that is being configured in this procedure is shown in 6 or 10, choose another point code to configure with this procedure.

    Continue the procedure by performing one of these steps.

    • If the clli parameter value is not being changed, continue the procedure with 15.
    • If the clli parameter value is being changed, continue the procedure with 11.
11. Enter the rtrv-feat command, or examine the rtrv-feat output in 4, if 4 was performed, to verify that the Eagle Support for Integrated Sentinel feature is on.

    If the Eagle Support for Integrated Sentinel feature is on, the E5IS field should be set to on.

    Note:

    The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in Commands User's Guide.

    Continue the procedure by performing one of these steps.

    • If the Eagle Support for Integrated Sentinel feature is not on, continue the procedure with 15.
    • If the Eagle Support for Integrated Sentinel feature is on, continue the procedure with 12.
12. Display the EISCOPY option by entering the rtrv-eisopts command.

    This is an example of the possible output.

    
    rlghncxa03w 10-07-07 11:43:04 GMT  EAGLE5 42.0.0
    EIS OPTIONS
    ------------------
    EISCOPY = ON
    
    FAST COPY OPTIONS
    --------------------------------
    FCGPL = IPSG      FCMODE = FCOPY
    FCGPL = IPGHC     FCMODE = FCOPY
    --------------------------------
    

    Continue the procedure by performing one of these steps.

    • If the EISCOPY option is off, continue the procedure with 15.
    • If the EISCOPY option is on, continue the procedure by performing one of these steps..
      • If the FCMODE value for all the GPLs shown in the rtrv-eisopts output is OFF, continue the procedure with 15.
      • If the FCMODE value for any of the GPLs shown in the rtrv-eisopts output is STC or FCOPY, continue the procedure with 13.
13. Change the FCMODE values for all the GPLs shown in 12 to OFF by entering this command.

    chg-eisopts:fcmode=off:fcgpl=all

    When the chg-eisopts has successfully completed, this message should appear.

    
    rlghncxa03w 10-07-07 11:43:04 GMT  EAGLE5 42.0.0
    CHG-EISOPTS: MASP A - COMPLTD
    

14. Turn the EISCOPY option off by entering the chg-eisopts command with the eiscopy=off parameter.

    Caution:

    Changing the EISCOPY option to off will disable the Eagle Support for Integrated Sentinel feature.

    When the chg-eisopts has successfully completed, this message should appear.

    
    rlghncxa03w 08-09-07 11:43:04 GMT  EAGLE5 39.2.0
    CHG-EISOPTS: MASP A - COMPLTD
    

    Continue the procedure by performing one of these steps.

    • If capability point codes will not be provisioned in this procedure, continue the procedure with 19.
    • If capability point codes will be provisioned in this procedure, continue the procedure with 15.
15. To add a particular type of CPC, only one CPC type (the cpctype parameter) can be specified with the chg-sid command, and the feature corresponding to the CPC type must be enabled or turned on.
    The EAGLE supports these types of CPCs.

    • STP CPCs - no feature is required to be enabled or turned on to specify STP CPCs. If you wish to add an STP CPC, continue the procedure with 19.
    • LNPCPCs - If you wish to add an LNP CPC and LNP CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If only STP CPCs are shown in the rtrv-sid output in 1, continue the procedure with 18. If any of these CPCs are shown in the rtrv-sid output in 1: INP, G-Port, G-Flex, EIR, MNP, V-Flex, ATINPQ, LNP CPCs cannot be added.
    • INP CPCs - If you wish to add an INP CPC and INP CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If INP and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16. If LNP CPCs are shown in the rtrv-sid output in 1, INP CPCs cannot be added.
    • G-Flex CPCs - If you wish to add a G-Flex CPC and G-Flex CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If G-Flex and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16. If LNP CPCs are shown in the rtrv-sid output in 1, G-Flex CPCs cannot be added.
    • MNP CPCs - If you wish to add an MNP CPC and MNP CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If MNP and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16. If LNP CPCs are shown in the rtrv-sid output in 1, MNP CPCs cannot be added.
    • EIR CPCs - If you wish to add an EIR CPC and EIR CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If EIR and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16. If LNP CPCs are shown in the rtrv-sid output in 1, EIR CPCs cannot be added.
    • V-Flex CPCs - If you wish to add a V-Flex CPC and V-Flex CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If V-Flex and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16. If LNP CPCs are shown in the rtrv-sid output in 1, V-Flex CPCs cannot be added.
    • ATINPQ CPCs - If you wish to add an ATINPQ CPC and ATINPQ CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If ATINPQ and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16. If LNP CPCs are shown in the rtrv-sid output in 1, ATINPQ CPCs cannot be added.
    • G-Port CPCs - If you wish to add a G-Port CPC and G-Port CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If G-Port, MNP, and LNP CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 17. If LNP or MNP CPCs are shown in the rtrv-sid output in 1, G-Port CPCs cannot be added.
    • AIQ CPCs - If you wish to add an AIQ CPC and AIQ CPCs are shown in the rtrv-sid output in 1, continue the procedure with 19. If AIQ CPCs are not shown in the rtrv-sid output in 1, continue the procedure with 16.
16. To specify these types of CPCs: INP, G-Flex, MNP, EIR, V-Flex, ATINPQ, AIQ, the following features must be enabled, and turned on if necessary.
    • INP CPCs - the INP or ANSI-41 INP Query features must be enabled and turned on.
    • G-Flex CPCs - the G-Flex feature must be enabled and turned on.
    • EIR CPCs - the EIR feature must be enabled and turned on.
    • MNP CPCs - the A-Port or IS41 GSM Migration features must be enabled.
    • V-Flex CPCs - the V-Flex feature must be enabled and turned on.
    • ATINPQ CPCs - the ATINP feature must be enabled.
    • AIQ CPCs - the ANSI41 AIQ feature must be enabled.

    Enter the rtrv-ctrl-feat command to verify the status of the feature required for the CPC that is being added. This is an example of the possible output.

    
    rlghncxa03w 08-09-28 21:15:37 GMT EAGLE5 39.2.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Command Class Management  893005801  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    XGTT Table Expansion      893006101  on      4000000
    XMAP Table Expansion      893007710  on      3000
    Large System # Links      893005901  on      1500
    Routesets                 893006401  on      6000
    HC-MIM SLK Capacity       893012707  on      64
    
    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 LNP feature is enabled, LNP, AIQ, or STP CPCs can be specified in this procedure. If an AIQ CPC will be provisioned, continue with this step. If an LNP or STP CPC will be provisioned, continue the procedure with 19.

    If the feature that is required for the CPC that is being added is enabled, and turned on if required, continue the procedure with 19.

    If the feature that is required for the CPC that is being added is not enabled, or turned on if required, perform the procedures in one of the following manuals to enable, and turn on if required, the feature required to support the CPC that is being added.

    • INP CPCs - INP/AINPQ User's Guide – to enable and turn on the INP or ANSI-41 INP Query features.
    • G-Flex CPCs - G-Flex User's Guide – to enable and turn on the G-Flex feature.
    • EIR CPCs - EIR User's Guide – to enable and turn on the EIR feature.
    • MNP CPCs - A-Port User's Guide to enable the A-Port feature, or IS41 GSM Migration User's Guide – to enable the IS41 GSM Migration feature.

      Note:

      If G-Port CPCs are shown in the rtrv-sid output, when the A-Port or IS41 GSM Migration features are enabled, the G-Port CPCs are changed to MNP CPCs.
    • V-Flex CPCs - V-Flex User's Guide – to enable and turn on the V-Flex Feature.
    • ATINPQ CPCs - ATINP User's Guide – to enable the ATINP feature.
    • AIQ CPCs - Analyzed Information Features User's Guide – to enable the ANSI41 AIQ feature.

    After the required feature has been enabled, and turned on if required, continue the procedure with 19.

17. To provision G-Port CPCs, the G-Port feature must be enabled. Verify that the G-Port feature is enabled by entering the rtrv-ctrl-feat command. This is an example of the possible output.

    
    rlghncxa03w 08-09-28 21:15:37 GMT EAGLE5 39.2.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Command Class Management  893005801  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    XGTT Table Expansion      893006101  on      4000000
    XMAP Table Expansion      893007710  on      3000
    Large System # Links      893005901  on      1500
    Routesets                 893006401  on      6000
    HC-MIM SLK Capacity       893012707  on      64
    
    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 G-Port feature is enabled, continue the procedure with 19.

    If the G-Port feature is not enabled, perform the procedures in the G-Port User's Guide to enable the G-Port feature. After the G-Port feature has been enabled, continue the procedure with 19.

    If the LNP feature is enabled, LNP, AIQ, or STP CPCs can be specified in this procedure. If an AIQ CPC will be provisioned, continue the procedure with 16. If an LNP or STP CPC will be provisioned, continue the procedure with 19.

    If either the A-Port or IS41 GSM Migration features are enabled, G-Port CPCs cannot be provisioned. If you wish to provision other types of CPCs, go back to 15 and select another type of CPC to provision. If you do not wish to provision other CPCs, continue the procedure with 19 to provision the self identification without provisioning CPCs.

18. To provision LNP CPCs, the LNP feature must be enabled. Verify that the LNP feature is enabled by entering the rtrv-ctrl-feat command. This is an example of the possible output.

    
    rlghncxa03w 08-09-28 21:15:37 GMT EAGLE5 39.2.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Command Class Management  893005801  on      ----
    LNP Short Message Service 893006601  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    XGTT Table Expansion      893006101  on      4000000
    XMAP Table Expansion      893007710  on      3000
    Large System # Links      893005901  on      1500
    Routesets                 893006401  on      6000
    HC-MIM SLK Capacity       893012707  on      64
    
    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 LNP feature is enabled, continue the procedure with 19.

    If the LNP feature is not enabled and none of the features shown in 16 or 17 are enabled, except ANSI41 AIQ, and turned on if required, perform the procedures in ELAP Administration and LNP Feature Activation User's Guide to enable the LNP feature. After the LNP feature has been enabled, continue the procedure with 19. AIQ CPCs can be provisioned regardless of which features are enabled or turned on. The ANSI41 AIQ feature must be enabled to provision AIQ CPCs.

    If any of the features shown in 16 or 17 are enabled, and turned on if required, except ANSI41 AIQ, LNP CPCs cannot be specified. If you wish to provision CPCs for the features that are enabled, and turned on if required, go back to 15 and select another type of CPC to provision. If you do not wish to provision other CPCs, continue the procedure with 19 to provision the self identification without provisioning CPCs.

19. Change the value of the self-identification of the EAGLE, using the chg-sid command.

    For this example, the point code of the EAGLE is being changed to these values:

    • ANSI point code = 100-100-100
    • ITU international point code = 3-75-7
    • ITU national point code = 7-9-8-1
    • LNP capability point code = 006-006-006

    To make these changes, enter this command.

    chg-sid:pca=100-100-100:pci=3-75-7:pcn=7-9-8-1 :cpca=006-006-006:cpctype=lnp

    If you wish to configure network routing point codes using the network indicator values 1 through 5, the pctype parameter value must be other. For more information on network routing point codes, see the Network Routing section.

    When this command has successfully completed, this message should appear.

    
    rlghncxa03w 08-09-07 09:17:40 GMT  EAGLE5 39.2.0
    CHG-SID: MASP A - COMPLTD
    

    If any of the pc/pca/pci/pcn/pcn24 parameters are changed, the EAGLE needs to be reinitialized. A caution message is displayed indicating that the EAGLE needs to be reinitialized.

    
    CAUTION: SYSTEM SITE ID HAS BEEN CHANGED, MANUAL RE-INITIALIZATION IS NEEDED
    

    If the CLLI value has been changed, and the SEAS over IP feature is enabled and turned on, shown in the rtrv-ctrl-feat output, this caution messages appears.

    
    CAUTION: System CLLI has changed, CCSMR re-configuration required
    

    If the gateway screening redirect function's DPC is the pc/pca/pci/pcn/pcn24 parameter value and this parameter value was changed in this step, this caution message appears.

    
    CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC
    

    Continue the procedure by performing one of these steps.

    • If the pc/pca/pci/pcn/pcn24 and clli parameters were not changed, continue the procedure with 27.
    • If the clli parameter was changed, but the pc/pca/pci/pcn/pcn24 was not changed, continue the procedure by performing one of these steps.
      • If this caution message, CAUTION: System CLLI has changed, CCSMR re-configuration required, appeared after the chg-sid command was performed, continue the procedure with 23.
      • If the caution message did not appear after the chg-sid command was performed, continue the procedure with one of these steps.
        • If the EISCOPY option was changed in 14, continue the procedure with 24.
        • If the EISCOPY option was not changed in 14, continue the procedure with 27.
    • If the pc/pca/pci/pcn/pcn24 parameter was changed, continue the procedure by performing one of these steps.
      • If you wish to change the RSTRDEV STP option, continue the procedure with 20.
      • If you do not wish to change the RSTRDEV STP option, continue the procedure with 21.
20. Enter the rtrv-stpopts command to display the setting of the rstrdev parameter.

    21 instructs you to enter the init-sys command.

    If you do not want the EAGLE to restore previous device states after the init-sys command has executed and RSTRDEV value is on in the rtrv-stpopts output, enter the chg-stpopts:off=rstrdev command.

    If you want the EAGLE to restore previous device states after the init-sys command has executed, and RSTRDEV value is off in the rtrv-stpopts output, enter the chg-stpopts:on=rstrdev command.

    Continue with 21.

    Caution:

    The init-sys command causes a complete EAGLE reload, and should only be used during periods of low traffic. Using this command ensures the updated self-identification information is loaded onto all cards, but will interrupt service.

    Caution:

    The rstrdev value of the chg-stpopts command can be used to turn on the Persistent Device States (PDS) feature. When PDS is turned off and the init-sys command executes, the EAGLE does not retain the manually initiated state (for example, OOS-MT-DSBLD) for the signaling links, cards, or terminals. After the command executes, the EAGLE attempts to bring all provisioned signaling links, cards, and terminals on-line, including those that were previously out of service. You will need to manually put each device back into its previous state after the EAGLE is back on-line. It is, therefore, advisable to print or electronically capture the output of the rept-stat-slk, rept-stat-card, and rept-stat-trm commands for reference prior to issuing theinit-sys command. To restore a device to its previous state, issue the appropriate inhibit/deactivate command listed in Commands User's Guide in the Related Commands section for each of the above rept-stat commands. When PDS is turned on using the chg-stpopts:on=rstrdev command, the EAGLE restores the previous device states of signaling links, terminals, and cards after the init-sys command has executed.
21. Reinitialize the EAGLE by entering the init-sys command.

    Note:

    Th einit-sys command must be entered twice within 30 seconds for the EAGLE to be re-initialized. If the init-sys command is not executed twice within 30 seconds, the attempt to re-initialize the EAGLE is aborted.

    When the init-sys command is first entered, this message should appear.

    
    rlghncxa03w 08-09-28  07:05:01 GMT  EAGLE5 39.2.0
    CAUTION: This command causes a complete system reload, and
    will result in traffic loss.
    Re-enter command within 30 seconds to confirm.
    

    When the init-sys command is re-entered within the 30 second time limit, this message should appear.

    
    rlghncxa03w 08-09-28  07:05:17 GMT  EAGLE5 39.2.0
    Init System command issued at terminal #3
    

    From the time that the init-sys command is accepted, you must wait approximately two minutes before you can perform 22 (logging onto the EAGLE). If the EAGLE terminal is in the VT-100/VT-320 mode, the terminal display will be refreshed with non-zero alarm counts. During this 2-minute interval, an intermediate screen refresh is caused by the MASPs role change from active to standby, and from standby to active. This screen refresh is typically a partial refresh, and the alarm indicators are set to zero.

    If you are logged into the EAGLE in the KSR mode, the only response you will receive indicating that you are now able to log into the EAGLE is UAM 0009, MASP became active. UAM 0009 could be issued twice due to possible transient MASP role change (switching from active to standby).

    Following the execution of the init-sys command, the MASP that was active before the init-sys command was entered will be the active MASP when the EAGLE has finished reinitializing.

22. Log into the EAGLE using the login command (or the act-user command).

    This is an example of the messages that appear when the login session has successfully completed.

    
    NOTICE: This is a private computer system. 
    Unauthorized access or use may lead to prosecution. 
    0 LOGIN failures since last successful LOGIN
    Last successful LOGIN was on port 4 on 04-06-02 @ 09:34:56
    

    If the clli parameter was not changed in 19, continue the procedure by performing one of these steps.

    • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was displayed in 19, continue the procedure with 26.
    • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was not displayed in 19, continue the procedure with 27.

    If this caution message, CAUTION: System CLLI has changed, CCSMR re-configuration required, appeared in 19, continue the procedure with 23. If the caution message did not appear in 19, continue the procedure by performing one of these steps.

    • If the EISCOPY option was changed in 14, continue the procedure with 24.
    • If the EISCOPY option was not changed in 14, continue the procedure by performing one of these steps.
      • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was displayed in 19, continue the procedure with 26.
      • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was not displayed in 19, continue the procedure with 27.
23. Perform the procedures in the "SEAS Over IP Configuration Procedures" chapter in Database Administration - System Management User's Guide to re-configure the CCSMRs with the new CLLI information.
    After the CCSMRs have been re-configured, continue the procedure by performing one of these steps.

    • If the EISCOPY option was changed in 14, continue the procedure with 24.
    • If the EISCOPY option was not changed in 14, continue the procedure by performing one of these steps.
      • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was displayed in 19, continue the procedure with 26.
      • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was not displayed in 19, continue the procedure with 27.
24. Turn the EISCOPY option on by entering the chg-eisopts command with the eiscopy=on parameter.

    Caution:

    The Eagle Support for theIntegrated Sentinel feature will be disabled if this step is not performed.

    When the chg-eisopts has successfully completed, this message should appear.

    
    rlghncxa03w 08-09-28  07:05:01 GMT  EAGLE5 39.2.0
    CHG-EISOPTS: MASP A - COMPLTD
    

    After the EISCOPY option has been changed, continue the procedure by performing one of these steps.

    • If the FCMODE value was changed in 13, continue the procedure with 25.
    • If 13 was not performed, continue the procedure by performing one of these steps.
      • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was displayed in 19, continue the procedure with 26.
      • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was not displayed in 19, continue the procedure with 27.
25. Change the FCMODE values that were changed in 13 to the values that were displayed in 12 by entering the chg-eisopts command with the fcmode and fcgpl parameter values that were displayed in 12. If all the GPL values were changed in 13, the gpl=all parameter can be specified with the chg-eisopts command.

    For this example, enter this command.

    chg-eisopts:fcmode=fcopy:fcgpl=all

    When the chg-eisopts has successfully completed, this message should appear.

    
    rlghncxa03w 10-07-28  07:05:01 GMT  EAGLE5 42.0.0
    CHG-EISOPTS: MASP A - COMPLTD
    

    Continue the procedure by performing one of these steps.

    • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was displayed in 19, continue the procedure with 26.
    • If the CAUTION: SYSTEM SITE ID WAS REFERENCED BY THE REDIRECT FUNCTION’S DPC message was not displayed in 19, continue the procedure with 27.
26. If the point code of the EAGLE or capability point code is referenced by the gateway screening redirect function and the gateway screening redirect function is enabled, the gateway screening redirect function’s DPC must be changed to reference the new EAGLE’s point code.

    Use the chg-gws-redirect command to change the gateway screening redirect function’s DPC. Perform the Changing the Gateway Screening Redirect Parameters procedure in the Database Administration - Features User's Guide to change the gateway screening redirect function’s DPC.

27. Verify the changes using the rtrv-sid command.

    This is an example of the possible output.

    
    rlghncxa03w 08-09-10 11:43:04 GMT  EAGLE5 39.2.0
       PCA             PCI          PCN                CLLI              PCTYPE
       100-100-100     3-75-7       7-9-8-1            rlghncxa03w       OTHER
    
       CPCA
       002-002-002       002-002-003       002-002-004      002-002-005
       002-002-006       002-002-007       002-002-008      002-002-009
       004-002-001       004-003-003       050-060-070
    
       CPCA (LNP)
       005-005-002       005-005-004       005-005-005      006-006-006
    
       CPCI
       1-002-1           1-002-2           1-002-3          1-002-4
       2-001-1           7-222-7
    
       CPCN
       2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
       2-2-3-3           2-2-4-0           10-14-10-1
    

28. 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.
    

The Cluster Routing and Management Diversity feature eliminates the need for a full point code entry in the routing table to route to every signaling point in every network. The Cluster Routing and Management Diversity feature allows the EAGLE to configure one routeset to a entire cluster of destinations. This feature also allows the EAGLE to manage and switch traffic to more end nodes.

A cluster is defined as a group of signaling points whose point codes have identical values for the network and cluster fields of the point codes. A cluster entry in the routing table is shown with an asterisk (*) in the member field of the point code, for example, 111-011-*. With this feature, ANSI destination point codes can be specified as either a full point code, for example, 123-043-045, or as a cluster of signaling point codes, for example, 111-011-*.

The Cluster Routing and Management Diversity feature allows provisioning of clusters, as well as of full point codes that belong to the same cluster as destination point codes (Figure 2-21). The point codes 111-011-*, 111-011-005 and 111-011-045 entries can be provisioned. In Figure 2-21, the cluster destination point code 111-011-* represents all the point codes of the cluster except for point codes 111-011-005 and 111-011-045. Cluster entries in the destination point code table can also be used as a DPC for a route. A group of such routes with varying relative cost forms a routeset to a cluster, just like a routeset to a full point code.

Figure 2-21 Cluster Routing and Management Diversity

Cluster Routing and Management Diversity Example

This section shows an example of the Cluster Routing and Management Diversity feature, and lists the network events affecting the EAGLE. This example is based on Figure 2-22 and Table 2-7.

Figure 2-22 Cluster Management

Table 2-7 Example Cluster Routing Information

	Route Table for Destination 005-005-001	Route Table for Cluster 005-005-*
1	LSN 1, Cost=10	LSN 1, Cost=10
2	LSN 2, Cost=15	LSN 2, Cost=15
3	LSN 3, Cost=20	LSN 3, Cost=20

When the normal routes, linksets LSN 1 and LSN 2, become available, the EAGLE sends a preventive TFP for destination 005-005-001 and a preventive TCP for cluster 005-005-* to node 002-002-002, and starts routing messages to destination 005-005-001 and cluster 005-005-* using linkset LSN 1. The EAGLE broadcasts TFAs about destination 005-005-001 and TCAs about cluster 005-005-* to all other adjacent nodes.

1. When linkset LSN 4 fails, node 002-002-002 sends a TFP for destination 005-005-001 to the EAGLE. Linkset LSN 4 is prohibited from carrying traffic from the EAGLE to destination 005-005-001. The EAGLE stops using linkset LSN 1 to send traffic to destination 005-005-001, performs forced rerouting, starts level 3 timer T11 for destination 005-005-001, and starts using linkset LSN 2 to send messages to destination 005-005-001. The EAGLE generates preventive TFPs about destination 005-005-001 to node 002-002-003. The preventive TCP for cluster 005-005-* sent to node 002-002-002 remains in effect.

   When the level 3 timer T11 for destination 005-005-001 expires, TFRs are broadcast for destination 005-005-001 to nodes 004-004-004, 006-006-006, 007-007-007, and 008-008-008. Destination 005-005-001 is restricted.

2. When linkset LSN 5 fails, node 002-002-002 sends a TCP for cluster 005-005-* to the EAGLE. Linkset LSN 5 is prohibited from carrying traffic from the EAGLE to cluster 005-005-*. The EAGLE stops using linkset LSN 1 to send traffic to cluster 005-005-*, performs forced rerouting, starts the level 3 timer T11 for cluster 005-005-*, and starts using linkset LSN 2 to send messages to cluster 005-005-*. The EAGLE sends preventive TCPs for cluster 005-005-* on linkset LSN 2. The EAGLE sends a TCR for cluster 005-005-* on linkset LSN 1, to allow cluster 005-005-* and destination 005-005-001 to send messages back to the EAGLE on linkset LSN 1. When the level 3 timer T11 for cluster 005-005-* expires, the EAGLE sends a TCR for cluster 005-005-* to nodes 004-004-004, 006-006-006, 007-007-007, and 008-008-008. Cluster 005-005-* is restricted.
3. When linkset LSN 6 fails, node 003-003-003 sends a TCP for cluster 005-005-* to the EAGLE. The EAGLE performs forced rerouting, sends a preventive TFP for destination 005-005-001 and a TCP for destination 005-005-001 to node 004-004-004, and starts using linkset LSN 3 for sending messages to destination 005-005-001 and cluster 005-005-*.
4. When linkset LSN 7 fails, node 004-004-004 sends a TCP for cluster 005-005-* to EAGLE. The EAGLE cannot send traffic to either destination 005-005-001 or cluster 005-005-*. The EAGLE broadcasts TCPs for cluster 005-005-* to nodes 002-002-002, 003-003-003, 004-004-004, 006-006-006, 007-007-007, and 008-008-008. Cluster 005-005-* and destination 005-005-001 are inaccessible.
5. When linkset LSN 7 recovers, node 004-004-004 sends a TCA for cluster 005-005-* to the EAGLE. The EAGLE sends a preventive TCP for cluster 005-005-* to node 004-004-004, and starts using linkset LSN 3 to send traffic to cluster 005-005-*. The EAGLE sends a TCR for cluster 005-005-* to node 002-002-002. This allows cluster 005-005-* to send messages back to the EAGLE on linkset LSN 3. The EAGLE sends a preventive TCP for cluster 005-005-* to nodes 003-003-003 and 004-004-004. The EAGLE sends a TCR for cluster 005-005-* to nodes 006-006-006, 007-007-007, and 008-008-008. The EAGLE enables response method for destination 005-005-001, and starts a routeset test for destination 005-005-001 on linkset LSN 3. Cluster 005-005-* is restricted.
6. When linkset LSN 6 recovers, node 003-003-003 sends a TCA for cluster 005-005-* to the EAGLE. The EAGLE performs controlled rerouting on cluster 005-005-*, sends a preventive TCP for cluster 005-005-* to node 003-003-003, and starts using linkset LSN 2 to send traffic to cluster 005-005-*. The EAGLE sends a TCR for cluster 005-005-* to node 004-004-004. The EAGLE starts a routeset test for destination 005-005-001 on linkset LSN 2.
7. When linkset LSN 5 recovers, node 002-002-002 sends a TCA for cluster 005-005-* to the EAGLE. The EAGLE performs controlled rerouting, and starts using linkset LSN 1 to send traffic to cluster 005-005-*. The EAGLE sends a preventive TCP for cluster 005-005-* to node 002-002-002. The EAGLE broadcasts a TCA for cluster 005-005-* to nodes 003-003-003, 004-004-004, 006-006-006, 007-007-007, and 008-008-008. The EAGLE enables response method for destination 005-005-001, and starts a routeset test for destination 005-005-001 on linkset LSN 1. Cluster 005-005-* is allowed.
8. In response to the routeset test, node 004-004-004 sends a TFA for destination 005-005-001 to the EAGLE. The EAGLE performs controlled rerouting, and starts using linkset LSN 3 to send traffic to destination 005-005-001. The EAGLE sends a preventive TFP for destination 005-005-001 to nodes 003-003-003 and 004-004-004. The EAGLE sends a TFR for destination 005-005-001 to node 002-002-002 that allows destination 005-005-001 to send messages back to the EAGLE on linkset LSN 1. The EAGLE broadcasts a TFR for destination 005-005-001 to nodes 006-006-006, 007-007-007, and 008-008-008. Destination 005-005-001 is restricted.
9. In response to the routeset test, node 003-003-003 sends a TFA for destination 005-005-001 to the EAGLE. The EAGLE performs controlled rerouting and starts using linkset LSN 2 to send traffic to destination 005-005-001. The EAGLE sends a preventive TFP for destination 005-005-001 to node 003-003-003. The EAGLE sends a TFR for destination 005-005-001 to node 004-004-004.
10. In response to the routeset test, node 002-002-002 sends a TFA for destination 005-005-001 to the EAGLE. The EAGLE performs controlled rerouting, and starts using linkset LSN 1 to send traffic to destination 005-005-001. The EAGLE sends a preventive TFP for destination 005-005-001 to node 002-002-002. The EAGLE sends a TFA for destination 005-005-001 to nodes 003-003-003, 004-004-004, 006-006-006, 007-007-007, and 008-008-008. Destination 005-005-001 is allowed.

Home Cluster Example

Figure 2-23 Home Cluster Example

Table 2-8 Home Cluster Routing Information

	Route table for Destination 002-002-005	Route table for cluster 002-002-*
1	LSN 1, Cost=10	LSN 1, Cost=10
2	LSN 2, Cost=15	LSN 2, Cost=15

A home cluster is a cluster point code that contains either the true point code or any capability point code of the EAGLE. For example, if the EAGLE’s true point code or any capability point code is 002-002-001 and a cluster 002-002-* is configured, then the cluster 002-002-* is a home cluster.

Provisioning a home cluster causes a profound impact on network management, regarding the home cluster as well as members of the cluster. These impacts are:

• Because the EAGLE is one of the accessible members of the home cluster, the EAGLE never transmits TCP or TCR messages regarding the home cluster, except for these:
  • Preventive TCP – when starting to route to the cluster through an adjacent node
  • Broadcast TCR – when the EAGLE starts routing on an alternate route for the entire cluster
  • Back Routing TCR – to allow adjacent nodes on normal routes to route through the EAGLE, when the cluster is not accessible on the normal route
  • Broadcast TCP – when the cluster (except the EAGLE itself) becomes inaccessible
• If individual members are provisioned for the home cluster, the EAGLE properly generates network management messages for these nodes, except that no TFRs can be sent from those members being routed on the alternate route to the EAGLE.
• Network management replies to the routeset test, and the response method generates the correct network management messages for the home cluster, its members, and unprovisioned member point codes.
• When the entire home cluster is being routed on the alternate route, the EAGLE generates a full point code response method TFR reply. In such a case, the EAGLE generates only one TFR for the very first member of the cluster for which MSU is received on each signaling link to that cluster.
• When the home cluster is inaccessible, the EAGLE generates one response TFP, at an interval equal to the value of the level 3 timer T8 for the members of the home cluster. If the EAGLE keeps receiving traffic for the home cluster, the EAGLE sends response TFPs for all members of the cluster.

This makes network management unreliable for the home cluster and its members.

When the normal routes, linksets LSN 1 and LSN 2, become available, the EAGLE sends a preventive TFP for destination 002-002-005 to node 002-002-002, and starts sending messages to destination 002-002-005 and cluster 002-002-* using linkset LSN 1. No preventive messages are sent for cluster 002-002-*. The EAGLE broadcasts a TFA for destination 002-002-005 and a TCA for cluster 002-002-* to all other adjacent nodes.

1. Node 002-002-002 sends an MSU containing the destination point code 002-002-006 on linkset LSN 1. The EAGLE responds with a response preventive TFP for destination 002-002-006 to node 002-002-002.
2. When linkset LSN 3 fails, node 002-002-002 sends a TFP for destination 002-002-005 to the EAGLE. The EAGLE stops using linkset LSN 1 to send traffic to destination 002-002-005, performs forced rerouting, starts the level 3 timer T11 for destination 002-002-005, and starts using linkset LSN 2 to send traffic to destination 002-002-005. The EAGLE generates a preventive TFP for destination 002-002-005 to node 002-002-003. When the level 3 timer T11 for destination 002-002-005 expires, TFRs for destination 002-002-005 are broadcast to nodes 002-002-003 and 001-001-001. Destination 002-002-005 is restricted.
3. Node 002-002-002 sends an MSU containing the destination point code 002-002-005 on linkset LSN 1. The EAGLE responds with a response preventive TFP for destination 002-002-005 to node 002-002-002, because no member of a home cluster is allowed to route messages back to the EAGLE.
4. When linkset LSN 1 fails, the EAGLE stops using linkset LSN 1 to send traffic to cluster 002-002-*, performs forced rerouting, starts the level 3 timer T11 for cluster 002-002-*, and starts using linkset LSN 2 to send traffic to cluster 002-002-*. Cluster 002-002-* is restricted. No preventive or broadcast messages are sent, and no member of the cluster is allowed to send messages back to the EAGLE.
5. Node 001-001-001 sends an MSU containing the destination point code 002-002-006. The EAGLE responds with a response TFR for destination 002-002-006 to node 001-001-001. The MSU is routed on linkset LSN 2.
6. Node 001-001-001 sends an MSU containing the destination point code 002-002-005. The EAGLE responds with a response TFR for destination 002-002-005 to node 001-001-001. The MSU is routed on linkset LSN 2.
7. Node 001-001-001 sends an MSU containing the destination point code 002-002-007 and receives no response. The MSU is routed on linkset LSN 2.
8. When linkset LSN 2 fails, destination 002-002-005 and cluster 002-002-* are prohibited. The EAGLE broadcasts a TFP for destination 002-002-005 to node 001-001-001.
9. Node 001-001-001 sends an MSU containing the destination point code 002-002-007. The EAGLE responds with a TFP for destination 002-002-007 to node 001-001-001, and starts the level 3 timer T8 for cluster 002-002-*.
10. Node 001-001-001 sends an MSU containing the destination point code 002-002-006, and receives no response until the level 3 timer T8 expires.
11. Node 001-001-001 sends an MSU containing the destination point code 002-002-005. The EAGLE responds with a TFP for destination 002-002-005 to node 001-001-001, and starts the level 3 timer T8 for destination 002-002-005.
12. Node 001-001-001 sends an MSU containing the destination point code 002-002-006. After the level 3 timer T8 for cluster 002-002-* expires, the EAGLE responds with a TFP for destination 002-002-006 to node 001-001-001, and starts the level 3 timer T8 for cluster 002-002-*.

When a node is switching traffic to remote (non-adjacent) nodes, it is possible that an STP is using at least one route that is different from the other members of a cluster. Typically, this occurs when the node is directly connected to the member of a cluster, such as when an STP has A-links or E-links that are connected to a member. The nested cluster routing feature provides a mechanism that allows both cluster and member routes to be provisioned in the same cluster.

Nested Cluster Routing Example

Figure 2-24 provide an example of nested cluster routing. Table 2-10 and Table 2-11 show the routing tables for the cluster point code and one of the members of the cluster point code. Table 2-12 shows what actions the EAGLE takes when the linksets in a nested cluster configuration fail and recover. The actions in Table 2-12 are based on the example nested cluster routing configuration shown in Figure 2-24.

Figure 2-24 Nested Cluster Routing Sample Configuration

Table 2-10 Routing Table for Nested Cluster 5-5-*

Linkset Name	Route DPC	Cost Value of the Route
LSB	5-5-*	10
LSC	5-5-*	20

Table 2-11 Routing Table for Full Point Code Member 5-5-1

Linkset Name	Route DPC	Cost Value of the Route
LSE	5-5-1	5
LSB	5-5-1	10
LSC	5-5-1	20

Table 2-12 Example of Nested Cluster Routing Failure and Recovery Actions

Event	Action
All linksets are up and all routes are available.	The EAGLE does not send a preventive TCP for cluster 5-5-* to node B because cluster 5-5-* is a nested cluster. Messages are routed to SSP 5-5-1 using linkset LSE and to cluster 5-5-* using linkset LSB. The EAGLE broadcasts TCAs concerning cluster 5-5-* to nodes SSP1, SSP 5-5-1, node A, and node B.
The linkset between node B and SSP 5-5-2 fails. Node B sends a TFP concerning SSP 5-5-2.	The EAGLE creates an x-list entry for point code 5-5-2 and marks it prohibited on linkset LSB. The EAGLE broadcasts TFPs to SSP1, SSP 5-5-1 and node A and sends response method TFP concerning point code 5-5-2. The EAGLE starts an RSP for SSP 5-5-2 on linkset LSB.
The linkset between node B and SSP 5-5-1 fails. Node B sends a TFP for SSP 5-5-1 to the EAGLE.	The EAGLE marks full point code 5-5-1 as prohibited on linkset LSB. The EAGLE routes the traffic to SSP 5-5-1 using linkset LSE. The EAGLE starts an RSP for SSP 5-5-1 on linkset LSB.
The linkset between node B and SSP 5-5-2 recovers, and node B sends a TFA for SSP 5-5-2 to the EAGLE.	The EAGLE removes point code 5-5-2 from the exception list. The status of linkset LSB is changed from prohibited to allowed. Traffic is routed to SSP 5-5-2 using linkset LSB. The EAGLE broadcasts a TFA concerning SSP 5-5-2 to SSP1, SSP 5-5-1 and node A. The EAGLE sends a preventive TFP concerning SSP 5-5-2 to node B.
The linkset between node B and SSP 5-5-1 recovers, and node B sends a TFA concerning SSP 5-5-1 to the EAGLE.	The EAGLE marks full point code 5-5-1 as allowed on linkset LSB.
Linkset LSB fails.	The EAGLE stops using linkset LSB to send traffic to cluster 5-5-*. Linkset LSB is marked prohibited, forced rerouting is performed, level 3 timer T11 for cluster 5-5-* is started, and starts using linkset LSC to send traffic to cluster 5-5-*. The EAGLE marks cluster 5-5-* restricted on linkset LSC for all members of cluster 5-5-* except full point code 5-5-1. When level 3 timer T11 expires, a TFR response method is sent for all members of cluster 5-5-* except full point code 5-5-1.
SSP1 sends an MSU with DPC=5-5-2.	The EAGLE responds with TFR concerning SSP 5-5-2 to SSP1. The MSU is routed on linkset LSC.
SSP1 sends an MSU with DPC=5-5-1.	The EAGLE routes the MSU to SSP 5-5-1 using linkset LSE.
Linkset LSB recovers.	The EAGLE stops using linkset LSC to send traffic to cluster 5-5-*, performs controlling rerouting on cluster 5-5-*, marks cluster 5-5-* as allowed on linkset LSB, and starts routing traffic to cluster 5-5-* using linkset LSB.
The SSP sends a routeset test (RSR) concerning SSP 5-5-2 to the EAGLE.	The EAGLE responds with a TFA concerning SSP 5-5-2.
Linkset LSC fails.	The EAGLE stops using linkset LSC to send traffic to cluster 5-5-* or full point code 5-5-1, and marks cluster 5-5-* and full point code 5-5-1 as prohibited on linkset LSC.
Linkset LSC recovers.	The EAGLE marks cluster 5-5-* and full point code 5-5-1 as allowed on linkset LSC.
Linkset LSE fails.	The EAGLE stops using linkset LSE to send traffic to SSP-5-5-1, marks SSP 5-5-1 as prohibited on linkset LSE, performs forced rerouting, starts level 3 timer T11 concerning SSP 5-5-1, sends preventive TFP concerning SSP 5-5-1 to node B, and starts using linkset LSB to send traffic to full point code 5-5-1. The EAGLE marks full point code 5-5-1 as restricted on linkset LSB. When level 3 timer T11 expires, a TFR concerning SSP 5-5-1 is sent to SSP1 and node A.
SSP1 sends an MSU with the DPC 5-5-2.	The EAGLE routes the MSU to SSP 5-5-2 using linkset LSB.
SSP1 sends an MSU with the DPC 5-5-1.	The EAGLE responds with a TFR concerning SSP 5-5-1 to SSP1. The MSU is routed to SSP 5-5-1 using linkset LSB.
Linkset LSE recovers.	The EAGLE stops using linkset LSB to send traffic to SSP 5-5-1, performs controlling rerouting on full point code 5-5-1, marks full point code 5-5-1 as allowed on linkset LSE, and starts routing traffic to full point code 5-5-1 using linkset LSE. The EAGLE broadcasts a TFA for SSP 5-5-1 to SSP1, node A, and node B.

1. Display the current destination point codes in the database, using the rtrv-dstn 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          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
      002-002-002   ----------- no  --- --------------   --------------   SS7
      020-002-045   rlghncbb100 no  --- --------------   --------------   SS7
      020-002-050   rlghncbb100 no  --- --------------   --------------   SS7
      030-045-001   ----------- yes --- --------------   --------------   SS7
      111-011-001   ----------- yes --- --------------   --------------   SS7
      240-012-005   rlghncbb002 yes ---    1-112-2          11112         SS7
      240-012-006   rlghncbb003 yes ---    1-112-3          11113         SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
      2-131-1       rlghncbb023 no  ---    222-210-000      12001         SS7
      2-131-2       ----------- no  ---    222-211-001      12002         SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA           ALIASI        DMN
      11211         rlghncbb013 no  ---    222-200-200      2-121-1       SS7
      11212         rlghncbb013 no  ---    222-200-201      2-121-2       SS7
   
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   11
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 0
       TOTAL DPC(s):                  11
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  12
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   If the addition of the cluster point code will not exceed the current DPC capacity shown in the rtrv-dstn output, continue the procedure with 2.

   If the addition of the cluster point code will exceed the current DPC capacity, and the current capacity is less than 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Changing the DPC Quantity procedure to change the DPC quantity. Continue the procedure with 2.

   If the addition of the cluster point code will exceed the current DPC capacity, and the current capacity is 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Removing a Destination Point Code procedure to remove a DPC or perform the Removing a Route Exception Entry procedure to remove an exception route. Continue the procedure with 2.

   Note:

   If thertrv-dstn output in1shows any cluster point codes, and nested cluster point codes are not being configured in this procedure, continue the procedure with3.

   Note:

   If cluster point codes are not shown in thertrv-dstn output in1, but ANSI point codes are shown in1, continue the procedure with3.
2. Display the self-identification of the EAGLE using the rtrv-sid command. This is an example of the possible output..

   
   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   PCA              PCI             PCN           CLLI            PCTYPE
   010-020-030      0-123-1         12-0-14-1     rlghncxa03w     OTHER
   
   CPCA
   002-002-002       002-002-003       002-002-004      002-002-005
   002-002-006       002-002-007       002-002-008      002-002-009
   004-002-001       004-003-003       050-060-070
   
   CPCI
   1-001-1           1-001-2           1-001-3          1-001-4
   1-002-1           1-002-2           1-002-3          1-002-4
   2-001-1           7-222-7
   
   CPCN
   2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
   2-2-3-3           2-2-4-0           10-14-10-1
   

   If the PCA field does not contain an entry, perform the Changing the Self-Identification of the EAGLE procedure and add an ANSI point code to the self identification of the EAGLE.

   Note:

   If theDESTINATION ENTRIES ALLOCATEDandX-LIST ENTRIES ALLOCATED fields are shown in thertrv-dstn output in1, and nested cluster point codes are not being configured in this procedure, continue the procedure with6.
3. Verify that the Cluster Routing and Management Diversity feature is turned on, by entering the rtrv-feat command. If nested cluster point codes are to be configured in the database, the nested cluster routing feature must be turned on. If the Cluster Routing and Management Diversity feature is turned on, the CRMD field should be set to on. If the nested cluster routing feature is turned on, the NCR field should be set to on. In this example, both features are 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 Commands User's Guide.
4. Turn the Cluster Routing and Management Diversity feature on by entering this command.

   chg-feat:crmd=on

   Note:

   If the Cluster Routing and Management Diversity feature is on, shown by theCRMD = on entry in thertrv-feat command output in3, continue the procedure with5.

   Note:

   Once the Cluster Routing and Management Diversity feature is turned on with thechg-feat command, it cannot be turned off.

   The Cluster Routing and Management Diversity 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 Cluster Routing and Management Diversity feature, contact your Sales Representative or Account Representative.

   When this command has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

   If nested cluster point codes are being added to the database or the ncai parameter is be specified for the cluster point code and the nested cluster routing feature is on, shown by the NCR = on entry in the rtrv-feat command output in 3, and DPCs are shown in the rtrv-dstn output that are members of the cluster point code that is being added, continue the procedure with 6. If the rtrv-dstn output does not show any DPCs that are members of the cluster point code being added, continue the procedure with 9.

   If nested cluster point codes are being added to the database or the ncai parameter is be specified for the cluster point code and the nested cluster routing feature is off, continue the procedure with 5.

5. Turn the nested cluster routing feature on by entering this command.
   chg-feat:ncr=on

   Note:

   Once the nested cluster routing feature is turned on with thechg-feat command, it cannot be turned off.

   The nested cluster routing 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 nested cluster routing feature, contact your Sales Representative or Account Representative.

   When this command has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

   Note:

   If thertrv-dstn output does not show any DPCs that are members of the cluster point code being added in this procedure, continue the procedure with 9 .
6. The cluster point code cannot be added to the database if the database contains member point codes assigned to routes that are assigned to linksets whose linkset type is either A or E.

   Enter the rtrv-rte command with one of the DPCs that is a member of the cluster point code being added in this procedure. For this example, enter these commands.

   rtrv-rte:dpca=111-011-001

   This is an example of the possible output.

   
   rlghncxa03w 07-05-17 15:35:05 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      111-011-001    -------    -----------   lsn2       10   111-011-001
                                                  RTX:No  CLLI=-----------
   

   rtrv-rte:dpca=030-045-001

   This is an example of the possible output.

   
   rlghncxa03w 07-05-17 15:35:05 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      030-045-001    -------    -----------   lsn3       10    030-045-001
                                                  RTX:No  CLLI=-----------
   

   If the DPC specified in this step is the DPC of a route, continue the procedure with 7.

   If the DPC specified in this step is not the DPC of a route, repeat this step for other DPCs, shown in the rtrv-dstn output, that are members of the cluster point code being added in this procedure.

   If all the DPCs that are members of the cluster point code being added have been displayed, and none of these DPCs are DPCs of routes, continue the procedure with 9.

7. Enter the rtrv-ls command with the linkset name shown in the rtrv-rte output in 6.

   The linkset name is shown in the LSN column of the rtrv-rte output. For this example, enter these commands.

   rtrv-ls:lsn=lsn2

   This is an example of the possible output.

   
   rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn2          111-011-001   none 1   1   no  B   2    off off off no    off
   
              CLLI         TFATCABMLQ MTPRSE ASL8
              -----------  1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA                no
   
                                     L2T               PCR  PCR
              LOC  LINK SLC TYPE     SET  BPS    ECM   N1   N2
              1103 A     0  LIMDS0   1    56000  BASIC ---  -----
              1104 A     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (6 of 1024) 1% full.
   

   rtrv-ls:lsn=lsn3

   This is an example of the possible output.

   
   rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn3          030-045-001   none 1   1   no  B   2    off off off no    off
   
              CLLI         TFATCABMLQ MTPRSE ASL8
              -----------  1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA                no
   
                                     L2T               PCR  PCR
              LOC  LINK SLC TYPE     SET  BPS    ECM   N1   N2
              1103 B     0  LIMDS0   1    56000  BASIC ---  -----
              1104 B     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (6 of 1024) 1% full.
   

   If the linkset type of the linkset is either A or E, performChanging an SS7 Linkset to change the linkset type to B, C, or D.

   If all the DPCs that are members of the cluster point code being added have not been displayed in 6, repeat 6 and 7.

   After all the linksets whose APCs are members of the cluster point code that is being added, and the linkset type of these linksets shown in this step is B, C, or D, or the linkset type was changed, continue the procedure by performing one of these steps.

   • If the nprst, rcause, or splitiam parameters will not be specified for the cluster point code, continue the procedure with 9 .
   • If the nprst, rcause, or splitiam parameters will be specified for the cluster point code, continue the procedure with 8.
8. Display the features that are enabled by entering the rtrv-ctrl-feat command. This is an example of the possible output.

   
   rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   HC-MIM SLK Capacity       893012707 on     64
   TIF Number Portability    893018901 off    ----
   XUDT UDT Conversion       893035301 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.
   

   To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.

   • TIF Number Portability - part number 893018901
   • TIF SCS Forwarding - part number 893022201
   • TIF Simple Number Substitution - part number 893024001
   • TIF Additional Subscriber Data - part number 893024501
   • TIF Generic Routing Number - part number 893025501

   Perform the procedures in TIF User's Guide to enable these features as required.

9. Continue the procedure by performing one of these steps.
   • Continue the procedure with 11 if any of these conditions are present.
     • The sccpmsgcnv parameter will not be specified for the cluster point code.
     • The sccpmsgcnv parameter will be specified for the cluster point code and the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is enabled and turned on. If the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.
   • Continue the procedure with 10 if the sccpmsgcnv parameter will be specified for the cluster point code and 8 was not performed.
10. Enter this command to verify the status of the XUDT UDT Conversion feature.

    rtrv-ctrl-feat:partnum=893035301

    This is an example of the possible output.

    
    rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum   Status Quantity
    XUDT UDT Conversion       893035301 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 XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

    If the XUDT UDT Conversion feature is enabled and turned on, or the "Activating the XUDT UDT Conversion Feature" procedure was performed in this step, continue the procedure with 11.

11. Add the cluster point code to the database, by using the ent-dstn command.

    For this example, enter these commands.

    ent-dstn:dpca=111-011-*:clli=rlghncbb000:bei=yes:elei=yes:domain=ss7

    ent-dstn:dpca=030-045-*:clli=rlghncbb010:bei=yes:elei=yes :domain=ss7:ncai=yes

    ent-dstn:dpca=100-075-*:bei=yes:elei=yes:ncai=yes:nprst=on:rcause=15 :splitiam=10:sccpmsgcnv=udt2xudt

    When these commands have successfully completed, this message should appear.

    
    rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD
    

12. Verify the changes using the rtrv-dstn command and specifying the DPC that was entered in 11.

    For this example, enter these commands.

    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
       -----------  no           none   off   none     no     no    none 
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    rtrv-dstn:dpca=030-045-*

    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
       030-045-*     rlghncbb010 yes yes ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no           none   off   none     no     no    none
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    rtrv-dstn:dpca=100-075-*

    
    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       100-075-*     ----------- yes yes ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  yes          15     on      10     no     no    udt2xudt
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    Note:

    If you do not wish to change the exception list parameters for the Cluster Routing and Management Diversity feature, continue the procedure with16.
13. The parameters for the exception list for the Cluster Routing and Management Diversity feature can be changed from the default settings by using the chg-stpopts command. The parameters of the chg-stpopts command that control the exception point-code list are:

    mtpxlq = the maximum number of entries the exception list (x-list) can contain

    mtpxlet = the maximum amount of time the EAGLE will maintain an unreferenced exception list (x-list) entry, expressed in the format hhmm, where hh is the number of hours, and mm is the number of minutes.

    mtpxlot = the exception list (x-list) occupancy threshold (in terms of percentage of space available). If this threshold is exceeded, the EAGLE raises a minor alarm.

    mtpdpcq = the maximum number of destination point codes that can be configured on the EAGLE.

    Note:

    The sum of theMTPDPCQ andMTPXLQ value’s cannot exceed one of these totals depending on the features that are enabled or turned on:

    • 2500 – if the 5000 Routes feature is not on, and 6000, 7000, or 8000 routesets are not enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 2000.
    • 5500 – if the 5000 Routes feature is on, but 6000, 7000, or 8000 routesets are not enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 5000.
    • 6500 – if 6000 routesets are enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 6000.
    • 7500 – if 7000 routesets are enabled. The range of values for the mtpdpcq parameter is 500 to 7000. The range of values for the mtpxlq parameter is 500 to 6000.
    • 8500 – if 8000 routesets are enabled. The range of values for the mtpdpcq parameter is 500 to 8000. The range of values for the mtpxlq parameter is 500 to 6000.
    • 10,500 – if 10,000 routesets are enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 10,000.

    Display the existing values for the exception list parameters, by entering the rtrv-stpopts command. This is an example of the possible output.

    
    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    STP OPTIONS
    -----------------------
    MTPXLQ             500
    MTPXLET           0100
    MTPXLOT            90%
    MTPDPCQ           2000
    

    Note:

    Thertrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-stpopts command, see thertrv-stpopts command description in Commands User's Guide.

    Note:

    If the Cluster Routing and Management Diversity was turned on in this procedure, theMTPXLQ,MTPXLET, andMTPXLOT parameters are shown with these default values.

    • MTPXLQ – 500
    • MTPXLET – 0100
    • MTPXLOT – 90%

    The MTPDPCQ value is not changed when the Cluster Routing and Management Diversity is turned on.

14. If you wish to change the exception list parameters or the mtpdpcq value, enter the chg-stpopts command.

    Note:

    If the DPC quantity or the exception list quantity is being changed in this step, both the mtpdpcq andmtpxlq parameters do have to be specified in this step unless the resulting sum of themtpdpcq andmtpxlq parameters would exceed the totals shown in12. For example, the currentmtpdpcq value is 4000 and the currentmtpxlq value is 1500, resulting in a sum of 5500, and only the 5000 Routes feature is on. To change either value, both parameters must be specified and the sum of the new values cannot exceed 5500. If in this example, the currentmtpdpcq value is 3000 and the currentmtpxlq value is 1500, resulting in a sum of 4500, either parameter value can be changed without specifying the other parameter as long as the sum of the values does not exceed 5500.

    For this example, change the DPC quantity value to 1750, the exception list size to 750, the exception list timer to 1 hour and 30 minutes (90 minutes), and the exception list occupancy threshold to 75%. Enter this command.

    chg-stpopts:mtpdpcq=1750:mtpxlq=750:mtpxlet=0130:mtpxlot=75

    When this command has successfully completed, this message should appear.

    
    rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
    CHG-STPOPTS: MASP A - COMPLTD
    

15. Verify the changes using the rtrv-stpopts command.

    This is an example of the possible output.

    
    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    STP OPTIONS
    -----------------------
    MTPXLQ             750
    MTPXLET           0130
    MTPXLOT            75%
    MTPDPCQ           1750
    

    Note:

    Thertrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-stpopts command, see thertrv-stpopts command description in Commands User's Guide.
16. 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.
    

1. Display the current destination point codes, using the rtrv-dstn 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          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      020-002-*     rlghncbb000 yes yes ----------      --------------   SS7
      240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3     SS7
      240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
      240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1    SS7
      240-012-007   ----------- yes ---    1-117-3         10-13-11-1    SS7
      240-012-008   ----------- yes ---    1-113-5         10-13-10-2    SS7
      030-003-*     rlghncbb333 yes yes ----------      --------------   SS7
      030-003-100   rlghncbb334 yes ---    1-112-3         10-13-10-1    SS7
      030-003-200   rlghncbb335 yes ---    1-117-3         10-13-11-1    SS7
      030-003-225   rlghncbb336 yes --- ----------      --------------   SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
      2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1     SS7
      2-131-2       ----------- no  ---    222-211-001     11-11-8-2     SS7
      2-131-3       ----------- no  ---    222-211-002     11-11-8-3     SS7
      4-163-5       ----------- no  ---    250-200-007     15-11-5-1     SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
      7-9-10-1      ----------- no  ---    210-090-100     1-75-6        SS7
      10-15-2-3     rlghncbb013 no  ---    222-200-200     2-121-1       SS7
      10-15-3-0     rlghncbb013 no  ---    222-200-201     2-121-2       SS7
   
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  22
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  28
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   If the CLLI value for the cluster point code is not being changed in this procedure, continue the procedure with 3.

   If the CLLI value for the cluster point code is being changed in this procedure, continue the procedure with 2.

2. Display the self-identification of the EAGLE using the rtrv-sid command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
      PCA             PCI          PCN                CLLI              PCTYPE
   
      010-020-030     0-123-1      12-0-14-1          rlghncxa03w       OTHER
   
      CPCA
      002-002-002       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
   
      CPCI
      1-001-1           1-001-2           1-001-3          1-001-4
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
   
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1
   

   If the CLLI value for the cluster point code is being changed in this procedure, that CLLI value cannot be shown in the CLLI fields of either the rtrv-dstn (1) or the rtrv-sid command outputs.

3. Display the attributes of the cluster point code being changed, by entering the rtrv-dstn command and specifying the cluster point code that is being changed.

   For this example, enter this command.

   rtrv-dstn:dpca=030-003-*

   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
      030-003-*     rlghncbb333 yes yes ----------      --------------   SS7
   
      SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
      -----------  yes          none   off   none     no     no    none
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  22
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  28
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   Continue the procedure by performing one of these steps.

   • If the nprst, rcause, splitiam, sccpmsgcnv, or ncai parameter values will not be changed, continue the procedure with 10.
   • If only the ncai parameter value will be changed, continue the procedure by performing one of these steps.
     • If the current ncai parameter value is no, continue the procedure with 8.
     • If the current ncai parameter value is yes, continue the procedure with 6.
   • If the sccpmsgcnv parameter value will be changed and the nprst, rcause, or splitiam parameter values will not be changed, continue the procedure with 5.
   • If the nprst, rcause, or splitiam parameter value will be changed, continue the procedure with 4.
4. Display the features that are enabled by entering the rtrv-ctrl-featcommand. This is an example of the possible output.

   
   rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   HC-MIM SLK Capacity       893012707 on     64
   TIF Number Portability    893018901 off    ----
   XUDT UDT Conversion       893035301 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.
   

   To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.

   • TIF Number Portability - part number 893018901
   • TIF SCS Forwarding - part number 893022201
   • TIF Simple Number Substitution - part number 893024001
   • TIF Additional Subscriber Data - part number 893024501
   • TIF Generic Routing Number - part number 893025501

   Perform the procedures in TIF User's Guide to enable these features as required.

   Continue the procedure by performing one of these steps.

   • If the sccpmsgcnv or ncai parameter values will not be changed, continue the procedure with 10.
   • If only the ncai parameter value will be changed, continue the procedure by performing one of these steps.
     • If the current ncai parameter value is no, continue the procedure with 8.
     • If the current ncai parameter value is yes, continue the procedure with 6.
   • If the sccpmsgcnv parameter value will be changed, continue the procedure with 5.
5. To specify the sccpmsgcnv parameter the XUDT UDT Conversion feature must be enabled and turned on.
   If 4 was performed and the rtrv-ctrl-feat output in 4 shows that the XUDT UDT Conversion feature is enabled and turned on, continue the procedure by performing one of these steps.

   • If the ncai parameter values will not be changed, continue the procedure with 10.
   • If the ncai parameter value will be changed, continue the procedure by performing one of these steps.
     • If the current ncai parameter value is no, continue the procedure with 8.
     • If the current ncai parameter value is yes, continue the procedure with 6.

   If 4 was performed and the rtrv-ctrl-feat output in 4 shows that the XUDT UDT Conversion feature is not enabled and turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

   If 4 was not performed, enter this command to verify the status of the XUDT UDT Conversion feature.

   rtrv-ctrl-feat:partnum=893035301

   This is an example of the possible output.

   
   rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   XUDT UDT Conversion       893035301 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 rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

   If the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is enabled and turned on, or the "Activating the XUDT UDT Conversion Feature" procedure was performed in this step, continue the procedure by performing one of these steps.

   • If the ncai parameter values will not be changed, continue the procedure with 10.
   • If the ncai parameter value will be changed, continue the procedure by performing one of these steps.
     • If the current ncai parameter value is no, continue the procedure with 8.
     • If the current ncai parameter value is yes, continue the procedure with 6.
6. Enter the rtrv-dstn command with the cluster point code being changed, but with three asterisks for the network-cluster member value of the cluster point code instead of one asterisk.

   For this example, enter this command.

   rtrv-dstn:dpca=030-003-***

   This is an example of the possible output.

   
   rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
   
      DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      030-003-*     rlghncbb333 yes yes ----------      --------------   SS7
      030-003-100   rlghncbb334 yes no     1-112-3         10-13-10-1    SS7
      030-003-200   rlghncbb335 yes no     1-117-3         10-13-11-1    SS7
      030-003-225   rlghncbb336 yes no  ----------      --------------   SS7
   
   Destination table is (20 of 2000) 1% full
   Alias table is (28 of 8000) 1% full
   RTRV-DSTN: MASP A - COMPLTD
   

   If the cluster point code does not have any member point codes in the database, continue the procedure with 8.

   If the cluster point code has member point codes in the database, continue the procedure with 7.

7. Display the routes to the members of the cluster point code, shown in 6, in the database using the rtrv-rte command with the DPC values shown in 6 for the members of the cluster point code.

   For this example, enter these commands.

   rtrv-rte:dpca=030-003-100

   This is an example of the possible output.

   
   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
   
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      030-003-100    1-112-3    10-13-10-1    ls000300   10    030-003-100
   
                                                  RTX:No  CLLI=rlghncbb334
   

   rtrv-rte:dpca=030-003-200

   This is an example of the possible output.

   
   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
   
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      030-003-200    1-117-3    10-13-11-1    ls000301   10    10 030-003-200
   
                                                  RTX:No  CLLI=rlghncbb335
   

   rtrv-rte:dpca=030-003-225

   This is an example of the possible output.

   
   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
   
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      030-003-225 ---------- --------------   ls000301   10    030-003-300
   
                                                  RTX:No  CLLI=rlghncbb336
   

   If the NCAI parameter is being changed from YES to NO, the routes to the point codes that are members of the cluster point code being changed must be removed from the database. Perform the Removing a Route procedure to remove these routes from the database. For this example, the routes to point codes 030-003-100, 030-003-200, and 030-003-225 must be removed. Continue the procedure with 10.

8. Verify that the nested cluster routing feature is on with the rtrv-feat command.

   If the nested cluster routing feature is turned on, the NCR field should be set to on. In this example, the nested cluster routing 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 Commands User's Guide.

   If the nested cluster routing feature is on, continue the procedure with 10.

   If the nested cluster routing feature is off, continue the procedure with 9.

9. Turn the nested cluster routing feature on by entering this command.

   chg-feat:ncr=on

   Note:

   Once the nested cluster routing feature is turned on with thechg-feat command, it cannot be turned off

   The nested cluster routing 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 nested cluster routing features, contact your Sales Representative or Account Representative.

   When this command has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

10. Change the attributes of the cluster point code, using the chg-dstn command.

    If the rcause, nprst, and splitiam parameters will be specified for the cluster point code, one or more of the features shown in 4 must be enabled.

    If the sccpmsgcnv parameter will be specified for the cluster point code, the XUDT UDT Conversion feature, shown in the rtrv-ctrl-feat output in either 4 or 5, must be enabled.

    For this example, enter this command.

    chg-dstn:dpca=030-003-*:clli=ls09clli:ncai=no:elei=no:nprst=on:rcause=5 :splitiam=20:sccpmsgcnv=xudt2udt

    When this command has successfully completed, this message should appear.

    
    rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   20
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  22
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  28
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    CHG-DSTN: MASP A - COMPLTD
    

11. Verify the changes using the rtrv-dstn command, and specifying the cluster point code that was entered in 10 with the dpca parameter.

    For this example, enter this command.

    rtrv-dstn:dpca=030-003-*

    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
       030-003-*     ls09clli    yes no  --------------   --------------  SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no           5      on      20     no     no    xudt2udt
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   20
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  22
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  28
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

12. 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.
    

Network routing allows the user to provision a single routeset that can used for all MSUs destined to members of that network. The advantages of network routing are:

• Reduces the number of entries in the route table
• Allows routing to members of a network without having to add those members to the route table

A EAGLE user can connect to a remote network by provisioning a single route table element. As the remote network grows, the EAGLE user does not have to add new route table entries for each new point code in the remote network.

Applications

Network routing is very useful when the destination node is very far away from the source node. The reliability of network routing increases when the destination is further away. Notice that in Figure 2-27, routing from network A is more reliable to nodes in network C than to nodes in network B.

Figure 2-27 Example of Network Routing Reliability

If the nodes in network A use network routing for network C, network A can still route traffic to SSP C, even if two linksets fail. In this example, one of the A-linksets to SSP C and the C-linkset between node C1 and node C2 fail. In this case, the EAGLE in network A continues to route half its traffic to node B1, and half to node B2. Node B1 and node B2 (which do not use network routing) route all traffic for SSP C through node C2.

If the nodes in network A use network routing for network B, traffic going to SSP B may be lost if two linksets fail. In this example, one of the A-linksets to SSP B and the C-linkset between node B1 and node B2 fail. In this case, the EAGLE in network A continues to route half its traffic to node B1, and half to node B2. Traffic for SSP B routed through node B1 is discarded, resulting in message loss.

Route Availability

A route is one path to a destination. A routeset is a list of paths to a destination. Route availability consists of two parts:

• Local availability
• Remote availability

Remote availability is affected by TFx network management messages. Local availability is affected by linkset failures and recoveries. TFx messages do not affect point codes accessed by network route entries. Therefore, for network route entries, route availability consists of only local availability. The highest priority linkset available for traffic is used for routing MSUs, regardless of the remote availability of that route.

Figure 2-28 Potential Routing Network Failure

In the example in Figure 2-28, linksets LS-C and LS-D form a combined route to network route 7-*-*. Because 7-*-* is a network route, the EAGLE always considers the non-adjacent status of the routes to be allowed. In the example shown, the EAGLE routes traffic destined to 7-7-1 over LS-C and LS-D. The EAGLE ignores TFPs concerning 7-7-1 or TCPs concerning 7-7-*.

E2169 Cmd Rej: Point code out of range

1. Display the current destination point codes using the rtrv-dstn 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          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      001-002-003   ls04clli    yes --- ----------      --------------   SS7
      030-045-*     rlghncbb010 yes yes ----------      --------------   SS7
      111-011-*     rlghncbb000 yes yes ----------      --------------   SS7
      240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3     SS7
      240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
      240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1    SS7
      240-012-008   ----------- yes ---    1-113-5         10-13-10-2    SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
      2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1     SS7
      2-131-2       ----------- no  ---    222-211-001     11-11-8-2     SS7
      2-131-3       ----------- no  ---    222-211-002     11-11-8-3     SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
      10-15-2-3     rlghncbb013 no  ---    222-200-200     2-121-1       SS7
      10-15-3-0     rlghncbb013 no  ---    222-200-201     2-121-2       SS7
   
   
   DESTINATION ENTRIES ALLOCATED:   6000
       FULL DPC(s):                   14
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  16
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  18
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   If the addition of the network routing point code will not exceed the current DPC capacity shown in the rtrv-dstn output, continue the procedure with 2.

   If the addition of the network routing point code will exceed the current DPC capacity, and the current capacity is less than 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Changing the DPC Quantity procedure to change the DPC quantity. Continue the procedure with 2.

   If the addition of the network routing point code will exceed the current DPC capacity, and the current capacity is 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Removing a Destination Point Code procedure to remove a DPC or perform the Removing a Route Exception Entry procedure to remove an exception route. Continue the procedure with 2.

2. Verify that the network routing feature is on, by entering the rtrv-feat command.

   If the network routing feature is on, the NRT field should be set to on. For this example, the network routing 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 Commands User's Guide.

   If the network routing feature is on, continue the procedure with 4.

3. If the network routing feature is not on, shown by the NRT = off entry in the rtrv-feat command output of 2, turn the network routing feature on by entering this command.
   chg-feat:nrt=on

   Note:

   Once the network routing feature is turned on with thechg-feat command, it cannot be turned off.

   The network routing 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 network routing feature, contact your Oracle Sales Representative or Account Representative.

   When the chg-feat has successfully completed, this message should appear.

   
   rlghncxa03w 07-05-07 00:57:31 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

   Continue the procedure by performing one of these steps.

   • If you wish to enter a network routing point code with the network indicator values 1 through 5, and the network indicator values 1 through 5 are not shown in the rtrv-dstn output in 1, perform 4 to verify the pctype value.
   • If ANSI point codes are not shown in the rtrv-dstn output in 1, perform 4 to verify that an ANSI point code is assigned to the self-identification of the EAGLE.
   • If the rtrv-dstn output in 1 shows ANSI point codes or shows ANSI point codes that contain the network indicator values 1 through 5, or you do not wish to provision a network routing point code with the network indicator values 1 through 5, continue the procedure by performing one of these steps.
     • If the nprst, rcause, or splitiam parameters will not be specified for the cluster point code, continue the procedure with 6.
     • If the nprst, rcause, or splitiam parameters will be specified for the cluster point code, continue the procedure with 5.
4. Display the self-identification of the EAGLE using the rtrv-sid command.

   This is an example of the possible output.

   
   rlghncxa03w 07-05-10 11:43:04 GMT  EAGLE5 37.0.0
   
      PCA             PCI          PCN                CLLI              PCTYPE
      100-100-100     3-75-7       7-9-8-1            rlghncxa03w       OTHER
   
      CPCA
      002-002-002       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
   
      CPCA (LNP)
      005-005-002       005-005-004       005-005-005
   
      CPCI
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
   
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2         2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1
   

   To enter an ANSI destination point code with the ent-dstn command, a point code must be shown in the PCA field of the rtrv-sid command output.

   If the required point code is not shown in the PCA field of the rtrv-sid command output, perform the Changing the Self-Identification of the EAGLE procedure to configure the required point codes.

   To enter a network routing point code with the network indicator values 1 through 5, the pctype parameter value of the chg-sid command must be set to other. If you wish to enter a network routing point code with a network indicator value 1 through 5, and the pctype parameter value is ansi, perform the Changing the Self-Identification of the EAGLE procedure to change the pctype value to other.

   Continue the procedure by performing one of these steps.

   • If the nprst, rcause, or splitiam parameters will not be specified for the cluster point code, continue the procedure with 6 .
   • If the nprst, rcause, or splitiam parameters will be specified for the cluster point code, continue the procedure with 5.
5. Display the features that are enabled by entering the rtrv-ctrl-feat command. This is an example of the possible output.

   
   rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   HC-MIM SLK Capacity       893012707 on     64
   TIF Number Portability    893018901 off    ----
   
   
   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.
   

   To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.

   • TIF Number Portability - part number 893018901
   • TIF SCS Forwarding - part number 893022201
   • TIF Simple Number Substitution - part number 893024001
   • TIF Additional Subscriber Data - part number 893024501
   • TIF Generic Routing Number - part number 893025501

   Perform the procedures in TIF User's Guide to enable these features as required.

6. Continue the procedure by performing one of these steps.
   • Continue the procedure with 8 if any of these conditions are present.
     • The sccpmsgcnv parameter will not be specified for the cluster point code.
     • The sccpmsgcnv parameter will be specified for the cluster point code and the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is enabled and turned on. If the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT to enable and turn on the XUDT UDT Conversion feature.
   • Continue the procedure with 7 if the sccpmsgcnv parameter will be specified for the cluster point code and 5 was not performed.
7. Enter this command to verify the status of the XUDT UDT Conversion feature.

   rtrv-ctrl-feat:partnum=893035301

   This is an example of the possible output.

   
   rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   XUDT UDT Conversion       893035301 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 XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

   If the XUDT UDT Conversion feature is enabled and turned on, or the "Activating the XUDT UDT Conversion Feature" procedure was performed in this step, continue the procedure with 8.

8. Add the network routing destination point code, using the ent-dstn command.

   For this example, enter this command.

   ent-dstn:dpca=007-*-*:rcause=50:nprst=on:splitiam=25:sccpmsgcnv=sxudt2udt

   When this command has successfully completed, and the Cluster Routing and Management Diversity feature is turned off (shown with the CRMD = off entry in the rtrv-feat command output), this message should appear.

   
   rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
   Destination table is (17 of 2000) 1% full 
   ENT-DSTN: MASP A - COMPLTD
   

   If the Cluster Routing and Management Diversity feature is turned on (CRMD = on in the rtrv-feat command output), this message should appear when each command has successfully completed.

   
   rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
   DESTINATION ENTRIES ALLOCATED:   6000
       FULL DPC(s):                   14
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 1
       CLUSTER DPC(s):                 2
       TOTAL DPC(s):                  17
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  18
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   ENT-DSTN: MASP A - COMPLTD
   

9. Verify the changes using the rtrv-dstn command and specifying the DPC that was entered in 8.

   For this example, enter this command.

   rtrv-dstn:dpca=007-*-*

   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
      007-*-*       ----------- yes --- ----------      --------------   SS7
   
      SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
      -----------  ----         50     on    25       no     no    sxudt2udt
   
   Destination table is (14 of 2000) 1% full
   Alias table is (18 of 8000) 1% full
   

10. 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.