1. EAGLE INP/AINPQ User's Guide
  2. INP/AINPQ Feature Configuration

4 INP/AINPQ Feature Configuration

This chapter describes prerequisites and procedures for configuration of the INP and AINPQ features on the EAGLE. The INP and AINPQ features can be enabled and turned on independently or together in the system. This chapter also includes procedures for configuration of the Service Portability feature for use with INP, and for enabling and turning on the INP Circular Route Prevention (INP CRP) feature.

Introduction

This chapter describes prerequisites and procedures for configuration of the INP and AINPQ features on the EAGLE. The INP and AINPQ features can be enabled and turned on independently or together in the system. This chapter also includes procedures for configuration of the Service Portability feature for use with INP and AINPQ, and for enabling and turning on the INP Circular Route Prevention (INP CRP) feature.

INP and AINPQ Configuration Procedure lists the steps for enabling and turning on the features, and for the provisioning required for the features. Each step contains a link or reference to information and procedures to use to complete the step. Feature provisioning can be performed only after the INP or AINPQ feature is turned on. Refer to Commands User's Guide for complete descriptions of the commands used in these procedures.

Note:

The INP feature, AINPQ feature, and other related features are optional and must be purchased from Oracle before they can be used in your system. If you are not sure whether you have purchased a specific feature, contact your Oracle Sales or Account Representative.

Caution:

For an in-service environment, contact the unresolvable-reference.html#GUID-F6B3D647-C34D-4046-83F4-3D37AC9F2F63 before continuing to configure either the INP feature or the AINPQ feature. For an environment that is not yet in-service, continue with the configuration.

System Prerequisites

Before any feature that is described in this manual can be enabled, the prerequisites listed in Table 4-1 are required in the system.

Table 4-1 System Prerequisites

Prerequisite Verification and Provisioning

The system serial number must be correct and locked.

For new installations, the system is shipped with an unlocked serial number. The serial number can be changed if necessary and must be locked after the system is on-site.

For systems that are being upgraded, the serial number is usually already verified and locked.

 Note: The serial number cannot be changed after it is entered and locked in the system.

Locate the serial number for the system on a label affixed to the control shelf (1100).

Enter the rtrv-serial-num command to display the serial number and its locked status.

Verify that the displayed serial number is correct for the system.

If no serial number is displayed, enter the ent-serial-num command (without the lock parameter) to provision the serial number that appears on the control shelf label. Enter the rtrv-serial-num command and verify that the serial number was entered correctly.

Enter the ent-serial-num command with the lock=yes parameter to lock the serial number in the system.

A sufficient number of Service Module cards must be equipped.

Enter the rept-stat-card:appl=vsccp command to list the Service Module cards in the system.

If more cards or cards of a different type are needed, refer to the procedures in Database Administration - GTT User's Guide to add or remove Service Module cards.

The GTT feature must be on in the system.

Some features require an additional GTT-related feature such as EGTT. See the specific feature prerequisites in this section.

Enter the rtrv-feat command to display the GTT feature status.

If the GTT feature is on, the gtt=on entry appears in the output.

If the gtt=off entry appears in the output, use the procedures in Database Administration - GTT User's Guide to turn on and provision the GTT feature and any other GTT-related features and functions that will be used in the system.

INP and AINPQ Feature Prerequisites

Before the INP feature or the AINPQ feature can be enabled, the following prerequisites are required in the system:

Table 4-2 INP and AINPQ Feature Prerequisite

Prerequisite Verification and Provisioning
The LNP feature cannot be on in the system

Enter the rtrv-ctrl-feat command.

If the LNP feature is on, shown with a quantity greater than zero for the LNP ported TNs entry in the command output, features described in this manual cannot be enabled.

The system must be configured for HLR destinations. The system must be configured to communicate with the system of the HLR database. See Configure the System for HLR Destinations.

INP and AINPQ Configuration Procedure

The EAGLE configuration of the INP feature and the AINPQ feature consists of the following steps. The steps contain links and references to detailed procedures and information needed to complete each step.

EPAP Provisioning

