4 EIR Configuration

This chapter identifies prerequisites and procedures for configuration of the EIR feature in the EAGLE.

4.1 Introduction

This chapter describes prerequisites and procedures for configuration of the EIR feature on the EAGLE.

The Equipment Identity Register (EIR) feature is configured on the EAGLE and on the EPAP (in association with either the G-Flex or G-Port feature). This chapter covers the EAGLE configuration only. Refer to Administration Guide for EPAP and EPAP Entity Provisioning in this manual for information about EPAP configuration.

EIR Configuration Procedure lists the steps for enabling and turning on the feature, and for the provisioning required for the feature. 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 EIR feature is turned on. Refer to Commands User's Guide for complete descriptions of the commands used in these procedures.

Note:

The EIR feature is optional and you must be entitled to use it in your system. If you are not sure whether you are entitled to use a specific feature, contact your Sales Representative or Account Representative.

4.2 EPAP Entity Provisioning

Oracle recommends that EPAP entity (SP or RN) administration not be performed until after the Point Code and/or Subsystem Number has been entered into the EAGLE MAP table.
  • EPAP-administered entity data can 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 is sent to the EAGLE maintenance terminal. (Example UIMs: SCCP did not route - DPC not in MAP tbl, SCCP did not route - SS not in MAP tbl.)

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

4.4 EIR Feature Prerequisites

Before the EIR feature can be enabled, the following prerequisites are required in the system:

Table 4-2 EIR Feature Prerequisite

Prerequisite Verification and Provisioning

The ANSIGFLEX system option cannot be set to Yes.

Enter the rtrv-stpopts command.

Verify that the ANSIGFLEX entry does not appear in the command output or that the ANSI GFLEX entry shows a value of No.

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, the feature described in this manual cannot be enabled.

4.5 EIR Configuration Procedure

The EAGLE configuration of the Equipment Identity Register (EIR) feature consists of the following steps. The steps contain links and references to detailed procedures and information needed to complete each step.

  1. Verify, and provision if needed, the system prerequisites. See System Prerequisites.
  2. Verify, and provision if needed, the feature prerequisites. See EIR Feature Prerequisites.
  3. Enable the EIR feature, set system STP options, and turn on the EIR feature. See Enabling and Turning On the EIR Feature.
  4. Change the self identification of the EAGLE node to include true point codes and EIR capability point codes. Refer to the procedures in Database Administration - SS7 User's Guide.
  5. Refer to the procedures in Database Administration - GTT User's Guide to provision the following items:
    • Translation types and mappings
    • Mated Application (MAP) table entries for the EIR feature that contain the EAGLE ANSI, ITU-I, and ITU-N true point codes, the EIR capability point codes, and the EIR subsystem number. Only solitary and dominant loadsharing are supported.

    The EIR subsystem can have a mate subsystem and a concerned point code group assigned to it in the MAP table.

    If multiple point code types for EIR are provisioned in the MAP table, then the point code type for the Subsystem Out-of-Service Request message (SOR) is determined using the following order:
    1. ANSI
    2. ITU-N
    3. ITU-N Spare
    4. ITU-I
    5. ITU-I Spare
  6. Provision the state and subsystem number for the EIR local subsystem application. See Adding the EIR Subsystem Application.
  7. Provision the service selector mechanism to route MSUs to the EIR subsystem. See Provisioning the EIR Service Selectors.

    The EIR service is eir.

    The Translation Type and Subsystem Number are the values assigned for the EIR local subsystem when the MAP table entries were defined. See Step 5 in this procedure. The asterisk value (*) for the Subsystem Number is supported for the EIR subsystem.

    EIR supports ANSI, ITU-I, and ITU-N Global Title Indicators.

    • The gtii/gtin/gtin24 value can be either 2 or 4.
    • If the gtii/gtin/gtin24 value is 2, the np, nai, npv, or naiv parameters cannot be specified with the ent-srvsel command.
    • If the gtii/gtin/gtin24 value is 4, either the np and nai or the npv and naiv parameters must be specified with the ent-srvsel command.

    EIR does not support the Service Nature of Address or the Service Numbering Plan.

  8. Provision GSM options, including the EIR Global Response status, EIR Response Type, and EIR IMSI Check status options. See Changing the EIR Options.
  9. Activate the EIR local subsystem. See Activating the EIR Local Subsystem.
  10. Configure the Measurements Platform feature or the E5-OAM Integrated Measurements feature if measurements are to be collected for EIR.

    Refer to the procedures in Database Administration - System Management User's Guide for configuring the Measurements Platform feature, the E5-OAM Integrated Measurements feature, and the EAGLE OA&M IP Security feature in the EAGLE. OAM-based measurements reports are not available for EIR.

