Changing the Self-Identification of the EAGLE

This procedure is used to change the self-identification of the EAGLE using the chg-sid command. The self-identification of the EAGLE is a set of point codes made up of a true point code (PC) and a capability point code (CPC) for each network type to which the EAGLE is connected. A capability point code identifies a group of nodes that have similar capabilities, for example, global title translation.

Caution:

Use this procedure only during periods of low traffic. If the EAGLE’s point code, defined by the pc/pca/pci/pcn/pcn24 parameter, is changed with the procedure, the EAGLE must be reinitialized with the init-sys command. The init-sys command reboots the entire EAGLE and reloads all cards with the updated self-identification information.

Therstrdev value of thechg-stpopts command can be used to turn on the Persistent Device States (PDS) feature. If PDS is on, the current device states for cards, signaling links, and terminals are restored after the init-sys command has executed. Refer to the chg-stpopts command description in Commands User's Guide for more information about PDS.

Note:

If the PCA, PCI, PCN, or PCN24 fields in the rtrv-sid output do not contain any values, and you only wish to add these values, it is recommended that the “Adding a Point Code to the Self-Identification of the EAGLE” procedure procedure be used to add these values instead of using this procedure as the “Adding a Point Code to the Self-Identification of the EAGLE” procedure does not require the EAGLE to be re-initialized after the point code value is added.

The chg-sid command uses these parameters:

:pc/pca/pci/pcn/pcn24 – The point code used to uniquely identify the EAGLE or, with the value none, the point code is defined by the pc/pca/pcn24 parameter is removed from the database. Removing the pci or pcn value should be done by using the npci or npcn parameters.

:cpc/cpca/cpci/cpcn/cpcn24 – The point code used to identify a group of functionally related nodes in the signaling network to which the EAGLE belongs. This point code is called the capability point code.

:ncpc/ncpca/ncpci/ncpcn/ncpcn24 – The new capability point code that replaces an existing capability point code in the database or, with the value none, removes an existing capability point code from the database.

:npci/npcn – The new ITU-I (npci) or 14-bit ITU-N (npcn) point code used to uniquely identify the EAGLE that replaces an existing pci or pcn parameter value, with the value none, removes an existing pci or pcn parameter value from the database. The npci/npcn parameter values cannot be equal to any cpc or pc parameter values. The pci parameter must be specified if the npci parameter is specified. The pcn parameter must be specified if the npcn parameter is specified. The new ITU-I or 14-bit ITU-N point code values (npci/npcn) must be the same type as the pci/pcn parameter value. For example, if the pci value is a non-spare point code, the npci value must be a non-spare point code. If the pci value is a spare point code, the npci value must be a spare point code.

Note:

See Point Code Formats for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

:clli – The Common Language Location Identifier assigned to the EAGLE

:pctype – Point code type, either ansi or other.

:cpctype – the type of capability point code: STP, LNP, INP, EIR, GPORT, GFLEX, MNP, VFLEX, ATINPQ, AIQ.

The self-identification of the EAGLE can consist of an ANSI point code, an ITU international non-spare point code, an ITU international spare point code, a 14-bit ITU national non-spare point code, a 14-bit ITU national spare point code, or a 24-bit ITU national point code, or combinations of these types of point codes. The self-identification of the EAGLE cannot have both a 14-bit ITU-N point code (spare or non-spare) and a 24-bit ITU-N point code.

The self-identification of the EAGLE must contain point codes whose formats match the network the EAGLE is connected to. For example, if the EAGLE is connected to an ANSI network, the self-identification of the EAGLE must contain an ANSI point code. If the EAGLE is connected to an ITU international network, the self-identification of the EAGLE must contain an ITU international point code. If the EAGLE is connected to an ITU national network, the self-identification of the EAGLE must contain either a 14-bit or a 24-bit ITU national point code.

The self-identification of the EAGLE can contain capability point codes. A capability point code is used by the SS7 protocol to identify a group of functionally related nodes in the signaling network. The self-identification of the EAGLE can contain up to 96 capability point codes which can be all one point code network type, or a mixture of all three point code network types.

The EAGLE can contain an ANSI capability point code, an ITU national capability point code (spare or non-spare), and either a 14-bit (spare or non-spare) or a 24-bit ITU-N capability point code.

Note:

The self-identification of the EAGLE cannot contain private point codes, and private point codes cannot be assigned as capability point codes.