It is recommended that EPAP entity (SP or RN) administration not be done until after the point code and/or subsystem number has been entered into the EAGLE MAP table (see Step 8).
  • EPAP-administered entity data can possibly become out-of-sync with the EAGLE MAP table when the creation of point codes and/or subsystem numbers in the MAP table is performed after EPAP database administration.
  • If this mismatch is discovered in real-time operations, a UIM (such as SCCP did not route - DPC not in MAP tbl or SCCP did not route - SS not in MAP tbl) is sent to the EAGLE maintenance terminal.
  1. Verify, and provision if needed, the system prerequisites. See System Prerequisites.
  2. Verify, and provision if needed, the feature prerequisites. See INP and AINPQ Feature Prerequisites.
  3. Enable the INP feature, the AINPQ feature, or both features. See Enabling the INP and AINPQ Features.
  4. Turn on the INP feature, the AINPQ feature, or both features. See Turning On the INP and AINPQ Features.
  5. If the INP CRP feature will be used with INP, enable the INP CRP feature. See Enabling the INP Circular Route Prevention (INP CRP) Feature.
  6. If the INP CRP feature is enabled, turn on the INP CRP feature. See Turning On the INP Circular Route Prevention (INP CRP) Feature.
  7. Provision capability point codes for INP Query service (used by INP and AINPQ). See Provisioning True Point Codes and Capability Point Codes.
  8. Refer to the procedures in Database Administration - GTT User's Guide to provision the following items in the Mated Application (MAP) table for the INP local subsystem:
    • Translation types and mappings
    • Concerned signaling point code (CSPC) of the EAGLE mate and of any nodes that will send Route-on-SSN queries to the INP local subsystem for INPQ queries (for INP and AINPQ)
    • Mated Application table entries for entity point codes and/or subsystem numbers for the INP local subsystem. Only solitary and dominant loadsharing are supported.
  9. Provision the state and subsystem number for the INP local subsystem (used by both INP and AINPQ for Query processing). See Provisioning the INP Local Subsystem.
  10. Provision the service selector mechanism to route MSUs to the INP subsystem. See Provisioning the INP Service Selectors.

    The INP services are inpq and inpmr.

    The Translation Type and Subsystem Number are the values assigned for the INP local subsystem when the MAP table entries were defined. See Step 8 in this procedure.

    INPQ supports the ITU-N Global Title Indicator; ANSI and ITU-I are not supported. INPQ does not support the Service Nature of Address Indicator and the Service Numbering Plan.

    INPMR support ITU-I and ITU-N Global Title Indicators. ANSI is not supported. The Service Nature of Address (SNAI) must be ccrndn, rnidn, rndnd, or rnsdn. The Service Numbering Plan must be e164.

    Note:

    If the AINPQ feature is enabled and the INP feature is not enabled, the INPMR service selector can still be provisioned, but the INPOPTS table cannot be provisioned. INPMR service will still be available and MSUs will be processed, but default values of the INPOPTS table will be used. To provision the INPOPTS table, the INP feature must be enabled.

  11. If non-international numbers need to be handled, verify that the STPOPTS values for the Default Country Code ( DEFCC parameter) and the Default Network Destination Code (DEFNDC parameter) are not none. Refer to the chg-stpopts and rtrv-stpopts command descriptions in Commands User's Guide to change and display the STPOPTS DEFCC and DEFNDC values.

  12. Enable the Service Portability feature, if it will be used with the INP or AINPQ feature. See Enabling the Service Portability Feature.
  13. Turn on the Service Portability feature, if it will be used with the INP feature, the AINPQ feature, or both features. See Turning On the Service Portability Feature.
  14. Provision option values for the feature or features that will be used in the system - INPOPTS options for the INP feature, AINPOPTS options for the AINPQ feature, options used for Service Portability, and options used for the INP CRP feature. See Provisioning the INP and AINPQ Options.
  15. Enable the S-Port Subscriber Differentiation feature, if it will be used with Service Portability for the INP feature with the INPMR service. See Enabling the S-Port Subscriber Differentiation Feature.
  16. Turn on the S-Port Subscriber Differentiation feature if it will be used with the Service Portability feature. See Turning On the S-Port Subscriber Differentiation Feature.
  17. Provision the SCCPOPTS option for S-Port Subscriber Differentiation if it will be used with Service Portability for the INP feature with the INPMR service. See Provisioning the S-Port Subscriber Differentiation SCCPOPTS Option.
  18. Provision Home RNs that are prefixed to DNs for incoming INPQ and INP MR messages. See Provisioning HOMERN Entries.
  19. Provision the INPQ service selector, the INPMR service selector , or both service selectors. See Provisioning the INP Service Selectors.
  20. Activate the INP local subsystem. See Activating the INP Local Subsystem.
  21. Initialize the Service Module cards to load the RTDB, OAM, GPL, and GTT data to the cards. Refer to the procedures in Database Administration - GTT User's Guide.
  22. Verify the operating status of the system, using the rept-stat-sccp, rept-stat-mps, and rept-stat-db:display=all commands.

EPAP can now be used to administer INP and AINPQ entity objects and subscribers. For the details about performing these actions, refer to Administration Guide for EPAP.

Configure the System for HLR Destinations

This section describes the configuration of the system for HLR destinations, so that the system can communicate with the system of the HLR database. The route to this database may already be configured.