4.6 Enabling and Turning On the EIR Feature

This procedure is used to enable and turn on the EIR feature in the EAGLE.
  • The EIR feature must be enabled using the EIR feature part number 893012301 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 Sales Representative or Account Representative.

    Note:

    Controlled features must be purchased before you can receive a feature access key to use to enable the feature. If you are not sure if you have purchased a feature and received the feature access key, contact your Sales Representative or Account Representative.

    The feature access key is based on the EIR feature part number and the serial number of the system, making the feature access key site-specific.

    When the EIR feature is enabled, it is permanently enabled. The EIR feature cannot be temporarily enabled.

  • After the EIR feature has been enabled, the EIR feature must be turned on using the chg-ctrl-feat command with the EIR feature part number and the status=on parameter.
  1. Enable the EIR feature. Enter the enable-ctrl-feat command with the EIR feature part number 893012301 and the FAK.
  2. Turn on the EIR feature on. Enter the chg-ctrl-feat command with the EIR feature part number 893012301 and the status=on parameter.
  3. Verify the changes. Enter the rtrv-ctrl-feat command with part number 893012301.
    
    rlghncxa03w 10-06-30 21:16:37 GMT  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on          64
    EIR                       893012301  on      ------
    
  4. Back up the 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.
    

4.7 Provisioning the EIR 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.

4.7.1 Adding the EIR Subsystem Application

This procedure is used to define the EIR 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 EIR local subsystem can be added to the database, the following prerequisites must exist in the system:

Table 4-3 EIR Local Subsystem Prerequisites

Prerequisite Verification

The EIR feature must be enabled and turned on.

Enter the rtrv-ctrl-feat command.

If the EIR entry with Status of on does not appear in the output, see the Enabling and Turning On the EIR Feature procedure.

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

Enter the rtrv-ss-appl command.

If the EIR entry appears in the output , this procedure cannot be performed.

EAGLE true point codes and EIR capability point codes must be defined, and entered in the Mated Application (MAP) table with a subsystem number to be used for the EIR 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 (PCI and PCN fields) needed for the feature are correct. If changes are required, refer to the procedures in Database Administration - SS7 User's Guide.

Enter the rtrv-map command, and verify that the MAP table entries include EAGLE true point code and the SSN for the EIR 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 example in this procedure reserves the subsystem number 100 for the EIR application and sets the EIR application status to online.

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

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

  2. Verify the changes; enter the rtrv-ss-appl command.
        tekelecstp 10-07-25 08:02:22 EST  EAGLE5 42.0.0
        APPL   SSN  STAT
        EIR    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 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.
    

4.7.2 Removing the EIR 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 number for the EIR local subsystem application in the database; enter the rtrv-ss-appl command.
  2. Display the operating status of the EIR subsystem; enter 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 EIR subsystem application out of service. Enter the inh-map-ss command and specify the EIR subsystem number displayed in 1.
    inh-map-ss:ssn=100
    
    rlghncxa03w 10-06-28 14:42:38 GMT  EAGLE5 42.0.0
    Inhibit map subsystem command sent to all SCCP cards.
    Command Completed.
    
  4. Verify that the EIR subsystem is out of service 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.

    When this 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; enter 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.
    

4.8 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. If either of these conditions is not met, the EAGLE will not reply to the SOR message.
  • The local subsystem is available
  • The total load on the DSM subsystem is less than 45% of its capacity

4.8.1 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  EAGLE5 42.0.0 
        APPL   SSN  STAT
        EIR    11   offline            
     
        SS-APPL TABLE IS 25% FULL (1 OF 4)
    ;
    If the EIR 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=eir:nstat=online
  4. Verify the changes by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE5 42.0.0 
        APPL   SSN  STAT
        EIR    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.

4.8.2 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 42.0.0 
        APPL   SSN  STAT
        EIR    11   online            
     
        SS-APPL TABLE IS 25% FULL (1 OF 4)
    ;
    If the EIR 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 Taking the Subsystem Application Online.
    inh-map-ss:ssn=11
        rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 42.0.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=eir:nstat=offline
  6. Verify the changes by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 42.1.0 
        APPL   SSN  STAT
        EIR    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.