ITU international and 14-bit ITU national spare point codes can be specified only if the ITU National and International Spare Point Code Support feature is enabled. The status of this feature can be verified by entering the rtrv-ctrl-feat command. 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 to enable the ITU National and International Spare Point Code Support feature.

The self-identification of the EAGLE can also contain a CLLI, the common language location identifier of the EAGLE.

The CLLI of the EAGLE cannot match the CLLI of any destination point code. Use the rtrv-dstn command to verify the CLLIs of the destination point codes in the database.

If the CLLI of the Eagle is changed and the SEAS over IP feature is enabled and turned on, the CCSMR configuration must be updated with the new CLLI. Perform the procedures in the "SEAS over IP Configuration Procedures" chapter in the Database Administration - System Management User's Guide to update the CCSMR configuration.

If the CLLI of the EAGLE is to be changed, and the Eagle Support for Integrated Sentinel (E5IS) feature is on, the EISCOPY option must be off before the chg-sid command is executed. The value of the EISCOPY option can be verified with the rtrv-eisopts command. After the chg-sid command is executed, the EISCOPY option must be changed back to on.

Capability point codes are specified with the cpctype parameter with the capability point code parameters, cpc/cpca/cpci/cpcn/cpcn24, or the new capability point code parameters, ncpc/ncpca/ncpci/ncpcn/ncpcn24. The EAGLE supports these types of capability point codes.