Perform the steps in the following procedure to verify that all HLR destinations for INP/AINPQ are entered, and make configuration changes as needed. The steps contain links and references to procedures and information that is needed to complete each step.

  1. Display and note current system settings for point codes (PCs) and capability point codes (CPCs), destination point codes (DPCs), routes, and linksets.
    • Enter the rtrv-stpopts command to display the ITU-N point code format if the network is an ITU-N network.
    • Enter the rtrv-sid command to display current PCs and CPCs by network type.
    • Enter the rtrv-dstn command to display current DPCs.
    • Enter the rtrv-rte command to display current route configurations.
  2. Identify PCs and CPCs; determine new PCs and CPCs to be entered.
  3. Remove the system PC from the MAP table if necessary. Refer to Database Administration - GTT User's Guide procedure Removing a Mated Application).
  4. Change PC, CPC, DPC, route, linkset, and LIM card configurations for the HLR database.
    • Refer to the procedures in Database Administration - SS7 User's Guide to configure PCs and CPCs by network type.
    • Refer to the procedures in Database Administration - SS7 User's Guide to configure DPCs for HLR destinations.
    • Refer to the procedures in Database Administration - System Management User's Guide to provision LIM cards in the system, if needed.
    • Refer to the procedures in Database Administration - SS7 User's Guide to assign DPCs and configure linksets, signaling links, and routes for HLR destinations.
    • Refer to the procedures in Database Administration - GTT User's Guide to configure mated applications.
  5. Allow LIM card operation in the system and verify the card operating status. Refer to the procedures in Database Administration - System Management User's Guide .
  6. Allow the operation of the signaling links in the system and verify the link operating status. Refer to the procedures in Database Administration - SS7 User's Guide .

Enabling the INP and AINPQ Features

This procedure is used to enable the INP and AINPQ features in the EAGLE.

Each feature must be enabled using its feature part number.
  • INP - Part Number 893017901
  • AINPQ - Part Number 893017801

Note:

Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.
When each feature is enabled, it is permanently enabled. The features cannot be temporarily enabled.

Provisioning of INP and AINPQ options and other information can be done after each feature is enabled and before each feature is turned on.

After a feature has been enabled and database provisioning is complete, the feature status must be set to on (the feature must be “turned on”) See Turning On the INP and AINPQ Features.

  1. Display the status of the features that are controlled with feature access keys. Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.

    If the entry for the feature that you want to enable appears in the rtrv-ctrl-feat output with status on, performing this procedure is not necessary.

  2. Enable the feature, by entering the enable-ctrl-feat command and specify the part number for the feature.
    enable-ctrl-feat:partnum=<893xxxxx>

    When the feature is enabled, the entry for the enabled feature appears in the output of the rtrv-ctrl-feat command. The feature Status is off. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  off         ----
    AINPQ                     893017801  off         ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Turning On the INP and AINPQ Features

Before the INP or AINPQ feature can be turned on, the feature must be enabled in the EAGLE 5 ISS.

Provisioning of INP or AINPQ options and other information can be done after the feature is enabled and before the feature is turned on.

After each feature has been enabled and database provisioning is complete, the feature status must be set to on (the feature must be “turned on”). MSUs will not be processed by the feature until the feature is turned on.

This procedure is used to turn on the INP and AINPQ features in the EAGLE 5 ISS. Each feature must be turned on using its feature part number.
  • INP - Part Number 893017901
  • AINPQ - Part Number 893017801

After the features are enabled and turned on, they cannot be turned off again.

  1. Display the status of the features that are controlled with feature access keys. Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
    rlghncxa03w 09-03-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  off         ----
    AINPQ                     893017801  off         ----
;

    If the entry for the feature that you want to turn on appears in the rtrv-ctrl-feat output with status on, performing this procedure is not necessary.

    If the status of the feature in the output is off, continue with 2.

  2. Turn on the feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=<893xxxxxx>:status=on

    When the feature is turned on, the feature status changes to on in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on          ----
    AINPQ                     893017801  on          ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Provisioning True Point Codes and Capability Point Codes

This procedure explains briefly how to provision EAGLE true point codes and capability point codes (CPCs) for EPAP-related features. Refer to the detailed procedures in Database Administration - SS7 User's Guide for provisioning true and capability point codes, and the CLLI if needed.

The INP Query service is used by both INP and AINPQ. The INP Message Relay service is used only by INP.

INP Message Relay (INPMR) and INP Query (INPQ) services should be given separate CPCs
  • For the INP Query service (INPQ), use CPCTYPE=INP.
  • For the INP Message Relay service (INPMR), use CPCTYPE=STP.

INP Query processing supports queries from ITU-N point codes, and supports use of the ITU National Duplicate Point Code feature.

INP Message Relay processing supports ITU-I and ITU-N point codes, including group codes and use of the ITU National Duplicate Point Code feature.

This procedure explains how to provision EAGLE true point codes and INP capability point codes.

  1. Display the true and capability point codes in the system. Enter the rtrv-sid command. 
        tekelecstp 08-07-22 15:07:48 EST  EAGLE 39.2.0

       PCA             PCI          PCN                CLLI              PCTYPE
       -----------     -------      -----              tekelecstp        ANSI
;
  2. Verify that the desired EPAP-related feature is enabled and turned on, by entering the rtrv-ctrl-feat command. 
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012701  on            64
    INP                       893017901  on          ----
    AINPQ                     893017801  on          ----
