7.3 LNP Feature Activation Procedure

This procedure contains the basic steps necessary to activate the LNP feature which makes the feature fully operational in the system. Some of the steps refer to other detailed procedures contained in this manual.

Refer to Commands User's Guide for complete descriptions of the EAGLE commands used in this procedure, including parameter names, valid parameter values, rules for using the commands, and output examples.

To make the LNP feature fully operational in the system, actions need to be taken at the LSMS, each ELAP, and the EAGLE.

1. At the EAGLE, perform Step 2 through Step 7.
2. Display the FAK-controlled features that are enabled in the system. Enter the rtrv-ctrl-feat command.

   Note:

   For an LNP ported TNs quantity (the "LNP feature") to be enabled or for the LNP ELAP Configuration feature to be enabled, the following features cannot be enabled:

   • All EPAP-related features
   • MTP Routed Messages for SCCP Applications feature

   If any EPAP-related features or the MTP Routed Messages for SCCP Applications feature are enabled, the LNP feature cannot be enabled; this procedure cannot be performed. If you want to enable the LNP feature, contact My Oracle Support (MOS) for assistance.

   Note:

   The E5-SM4G Throughput Capacity feature and the LNP feature can be enabled at the same time.
   • If both an LNP ported TNs quantity and the EAGLE LNP ELAP Configuration feature are not enabled, perform the LNP Feature Configuration on the EAGLE procedure. Then continue with Step 3.
   • If the LNP ELAP Configuration feature is enabled but the LNP ported TNs entry does not appear in the output, continue with Step 3.
   • If both an LNP ported TNs quantity and the LNP ELAP Configuration feature appear in the command output, continue with Step 3.
3. Verify the state and location of the Service Module cards running the VSCCP application. Enter the rept-stat-card:appl-vsccp command.

   Note:

   DSM cards are not supported. Only E5-SM4G cards and E5-SM8G-B cards running the VSCCP application and the SCCPHC GPL can be used as Service Module cards.
   • If a sufficient number of E5-SM4G and E5-SM8G-B Service Module cards running the SCCPHC GPL and no DSM cards running the VSCCP GPL are in the system, continue with Step 4.
   • If no cards running the VSCCP GPL or the SCCPHC GPL (Service Module cards) are shown in the output, perform the procedure Adding a Service Module in Database Administration - GTT User's Guide to configure and install a sufficient number of E5-SM4G or E5-SM8G-B Service Module cards in the system. Then continue with Step 4.
   • If DSM cards running the VSCCP GPL appear in the output, perform the Removing DSM Cards procedure to remove all DSM cards from the system. Then continue with Step 4.
4. Verify the Service Module card Ethernet configuration to the ELAPs. Enter the rtrv-ip-lnk command.
   • If all Service Module cards have IP links to the ELAPs, continue with Step 5.
   • If the output does not show IP links from some or any Service Module cards to the ELAPs, perform the Configuring the Service Module Card Ethernet Link to the MPS procedure to configure the IP link to ELAP A or ELAP B from each Service Module card that does not have an IP link configured. Then continue with Step 5.
5. Verify that the state of all Service Module cards is IS-NR (In-Service-Normal). Enter the rept-stat-sccp command.

   The state of the Service Module cards is shown in the PST column of the output.

   • If all Service Module cards are in the IS-NR state, continue with Step 6.

   • If the state of any Service Module card is not IS-NR, place each of these cards back into service. Enter the rst-card command for each card, with the loc parameter to specify the location for the card that is shown in the rept-stat-sccp command output. Then continue with Step 6.

6. Test port A of each Service Module card using the ping pass command with the card location of the Service Module card and the IP address for port A of that Service Module card shown in the command output in step 5.
   pass:cmd="ping 192.168.120.1":loc=1301
7. Test port B of each Service Module card using the ping pass command with the card location of the Service Module card and the IP address for port B shown in the command output in Step 5.
   pass:cmd="ping 192.168.121.1":loc=1301
8. At the MPS (ELAP A or B), perform Step 9 through Step 13.
9. Log into ELAP A or B.
10. From ELAP Menu, select Maintenance, and then Display Release Levels to verify that the ELAP version is correct .
    If the ELAP version is not correct, contact My Oracle Support (MOS) for assistance before continuing with this procedure.
11. Perform a health check of the MPS.
    Perform the MPS Health Check Procedure. Then continue with Step 12.
12. Disable the LSMS Connection.
    1. Select Maintenance, and then LSMS Connection, and then View Allowed.
       The View LSMS Connection Allowed dialog box is displayed. See Figure 7-1.

       Figure 7-1 View LSMS Connection Allowed Dialog

       
       
       

       • If the connection is disabled, no action is necessary. Go to Step 13.
       • If the connection is enabled, continue with Step b.
    2. Select Maintenance, and then LSMS Connection , and then Change Allowed.
       The Change LSMS Connection Allowed dialog box is displayed showing the Disable LSMS Connection button. See Figure 7-2.

       Figure 7-2 Change LSMS Connection Allowed Dialog

       
       
       
    3. Click the Disable LSMS Connection button.
       The Change LSMS Connection Allowed dialog box is displayed. See Figure 7-3.

       Figure 7-3 Change LSMS Connection Allowed - Disable Success Dialog

       
       
       
13. Repeat Step 9 through 11(a) for the other ELAP.
    Then continue with Step 14.
14. Verify the telephone number quantity on the ELAP.

    Perform the Verifying RTDB Status at the ELAP User Interface procedure.

    Record the TNs quantity shown in the Counts: line in the RTDB Status, for use in Step 15.

    Continue with Step 15.

15. At the EAGLE, verify the LNP feature quantity if the LNP feature is enabled.

    Enter the rtrv-ctrl-feat command.

    If the LNP ported TNs entry appears in the output, record the quantity shown in the command output.

    If the LNP ported TNs entry does not appear in the output (the LNP feature is not enabled yet), determine the quantity for the LNP feature that will be enabled in Step 16.

    Note:

    The number of telephone numbers on the ELAP (recorded in Step 14) must be less that the configured LNP feature quantity on the EAGLE. If the telephone number quantity on the ELAP is greater that the LNP feature quantity enabled on the EAGLE, the ELAP RTDB is not loaded onto the entire set of Service Module cards on the EAGLE. Some of the Service Module cards load the ELAP RTDB to provide a restricted level of GTT and LNP service. The remainder of the Service Module cards are put into a restricted state. UIM 1323 is generated at the EAGLE. To avoid this situation, make sure when performing Step 16 that the LNP feature quantity configured on the EAGLE is greater than the ELAP telephone number quantity.

    If the telephone number quantity that you recorded from the ELAP in Step 14 is less than the quantity shown in the LNP ported TNs entry in the rtrv-ctrl-feat output or is less than the LNP feature quantity that will be enabled in step 16, continue with Step 16.

16. At the EAGLE, enable the LNP feature for the desired LNP telephone number quantity.
    Perform the LNP Feature Configuration on the EAGLE procedure. Then continue with Step 17.
17. At the LSMS, perform Step 18 through Step 20.
18. Contact My Oracle Support (MOS) to enable the LNP telephone quantity on the LSMS.
19. Create a new EMS for the new MPSs.

    Perform the Creating an EMS Configuration Component procedure.

    Then continue with Step 20.

20. Configure new MPSs in the EMS Routing window.
    Perform the EMS Routing procedure. Then continue with Step 21.
21. At the MPS (ELAP A or B), perform Step 22 through Step 23.
22. Enable the LSMS Connection.
    1. Select Maintenance, and then LSMS Connection, and then View Allowed.
       The View LSMS Connection Allowed dialog box is displayed. See Figure 7-4.

       Figure 7-4 View LSMS Connection Allowed - Connection Enabled Dialog

       
       
       

       • If the connection is enabled, no action is necessary. Go to Step 24.
       • If the connection is disabled, continue with Step 22(b).
    2. Select Maintenance, and then LSMS Connection, and then Change Allowed.
       The Change LSMS Connection Allowed dialog box is displayed showing the Enable LSMS Connection button. See Figure 7-5.

       Figure 7-5 Change LSMS Connection Allowed - Connection Disabled Dialog

       
       
       
    3. Click the Enable LSMS Connection button.
       The Change LSMS Connection Allowed Dialog dialog box is displayed. See Figure 7-6.

       Figure 7-6 Change LSMS Connection Allowed - Enable Success Dialog

       
       
       