4.9 Provisioning the EIR Service Selectors

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

4.9.1 Adding an EIR Service Selector

This procedure is used to add a service selector for the EIR feature.

The EIR feature must be enabled and turned on before an EIR service selector can be added.

  1. Verify that the EIR feature is enabled and turned on, by entering the rtrv-ctrl-feat command.

    If the EIR feature is enabled and turned on, the status of the EIR feature is on

    rlghncxa03w 10-06-30 21:15:37 GMT  EAGLE5 42.0.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    EIR                       893012301  on          ----
    ;
    • If the EIR feature is enabled and turned on, continue with 2.
    • If the EIR feature is not enabled or turned on, go to the Enabling and Turning On the EIR Feature procedure to enable and turn on the EIR feature. Then continue with 2.
  2. Display the EIR service selectors in the database, using the rtrv-srvsel:serv=eir command.
    
    rlghncxa03w 10-06-28 14:42:38 GMT  EAGLE5 42.0.0
    
    GTII  TT   NP       NAI   SSN  SNP    SNAI   SERV
    4     1    e214     intl  3    ----   -----  eir
    4     2    e214     intl  *    ----   -----  eir
    
    SRV SELECTOR table is (4 of 20992)   1 % full
    ;
  3. Add the EIR service selector using the ent-srvsel command.

    For example, enter a command like these:

    ent-srvsel:serv=eir:tt=35:ssn=100:gtin=4:np=e214:nai=natl

    ent-srvsel:serv=eir:tt=57:ssn=75:gtin=2

  4. Verify the changes; enter the rtrv-srvsel command with the parameters and values used in 3.

    rtrv-srvsel:serv=eir:tt=35:ssn=100:gtin=4:np=e214:nai=intl

    
    rlghncxa03w 10-06-28 14:42:38 GMT  EAGLE5 42.0.0
    
    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV
    4     35   e214     natl  100  ----  -----  eir
    
    SRV SELECTOR table is (6 of 20992)   1 % full
    ;

    rtrv-srvsel:serv=eir:tt=57:ssn=75:gtin=2

    
    rlghncxa03w 10-06-28 14:42:38 GMT  EAGLE5 42.0.0
    
    GTIN  TT   NP       NAI   SSN   SNP    SNAI   SERV
    2     57   ---      ----   75   ----   -----  eir
    
    SRV SELECTOR table is (6 of 20992)   1 % full
    ;
  5. 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.
    

4.9.2 Removing a Service Selector

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

  1. Display the service selectors in the database, using the rtrv-srvsel command.

    The serv, gtii, gtin, gtin24, tt, ssn, np, nai, npv, and naiv parameter values can be used to limit the amount of information displayed with the rtrv-srvsel command.

  2. Remove the service selector from the database, using the dlt-srvsel command.

    To remove a service selector, the gtii/gtin/gtin24, tt, and ssn parameter values must be entered as shown in the rtrv-srvsel output.

    For example, enter a command like these:

    dlt-srvsel:serv=eir:tt=35:ssn=100:gtin=4:np=e214:nai=natl

    dlt-srvsel:serv=eir:tt=57:ssn=75:gtin=2

  3. Verify the changes; enter 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 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.
    

4.9.3 Changing an Existing Non-EIR Service Selector to an EIR Service Selector

This procedure is used to change a non-EIR service selector to an EIR service selector for the EIR feature.

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

:nserv – New DSM service type, EIR

:nsnp – An EIR 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.