;
    • If the feature entry appears in the command output, and the feature status is on, continue with 3.
    • If the feature entry does not appear in the command output or if the feature status in the entry is off, go to the procedures in this manual to enable and turn on the EPAP-related feature. Then continue with 3.
  3. Add or change the true point codes and capability point codes as needed, using the chg-sid command.
    Refer to the procedures in Database Administration - SS7 User's Guide for changing the Self-Identification of the EAGLE. The system may need to be initialized for the point code changes to take effect. This must be done carefully to minimize traffic loss.
  4. Verify the changes with the rtrv-sid command. 
        tekelecstp 08-08-22 15:07:48 EST  EAGLE 41.1.0

       PCA             PCI          PCN                CLLI              PCTYPE
       001-001-001     2-002-2      01234              tekelecstp        ANSI

       CPCA (INP)
       004-004-004

       CPCI (STP)
       5-012-0

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

Provisioning the INP Local Subsystem

The following procedures in this section are used to add or remove a local subsystem application:

See the procedures in Changing the State of a Subsystem Application to take the subsystem application online or offline.

Note:

The EAGLE supports the operation of two or more local subsystems for EPAP-related features in the system at one time. For example, the local subsystems for INP and EIR can coexist in the system.

Adding the INP Local Subsystem Application

This procedure is used to define the INP subsystem application. The subsystem application can be taken online when it is defined or later in the configuration process (see Changing the State of a Subsystem Application).

Before the INP subsystem application can be added to the database, the following conditions must exist in the system:

Table 4-3 INP Local Subsystem Prerequisites

Prerequisite Verification
The INP feature or AINPQ feature must be enabled and turned on.

Enter the rtrv-ctrl-feat command.

If the INP entry or AINPQ entry with Status of on does not appear in the output, see the Enabling the INP and AINPQ Features and Turning On the INP and AINPQ Features procedures.

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

Enter the rtrv-ss-appl command.

If the INP entry appears in the output, this procedure cannot be performed.
EAGLE true point codes, STP capability point code for INPMR, and INP capability point codes for INPQ must be defined, and entered in the Mated Application table with a subsystem number to be used for the INP subsystem application.

Only one subsystem number for the application can be defined, and must be used for all point code types assigned to the local subsystem.

Enter the rtrv-sid command, and verify that the true and capability point codes needed for the feature are correct. If changes are required, see Provisioning True Point Codes and Capability Point Codes.

Enter the rtrv-map command, and verify that the MAP table entries are correct for the INP local subsystem. If changes are required, refer to the procedures in Database Administration - GTT User's Guide for provisioning solitary and dominant mated applications.

The examples in this procedure reserve the subsystem number 100 for the INP subsystem application and set the INP subsystem application status to online.

  1. Add the INP application and subsystem number, using the ent-ss-appl command.

    If the stat parameter is not specified, the status defaults to offline.

    ent-ss-appl:appl=inp:ssn=100:stat=online
  2. Verify the changes, by entering the rtrv-ss-appl command. 
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    INP    100   online            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  3. 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.

Removing a Local Subsystem Application

This procedure is used to remove a subsystem application from the database. The subsystem application to be removed must be in the database and the subsystem must be out of service.

  1. Display the subsystem application number for the local subsystem application in the database, by entering the rtrv-ss-appl command.
  2. Display the operating status of the local subsystem, by entering the rept-stat-sccp command.
    If the subsystem is out of service , shown by an entry containing OOS-MT-DSBLD for the subsystem in the rept-stat-sccp output, go to 5.
  3. Place the local subsystem application out of service. Enter the inh-map-ss command and specify the subsystem number displayed in 1.
    inh-map-ss:ssn=11 
    rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 39.2.0
Inhibit map subsystem command sent to all SCCP cards.
Command Completed.
    When this command has successfully completed, the following message appears. If the force=yes parameter is not specified, wait for a message that indicates the subsystem is inhibited. 
    rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 39.2.0
Inhibit map subsystem command sent to all SCCP cards.
Command Completed.
  4. Verify that the local subsystem is out of service (OOS-MT-DSBLD), by entering the rept-stat-sccp command. If the local subsystem is not out of service, return to 3 and enter the inh-map-ss command with the force=yes parameter specified.
  5. Remove the local subsystem application from the database, by entering the dlt-ss-appl command.
    dlt-ss-appl:appl=<subsystem>
  6. Verify the changes by entering the rtrv-ss-appl command. The deleted entry should not appear in the output.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT

    SS-APPL TABLE IS 0% FULL (0 OF 4)
;
  7. 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.

Provisioning the INP and AINPQ Options

This procedure is used to provision the configuration options for the INP feature, the AINPQ feature, or both features, and the options required for using Service Portability.