STP capability point codes are specified with the cpctype=stp parameter. STP capability point codes can be any point code type. STP capability point codes can be specified regardless of which features are enabled or turned on.
LNP capability point codes are specified with the cpctype=lnp parameter. LNP capability point codes can be only ANSI point codes, specified with either the cpc, cpca,ncpc, or ncpca parameters. The LNP feature must be enabled to specify the cpctype=lnp parameter. This can be verified with the rtrv-ctrl-feat command. If the LNP feature is enabled, the entry LNP TNs is shown in the rtrv-ctrl-feat command output with a quantity greater than zero.
If any of these capability point codes are shown in the rtrv-sid output: INP, EIR, G-Port, G-Flex, MNP, V-Flex, ATINPQ; then LNP capability point codes cannot be provisioned. If any of these features are enabled, and turned on if required: INP, ANSI-41 INP Query, EIR, G-Port, A-Port, G-Flex, IS41 GSM Migration, V-Flex, ATINP; then LNP capability point codes cannot be provisioned. If the LNP feature is not enabled, perform the procedures in ELAP Administration and LNP Feature Activation User's Guide to enable the LNP feature.
INP capability point codes are specified with the cpctype=inp parameter. INP capability point codes can be either an ITU-I, 14-bit ITU-N, or 24-bit ITU-N point code, specified with either the cpci, cpcn, cpcn24, ncpci, ncpcn, or ncpcn24 parameters. The INP or ANSI-41 INP Query feature must be enabled and turned on to specify the cpctype=inp parameter. Enter the rtrv-ctrl-feat command to verify whether or not the INP or ANSI-41 INP Query feature is enabled and turned on.
If LNP capability point codes are shown in the rtrv-sid output, or the LNP feature is enabled, INP capability point codes cannot be provisioned. If either the INP or ANSI-41 INP Query feature is not enabled or turned on, perform the procedures in the INP/AINPQ User's Guide to enable and turn on the INP or ANSI-41 INP Query feature.
EIR capability point codes are specified with the cpctype=eir parameter. EIR capability point codes can be either an ITU-I, 14-bit ITU-N, or 24-bit ITU-N point code, specified with either the cpci, cpcn, cpcn24, ncpci, ncpcn, or ncpcn24 parameters. The EIR feature must be enabled and turned on to specify the cpctype=eir parameter. Enter the rtrv-ctrl-feat command to verify whether or not the EIR feature is enabled and turned on.
If LNP capability point codes are shown in the rtrv-sid output, or the LNP feature is enabled, EIR capability point codes cannot be provisioned. If the EIR feature is not enabled or turned on, perform the procedures in EIR User's Guide to enable and turn on the EIR feature.
G-Flex capability point codes are specified with the cpctype=gflex parameter. G-Flex capability point codes can be any point code type. The G-Flex feature must be enabled and turned on to specify the cpctype=gflex parameter. Enter the rtrv-ctrl-feat command to verify whether or not the G-Flex feature is enabled and turned on. If LNP capability point codes are shown in the rtrv-sid output, or if the LNP feature is enabled, G-Flex capability point codes cannot be provisioned. If the G-Flex feature is not enabled or turned on, perform the procedures in G-Flex User's Guide to enable and turn the G-Flex feature on.
G-Port capability point codes are specified with the cpctype=gport parameter. G-Port capability point codes can be any point code type. The G-Port feature must be enabled to specify the cpctype=gport parameter. Enter the rtrv-ctrl-feat command to verify whether or not the G-Port feature is enabled. If LNP or MNP capability point codes are shown in the rtrv-sid output, or the LNP, A-Port, or IS41 GSM Migration features are enabled, G-Port capability point codes cannot be provisioned. If the G-Port feature is not enabled, perform the procedures in G-Port User's Guide to enable the G-Port feature.
MNP capability point codes are specified with the cpctype=mnp parameter. MNP capability point codes can be any point code type. The A-Port feature or IS41 GSM Migration feature must be enabled to specify the cpctype=mnp parameter. Enter the rtrv-ctrl-feat command to verify whether or not the A-Port feature or IS41 GSM Migration feature is enabled. If LNP or G-Port capability point codes are shown in the rtrv-sid output, or the LNP or G-Port features are enabled, MNP capability point codes cannot be provisioned. If the A-Port feature is not enabled, perform the procedures in A-Port User's Guide to enable the A-Port feature. If the IS41 GSM Migration feature is not enabled, perform the procedures in IS41 GSM Migration User's Guide to enable the IS41 GSM Migration feature.
V-Flex capability point codes are specified with the cpctype=vflex parameter. V-Flex capability point codes can be any point code type. The V-Flex feature must be enabled and turned on to specify the cpctype=vflex parameter. Enter the rtrv-ctrl-feat command to verify whether or not the V-Flex feature enabled and turned on. If LNP capability point codes are shown in the rtrv-sid output, or the LNP feature is enabled, V-Flex capability point codes cannot be provisioned. If the V-Flex feature is not enabled or turned on, perform the procedures in V-Flex User's Guide to enable and turn on the V-Flex feature.
ATINPQ capability point codes are specified with the cpctype=atinpq parameter. ATINPQ capability point codes can be either an ANSI, ITU-I, or 14-bit ITU-N point code, specified with either the cpc/cpca, cpci, cpcn, ncpc/ncpca, ncpci, or ncpcn parameters.
The ATINP feature must be enabled to specify the cpctype=atinpq parameter. Enter the rtrv-ctrl-feat command to verify whether or not the ATINP feature is enabled. If LNP capability point codes are shown in the rtrv-sid output, or the LNP feature is enabled, ATINPQ capability point codes cannot be provisioned. If the ATINP feature is not enabled, perform the procedures in ATINP User's Guide to enable the ATINP feature.
AIQ capability point codes are specified with the cpctype=aiq parameter. AIQ capability point codes can be either an ANSI, ITU-I, or 14-bit ITU-N point code, specified with either the cpc/cpca, cpci, cpcn, ncpc/ncpca, ncpci, or ncpcn parameters.
The ANSI41 AIQ feature must be enabled to specify the cpctype=aiq parameter. Enter the rtrv-ctrl-feat command to verify whether or not the ANSI41 AIQ feature is enabled. AIQ capability point codes can be specified regardless of which features, other than the ANSI41 AIQ feature, are enabled or turned on. If the ANSI41 AIQ feature is not enabled, perform the procedures in the Analyzed Information Features User's guide to enable the ANSI41 AIQ feature.

The pctype parameter of the chg-sid command determines the format of point codes (but not the ITU international or ITU national point codes) that can be used on the EAGLE, ansi and other. The value ansi means the EAGLE supports point codes that meet the ANSI standard. The value other means that the EAGLE supports point codes that do not meet the ANSI standard. The pctype parameter does not apply to ITU international or ITU national point codes. See the “ANSI Point Codes” in the Point Code Formats section for more information about ANSI point codes.

This procedure causes a change in the routing information for this node. Make sure that all other nodes that route messages to this node are notified of these changes.

The point code of the EAGLE cannot match the capability point codes of the EAGLE. The point code of the EAGLE and the capability point codes of the EAGLE are shown in 1.

The point code and capability point codes of the EAGLE cannot match any destination point codes. Use the rtrv-dstn command to display the destination point codes in the database.