:nsnai – An EIR 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 chg-srvsel command requires that the gtii/gtin/gtin24, tt, np, nai, npv, naiv, ssn, and serv parameters be specified with the values shown in the rtrv-srvsel output for the service selector being changed. If you want to change any of these parameter values for an EIR service selector, use the Removing a Service Selector procedure to remove the existing service selector. Then use the Adding an EIR Service Selector procedure to add the new EIR service selector with the new parameter information.

  1. Display the service selectors in the database using the rtrv-srvsel command.
    
    rlghncxa03w 03-06-28 14:42:38 GMT  EAGLE5 42.0.0
    GTII  TT   NP       NAI   SSN  SNP   SNAI   SERV
    4     1    e214     intl  3    ---    ---   eir
    4     1    e214     intl  4    e164  intl   gport
    4     1    e214     intl  5    e164  intl   smsmr
    4     2    e214     intl  *    ---   ---    eir
    
    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV
    2     75   ---      ---   57   ---   ---    eir
    4     4    e214     natl  34   e164  intl   gflex
    4     9    e214     natl  250  e164  intl   gflex
    4     35   e214     natl  100  ---   ---    eir
    
    SRV SELECTOR table is (8 of 20992)   1 % full
    ;
    • If the rtrv-srvsel output in 1 does not show any EIR service selectors, continue with 2.
    • If the rtrv-srvsel output in 1 shows at least one EIR service selector, go to 3.
  2. Verify that the EIR feature is enabled and turned on; enter the rtrv-ctrl-feat command.
    • If the EIR feature is not enabled (does not appear in the command output ) or is not turned on, go to the Enabling and Turning On the EIR Feature procedure to enable and turn on the EIR feature. Then continue with 3.
    • If the EIR feature is enabled and turned on, continue with 3.
  3. Change the service selector, using the chg-srvsel command.
    For example, enter a command like the following one:

    chg-srvsel:gtin=4:tt=4:np=e214:nai=natl:ssn=34:nsnp=none :nsnai=none:nserv=eir

    If the snp or snai parameter values are shown as dashes in the rtrv-srvsel output, these parameters 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 with the chg-srvsel command.

    If the gtii/gtin/gtin24 parameter value is 4, either the np and nai, 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 naiv parameters so long as parameter values be specified correspond to the values shown in the rtrv-srvsel output.

    The gtii/gtin/gtin24, tt, ssn, np, nai, npv, or naiv parameters cannot be changed in this procedure. To change these parameters, use the Removing a Service Selector procedure to remove the service selector. Then use the Adding an EIR Service Selector procedure to re-enter the service selector as an EIR service selector.

  4. Verify the changes; enter the rtrv-srvsel command with the parameters and values that were used in 3.
  5. 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.
    

4.10 Changing the EIR Options

This procedure is used to change the EIR Global Response status, EIR Response Type, and EIR IMSI Check status option values with the chg-gsmopts command. The chg-gsmopts command uses these parameters to detect circular routing in the system. See EAGLE EIR GSM Options Commands.

  1. Verify that the EIR feature is enabled and turned on; enter 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
        EIR                       893012301  on          ----
    ;
    
    • If the EIR feature is not enabled (the EIR entry does not appear in the output) or is not turned on, go to the Enabling and Turning On the EIR Feature procedure to enable and turn on the EIR feature. Then continue with 2.
    • If the EIR feature is enabled and turned on, continue with 2.
  2. Display the status of the EIR options; enter the rtrv-gsmopts command.
  3. Change the EIR options by entering the chg-gsmopts command with at least one of the EIR option parameters.
  4. Verify the changes; enter the rtrv-gsmopts command.
  5. Back up the 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.
    

4.11 Configuring EIR S13/S13’ Interface Support (Diameter EIR/DEIR)

This procedure configures the EIR S13/S13’ Interface Support feature. 5 through 8 configure the DEIR connection.

  1. Enable the EIR S13/S13’ Interface Support feature with the enable-ctrl-feat command.

    enable-ctrl-feat:partnum=893042401:fak=<FeatureAccessKey>

  2. Turn on the EIR S13/S13’ Interface Support feature with the chg-ctrl-feat command.

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

  3. Provision the S13 card (DEIR64).

    ent-card:loc=1101:type=dsm:appl=deir64

  4. Configure Port A and B of the S13 card.

    chg-ip-lnk:port=a:submask=255.255.255.0:mcast=yes:ipaddr=192.168.120.11:loc=1101:duplex=full:speed=100

    chg-ip-lnk:port=b:submask=255.255.255.0:mcast=no:ipaddr=10.248.13.11:loc=1101:duplex=full:speed=100

  5. Enter the HOST information.

    ent-ip-host:host=hss:ipaddr=10.248.13.11:type=local:realm=abcdefg.com

    ent-ip-host:host=lmno:ipaddr=10.248.13.9:type=remote:realm=lmnopq.com

    ent-ip-host:host=lmno3:ipaddr=10.248.13.3:type=remote:realm=lmnopq.com

  6. Enter the SCTP Association.

    ent-assoc:aname=assoc1:lhost=hss:lport=5555:rhost=lmno:rport=5556

    ent-assoc:aname=assoc2:lhost=hss:lport=5557:rhost=lmno3:rport=5558

  7. Enter the Diameter Connection.

    ent-dconn: dcname=dcon1:aname=assoc1

    ent-dconn: dcname=dcon2:aname=assoc2

  8. Open the Diameter Connection.

    chg-assoc:aname=assoc1:open=yes

    chg-assoc:aname=assoc2:open=yes