See INP/AINPQ Configuration Options for information and considerations about provisioning INP and AINPQ configuration options.

  1. Verify that the INP or AINPQ feature is enabled, by entering the rtrv-ctrl-feat command.
    • If the feature is not enabled (the entry does not appear in the output), go to Enabling the INP and AINPQ Features to enable the feature. Then continue with 2.
    • If the feature is enabled or turned on (the feature status is off or on in the entry), continue with 2.
          rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  off         ----
    AINPQ                     893017801  off         ----
;
  2. Display the current settings of the feature options.

    Enter the rtrv-inpopts command for INP options.

    Enter the rtrv-ainpopts command for AINPQ options.

  3. Change the options for one or both features to the required settings. If Service Portability will be used with one or both features, change the options that apply to Service Portability to the required settings.

    Enter the chg-inpopts command for INP options.

    Enter the chg-ainpopts command for AINPQ options.

  4. Verify the changes.

    Enter the rtrv-inpopts command for INP options.

    Enter the rtrv-ainpopts command for AINPQ options.

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

Enabling the INP Circular Route Prevention (INP CRP) Feature

If INP Circular Route Prevention will be used with INP, use this procedure to enable the INP CRP feature in the EAGLE.

The INP CRP feature must be enabled using the feature part number 893028501 and the optional feature access key.

Note:

Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.
When the INP CRP feature is enabled, it is permanently enabled. The INP CRP feature cannot be temporarily enabled. After the INP CRP feature is enabled and turned on, the INP CRP feature can be turned off again.

After the S-Port feature has been enabled, the INP CRP feature must be turned on before INP CRP processing will occur.

  1. Display the status of the features that are controlled with optional feature access keys. Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on          ----    
;
  2. Enable the INP CRP feature, by entering the enable-ctrl-feat command.
    enable-ctrl-feat:partnum=893028501

    When the feature is enabled, the INP CRP entry appears in the output of the rtrv-ctrl-feat command. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on          ----
    INP CRP                   893028501  off         ----
 ;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Turning On the INP Circular Route Prevention (INP CRP) Feature

This procedure is used to turn on the INP CRP feature in the EAGLE, using the feature part number 893028501.

Before the INP CRP feature can be turned on, the feature must be enabled in the EAGLE.

After the INP CRP feature has been enabled, the INP CRP feature status must be set to on (the feature must be “turned on”). MSUs will not be processed by the INP CRP feature until the feature is turned on.

  1. Display the status of the features that are controlled with feature access keys. Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
    rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on          ----
    INP CRP                   893028501  off         ----
;

    If the entry for the INP CRP feature appears in the rtrv-ctrl-feat output with status on, performing this procedure is not necessary.

    If the status of the INP CRP feature in the output is off, continue with 2.

  2. Turn on the INP CRP feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=893028501:status=on

    When the feature is turned on, the feature status changes to on in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-08-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on           ----
    INP CRP                   893028501  on          ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Provisioning HOMERN Entries

The ent-homern command is used to provision the prefix RNs in the HOMERN table.

Enter any Home RNs that are prefixed to DNs for incoming INPQ and INPMR messages, and that are used to determine INP Circular Routes. This command can be used to enter up to 100 routing number prefixes for the operating network into the HOMERN table.

  1. Display the HOMERN table entries, by entering the rtrv-homern command.
  2. Enter the home routing number prefixes that will be used for INP/AINPQ. Use the following command for each prefix:
    ent-homern:rn=<routing number>
  3. Verify the changes by entering the rtrv-homern command.
  4. Back up the changes, using the chg-db:action=backup:dest=fixed command.
    These 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.

Provisioning the INP Service Selectors

The procedures in this section describe how to add, change, and remove a service selector. The INP-specific information is indicated.

Adding Service Selectors for INP and AINPQ

This procedure is used to add service selectors that are used by the INP and AINPQ features.

The INP or the AINPQ feature must be enabled and turned on before an INP service selector can be added.

  1. Verify that the INP feature or the AINPQ feature is enabled and turned on, by entering the rtrv-ctrl-feat command. If the feature is enabled and turned on, the status of the entry is on.
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on          ----
    AINPQ                     893017801  on          ----
;
  2. Display any existing INP service selectors in the database, by entering the rtrv-srvsel:serv=inpq command and the rtrv-srvsel:serv=inpmr command.
  3. Add new INP service selectors, using the ent-srvsel command.
  4. Verify the changes by entering the rtrv-srvsel command with the parameters and values used in 3.
  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.

Removing a Service Selector

This procedure is used to remove a service selector from the database.

To remove a service selector, the GTI, GTII, GTIN, tt, and ssn parameter values must be entered as shown in the rtrv-srvsel output.

These parameters can also be used to limit the amount of information displayed with the rtrv-srvsel command.

  1. Display the service selectors in the database, by entering the rtrv-srvsel command.
  2. Remove the service selector from the database, using the dlt-srvsel command.
  3. Verify the changes by entering the rtrv-srvsel command with the parameters and values used in 2.
  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.

Changing an Existing Service Selector to an INP Service Selector

This procedure is used to change an existing non-INP service selector to an INP service selector.