The point code and capability point codes of the EAGLE cannot be defined as a destination point code of a route. Use the rtrv-rte command to display the destination point codes of the routes in the database.

The point code and capability point codes of the EAGLE cannot match any emulated point code (EPC) values that are shown in the rtrv-pct output

The point code of the EAGLE or the capability point codes, specified by the pc/pca/pci/pcn/pcn24, cpc/cpca/cpci/cpcn/cpcn24 or ncpc/ncpca/ncpci/ncpcn/ncpcn24 parameters, must be a full point code and cannot be a cluster point code. A point code containing all zeros cannot be used as a value for ANSI (pc/pca, cpc/cpca, ncpc/ncpca) and ITU-I (pci, cpci, ncpci) parameters. A point code containing all zeros can be used as a value for 14-bit ITU-N (pcn, cpcn, ncpcn) and 24-bit ITU-N (pcn24, cpcn24, ncpcn24) parameters.

If either the cpctype parameter or the capability point code parameter (cpc/cpca/cpci/cpcn/cpcn24) are specified, the other parameter must be specified.

If the new capability point code parameter (ncpc/ncpca/ncpci/ncpcn/ncpcn24) is specified, the capability point code parameter (cpc/cpca/cpci/cpcn/cpcn24) and the cpctype parameters must be specified.

Only one of the new capability point code parameters (ncpc/ncpca/ncpci/ncpcn/npcn24) can be specified with the chg-sid command.

The new capability point code (ncpc/ncpca/ncpci/ncpcn/npcn24) must be of the same point code type as the capability point code (cpc/cpca/cpci/cpcn/cpcn24) specified in the command. For example, if an ITU international capability point code (cpci) is being replaced, then only the ncpci parameter can be specified.

The point code of the EAGLE cannot be changed if it is referenced in the mated application table. Enter the rtrv-map command to verify if the EAGLE’s point code is being referenced in the mated application table. The EAGLE’s point code would be shown in the PCA, PCI, PCN, PCN24, MPCA, MPCI, MPCN, or MPCN24 fields of the rtrv-map command output. If the EAGLE’s point code is referenced by the mated application table, perform the Removing a Mated Application procedure in Database Administration - GTT User's Guide, and remove the mated applications that reference the EAGLE’s point code.

The destination point codes and alias point codes are shown in the DPCA, DPCI, DPCN, DPCN24, ALIASA, ALIASI, ALIASN, and ALIASN24 fields in the rtrv-dstn command output. Secondary point codes are shown in the SPCA, SPCI, SPCN, and SPCN24 fields in the rtrv-spc command output. The EAGLE’s point code and capability point codes are displayed in the PCA, PCI, PCN, PCN24, CPCA, CPCI, CPCN, and CPCN24 fields in the rtrv-sid command output. The EAGLE’s true point code and capability point codes cannot be shown in either the rtrv-dstn or rtrv-spc command outputs.

To assign group codes to a 14-bit ITU-N point code, the ITU duplicate point code and multiple point code support features must be on. If the ITU National Duplicate Point Code feature is on, the entry ITUDUPPC = on is shown in the rtrv-feat command output. If the multiple point code support feature is on, the entry MPC = on is shown in the rtrv-feat command output. For more information on using group codes with 14-bit ITU-N point codes, see the ITU National Duplicate Point Codes section.

Note:

Once the ITU duplicate point code and multiple point code support features are turned on with the chg-feat command, they cannot be turned off.

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

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. 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 before the pcn24 parameter can be specified. If no value is shown in the PCN field, specifying the npcn=none parameter is not necessary.

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. If no value is shown in the PCN24 field, specifying the pcn24=none parameter is not necessary.

When the EAGLE is initially installed, the self-identification of the EAGLE must be configured before any destination point codes can be configured in the database.

For the examples in this procedure, the self-identification of the EAGLE is being changed to these values:

ANSI point code = 100-100-100

ITU international point code = 3-75-7

14-bit ITU national point code = 7-9-8-1

LNP capability point code = 006-006-006

The format of the 14-bit ITU national point codes used in these examples is 4-4-4-2.

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

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

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

For more information about the canc-cmd command, refer to Commands User's Guide.

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.

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

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.

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.

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.

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.

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

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

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

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

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

Figure 2-20 Changing the Self-Identification of the EAGLE