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
- 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 Verify that the displayed serial number is correct for the system. If no
serial number is displayed, enter the Enter the |
A sufficient number of Service Module cards must be equipped. |
Enter the 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 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 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 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.
- Verify, and provision if needed, the system prerequisites. See System Prerequisites.
- Verify, and provision if needed, the feature prerequisites. See EIR Feature Prerequisites.
- Enable the EIR feature, set system STP options, and turn on the EIR feature. See Enabling and Turning On the EIR Feature.
- 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.
- 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:- ANSI
- ITU-N
- ITU-N Spare
- ITU-I
- ITU-I Spare
- Provision the state and subsystem number for the EIR local subsystem application. See Adding the EIR Subsystem Application.
- 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.
- Provision GSM options, including the EIR Global Response status, EIR Response Type, and EIR IMSI Check status options. See Changing the EIR Options.
- Activate the EIR local subsystem. See Activating the EIR Local Subsystem.
-
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
- 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.
4.7 Provisioning the EIR Local Subsystem
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).
Table 4-3 EIR Local Subsystem Prerequisites
Prerequisite | Verification |
---|---|
The EIR feature must be enabled and turned on. |
Enter the 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 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 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.
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.
- The local subsystem is available
- The total load on the DSM subsystem is less than 45% of its capacity
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.
4.9.2 Removing a Service Selector
This procedure is used to remove a service selector from the database.
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
: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.
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.
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.
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. |