The only parameters that can be changed using this procedure are:

:nserv
New DSM service type, inpq or inpmr
:nsnp
The inpq service selector cannot contain an SNP value; if the service selector being changed contains an SNP value, this value must be changed to none with this parameter.
The snp value for the inpmr service selector must be e164.
:nsnai
The inpq service selector cannot contain an SNAI value; if the service selector being changed contains an SNAI value, this value must be changed to none with this parameter.
The snai value for the inpmr service selector must be ccrndn, rndnd, rnndn, or rnsdn.

The chg-srvsel command requires that the following parameters be specified with the values shown in the rtrv-srvsel output for the service selector that is being changed. If any of these parameter values need to be changed for a new INP service selector, use the the procedure in Removing a Service Selector to remove the existing service selector. Then use the procedure in Adding Service Selectors for INP and AINPQ to add the new INP service selector with the new parameter information.

:gtii/gtin/gtin24
Global title indicator for ITU international (gtii) and ITU national using 14-bit point codes (gtin).
:tt
Translation type
:ssn
Subsystem number
:nai
Nature of address indicator
:naiv
Nature of address indicator value
:np
Numbering plan
:npv
Numbering plan value
  1. Display the service selectors in the database, using the rtrv-srvsel command.

    Note:

    If the rtrv-srvsel output shows INP service selectors, go to 3.
  2. Verify that the INP feature or AINPQ feature is enabled and turned on, by entering the rtrv-ctrl-feat command. If the feature is enabled and turned on, the status of the entry is on. 
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    INP                       893017901  on          ----
    AINPQ                     893017801  on          ----
;
  3. Change the service selector, using the chg-srvsel command.

    If the snp or snai parameater values are shown as dashes in the rtrv-srvsel output, these parameter cannot be specified with the chg-srvsel command.

    If the gtii/gtin/gtin24 parameter value is 2, the np, nai, npv, and naiv, parameters cannot be specified wit the chg-srvsel command.

    If the gtii/gtin/gtin24 parameter value is 4, eiher the np and nai parameters, or the npv and naiv parameters must be specified with the chg-srvsel command.

    The np and nai parameters can be specified in place of the npv and naiv parameters, and the npv and naiv parameters can be specified in place of the np and nai parameters, as long as the parameter values being specified correspond to the values shown in the rtrv-srvsel output.

    Refer to the chg-srvsel commnand description in Commands User's Guide.

  4. Verify the changes by entering the rtrv-srvsel command with the serv=inpq parameter or the serv=inpmr parameter and the values for the other parameters that were used in 3.
  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.

Activating the INP Local Subsystem

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

INP and AINPQ share operation of the INP local subsystem in the EAGLE.

When all configuration is complete for the feature or features, the INP 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=inp 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 4-4 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=inp :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 INP subsystem application, by entering the rtrv-ss-appl command.
        tekelecstp 07-07-25 08:02:22 EST  EAGLE 37.6.0 
    APPL   SSN  STAT
    INP    11   offline            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  2. Change the INP subsystem to status to online.
    chg-ss-appl:appl=inp:nstat=online
  3. Enter the command to allow the INP subsystem to begin operation.
    alw-map-ss:ssn=<INP 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 INP subsystem, by entering the rept-stat-sccp command.

Changing the State of a Subsystem Application

The procedures in this section are used to set the state of an existing subsystem application to either online or offline.

The online or offline status of the subsystem application is shown in the STAT field of the rtrv-ss-appl command output.

The rept-stat-sccp command displays the operating state (in or out of service) of the subsystem.

If the subsystem application is to be taken online, the subsystem application must be offline.

When the subsystem is taken online (regardless of how the subsystem was taken offline), the EAGLE sends SNR/SSA. A UAM is generated, indicating that the subsystem is ALLOWED.

If the subsystem application is to be taken offline, the subsystem application must be online. The subsystem must be taken out of service (OOS-MT-DSBLD) with the inh-map-ss command before it can be taken offline.

A subsystem application can be taken offline using coordinated state change, or forced offline without using coordinated state change.

When the inh-map-ss command is entered for the subsystem, a coordinated shutdown is attempted. If the coordinated shutdown fails, a UIM is generated, indicating that the shutdown failed. If the force parameter is specified, the subsystem is forced to shut down; a coordinated shutdown is not performed.

For coordinated state change, SCMG sends an SOR message to the mated subsystem and will start a Tcoord timer (30 seconds). If SCMG receives an SOG message from the mated subsystem before the Tcoord timer expires, SCMG will broadcast SSPs to the concerned point code group, send SBR/SSP, and take the subsystem offline. A UAM is generated, indicating that the subsystem is PROHIBITED. If the SOG is not received before Tcoord expires, then the inhibit request is denied and a UIM is generated.

When the subsystem is taken offline without coordinated state change, the EAGLE sends SBR/SSPs. A UAM is generated, indicating that the subsystem is PROHIBITED.