23. Repeat Step 22 for the other ELAP.
    Then continue with Step 24.
24. At the LSMS, perform a bulk download or SERVDI (Support ELAP Reload Via Database Image) bulk download to one of the ELAPs.
    Perform the procedures in Bulk Load Procedure or in SERVDI Bulk Download. Then continue with Step 25.
25. At the MPS (the ELAP specified in Step 9), perform Step 26 through Step 27.
26. Copy the bulk downloaded database to the other ELAP; or if the SERVDI procedure is used, restore the RTDB.
    Perform the procedures in Copying One RTDB from Another RTDB, or in Restore RTDB on ELAP for SERVDI. Then continue with Step 27.
27. Perform a health check of the MPS.
    Perform the procedure in MPS Health Check Procedure. Then continue with Step 28.
28. At the EAGLE, distribute the RTDB to each Service Module card in the EAGLE.
    Perform the procedures in Distributing the LNP Database after LSMS-Based Operation or RTDB Copy. Then continue with Step 29.
29. At the MPS (ELAP A or B), perform Step 29 through Step 33.
30. Disable the LSMS Connection.
    1. Select Maintenance, and then LSMS Connection , and then View Allowed.
       The View LSMS Connection Allowed dialog box is displayed. See Figure 7-4.

       Figure 7-7 View LSMS Connection Allowed - Connection Enabled Dialog

       
       
       

       If the connection is disabled, no action is necessary. Continue with Step 31 - Step 32 .

       If the connection is enabled, continue with Step 30(b).

    2. Select Maintenance, and then LSMS Connection, and then Change Allowed.
       The Change LSMS Connection Allowed dialog box is displayed showing the Disable LSMS Connection button. See Figure 7-8.

       Figure 7-8 Change LSMS Connection Allowed - Connection Enabled Dialog

       
       
       
    3. Click the Disable LSMS Connection button.
       The Change LSMS Connection Allowed Dialog is displayed. See Figure 7-9.

       Figure 7-9 Change LSMS Connection Allowed - Disable Success Dialog

       
       
       
31. Repeat Step 29(a) for the other ELAP.
    Then continue with Step 31 - 32.
32. Enable LSMS Connection.
    1. Select Maintenance, and then LSMS Connection, and then View Allowed.
       The View LSMS Connection Allowed dialog box is displayed. See Figure 7-10.

       Figure 7-10 View LSMS Connection Allowed - Connection Enabled Dialog

       
       
       

       If the connection is enabled, no action is necessary. Continue with Step 34.

       If the connection is disabled, continue with Step 31(b).

    2. Select Maintenance, and then LSMS Connection, and then Change Allowed.
       The Change LSMS Connection Allowed dialog box is displayed showing the Enable LSMS Connection button. See Figure 7-11.

       Figure 7-11 Change LSMS Connection Allowed - Connection Disabled Dialog

       
       
       
    3. Click the Enable LSMS Connection button.
       The Change LSMS Connection Allowed dialog box is displayed. See Figure 7-12.

       Figure 7-12 Change LSMS Connection Allowed - Enabled Success Dialog

       
       
       
33. Repeat Step 31 - 32 for the other ELAP.
    Then continue with Step 34.
34. At the LSMS, verify that both EMSs are associated with the LSMS.
    The EMS Status area in the LSMS Console window should show that the EMSs connected to the LSMS are green.

7.3.1 LNP Feature Configuration on the EAGLE

This procedure is performed on the EAGLE to configure the LNP feature.

Refer to Commands User's Guide for complete descriptions of the commands used in this procedure, including parameter names and valid values, rules for using the commands correctly, and output examples.

The LNP feature is a quantity feature that specifies the maximum number of LNP ported TNs that can be defined in the ELAP RTDB. The quantity that can be enabled per EAGLE node ranges from 24 million LNP numbers and number blocks to 756 million LNP numbers and number pool blocks. LNP-related features can provide up to 200,000 LRNs and 350,000 NPANXX numbers on a single node.

The LNP feature prerequisites are ELAP 10.0 and LSMS 12.0 or higher.

The LNP ELAP Configuration feature must be enabled and turned on before the LNP quantity feature can be enabled. The LNP feature is automatically turned on when it is enabled.

The LNP quantity feature and the LNP ELAP Configuration feature must be purchased before they can be enabled on the EAGLE. If you are not sure if you have purchased the desired LNP quantity feature and the LNP ELAP Configuration feature, contact your system administrator or My Oracle Support (MOS).

Refer to the description of the enable-ctrl-feat command in Commands User's Guide for a list of the part numbers for the available LNP telephone number quantities.

After the LNP feature is enabled for a specific quantity, that quantity cannot be reduced. The LNP ELAP Configuration and LNP features cannot be disabled or turned off, and cannot be enabled with a temporary Feature Access Key.

1. Display the status of the EAGLE database by entering the rept-stat-db command.
   The EAGLE database is backed up to the fixed disk and a removable cartridge or medium before the LNP feature is enabled. The removable cartridge or medium that contains the database must be inserted in the removable cartridge drive or USB port.

   • If the RD BKUP field of the rept-stat-db output contains dashes, the removable cartridge drive or USB port does not contain a removable cartridge or medium. If dashes are shown in the RD BKUP field, insert the removable cartridge or medium that contains the database into the removable cartridge drive or USB port.
   • If the removable cartridge or medium is not the one that contains the database, replace the removable cartridge or medium with the one that contains the database.
2. Back up the database using the chg-db:action=backup:dest=fixed command.

   The following messages appear. The active Maintenance and Administration Subsystem Processor (MASP) message 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.
   

3. Back up the database to the removable cartridge or medium using the chg-db:action=backup:dest=remove command.

   The following messages appear:

   
   BACKUP (REMOVABLE) : MASP B - Backup starts on active MASP.
   BACKUP (REMOVABLE) : MASP B - Backup to removable cartridge complete.
   

4. Display the status of the databases by entering the rept-stat-db command.
   • If the databases are not coherent after Step 2 and Step 3 are performed, stop performing this procedure and contact My Oracle Support (MOS).
   • If the databases are coherent after Step 2 and Step 3 are performed, remove the removable cartridge or medium from the removable cartridge drive or USB port and store the removable cartridge or medium in a secure place.
5. Display a summary report of all of the device trouble notifications in the EAGLE by entering the rept-stat-trbl command.
   If any alarms are shown in the rept-stat-trbl output, stop performing this procedure and contact My Oracle Support (MOS).
6. Display the status of the cards in the EAGLE by entering the rept-stat-card command.
   If the PST status of any of the cards shown in the rept-stat-card output is not IS-NR, stop performing this procedure and contact My Oracle Support (MOS).
7. Display the status of the Service Module Cards running the VSCCP application by entering the rept-stat-sccp command.

   Note:

   The rept-stat-sccp command output contains fields that are not used by this procedure. To see the fields displayed by the rept-stat-sccp command, refer to the rept-stat-sccp command description in Commands User's Guide.
8. Display the controlled features that are enabled in the system, by entering the rtrv-ctrl-feat command..
   • If the LNP ELAP Configuration feature entry does not appear in the rtrv-ctrl-feat command output, continue with Step 9.
   • If the rtrv-ctrl-feat output shows the LNP ELAP Configuration feature with Status of off, go to Step 10,
9. Enable the LNP ELAP Configuration feature by entering the following command.
   enable-ctrl-feat:partnum=893010901
10. Turn the LNP ELAP Configuration feature on by entering the following command.
    chg-ctrl-feat:partnum=893010901:status=on
11. Verify the changes by entering the rtrv-ctrl-feat command.
    rtrv-ctrl-feat:partnum=893010901
12. Enable the LNP quantity feature using the enable-ctrl-feat command with the part number of the desired quantity.
    enable-ctrl-feat:partnum=893011012