4.12 Configuring DEIR on SLIC

This procedure configures the EIR S13/S13’ Interface Support (DEIR) feature on the SLIC card to provide network redundancy. Step 5 through step 8 configure the DEIR connection.

  1. Enable the DEIR feature with the enable-ctrl-feat command.

    enable-ctrl-feat:partnum=893042401

  2. Turn on the DEIR feature with the chg-ctrl-feat command.

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

  3. Provision the SLIC S13 card (DEIR64).

    ent-card:loc=1101:type=dsm:appl=deir64

  4. Configure ports A, B, C, and D of the SLIC S13 card.

    chg-ip-lnk:port=a:submask=255.255.255.0:mcast=yes:ipaddr=192.168.120.11:loc=1101:duplex=full:speed=100

    chg-ip-lnk:port=b:submask=255.255.255.0:mcast=no:ipaddr=10.248.13.11:loc=1101:duplex=full:speed=100

    chg-ip-lnk:port=c:submask=255.255.255.0:mcast=no:ipaddr=10.248.14.12:loc=1101:duplex=full:speed=100

    chg-ip-lnk:port=d:submask=255.255.255.0:mcast=yes:ipaddr=192.168.121.20:loc=1101:duplex=full:speed=100

  5. Enter the HOST information.

    ent-ip-host:host=hss:ipaddr=10.248.13.11:type=local:realm=abcdefg.com

    ent-ip-host:host=hss2:ipaddr=10.248.14.12:type=local:realm=abcdefg.com

    ent-ip-host:host=lmno:ipaddr=10.248.13.9:type=remote:realm=lmnopq.com

    ent-ip-host:host=lmno3:ipaddr=10.248.13.3:type=remote:realm=lmnopq.com

    ent-ip-host:host=lmno4:ipaddr=10.248.14.5:type=remote:realm=lmnopq.com

    ent-ip-host:host=lmno5:ipaddr=10.248.14.7:type=remote:realm=lmnopq.com

  6. Enter the SCTP Association.

    ent-assoc:aname=assoc1:lhost=hss:alhost=hss2:lport=5555:rhost=lmno:rport=5556

    ent-assoc:aname=assoc2:lhost=hss:alhost=hss2:lport=5557:rhost=lmno3:rport=5558

  7. Enter the Diameter Connection.

    ent-dconn: dcname=dcon1:aname=assoc1

    ent-dconn: dcname=dcon2:aname=assoc2

  8. Open the Diameter Connection.

    chg-assoc:aname=assoc1:open=yes:rhost=lmno4:rhosttype=alternate

    chg-assoc:aname=assoc2:open=yes:rhost=lmno5:rhosttype=alternate

4.13 Activating the EIR Local Subsystem

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

When all feature configuration is complete, the EIR 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 command can be used to change the online or offline database state of the subsystem. The rtrv-ss-appl command displays the online or offline provisioned value.

When the first Service Module card is loaded, the local subsystem operating 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 to allowed or inhibited. The inh-map-ss command does not necessarily force a state change, because it can fail if the mate does not send an 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 because the subsystem must be online to be in the Allowed state. 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=eir :nstat=online Changes local subsystem status to online. No change to local subsystem status in the database
chg-ss-appl:appl=eir :nstat=offline Command is rejected because the subsystem must be inhibited to go offline. Changes local subsystem database status to offline.
  1. Display the online/offline status of the EIR subsystem application, by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE5 39.2.0 
        APPL   SSN  STAT
        EIR    11   offline            
     
        SS-APPL TABLE IS 25% FULL (1 OF 4)
    ;
  2. Change the EIR subsystem status to online.
    chg-ss-appl:appl=eir:nstat=online
  3. Enter the command to allow the EIR subsystem to begin operation.
    alw-map-ss:ssn=<EIR ssn>
        integrat40 08-05-24 10:37:22 EST  EAGLE5 39.2.0
        Allow map subsystem command sent to all SCCP cards.
        Command Completed.
    ;
  4. Display and verify the operating status of the EIR subsystem, by entering the rept-stat-sccp command.