When the EAGLE receives an SOR message from its mated subsystem, it will reply with an SOG message if both of the following conditions are met:
  • The local subsystem is available
  • The total load on the DSM subsystem is less than 45% of its capacity

If either of these conditions is not met, the EAGLE will not reply to the SOR message.

Taking the Subsystem Application Offline

Use the procedure in this section to take a subsystem application offline.

  1. Verify the online or offline state of the subsystem application, by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    INP    11   online            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
    If the INP subsystem application is offline, this procedure does not need to be performed.
  2. Verify the operating status of the subsystem by entering the rept-stat-sccp command.
  3. Place the subsystem out of service. Specify the subsystem number displayed in the output in 1.
    inh-map-ss:ssn=11 
        rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 39.2.0
    Inhibit map subsystem command sent to all SCCP cards.
    Command Completed.
;
  4. Verify that the subsystem is out of service, by entering the rept-stat-sccp command.
  5. Take the subsystem offline. Enter the chg-ss-appl command with the nstat=offline parameter.
    chg-ss-appl:appl=inp:nstat=offline
  6. Verify the changes by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    INP    11   offline            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  7. Back up the new 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.

Taking the Subsystem Application Online

Use the procedure in this section to take the subsystem application online.

  1. Verify the state of the subsystem application - online or offline, by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    INP    11   offline            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
    If the INP subsystem is online, this procedure does not need to be performed.
  2. Display the operating status of the subsystem by entering the rept-stat-sccp command.
  3. Take the subsystem application online. Enter the chg-ss-appl command with the nstat=online parameter.
    chg-ss-appl:appl=inp:nstat=online
  4. Verify the changes by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    INP    11   online            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  5. Back up the new 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.

Service Portability Feature Configuration Procedures

The procedures in this section are used for configuration of the Service Portability (S-Port) feature.

Enabling the Service Portability Feature

If Service Portability can be applied to the messages processed by a feature described in this guide, use this procedure to enable the Service Portability feature in the EAGLE.

The Service Portability feature must be enabled using the feature part number 893034301 and a feature access key.

Note:

Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.
When the S-Port feature is enabled, it is permanently enabled. The S-Port feature cannot be temporarily enabled. After the S-Port feature is enabled and turned on, the S-Port feature can be turned off again.

Provisioning of S-Port options can be done after the feature is enabled and before the feature is turned on.

After the S-Port feature has been enabled and database provisioning is complete, the S-Port feature status must be set to on (the feature must be “turned on”) before S-Port processing will occur.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature. 
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
;

    If the Service Portability entry appears in the rtrv-ctrl-feat output, performing this procedure is not necessary.

  2. Enable the S-Port feature, by entering the enable-ctrl-feat command.
    enable-ctrl-feat:partnum=893034301:fak=<feature access key>

    When the feature is enabled, the Service Portability entry appears in the output of the rtrv-ctrl-feat command. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Service Portability       893034301  off         ----
 ;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Turning On the Service Portability Feature

This procedure is used to turn on the Service Portability feature in the EAGLE, using the feature part number 893034301.

Before the Service Portability (S-Port) feature can be turned on, the feature must be enabled in the EAGLE.

Provisioning of S-Port options can be done after the feature is enabled and before the feature is turned on.

After the S-Port feature has been enabled and database provisioning is complete, the Service Portability feature status must be set to on (the feature must be “turned on”). MSUs will not be processed by the Service Portability feature until the feature is turned on.

After the Service Portability feature is enabled and turned on, it can be turned off again. Service Portability processing can occur only when the Service Portability feature is on and a feature that uses S-Port is on.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
    • If the entry for the Service Portability feature appears in the rtrv-ctrl-feat output with status on, performing this procedure is not necessary.
    • If the status of the Service Portability feature in the output is off, continue with 2.
  2. Turn on the S-Port feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=893034301:status=on

    When the feature is turned on, the feature status changes to on in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-08-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893022101  on          ----
    Service Portability       893034301  on          ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Turning Off the Service Portability Feature

Before the Service Portability (S-Port) feature can be turned on and off, the feature must be enabled in the EAGLE.

This procedure is used to turn off the Service Portability feature, using its feature part number 8930343001.

Note:

MSUs will not be processed by a feature when the feature is turned off in the system.
  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    TIF Number Portability    893018901  on          ----
    Service Portability       893034301  on          ---- 
;

    If the entry for the Service Portability feature appears in the rtrv-ctrl-feat output with status off, performing this procedure is not necessary.

    If the status of the Service Portability feature in the output is on, continue with 2.

  2. Turn off the S-Port feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=<893034301>:status=off

    When the feature is turned off, the feature status changes to off in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-05-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    TIF Number Portability    893018901  on          ----
    Service Portability       893034301  off         ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

S-Port Subscriber Differentiation Feature Configuration Procedures

The procedures in this section are used for configuration of the S-Port Subscriber Differentiation feature.

Enabling the S-Port Subscriber Differentiation Feature