13. Verify the changes by entering the rtrv-ctrl-feat command with the LNP feature part number that was enabled in Step 12.
14. Verify the changes to the Service Module cards running the VSCCP application by entering the rept-stat-sccp command.
    In the rept-stat-sccp output, the primary state (PST) of each card should be IS-NR, and dashes should be shown in the AST column.

    Note:

    The rept-stat-sccp command output contains fields that are not used by this procedure. To see the fields displayed by therept-stat-sccp command, see therept-stat-sccp command description in Commands User's Guide.
15. Display a summary report of all of the device trouble notifications in the EAGLE by entering the rept-stat-trbl command.
    If any alarms are shown in the rept-stat-trbl output, stop performing this procedure and contact My Oracle Support (MOS).
16. Display the overall status of the ELAP subsystem running on the MPS (Multi-Purpose Server) by entering the rept-stat-mps command.
    If any alarms are shown in the rept-stat-mps output, stop performing this procedure and contact My Oracle Support (MOS).
17. Back up the changes using the chg-db:action=backup:dest=fixed command.
    The following messages 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.
    

18. Display the status of the databases with the rept-stat-db command.

    If the databases are not coherent, or if ELAP A and ELAP B do not have the same birthdate, contact My Oracle Support (MOS).

    If the databases are coherent, and if ELAP A and ELAP B have the same birthdate, this procedure is finished.

7.3.2 Adding an LNP Service

This procedure is used to assign an LNP translation type to a unique LNP service using the ent-lnp-serv command. The ent-lnp-serv command uses these parameters.

Note:

LNP Translation type name referenced in the ENT-LNP-SERV command is different from the Translation type name referenced in ENT-TT command.

:serv – the LNP service assigned to the LNP translation type

:tt – the LNP translation type

:ttn – the LNP translation type name