If S-Port Subscriber Differentiation will be used with Service Portability for the messages processed by a feature described in this manual, use this procedure to enable the S-Port Subscriber Differentiation feature in the EAGLE.

The S-Port Subscriber Differentiation feature must be enabled using the feature part number 893037901 and a feature access key.

Note:

Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.
When the S-Port Subscriber Differentiation feature is enabled, it is permanently enabled. The S-Port Subscriber Differentiation feature cannot be temporarily enabled.

After the S-Port Subscriber Differentiation feature has been enabled, the S-Port Subscriber Differentiation feature status must be set to on. See Turning On the S-Port Subscriber Differentiation Feature. The S-Port Subscriber Differentiation feature cannot be turned off after the feature is turned on.

Provisioning of the S-Port Subscriber Differentiation SCCPOPTS configuration option can be done only after the feature is enabled and turned on. See Provisioning the S-Port Subscriber Differentiation SCCPOPTS Option.

Before S-Port Subscriber Differentiation processing of MSUs can occur, the Service Portability feature, the S-Port Subscriber Differentiation feature, the S-Port Subscriber Differentiation option, and a feature that uses Service Portability must be on.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature. 
        rlghncxa03w 10-06-29 16:40:40 EST  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Service Portability       893034301  off         ----
;

    If the S-Port Sub Dfrntiation entry appears in the rtrv-ctrl-feat output, performing this procedure is not necessary.

  2. Enable the S-Port Subscriber Differentiation feature, by entering the enable-ctrl-feat command.
    enable-ctrl-feat:partnum=893037901:fak=<feature access key>

    When the feature is enabled, the S-Port Sub Dfrntiation entry appears in the output of the rtrv-ctrl-feat command. 

        rlghncxa03w 10-06-29 16:40:40 EST  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Service Portability       893034301  off         ----
    S-Port Sub Dfrntiation    893037901  off         ----
 ;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Turning On the S-Port Subscriber Differentiation Feature

This procedure is used to turn on the S-Port Subscriber Differentiation feature in the EAGLE, using the feature part number 893037901.

Before the S-Port Subscriber Differentiation feature can be turned on, the feature must be enabled in the EAGLE.

After the S-Port Subscriber Differentiation feature has been enabled, the S-Port Subscriber Differentiation feature status must be set to on (the feature must be “turned on”). After the S-Port Subscriber Differentiation feature is enabled and turned on, it cannot be turned off again.

Provisioning of the S-Port Subscriber Differentiation option can be done only after the feature is enabled and turned on. The S-Port Differentiation option can be turned on and off.

MSUs will not be processed by the S-Port Subscriber Differentiation feature until the feature and the option are turned on. S-Port Subscriber Differentiation processing can occur only when the Service Portability feature, the S-Port Subscriber Differentiation feature, the S-Port Differentiation option, and a feature that uses Service Portability are all on.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
    rlghncxa03w 10-06-29 16:40:40 EST  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Info Analyzed Relay Base  893034201  off         ----
    Service Portability       893034301  off         ----
    S-Port Sub Dfrntiation    893037901  off         ----
;

    If the S-Port Sub Dfrntiation entry appears in the rtrv-ctrl-feat output with Status of on, performing this procedure is not necessary.

    If the status of the S-Port Subscriber Differentiation feature in the output is off, continue with 2.

  2. Turn on the S-Port Subscriber Differentiation feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=893037901:status=on

    When the feature is turned on, the feature status changes to on in the rtrv-ctrl-feat command output. 

        rlghncxa03w 10-08-29 16:40:40 EST  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Info Analyzed Relay Base  893034201  off         ----
    Service Portability       893034301  off          ----
    S-Port Sub Dfrntiation    893037901  on          ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    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.

Provisioning the S-Port Subscriber Differentiation SCCPOPTS Option

This procedure is used to provision the SCCPOPTS configuration option for the S-Port Subscriber Differentiation feature.

The S-Port Subscriber Differentiation feature must be enabled and turned on before SCCPOPTS SUBDFRN option can be provisioned.

  1. Verify that the S-Port Subscriber Differentiation feature is enabled and on, by entering the rtrv-ctrl-feat command. 
        rlghncxa03w 10-06-29 16:40:40 EST  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Info Analyzed Relay Base  893034201  off         ----
    Service Portability       893034301  off         ----
    S-Port Sub Dfrntiation    893037901  on          ----
;
  2. Display the current settings of the SCCPOPTS options, using the rtrv-sccpopts command.
  3. Change the SCCPOPTS SUBDFRN option to the required setting (on or off), by entering the chg-sccpopts command with the subdfrn option parameter specified.
    Refer to the chg-sccpopts command description in Commands User's Guide for valid parameter values, input examples, and rules for entering the command correctly.
  4. Verify the changes, by entering the rtrv-sccpopts command.
  5. Back up the changes using the chg-db:action=backup:dest=fixed command.
    These 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.