:dv – the type of digits used by LNP (SCCP, TCAP

:alias – the alias LNP translation type

:on/:off=gttrqd - GTT Required; indicates whether GTT needs to be performed on an LNP MSU before NP Query Service processing or after LNP MR processing.

:gttselid - GTT Selector ID used to perform GTT on an MSU before LNP Query processing or after LNP Message Relay processing

:dfltact - Action taken when a GTT selector search (using the GTT Selector ID from the LNP Service table entry) fails while performing Pre-LNP Query Service GTT processing or Fall-back to GTT after LNP MR Service processing

The LNP feature must be enabled. Verify this by entering the rtrv-ctrl-feat command. If the LNP feature is enabled, the entry LNP ported TNs is shown in the rtrv-ctrl-feat output with a quantity greater than zero.

A maximum of 10 LNP services can be assigned to LNP translation types.

The following LNP MR services can be assigned to LNP translation types:

• CLASS

• CNAM

• LIDB

• ISVM

• LNP Short Message Service (Wireless Short Message Service Center serv=wsmsc)

• Four user-defined services (UDF1, UDF2, UDF3, UDF4).

The following LNP Query services can be assigned to LNP translation types:

• AIN

• IN

• Wireless Number Portability (serv=wnp)

• PCS 1900 Number Portability (serv=pcs)

• LNP Query Service (serv=lnpqs)

• ITU TCAP LRN Query serv=lrnqt

• Four user-defined services (UDF1, UDF2, UDF3, UDF4).

The alias LNP translation type provides an alternate value for the LNP translation type, so that different networks can use different translation type values for the specified LNP service. If the alias translation type in the SCCP Called Party Address is defined in the database as an alias LNP translation type, the alias translation type value is mapped to the associated true LNP translation type value, defined by the tt parameter, in the database to determine the LNP service that is used on the message. All translation type values (0 - 255) can be used as values for the alias parameter, as long as that value is not already in the database as a value for the tt parameter.

The tt and serv parameter combination can be specified only once.

The tt and alias parameters cannot be specified at the same time. To add a new LNP service and an alias translation type for that service, the ent-lnp-serv command must be entered at least twice, depending on how many aliases you wish to enter. The first time the ent-lnp-serv command is entered, the LNP service (serv) and true translation type (tt) is defined in the database. When the ent-lnp-serv command is entered again with the specified LNP service and the alias parameter, the alias translation types (alias) are assigned to the LNP service.

The value of the alias parameter cannot be in the database as an LNP translation type (tt).

The value of the tt parameter cannot be in the database as an alias LNP translation type (alias).

If the serv and tt parameters are specified, the service type specified by the serv parameter cannot be in the database.

Translation type names can be assigned to the LNP service and translation type with the ttn parameter. If the parameter is not specified, the translation type name is set to the LNP service name. The translation type name must be unique in the database. The word none is used as a value for the ttn parameter of the chg-lnp-serv command and cannot be used as a translation type name with the ent-lnp-serv command.

A translation type name can be the service type name only if the service type name matches the value of the serv parameter.

If the value of the serv parameter is a user defined service type, the value of the dv parameter must be sccp.

If the value of the serv parameter is a either ain, in, wnp, pcs, or lnpqs, the value of the dv parameter must be tcap.

The translation type and LNP service specified with the ent-lnp-serv command cannot be in the database.

To specify the serv=wnp parameter with the ent-lnp-serv command, the Wireless Number Portability feature must be turned on. This can be verified with the WNP = on entry in the rtrv-feat command output.

To specify the serv=pcs parameter with the ent-lnp-serv command, the PCS 1900 Number Portability feature must be turned on. This can be verified with the PLNP = on entry in the rtrv-feat command output.

To specify the serv=wsmsc parameter with the ent-lnp-serv command, the LNP Short Message Service (LNP SMS) feature must be enabled and on. This can be verified in the rtrv-ctrl-feat command output. If the LNP SMS feature is not enabled and on, perform the LNP Short Message Service (LNP SMS) Feature Configuration Procedure procedure to enable and turn the LNP SMS feature on.

The LNP service LNPQS defines the translation type used for LNP queries between networks. This service is defined with the serv=lnpqs parameter. While the EAGLE allows any translation type to be assigned to the LNPQS service, it is recommended that translation type 11 is assigned to the LNPQS service. If any LNP service is assigned translation type 11, and you wish to provision the LNPQS service, the existing service using translation type 11 must be changed to use another translation type. Perform the Changing an LNP Service procedure to change the translation type of the existing service. See LNP Query Service (LNPQS) for more information on LNPQS queries.

The examples in this procedure are used to add the LNP services and alias translation types shown in Table 7-9.

Table 7-9 Example LNP Service Configuration

SERV	TT	TTN	DV	ALIAS
IN	30	INGTE	TCAP	---
IN	---	---	----	150
IN	---	---	----	175
UDF3	100	UDF3	SCCP	---
UDF3	---	---	----	40
UDF3	---	---	----	45
AIN	---	---	----	240
LIDB	---	---	----	80
WNP	50	WNP50	TCAP	---
PCS	19	PCS19	TCAP	---
WSMSC	139	WSMSC1	TCAP	---
LNPQS	11	LNPQS	TCAP	---

1. Verify that the LNP feature is enabled by entering the rtrv-ctrl-feat command.
   If the LNP feature is enabled, the entry LNP ported TNs should appear in the rtrv-ctrl-feat output with a quantity greater than 0.
   If the LNP feature is not enabled, perform the procedures in LNP Feature Activation Procedure to enable the LNP feature.
   If the LNP feature is enabled, continue with Step 2.
2. Display the LNP services and translation type assignments in the database with the rtrv-lnp-serv command.
   • If the rtrv-ctrl-feat output in step 1 showed that the LNP feature was not enabled, go to Step 4.
   • If the serv=wnp or serv=pcs parameters will not be specified with the ent-lnp-serv command, go to Step 6.
3. Verify that the Wireless Number Portability feature (if the serv=wnp parameter will be specified in the ent-lnp-serv command) or the PCS 1900 Number Portability feature (if the serv=pcs parameter will be specified in the ent-lnp-serv command), by entering the rtrv-feat command.

   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 thertrv-feat command description in Commands User's Guide.

   If the Wireless Number Portability Feature is on, the entry WNP = on appears in the rtrv-feat output.

   If the PCS 1900 Number Portability Feature is on, the entry PLNP = on appears in the rtrv-feat output.

   Perform Step 4 only if the wireless number portability feature is off and the serv=wnp parameter will be specified with the ent-lnp-serv command.

   Perform Step 5 only if the PCS 1900 number portability feature is off and the serv=pcs parameter will be specified with the ent-lnp-serv command.

4. Turn the Wireless Number Portability Feature on with the chg-feat command.
   Enter this command: chg-feat:wnp=on

   Note:

   Once the Wireless Number Portability feature is turned on with thechg-feat command, it cannot be turned off. The Wireless Number Portability feature must be purchased before you turn the feature on with thechg-feat command. If you are not sure if you have purchased the feature, contact My Oracle Support (MOS).
5. Turn the PCS 1900 Number Portability Feature on with the chg-feat command.
   Enter this command: chg-feat:plnp=on

   Note:

   After the PCS 1900 Number Portability Feature is turned on with the chg-feat command, it cannot be turned off. The PCS 1900 Number Portability feature must be purchased before you turn the feature on with the chg-feat command. If you are not sure if you have purchased the PCS 1900 number portability feature, contact My Oracle Support (MOS).

   Note:

   If you are not assigning a translation type to the WSMSC service, go to Step 7.
6. If the rtrv-ctrl-feat output in Step 1 shows that the LNP SMS feature is enabled and on, go to Step 7.
   If the rtrv-ctrl-feat output in Step 1 shows that the LNP SMS feature is not enabled or on, perform the LNP Short Message Service (LNP SMS) Feature Configuration Procedure procedure to enable and turn the LNP SMS feature on. Continue with Step 7.

   Note:

   If you are not assigning a translation type to the LNPQS service, go to Step 8.

7. Any translation type can be assigned to the LNPQS service, but because translation type 11 is used for LNP queries between networks, it is recommended that translation type 11 is assigned to the LNPQS service.
   Examine the rtrv-lnp-serv output in Step 2 to verify whether or not translation type 11 is assigned to any existing LNP services. If translation type 11 is assigned to any existing LNP services, perform the Changing an LNP Service procedure and change the translation type of the service using translation type 11.
8. Add the LNP services or alias translation types to the database using the ent-lnp-serv command.
   For this example, enter these commands:
   • ent-lnp-serv:serv=in:tt=30:ttn=ingte:dv=tcap
   • ent-lnp-serv:serv=udf3:tt=100:dv=sccp
   • ent-lnp-serv:serv=ain:alias=240
   • ent-lnp-serv:serv=in:alias=150
   • ent-lnp-serv:serv=in:alias=175
   • ent-lnp-serv:serv=lidb:alias=80
   • ent-lnp-serv:serv=udf3:alias=40
   • ent-lnp-serv:serv=udf3:alias=45
   • ent-lnp-serv:serv=wnp:tt=50:ttn=wnp50:dv=tcap
   • ent-lnp-serv:serv=pcs:tt=19:ttn=pcs19:dv=tcap
   • ent-lnp-serv:serv=wsmsc:tt=139:ttn=wsmsc1:dv=tcap
   • ent-lnp-serv:serv=lnpqs:tt=11:ttn=lnpqs:dv=tcap
9. Verify the changes with the rtrv-lnp-serv command.
10. Back up the changes using the chg-db:action=backup:dest=fixed command.
    The following messages 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.
    

7.3.3 Removing an LNP Service

This procedure is used to remove an LNP service from the database using the dlt-lnp-serv command. The dlt-lnp-serv command uses two parameters.

:serv – the LNP service

:alias – the alias LNP translation type assigned to the LNP service

If the alias parameter is specified, the alias translation type value must be assigned to the specified LNP service. The alias translation types are shown in the ALIAS field of the rtrv-lnp-serv command output.

The value of the alias parameter cannot be in the database as a true translation type value. The true translation types are shown in the TT field of the rtrv-lnp-serv command output.

Before an LNP service can be removed from the database, all alias translation types assigned to that service must be removed from the database.

The example in this procedure removes LNP service UDF3 from the database.

1. Display the LNP services and translation type assignments in the database with the rtrv-lnp-serv command.
2. Remove the LNP service from the database using the dlt-lnp-serv command.
   For this example, enter these commands:

   dlt-lnp-serv:serv=udf3:alias=40

   dlt-lnp-serv:serv=udf3:alias=45

   dlt-lnp-serv:serv=udf3

3. Verify the changes with the rtrv-lnp-serv command.
4. Back up the changes using the chg-db:action=backup:dest=fixed command.
   The following messages 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.
   

7.3.4 Changing an LNP Service

This procedure is used to change the attributes of an existing LNP service using the chg-lnp-serv command. The chg-lnp-serv command uses these parameters.

:serv – the LNP service

:nserv – the new LNP service

:tt – the current LNP translation type assigned to the LNP service

:ntt – the new LNP translation type assigned to the LNP service

:nttn – the new LNP translation type name assigned to the LNP service

:ndv – the new digits valid indication for the LNP service

:on/:off=gttrqd - GTT Required; indicates whether GTT needs to be performed on an LNP MSU before NP Query Service processing or after LNP MR processing.

:gttselid - GTT Selector ID used to perform GTT on an MSU before LNP Query processing or after LNP Message Relay processing

:dfltact - Action taken when a GTT selector search (using the GTT Selector ID from the LNP Service table entry) fails while performing Pre-LNP Query Service GTT processing or Fall-back to GTT after LNP MR Service processing

The values of the serv and tt parameters must be in the database.

To change the attributes of an LNP service, either the serv or tt parameters must be specified, but not both parameters. If you are changing the translation type assigned to the LNP service, the serv and ntt parameters must be specified. If you are changing the LNP service assigned to a translation type, the tt and nserv parameters must be specified. The nserv and ntt parameters cannot be specified together in the chg-lnp-serv command.

The new translation type name must be unique in the database.

The new translation type (ntt) cannot be in the database as a true translation type or an alias translation type. The true translation types and alias translation types are shown in the rtrv-lnp-serv command output. The true translation types are shown in the TT field and the alias translation types are shown in the ALIAS field.

The word none sets the translation type name value to the service type name. A translation type name can be the service type name only if the service type name matches the value of the serv parameter.

If the value of the serv parameter is a user defined service type or wsmsc, the value of the ndv parameter must be sccp.

If the value of the serv parameter is a either ain, in, wnp, pcs, or lnpqs, the value of the ndv parameter must be tcap.

If the ndv parameter is specified, the value must be different from the current value of the DV field. The DV value can be changed only for these services: cnam, lidb, isvm, or class.

An LNP service cannot be changed if an alias translation type is assigned to the service. The aliases must be removed from the database using the dlt-lnp-serv command. If you wish to continue using the alias translation types with the LNP service after the LNP service has been changed, they must be re-assigned to the LNP service using the ent-lnp-serv command.

Any translation type can be assigned to the LNPQS service, but it is recommended that translation type 11 is assigned to the LNPQS service. If you are changing the translation type of another service, and the LNPQS service is provisioned in the database, select a translation type other than 11.

The examples in this procedure are used to change the AIN and CLASS services to the values shown in Table 7-10.

Table 7-10 Changing the LNP Service

SERV	TT	NTT	DV	NDV	TTN	NTTN
AIN	15	55	TCAP	----	AINGTE	AINLIDB
CLASS	25	140	SCCP	TCAP	CLASSGTE	CLASS
WNP	50	75	TCAP	---	WNP50	WNP75

1. Display the LNP services and translation type assignments in the database with the rtrv-lnp-serv command.
2. If the LNP service being changed has any alias translation types assigned to it, shown in the ALIAS field in the output of Step 1, remove the alias translation types from the LNP service using the dlt-lnp-serv command.
   If the LNP service does not have any alias translation types assigned to it, go to Step 3. For this example, the AIN service has alias translation types assigned to it. Remove the alias translation types with these commands:
   dlt-lnp-serv:serv=ain:alias=235
   dlt-lnp-serv:serv=ain:alias=236
   dlt-lnp-serv:serv=ain:alias=240
3. Verify that the Wireless Number Portability feature (if the nserv=wnp parameter will be specified in the chg-lnp-serv command) or the PCS 1900 Number Portability (PLNP) feature (if the nserv=pcs parameter will be specified in the chg-lnp-serv command), by entering the rtrv-feat command.

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

   If the Wireless Number Portability feature is on, the entry WNP = on appears in the rtrv-feat output. If the PCS 1900 Number Portability feature is on, the entry PLNP = on appears in the rtrv-feat output. Perform Step 4 only if the Wireless Number Portability feature is off and the nserv=wnp parameter will be specified with the chg-lnp-serv command. Perform Step 3 only if the PCS 1900 Number Portability feature is off and the nserv=pcs parameter will be specified with the chg-lnp-serv command.

4. Turn the Wireless Number Portability feature on with the chg-feat command.

   For this example, enter this command chg-feat:wnp=on

   Note:

   After the Wireless Number Portability feature is turned on with the chg-feat command, it cannot be turned off. The wireless number portability feature must be purchased before you turn the feature on with the chg-feat command. If you are not sure if you have purchased the Wireless Number Portability feature, contact My Oracle Support (MOS).
5. Turn the PCS 1900 Number Portability feature on with the chg-feat command.
   For this example, enter this command.chg-feat:plnp=on

   Note:

   Once the PCS 1900 Number Portability feature is turned on with the chg-feat command, it cannot be turned off. The PCS 1900 Number Portability feature must be purchased before you turn the feature on with the chg-feat command. If you are not sure if you have purchased the PCS 1900 Number Portability feature, contact My Oracle Support (MOS).

   Note:

   If the LNP service name (serv parameter value) is being changed to a service name other than WSMSC, go to Step 7.
6. Verify that the LNP Short Message Service is enabled and on by entering the rtrv-ctrl-feat command.

   If the rtrv-ctrl-feat output shows that the LNP SMS feature is enabled, and on, go to Step 7. If the rtrv-ctrl-feat output shows that the LNP SMS feature is not enabled or on, perform LNP Short Message Service (LNP SMS) Feature Configuration Procedure to enable and turn the LNP SMS feature on.

   Note:

   If only the alias translation type values for the LNP service are being changed, go to Step 9 to add the new alias translation type values.
7. Change the LNP service using the chg-lnp-serv command.
8. Verify the changes with the rtrv-lnp-serv command.
9. To continue using the alias translation types removed in Step 2 with the changed LNP service, or add new alias translation types to the LNP service, add them with the ent-lnp-serv command.
   For this example, the alias translation types removed in Step 2 are added back to the AIN service. Enter these commands:
   ent-lnp-serv:serv=ain:alias=235
   ent-lnp-serv:serv=ain:alias=236
   ent-lnp-serv:serv=ain:alias=240
10. Verify the changes with the rtrv-lnp-serv command.
11. Back up the changes using the chg-db:action=backup:dest=fixed command.
    The following messages 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.
    

7.3.5 Changing LNP Options

This procedure is used to change the LNP configuration options (shown in Table 7-11), using the chg-lnpopts command.

Note:

If LNPOPTS options for the following features need to be changed, do not use this procedure; use the procedures in the indicated section of this manual:

• Triggerless LNP (TLNP - use the procedures in Triggerless LNP Feature Configuration.
• LNP Short Message Service (LNP SMS) - use the procedures in LNP Short Message Service (LNP SMS) Feature Configuration Procedure.

Table 7-11 LNPOPTS Configuration Options

Parameter	Value	Description	Notes
ADMINHIPRI - LNP Database Administration Highest Administrative Priority	Yes	LNP database administration can starve out normal STP updates during LNP administration of 2 TNs per second.
	No	STP and LNP updates receive the same priority. Depending on the system activity level, the performance of LNP updates may be reduced.
AMACTYPE - AMA Call Type	3 digits
AMAFEATID - AMA Feature ID	3 digits
AMASLPID - AMA Slip ID	9 digits
CCP - Copy Charge Parameters	Yes	The EAGLE copies the Charge Number and Charge Party Station type from an LNP AIN query (if present) to the LNP AIN Response message.
	No	The Charge Number and Charge Party Station type are not copied from the AIN query to the AIN Response message.
CIC - Carrier Identification Code	3-4 digits
DRA - Destination Routing Address content	LRNTN	LRN and TN
	LRN	LRN only
FRCSMPLX - Allow Simplex Database Updates	Yes	LNP updates are accepted when the EAGLE is in the simplex mode (when the standby MASP is incoherent, at a different level compared to the active MASP, or unstable).
	No	LNP updates are not accepted when the EAGLE is in the simplex mode (when the standby MASP is incoherent, at a different level compared to the active MASP, or unstable).
GTWYSTP - LNP System is also a Gateway STP	Yes	The system is configured as a Gateway STP running the LNP feature.	The NPAC sends LNP subscriptions that contain capability point codes that do not have routes assigned to them in the EAGLE database.
	No	The EAGLE is not configured as a Gateway STP.
INCSLP - AMA Service Logic ID included in the response	Yes	AMA Service Logic ID is included in the response.
	No	AMA Service Logic ID is not included in the response.
JIPDIGITS - Jurisdiction Information Parameter value	6 digits		The Triggerless LNP (TLNP) feature must be on. See Triggerless LNP Feature Configuration.
JIPPRV - Add Jurisdiction Information Parameter value to IAM	Yes	A Jurisdiction Information Parameter value is added to the IAM.	The Triggerless LNP (TLNP) feature must be on. See Triggerless LNP Feature Configuration.
	No	A Jurisdiction Information Parameter value is not added to the IAM.
LRNDGTS - LRN digits	1-10 digits
NAIV - Name of Address Indicator Value	0-127 digits
SERVPORT - Service Portability	Yes	A protocol setting that allows splitting services between TN and LRN override records.	This setting lets the EAGLE LNP craftsperson update LRN overrides for Message Relay services that are to be supported in the network. The EAGLE then uses the TN gateway point code (NPAC subscription data) for Message Relay services the CLEC wants to provide.
	No	If no LRN override services are provisioned, then the TN gateway point codes (NPAC subscription data) are used to route queries out of the network.	If one or more LRN override services are provisioned, the TN is considered to be ported into the network. In this case, if an LRN override service is requested and the LRN has other services administered, but the requested service is not provisioned, then a UDTS response for the service is provided.
SP - Service Provider ID	4 alphanumeric characters
TNDGTS - TN Digits	1-10 digits
WQREDRCT - Wireless Queries Directed to default GTT	Yes	Allows GTT to treat any wireless LNP (WNP and PLNP) queries that require GT as a normal GTT.	The Wireless Number Portability (WNP) feature or the PCS 1900 Number Portability (PLNP) feature must be on.
	No	Routes all wireless LNP queries (WNP and PCS) that require GTT directly to the local subsystem.
WSMSC10DIG - SCCP GTA Digit Length Indicator for 10 or 11 digits	Yes	The system verifies that either 10 or 11 digits are present in the CdPA GTA. If 11 digits are present, the first digit is stripped to derive 10 digits for LNP SMS translation. If 10 digits are present, all 10 digits are used for LNP WSMSC translation.	The LNP SMS feature must be on. See LNP Short Message Service (LNP SMS) Feature Configuration Procedure.
	No	The system verifies that 11 digits (plus a padded 0 digit) are present in the CdPA GTA. If 11 digits are present, the system strips the first digit and considers only 10 digits for LNP WSMSC translation.

The LNP feature must be enabled before the LNPOPTS options can be configured.

The value is not changed for any option that is not specified in the chg-lnpopts command.

1. Verify that the LNP feature is enabled by entering the rtrv-ctrl-feat command.
   If the LNP feature is enabled, the LNP ported TNs entry appears in the rtrv-ctrl-feat output with a quantity greater than 0.
   • If the LNP feature is enabled, continue with Step 2.
   • If the LNP feature is not enabled, perform the procedures in LNP Feature Activation Procedure to enable the LNP feature. Then continue with Step 2.
2. Display the LNP option values in the database. Enter the rtrv-lnpopts command.
3. If the wqredrct option will be changed in this procedure, verify that the Wireless Number Portability (WNP) feature or the PCS 1900 Number Portability (PLNP) feature is on . Enter the rtrv-feat command.
   • If the wqredrct option will not be specified in this procedure, go to Step 5.
   • If the wqredrct option will be specified in this procedure, continue with this step.

   If the WNP feature is on, the entry WNP = on appears in the rtrv-feat output.

   If the PLNP feature is on, the entry PLNP = on appears in the rtrv-feat output.

   • If the WNP feature or the PLNP feature or both features are on, go to Step 5.
   • If the WNP feature or the PLNP feature or both features are not on, continue with Step 4.
4. Turn on the WNP feature or the PLNP feature or both features.

   The Wireless Number Portability and PCS 1900 Number Portability features must be purchased before you turn these features on with the chg-feat command. If you are not sure if you have purchased these features, contact My Oracle Support (MOS).

   Note:

   After the Triggerless LNP, Wireless Number Portability or PCS 1900 Number Portability features are turned on with the chg-feat command, they cannot be turned off.

   To turn on the Wireless Number Portability feature, enter the chg-feat:wnp=on command.

   To turn on the PCS 1900 Number Portability feature, enter the chg-feat:plnp=on command.

   To turn on both features in the same command, enter the chg-feat:wnp=on:plnp=on command.

5. Change the LNP option values that need to be changed, using the chg-lnpopts command.
6. Verify the changes with the rtrv-lnpopts command.
7. 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.
   

7.3.6 Changing the LNP Telephone Number Alarm Thresholds

This procedure is used to change the alarm thresholds for generating alarms when the LNP Telephone number quantity has exceeded the defined percentage of the maximum number of LNP telephone numbers the EAGLE can contain. The alarm thresholds are changed using the chg-th-alm command and these parameters:

:lnptndblv1 – The percentage, from 0 to 100, of the maximum number of LNP telephone numbers the EAGLE can contain that generates major alarm UAM 0288. The system default value for the lnptndbvl1 parameter is 90. The current value of this parameter is shown in the LNP TN DB Alarm Level 1: field of the rtrv-th-alm command output.

:lnptndblv2 – The percentage, from 0 to 100, of the maximum number of LNP telephone numbers the EAGLE can contain that generates critical alarm UAM 0287. The system default value for the lnptndbvl2 parameter is 95. The current value of this parameter is shown in the LNP TN DB Alarm Level 2: field of the rtrv-th-alm command output.

The chg-th-alm command contains other optional parameters. These parameters are not shown here because they are not necessary to provision the LNP telephone number alarm thresholds. These parameters are explained in more detail in Commands User's Guide.

The maximum number of LNP telephone numbers the EAGLE can contain is shown in the rtrv-ctrl-feat command output or in the TN: row in the PROVISIONED TABLE QTY: section of the rept-stat-lnp command output.

1. Display the current LNP telephone number alarm thresholds by entering the rtrv-th-alm command.
   This is an example of the possible output.

   
   rlghncxa03w 06-08-28 09:12:36 GMT EAGLE5 35.1.0
   LNP TN  DB Alarm Level 1:            80% 
   LNP TN  DB Alarm Level 2:            90% 
   Command Executed
   

   Note:

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

2. Change the LNP telephone number alarm thresholds by entering the chg-th-alm command with at least one of the LNP telephone number alarm thresholds.
   One or both LNP telephone number alarm threshold parameters can be specified with the chg-th-alm command. If a parameter is not specified with the chg-th-alm command, that parameter value will not be changed. However, after the chg-th-alm command is performed, the lnptndblv2 parameter value must be greater than the lnptndblv1 parameter value. For this example, enter this command:
   chg-th-alm:lnptndblv1=70:lnptndblv2=80
   When this command has successfully completed, this message should appear.

   
   rlghncxa03w 06-08-28 09:12:36 GMT EAGLE5 35.1.0
   CHG-TH-ALM: MASP A - COMPLTD
   

3. Verify the changes using the rtrv-th-alm command.
   This is an example of the possible output.

   
   rlghncxa03w 06-08-28 09:12:36 GMT EAGLE5 35.1.0
   LNP TN  DB Alarm Level 1:            70% 
   LNP TN  DB Alarm Level 2:            80% 
   Command Executed
   

   Note:

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

4. Backup 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.
   

7.3.7 Adding a Subsystem Application

This procedure is used to reserve a subsystem number for the LNP application and place the LNP application either online or offline using the ent-ss-appl command. The ent-ss-appl command uses the following parameters:

:appl – the application type, LNP

:ssn – the LNP subsystem number

:stat – the state of the LNP application

The LNP feature must be enabled. Verify this by entering the rtrv-ctrl-feat command. If the LNP feature is enabled, the entry LNP ported TNs should appear in the rtrv-ctrl-feat output with a telephone quantity greater than 0. If the LNP feature is not enabled, perform the procedures in LNP Feature Activation Procedure to enable the LNP feature.

Only one subsystem number for each application can be defined.

If the stat parameter is not specified, the application will be offline.

The LNP application applies to both global title translation services and LNP queries.

The application specified by the appl parameter cannot already be in the database.

Before the subsystem application can be added to the database, the EAGLE true point code and the subsystem number must be in the mated application table. The EAGLE true point code is verified with the rtrv-sid command and shown in the PCA field. The mated application table is displayed with the rtrv-map command. The EAGLE true point code is shown in the PCA field of the rtrv-map command output and the subsystem number is shown in the SSN field of the rtrv-map command output. If the EAGLE’s true point code and the subsystem number are not shown in the rtrv-map command output, perform one of the “Mated Application” procedure in Database Administration – GTT User's Guide and add the EAGLE true point code and the subsystem to the database.

The example in this procedure reserves the subsystem number 254 for the LNP application and sets the LNP application online.

1. Verify that the LNP feature is enabled by entering the rtrv-ctrl-feat command.
   • If the LNP feature is enabled, the entry LNP ported TNs appears in the rtrv-ctrl-feat output with a quantity greater than 0. If the LNP feature is enabled, continue with Step 1.
   • If the LNP feature is not enabled, perform the procedures in LNP Feature Activation Procedure to enable the LNP feature. Then continue with Step 1.
2. Display the subsystem number for the LNP application in the database with the rtrv-ss-appl command.
3. Display the EAGLE true point code using the rtrv-sid command.
   The EAGLE true point code is shown in the PCA field of the rtrv-sid output.
4. Display the mated applications using the rtrv-map command specifying the EAGLE true point code (shown in Step 3) and the LNP subsystem number.
   For this example, enter teh following command:
   rtrv-map:pca=100-100-100:ssn=254
5. Add the subsystem number for the LNP application using the ent-ss-appl command.
   For this example, enter the following command:
   ent-ss-appl:appl=lnp:ssn=254:stat=online
6. Verify the changes with the rtrv-ss-appl command.
7. Back up the 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.
   

7.3.8 Removing a Subsystem Application

This procedure is used to remove a subsystem application from the database using the dlt-ss-appl command. The dlt-ss-appl command uses only one parameter:

:appl – the subsystem application, LNP .

The subsystem application must be in the database, and the subsystem must be out of service.

1. Display the status of the LNP subsystem with the rept-stat-lnp command.
2. Display the subsystem application number for the LNP application in the database with the rtrv-ss-appl command.
3. Place the LNP subsystem application out of service with the inh-map-ss command specifying the LNP subsystem number displayed in Step 2.
   For this example, enter this command.inh-map-ss:ssn=254
4. Verify that the LNP subsystem is out of service with the rept-stat-lnp command.
5. Remove the LNP subsystem application from the database using the dlt-ss-appl command.

   For this example, enter this command.dlt-ss-appl:appl=lnp

   When the command has successfully completed, the following message appears.

   
   rlghncxa03w 09-04-05 17:34:20 EST  EAGLE 41.0.0
   DLT-SS-APPL: MASP A - CAUTION: DELETED APPL SSN MAY BE REFERENCED BY GTT ENTRY
   DLT-SS-APPL: MASP A - COMPLTD
   ;
   

6. Verify the changes with the rtrv-ss-appl command.
7. Back up the 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.
   

7.3.9 Increasing the LRN and NPANXX Quantities on the EAGLE

When the LNP feature is enabled for the first time for a quantity less than 240 million numbers, the LRN (Location Routing Number) and NPANXX quantities are set at 100,000 LRNs and 150,000 NPANXXs.

When the LNP quantity is 60-228 million numbers, the LRN and NPANXX quantities can be increased to 150,000 LRNs and 300,000 NPANXXs The procedure in this section explains how to increase the quantities. (To increase the current LNP quantity, see the Increasing LNP Telephone Number Quantity on EAGLE procedure.)

When the LNP telephone number quantity is 240-756 million numbers, the LRN and NPANXX quantities are automatically increased to 200,000 LRNs and 350,00 NPANXXs. No action is necessary for the increase.

The current assigned quantities can be verified by entering the rtrv-ctrl-feat command.

The LRN and NPANXX quantities are increased using the enable-ctrl-feat command to specify the optional Feature Access Key (FAK) and part number of the desired LRN quantity feature (part number 893010501) and the NPANXX quantity feature (part number 893009402). The Feature Access Key (FAK), which is provided when the feature is purchased, is based on the feature part number and the serial number of the EAGLE, which means that the Feature Access Key (FAK) is site-specific.

To fully use the increased LRN and NPANXX quantities for 60-756 million LNP numbers, the Measurements Platform must be configured on the EAGLE. If the Measurements Platform is not configured, the measurements for LRNs are capped at 100,000 LRNs, and the measurements for NPANXXs are capped at 150,000 NPANXXs. Measurements for LRN and NPANXX quantities beyond 100,000 LRNs and 150,000 NPANXXs will be truncated. To configure the Measurements Platform, refer to the procedures in Database Administration - System Management User's Guide.

1. Display the status of the LNP-related features. Enter the rtrv-ctrl-feat command and verify the entries for LRN and NPANXX quantities:
   • If the rtrv-ctrl-feat output shows that the LRN quantity is 150,000, and the NPANXX quantity is 300,000, no further action is necessary. This procedure cannot be performed.
   • If the rtrv-ctrl-feat output shows that the LRN quantity is 200,000, and the NPANXX quantity is 350,000, no further action is necessary. This procedure cannot be performed.
   • If the LNP ported TNs quantity shown in the rtrv-ctrl-feat output is 48000000 or less, see Increasing LNP Telephone Number Quantity on EAGLEto increase the LNP telephone number quantity to 60000000 or greater. Then continue with Step 2.
2. Verify the NPANXX and LRN quantities on the ELAP.

   Perform the Verifying RTDB Status at the ELAP User Interface procedure.

   The number of NPANXXs and LRNs on the ELAP must be less that the configured quantity on the EAGLE. If either the NPANXX and LRN quantity on the ELAP is greater that the quantity shown in the rtrv-ctrl-feat output, the ELAP RTDB is not loaded onto the entire set of Service Module cards on the EAGLE. Some of the Service Module cards load the ELAP RTDB to provide a restricted level of GTT/LNP service. The remainder of the Service Module cards are put into a restricted state.

   UIM 1324 is generated at the EAGLE if the NPANXX quantity on the ELAP is greater than the NPANXX quantity configured on the EAGLE.

   UIM 1325 is generated at the EAGLE if the LRN quantity on the ELAP is greater than the LRN quantity configured on the EAGLE.

   To avoid this situation, make sure when performing this procedure that the NPANXX and LRN quantities configured on the EAGLE are greater than the NPANXX and LRN quantities on the ELAP. If the NPANXX and LRN quantity on the ELAP is less that the quantity shown in the rtrv-ctrl-feat output in Step 1, or is less than the quantity that will be configured in this procedure, continue with Step 3.

3. Verify whether or not the Measurements Platform is functioning on the EAGLE.

   Enter the rtrv-feat command. If the Measurements Platform feature is on, the measplat=on entry appears in the command output.

   Enter the rtrv-measopts command. If Measurements Platform collection is enabled, the PLATFORMENABLE = on entry appears in the output.

   Note:

   The rtrv-measopts command output contains other fields that are not used by this procedure. To see all the of the fields that are displayed by the rtrv-measopts command, refer to the rtrv-measopts command description in Commands User's Guide.

   If Measurements Platform collection is not enabled, perform the procedure in Database Administration - System Management User's Guide to configure the Measurements Platform.

4. Increase the LRN and NPANXX quantities by entering these commands.

   enable-ctrl-feat:partnum=893010501:fak=<LRN Quantity Feature Access Key>

   enable-ctrl-feat:partnum=893009402:fak=<NPANXX Quantity Feature Access Key>

   The Feature Access Key (FAK) is provided when the feature is purchased. If you do not have the Feature Access Key for the desired quantity, contact My Oracle Support (MOS).

5. Verify the changes by entering these commands.

   rtrv-ctrl-feat:partnum=893010501. The following is an example of the possible output.

   rtrv-ctrl-feat:partnum=893009402. The following is an example of the possible output.

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

7.3.10 Activating the LNP Local Subsystem

The procedure in this section explains how to activate the LNP local subsystem.

When all configuration is complete for the feature or features, the LNP subsystem application must taken online and the local subsystem must be activated to allow it to begin operation.

When the local subsystem operating state is Inhibited, the chg-ss-appl:appl=lnp command can be used to specify the value online or the value offline to control the persistent setting for the local subsystem. The rtrv-ss-appl command always displays the online or offline provisioned value. When the first Service Module card is loaded, this state tells whether the subsystem should be considered allowed (online) or inhibited (offline). This is a database state. If the command is accepted, then the change is made to the tables and can be read after an init-sys command is entered to initialize the system.

When the Service Module cards are in-service and the subsystem application is online, the alw/inh-map-ss commands can be used to change the dynamic operating state of the local subsystem. The inh-map-ss command does not necessarily force a state change, because it can fail if the mate does not send SOG. The force=yes parameter must be specified to bypass the SOR/SOG exchange and inhibit immediately. (There is no rtrv-map-ss command.)

The procedures in Changing the State of a Subsystem Application explain how to take a local subsystem online and offline.

Table 7-12 Subsystem Allow/Inhibit

Command\ Subsystem State	Offline	Online
alw-map-ss	Command is rejected.	Attempts to make the local subsystem active.
inh-map-ss	Command accepted, but no action because offline implies inhibited.	Attempts to inhibit the local subsystem. Use of the force=yes parameter bypasses the SOR/SOG exchange and inhibits immediately.
chg-ss-appl :appl=lnp :nstat=online	Command is rejected, because the subsystem must be online to be in the allowed state.	Changes local subsystem database status to online.
chg-ss-appl :appl=inp :nstat=offline	Command is rejected because the subsystem must be inhibited to go offline.	Changes local subsystem database status to offline.

1. Display the status of the LNP subsystem application, by entering the rtrv-ss-appl command.

       tekelecstp 07-07-25 08:02:22 EST  EAGLE 37.6.0 
       APPL   SSN  STAT
       LNP    11   offline            
    
       SS-APPL TABLE IS 25% FULL (1 OF 4)
   ;

2. Change the LNP subsystem to status to online.
   chg-ss-appl:appl=lnp:nstat=online
3. Enter the command to allow the INP subsystem to begin operation.
   alw-map-ss:ssn=<LNP ssn>

       integrat40 00-05-24 10:37:22 EST  EAGLE5 37.6.0
       Allow map subsystem command sent to all SCCP cards.
       Command Completed.
   ;

4. Display the operating status of the LNP subsystem, by entering the rept-stat-sccp command.

7.3.11 Increasing LNP Telephone Number Quantity on EAGLE

Note:

Use this procedure only if the LNP ELAP Configuration feature is enabled and turned on and an LNP quantity feature is enabled. Enter the rtrv-ctrl-feat command, and verify that an LNP ported TNs entry appears in the output. If the LNP ported TNs entry is not in the output, do not perform this procedure but go to LNP Feature Activation Procedure to enable and turn on the LNP ELAP Configuration feature and enable the LNP feature.

Using the enable-ctrl-feat Command to Set LNP Telephone Number Quantity

This procedure is used to increase the current quantity of LNP telephone numbers in the EAGLE using the enable-ctrl-feat command specifying the part number of the desired LNP telephone number quantity. The current LNP telephone number quantity is shown in the LNP ported TNs entry in the rtrv-ctrl-feat command output.

The LNP Telephone Number quantity is used to report the maximum provisioned quantity by the rtrv-ctrl-feat command and is also used to generate database consumption alarms that can be configured using the lnptndblv1 and the lnptndblv2 parameters of the chg-th-alm command.

Note:

After a specific LNP telephone number quantity is enabled with the enable-ctrl-feat command, that quantity cannot be reduced. The LNP feature cannot be turned off using the chg-ctrl-feat command, and cannot be enabled with a temporary Feature Access Key.

The LNP telephone number quantity must be purchased before you can enable that quantity with the enable-ctrl-feat command. If you are not sure if you have purchased the desired LNP telephone number quantity or do not have the Feature Access Key for the LNP telephone number quantity being enabled, contact My Oracle Support (MOS).

Caution:

Make sure that the LNP telephone number quantity configured in this procedure is greater than the ELAP telephone number quantity. The ELAP telephone number quantity can be verified by performing the Verifying RTDB Status at the ELAP User Interface procedure. If the telephone number quantity on the ELAP is greater than the LNP telephone number quantity configured in this procedure, the ELAP RTDB is not loaded onto the entire set of Service Module cards on the EAGLE. Some of the Service Module cards load the ELAP RTDB to provide a restricted level of GTT/LNP service. The remainder of the Service Module cards are put into a restricted state. UIM 1323 is generated at the EAGLE.

1. Display the status of the controlled features in the system, by entering the rtrv-ctrl-feat command.

   If the rtrv-ctrl-feat output shows that the LNP ELAP Configuration feature is not enabled or turned on, do not perform this procedure but go to LNP Feature Activation Procedure to enable and turn on the LNP ELAP Configuration feature and enable the LNP feature.

2. Display the status of the Service Module cards by entering the rept-stat-sccp command.
3. Enable the new LNP telephone number quantity using the enable-ctrl-feat command with the part number of the desired quantity.
   enable-ctrl-feat:partnum=893011036

   Refer to the description of the enable-ctrl-feat command in Commands User's Guide for a list of the LNP quantity feature part numbers.

4. Verify the changes by entering the rtrv-ctrl-feat command with the part number specified in Step 3.
   rtrv-ctrl-feat:partnum=893011036

   rlghncxa03w 10-05-01 21:16:37 GMT EAGLE5 46.3.0
   The following features have been permanently enabled:
       Feature Name              Partnum    Status     Quantity
       LNP ELAP Configuration    893010901  on             ----    
       LNP ported TNs            893011036  on        504000000
   

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

7.3.11.1

Using the chg-stpopts Command to Set the LNP Telephone Number Quantity to 756 Million

In addition to using the enable-ctrl feat command described previously for increasing the LNP Telephone Number quantity in 12M increments, the chg-stpopts command must be used to turn on the lnptn756m option for any LNP quantity greater than 504 million numbers.

1. Display the status of the controlled features in the system by entering the rtrv-ctrl-feat command.

   
       tklc1180801 20-11-18 09:22:33 EST  EAGLE 46.9.3.0.0-76.43.0
       rtrv-ctrl-feat
       Command entered at terminal #4.
   ;
   
       tklc1180801 20-11-18 09:22:33 EST  EAGLE 46.9.3.0.0-76.43.0
       The following features have been enabled:
   
       Feature Name              Partnum   Status Quantity
       Large System # Links      893005910 on     2000
       XGTT Table Expansion      893006110 on     1000000
       Routesets                 893006403 on     8000
       LNP Short Message Serv.   893006601 on     ----
       Intermed GTT Load Sharing 893006901 on     ----
       Command Class Management  893005801 on     ----
       Telnet                    893005701 on     ----
       EAGLE5 Product            893007101 on     ----
       XMAP Table Expansion      893007701 on     2000
       LNP ported NPANXXs        893009403 on     350000
       LNP ported LRNs           893010506 on     200000
       LNP ELAP Configuration    893010901 on     ----
       LNP ported TNs            893011046 on     504000000
       HC-MIM SLK Capacity       893012707 on     64
       EAGLE OA&M IP Security    893400001 on     ----
       Flexible GTT Load Sharing 893015401 on     ----
       Origin Based SCCP Routing 893014301 on     ----
       Hex digit support for GTT 893018501 on     ----
       E5-SM4G Throughput Cap    893019101 on     5000
       AMGTT                     893021801 on     ----
       VGTT with 16 GTT lengths  893024801 on     ----
       ITU TCAP LRN QUERY(LRNQT) 893026301 on     ----
       Flex Lset Optnl Based Rtg 893027701 on     ----
       TCAP Opcode Based Routing 893027801 on     ----
       TOBR Opcode Quantity      893027901 on     3
       PC & CIC Translation      893037208 on     1000
       3 Links per E5-ATM card   893039104 on     20
       Integrated GLS            893038901 on     ----
       SIP Number Portability    893040601 on     ----
       Dual ExAP Config          893040501 on     ----
   ; 
   

   If the rtrv-ctrl-feat output shows that the LNP ELAP Configuration feature is not enabled or turned on, do not perform this procedure. However, perform LNP Feature Activation Procedure to enable and turn on the LNP ELAP Configuration feature and enable the LNP feature.

2. Display the status of the Service Module cards by entering the rept-stat-sccp command.
3. In EAGLE 47.0 and later releases, both the lnptn756m chg-stpopts parameter must be turned on and the 893-0110-xx part number must be enabled for LNP capacity increases in 12M increments beyond 504 million. Enable the new LNP telephone number quantity greater than 504 million numbers using the enable-ctrl-feat command with the part number of the desired quantity.
   enable-ctrl-feat:partnum=8930110xx

   Refer to the description of the enable-ctrl-feat command in Commands User's Guide for a list of the LNP quantity feature part numbers.

4. Turn on the option to increase the capacity up to 756 million numbers by entering the following command:
   chg-stpopts:on=lnptn756m

   tklc1180801 20-11-18 10:53:53 EST  EAGLE 46.9.3.0.0-76.43.0
       chg-stpopts:on=lnptn756m
       Command entered at terminal #4.
   ;
   
       tklc1180801 20-11-18 10:53:53 EST  EAGLE 46.9.3.0.0-76.43.0
       CHG-STPOPTS: MASP B - COMPLTD
   ;
   

5. Verify the change by entering the following command:
   rtrv-stpopts

   rtrv-stpopts
   
   Command Accepted - Processing
   
       tklc1180801 20-11-18 10:54:02 EST  EAGLE 46.9.3.0.0-76.43.0
       rtrv-stpopts
       Command entered at terminal #4.
   ;
   
       tklc1180801 20-11-18 10:54:02 EST  EAGLE 46.9.3.0.0-76.43.0
       STP OPTIONS
       -------------------------------
       MTPT31CTL                     1
       MTPLTI                      yes
       MTPLTCTDPCQ                   3
       MTPLTST                   10000
       MTPXLQ                      500
       MTPXLET                     100
       MTPXLOT                      90
       MTPDPCQ                    8000
       TFATFRPR                   1000
       MTPRSI                       no
       MTPRSIT                    5000
       MTPLPRST                    yes
       MTPT10ALT                 30000
       UIMRD                        no
       SLSCNV                      off
       CRITALMINH                   no
       DISPACTALMS                  no
       NPCFMTI             14-00-00-00
       DEFCC                         1
       DEFNDC                     none
       DSMAUD                       on
       RPTLNPMRSS                  yes
       RANDSLS                     off
       RSTRDEV                     off
       ARCHBLDID                   off
       MFC                          on
       PCT                        lset
       PCN16FMT                    745
       UITHROTTLE                    9
       GBSUSNMINM                  off
       GDPCA            --------------
       EPAP240M                    off
       EPAPX                       off
       UIMPERIOD                     0
       VISUALIZATION               off
       LNPTN756M                    on
   

LSMS Configuration Change for increasing LNP Telephone Number Quantity

Refer to LSMS Configuration Guide for instructions on how to set the LNP telephone number quantity on the LSMS to match what is set on the EAGLE.

ELAP Configuration Change for increasing LNP Telephone Number Quantity

After the ELAP has been upgraded to ELAP 10.2 or later, run the uiEdit command from the command line and locate the value displayed for the LNP_TN_QTY parameter. If the value is anything other than 756000000, execute the uiEdit LNP_TN_QTY 756000000 command to set the parameter value to 756M LNP entries.