This chapter also contains the procedures that are common to configuring either the Global Title Translation (GTT) feature or the Enhanced Global Title Translation (EGTT) feature. To find out about the differences between Global Title Translation feature and the Enhanced Global Title Translation feature, refer to the Upgrading from Global Title Translation (GTT) to Enhanced Global Title Translation (EGTT) section.

The Global Title Translation (GTT) feature is designed for the signaling connection control part (SCCP) of the SS7 protocol. The EAGLE uses this feature to determine to which service database to send the query message when a Message Signaling Unit (MSU) enters the EAGLE and more information is needed to route the MSU.

If an MSU enters the EAGLE and more information is needed to route the MSU, the SCCP of the SS7 protocol sends a query to a service database to obtain the information. The EAGLE uses the GTT feature for the SCCP to determine which service database to send the query messages to. These service databases are also used to verify calling card numbers and credit card numbers. The service databases are identified in the SS7 network by a point code and a subsystem number.

The GTT feature uses global title address (GTA) information to determine the destination of the MSU. The translation type (TT) indicates which global title translation table is used to determine the routing to a particular service database. Each global title translation table includes the point code (pc) of the node containing the service database, the subsystem number (ssn) identifying the service database on that node, and a routing indicator (ri). The routing indicator determines if further global title translations are required. GTA and TT are contained in the called party address (CDPA) field of the MSU.

The global title translation feature changes the destination point code and the origination point code in the routing label. The global title information is not altered. The routing label is changed to indicate the new destination point code retrieved from the global title translation and the origination point code is set to the EAGLE’s point code.

Depending on how the global title translation data is configured, the routing indicator, the subsystem number, or the translation type in the called party address may also be changed by the global title translation feature. The gray shaded areas in Figure 2-1 show the message fields affected by global title translation.

Figure 2-1 ANSI and ITU MSU Fields affected by the Global Title Translation Feature

The GTT feature allows global title translation on global title addresses of fixed length. There are three optional add-on features that enhance the functionality of the global title translation feature:

• The Variable-length Global Title Translation feature (VGTT) feature allows global title translation on global title addresses of varying length. For more information on this feature, refer to the Variable-length Global Title Translation Feature section.
• The Advanced GT Modification feature allows the EAGLE to modify other fields of an MSU in addition to the translation type when the MSU requires further global title translation and the translation type is to be replaced. For more information about this feature, refer to the Advanced GT Modification Feature section.
• The ANSI/ITU SCCP Conversion Feature converts SCCP messages between the ANSI and ITU formats. For more information about this feature, refer to the ANSI/ITU SCCP Conversion Featuresection.

The EAGLE supports:

• 269,999, 400,000, or 1,000,000 global title translations. The system default is 269,999 global title translations. This quantity can be increased to 400,000 by enabling the feature access key for part number 893-0061-01, or to 1,000,000 by enabling the feature access key for part number 893-0061-10. For more information on enabling these feature access keys, refer to the Enabling the XGTT Table Expansion Feature procedure.
• A maximum of 200,000 global title translations assigned to a translation type.
• 512 translation types, 256 translation types for ANSI MSUs, and 256 translation types for ITU MSUs.
• 1024, 2000, or 3000 remote point codes (mated applications), with up to 10 subsystems at each point code. The system default is 1024 mated applications. This quantity can be increased to 2000 by enabling the feature access key for part number 893-0077-01, or to 3000 by enabling the feature access key for part number 893-0077-10. For more information on enabling these feature access keys, refer to the Enabling the XMAP Table Expansion Feature procedure.

The GTT feature requires one of the following cards:

• Database Services Module (DSM) (Refers to the E5-SM4G or E5-SM8G-B card)
• SLIC card

For more information on these cards, refer to the Adding a Service Module procedure or to Hardware Reference.

The Enhanced Global Title Translation (EGTT) feature is designed for the signaling connection control part (SCCP) of the SS7 protocol. The EAGLE uses this feature to determine to which service database to send the query message when a Message Signaling Unit (MSU) enters the EAGLE and more information is needed to route the MSU.

If an MSU enters the EAGLE and more information is needed to route the MSU, the SCCP of the SS7 protocol sends a query to a service database to obtain the information. The EAGLE uses the EGTT feature for the SCCP to determine which service database to send the query messages to. The service databases are identified in the SS7 network by a point code and a subsystem number.

The EGTT feature uses global title information (GTI) to determine the destination of the MSU. The EAGLE supports ANSI GTI format 2 and ITU GTI formats 2 and 4. The GTI is contained in the called party address (CDPA) field of the MSU. For ITU GTI format 4, the GTI is made up of the Numbering Plan (NP), Nature of Address Indicator (NAI), and Translation Type (TT) selectors.

The EGTT feature allows global title translation on global title addresses of fixed length. There are three optional add-on features that enhance the functionality of the enhanced global title translation feature:

• The Variable-length Global Title Translation feature (VGTT), allows global title translation on global title addresses of varying length. For more information on this feature, refer to the Variable-length Global Title Translation Featuresection.
• The Advanced GT Modification feature allows the EAGLE to modify other fields of an MSU in addition to the translation type when the MSU requires further global title translation and the translation type is to be replaced. For more information about this feature, refer to the section Advanced GT Modification Feature.
• The ANSI/ITU SCCP Conversion Feature converts SCCP messages between the ANSI and ITU formats. For more information about this feature, refer to the ANSI/ITU SCCP Conversion Feature section.

The EGTT feature requires one of the following cards:

• EAGLE 5-Service Module 8GB (E5-SM8G-B) or SLIC

For more information on these cards, refer to the Adding a Service Module procedure or to Hardware Reference.

Inclusion of SSN in the CDPA

When the obtained translation data contains a subsystem, the translated SSN is placed in the SCCP CDPA before the message is sent to the next node. However, when no SSN is present in the CDPA, this insertion applies to ITU messages only. ANSI messages that do not contain an SSN in the CDPA will be rejected. The gray shaded areas in Figure 2-2 show the message fields affected by enhanced global title translation.

Figure 2-2 ANSI and ITU MSU Fields affected by the Enhanced Global Title Translation Feature

A translation type or GTT set can contain global title addresses of varying length. If the Variable-length Global Title Translation (VGTT) feature is turned on with the chg-feat command, a translation type or GTT set contain up to 10 different length global title addresses. If the Support for 16 GTT Lengths in VGTT feature is enabled and turned on with the enable-ctrl-feat and chg-ctrl-feat commands, a translation type or GTT set can contain up to 16 different length global title addresses. The Support for 16 GTT Lengths in VGTT feature cannot be enabled and turned on unless the VGTT feature is turned on.

The length of the global title address is only limited by the range of values for the gta and egta parameters of either the ent-gtt and chg-gtt commands, if only the GTT feature is turned on, or the ent-gta and chg-gta commands, if the EGTT feature is turned on, and by the global title addresses already assigned to the translation type or GTT set. The length of a global title address is from 1 to 21 digits, or 1 to 21 hexadecimal digits if the Hex Digit Support for GTT feature is enabled. The ndgt parameter of the ent-tt or ent-gttset command has no effect on the length of the global title address and cannot be used. If the ndgt parameter is specified with the ent-tt or ent-gttset command and the VGTT feature is on or the Support for 16 GTT Lengths in VGTT feature is enabled and turned on, the ent-tt or ent-gttset command is rejected with this message.

E4011 Cmd Rej: NDGT parameter is invalid for VGTT

As global title addresses of different lengths are assigned to a specific translation type, these lengths are displayed in the NDGT field of the rtrv-tt command output, as shown in the following example.

rlghncxa03w 09-05-25 09:57:31 GMT  EAGLE5 41.0.0
TYPEA      TTN        NDGT
1          lidb       6, 12, 15
2          c800       10
3          d700       6

ALIAS      TYPEA
50         3
65         3

TYPEI      TTN        NDGT
105        itudb      8

ALIAS      TYPEI
7          105

TYPEN      TTN        NDGT
120        dbitu      7

ALIAS      TYPEN
8          120

If the global title addresses are assigned to a GTT set, these lengths are displayed in the NDGT field of the rtrv-gttset command output, as shown in the following example.

rlghncxa03w 09-07-07 00:30:31 GMT EAGLE5 41.1.0
GTTSN     NETDOM  NDGT
lidb      ansi    3, 7, 10
t800      ansi    6
si000     itu     15
imsi      itu     15
abcd1234  itu     12

GTT-SET table is (5 of 2000) 1% full.

In the rtrv-tt output example, the ANSI translation type 1 contains three different length global title addresses; global title addresses containing 6 digits, 12 digits, and 15 digits.

In the rtrv-gttset example, the GTT set lidb contains three different length global title addresses; global title addresses containing 3 digits, 7 digits, and 10 digits.

When the VGTT feature is on, and the last global title address of a particular length is deleted for the specified translation type or GTT set, then that length is no longer supported. That length is not displayed in the NDGT field of the rtrv-tt or the rtrv-gttset output. For example, if the last 6-digit global title address is deleted from ANSI translation type 1 (from the previous example), the NDGT field of the rtrv-tt command shows only the numbers 12 and 15 in the NDGT field indicating that ANSI translation type 1 contains only 12- and 15-digit global title addresses. If the last 7-digit global title address is deleted from GTT set lidb (from the previous example), the NDGT field of the rtrv-gttset command shows only the numbers three and 10 in the NDGT field indicating that GTT set lidb contains only 3- and 10-digit global title addresses.

If the translation type has the maximum number of different length global title addresses assigned to it, and another global title address is specified for the translation type, the length of the global title address being added to the translation type must be the same as one of the lengths already assigned to the translation type. If the length of the global title address is not one of the lengths shown in the rtrv-tt output, the ent-gtt command is rejected with this message.

E4007 Cmd Rej: Exceeding max GTA Lengths supported per TT

If the GTT set has the maximum number of different length global title addresses assigned to it, and another global title address is specified for the GTT set, the length of the global title address being added to the GTT set must be the same as one of the lengths already assigned to the GTT set. If the length of the global title address is not one of the lengths shown in the rtrv-gttset output, the ent-gta command is rejected with this message.

E4008 Cmd Rej: Exceeding max GTA Lengths supported per GTTSET

If the translation type or GTT set has less than the maximum number of different length global title addresses assigned to it, and another global title address is specified for the translation type or GTT set, the length of the global title address can be from one to 21 digits and does not have to match the length of the other global title addresses assigned to the translation type or the GTT set.

If the VGTT feature is off, shown the entry VGTT = off in the rtrv-feat output, the global title address length must be equal to the number of digits specified by the given translation type or GTT set. The length of the global title address can be verified with the rtrv-tt or rtrv-gttset command.

The VGTT and the Support for 16 GTT Lengths in VGTT features require that a service module is installed in the EAGLE. Adding a Service Module shows the type of service modules that can be used depending on which features are on or enabled.

This feature allows the EAGLE to modify other fields of an MSU in addition to the translation type, destination point code, called party point code, called party SSN, routing indicator, numbering plan, and nature of address indicator when the MSU requires further global title translation and the translation type is to be replaced.

The numbering plan, nature of address indicator, and the prefix or suffix digits, in the called party address or calling party address portion of outbound MSUs can be changed with this feature to make the MSU more compatible with the network that the MSU is being sent to and to ensure that the MSU is routed correctly. These changes are made after the global title translation process, but before the MSU is routed to its destination.

This feature requires that service modules are installed in the EAGLE. Adding a Service Module shows the type of service modules that can be used depending on which features are on or enabled.

For the EAGLE to be able to make these changes to the called party address or calling party address portion of the MSU, the one of the Advanced GT Modification features shown in the following list must be enabled with the enable-ctrl-feat command.

• 893021801 - AMGTT - provides GT modification to both the called party address and the calling party address of SCCP messages. This part number can be specified only if no Advanced GT Modification feature is currently enabled.
• 893021802 - AMGTT CdPA Only - provides GT modification to the called party address of SCCP messages only. This feature and its part number is shown in the rtrv-ctrl-feat output only if the MGTT feature from previous releases was turned on when the Eagle was upgraded to the release containing the Advanced GT Modification feature. This part number cannot be specified with the enable-ctrl-feat command.
• 893021803 - AMGTT CgPA Upgrade - provides GT modification to the calling party address and called party address of SCCP messages. This part number can be specified only if the AMGTT CdPA Only feature (part number 893021802) is enabled.

Perform the Activating the Advanced GT Modification Feature procedure to enable the Advanced GT Modification feature.

After the Advanced GT Modification feature has been enabled, the parameters shown in this list are used to modify the calling party address or called party address of the SCCP message.

• gtmodid – The name of the GT modification identifier
• ntt – The new translation type. None of the Advanced GT Modification features have to be enabled to create an entry in the GT modification table that contains only the ntt parameter value.
• nnp – The new numbering plan
• nnai – The new nature of address indicator
• npdd – The number of digits to be deleted from the beginning of the Global Title Address digits (the prefix digits)
• npds – The digits that are being substituted for the prefix digits
• nsdd – The number of digits to be deleted from the end of the Global Title Address digits (the suffix digits)
• nsds – The digits that are being substituted for the suffix digits
• cgpassn – The calling party subsystem number
• gt0fill – Specifies whether the final 0 of the global title address is considered a valid digit in the global title address or as a filler during the GT modification process when going from GTI=2 to GTI=4. If the final 0 is considered as a filler, then it is ignored during the GT modification process. This parameter has two values, on or off. If the gt0fill value is on, the final 0 in the global title address is a filler. If the gt0fill value is off, the final 0 in the global title address is a valid digit.
• ngti – The new global title indicator value
• precd – Specifies whether the prefix or suffix digits take precedence when modifying the received global title address. This parameter can be specified only when the npdd/npds and the nsdd/nsds parameters are specified. This parameter has two values, pfx and sfx. When the precd value is pfx, the prefix digits (npdd/npds values) are processed before the suffix digits (nsdd/nsds) values.When the precd value is sfx, the suffix digits (nsdd/nsds values) are processed before the prefix digits (npdd/npds) values
• cggtmod - The calling party GT modification indicator. This parameter specifies whether or not calling party global title modification is required. This parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled. The cggtmod parameter can also be specified for when provisioning a linkset to indicate that calling party global title modification is required for SCCP traffic on the linkset. This parameter is configured with the ent-gtt, chg-gtt, ent-gta, or chg-gta commands.

To configure the cggtmod parameter, perform one of these procedures.

• Adding a Global Title Translation
• Changing a Global Title Translation
• Adding Global Title Address Information
• Changing Global Title Address Information

This feature allows GTT traffic between multiple nodes to be load shared when intermediate global title translation (routing indicator in the message is GT) is being performed. A mated relay node (MRN) group is provisioned in the database to identify the nodes that the traffic is load shared with, and the type of routing, either dominant, load sharing, or combined dominant/load sharing. This load sharing is performed after intermediate global title translation is performed on the message. For more information, refer to Provisioning MRN Entries.

Since some ANSI and ITU SCCP parameters are incompatible in format or coding, this feature provides a method for the EAGLE to convert these SCCP parameters in UDT, UDTS, XUDT, and XUDTS messages. Other types of SCCP messages (for example, XUDTS) are not supported and are discarded.

A specialized SCCP/TCAP conversion, introduced in EAGLE release 22.2 and used only in the Korean market, does not support this feature. The ANSI/ITU SCCP Conversion feature cannot be used with the EAGLE release 22.2 SCCP and TCAP Conversion features.

The ANSI/ITU SCCP Conversion feature provides a generic capability to correctly format and decode/encode these SCCP messages:

• UDT, UDTS, XUDT, and XUDTS messages. UDT and UDTS messages include SCMG messages, which are a specialized form of UDT messages.

• MTP routed SCCP messages.

• GT routed SCCP messages.

This feature also provides SCCP management (SCMG) across network type boundaries. For example, concerned signaling point codes for a mated application may be of a different network type than the primary point code of the mated application.

The ANSI/ITU SCCP Conversion is optional for ITU-X to ITU-Y domain crossing, where X and Y are different variants of ITU domains (ITU-I, ITU-N, ITU-I Spare and ITU-N Spare).

The Support of SCCP XUDT Messages feature allows the global title translation feature and the following SCCP services to process XUDT messages.

• G-FLEX – supported for segmented or non-segmented XUDT messages. G-Flex Map Layer Routing only supports non-segmented XUDT messages.
• INP – Message Relay service supports segmented and non-segmented XUDT messages. Call related query service (INP-QS) only supports non-segmented XUDT messages.
• G-PORTMNP - XUDT response generation (that is, XUDTSRI_ack), when an XUDT SRI message is received, is supported if the SRI is not segmented. G-PORT treats any segmented message (SRI or non-SRI) as a non-SRI message and message relay is performed on the message. G-PORT Message Relay is supported for all non-SRI messages, including segmented and non-segmented, Class 0 and Class 1.
• A-PORT MNP - XUDT response generation, when an XUDT LocationRequest message is received, is supported if the XUDT message is not segmented. A-PORT treats any segmented message as a non-LocationRequest message and message relay is performed on the message. A-PORT Message Relay is supported for all non-LocationRequest messages, including segmented and non-segmented, Class 0 and Class 1.
• EAGLE's IS-41 to GSM Migration - XUDT response generation, when an XUDT/ GSMSRI, XUDTGSMSRI_for_SM, XUDT IS-41 LocationRequest, and XUDT IS-41 SMSRequest is received is supported if the message received by the EAGLE is not segmented. If the messages are segmented, the EAGLE performs message relay.
• GSMMAP Screening/Enhanced GSM MAP Screening - GSMMAP Screening (GMS) and Enhanced GSMMAP Screening (EGMS) supports screening on non-segmented XUDT messages, but does not support screening on segmented XUDT messages. If a segmented XUDT message is received on a linkset which has GMS or EGMS activated, GMS/EGMS is bypassed for that message, even if the parameters in the message match the provisioned screening rules. The SCCP processing of the message continues.
• Intermediate GTT Loadsharing - Class 0 and Class 1 SCCP XUDT messages are supported.
• Prepaid SMS Intercept (PPSMS) supports only non-segmented XUDT messages.
• MNP Check for MOSMS (MNPSMS) supports only non-segmented XUDT messages.

The following features do not support this feature:

• North American Local Number Portability (LNP)
• ANSI-ITU SCCP Conversion
• GSM Equipment Identity Register (EIR)

XUDT messages can be screened by Gateway Screening and all gateway screening stop actions can be applied to XUDT messages.

The In-Sequence Delivery of Class 1 UDT Messages provides for the sequencing for both UDT and XUDT Class 1 MSUs. All UDT/XUDT Class 1 messages are routed out of the EAGLE in the same order that they were received by the EAGLE. To enable the sequencing of UDT/XUDT Class 1 messages, the class1seq parameter value of the chg-sccpopts command is set to on.

When the class1seq parameter value is on, load sharing of these messages is performed in the dominant mode, overriding the load sharing configuration in the MAP and MRN tables. Delivering the UDT/XUDT Class 1 ITU messages in sequence is guaranteed only if the randsls parameter value of the chg-stpopts command is either off or class0. If you wish to guarantee delivering these messages in sequence, the class1seq=on and the randsls=all parameters should not be used together in the EAGLE. The value of the randsls parameter is shown in the rtrv-stpopts command.

When the class1seq parameter value is off, load sharing of the UDT/XUDT Class 1 messages is performed using the load sharing configuration in the MAP and MRN tables. The delivery of the UDT/XUDT Class 1 messages in sequence is not guaranteed.

If the messages are not in the correct sequence when they arrive at the EAGLE, they are not delivered to the next node in the correct sequence. The EAGLE does not perform message re-sequencing for messages that are received out of sequence, because the EAGLE is a transit node. Message re-sequencing is the responsibility of the originating and destination nodes.

GT-routed Class 0 UDT/XUDT messages are not sequenced, therefore, the EAGLE does not guarantee routing these messages out of the EAGLE in the same order that they were received.

The Origin-Based SCCP Routing feature provides additional options for routing SCCP messages. Without the Origin-Based SCCP Routing feature enabled, the routing of SCCP messages is based only on the called party address fields in the message. With the Origin-Based SCCP Routing feature enabled, SCCP messages can be routed based on the called party address (CdPA), the calling party address (CgPA), CgPA point code, CgPA subsystem number, or originating point code (OPC) fields in the message.

Origin-Based SCCP Routing provides three modes of global title translation:

• CdPA global title translation
• CgPA global title translation
• Advanced CdPA global title translation

The CgPA global title translation and Advanced CdPA global title translation modes are performed only if the Origin-Based SCCP Routing feature is enabled and turned on. The CdPA global title translation mode is performed whether or not the Origin-Based SCCP Routing feature is enabled and turned on.

The CdPA global title translation mode is based on the CdPA global title address, translation type, and global title indicator in the incoming message. If the global title indicator value in the message is 4, the CdPA numbering plan and nature of address indicator is also used in the CdPA global title translation mode.

The CgPA global title translation mode is based on this criteria.

• CgPA global title address, translation type, global title indicator, and subsystem number in the incoming message. If the global title indicator value in the message is 4, the CgPA numbering plan and nature of address indicator is also used in the CgPA global title translation mode.
• CgPA point code, translation type, global title indicator, and subsystem number in the incoming message. If the global title indicator value in the message is 4, the CgPA numbering plan and nature of address indicator is also used in the CgPA global title translation mode.

The Advanced CdPA global title translation mode is based on this criteria.

• The CdPA global title address
• The CgPA global title address, or CgPA point code, or Selector ID. If the Selector ID is used in the Advanced CdPA global title translation mode, the CgPA translation type and CgPA global title indicator are also used in the Advanced CdPA global title translation mode if the CgPA global title indicator value is not 0. If the CgPA GTI value is 0, then the CGPC GTT set name shown in the rtrv-sccpopts output is used to determine the global title translation performed on the message.
• The CgPA subsystem number
• The OPC from the MTP Routing Label
• The CdPA translation type
• The CdPA global title indicator
• If the global title indicator value in the message is 4, the CdPA numbering plan and nature of address indicator is also used in the Advanced CdPA global title translation mode and in the CgPA global title translation mode

The Hex Digit Support for GTT feature, when enabled, allows the EAGLE to process incoming messages that contain either decimal (0-9) or hexadecimal digits (0-9, a-f, A-F) in the global title address in the called party address field of the messages.

If the Hex Digit Support for GTT feature is enabled and the Origin-Based SCCP Routing feature is enabled and turned on, the EAGLE can process messages containing decimal or hexadecimal digits in the global title address in either the calling party address or the called party address fields of the messages, depending on the GTT hierarchy that is used to process the messages. For more information on the Origin-Based SCCP Routing feature, refer to the Origin-Based SCCP Routing section.

With the Hex Digit Support for GTT feature enabled, hexadecimal digits can be specified for the gta and egta parameters of the ent-gtt, chg-gtt, ent-gta, and chg-gta commands. If the Advanced GT Modification feature is enabled, hexadecimal digits can be specified for the values of the prefix and suffix deletion digit parameters (npds and nsds) of the ent-gtmod, and chg-gtmod commands. For more information on the Advanced GT Modification feature, refer to the Advanced GT Modification Feature section.

If the ANSI/ITU SCCP Conversion feature is enabled, hexadecimal digits can be specified for the values of the prefix and suffix deletion digit parameters (npds and nsds) of the ent-gtcnv or chg-gtcnv commands. For more information on the ANSI/ITU SCCP Conversion feature, refer to the ANSI/ITU SCCP Conversion Feature section.

After the Hex Digit Support for GTT feature is enabled, any existing range entries for global title addresses are treated as a range of hexadecimal values instead of a range of decimal values. For example, the database contains an entry that contains the range of global title addresses from 20 to 30. With the Hex Digit Support for GTT feature not enabled, this translation would match MSUs containing the global title addresses 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, and 30. With the Hex Digit Support for GTT feature enabled, this translation would match MSUs containing the global title addresses 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2A, 2B, 2C, 2D, 2E, 2F, and 30. Translations containing a single entry for the global title address are not changed.

If you wish to have different translated data for hexadecimal digits, the existing range entry can be split into 3 entries as follows in Table 2-1.

Hexadecimal digits cannot be used as a value for the gta parameter for the ent-gws-redirect and chg-gws-redirect commands.

Hexadecimal digits can be used as values for GSM MAP screening entries only if the Enhanced GSM MAP Screening feature is enabled.

Provisioning the Hex Digit Support for GTT Feature

To provision the Hex Digit Support for GTT feature, perform these steps.

1. Turn the GTT feature on using the chg-feat command. Add the required service modules to the database using the ent-card command. Perform the Adding a Service Module procedure. If Enhanced Global Title Translation will be used, turn the EGTT feature on using the chg-feat command.
2. Enable the Hex Digit Support for GTT feature using the enable-ctrl-feat command. Perform the Activating the Hex Digit Support for GTT Feature procedure.

   Note:

   Once this feature is enabled, the feature is also turned on. The chg-ctrl-feat cannot be used to turn this feature on. Once this feature is enabled, the feature cannot be turned off.
3. Provision the required destination point codes, linksets, signaling links, and routes, by performing these procedures.
   • Destination Point Codes - Adding a Destination Point Code procedure in Database Administration - SS7 User's Guide.
   • Linksets - Perform one of these procedures depending on the type of linkset.
     • SS7 Linkset - Adding an SS7 Linkset procedure in Database Administration - SS7 User's Guide
     • These procedures in Database Administration - IP7 User's Guide.
       • IP Gateway Linkset - Configuring an IPGWx Linkset
       • IPSG M2PA Linkset - Adding an IPSG M2PA Linkset
       • IPSG M3UA Linkset - Adding an IPSG M3UA Linkset
   • Signaling Links - Perform one of these procedures depending on the type of signaling link.
     • A low-speed SS7 signaling link - Adding an SS7 Signaling Link procedure in Database Administration - SS7 User's Guide
     • An E1 signaling link - Adding an E1 Signaling Link procedure in the Database Administration Manual - SS7
     • A T1 signaling link - Adding a T1 Signaling Link procedure in Database Administration - SS7 User's Guide
     • An ATM signaling link - Adding an ATM High-Speed Signaling Link procedure in Database Administration - SS7 User's Guide
     • These procedures in Database Administration - IP7 User's Guide.
       • IPLIMx Signaling Link - Adding an IPLIMx Signaling Link
       • IPGWx Signaling Link - Adding an IPGWx Signaling Link
       • IPSG M2PA Signaling Link - Adding an IPSG M2PA Signaling Link
       • IPSG M3UA Signaling Link - Adding an IPSG M3UA Signaling Link
   • Routes - Perform one of these procedures in Database Administration - SS7 User's Guide depending on the type of route.
     • A route containing an SS7 DPC - Adding a Route Containing an SS7 DPC procedure
     • A route containing a cluster point code - Adding a Route Containing a Cluster Point Code procedure
     • A route containing an IPGWx Linkset - Adding a Route Containing an IPGWx Linkset procedure

   Note:

   If only the GTT feature was turned on in step 1, perform steps 4 and 5. If the EGTT feature was turned on in step 1, skip steps 4 and 5 and perform steps 6, 7, and 8.
4. Provision the required translation types using the ent-tt command. Perform the Adding a Translation Type procedure.
5. Provision the required global title translations using the ent-gtt command. Perform the Adding a Global Title Translation procedure.

   Note:

   After the required global title translations have been provisioned in step 5, skip steps 6, 7, and 8.
6. Provision the required GTT sets using the ent-gttset command. Perform the Adding a GTT Set procedure.
7. Provision the required GTT translations using the ent-gta command. Perform the Adding Global Title Address Information procedure.

   Note:

   The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the ent-gta command are too long to fit on the ent-gta command line, perform the chg-gta command to complete adding the GTA entry. If the parameters and values specified with the chg-gta command are too long to fit on the chg-gta command line, perform the chg-gta command as many times as necessary to complete the GTA entry.
8. Provision the required GTT selectors using the ent-gttsel command. Perform the Adding a GTT Selector procedure.

The default behavior of the EAGLE for performing load sharing between nodes with the same relative cost is to perform the load sharing in a round-robin fashion. A limitation of this design is that all destinations have equal processing power and should receive an equal load. However, as new hardware is added to load-sharing groups, the load-sharing groups may have different processing capabilities. Customization of the load-sharing group would allow the traffic load to be distributed on the individual characteristics of each destination.

Another default behavior of the EAGLE is to route traffic to a load-shared group if any member of that group with the relative cost value is available. Depending on the traffic, this can overwhelm and congest a node, even though other nodes at different relative cost values could have handled the traffic.

Both of these scenarios can be solved with the Weighted GTT Load Sharing feature, which allows unequal traffic loads to be provisioned in mated application (MAP) and mated relay node (MRN) load sharing groups.

The MAP and MRN load sharing groups can be MAP or MRN load sharing groups without the Flexible GTT Load Sharing enabled, or MAP or MRN sets with the Flexible GTT Load Sharing feature enabled. Weighted GTT Load Sharing can be applied to only load shared or combined dominant/load shared MAP or MRN groups, and cannot be applied to solitary mated applications, or dominant MAP or MRN groups.

This feature also allows provisioning control over load sharing groups so that if insufficient capacity within the load sharing group is available, the load sharing group is not used.

Weighted GTT Load Sharing provides two controls for GTT traffic distribution through either the MAP or MRN groups:

• Individual weighting for each entity in a relative cost (RC) group
• In-Service threshold for each RC group

An RC group is a group of entries in either a MAP group or an MRN group that have the same relative cost value. An entity is either a point code entry in the MRN table or a point code and subsystem number entry in the MAP table.

A MAP group or MRN group can also be referred to as an entity set.

Weighted GTT Load Sharing can be applied to only load shared or combined dominant/load shared MAP or MRN groups, and cannot be applied to solitary mated applications, or dominant MAP or RN groups.

Transaction-Based GTT Load Sharing allows messages with the same transaction parameters (TCAP, SCCP, MTP, ENHMTP, MTPSCCP or ENHMTPSCCP parameters) to be routed to the same destination within an entity set. An entity set is a group of entities that are used to determine the proper destination of a post-GTT message. This group of entities can be one of the following:

• A mated application (MAP) group
• A mated relay node (MRN) group
• A mated application set (MAPSET), if the Flexible GTTLoad Sharing feature is enabled
• A mated relay node set (MRNSET), if the Flexible GTTLoad Sharing feature is enabled.

This feature applies to the following types of SCCP messages:

• UDT/UDTS class 0 messages
• UDT/UDTS class 1 messages
• XUDT/XUDTS class 0 messages
• XUDT/XUDTS class 1 messages.

The parameters used for Transaction-Based GTT Load Sharing are selected using the chg-sccpopts command. These parameters are:

• :tgtt0 – enable or disable Transaction-Based GTT Load Sharing for SCCP Class 0 UDT, UDTS, XUDT, or XUDTS messages.
• :tgtt1 – enable or disable Transaction-Based GTT Load Sharing for SCCP Class 1 UDT, UDTS, XUDT, or XUDTS messages.
• :tgttudtkey – the Transaction Parameter for the incoming UDT or UDTS messages.
• :tgttxudtkey – the Transaction Parameter for the incoming XUDT or XUDTS messages.

Figure 2-3 describes how the Transaction-Based GTT Load Sharing SCCP options are used.

Figure 2-3 Transaction-based GTT Load Sharing SCCP Options

For more information on provisioning the Transaction-Based GTT Load Sharing option parameters, refer to the Changing the Transaction-Based GTT Load Sharing Options procedure.

Only load shared and combined dominant/load shared entity sets are used to determine the routing for messages that are processed by the Transaction-Based GTT Load Sharing feature.

Using a load shared entity set, the entire entity set is a part of one RC group and the messages are load-shared based on the Transaction Parameter in the entities in the entity set. If none of the entities in the entity set are available for routing, then the message is discarded and a UDTS/XUDTS message is generated if "Return on Error" is set in the SCCP message. A UIM is generated indicating that the message has been discarded.

Using a combined dominant/load shared entity set, the RC group containing the point code, or point code and SSN, obtained as a result of the global title translation process is used to determine how the message is routed. If none of the entities in this RC group are available for routing, the next higher cost RC group is chosen. This is repeated until an entity in an entity set is available for routing. When an entity is found that is available for routing, the message is routed according to the criteria in that entity. If none of the entities in the entity set are available for routing, the message is discarded. A UDTS/XUDTS message is generated if “Return on Error” is set in the SCCP message. A UIM is generated indicating that the message has been discarded.

Once the MSU key is generated, it is passed to to the Weighted GTT Load Sharing mode entity sets to determine how the message will be routed. If the Weighted GTT Load Sharing feature is active and weights have been assigned to the entity set, the Weighted GTT Load Sharing feature uses these weights to determine how to route the message. If no weights have been assigned to the entity set, then each RC group in the entity set is considered to be equally weighted.

Static routing is performed on all the messages that the Transaction-Based GTT Load Sharing feature has assigned an MSU key. Static routing always assigns an MSU key to the same node within an RC group. If static routing does not provide an available entity for routing the message, dynamic routing is used to find an available entity for routing the message. Figure 2-4 illustrates this process.

Figure 2-4 Message Routing using Transaction-Based GTT Load Sharing

This feature detects SCCP looping of UDT/UDTS and XUDT/XUDTS messages. The SCCP Loop Detection feature requires a feature access key (FAK) for part number 893-0165-01 to enable the feature.

Normally, an STP sends GTT messages to the capability point codes (CPCs) of mated nodes for load sharing. However, approach can result in SCCP looping if the destination point code is the same as the originating point code or the point code of any intermediate in the network.

This looping can be resolved by eliminating the use of CPCs and verifying at an intermediate STP whether the OPC of the incoming MSU is the same as the true point code (TPC) of the DPC after GTT. However, CPCs are often used to implement LNP in addition to the SCCP.

The SCCP Loop Detection feature resolves the looping issue by providing a correlation between the MTP-designated TPCs/secondary point codes (SPCs) and the CPCs for all concerned STPs.

The SCCP Loop Detection feature is provisioned by configuring the Loopset Table and adding a loopset to a to a Global Title Translation.

The loopset commands define the correlation between MTP-designated point codes and the capability point codes of the STPs that detect SCCP looping. The GTT commands allow the administration, deletion, and retrieval of loopset table entries for a particular Global Title Translation.

The SCCP Loop Detection feature operates in Regular or Discard modes. In the Regular (default) mode, the SCCP Loop Detection Feature generates a UIM when it detects SCCP looping but does not discard the MSU. This UIM allows the operator to capture and verify MSUs throughout the system for SCCP looping. In the Discard mode, the SCCP Loop Detection feature generates a UIM when it detects SCCP looping and discards the MSU.

Flexible Linkset Optional Based Routing allows the EAGLE to route GTT traffic based on the incoming link set and to route GTT traffic based on a variety of parameters (MTP, SCCP and TCAP depending on features that are enabled and turned on) in a flexible order on a per-translation basis.

Flexible Linkset Optional Based Routing can be used with or without the Origin-Based SCCP Routing or the TCAP Opcode Based Routing features. Flexible Linkset Optional Based Routing can be enabled and turned on only if the EGTT feature is turned on. If only the Flexible Linkset Optional Based Routing is enabled and turned on, the name of the incoming linkset that will help to determine how the GTT traffic is routed can be provisioned in the GTT selectors. If the Origin-Based SCCP Routing feature or the TCAP Opcode Based Routing feature is used with the Flexible Linkset Optional Based Routing feature, the name of the incoming linkset can be provisioned along with the provisioning for the Origin-Based SCCP Routing or the TCAP Opcode Based Routing features. Table 2-7 shows the type of GTT sets that can be provisioned for GTT selectors based on the features that are enabled and turned on.

Enhancements to Flexible Linkset Optional Based Routing

In previous releases, the GTT and TT command sets were replaced by the GTTSET, GTTSEL, and GTA command sets when the EGTT feature is turned on. Now the GTT and TT command sets can be used when EGTT feature is turned on.

In previous releases, the selid parameter in the ent-gttsel, dlt-gttsel, and chg-gttsel commands could be configured only when the Flexible Linkset Optional Based Routing feature is enabled and turned on or the Origin-Based SCCP Routing feature is enabled. Now the selid parameter of these commands can be configured when the EGTT feature is turned on.

An SCCP message (RT-on-GT or MTP-routed) received by the EAGLE can be routed (Relayed or Redirected) to another destination based on the routing data obtained from the EPAP database or PPSOPTS table by the EPAP-based service. This type of message is called a Service Relayed MSU. In previous releases, global title translation is not performed on Service Relayed MSUs. These messages are directly sent to destination obtained from EPAP database or PPSOPTS table.

Now global title translation can be performed Service Relayed MSUs. To do this, these three optional parameters of the ent-srvsel and chg-srvsel commands are supported on per Service Selector basis for the non-GTT Message Relay Services.

An example service selector entry is shown in Figure 2-5.

Figure 2-5 Message Relay Services and GTT Actions

The GTT Required option indicates whether global title translation needs to be performed after successfully finding the routing data from the EPAP database or PPSOPTS database for non-GTT Message Relay Services. If the routing data is not found for non-GTT Relay Services from the EPAP database or PPSOPTS database, the standard Fall through to GTT procedure shall be performed.

Fallback to GTT

Fallback to GTT allows global title translation to be performed on Service Relayed MSUs by using the GTT Required parameter on per Service Selector basis for the non-GTT Message Relay Services shown in Table 2-8. Provisioning of the GTT Required parameter can be performed only if the EAGLE contains E5-SM4G cards.

The GTT Required parameter is invoked only if a message is required to be relayed based on the routing data from EPAP database or PPSOPTS table after the successful execution of a non-GTT Message Relay Service. Table 2-8 lists the non-GTT Message Relay Services and the corresponding feature(s) which may result in the message being relayed based on the routing data from EPAP database or PPSOPTS table. If the GTT Required parameter value indicates that global title translation is required on the Service Relayed MSU, then global title translation is performed on the MSU modified by the relay service according to GTT hierarchy of the incoming link set. The default value of GTT Required parameter is set to indicate that global title translation is not required on the Service Relayed MSU. If global title translation is performed on the Service Relayed MSU successfully, then the message is processed through all the GTT-related features that are enabled and turned on.

Exceptions to Fallback to GTT

If a service performs global title translation on service specific parameters to obtain information required for message routing (for example, the MO SMS B-Party Routing feature in the SMSMR service finds the routing information by performing global title translation on the CDPN), then Fallback to GTT is not applied on those messages. The exceptions to Fallback to GTT are shown in Table 2-9.

The service selector search is not performed for the MTP-routed messages whose CDPA GTI value is 0 (zero). The parameters required to perform Fallback to GTT are not available for MTP-routed messages whose CDPA GTI value is 0 (zero). Fallback to GTT on Service Relayed MSUs does not apply to messages whose CDPA GTI value is 0 (zero). If a message whose CDPA GTI value is 0 (zero) is relayed by an EPAP-based service, then global title translation is not be performed on the message.

GTT Selector ID and the Service Selector

For the non-GTT Message Relay Services, shown in Table 2-8, GTT selector IDs (SELIDs) can be provisioned. Only one GTT selector ID is allowed for each service selector entry. The GTT selector ID is used to perform GTT selector searches while performing global title translation on the Service Relayed MSUs. The GTT selector ID is not used while performing global title translation as a part of the existing Fall through to GTT message processing. The GTT selector ID from service selector shall be used only in first GTT selector search. If further GTT selector searches are required (when the matching translation is provisioned with a CDSELID or CGSELID), then the GTT selector ID found from the previous matched translation is used as is currently done when processing the translation for the Origin-Based SCCP Routing and Flexible Linkset Optional Based Routing features. The default value for the GTT selector ID in the service selector entry is none. The GTT selector ID in the service selector can be provisioned when the EGTT feature is on. The Origin-Based SCCP Routing and Flexible Linkset Optional Based Routing features are not required to be enabled or turned on to provision the GTT selector ID in the service selector.

Default Action and the Service Selector

For the non-GTT Message Relay Services shown in Table 2-8, a default action can be provisioned for each service selector entry. The default action parameter in the service selector can be one of these values.

• Fall through to GTT
• The Discard GTT Action ID
• The UDTS GTT Action ID
• The TCAP Error GTT Action ID
• Fallback (route the MSU based on the relay data)

The default action from the service selector is used only if the GTT selector search using the GTT selector ID from the service selector fails while performing global title translation on the Service Relayed MSU.

If the GTT selector search using the GTT selector ID from the service selector fails and the default action in the service selector is Fall through to GTT, then the action that is performed depends on the value of the GTT selector ID in the service selector. If the GTT selector ID value in the service selector is none, then the message is discarded and UIM 1042 is generated. If the GTT selector ID value in the service selector is not none, then the GTT selector search is attempted again with GTT selector ID value of none. If the subsequent GTT selector search, attempted with GTT selector ID value of none, also fails, then the message is discarded and UIM 1042 is generated.

If the GTT selector search using the GTT selector ID from the service selector fails and the default action value in the service selector is either the Discard GTT Action ID, UDTS GTT Action ID, or the TCAP Error GTT Action ID, then the corresponding GTT action is performed.

If the GTT selector search using the GTT selector ID from the service selector fails and the default action value in the service selector is Fallback, then the message is relayed based on the routing data from the EPAP database or PPSOPTS table.

Overall Functionality

After successfully getting the routing data for non-GTT Message Relay Services, if the GTT Required value is set to Yes and the GTT SELID is provisioned for this service, global title translation is performed on the MSU with specified SELID value to find the matching translation based on the GTT hierarchy on the linkset on which this MSU arrived.

• If a matching GTT selector is not found, the default action is applied to the MSU. The default action can be any of the actions shown in the Default Action and the Service Selector section. The default value of default action parameter is Fallback (route the MSU based on the relay data).
• If a global title translation is not found, then existing global title translation error handling procedures are applied.
• If a matching global title translation is found and:
  • If the matched global title translation contains routing data, the global title translation routing data is used on top of the EPAP or PPSOPTS routing data.
  • If the matched global title translation doesn't contain routing data (xlat parameter value is none), the MSU continues to use the EPAP or PPSOPTS routing data.
  • If the matched global title translation contains values for the cggtmod or gtmodid parameters, then the cggtmod parameter value or the parameter values contained in the GT modification entry that is defined by the gtmodid parameter are applied to the MSU.
  • If a GTT action set is associated with the matched translation, then the GTT Actions feature is applied to the MSU.
  • If matched translation contains a value for the ccgt parameter, then the ccgt parameter value is applied to the MSU as is currently done with the Advanced GT Modification feature.

Linkset Based Routing

After the Flexible Linkset Optional Based Routing feature enabled and turned on, Eagle considers the incoming link set as part of the GTT selection process for performing global title translation. If EAGLE receives MSUs with the same routing information on different link sets, it has the flexibility to route them based on different GTT rules. This also applies to the messages that fall through to GTT after being processed by MPS based services on the EAGLE. The incoming link set of the original MSU is used for these messages.

MSUs generated by the EAGLE that require global title translation are handled differently since they do not have a valid incoming link set. A separate set of GTT selector entries can be provisioned for these MSUs.

A separate set of GTT selector entries can be provisioned for messages generated by the EAGLE.

Flexible Linkset Optional Based Routing GTT Hierarchies

The Flexible Linkset Optional Based Routing feature introduced four more GTT hierarchies in addition to the GTT hierarchies used for the Origin-Based SCCP Routing feature. These hierarchies are shown in Table 2-10. These GTT hierarchies are available only when the corresponding feature is enabled, and turned on if necessary. All the GTT hierarchies are available when both the Origin-Based SCCP Routing and the Flexible Linkset Optional Based Routing features are enabled, and turned on if necessary. The GTT hierarchy can be provisioned on a link set basis or a system wide basis. The default GTT hierarchy is CdPA only.

Fallback Option

The per-translation option overrides the system default just for that translation. The Origin-Based SCCP Routing hierarchies do not use the fallback option.

Routing when the Subsequent GTT Set Search Failed

In this example, Set 1 is used to start the search. The matching translation in Set 1 points to Set 2. The matching translation in Set 2 points to Set 3 and there is no matching translation found in Set 3. Since the fallback option for the matched translation in Set 2 set to No, the MSU is discarded.

Figure 2-6 Action When the Subsequent Translation Search Fails

If the matching translation is not found in Set 2 (Set 2 Translation in Figure 2-6 is not found) and since the fallback option value in the Set 1 Translation is set to Yes, the MSU is routed based on the routing data in the Set 1 Translation. If the matching translation in Set 2 does not contain any GTT set/SELID combination (the Set 3 GTT set as shown in Figure 2-6 is not provisioned), then the fallback option is ignored and the MSU is routed based on routing data in the Set 2 Translation. If the matching translation in Set 1 is not found, then the GTT process fails.

Routing When the Subsequent Search for the SELID Fails

In this example, Set 1 is used to start the search. The matching translation in Set 1 (for example, a CdPA SSN/Opcode/CdPA GTA translation) contains SELID/Set 2 and also Set 3 (in this case Set 3 is an OPC GTT set).

Figure 2-7 Action When the Subsequent SELID Search Fails

If a matching GTT selector is not found with an SELID in the Set 1 translation, the search continues searching for the matching translation in Set 3. If a matching translation is found in Set 3 and no matching translation is found in Set 4, the fallback option No in the Set 3 Translation is performed and the MSU is discarded. If a matching GTT selector is not found with an SELID in the Set 1 translation and a matching translation is not found in Set 3, the fallback option Yes in the Set 1 Translation is performed and the MSU is routed based on the routing data in the Set 1 Translation. If a GTT selector with an SELID results in a GTT set name that is already referred to, the action based on the fallback option in the Set 1 Translation is performed.

Routing When the Same GTT Set Name is Referred To More than Once

Figure 2-8 Action When the Same GTT Set Name is Referred to More Than Once

In Figure 2-8, even if the Set 5 Translation contains the Set 6 GTT set (Set 5 and Set 6 are that same type of GTT sets), the Set 6 Translation will be searched for the matching translation. If the Set 6 Translation contains the Set 1 GTT set and since Set 1 has already searched, the Set 1 translation is not searched again and the fallback option of the last matched translation is examined. Since the last matched translation is found in Set 6 and the fallback option is set to No, the MSU is discarded. UIM 1413 - GTT(FLOBR) failure: duplicate set name is generated to describe the condition. In Figure 2-8, if the Set 6 Translation was not found and since the fallback option in the Set 5 Translation is set to Yes, the MSU is routed based on the data in the Set 5 Translation.

Limiting the Number of Database Searches for the Flexible Linkset Optional Based Routing Feature

The number of database searches is limited to seven when the Flexible Linkset Optional Based Routing feature is enabled and turned on. This includes searching the GTT selector table when a translation contains the CgPA SELID or CdPA SELID parameter.

Figure 2-9 Limit the Number of Database Searches

As shown in Figure 2-9, when a translation contains the CdPA SELID or CgPA SELID, the search in the GTT selector table is also counted toward the maximum seven searches. After completing seven searches, if the search is terminated because of the maximum seven search criteria, the action defined in the last matched Set 4 Translation fallback option (in this case No) is performed and MSU is discarded. UIM 1412 - GTT (FLOBR) failure: max search depth is generated to describe the condition. After completing seven searches, if the last matched translation contains no GTT set/SELID data (if the CdPA SELID data is not provisioned in the Set 4 Translation), the MSU is routed based on the routing data in the Set 4 Translation. The first GTT selector search when the GTT functionality is selected (deriving Set 1 in Figure 2-9) is not counted toward the maximum seven search criteria.

Limiting the Number of GTT Set Searches for the Flexible Linkset Optional Based Routing Feature

The number of GTT set searches is limited to seven when the Flexible Linkset Optional Based Routing feature is enabled and turned on.

Figure 2-10 Limit the Number of GTT Set Searches

As shown in Figure 2-10, after completing seven GTT set searches, if the search is terminated because of the maximum of seven searches have been performed, the action defined by the fallback option in Set 7 Translation, in this case No, is performed and the MSU is discarded. UIM 1412 - GTT(FLOBR) failure: max search depth is generated to describe the condition. If the Set 7 Translation contains no GTT sets, Set 8 is this case, the MSU is routed based on the routing data in the Set 7 Translation.

GTT for MSUs Generated by the EAGLE

The EAGLE performs global title translation on some messages generated by itself. These messages are sent in response to queries received by local subsystems. SCCP UDTS and XUDTS messages also fall under this category. Global title translation is performed to find the destination for the responses when the SCCP calling party address in query messages is Route-on-GT. Since there is no valid incoming link set for messages generated by the EAGLE, a special set of GTT selector entries are used when the Flexible Linkset Optional Based Routing feature is enabled and turned on. The eaglegen=yes parameter in the ent-/dlt-/chg-/rtrv-gttsel commands is used to provision a GTT selector for messages generated by the EAGLE. If the eaglegen=no parameter is specified for a GTT selector, the GTT selector is not provisioned for messages generated by the EAGLE.

If the GTT set name assigned to a GTT selector for messages generated by the EAGLE is changed with the chg-gttsel command, the new GTT set must be a CdPA GTT set.

If no match is found in the GTT selector entries that contain the eaglegen=yes parameter, the entries with LSN value ANY are searched. If a matching entry is still not found, for GTI=4 entries, the GTT set with CdPA set type for NP and NAI values Default are returned. For GTI=2 entries, a match not found message is returned. The Flexible Linkset Optional Based Routing feature hierarchies do not apply for GTT selectors provisioned for messages generated by the EAGLE and the CDPA Only GTT mode is used for such translations.

GTT Selector Key

Table 2-11 defines the keys into GTT selector table based on the feature combination. If a feature supports specific parameters and that feature is not enabled or turned, if necessary, then default values for these parameters are entered into the database.

Searching Order in the GTT Selector Table with the Flexible Linkset Optional Based Routing Feature

Hardware Requirements

To enable the Flexible Linkset Optional Based Routing feature DSM or SLIC cards must be provisioned in the database. Any Legacy Cards must be replaced.

Provisioning the Flexible Linkset Optional Based Routing Feature

To provision the Flexible Linkset Optional Based Routing feature, perform these steps.

1. Turn the GTT and EGTT features on using the chg-feat command. Add the required DSM or SLIC cards to the database using the ent-card command. Perform Adding a Service Module.
2. Enable and turn on the Flexible Linkset Optional Based Routing feature using the enable-ctrl-feat and the chg-ctrl-feat commands. Perform Activating the Flexible Linkset Optional Based Routing Feature.
3. Provision the required GTT sets using the ent-gttset command. Perform Adding a GTT Set.
4. Provision the required GTT translations using the ent-gta command. Perform Adding Global Title Address Information.
5. Provision the required GTT selectors using the ent-gttsel command. Perform Adding a GTT Selector.
6. Change the default fallback option, if desired, using the chg-sccpopts command. Perform Changing the Default GTT Mode Options.

TCAP Opcode Based Routing allows EAGLE to route messages based on their operation codes. When the TCAP Opcode Based Routing feature is enabled and turned on, this information contained in the TCAP portion of messages is used for performing global title translation. TOBR is also able to process Segmented XUDT(S) message.

TCAP Opcode Based Routing requires that the Flexible Linkset Optional Based Routing feature is enabled and turned on. TCAP Opcode Based Routing can be used with or without the Origin-Based SCCP Routing feature. Table 2-7 shows the type of GTT sets that can be provisioned for GTT selectors based on the features that are enabled and turned on.

TOBR Enhancement

TCAP Opcode Based Routing provides additional capability to EAGLE to route the message based on Operation Code Tag. This routing enables the EAGLE to prevent the “Global Tag Abuse” security issue. To perform global title translation on ITU messages, EAGLE considers the following information contained in the TCAP portion of the message:

• Message Type / Package Type
• Application Context Name
• Operation Code
• Operation Code Tag

TCAP Decoding

As part of the TCAP Opcode Based Routing feature, the EAGLE attempts to decode TCAP portion of all UDT/UDTS/XUDT/XUDTS queries coming to service modules for global title translation. Messages are decoded only if a TOBR Opcode Quantity is enabled. The objective of this decoder is not to validate the correctness of the message but simply to obtain the required TCAP data. The message is validated only for the encoding rules that are required to successfully decode the required TCAP information. In general, Tag-Length-Value encoding is validated; unsupported Tag values are skipped if they are encountered, unless a specific Tag order is expected.

The Tag is composed of "Class", "Form", and "Tag code" components. The Tag Class consists of “Universal”, “Application-wide”, “Context-specific”, and “Private use” parameters. EAGLE allows messages only with TCAP Tag Class UNIVERSAL. TOBR returns decoding error in case Opcode Tag Class is other than UNIVERSAL. Such a message is discarded and does not undergo GTT using any of the default values.

The TCAP Opcode Based Routing feature supports the following messages.

• ITU TCAP Message/Package Types:
  • Begin
  • Continue
  • End
  • Abort
  • Unidirectional
• ANSI TCAP Message/Package Types:
  • Unidirectional
  • Query With Permission
  • Query Without Permission
  • Response
  • Conversation With Permission
  • Conversation Without Permission
  • Abort

Other message/package types are treated as an unknown message type and are not proceed with the decoding. This is not considered an error, because many non-TCAP SCCP messages are processed by the EAGLE. For these messages, the TCAP data is not used for routing. If an opcode translation set is encountered while performing global title translation, the opcode translation set is considered as a “translation not found” in that set. Such messages are routed based on last matched translation depending on its fallback option. Refer to Flexible Linkset Optional Based Routing for more details on the fallback option.

The application context name (ACN) is used for all supported ITU TCAP messages except Abort messages. No attempt to retrieve the ACN is made for Abort messages. All other supported messages may have a Dialog portion containing Dialogue Request / Unidirectional Dialogue / Dialogue Response PDU, from which the ACN is retrieved. If no Dialog portion is detected, then the ACN is assumed to be NONE. The TCAP Opcode Based Routing feature attempts to find the operation code (opcode) in all supported ITU TCAP messages except Abort. These messages must contain Invoke or Return Result (Last or Not Last) as the first component. If not, the opcode is assumed to be NONE.

At any point of time during the decoding process, if it is found that the current position in TCAP message is extending beyond the SCCP data portion length, the decoder process stops.

TCAP Opcode Based Routing GTT Sets

The TCAP Opcode Based Routing feature introduces the GTT Set Opcode with set type opcode. The opcode GTT set supports translations for ANSI and ITU opcodes.

TOBR Opcode Quantities

MAP Based Routing

These GTT settypes allow additional MAP Components to be used in the selection process. These GTT settypes are allowed to be provisioned ONLY in GTA entries from an OPCODE GTT Set type or one of the other GTT settypes supported by SS7 Firewall feature.

Additional opcodes supported by MAP Based Routing include:

• PurgeMS
• RestoreData
• Reset
• RegisterSS
• USSD-Request
• USSD-Notify
• SnedAuthenticationInfo
• CheckIMEI
• Provide Subscriber Location
• SubscriberLocationReport
• UpdateGPRSLocation

When an MSU is processed by the TOBR GTT translation with the OPTSN as one of MAP Based Routing settypes, the EAGLE decodes the TCAP part and extracts the required TCAP parameter from the MSU. The digits in this parameter are used as the key to search for the translation in the GTT set.

Only TCAP Package Types BEGIN, CONTINUE & END are supported for MAP Based Routing. OPTSN with one of the MAP Based Routing GTT settypes are allowed to be provisioned only for TOBR GTA entries that have PKGTYPE as BGN, or CNT or END.

For some MAP operations, it is possible for IMSI/MSISDN to be present in the Destination Reference of the dialogue portion; however, currently this feature only supports decoding the key from only the component portion of the TCAP part. If the required parameter is not present in the component portion, the parameter will be deemed 'not present' even though it is in the dialogue portion.

If the Dialogue Portion is present but the ACN could not be decoded, then the default version will be picked up from the defmapvr parameter for further processing. defmapvr is configured in opcode translation and used for opcodes that have MAP translations associated with it.

Figure 2-11 MAP Based Routing Flowchart

GTT Translations

TCAP Opcode Based Routing Feature Translations with an ANSI Opcode

The key for ANSI opcode translations is the ANSI opcode specifier, the ANSI TCAP Package Type, and the Family (part of ANSI TCAP opcode field). The ANSI opcode specifier values can be 0 to 255, None, and * (any opcode specifier value). The value none indicates the absence of the opcode in the incoming MSU. The ANSI TCAP Package Type values are Unidirectional, Query with Permission, Query without Permission, Response, Conversation with Permission, Conversation without Permission, Abort, and Any. The Family value can be 0 to 255, None, and * (any family value). While provisioning, when ANSI TCAP Package type is specified as Abort, then the ANSI opcode specifier and Family values must be none. Since the opcode specifier and family values exist together in the incoming MSU, both values in the translation must be none if either value is specified as none.

Search Order for the TCAP Opcode Based Routing Feature Translations with an ANSI Opcode

Table 2-15 shows the searching order for The TCAP Opcode Based Routing feature translations with an ANSI opcode. The ANSI opcode translations are matched to ANSI MSUs:

TCAP Opcode Based Routing Feature Translations with an ITU Opcode

The key for ITU opcode translations is the ITU opcode, the ITU TCAP Package Type, and the application context name (ACN). The ITU opcode values can be 0 to 255, None, and * (any opcode value). The value none indicates the absence of the opcode in the incoming MSU. The ITU TCAP Package Type values are Begin, End, Continue, Abort, Unidirectional, and Any. The ACN value can be 1 to 7 bytes - the value of each byte is from 0 to 255, none and Any. The none value indicates the absence of the ACN value in the incoming MSU. Though the VGTT feature is not supported for opcode GTT set, different digit length ACNs for the opcode GTT set can be provisioned. While provisioning, when ITU TCAP Package type is specified as Abort, then the ITU opcode and ACN values must be none. An ACN value cannot contain a mixture numbers, the value none, or the value Any. Table 2-16 shows the valid and invalid values for the ACN.

For the Operation Code Tag based routing, the key for ITU opcode translations is the ITU opcode, the ITU TCAP Package Type, the Application Context Name (ACN), and the OpCodeTag. The values in ITU OpCode Tag can be "local", "global", "any" and "none". The value "none" in the OpCode Tag indicates that the TOBR is not able to decode the OpCodeTag in the incoming MSU message.

Search Order for the TCAP Opcode Based Routing Feature Translations with an ITU Opcode

Table 2-17 shows the search order for the TCAP Opcode Based Routing feature translations with an ITU opcode when the TCAP Opcode Based Routing feature is enabled and turned on. The ITU opcode translations are only matched to ITU MSUs. If any MSU contains a 7-byte ACN value, an attempt is made to match the 7-byte ACN values with the values in the database. If a match is not found, no attempt is made to match any 6-/5-/4-/3-/2-/1-byte ACN values in the database. An attempt is made to match to any ACN=ANY entries in the database, if these entries are provisioned in the database.

For the Operation Code Tag based routing, TOBR matches the translation based on OpCodeTag with the OpCodeTag of the incoming MSU. Table 2-18 shows the search order for OpCodeTag Translation.

If no entry is found then TOBR searches the translation which matched the opcode with opcode of the incoming MSU as mentioned in Table 2-17.

TCAP Segmentation SMS Support Phase 2

An objective of the TCAP Opcode Based Routing feature is to allow EAGLE to route segmented TCAP SMS messages in the same manner as non-segmented TCAP messages are routed. This would mean routing all TCAP SMS messages within a particular transaction to the same place. Routing rules based on the opcode are used to route messages for special application handling. These rules work well for non-segmented TCAP messages. However they do not work well for segmented TCAP messages, because the initial BEGIN message does not contain an opcode. These messages must be identified for special routing based on other criteria. The TCAP Opcode Based Routing feature achieves this discrimination by allowing the EAGLE to route messages based on the TCAP Opcode and Dialogue portion information in the message. The EAGLE uses the Application Context Name from the Dialogue portion to route the TCAP Begin messages without the component portion (and without the operation code). The same routing rules to route messages with an ACN and opcode, an ACN only, or an opcode only value can be used. GSM SMS messages work particularly well in this solution, because there is a 1 to 1 correspondence between the ACN and opcode values.

Hardware Requirements

To enable the TCAP Opcode Based Routing feature E5-SM4G cards must be provisioned in the database. Any SMs must be replaced by the E5-SM4G cards.

Provisioning the TCAP Opcode Based Routing Feature

To provision the TCAP Opcode Based Routing feature, perform these steps.

1. Turn the GTT and EGTT features on using the chg-feat command. Add the required E5-SM4G cards to the database using the ent-card command. Perform the Adding a Service Module procedure.
2. Enable and turn on the TCAP Opcode Based Routing feature using the enable-ctrl-feat and the chg-ctrl-feat commands. Perform the Activating the TCAP Opcode Based Routing Feature procedure. To enable and turn on the TCAP Opcode Based Routing feature, the Flexible Linkset Optional Based Routing feature must be enabled and turned on. The status of the Flexible Linkset Optional Based Routing feature is verified when the Activating the TCAP Opcode Based Routing Feature procedure is performed.
3. Enable a TOBR Opcode Quantity using the enable-ctrl-feat command. Perform the Enabling a TOBR Opcode Quantity procedure.
4. Provision the required GTT sets using the ent-gttset command. Perform the Adding a GTT Set procedure.
5. Provision the required GTT translations using the ent-gta command. Perform the Adding Global Title Address Information procedure.
6. Provision the required GTT selectors using the ent-gttsel command. Perform the Adding a GTT Selector procedure.

The GTT Actions allows these actions to be applied to MSUs during global title translation message processing:

• Discard
• UDTS
• Duplicate
• TCAP error
• Forward
• Services
• SFLOG
• SFTHROT
• SCPVAL
• SFAPP

A GTT action entry contains one GTT action, a GTT action ID, data specific to the action, and a reference count. These actions are contained in a GTT action entry. The EAGLE contain a maximum of 2000 GTT action entries. A GTT action entry, identified by the GTT action ID, is assigned to a GTT action set. The GTT action set is assigned to the global title address entry. The reference count in the GTT action entry shows the number of database entities GTT action sets that reference the GTT action entry. When a GTT action entry is referenced by a GTT action set, a service selector ID, or a Forward GTT action entry, or an LNP service, the reference count is increased by 1. When a GTT action set, a service selector ID, or a Forward GTT action entry, or an LNP service no longer references the GTT action entry, the reference count is decreased by 1. The GTT action entry can be removed only when the reference count is zero. The data for each GTT action entry is shown in the rtrv-gttact output.

Discard GTT Action

An example of the Discard GTT action entry is shown in Figure 2-12.

Figure 2-12 Discard GTT Action Entry

UDTS GTT Action

An example of the UDTS GTT action entry is shown in Figure 2-13.

Figure 2-13 UDTS GTT Action Entry

TCAP Error GTT Action

An example of the TCAP Error GTT action entry is shown in Figure 2-14.

Figure 2-14 TCAP Error GTT Action Entry

Duplicate GTT Action

An example of the Duplicate GTT action entry is shown in Figure 2-15.

Figure 2-15 Duplicate GTT Action Entry

Forward GTT Action

The Forward GTT action diverts the translated MSU to another node. If the EAGLE fails to forward the MSU, UIM 1079 GTT Action FORWARD FAILED is generated.

An example of the Forwarded GTT action entry is shown in Figure 2-16.

Figure 2-16 Forward GTT Action Entry

Services GTT Action

GTT Action Services allow triggering a Service as a GTT action either based on the usual GTT rules or after FLOBR/TOBR execution.

An example of the Services GTT action entry is shown in Figure 2-17.

Figure 2-17 Services GTT Action Entry

Any of these three Services can be applied on the translated MSU -GPORT, GFLEX or SMSMR. The new GTT Actions Service cannot be applied on MTP routed MSUs.

GTT Action Services can work with the RTDB Split Feature (240M DN and 240M IMSIs via split database). This compatibility is possible only when GTT Action is executed on GTT enabled LIM cards.

If the Service is triggered by the GTT Action Service fails, the MSU can be processed by applying the results of the pre-Service GTT or processing with the specific Service error.

SFTHROT GTT Action

The SFTHROT GTT Action is used to control the throttling of MSUs on SCCP cards. Thirty-two (32) GTT actions of the type SFTHROT will be allowed. For each such GTT action, the user will provision a threshold as a maximum number of MSUs hitting the GTT action in a 30-second period.

When an MSU hits a GTT action of the type SFTHROT, the SCCP card updates the count of messages that hit the Throttling GTT action and periodically communicates the count to the OAM card via maintenance blocks. The OAM sums the total number of these messages on all SCCP cards, decides if the number of messages has crossed the provisioned threshold, and then communicates to the SCCP card to start throttling the messages.

The OAM will communicate to the SCCP card that the threshold for a particular Throttling GTT action has crossed. The SCCP card will then put that GTT action in the BLOCKED state for the remaining time of the current 30-second window. While the Throttling GTT Action is in the BLOCKED state, any MSU hitting that GTT action will be discarded.

A GTT Action set will only have a maximum of one SFTHROT GTT Action.

Figure 2-18 Throttling Framework

SFLOG GTT Action

The SFLOG GTT Action is used for logging. An SCCP card will be allowed to log up to 100 log event/second. The SCCP card will transfer all the log events for the MSUs that will hit the SFLOG GTT action. Two IPS cards will act as the Primary and Secondary Logging Card. At any given time, the Primary logging card will be actively logging. The standby logging card will only be used for logging if the active logging card is unavailable for logging for an extended period of time.

The SFTP Client interface will enable LOG events to be transferred from an EAGLE to other workstations. The file naming convention for the LOG SFTP reports is: <clli>_sflog_<date in yymmdd format>_<time in hh24mmss>.pcap. The EAGLE will provide an SFTP transfer of the LOG files after every 15 minutes. The EAGLE may also be configured to transfer LOG events periodically to a customer workstation. When the SFTP Client has been configured and the SFLOG GTT Action has been configured on some translation, the Logging Framework begins periodic transfers after collection completes for the next appropriate period.

The LOG event files to be transferred for that collection period are created and stored in IPS RAM Disk. The logging 15 minutes timer will start on both the SFLOG cards, Primary and Secondary (if configured), once the cards come into ACTIVE/IS-NR state. When the LOG event files have been generated, the Primary IPS logging card begins the file transfer to the Primary SFTP Server.

The IPS logging card does not know if an SFTP Server is up and running until it attempts a transfer. If a transfer fails, the transfer to the lowest priority number SFTP Server for the LOG file scheduled for that period is considered a failure, and the Logging system attempts to transfer the LOG file to the next higher priority number SFTP Server. It also raises a MINOR Alarm indicating the failure to transfer to the Primary SFTP Server.

If the IPS logging card is unable to establish a connection with any of the SFTP servers, a MAJOR Alarm is generated to record the file transfer failure event, and the LOG file scheduled for transfer is deleted from the file transfer repository. No further attempts are made to regenerate or transfer the file to the SFTP servers.

Release 46.3 implements the SFLOG MFC card service for the MFC interface. The SCCP uses this MFC service to send the log events to the IPS logging cards.

SCCP cards are the MFC client cards and IPS logging cards are MFC server cards for this MFC service. SCCP cards will only send the log event to the active IPS logging card (based on the broadcast message it gets from the active IPS logging card).

The log file format has the libpcap format already supported by EagleEyes.

A GTT Action set will only have a maximum of one SFLOG GTT Action.

SCPVAL GTT Action

Figure 2-19 MAP SCCP Validation Flowchart

SFAPP GTT Action

The SFAPP GTT action diverts the translated MSU to the SFAPP card.

Figure 2-20 Forward SFAPP GTT Action Entry

The user is able to provision SFAPP card information in the SFAPP GTT Action entry through SCFADDR. HLRADDR is used later on the SFAPP card.

The SFAPP GTT Action is controlled by the "GTT Action - SFAPP" parameter.

Figure 2-21 SFAPP Action Processing

GTT Action Set

A GTT action set contains from one to six GTT action entries, the GTT action set ID which is used by global title address entries to reference the GTT action set, a test mode field whose value can be either on or off, and a reference count. The EAGLE can contain 20,000 GTT action sets.

A GTT action set is assigned to a global title address entry. The reference count in the GTT action set shows the number of global title address entries that reference the GTT action set. When a GTT action set is referenced by an global title address entry, the reference count is increased by 1. When a global title address entry no longer references the GTT action set, the reference count is decreased by 1. The GTT action set can be removed only when the reference count is zero. When the GTT action set is removed, the reference counts of GTT action entries that are in the GTT action set are decreased by 1.The data for each GTT action set is shown in the rtrv-gttaset output.

The default value for the test mode field, if neither the on=testmode or off=testmode parameters are specified, is off.

GTA Entries and the Discard/UDTS/TCAP Error GTT Action

In previous releases, only the Discard and UDTS GTT actions could be assigned to a GTA entry, but the GTA entry could contain no routing data (the point code, SSN, routing indicator, MRN set and MAP set values). With the GTT Actions feature, the GTA entry that references the GTT action set that contains the Discard, UDTS, or TCAP Error GTT actions can contain routing data, although the routing data is not used during message processing. This allows the user to change the GTT action set that is being referenced by the GTA entry to a GTT action set that requires routing data, a GTT action set that contains either the Duplicate or Forward GTT actions, without having to provision the routing data for the GTA entry.

GTA Entries with the XLAT=NONE Parameter

In previous releases, the Discard and UDTS GTT actions were specified for the GTA entry with the xlat=disc and the xlat=udts parameters of the ent-gta or chg-gta commands. The GTT Actions feature allows a GTA entry to be provisioned with the xlat=none parameter. The GTA entry that contains the xlat=none parameter can contain any data except the routing data (the point code, SSN, and routing indicator). That means, it is possible to specify any GTT Action Set, CGGTMOD, GTMOD Id, Per Path Measurements Required, New Translation Type and Cancel GT for the GTT Translations with xlat=none. In addition, xlat=none translations support provisioning of a MAPSET as well as an MRNSET. At any point of time, in a given GTT set, two GTA entries with same GTA value and different XLAT values are not allowed.

GTT Action Per-TT Measurements

GTT action-related events recorded by the SCCP application are reported as system-wide totals, on a per-translation type basis (per-TT), and a per-path basis. The events recorded for GTT Actions are shown in Table 2-20 and Table 2-21.

The per-translation type report contains a breakdown of the GTT action events for each of the translation types provisioned in the database, up to a maximum of 256 translation types. This data is available for every 30-minute interval, and for every 15-minute interval if the 15-Minute Measurements feature is enabled and turned on. The GTT Actions system-wide measurements report provides the totals of all the actions that were performed on the EAGLE for all the GTT action sets. This report is available for every 30-minute interval, and for every 15-minute interval if the 15-Minute Measurements feature is enabled and turned on.

GTT Action Per-Path Measurements

The GTT action per-path measurements provides measurement counts for the GTT actions applied to the messages that match a pre defined combination of “CgPA GTA”, “CdPA GTA”, and “Opcode” values. The combination of these values are provisioned in the GTT Path table with the ent-gttapath command. Each entry in the GTT Path table must be unique combination of CdPA GTA, CgPA GTA and Opcode values and this combination is called a path. If a translation search in Global Title Translation table matches the path specified in GTT Path table, then the corresponding measurement counts for that path are incremented. However, if the ppmeasreqd parameter (Per Path Measurements required) value for the final translation is no, then the per-path measurement counts for the matching path are not pegged.

An example of a GTT action path entry is shown in Figure 2-24.

Figure 2-24 GTT Action Path Entry

The GTT Action path table can contain a maximum of 10,000 entries. A GTT path entry shall have up to three GTT set-value combinations in it, where the GTT set and value must be a valid entry in the GTT Translation table. However, a GTT path must be provisioned with at least one GTT set and value (CdPA GTA/CgPA GTA/Opcode). For every GTT action path, the GTT set and the value must be specified together as a combination. If the GTT Set-value combination is not provisioned in a GTT action path then it is considered as no value and is displayed as “----“ in the rtrv-gttapath output for that combination. Translation entries cannot be removed or modified (in case of GTA range splitting) if the entries are referenced in a GTT action path. Figure 2-25 shows the relation between the two tables.

Figure 2-25 GTT Translation and GTT Action Path Table Relationship

The GTT actions per-path measurements report contains the GTT Action events for the predefined GTT paths that are provisioned in the database, up to a maximum of 10,000 predefined paths. The per-path measurement data is collected during the 60 minute interval period (per hour). The hourly data is retained for 24 hours. The daily collection data is retained for seven days. The data collection reports are available as both scheduled and on-demand reports. The events recorded for the GTT actions per-path measurements is shown in Table 2-21.

GTT Action Path Entry Searched with all the GTT Set-Value Combinations Specified

All three specified GTT Set-value combinations (opcode/CgPA/CdPA) are provisioned in a GTT action path in GTT action path table as shown in Figure 2-26.

Figure 2-26 Example GTT Action Path Table Entry

Figure 2-27 GTT Translation Lookup - Exact GTT Action Path Match

This combination matches the entry # 1 in the GTT action path table shown in Figure 2-26. Since the per-path measurement required value is set to Yes in Set 7 (the translation result), entry #1 in Figure 2-26 is pegged in the per-path measurements report. If the per-path measurement required value is set to No in Set 7, then entry #1 in Figure 2-26 is not pegged in the per-path measurements report.

GTT Action Path Entry Not Searched in the Translation Lookup

If a GTT set-value combinations search is performed during the translation lookup, and all the searched combinations do not match any of the provisioned GTT action paths, then the per-path measurements are not pegged.

Figure 2-28 GTT Translation Lookup - No GTT Action Path Match

In Figure 2-28, a search is performed for this translation data during the global title translation lookup. CDPA GTA and CgPA GTA searches were not performed.

The entries in Figure 2-26 do not contain any entries that have only an Opcode entry, so the per-path measurements are not pegged.

GTT Path Entry Searched with Some GTT Set-Value Combinations Specified

Figure 2-29 GTT Translation Lookup - Exact GTT Action Path Match (with Unspecified GTT Set-Value Combinations)

In Figure 2-29, searches are performed for this translation data during the global title translation lookup. CDPA GTA search was not performed

The searched CGPA GTA/CdPA GTA/OPCODE values matches Entry #3 in Figure 2-26 where the CDPA GTA is provisioned as none. Since the per-path measurement required value is set to Yes in Set 6 (the translation result), entry #3 in Figure 2-26 is pegged in the per-path measurements report.

Provisioning the GTT Actions Feature

To provision the GTT Actions feature, perform these steps.

1. Turn the GTT and EGTT features on using the chg-feat command. Add the required service modules to the database using the ent-card command. Perform the Adding a Service Module procedure.
2. Enable and turn on one or more of these features using the enable-ctrl-feat and the chg-ctrl-feat commands.
   • To perform the GTT actions Discard, UDTS, or TCAP Error - GTT Action – DISCARD – 893027501
   • To perform the GTT action Duplicate - GTT Action – DUPLICATE – 893027601
   • To perform the GTT action Forward - GTT Action – FORWARD – 893037501

   Perform the Activating the GTT Actions Features procedure to enable and turn on these features.

3. Provision the required GTT actions using the ent-gttact command by performing the Adding a GTT Action procedure.
4. Provision the required GTT action sets using the ent-gttaset command by performing the Adding a GTT Action Set procedure.
5. Provision the required GTT translations using the ent-gta command. Perform Adding Global Title Address Information.

To provision the GTT action paths, perform these steps.

1. Perform the Activating the GTT Actions Features procedure to enable and turn on these features.
   • To perform the GTT actions Discard, UDTS, or TCAP Error - GTT Action – DISCARD – 893027501
   • To perform the GTT action Duplicate - GTT Action – DUPLICATE – 893027601
   • To perform the GTT action Forward - GTT Action – FORWARD – 893037501
2. Provision the required GTT sets using the ent-gttset command. Perform Adding a GTT Set.
3. Provision the required GTT translations using the ent-gta command. Perform Adding Global Title Address Information.
4. Provision the required GTT action paths using the ent-gttapath command by performing the Adding a GTT Action Path Entry procedure.

The CAT2 SS7 security functionality is achived using the CAT2 Utility. This utility is external to EAGLE and can be downloaded from the Oracle Software Delivery Cloud along with the other EAGLE components.

The CAT2 Utility is used for reading and recording the information present in GSMA IR.21 document into database tables. The SCPVAL GTT Action addresses the SS7 CAT2 security checks. This GTT action ensures that the MSU details such as, CgPA and IMSI belongs to same operator after validating it with the newly generated table.

CAT2 SS7 Security Workflow

The following flow chart provides an overview of the CAT2 SS7 Security functionality:

Figure 2-30 CAT2 SS7 Security Workflow

The CAT2 SS7 Security functionality is described as follows:

• The IR.21 XML file is parsed on a linux machine using the external CAT2 Utility. The utility extracts the information required from the IR.21 file for validation of the message and convert the data in tabular format to be used in EAGLE.IR.21 input file in XML format and generate error message in case of no or other than IR.21 XML files.
• The output is generated in CAT2IMSI and CAT2GTA tables and the network card supporting SCCP functionality gets updated along with table data.
  The following data is extracted from IR.21 file and stored on EAGLE:

  • Sender TADIG code (RAEX IR.21 Information) : It is retrieved from the RAEX IR.21 FileHeader tag and used to identify the operator. It consist of two fields, with a total length of five characters consisting of three-character country code and a two character operator or company idenfier. Sender TADIG code is stored against each entry in both the tables.
  • Routing Information Data (Section ID 4) : It is a mandatory section in IR.21 document of the operator. The EAGLE CAT2IMSI table stores the MCC-MNC (E.212) along with TADIG code from this section. The EAGLE CAT2GTA stores the CC-NC (from E.214) along with TADIG code from this section.
  • Network Element Information Data (Section ID 13) – It is an optional section in IR.21 document of the operator. The EAGLE CAT2GTA table stores the HLR Node type GT address or Address range along with the TADIG code from this section.
• The SCPVAL GTT action validates that the MSU details: CgPA and IMSI belongs to same operator. The validation is based on the following two rules:
  • The IMSI within MAP layer of a message must match with the IMSI prefixes (MCC + MNC) of the protected network.
  • The OperatorID (TADIG code) referenced by all parameters in the MAP layer of the message (IMSI and HLR) must match with the OperatorID referenced by the matching IR.21 nodal GT ranges.

    The MSUs that passes these rules are considered as free from CAT2 anomalies.

  All the supported Category 2 Opcodes are screened with these rules. If the first rule passes, then only MSU validates for the second rule. Otherwise, the SCPVAL GTT Action is considered as failure.

In previous releases, MTP routed SCCP messages are routed to the service module if either the MTP Msgs for SCCP Apps feature, part number 893017401, is enabled and turned on, or the MSU is screened by the Gateway Screening stop action SCCP. These actions were performed on the service modules

1. EPAP service handling is performed.
2. If the EPAP service handling resulted in Fall through to MTP routing, then MTP Routed GSM MAP Screening is performed, if applicable.
3. The MSU is MTP routed if the message is not discarded by MTP Routed GSM MAP Screening.

In addition to the actions that were performed in previous releases, global title translation and GTT Actions are performed on MTP routed MSUs similar to the existing global title translation GTT handling for GT routed MSU’s. Global title translation on MTP routed MSUs is performed if the service handling results in Fall through to GTT or if the GTT required option in the service selector is set to on for the service relayed MSU.

In previous EAGLE releases that did not support the Unique GTT Selectors feature, all ITU GTT selectors shared the same space in the GTT selector table. Only one entry for an ITU GTT selector that contains a specific GTI and translation type value, regardless of the network type or domain of the ITU GTT selector, could be defined in the GTT selector table. For example, if the GTT selector table contained an ITU-I GTT selector with the GTI value 2 and the translation type value 5, this GTI and translation type value combination could not be assigned to an ITU-N or ITU-N24 GTT selector.

When the EAGLE is upgraded from a release that did not support the Unique GTT Selectors feature to a release that does support the Unique GTT Selectors feature, the ITU GTT selectors created in the previous release become overlapped GTT selectors.

In a release that does support the Unique GTT Selectors feature, the user is able to add more GTT Selectors for the existing overlapped GTT Selector as long as the GTIx (ITU domain only) and TT combination matches the existing overlapped GTT Selector.

The user will not be able to add a new non-overlapped GTT selector entry if the GTIx (ITU domain only) and TT combination matches to an existing overlapped GTT Selector entry created during upgrade to a release that supports the Unique GTT Selectors feature from a release that did not support it. The unqgttsel parameter in the SCCPOPTS table controls run-time behavior of the Unique GTT Selector feature; when it is set to "exactmatch," overlapped entries will behave as non-overlapped entry.

Any new entries added in a release that supports the Unique GTT Selectors feature, with the GTIx and TT combination that were not present in the system while upgrading to a release that supports the Unique GTT Selectors feature, will be added as non-overlapped entries.

The provisioning of ITU-I spare and ITU-N spare GTT selectors is the same as provisioning ITU-I and ITU-N GTT selectors. This includes the provisioning of default GTT selectors using the ent-tt command. For more information about using the ent-tt command to provision default GTT selectors, see the Adding a Translation Type procedure.

GTT Selectors with the GTI Value of 0

With the Unique GTT Selectors feature, The EAGLE can process MSUs whose GTI value is 0 (a GTI=0 GTT selector) for all network types, including ITU-I spare and ITU-N spare. A GTI=0 GTT selector cannot contain tt, np, nai, and Eagle-Gen values. A GTI=0 GTT selector can contain lsn (the name of a linkset), selid, and cgssn values. The values that can be specified for a GTI=0 GTT selector is determined by the features that are enabled and turned on.

GTT Selector Key for GTI=0 GTT Selectors

Table 2-22 defines the keys in the GTT selector table based on the feature combination for GTI=0 GTT selectors. If a feature supports specific parameters and that feature is not enabled or turned on, then default values are entered into the database for those parameters.

Searching Order for GTI=0 GTT Selectors

Table 2-23 and Table 2-24 shows the searching order for CdPA and CgPA GTI=0 GTT Selectors.

For the Origin-Based SCCP Routing feature GTT hierarchy, meaningful means following the Origin-Based SCCP Routing feature rules; the GTT set type of a CdPA GTT set must be CDGTA and the GTT set type of a CgPA GTT set must be either CGGTA or CGPC. If a Flexible Linkset Optional Based Routing feature GTT hierarchy is being used, then any GTT set type can be used.

The Linkset ID, SELID, and CGSSN parameters are controlled by the Flexible Linkset Optional Based Routing and Origin-Based SCCP Routing features. If a parameter is not allowed, it assumes the value of Any in the database. In Table 2-23 and Table 2-24, if a parameter is specified as Exact and that parameter is not allowed, then the Exact value is the same as the Any value.

Using the Unique GTT Selectors Feature

The unqgttsel parameter value can be changed at any time. Non-overlapped GTT selectors can be provisioned regardless of the unqgttsel parameter value. When there are no overlapped GTT selectors in the database and only non-overlapped GTT selectors are in the database, the exactmatch value of the unqgttsel parameter is applied to the GTIx=2 and GTIx=4 GTT selectors. The system default value of the unqgttsel parameter is bestmatch.

The conversion is performed on a service module card if the message was generated by the EAGLE, or on a LIM receiving the message if the message is MTP-routed. The conversion takes place just before the message is sent to the LIM that will be transmitting the message out of the EAGLE.

An SCCP Class 1 message that requires SCCP processing is processed by a service module card and then sent back to the receiving LIM to maintain sequencing. Message routing and the XUDT(S) UDT(S) conversion is performed on the receiving LIM in this case.

The Enhanced Global Title Translation (EGTT) feature provides enhancements to existing global title translation functions and automatically updates the database when the EGTT feature is turned on. Turning on the EGTT feature overrides the Global Title Translation (GTT) feature. This section provides a high-level summary of feature enhancements, the upgrade process, and upgrade considerations for the GTT and EGTT features.

The signaling connection control part (SCCP) is divided into two functions:

• SCCP Routing Control
• SCCP Management

Figure 2-31 shows the relationship of these two functions.

Figure 2-31 Logical View of SCCP Subsystems

SCCP Routing Control

SCCP routing control receives messages from other nodes in the network via the MTP-Transfer indication.

A load balancing function assigns each LIM to a service module to distribute the SCCP traffic among the available service modules. When a LIM receives an SCCP message that is destined for the EAGLE, it sends the message to the service module assigned to that LIM. If that LIM does not have a service module assigned to it, the LIM discards the SCCP message. If no service modules are equipped or available, the SCCP message is discarded and the LIM transmits a User Part Unavailable MSU to the sending node.

When a LIM receives an SCCP message that is destined for another node, the LIM performs MTP routing and the SCCP message is not sent to the service module. Figure 2-32 shows the message flow for an SCCP message destined for the EAGLE and for an SCCP message destined for another node.

Figure 2-32 SCCP Message Flow through the EAGLE

When SCCP receives a message from MTP, it checks the routing indicator in the called party address. There are two types of routing shown by the called party address routing indicator.

1. Subsystem (ssn) – This indicates the message is destined for a subsystem at this node. For the EAGLE, the only valid local subsystem is SCCP management (ssn = 1). If the LNP feature is enabled, the EAGLE contains an LNP subsystem which can be numbered from 2 to 255. The LNP subsystem number can be configured with the "Adding a Subsystem Application" procedure in Administration and LNP Feature Activation Guide for ELAP.
2. Global Title (gt) – This indicates that global title translation is required. The EAGLE performs the translation, determines the new DPC for the message, and routes the message to that DPC.

Interaction with the Global Title Translation (GTT) Feature

The SCCP routing function control uses two tables to perform global title translation: the translation type table and the global title translation table. Figure 2-33 shows how these tables are organized.

Figure 2-33 Example of Using Translation Type and Global Title Translation Tables

The translation type table is used by SCCP to determine which global title translation table to access. This allows translation tables to be customized to the type of translations that need to be performed, (for example, 6 digit, 800, etc.). The translation block is accessed by using the translation type in the called party address and the network type of the MSU (ANSI or ITU) as an index within the table. Each entry points to the start of a global title translation table.

The translation type table is configured by the ent-tt command. For more information on the ent-tt command, refer to the Commands Manual.

Each translation type entry in the translation type table contains these fields:

• name of translation type (optional) (8 bytes)
• number of digits (1 byte)
• alias translation type (2 bytes)
• pointer to translation table (4 bytes)
• network type (1 byte)

The global title translation table is used by SCCP to map a global title address to an SS7 network address so that the SCCP message can be routed to its destination. The global title translation table is configured by the ent-gtt or chg-gtt commands. For more information on the ent-gtt or chg-gtt commands, refer to Commands User's Guide.

Each global title translation entry in the global title translation table contains these fields:

• Global title address low value (up to 21 digits) (11 bytes)
• Global title address high value (up to 21 digits) (11 bytes)
• Destination point code (may be an ANSI, ITU national, or ITU international point code) (4 bytes)
• Field that contains either a subsystem number (for route on SSN translation results only) (1 byte) or a new translation type (for new GT translation result only) (1 byte)
• Translation result consisting of one of these conditions (1 byte):
  • Translate on the DPC only, route on GT (subsequent global title translation required)
  • Translate on the DPC only, route on SSN
  • Translate on the DPC and SSN, route on GT (subsequent global title translation required)
  • Translate on the DPC and SSN, route on SSN
  • Translate on new GT (subsequent global title translation required)

The translation result determines what data in the message is replaced. The DPC in the routing label is always replaced after the SCCP message is translated. If a point code exists in the called party address, it is also replaced. The subsystem number or the translation type in the called party address can be replaced, but neither have to be replaced. The routing indicator in the called party address can be set to “route on SSN,” or can remain set to “route on GT.” Table 2-30 shows which fields in the MSU are modified for each translation result.

Table 2-30 MSU Fields Modified by Global Title Translation

Translation Result	Routing Label DPC Replaced	CDPA SSN Replaced	CDPA Routing Indicator Replaced	CDPA Translation Type Replaced	CDPA PC Replaced (if it already exists)
Translate on DPC only, route on GT	yes	no	no – remains set to route on GT	Can be replaced (See note)	yes
Translate on DPC only, route on SSN	yes	no	yes – set to route on SSN	no	yes
Translate on DPC and SSN, route on GT	yes	yes	no – remains set to route on GT	no	yes
Translate on DPC and SSN, route on SSN	yes	yes	yes – set to route on SSN	no	yes
Translate on new GT	yes	no	no – remains set to route on GT	yes	yes
Note: The CDPA translation type can be replaced when translating on the DPC only and routing on GT only if the ANSI/ITU SCCP Conversion feature is enabled. If the ANSI/ITU-China SCCP Conversion feature is not enabled when translating on the DPC only and routing

Interaction with the Enhanced Global Title Translation (EGTT) Feature

The SCCP routing function control uses three tables to perform global title translation: the GTT Selector table, the GTT Set table, and the global title address (GTA) table. The SCCP use the GTT Set table together with the GTT Selector table to determine which GTA table to access. This allows translation tables to be customized with the type of translations that need to be performed.

Figure 2-34 Example of Using GTT Selector, GTT Set, and GTA Tables

The GTT Set table is configured by the ent-gttset command; the GTT Selector table is configured by the ent-gttsel. For more information on this command, refer to Commands User's Guide.

Each GTT Set table contains these fields:

• GTT Set name
• Network domain name
• Number of digits

Each GTT Selector table contains these fields:

• GTT Set name
• The global title indicator (GTI). The GTI defines the domain as
  • gti and gtia (ANSI) with GTI=2
  • gtii (ITU international) with GTI=2 or GTI=4, and
  • gtin (ITU national) with GTI=2 or GTI=4.
    The global title indicator is made up of the:

    • name of the global title translation type (TT); and the
    • numbering plan (NP) or numbering plan value (NPV) if GTI=4; and the
    • nature of address indicator (NAI) or nature of address indicator value (NAIV) if GTI=4.

      Note:

      Both the numbering plan and nature of address indicator parameters can be specified by supplying either a mnemonic or an explicit value. At no time may both the mnemonic and the explicit value be specified at the same time for the same parameter.

The GTA table is used by the SCCP to map a global title address to an SS7 network address so that the SCCP message can be routed to its destination. The GTA table is configured by the ent-gta or chg-gta commands. For more information on the ent-gta or chg-gta commands, refer to Commands User's Guide.

Each global title address entry in the GTA table contains these fields:

• GTT Set name
• Start of the global title address (up to 21 digits)
• End of the global title address (up to 21 digits)
• Destination point code (may be an ANSI, ITU national, or ITU international point code)
• Translated subsystem number
• Translate indicator
• Cancel Called Global Title indicator
• Routing indicator (translation results)
  • Translate on the DPC only, route on GT (subsequent global title translation required)
  • Translate on the DPC only, route on SSN
  • Translate on the DPC and SSN, route on GT (subsequent global title translation required)
  • Translate on the DPC and SSN, route on SSN
  • Translate on new GT (subsequent global title translation required)

The translation result determines what data in the message is replaced. The DPC in the routing label is always replaced after the SCCP message is translated. If a point code exists in the called party address, it is also replaced. The subsystem number or the translation type in the called party address can be replaced, but neither have to be replaced. The routing indicator in the called party address can be set to “route on SSN” or can remain set to “route on GT.” Table 2-31 shows which fields in the MSU are modified for each translation result.

Table 2-31 MSU Fields Modified by Enhanced Global Title Translation

Translation Result	Routing Label DPC Replaced	CDPA SSN Modified	CDPA Routing Indicator Replaced	CDPA Translation Type Replaced	CDPA PC Replaced (if it already exists)	GT Deleted
Translate on DPC only, route on GT	yes	no	no – remains set to route on GT	Can be replaced (See note)	yes	no
Translate on DPC only, route on SSN	yes	no	yes – set to route on SSN	no	yes	yes
Translate on DPC and SSN, route on GT	yes	yes	no – remains set to route on GT	no	yes	no
Translate on DPC and SSN, route on SSN	yes	yes	yes – set to route on SSN	no	yes	yes
Translate on new GT	yes	no	no – remains set to route on GT	yes	yes	no
Note: The CDPA translation type can be replaced when translating on the DPC only and routing on GT only if the ANSI/ITU SCCP Conversion feature is enabled. If the ANSI/ITU SCCP Conversion feature is not enabled when translating on the DPC only and routing on GT, the CDPA translation type cannot be replaced.

Translation Type Mapping

Certain SCCP messages contain a called party address parameter that contains a translation type field. The translation type field indicates the type of global title processing the EAGLE must perform. The values used within any particular network may be different than the standardized values that are defined for internetwork applications.

The translation type mapping feature maps standardized internetwork translation type values to intranetwork translation type values used within any particular network. This feature also maps intranetwork translation type values to standardized internetwork translation type values.

The only SCCP messages that are affected by translation type mapping are UDT and XUDT messages, received or transmitted, whose global title indicator is 0010 (ANSI/ITU) or 0100 (ITU). The translation type will be modified for these messages regardless of whether the destination point code in the MTP routing label is an EAGLE point code and regardless of the SCCP CdPA routing indicator value. Other messages that contain the called party address parameter are not affected. For example, UDTS messages are assumed to be MTP routed and need not be examined. XUDTS messages are either MTP routed or use one translation type value indicating global title to point code translation and should not be mapped.

Translation type mapping is performed on each LIM in the linkset. Incoming translation type mapping is performed on linksets bringing messages into the EAGLE, and is performed before the global title translation function, the gateway screening function. Outgoing translation type mapping is performed on linksets carrying messages out of the EAGLE to other destinations, and is performed after the global title translation function, the gateway screening function.

When outgoing translation type mapping is configured and the MSU must be re-routed due to a changeback or signaling link failure, the re-routed MSU could be double mapped. This is a limitation since re-screening or re-translating (with possible incorrect results) can occur by performing the global title translation and gateway screening functions on the mapped MSU. Figure 2-36 shows an example of a translation type that is double mapped.

Figure 2-36 An Example of Double Translation Type Mapping

In Figure 2-36, MSUs on the outgoing linkset LS1 containing the existing translation type (ETT) 251 are mapped to translation type 127 (MTT). MSUs on the outgoing linkset LS2 containing the existing translation type 127 are mapped to translation type 96. Linkset LS1 fails and the traffic is re-routed on linkset LS2. Any outgoing traffic that was on linkset LS1 containing the translation type 251 has been changed to translation type 127. When this traffic is re-routed on linkset LS2, the translation type of the messages that was changed to 127 remains 127 and is not changed back to 251. When the messages are sent over linkset LS2, the existing translation type 127 is changed to translation type 96. This is an example of double mapping a translation type. In this example, the messages leaving network 1 on linkset LS1 were mapped to translation type 127, an “800” translation type. Because of double mapping, that translation type was changed to 96, a “LIDB” translation type. These messages can be routed to the wrong subsystem database; or if gateway screening is configured to screen for these messages, these messages could be discarded before they leave network 1, and network 2 would never receive them.

To help prevent this from happening, configure the incoming traffic on the linkset to map the mapped translation type of the outgoing traffic on that linkset (MTT) to the existing translation type for outgoing traffic on that linkset (ETT). In this example, for incoming traffic on linksets LS1 and LS2, map the existing translation type 127 (the mapped translation type for outgoing traffic on these linksets) to the mapped translation type 251 (the existing translation type for outgoing traffic on these linksets). When linkset LS1 fails, the incoming messages on linkset LS2 containing translation type 127, including those that were mapped to 127 on linkset LS1 and are now being rerouted, are now mapped to translation type 251. When these messages become outgoing messages on linkset LS2, those messages containing translation type 251 are mapped to translation type 127 instead of 96. These messages can then continue to be routed to the proper subsystem database. If gateway screening is configured to screen for and discard messages with translation type 96, the rerouted messages are not effected by the results of the translation type mapping.

If the database transport access feature is being used, and the MSU encapsulated by the gateway screening redirect function contains a translation type that must be mapped on an incoming basis, the encapsulated MSU contains the mapped translation type. The translation type of the new MSU is obtained from the gateway screening redirect table.

The EAGLE supports 64 translation type mappings for each linkset. This includes both incoming and outgoing translation type mappings. EAGLE supports translation type mapping entries for 255 linksets. The maximum number of translation type mappings that can be configured in the EAGLE is 16,320.

The translation type mapping information is configured in the database using the ent-ttmap, chg-ttmap, dlt-ttmap, and rtrv-ttmap commands.

The following procedures describe the steps needed to add, remove, or change global title translation (GTT) data in the database.

The items configured in this section are:

• Service modules
• Translation type mapping
• Concerned signaling point codes
• Mated applications
• Mated relay nodes.
• GT conversion table entries for the ANSI/ITU SCCP Conversion feature
• Loopsets for the SCCP Loop Detection feature.
• GT modification identifiers for the Advanced GT Modification feature.

To configure the global title translation feature, translation types and global title translations must also be configured. The procedures to configure translation types and global title translations are located in the Global Title Translation (GTT) Configuration section.

The procedures shown in this chapter use a variety of commands. If more information on these commands is needed, refer to Commands User's Guide to find the required information.

There must be SS7 routes to the nodes referenced by the global title translation entities in the database. Perform one of the Adding a Route procedures in Database Administration – SS7 User's Guide to configure these routes.

The following is a brief description of the global title translation entities. These global title translation entities must be configured in the order that they are shown.

1. The GTT feature must be turned on with the chg-feat:gtt=on command. Verify this with the rtrv-feat command.

   Note:

   Once the Global Title Translation (GTT) feature is enabled with the chg-feat command, it cannot be disabled.

   The GTT feature must be purchased before enabling this feature. If you are not sure whether you have purchased the GTT feature, contact your Oracle Sales Representative or Account Representative.

2. A service module must be configured in the database with the ent-card command. A service module can be one of these cards: DSM (E5-SM4G/E5-SM8G-B), or SLIC. The DSM card is specified with the type=dsm and appl=vsccp parameters of the ent-card command. The SLIC card is specified with type=dsm (in the odd numbered card slots) or type=slic (in the even numbered card slots), and appl=vsccp parameters of the ent-card command. Refer to the Adding a Service Module procedure for the required cards. The card configuration can be verified with the rtrv-card command.
3. A translation type must be defined in the database. Verify this with the rtrv-tt command. If the necessary translation types are not in the database, add them with the ent-tt command. The translation type is used by the ent-gtt command and defines the length of the global title address.

   If the Variable-length Global Title Translation (VGTT) feature is being used, it must be enabled with the chg-feat:vgtt=on command. Verify this with the rtrv-feat command. Refer to the Variable-length Global Title Translation Feature section for more information on this feature.

   Note:

   Once the Variable-length Global Title Translation (VGTT) feature is enabled with the chg-feat command, it cannot be disabled.

   The VGTT feature must be purchased before enabling this feature. If you are not sure whether you have purchased the VGTT feature, contact your Oracle Sales Representative or Account Representative.

4. The translation type can be mapped to another translation type. This is a function of the translation type mapping feature. The translation type mapping feature maps standardized internetwork translation type values to intranetwork translation type values used within any particular network. This feature also maps intranetwork translation type values to standardized internetwork translation type values. Enter the rtrv-ttmap command to verify that the necessary translation type mapping information is in the database. Enter the necessary translation type mapping information in the database using the ent-ttmap command.
5. The concerned signaling point code broadcast groups must be defined in the database. These groups define the point codes that receive subsystem allowed and subsystem prohibited status messages about a particular global title translation node. These messages are broadcast from SCCP management. Verify that these groups are in the database with the rtrv-cspc command. If these groups are not in the database, add them with the ent-cspc command.
6. The mated applications must be defined in the database. The mated applications are the point codes and subsystem numbers of the service databases along with parameters describing the routing between replicated pairs of service databases. Verify the mated application information in the database with the rtrv-map command. If the necessary mated application information is not in the database, add the necessary information with the ent-map command.

   If the XMAP Table Expansion feature is to be used to increase the number of mated application entries in the mated application table to either 2000 or 3000 entries, the XMAP Table Expansion feature must be enabled with the enable-ctrl-feat command. Verify the status of the XMAP Table Expansion feature with the rtrv-ctrl-feat command.

   The mated applications provide load sharing of the traffic between replicated pairs of service databases. The Flexible GTT Load Sharing feature provides more flexible load sharing capabilities for final global title translations (global title translation containing the routing indicator value SSN) than the mated applications can provide without the Flexible GTT Load Sharing feature enabled. With this feature enabled, MAP sets are provisioned. These MAP sets are assigned to global title translations. Refer to Flexible Final GTT Load Sharing for more information on using the Flexible GTT Load Sharing feature with mated applications.

   Load sharing based on the transaction parameters of the message can be performed if the Transaction-Based GTT Load Sharing feature is enabled and turned on. Refer to the Transaction-Based GTT Load Sharing section for more information on using the Transaction-Based GTT Load Sharing feature.

   Load sharing based on the weight assigned to an individual entities in a load sharing MAP group can be performed if the Weighted GTT Load Sharing feature is enabled and turned on. Refer to the Weighted GTT Load Sharing section for more information on using the Weighted GTT Load Sharing feature.

7. The mated relay node groups can be defined in the database if the Intermediate GTT Load Sharing feature is to be used. Verify this with the rtrv-mrn command. If the necessary global title translation information is not in the database, add it with the ent-mrn command.

   The Intermediate GTT Load Sharing (IGTTLS) feature must be enabled with the enable-ctrl-feat and chg-ctrl-feat commands. Verify this with the rtrv-ctrl-feat command. Refer to the Intermediate GTT Load Sharing Feature section for more information on this feature.

   The Flexible GTT Load Sharing feature provides more flexible load sharing capabilities for intermediate global title translations (global title translation containing the routing indicator value GT) than the Intermediate GTT Load Sharing feature can provide. With this feature enabled, MRN sets are provisioned. These MRN sets are assigned to global title translations. Refer to Flexible Intermediate GTT Load Sharing for more information on using the Flexible GTT Load Sharing feature with mated relay node groups.

   Load sharing based on the transaction parameters of the message can be performed if the Transaction-Based GTT Load Sharing feature is enabled and turned on. Refer to the Transaction-Based GTT Load Sharing section for more information on using the Transaction-Based GTT Load Sharing feature.

   Load sharing based on the weight assigned to an individual entities in a load sharing MRN group can be performed if the Weighted GTT Load Sharing feature is enabled and turned on. See the Weighted GTT Load Sharing section for more information on using the Weighted GTT Load Sharing feature.

8. The global title translation data must be defined in the database. This data is used to determine the destination of the service database that needs to queried for additional routing information. Verify this with the rtrv-gtt command. If the necessary global title translation information is not in the database, add it with the ent-gtt command.
   If the Advanced GT Modification feature is being used, it must be enabled with the enable-ctrl-feat command. Verify this with the rtrv-ctrl-feat command. Refer to the Advanced GT Modification Feature section for more information on this feature.

   Note:

   Once the Advanced GT Modification feature is enabled, it cannot be disabled.

   If the XGTT Table Expansion feature is to be used to increase the number of mated application entries in the mated application table to either 400,000 or 1,000,000 entries, the XGTT Table Expansion feature must be enabled with the enable-ctrl-feat command. Verify the status of the XGTT Table Expansion feature with the rtrv-ctrl-feat command.

   The ANSI/ITU SCCP Conversion feature provides a means to perform SCCP conversion between ANSI MSUs and ITU MSUs. To perform this conversion, the ANSI/ITU SCCP Conversion feature must be enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. Verify the status of the ANSI/ITU SCCP Conversion feature with the rtrv-ctrl-feat command. Entries must be also configured in the GT conversion table with the ent-gtcnv command. The content of the GT conversion table can be verified with the rtrv-gtcnv command.

   Decimal digits (0-9) or hexadecimal digits (0-9, a-f, A-F) can be specified for these items that are assigned to the global title translation entry.

   • The global title address (gta and egta) values
   • Entries in the GT conversion table
   • The prefix (npds) and suffix (nsds) values in the GTMOD identifier that is assigned to the global title translation entry.

   Hexadecimal digits can be specified only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature with the rtrv-ctrl-feat command. Refer to the Hex Digit Support for GTT section for more information on this feature.

   The SCCP Loop Detection feature provides a method for detecting SCCP looping. With this feature enabled, loopsets are provisioned. These loopsets are assigned to Global Title Translations. See the SCCP Loop Detection section for more information on using the SCCP Loop Detection feature with Global Title Translations.

The procedures to configure these items are located in the Enhanced Global Title Translation (EGTT) Configuration section.

The translation type (ent-/dlt-/rtrv-tt) and the GTT (ent-/dlt-/chg-/rtrv-gtt) commands can be executed when the EGTT feature is turned on, but will only produce CDGTA GTT sets and CDGTA GTT selectors.

The following is a brief description of the enhanced global title translation entities. These entities must be configured in the order that they are shown.

1. The Enhanced Global Title Translation (EGTT) feature must be turned on with the chg-feat:egtt=on command. The Global Title Translation (GTT) must be on before the EGTT feature can be turned on. Verify this with the rtrv-feat command.

   Note:

   Once the Enhanced Global Title Translation (EGTT) feature is turned on with the chg-feat command, it cannot be turned off.

   The EGTT feature must be purchased before turning on the feature. If you are not sure whether you have purchased the EGTT feature, contact your Sales Representative or Account Representative.

2. A service module must be configured in the database with the ent-card command. A service module can be either a DSM or SLIC card. The DSM card is specified with the type=dsm and appl=vsccp parameters of the ent-card command. The SLIC card is specified with type=dsm (in the odd numbered card slots) or type=slic (in the even numbered card slots), and appl=vsccp parameters of the ent-card command.. Refer to the Adding a Service Module procedure for the required cards. The card configuration can be verified with the rtrv-card command.
3. A global title translation (GTT) set must be defined in the database. Verify this with the rtrv-gttset command. If the necessary GTT set is not in the database, add it with the ent-gttset command.

   If the Variable-length Global Title Translation (VGTT) feature is being used, it must be turned on with the chg-feat:vgtt=on command. Verify this with the rtrv-feat command. Refer to the Variable-length Global Title Translation Feature section for more information on this feature.

   Note:

   Once the Variable-length Global Title Translation (VGTT) feature is turned on with the chg-feat command, it cannot be turned off.

   The VGTT feature must be purchased before turning it on. If you are not sure whether you have purchased the VGTT feature, contact your Oracle Sales Representative or Account Representative.

4. A translation type must be defined in the database. Verify this with the rtrv-gttsel command. If the necessary translation types are not in the database, add them with the ent-gttsel command. The translation type is used by the ent-gta command and defines the length of the global title address.
5. The translation type can be mapped to another translation type. This is a function of the translation type mapping feature. The translation type mapping feature maps standardized internetwork translation type values to intranetwork translation type values used within any particular network. This feature also maps intranetwork translation type values to standardized internetwork translation type values. Enter the rtrv-ttmap command to verify that the necessary translation type mapping information is in the database. Enter the necessary translation type mapping information in the database using the ent-ttmap command.
6. The concerned signaling point code broadcast groups must be defined in the database. These groups define the point codes that receive subsystem allowed and subsystem prohibited status messages about a particular global title translation node. These messages are broadcast from SCCP management. Verify that these groups are in the database with the rtrv-cspc command. If these groups are not in the database, add them with the ent-cspc command.
7. The mated applications must be defined in the database. The mated applications are the point codes and subsystem numbers of the service databases along with parameters describing the routing between replicated pairs of service databases. Verify the mated application information in the database with the rtrv-map command. If the necessary mated application information is not in the database, add the necessary information with the ent-map command.

   If the XMAP Table Expansion feature is to be used to increase the number of mated application entries in the mated application table to either 2000 or 3000 entries, the XMAP Table Expansion feature must be enabled with the enable-ctrl-feat command. Verify the status of the XMAP Table Expansion feature with the rtrv-ctrl-feat command.

   The mated applications provide load sharing of the traffic between replicated pairs of service databases. The Flexible GTT Load Sharing feature provides more flexible load sharing capabilities for final global title translations (global title translation containing the routing indicator value SSN) than the mated applications can provide without the Flexible GTT Load Sharing feature enabled. With this feature enabled, MAP sets are provisioned. These MAP sets are assigned to global title translations. Refer to Flexible Final GTT Load Sharing for more information on using the Flexible GTT Load Sharing feature with mated applications.

   Load sharing based on the transaction parameters of the message can be performed if the Transaction-Based GTT Load Sharing feature is enabled and turned on. Refer to the Transaction-Based GTT Load Sharing section for more information on using the Transaction-Based GTT Load Sharing feature.

8. The mated relay node groups can be defined in the database if the Intermediate GTT Load Sharing feature is to be used. Verify this with the rtrv-mrn command. If the necessary global title translation information is not in the database, add it with the ent-mrn command.

   The Intermediate GTT Load Sharing (IGTTLS) feature must be enabled with the enable-ctrl-feat and chg-ctrl-feat commands. Verify this with the rtrv-ctrl-feat command. Refer to the Intermediate GTT Load Sharing Feature section for more information on this feature.

   The Flexible GTT Load Sharing feature provides more flexible load sharing capabilities for intermediate global title translations (global title translation containing the routing indicator value GT) than the Intermediate GTT Load Sharing feature can provide. With this feature enabled, MRN sets are provisioned. These MRN sets are assigned to global title translations. Refer to Flexible Intermediate GTT Load Sharing for more information on using the Flexible GTT Load Sharing feature with mated relay node groups.

   Load sharing based on the transaction parameters of the message can be performed if the Transaction-Based GTT Load Sharing feature is enabled and turned on. Refer to the Transaction-Based GTT Load Sharing section for more information on using the Transaction-Based GTT Load Sharing feature.

   Load sharing based on the weight assigned to an individual entities in a load sharing MRN group can be performed if the Weighted GTT Load Sharing feature is enabled and turned on. Refer to the Weighted GTT Load Sharing section for more information on using the Weighted GTT Load Sharing feature.

9. The global title address data must be defined in the database. This data is used to determine the destination of the service database that needs to be queried for additional routing information. Verify this with the rtrv-gta command. If the necessary global title address information is not in the database, add it with the ent-gta command.
   If the Advanced GT Modification feature is being used, it must be enabled with the enable-ctrl-feat command. Verify this with the rtrv-ctrl-feat command. Refer to the Advanced GT Modification Feature section for more information on this feature.

   Note:

   Once the Advanced GT Modification feature is enabled, it cannot be disabled.

   The XGTT Table Expansion feature is used to increase the number of entries in the GTT table to either 400,000 or 1,000,000 entries, the XGTT Table Expansion feature must be enabled with the enable-ctrl-feat command. Verify the status of the XGTT Table Expansion feature with the rtrv-ctrl-feat command.

   The ANSI/ITU SCCP Conversion feature provides a means to perform SCCP conversion between ANSI MSUs and ITU MSUs. To perform this conversion, the ANSI/ITU SCCP Conversion feature must be enabled with the enable-ctrl-feat command, and turned on with the chg-ctrl-feat command. Verify the status of the ANSI/ITU SCCP Conversion feature with the rtrv-ctrl-feat command. Entries must be also configured in the GT conversion table with the ent-gtcnv command. The content of the GT conversion table can be verified with the rtrv-gtcnv command.

   Decimal digits (0-9) or hexadecimal digits (0-9, a-f, A-F) can be specified for these items that are assigned to the global title address entry.

   • The global title address (gta and egta) values
   • Entries in the GT conversion table
   • The prefix (npds) and suffix (nsds) values in the GTMOD identifier that is assigned to the global title address entry.

   Hexadecimal digits can be specified only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature with the rtrv-ctrl-feat command. Refer to the Hex Digit Support for GTT section for more information on this feature.

   The SCCP Loop Detection feature provides a method for detecting SCCP looping. With this feature enabled, loopsets are provisioned. These loopsets are assigned to Global Title Translations. Refer to the SCCP Loop Detection section for more information on using the SCCP Loop Detection feature with Global Title Translations.

10. A set of these actions, discard, UDTS, duplicate, TCAP error, forward, and services (SRVC) for GPORT, GFLEX and SMSMR can be assigned to the global title address entry. These actions are contained in a GTT action set. A GTT action set name identifies each set of these actions and this name is assigned to the global title address entry. The actions in the action set are performed on the MSU when global title translation finishes processing the MSU. Refer to the GTT Actions section for more information on using GTT actions with the global title address entries.
11. The GTT Action per-path measurements provides measurement counts for the GTT actions that are applied to messages that match a pre-defined combination of CgPA GTA, CdPA GTA, and Opcode values, called a path. The combination of these values are provisioned in the GTT Path table. Refer to the GTT Actions section for more information on using GTT Action per-path measurements.

1. Display the cards in the EAGLE using the rtrv-card command to verify that the card location for the new service module is not provisioned. This is an example of the possible output.

   Note:

   Cards should be distributed throughout the EAGLE for proper power distribution. Refer to Installation Guide for the shelf power distribution.

   This is an example of the possible output:

   tklc1110501 15-06-24 16:59:18 EST  EAGLE5 46.2.0-65.53.1
   CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC  DATA
   1101   DCM       IPLIM    stpb058a    A    0   stpb058a    B    6
                             stpb058a    A1   1   stpb058a    B1   7
                             stpd078a    A2   0   stpd078a    B2   6
                             stpd078a    A3   1   stpd078a    B3   7
   1102   TSM       GLS
   1103   DCM       IPLIM    stpb058a    A    8   stpd078a    B    8
                             stpb058a    A1   9   stpd078a    B1   9
                             stpb058a    A2   10  stpd078a    B2   10
                             stpb058a    A3   11  stpd078a    B3   11
   1104   TSM       GLS
   1105   DCM       SS7IPGW  sc1b059a    A    0
   1106   DCM       SS7IPGW  sc1b059a    A    1
   1107   DSM       VSCCP                                               ELAP
   1111   MCPM      MCP
   1112   MCPM      MCP
   1113   E5-MCAP   OAM
   1114   TDM-A
   1115   E5-MCAP   OAM
   1116   TDM-B
   1117   MDAL
   1201   LIMATM    ATMANSI  ls1201a00   A    0   ls1201a04   B    0
   1204   LIMT1     SS7ANSI  ls1204a00   A    0   ls1204a01   A1   0
                             ls1204a02   A2   0   ls1204a00   A4   1
                             ls1204a01   A5   1   ls1204a02   A6   1
   1205   LIME1     CCS7ITU  ls1205i00   A    0   ls1205i04   B    0
                             ls1205i01   A1   0   ls1205i05   B1   0
                             ls1205i02   A2   0   ls1205i06   B2   0
                             ls1205i03   A3   0   ls1205i07   B3   0
                             ls1205i08   A4   0   ls1205i12   B4   0
                             ls1205i09   A5   0   ls1205i13   B5   0
                             ls1205i10   A6   0   ls1205i14   B6   0
                             ls1205i11   A7   0   ls1205i15   B7   0
                             ls1205i04   A8   1   ls1205i00   B8   1
                             ls1205i05   A9   1   ls1205i01   B9   1
                             ls1205i06   A10  1   ls1205i02   B10  1
                             ls1205i07   A11  1   ls1205i03   B11  1
                             ls1205i12   A12  1   ls1205i08   B12  1
                             ls1205i13   A13  1   ls1205i09   B13  1
                             ls1205i10   B14  1   ls1205i11   B15  1
   1206   LIME1     CCS7ITU  ls1206n00   A    0   ls1206n04   B    0
                             ls1206n01   A1   0   ls1206n05   B1   0
                             ls1206n02   A2   0   ls1206n06   B2   0
                             ls1206n03   A3   0   ls1206n07   B3   0
                             ls1206n08   A4   0   ls1206n12   B4   0
                             ls1206n09   A5   0   ls1206n13   B5   0
                             ls1206n10   A6   0   ls1206n14   B6   0
                             ls1206n11   A7   0   ls1206n15   B7   0
                             ls1206n12   A8   1   ls1206n00   B8   1
                             ls1206n13   A9   1   ls1206n01   B9   1
                             ls1206n14   A10  1   ls1206n02   B10  1
                             ls1206n15   A11  1   ls1206n03   B11  1
                             ls1206n04   A12  1   ls1206n08   B12  1
                             ls1206n05   A13  1   ls1206n09   B13  1
                             ls1206n10   B14  1   ls1206n11   B15  1
   1207   LIME1     CCS7ITU  ls1207i00   A    0   ls1207i04   B    0
                             ls1207i00   A1   1   ls1207i04   B1   1
                             ls1207i02   A2   0   ls1207i06   B2   0
                             ls1207i02   A3   1   ls1207i06   B3   1
                             ls1207i08   A4   0   ls1207i12   B4   0
                             ls1207i08   A5   1   ls1207i12   B5   1
                             ls1207i10   A6   0   ls1207i14   B6   0
                             ls1207i10   A7   1   ls1207i14   B7   1
                             ls1207i00   A8   2   ls1207i04   B8   2
                             ls1207i00   A9   3   ls1207i04   B9   3
                             ls1207i02   A10  2   ls1207i06   B10  2
                             ls1207i02   A11  3   ls1207i06   B11  3
                             ls1207i08   A12  2   ls1207i12   B12  2
                             ls1207i08   A13  3   ls1207i12   B13  3
                             ls1207i10   A14  2   ls1207i14   B14  2
                             ls1207i10   A15  3   ls1207i14   B15  3
   1208   LIMT1     SS7ANSI  ls1208a00   A    0   ls1208a04   B    0
                             ls1208a01   A1   0   ls1208a05   B1   0
                             ls1208a02   A2   0   ls1208a06   B2   0
                             ls1208a03   A3   0   ls1208a07   B3   0
                             ls1208a08   A4   0   ls1208a09   A5   0
                             ls1208a10   A6   0   ls1208a11   A7   0
                             ls1208a04   A8   1   ls1208a00   B8   1
                             ls1208a05   A9   1   ls1208a01   B9   1
                             ls1208a06   A10  1   ls1208a02   B10  1
                             ls1208a07   A11  1   ls1208a03   B11  1
                             ls1208a08   B12  1   ls1208a09   B13  1
                             ls1208a10   B14  1   ls1208a11   B15  1
   1212   LIME1     CCS7ITU  lsstpb100i  A    0   lsstpb101i  B    0
                             lsstpb100i  A1   1   lsstpb101i  B1   1
                             lsstpb100i  A2   2   lsstpb101i  B2   2
                             lsstpb100i  A3   3   lsstpb101i  B3   3
                             lsstpb100i  A4   4   lsstpb101i  B4   4
                             lsstpb100i  A5   5   lsstpb101i  B5   5
                             lsstpb100i  A6   6   lsstpb101i  B6   6
                             lsstpb100i  A7   7   lsstpb101i  B7   7
                             lsstpb102i  A8   0   lsstpb103i  B8   0
                             lsstpb102i  A9   1   lsstpb103i  B9   1
                             lsstpb102i  A10  2   lsstpb103i  B10  2
                             lsstpb102i  A11  3   lsstpb103i  B11  3
                             lsstpb102i  A12  4   lsstpb103i  B12  4
                             lsstpb102i  A13  5   lsstpb103i  B13  5
                             lsstpb102i  A14  6   lsstpb103i  B14  6
                             lsstpb102i  A15  7   lsstpb103i  B15  7
                             lsstpb104i  A16  0   lsstpb106i  B16  0
                             lsstpb104i  A17  1   lsstpb106i  B17  1
                             lsstpb104i  A18  2   lsstpb106i  B18  2
                             lsstpb104i  A19  3   lsstpb106i  B19  3
                             lsstpb104i  A20  4   lsstpb106i  B20  4
                             lsstpb104i  A21  5   lsstpb106i  B21  5
                             lsstpb104i  A22  6   lsstpb106i  B22  6
                             lsstpb104i  A23  7   lsstpb106i  B23  7
                             lsstpb105i  A24  0   lsstpb107i  B24  0
                             lsstpb105i  A25  1   lsstpb107i  B25  1
                             lsstpb105i  A26  2   lsstpb107i  B26  2
                             lsstpb105i  A27  3   lsstpb107i  B27  3
                             lsstpb105i  A28  4   lsstpb107i  B28  4
                             lsstpb105i  A29  5   lsstpb107i  B29  5
                             lsstpb105i  A30  6   lsstpb107i  B30  6
                             lsstpb105i  A31  7   lsstpb107i  B31  7
   1214   LIMT1     SS7ANSI  lsstpb108a  A    1   lsstpb108a  B    2
   1215   LIME1     CCS7ITU  ls1215c00   A    0   ls1215c04   B    0
                             ls1215c01   A1   0   ls1215c05   B1   0
                             ls1215c02   A2   0   ls1215c06   B2   0
                             ls1215c03   A3   0   ls1215c07   B3   0
                             ls1215c08   A4   0   ls1215c09   A5   0
                             ls1215c10   A6   0   ls1215c11   A7   0
                             ls1215c04   A8   1   ls1215c00   B8   1
                             ls1215c05   A9   1   ls1215c01   B9   1
                             ls1215c06   A10  1   ls1215c02   B10  1
                             ls1215c07   A11  1   ls1215c03   B11  1
                             ls1215c08   B12  1   ls1215c09   B13  1
                             ls1215c10   B14  1   ls1215c11   B15  1
   1216   LIME1     CCS7ITU  ls1216i00   A    0   ls1216i04   B    0
                             ls1216i00   A1   1   ls1216i04   B1   1
                             ls1216i00   A2   2   ls1216i04   B2   2
                             ls1216i00   A3   3   ls1216i04   B3   3
                             ls1216i00   A4   4   ls1216i04   B4   4
                             ls1216i00   A5   5   ls1216i04   B5   5
                             ls1216i00   A6   6   ls1216i04   B6   6
                             ls1216i00   A7   7   ls1216i04   B7   7
                             ls1216i00   A8   8   ls1216i04   B8   8
                             ls1216i00   A9   9   ls1216i04   B9   9
                             ls1216i00   A10  10  ls1216i04   B10  10
                             ls1216i00   A11  11  ls1216i04   B11  11
                             ls1216i00   A12  12  ls1216i04   B12  12
                             ls1216i00   A13  13  ls1216i04   B13  13
                             ls1216i00   A14  14  ls1216i04   B14  14
                             ls1216i00   A15  15  ls1216i04   B15  15
   1217   IPSM      IPS
   1218   LIME1     CCS7ITU  ls1218c00   A    0   ls1218c01   A1   0
                             ls1218c02   A2   0   ls1218c03   A3   0
                             ls1218c00   A4   1   ls1218c01   A5   1
                             ls1218c02   A6   1   ls1218c03   A7   1
   1301   LIMT1     SS7ANSI  ls1301a01   A    0   ls1301a01   B    1
                             ls1301a02   A1   0   ls1301a02   B1   1
                             ls1301a03   A2   0   ls1301a03   B2   1
                             ls1301a04   A3   0   ls1301a04   B3   1
                             ls1301a05   A4   0   ls1301a05   B4   1
                             ls1301a06   A5   0   ls1301a06   B5   1
                             ls1301a07   A6   0   ls1301a07   B6   1
                             ls1302a01   A7   0   ls1302a01   B7   1
                             ls1302a02   A8   0   ls1302a02   B8   1
                             ls1302a03   A9   0   ls1302a03   B9   1
                             ls1302a04   A10  0   ls1302a04   B10  1
                             ls1302a05   A11  0   ls1302a05   B11  1
                             ls1302a06   A12  0   ls1302a06   B12  1
                             ls1303a01   A13  0   ls1303a01   B13  1
                             ls1303a02   A14  0   ls1303a02   B14  1
                             ls1301a27   A15  0   ls1301a27   B15  1
   1302   LIMT1     SS7ANSI  ls1301a00   A    0   ls1303a00   B    0
                             ls1301a00   A1   1   ls1303a00   B1   1
                             ls1301a00   A2   2   ls1303a00   B2   2
                             ls1301a00   A3   3   ls1303a00   B3   3
                             ls1301a00   A4   4   ls1303a00   B4   4
                             ls1301a00   A5   5   ls1303a00   B5   5
                             ls1301a00   A6   6   ls1303a00   B6   6
                             ls1301a00   A7   7   ls1303a00   B7   7
                             ls1301a00   A8   8   ls1303a00   B8   8
                             ls1301a00   A9   9   ls1303a00   B9   9
                             ls1301a00   A10  10  ls1303a00   B10  10
                             ls1301a00   A11  11  ls1303a00   B11  11
                             ls1301a00   A12  12  ls1303a00   B12  12
                             ls1301a00   A13  13  ls1303a00   B13  13
                             ls1301a00   A14  14  ls1303a00   B14  14
                             ls1301a00   A15  15  ls1303a00   B15  15
   1313   LIME1ATM  ATMITU   ls1313i00   A    0   ls1313i04   B    0
                             ls1313i01   A1   0
   1314   LIMT1     SS7ANSI  ls1314a02   A    0   ls2214a02   B    0
                             ls1314a02   A1   1   ls2214a02   B1   1
                             ls1314a03   A2   0   ls2214a03   B2   0
                             ls1314a03   A3   1   ls2214a03   B3   1
                             ls1314a04   A4   0   ls2214a04   B4   0
                             ls1314a04   A5   1   ls2214a04   B5   1
                             ls1314a05   A6   0   ls2214a05   B6   0
                             ls1314a05   A7   1   ls2214a05   B7   1
                             ls1314a06   A8   0   ls2214a06   B8   0
                             ls1314a06   A9   1   ls2214a06   B9   1
                             ls1314a07   A10  0   ls5213a07   B10  0
                             ls1314a07   A11  1   ls5213a07   B11  1
                             ls2114a00   A12  0   ls5313a00   B12  0
                             ls2114a00   A13  1   ls5313a00   B13  1
                             ls2114a01   A14  0   ls5313a01   B14  0
                             ls2114a01   A15  1   ls5313a01   B15  1
   1315   DCM       SS7IPGW  ls1315a00   A    0
   1316   DCM       SS7IPGW  ls1315a00   A    1
   1317   DSM       VSCCP                                               ELAP
   2112   LIMT1     SS7ANSI  ls2112a00   A    0   ls2112a04   B    0
                             ls2112a00   A1   1   ls2112a04   B1   1
                             ls2112a00   A2   2   ls2112a04   B2   2
                             ls2112a00   A3   3   ls2112a04   B3   3
                             ls2112a00   A4   4   ls2112a04   B4   4
                             ls2112a00   A5   5   ls2112a04   B5   5
                             ls2112a00   A6   6   ls2112a04   B6   6
                             ls2112a00   A7   7   ls2112a04   B7   7
                             ls2112a00   A8   8   ls2112a04   B8   8
                             ls2112a00   A9   9   ls2112a04   B9   9
                             ls2112a00   A10  10  ls2112a04   B10  10
                             ls2112a00   A11  11  ls2112a04   B11  11
                             ls2112a00   A12  12  ls2112a04   B12  12
                             ls2112a00   A13  13  ls2112a04   B13  13
                             ls2112a00   A14  14  ls2112a04   B14  14
                             ls2112a00   A15  15  ls2112a04   B15  15
   2113   LIME1ATM  ATMITU   ls1313i00   A    1   ls1313i04   B    1
                             ls1313i01   A1   1
   2114   LIMT1     SS7ANSI
   2115   DCM       SS7IPGW  ls1315a00   A    2
   2116   DCM       SS7IPGW  ls1315a00   A    3
   2117   DCM       SS7IPGW  ls1315a00   A    4
   2118   DCM       SS7IPGW  ls1315a00   A    5
   2201   LIMATM    ATMANSI  ls2201a00   A    0   ls2201a04   B    0
                             ls2201a01   A1   0
   2202   LIMATM    ATMANSI  ls2202a00   A    0   ls2202a04   B    0
                             ls2202a01   A1   0
   2208   LIME1ATM  ATMITU   ls2208i00   A    0   ls2208n04   B    0
   2211   DSM       VSCCP                                               GTT
   2213   LIME1ATM  ATMITU   ls2213i00   A    0   ls2213i04   B    0
                             ls2213i01   A1   0
   2216   LIMT1     SS7ANSI  ls2216a00   A    0   ls2216a04   B    0
                             ls2216a00   A1   1   ls2216a04   B1   1
                             ls2216a00   A2   2   ls2216a04   B2   2
                             ls2216a00   A3   3   ls2216a04   B3   3
                             ls2216a00   A4   4   ls2216a04   B4   4
                             ls2216a00   A5   5   ls2216a04   B5   5
                             ls2216a00   A6   6   ls2216a04   B6   6
                             ls2216a00   A7   7   ls2216a04   B7   7
                             ls2216a00   A8   8   ls2216a04   B8   8
                             ls2216a00   A9   9   ls2216a04   B9   9
                             ls2216a00   A10  10  ls2216a04   B10  10
                             ls2216a00   A11  11  ls2216a04   B11  11
                             ls2216a00   A12  12  ls2216a04   B12  12
                             ls2216a00   A13  13  ls2216a04   B13  13
                             ls2216a00   A14  14  ls2216a04   B14  14
                             ls2216a00   A15  15  ls2216a04   B15  15
   2217   DSM       VSCCP                                               ELAP
   2301   LIMATM    ATMANSI  ls2201a00   A    1   ls2201a04   B    1
                             ls2201a01   A1   1
   2302   LIMATM    ATMANSI  ls2202a00   A    1   ls2202a04   B    1
                             ls2202a01   A1   1
   2305   DSM       VSCCP                                               IMSI
   2308   LIMATM    ATMANSI  ls1201a00   A    1   ls1201a04   B    1
   2311   DSM       VSCCP                                               IMSI
   2313   LIME1ATM  ATMITU   ls2213i00   A    1   ls2213i04   B    1
                             ls2213i01   A1   1
   2317   DSM       VSCCP                                               ELAP
   3101   DCM       SS7IPGW  sc1d079a    A    0
   3102   IPSM      IPS
   3103   DSM       VSCCP                                               ELAP
   3108   LIME1ATM  ATMITU   ls3108i00   A    0   ls2208i00   B    1
                             ls3108n01   A1   0
   3111   DSM       VSCCP                                               DN
   3113   LIME1ATM  ATMITU   ls3108i00   A    1   ls3113n04   B    0
                             ls3113n01   A1   0
   3114   STC       EROUTE
   3116   STC       EROUTE
   3117   DCM       SS7IPGW  ls1315a00   A    6
   3118   DCM       SS7IPGW  ls1315a00   A    7
   3201   DSM       VSCCP                                               ELAP
   3203   DSM       VSCCP                                               ELAP
   3205   DSM       VSCCP                                               ELAP
   3207   DSM       VSCCP                                               ELAP
   3211   ENET      IPSG     ls3211a00   A    0
   3212   ENET      IPSG     ls3211a00   A    1
   3213   ENET      IPSG     ls3211a00   A    2
   3214   ENET      IPSG     ls3211a00   A    3
   3215   ENET      IPSG     ls3211a00   A    4
   3216   ENET      IPSG     ls3211a00   A    5
   3217   DSM       VSCCP                                               ELAP
   3301   DCM       SS7IPGW  ls3301a00   A    0
   3302   DCM       SS7IPGW  ls3301a00   A    1
   3303   DCM       SS7IPGW  ls3301a00   A    2
   3304   DCM       SS7IPGW  ls3301a00   A    3
   3305   DCM       SS7IPGW  ls3301a00   A    4
   3306   DCM       SS7IPGW  ls3301a00   A    5
   3307   DCM       SS7IPGW  ls3301a00   A    6
   3308   DCM       SS7IPGW  ls3301a00   A    7
   3311   DCM       SS7IPGW  ls3311a00   A    0
   3312   DCM       SS7IPGW  ls3311a00   A    1
   3313   DCM       SS7IPGW  ls3311a00   A    2
   3314   DCM       SS7IPGW  ls3311a00   A    3
   3315   DCM       SS7IPGW  ls3311a00   A    4
   3316   DCM       SS7IPGW  ls3311a00   A    5
   3317   DCM       SS7IPGW  ls3311a00   A    6
   3318   DCM       SS7IPGW  ls3311a00   A    7
   4107   DSM       VSCCP                                               IMSI
   4111   DSM       VSCCP                                               GTT
   4113   LIMT1     SS7ANSI  ls4113a00   A    0   ls4113a04   B    0
                             ls4113a00   A1   1   ls4113a04   B1   1
                             ls4113a00   A2   2   ls4113a04   B2   2
                             ls4113a00   A3   3   ls4113a04   B3   3
                             ls4113a00   A4   4   ls4113a04   B4   4
                             ls4113a00   A5   5   ls4113a04   B5   5
                             ls4113a00   A6   6   ls4113a04   B6   6
                             ls4113a00   A7   7   ls4113a04   B7   7
                             ls4113a00   A8   8   ls4113a04   B8   8
                             ls4113a00   A9   9   ls4113a04   B9   9
                             ls4113a00   A10  10  ls4113a04   B10  10
                             ls4113a00   A11  11  ls4113a04   B11  11
                             ls4113a00   A12  12  ls4113a04   B12  12
                             ls4113a00   A13  13  ls4113a04   B13  13
                             ls4113a00   A14  14  ls4113a04   B14  14
                             ls4113a00   A15  15  ls4113a04   B15  15
   4115   DCM       SS7IPGW  ls4115a00   A    0
   4116   DCM       SS7IPGW  ls4115a00   A    1
   4117   DCM       SS7IPGW  ls4115a00   A    2
   4118   DCM       SS7IPGW  ls4115a00   A    3
   4207   DSM       VSCCP                                               DN
   4212   LIME1     CCS7ITU  ls4212n00   A    0   ls4212n04   B    0
                             ls4212n00   A1   1   ls4212n04   B1   1
                             ls4212n02   A2   0   ls4212n06   B2   0
                             ls4212n02   A3   1   ls4212n06   B3   1
                             ls4212n08   A4   0   ls4212n12   B4   0
                             ls4212n08   A5   1   ls4212n12   B5   1
                             ls4212n10   A6   0   ls4212n14   B6   0
                             ls4212n10   A7   1   ls4212n14   B7   1
                             ls4212n00   A8   2   ls4212n04   B8   2
                             ls4212n00   A9   3   ls4212n04   B9   3
                             ls4212n02   A10  2   ls4212n06   B10  2
                             ls4212n02   A11  3   ls4212n06   B11  3
                             ls4212n08   A12  2   ls4212n12   B12  2
                             ls4212n08   A13  3   ls4212n12   B13  3
                             ls4212n10   A14  2   ls4212n14   B14  2
                             ls4212n10   A15  3   ls4212n14   B15  3
   4213   LIMT1     SS7ANSI  ls4213a00   A    0   ls4213a04   B    0
                             ls4213a00   A1   1   ls4213a04   B1   1
                             ls4213a02   A2   0   ls4213a06   B2   0
                             ls4213a02   A3   1   ls4213a06   B3   1
                             ls4213a08   A4   0   ls4213a12   B4   0
                             ls4213a08   A5   1   ls4213a12   B5   1
                             ls4213a10   A6   0   ls4213a14   B6   0
                             ls4213a10   A7   1   ls4213a14   B7   1
                             ls4213a00   A8   2   ls4213a04   B8   2
                             ls4213a00   A9   3   ls4213a04   B9   3
                             ls4213a02   A10  2   ls4213a06   B10  2
                             ls4213a02   A11  3   ls4213a06   B11  3
                             ls4213a08   A12  2   ls4213a12   B12  2
                             ls4213a08   A13  3   ls4213a12   B13  3
                             ls4213a10   A14  2   ls4213a14   B14  2
                             ls4213a10   A15  3   ls4213a14   B15  3
   4217   DCM       SS7IPGW  ls4115a00   A    4
   4218   DCM       SS7IPGW  ls4115a00   A    5
   4311   DSM       VSCCP                                               DN
   4313   LIMT1     SS7ANSI  ls4313a00   A    0   ls4313a04   B    0
                             ls4313a00   A1   1   ls4313a04   B1   1
                             ls4313a02   A2   0   ls4313a06   B2   0
                             ls4313a02   A3   1   ls4313a06   B3   1
                             ls4313a08   A4   0   ls4313a12   B4   0
                             ls4313a08   A5   1   ls4313a12   B5   1
                             ls4313a10   A6   0   ls4313a14   B6   0
                             ls4313a10   A7   1   ls4313a14   B7   1
                             ls4313a00   A8   2   ls4313a04   B8   2
                             ls4313a00   A9   3   ls4313a04   B9   3
                             ls4313a02   A10  2   ls4313a06   B10  2
                             ls4313a02   A11  3   ls4313a06   B11  3
                             ls4313a08   A12  2   ls4313a12   B12  2
                             ls4313a08   A13  3   ls4313a12   B13  3
                             ls4313a10   A14  2   ls4313a14   B14  2
                             ls4313a10   A15  3   ls4313a14   B15  3
   4317   DCM       SS7IPGW  ls4115a00   A    6
   4318   DCM       SS7IPGW  ls4115a00   A    7
   5101   LIME1     CCS7ITU  ls5101i00   A    0   ls5101i04   B    0
                             ls5101i00   A1   1   ls5101i04   B1   1
                             ls5101i00   A2   2   ls5101i04   B2   2
                             ls5101i00   A3   3   ls5101i04   B3   3
                             ls5101i00   A4   4   ls5101i04   B4   4
                             ls5101i00   A5   5   ls5101i04   B5   5
                             ls5101i00   A6   6   ls5101i04   B6   6
                             ls5101i00   A7   7   ls5101i04   B7   7
                             ls5101i00   A8   8   ls5101i04   B8   8
                             ls5101i00   A9   9   ls5101i04   B9   9
                             ls5101i00   A10  10  ls5101i04   B10  10
                             ls5101i00   A11  11  ls5101i04   B11  11
                             ls5101i00   A12  12  ls5101i04   B12  12
                             ls5101i00   A13  13  ls5101i04   B13  13
                             ls5101i00   A14  14  ls5101i04   B14  14
                             ls5101i00   A15  15  ls5101i04   B15  15
   5102   LIME1     CCS7ITU  ls5102i00   A    0   ls5102i04   B    0
                             ls5102i00   A1   1   ls5102i04   B1   1
                             ls5102i02   A2   0   ls5102i06   B2   0
                             ls5102i02   A3   1   ls5102i06   B3   1
                             ls5102i08   A4   0   ls5102i12   B4   0
                             ls5102i08   A5   1   ls5102i12   B5   1
                             ls5102i10   A6   0   ls5102i14   B6   0
                             ls5102i10   A7   1   ls5102i14   B7   1
                             ls5102i00   A8   2   ls5102i04   B8   2
                             ls5102i00   A9   3   ls5102i04   B9   3
                             ls5102i02   A10  2   ls5102i06   B10  2
                             ls5102i02   A11  3   ls5102i06   B11  3
                             ls5102i08   A12  2   ls5102i12   B12  2
                             ls5102i08   A13  3   ls5102i12   B13  3
                             ls5102i10   A14  2   ls5102i14   B14  2
                             ls5102i10   A15  3   ls5102i14   B15  3
   5103   LIME1     CCS7ITU  ls5103i00   A    0   ls5103i04   B    0
                             ls5103i00   A1   1   ls5103i04   B1   1
                             ls5103i02   A2   0   ls5103i06   B2   0
                             ls5103i02   A3   1   ls5103i06   B3   1
                             ls5103i08   A4   0   ls5103i12   B4   0
                             ls5103i08   A5   1   ls5103i12   B5   1
                             ls5103i10   A6   0   ls5103i14   B6   0
                             ls5103i10   A7   1   ls5103i14   B7   1
                             ls5103i00   A8   2   ls5103i04   B8   2
                             ls5103i00   A9   3   ls5103i04   B9   3
                             ls5103i02   A10  2   ls5103i06   B10  2
                             ls5103i02   A11  3   ls5103i06   B11  3
                             ls5103i08   A12  2   ls5103i12   B12  2
                             ls5103i08   A13  3   ls5103i12   B13  3
                             ls5103i10   A14  2   ls5103i14   B14  2
                             ls5103i10   A15  3   ls5103i14   B15  3
   5104   LIMATM    ATMANSI  stpd078a    A    3
   5105   LIMATM    ATMANSI  stpb058a    A    4
   5106   LIMATM    ATMANSI  stpd078a    A    4
   5107   LIMATM    ATMANSI  stpb058a    A    5
   5108   LIMATM    ATMANSI  stpd078a    A    5
   5112   LIME1     CCS7ITU  ls5112n00   A    0   ls5112n04   B    0
                             ls5112n00   A1   1   ls5112n04   B1   1
                             ls5112n02   A2   0   ls5112n06   B2   0
                             ls5112n02   A3   1   ls5112n06   B3   1
                             ls5112n08   A4   0   ls5112n12   B4   0
                             ls5112n08   A5   1   ls5112n12   B5   1
                             ls5112n10   A6   0   ls5112n14   B6   0
                             ls5112n10   A7   1   ls5112n14   B7   1
                             ls5112n00   A8   2   ls5112n04   B8   2
                             ls5112n00   A9   3   ls5112n04   B9   3
                             ls5112n02   A10  2   ls5112n06   B10  2
                             ls5112n02   A11  3   ls5112n06   B11  3
                             ls5112n08   A12  2   ls5112n12   B12  2
                             ls5112n08   A13  3   ls5112n12   B13  3
                             ls5112n10   A14  2   ls5112n14   B14  2
                             ls5112n10   A15  3   ls5112n14   B15  3
   5113   LIMT1     SS7ANSI  ls5113a00   A    0   ls5113a04   B    0
                             ls5113a00   A1   1   ls5113a04   B1   1
                             ls5113a02   A2   0   ls5113a06   B2   0
                             ls5113a02   A3   1   ls5113a06   B3   1
                             ls5113a08   A4   0   ls5113a12   B4   0
                             ls5113a08   A5   1   ls5113a12   B5   1
                             ls5113a10   A6   0   ls5113a14   B6   0
                             ls5113a10   A7   1   ls5113a14   B7   1
                             ls5113a00   A8   2   ls5113a04   B8   2
                             ls5113a00   A9   3   ls5113a04   B9   3
                             ls5113a02   A10  2   ls5113a06   B10  2
                             ls5113a02   A11  3   ls5113a06   B11  3
                             ls5113a08   A12  2   ls5113a12   B12  2
                             ls5113a08   A13  3   ls5113a12   B13  3
                             ls5113a10   A14  2   ls5113a14   B14  2
                             ls5113a10   A15  3   ls5113a14   B15  3
   5117   DCM       SS7IPGW  ls5117a00   A    0
   5118   DCM       SS7IPGW  ls5117a00   A    1
   5208   LIME1     CCS7ITU  ls5208i00   A    0   ls5208i04   B    0
                             ls5208i00   A1   1   ls5208i04   B1   1
                             ls5208i00   A2   2   ls5208i04   B2   2
                             ls5208i00   A3   3   ls5208i04   B3   3
                             ls5208i00   A4   4   ls5208i04   B4   4
                             ls5208i00   A5   5   ls5208i04   B5   5
                             ls5208i00   A6   6   ls5208i04   B6   6
                             ls5208i00   A7   7   ls5208i04   B7   7
                             ls5208i00   A8   8   ls5208i04   B8   8
                             ls5208i00   A9   9   ls5208i04   B9   9
                             ls5208i00   A10  10  ls5208i04   B10  10
                             ls5208i00   A11  11  ls5208i04   B11  11
                             ls5208i00   A12  12  ls5208i04   B12  12
                             ls5208i00   A13  13  ls5208i04   B13  13
                             ls5208i00   A14  14  ls5208i04   B14  14
                             ls5208i00   A15  15  ls5208i04   B15  15
   5211   DSM       VSCCP                                               IMSI
   5215   DCM       SS7IPGW  ls5117a00   A    2
   5216   DCM       SS7IPGW  ls5117a00   A    3
   5217   DCM       SS7IPGW  ls5117a00   A    4
   5218   DCM       SS7IPGW  ls5117a00   A    5
   5301   DCM       SS7IPGW  sc1d079a    A    1
   5302   IPSM      IPS
   5303   DCM       SS7IPGW  ls5117a00   A    6
   5304   DCM       SS7IPGW  ls5117a00   A    7
   5306   LIME1     CCS7ITU  ls5306i00   A    0   ls5306i04   B    0
                             ls5306i00   A1   1   ls5306i04   B1   1
                             ls5306i00   A2   2   ls5306i04   B2   2
                             ls5306i00   A3   3   ls5306i04   B3   3
                             ls5306i00   A4   4   ls5306i04   B4   4
                             ls5306i00   A5   5   ls5306i04   B5   5
                             ls5306i00   A6   6   ls5306i04   B6   6
                             ls5306i00   A7   7   ls5306i04   B7   7
                             ls5306i00   A8   8   ls5306i04   B8   8
                             ls5306i00   A9   9   ls5306i04   B9   9
                             ls5306i00   A10  10  ls5306i04   B10  10
                             ls5306i00   A11  11  ls5306i04   B11  11
                             ls5306i00   A12  12  ls5306i04   B12  12
                             ls5306i00   A13  13  ls5306i04   B13  13
                             ls5306i00   A14  14  ls5306i04   B14  14
                             ls5306i00   A15  15  ls5306i04   B15  15
   5307   DSM       VSCCP                                               GTT
   5312   LIME1     CCS7ITU  ls5312i00   A    0   ls5312i04   B    0
                             ls5312i00   A1   1   ls5312i04   B1   1
                             ls5312i02   A2   0   ls5312i06   B2   0
                             ls5312i02   A3   1   ls5312i06   B3   1
                             ls5312i08   A4   0   ls5312i12   B4   0
                             ls5312i08   A5   1   ls5312i12   B5   1
                             ls5312i10   A6   0   ls5312i14   B6   0
                             ls5312i10   A7   1   ls5312i14   B7   1
                             ls5312i00   A8   2   ls5312i04   B8   2
                             ls5312i00   A9   3   ls5312i04   B9   3
                             ls5312i02   A10  2   ls5312i06   B10  2
                             ls5312i02   A11  3   ls5312i06   B11  3
                             ls5312i08   A12  2   ls5312i12   B12  2
                             ls5312i08   A13  3   ls5312i12   B13  3
                             ls5312i10   A14  2   ls5312i14   B14  2
                             ls5312i10   A15  3   ls5312i14   B15  3
   5315   LIMT1     SS7ANSI  ls5315a00   A    0   ls5315a04   B    0
                             ls5315a00   A1   1   ls5315a04   B1   1
                             ls5315a02   A2   0   ls5315a06   B2   0
                             ls5315a02   A3   1   ls5315a06   B3   1
                             ls5315a08   A4   0   ls5315a12   B4   0
                             ls5315a08   A5   1   ls5315a12   B5   1
                             ls5315a10   A6   0   ls5315a14   B6   0
                             ls5315a10   A7   1   ls5315a14   B7   1
                             ls5315a00   A8   2   ls5315a04   B8   2
                             ls5315a00   A9   3   ls5315a04   B9   3
                             ls5315a02   A10  2   ls5315a06   B10  2
                             ls5315a02   A11  3   ls5315a06   B11  3
                             ls5315a08   A12  2   ls5315a12   B12  2
                             ls5315a08   A13  3   ls5315a12   B13  3
                             ls5315a10   A14  2   ls5315a14   B14  2
                             ls5315a10   A15  3   ls5315a14   B15  3
   5316   LIMT1     SS7ANSI  ls5316a00   A    0   ls5316a04   B    0
                             ls5316a00   A1   1   ls5316a04   B1   1
                             ls5316a00   A2   2   ls5316a04   B2   2
                             ls5316a00   A3   3   ls5316a04   B3   3
                             ls5316a00   A4   4   ls5316a04   B4   4
                             ls5316a00   A5   5   ls5316a04   B5   5
                             ls5316a00   A6   6   ls5316a04   B6   6
                             ls5316a00   A7   7   ls5316a04   B7   7
                             ls5316a00   A8   8   ls5316a04   B8   8
                             ls5316a00   A9   9   ls5316a04   B9   9
                             ls5316a00   A10  10  ls5316a04   B10  10
                             ls5316a00   A11  11  ls5316a04   B11  11
                             ls5316a00   A12  12  ls5316a04   B12  12
                             ls5316a00   A13  13  ls5316a04   B13  13
                             ls5316a00   A14  14  ls5316a04   B14  14
                             ls5316a00   A15  15  ls5316a04   B15  15
   5317   DSM       VSCCP                                               ELAP
   6101   DSM       VSCCP                                               ELAP
   6103   ENET      IPSG     ls3211a00   A    6
   6104   ENET      IPSG     ls3211a00   A    7
   6105   DSM       VSCCP                                               ELAP
   6107   DSM       VSCCP                                               ELAP
   6111   DSM       VSCCP                                               ELAP
   6113   DSM       VSCCP                                               ELAP
   6115   DSM       VSCCP                                               ELAP
   6117   DSM       VSCCP                                               ELAP

   If service modules are shown in the rtrv-card output, shown by the entry VSCCP in the APPL column, continue the procedure with 4.

   If service modules are not shown in the rtrv-card output, continue the procedure with 2.

2. Verify that the GTT feature is on by entering the rtrv-feat command. If the GTT feature is on, the GTT field should be set to on. For this example, the GTT feature is off.

   Note:

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

   If the GTT feature is on, continue the procedure with 4.

   If the GTT feature is off, continue the procedure with 3.

3. Turn the global title translation feature on by entering this command.

   chg-feat:gtt=on

   Note:

   Once the Global Title Translation (GTT) feature is turned on with the chg-featcommand, it cannot be turned off.

   The GTT feature must be purchased before turning it on. If you are not sure whether you have purchased the GTT feature, contact your Sales Representative or Account Representative.

   When the chg-feat has successfully completed, this message should appear.

   rlghncxa03w 09-07-25 09:57:41 GMT EAGLE5 41.1.0
   CHG-FEAT: MASP A - COMPLTD
   

   Continue the procedure by performing one of these steps.

   • If a card is being added, continue the procedure with 7.
   • If an E5-SM8G-B card is being added, continue the procedure with 6.
4. Display the status of the features in the database by entering the rtrv-ctrl-feat command. The following is an example of the possible output.

   tklc1110501 15-06-24 16:53:12 EST  EAGLE5 46.2.0-65.53.1
   The following features have been permanently enabled:
   
   Feature Name                 Partnum   Status Quantity
   Large System # Links         893005910 on     2000
   XGTT Table Expansion         893006110 on     1000000
   Routesets                    893006403 on     8000
   LNP Short Message Serv.      893006601 on     ----
   Intermed GTT Load Sharing    893006901 on     ----
   Command Class Management     893005801 on     ----
   Telnet                       893005701 on     ----
   EAGLE5 Product               893007101 on     ----
   XMAP Table Expansion         893007710 on     3000
   LNP ported NPANXXs           893009403 on     350000
   LNP ported LRNs              893010506 on     200000
   LNP ELAP Configuration       893010901 on     ----
   LNP ported TNs               893011036 on     384000000
   SCCP Conversion              893012001 on     ----
   HC-MIM SLK Capacity          893012707 on     64
   EAGLE OA&M IP Security       893400001 off    ----
   Flexible GTT Load Sharing    893015401 on     ----
   Origin-Based MTP Routing     893014201 on     ----
   Origin Based SCCP Routing    893014301 on     ----
   GPORT                        893017201 on     ----
   INP                          893017901 on     ----
   Throughput Cap               893019101 on     5000
   Multiple Linkset to APC      893019701 on     ----
   6-Way LS on Routesets        893019801 on     ----
   Proxy Point Code             893018710 on     100
   AMGTT                        893021801 on     ----
   VGTT with 16 GTT lengths     893024801 on     ----
   ITU TCAP LRN QUERY(LRNQT)    893026301 on     ----
   ISLSBR                       893026501 on     ----
   GTT Action - DISCARD         893027501 on     ----
   GTT Action - DUPLICATE       893027601 on     ----
   GTT Action - FORWARD         893037501 on     ----
   Flex Lset Optnl Based Rtg    893027701 on     ----
   TCAP Opcode Based Routing    893027801 on     ----
   TOBR Opcode Quantity         893027907 on     1000000
   ST-HSL-A SLK Capacity        893027301 on     4
   3 Links per E5-ATM card      893039104 on     20
   Integrated GLS               893038901 on     ----
   EPAP Data Split              893039801 on     ----
   Dual ExAP Config             893040501 on     ----
   
   The following features have been temporarily enabled:
   
   Feature Name                 Partnum   Status Quantity     Trial Period Left
   Zero entries found.
   
   The following features have expired temporary keys:
   
   Feature Name                 Partnum
   Zero entries found.

   Table 2-34 shows the ELAP-Based and EPAP-Based features that can be enabled. These features can affect how many service modules can be provisioned in the EAGLE.

   Table 2-34 ELAP-Based and EPAP-Based Features

   ELAP-Based Features
   LNP
   EPAP-Based Features
   EIR	G-Port	INP
   ANSI-41 INP Query	A-Port	IS41 GSM Migration
   G-Flex	TINP	V-Flex
   ATINP	TIF Number Portability	TIF SCS Forwarding
   TIF Simple Number Substitution	TIF ASD	TIF GRN
   Prepaid IDP Query Relay	IDP Screening for Prepaid	MO-based GSM SMS NP
   MO-based IS41 SMS NP	MO SMS IS41-to-GSM Migration	MO SMS ASD
   MO SMS GRN	Portability Check for MO SMS	Prepaid SMS Intercept Phase 1
   Service Portability	Info Analyzed Relay Base	TIF Selective Screening

   Continue the procedure by performing one of these steps.

   • If any of the features shown in Table 2-34 are enabled, or if any the shown in Table 2-34 will be enabled, continue the procedure with 5.
   • If none of the features shown in Table 2-34 are enabled and none of these features will be enabled, continue the procedure with 6.
5. Verify the number of service modules in the EAGLE by entering the rept-stat-sccp command. The number of service modules is shown in the SCCP Cards Configured field of the rept-stat-sccp output. This is an example of the possible output.

   tklc1110501 15-06-24 17:00:40 EST  EAGLE5 46.2.0-65.53.1
   SCCP SUBSYSTEM REPORT   IS-NR          Active     -----
        SCCP ALARM STATUS   = No Alarms
   MNP SERVICE REPORT      IS-ANR         Active     -----
        MNP ALARM STATUS    = **  0547 Service degraded
   LNP SUBSYSTEM REPORT    IS-NR          Active     -----
        LNP:    SSN STATUS  = Allowed     MATE SSN STATUS = ----------
        LNP ALARM STATUS    = **  0283 LNP Ported LRNs approaching Feat. Cap.
   INPQ SUBSYSTEM REPORT   IS-ANR         Active     -----
        INPQ:   SSN STATUS  = Allowed     MATE SSN STATUS = ----------
        INP ALARM STATUS    = **  0428 INP Subsystem degraded, cards abnormal
   
   SCCP Cards Configured=28      Cards IS-NR=27
   System Daily Peak SCCP Load       4134   TPS 15-06-24 07:13:24
   System Overall Peak SCCP Load     4134   TPS 15-06-24 07:13:24
   System Total SCCP Capacity        135000 TPS (135000 max SCCP Capacity)
   System SCCP Capacity Calc. Method (N)
   System TPS Alarm Threshold        108000 TPS ( 80% System   N SCCP Capacity)
   
   CARD   VERSION      PST     SST        AST    MSU    CPU   DATA
                                                USAGE  USAGE  TYPE
   ----------------------------------------------------------------
   1317   135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   2211   135-052-000  IS-NR   Active    -----    1%     9%   GTT
   2217   135-052-000  IS-NR   Active    -----   20%    10%   ELAP
   2305   135-052-000  IS-NR   Active    -----    1%     3%   IMSI
   2311   135-052-000  IS-NR   Active    -----    0%     1%   IMSI
   2317   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   3103   135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   3111   135-052-000  IS-NR   Active    -----    0%     5%   DN
   3201 P 135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   3203   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   3205   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   3207   135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   3217   135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   4107   135-052-000  IS-NR   Active    -----    0%     4%   IMSI
   4111   135-052-000  IS-NR   Active    -----    0%     9%   GTT
   4207 P 135-052-000  IS-NR   Active    -----    1%     5%   DN
   4311   -----------  OOS-MT  Isolated  -----    0%     0%   DN
   5211   135-052-000  IS-NR   Active    -----    1%     5%   IMSI
   5307   135-052-000  IS-NR   Active    -----    1%     9%   GTT
   5317   135-052-000  IS-NR   Active    -----   20%     4%   ELAP
   6101   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   6105   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   6107   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   6111   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   6113   135-052-000  IS-NR   Active    -----    2%     3%   ELAP
   6115   135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   6117   135-052-000  IS-NR   Active    -----    2%     5%   ELAP
   1107   135-052-000  IS-NR   Active    -----    2%     2%   ELAP
   ----------------------------------------------------------------
   SCCP Service Average MSU Capacity =   2%   Average CPU Capacity =   4%
   
   AVERAGE CPU USAGE PER SERVICE:
   GTT    =   1%  MNP    =   0%
   LNPMR  =   1%  LNPQS  =   1%  WNPQS  =   1%  TLNP   =   1%  PLNPQS =   1%
   LRNQT  =   0%  INPMR  =   0%
   
   TOTAL SERVICE STATISTICS:
                                   FAIL     REROUTE\       FORWARD
   SERVICE    SUCCESS    ERRORS   RATIO     WARNINGS        TO GTT     TOTAL
   GTT:           111         0      0%            -             -       111
   MNP:             0         0      0%            0             0         0
   LNPMR:        1602         0      0%            -             -      1602
   LNPQS:      109065        32      0%            -             -    109097
   WNPQS:        1266         0      0%            -             -      1266
   TLNP:          725         0      0%            -             -       725
   PLNPQS:       8817         0      0%            -             -      8817
   LRNQT:           0         0      0%            -             -         0
   INPMR:           0         0      0%            0             0         0
   INPQ:            0         0      0%            0             -         0

   Note:

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

   Table 2-35 shows the maximum number of service modules that can be provisioned based on the type of SCCP traffic the EAGLE is handling and whether or not the Throughput Capacity or the EAGLE SCCP Capacity Increase features are enabled and turned on.

   Table 2-35 SCCP Transactions Per Second

   Type of Traffic	Maximum Transactions per Second for EAGLE	Transactions per Second for Each Service Module	Maximum Number of Service Modules
   Throughput Capacity Feature for 5000 SCCP Transactions per Second is Enabled or Turned On (See Notes 1 and 2)
   GTT Traffic or ANSI41 AIQ only - No EPAP-Based Traffic or ELAP-Based (LNP) Traffic	200,000	5000	41
   ANSI G-Flex EPAP-Based Traffic Only	195,000	5000	40
   EPAP-Based Traffic (except ANSI G-Flex Traffic)	195,000	5000	40
   ELAP-Based (LNP) Traffic	85,000	5000	18 (See Note 3)
   Throughput Capacity Feature for 6800 SCCP Transactions per Second is Enabled and Turned On (See Notes 1 and 2)
   GTT Traffic or ANSI41 AIQ only - No EPAP-Based Traffic or ELAP-Based (LNP) Traffic	272,000	6800	41
   EPAP-Based Traffic (including ANSI G-Flex Traffic)	265,200	6800	40
   ELAP-Based (LNP) Traffic	115,600	6800	18 (See Note 3)
   Throughput Capacity Feature for 10000 SCCP Transactions per Second is Enabled and Turned On (See Note 4)
   GTT Traffic or ANSI41 AIQ	400,000	10,000	41
   EPAP-Based Traffic (including ANSI G-Flex Traffic)	390,000	10,000	40
   ELAP-Based (LNP) Traffic	17,000	10,000	18
   Throughput Capacity Feature for 13600 SCCP Transactions per Second is Enabled and Turned On
   GTT Traffic or ANSI41 AIQ	544,000	13,600	41
   EPAP-Based Traffic (including ANSI G-Flex Traffic)	530,400	13,600	40
   ELAP-Based (LNP) Traffic	231,200	13,600	18
   Notes: To achieve the maximum transactions per second shown in this portion of the table, all the service modules must be SLIC cards. The value shown in the Transactions per Second for each Service Module column in this portion of the table applies only to SLIC cards. The number of service modules can be a maximum of 18 only if the ELAP version is 9.0. If the ELAP version is less than 9.0, only nine service modules can be used for ELAP-based traffic. Throughput Capacity feature for 10000 TPS requires E5-SM8G-B cards, and 13.6K TPS requires SLIC cards.

   Table 2-36 shows the maximum SCCP throughput capacity based on the combinations of features and GPL/card.

   Table 2-36 SCCP Throughput Capacity

   SCCP Throughput Capacity Feature Activated	E5-SM8G-B TPS	SLIC TPS
   13.6K TPS (P/N: 893019104)	13600	13600 TPS if all below conditions are true: EGMS feature is not activated EPAP240M option in STPOPTS is OFF or SM card is provisioned as data=DN/IMSI/ELAP/GTT No UAM 548 or 549 present in the system
   		10000 TPS if any of the below conditions are true: EGMS feature is activated. EPAP240M option in STPOPTS is ON and SM card is not provisioned as data=DN/IMSI/ELAP/GTT UAM 548 or 549 is present in the system
   10K TPS (P/N: 893019103)	10000	10000
   6.8K TPS (P/N: 893019102)	6800	6800
   5K TPS (P/N: 893019101)	5000	5000

   The EAGLE’s total SCCP throughput capacity can be calculated as the number of SCCP cards in the system (N) times the SCCP throughput capacity per card (keeping in mind the SCCP configuration of the system: N or N+1). The number of SCCP cards in the system depends on whether the system is a pure GTT or EPAP or ELAP system and the specific EAGLE/EPAP/ELAP release.

   Table 2-37 Number Service Module Cards in the System

   MPS Release	SM4G Cards (up to 5K/6.8K/10KTPS)
   ELAP 10.0	18	Up to 384 mil TNs
   Up to EAGLE 41.1+ EPAP 16	25
   From EAGLE 42.0 + EPAP 16 on AS T1000	25 (in N+1 config)
   From EAGLE 42.0 +EPAP 16 on AS T1200	32 (in N+1 config)

   If the rept-stat-sccp output shows that the EAGLE has the maximum number of service modules, as shown in Table 2-37, the remainder of this procedure cannot be performed.

   If the rept-stat-sccp output shows that the EAGLE does not have the maximum number of service modules, as shown in Table 2-37, continue the procedure by performing one of these steps.

   • If a card is being added, continue the procedure with 7.
   • If an E5-SM8G-B card is being added, continue the procedure with 6.
6. Verify that HIPR2 cards are installed at card locations 9 and 10 in the shelf where the E5-SM8G-B card will be installed. Enter this command.

   rept-stat-gpl:gpl=hipr2

   This is an example of the possible output.

   rlghncxa03w 09-07-01 11:40:26 GMT  EAGLE5 41.1.0
   GPL        CARD      RUNNING          APPROVED       TRIAL
   HIPR2      1109      126-002-000      126-002-000    126-003-000
   HIPR2      1110      126-002-000      126-002-000    126-003-000
   HIPR2      1209      126-002-000      126-002-000    126-003-000
   HIPR2      1210      126-002-000      126-002-000    126-003-000
   HIPR2      1309      126-002-000      126-002-000    126-003-000
   HIPR2      1310      126-002-000      126-002-000    126-003-000
   HIPR2      2109      126-002-000      126-002-000    126-003-000
   HIPR2      2110      126-002-000      126-002-000    126-003-000
   Command Completed

   If HIPR2 cards are installed at card locations 9 and 10 in the shelf where the E5-SM8G-B card will be installed, continue the procedure with 7.

   If HIPR2 cards are not installed in the shelf where the E5-SM8G-B card will be installed, refer to Installation Guide to install the HIPR2 cards. Once the HIPR2 cards have been installed, continue the procedure with 7.

7. Verify the service module has been physically installed into the proper location according to the feature requirements. Table 2-32 shows the type of service module that is required based on the GTT-related features that are currently being used (also shown in the rtrv-feat output in 2 as being on, and in the rtrv-ctrl-feat output in 4 as being enabled) and any features that will be enabled after this procedure is performed.

   Caution:

   If the versions of the flash GPLs on the service module do not match the flash GPL versions in the database when the service module is inserted into the card slot, UAM 0002 is generated to indicate that these GPL versions do not match. If UAM 0002 has been generated, perform the alarm clearing procedure for UAM 0002 in Unsolicited Alarm and Information Messages Reference before proceeding with this procedure.
8. Verify the EAGLE has a fan unit and the fan unit is on. If the fan unit is not on, use the enable-ctrl-feat:fan=on command to turn on the fan.
9. Verify the MFC STP option is turned on. If the MFC STP option is not turned on, use the enable-ctrl-feat:MFC=on to turn it on.
10. Add the service module to the database using the ent-card command. For this example, enter this command.

    ent-card:loc=1301:type=dsm:appl=vsccp

    Note:

    If any EPAP-based feature is enabled and turned on, and the service module quantity will exceed 25, the ent-card command must be entered twice within 30 seconds on the same terminal for the service module to be added to the database.

    When this command has completed, one of these messages should appear.

    • If any of these conditions will be present after the new service module is added to the database:
      • the total number of service modules will not be increased beyond 25
      • the total number of service modules will be greater than 25 and no EPAP-based features are enabled and turned on (see Table 2-34)
      • the total number of service modules will be from 27 to 32 and any EPAP-based features are enabled and turned on (see Table 2-34)
      this message should appear.

      rlghncxa03w 10-07-25 09:57:51 GMT  EAGLE5 42.0.0
      ENT-CARD: MASP A - COMPLTD

    • If the addition of the new service module will increase the total number of service modules to 26 and any EPAP-based features are enabled and turned on (see Table 2-34), this message should appear.

      rlghncxa03w 10-07-25 09:57:51 GMT  EAGLE5 42.0.0
      
      CAUTION: Please ensure EPAP Application Server is running on
      hardware supporting 32 SCCP cards e.g.: T1200.                                                             
      Re-enter command within 30 seconds to confirm change.
          
      rlghncxa03w 10-07-25 09:57:51 GMT  EAGLE5 42.0.0
      ENT-CARD: MASP A - Command Aborted

      After this message appears, re-enter the ent-card command within 30 seconds. This message should appear.

      rlghncxa03w 10-07-25 09:57:51 GMT  EAGLE5 42.0.0
      ENT-CARD: MASP A - COMPLTD

      If the ent-card command is not re-entered within 30 seconds, this message should appear and the new service module will not be added to the database.

      ENT-CARD command (Type=DSM) confirmation timer expired

11. Verify the changes using the rtrv-card command with the card location specified. For this example, enter this command.

    rtrv-card:loc=1301

    This is an example of the possible output.

    rlghncxa03w 09-07-25 09:58:31 GMT EAGLE5 41.1.0
    CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
    1301   DSM       VSCCP

12. Display the current IP link parameters associated with the Service Module card in the database by entering the rtrv-ip-lnk command:

    RLGHNCXA03W 05-14-24 21:14:37 GMT EAGLE 46.0.0
    LOC PORT IPADDR SUBMASK DUPLEX SPEED MACTYPE AUTO MCAST
    1107 A ------- -------- HALF 10 DIX NO NO
    1107 B ------- -------- HALF 10 DIX NO NO

13. Enter the IP address and other parameter values associated with the Service Module card in the database using the chg-ip-lnk command:

    For example, enter:

    chg-ip-lnk:loc=1107:port=a:ipaddrr=192.168.122.1:mactype=dix:auto=yes: mcast=yes:submask=255.255.255.0

    chg-ip-lnk:loc=1107:port=b:ipaddrr=192.168.123.1:mactype=dix:auto=yes: mcast=yes:submask=255.255.255.0

    Where:

    :loc

    Card location or slot number of the SM card in the EAGLE

    :port

    Ethernet interface Port ID-the physical interface of the SM card

    :ipaddr

    IP address for the specified port. This is a TCP/IP address expressed in standard dot notation. IP addresses consist of the network number of the system and the unique host number.

    :submask

    Subnet mask of the IP interface in the form of an IP address with a restricted range of values

    :mactype

    Media Access Control Type of the interface. When a Service Module card is entered into the database, these values are automatically configured.

    :mcast

    Multicast Control to enable or disable multicast support for the interface. This parameter value must be yes to establish the connection from the SM card to the MPS system.

    :auto

    Tells hardware whether to automatically determine duplex and speed.

    Note:

    Corresponding ports on ExAP LAN switches should be configured accordingly to achieve the required operational speed and duplex of 1Gbps and Full Duplex. Refer to ExAP Administration Guide for more information. Once the SM (SMxG/SLIC) card is in service, the pass command pass:cmd="netstat -i":loc=<:SM card loc> can be used to verify the operational speed and duplex of ExAP ports on SM cards.
14. Verify the IP address and other parameter values associated with the Service Module card in the database by entering the rtrv-ip-lnk command:

    RLGHNCXA03W 05-14-24 21:14:37 GMT EAGLE 46.0.0
    LOC PORT IPADDR SUBMASK DUPLEX SPEED MACTYPE AUTO MCAST
    1107 A 192.168.122.1 255.255.255.0 HALF 100 DIX NO YES
    1107 B 192.168.123.1 255.255.255.0 HALF 10 DIX NO YES

15. Display the current IP host information in the database by entering the rtrv-ip-host command:

    RLGHNCXA03W 05-14-24 21:17:37 GMT EAGLE 46.0.0
    IPADDR HOST
    192.1.1.32 KC_HLR2
    192.1.1.50 DN_MSC1
    192.1.1.52 DN_MSC2

16. Add the host name and IP address for each VSCCP link, using the ent-ip-host command.

    Command examples:

    ent-ip-host:host=vsccp_1107_a:ipaddr=192.168.122.1

    ent-ip-host:host=vsccp_1107_b:ipaddr=192.168.123.1

    Where:

    :host

    Host name. Each VSCCP link must be specified separately.

    :ipaddr

    IP network address for each EPAP. The first three octets of the IP address must be the same as MPS A and B ports, respectively. The fourth octet identifies the SM card and must have a unique octet identifier for the card IP address

17. Verify the new IP host information in the database by entering the rtrv-ip-host command:

    RLGHNCXA03W 05-14-24 21:19:37 GMT EAGLE 46.0.0
    IPADDR HOST
    192.1.1.32 KC_HLR2
    192.1.1.50 DN_MSC1
    192.1.1.52 DN_MSC2
    192.168.122.1 VSCCP_1107_A
    192.168.123.1 VSCCP_1107_B

18. Enter local domain and IP router address for the SM card using the chg-ip-card command:

    Note:

    Most customer private networks do not require setting up a default router for the SM card. If your network configuration requires a default router to connect the Service Module card communication to the EPAP, then only one default router is assignable to each Service Module card. Assign the default router address to each Service Module card as shown in this step.

    For example:

    chg-ip-card:defrouter=192.168.122.250:domain=nc.tekelec.com:loc=<card location>

    Where:

    :defrouter

    Default router IP address. This is a TCP/IP address expressed in standard dot notation. IP addresses consist of the network number of the system and the unique host number.

    :domain

    Domain name of domain server

    :loc

    Card location or slot number of the SM card in the EAGLE

19. Verify the new TCP/IP parameters associated with the SM card in the database by entering the rtrv-ip-card commands:

    RLGHNCXA03W 05-14-24 21:21:37 GMT EAGLE 45.0.0
    LOC 1107
    SRCHORDR LOCAL
    DNSA -----------
    DNSB -----------
    DEFROUTER 192.168.122.250
    DOMAIN NC.TEKELEC.COM

20. Allow the SM card that was added to operate in the system, using the alw-card command:
    alw-card:loc=<card location>
21. Verify the In-Service-Normal (IS-NR) status of the SM card, using the rept-stat-card command.
22. Test the presence of the EPAP hosts on the network using the pass command with the ping parameter. This command is invoked with a destination that is either a hostname or IP address.

    Command examples:

    pass:loc=1107:cmd=”ping 192.168.122.100”

    pass:loc=1107:cmd=”ping 192.168.122.200”

    pass:loc=1107:cmd=”ping 192.168.123.100”

    pass:loc=1107:cmd=”ping 192.168.123.200”

    Where:

    :loc

    Card location or slot number in the EAGLE

    :cmd

    Command string passed to Service Module card for processing.

    After successful completion of each command, the system response is similar to the following output:

    rlghncxa03w 05-14-24 08:30:44 GMT EAGLE 46.0.0
    pass: loc=1107: cmd="ping 192.168.122.100"
    Command entered at terminal #1.
    ;
    rlghncxa03w 05-14-24 08:30:44 GMT EAGLE 46.0.0
    PASS: Command sent to card
    ;
    rlghncxa03w 05-14-24 08:30:44 GMT EAGLE 46.0.0
    PING command in progress
    ;
    rlghncxa03w 05-14-24 08:30:46 GMT EAGLE 46.0.0
    PING 192.168.122.100: 56 data bytes
    64 bytes from tekral.nc.tekelec.com (192.168.122.100):icmp_seq=0.time=5. ms
    64 bytes from tekral.nc.tekelec.com (192.168.122.100):icmp_seq=1.time=0. ms
    64 bytes from tekral.nc.tekelec.com (192.168.122.100):icmp_seq=2.time=0. ms
    ----192.168.100.3 PING Statistics----
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip (ms) min/avg/max = 0/1/5
    PING command complete

    If the pass commands with the ping parameter are not successful, verify the correct connection of the hardware cabling and repeat this step. If the command fails again, contact the unresolvable-reference.html#GUID-B82ED41B-4E6F-4168-AF60-FEC7BFB99F23.

23. Put the card in service using the rst-card command with the card location specified in global-title-translation-gtt-overview.html. For this example, enter this command.

    rst-card:loc=1301

    Note:

    The primary state of the service module will remain IS-ANR and the secondary state of the service module will remain MPS_UNAVAIL after the rst-card command is performed when these conditions are present.

    • An EPAP-based feature is enabled and turned on.
    • Adding the new service module increased the service module quantity beyond 25.

    When this command has successfully completed, this message should appear.

    rlghncxa03w 09-07-28 08:21:07 GMT  EAGLE5 41.1.0
    Card has been allowed.

    Continue the procedure by performing one of these steps.

    • If the EGTT feature is on, shown by the entry EGTT = on in the rtrv-feat command output in global-title-translation-gtt-overview.html , or if the EGTT feature is off and will not be turned on in this procedure, continue the procedure with global-title-translation-gtt-overview.html.
    • If the EGTT feature is off and will be turned on in this procedure, continue the procedure with global-title-translation-gtt-overview.html.
24. Turn the enhanced global title translation feature on by entering this command.

    Note:

    Once the Enhanced Global Title Translation (EGTT) feature is turned on with the chg-feat command, it cannot be turned off.

    The EGTT feature must be purchased before turning it on. If you are not sure whether you have purchased the EGTT feature, contact your Sales Representative or Account Representative.

    When the chg-feat has successfully completed, this message should appear.

    
    rlghncxa03w 09-07-25 09:57:41 GMT EAGLE5 41.1.0
    CHG-FEAT: MASP A - COMPLTD
    

25. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.

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

Figure 2-37 Add a Service Module - Sheet 1 of 4

Figure 2-38 Add a Service Module - Sheet 2 of 4

Figure 2-39 Add a Service Module - Sheet 3 of 4

Figure 2-40 Add a Service Module - Sheet 4 of 4

1. Display the status of the service modules by entering the rept-stat-sccp command.

   This is an example of the possible output.

   rlghncxa03w 06-10-25 09:57:31 GMT  EAGLE5 36.0.0
   
   CARD  VERSION      PST             SST        AST       MSU USAGE  CPU USAGE
   -----------------------------------------------------------------------------
   2101  113-002-001  IS-NR           Active     -----       47%         81%
   2103  113-002-001  IS-NR           Active     -----       34%         50%
   2111  113-002-001  IS-NR           Active     -----       21%         29%
   2115  113-002-001  IS-NR           Active     -----       35%         52%
   2117  113-002-001  IS-NR           Active     -----       40%         71%
   -----------------------------------------------------------------------------
   SCCP Service Average MSU Capacity = 36%       Average CPU Capacity = 56%
   Command Completed.

   Note:

   The rept-stat-sccp command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rept-stat-sccp command, refer to the rept-stat-sccp command description in Commands User's Guide.
2. Remove the card from service using the rmv-card command and specifying the card location.

   If the service module to be inhibited is the only service module in service, the force=yes parameter must also be specified. The cards that are in service are shown by the entry IS-NR in the PST field in the output in 1. For this example, enter this command.

   rmv-card:loc=1204

   When this command has successfully completed, this message should appear.

   rlghncxa03w 06-10-25 09:57:41 GMT  EAGLE5 36.0.0
   Card has been inhibited.

3. Remove the card from the database using the dlt-card command.

   The dlt-card command has only one parameter, loc, which is the location of the card. For this example, enter this command.

   dlt-card:loc=1204

   When this command has successfully completed, this message should appear.

   rlghncxa03w 06-10-25 09:57:51 GMT  EAGLE5 36.0.0
   DLT-CARD: MASP A - COMPLTD

4. Verify the changes using the rtrv-card command specifying the card that was removed in 2.

   For this example, enter this command.

   rtrv-card:loc=1204

   When this command has successfully completed, this message should appear.

   E2144 Cmd Rej: Location invalid for hardware configuration

5. Backup the new changes using the chg-db:action=backup:dest=fixed command.
   These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.

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

Figure 2-41 Remove a Service Module

1. Display the mapped translation types in the database using the rtrv-ttmap command.

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:31 GMT  EAGLE5 37.0.0
   LSN       IO  ETT  MTT
   nc001     I   047  032
   nc001     I   128  055
   nc001     I   238  128
   nc001     I   254  016
   nc001     O   016  254
   nc001     O   128  238

2. Display the linksets in the database using the rtrv-ls command. This is an example of the possible output.

   rlghncxa03w 09-05-25 09:57:41 GMT EAGLE5 41.0.0
   
                                     L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsa1          240-020-000   scr1  1    1  yes a   1    off off off no    off
   lsa2          240-030-000   scr2  1    2  no  c   3    on  on  on  yes   off
   lsa3          240-040-000   scr3  1    3  yes c   5    off off off yes   off
   lsn01         240-050-000   scr4  1    3  yes c   5    off off off yes   off
   nc001         240-060-000   scr5  1    3  yes c   5    off off off yes   off
   
                                     L3T SLT              GWS GWS GWS
   LSN           APCI (SS7)    SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsi1          1-111-1       scr1  1    1  yes a   1    off off off ---   ---
   lsi2          1-111-2       scr2  1    2  no  c   3    on  on  on  ---   ---
   lsi3          1-111-3       scr3  1    3  yes c   5    off off off ---   ---
   
                                     L3T SLT              GWS GWS GWS
   LSN           APCN (SS7)    SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn1          11111         scr1  1    1  yes a   1    off off off ---   off
   lsn2          11112         scr2  1    2  no  c   3    on  on  on  ---   off
   lsn3          11113         scr3  1    3  yes c   5    off off off ---   off
   
   Link set table is ( 11 of 1024)  1% full

   If the required linkset is not in the database, perform the “Adding an SS7 Linkset” procedure in Database Administration - SS7 User's Guide and add the linkset..

3. Add the mapped translation type to the database using the ent-ttmap command. For this example, enter this command.

   ent-ttmap:lsn=lsn01:io=i:ett=001:mtt=250

   When this command has successfully completed, this message should appear.

   rlghncxa03w 07-05-25 09:57:51 GMT  EAGLE5 37.0.0
   ENT-TTMAP: MASP A - COMPLTD
   
   TTMAP table for lsn01 is (1 of 64) 1% full

4. Verify the changes using the rtrv-ttmap command. This is an example of the possible output.

   rlghncxa03w 07-05-25 09:58:31 GMT  EAGLE5 37.0.0
   LSN       IO  ETT  MTT
   lsn01     I   001  250
   nc001     I   047  032
   nc001     I   128  055
   nc001     I   238  128
   nc001     I   254  016
   nc001     O   016  254
   nc001     O   128  238

5. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.

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

Figure 2-42 Add a Mapped SS7 Message Translation Type

1. Display the mapped translation types in the database using the rtrv-ttmap command.

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:31 GMT  EAGLE5 37.0.0
   LSN       IO  ETT  MTT
   lsn01     I   001  250
   nc001     I   047  032
   nc001     I   128  055
   nc001     I   238  128
   nc001     I   254  016
   nc001     O   016  254
   nc001     O   128  238

2. Add the mapped translation type to the database using the dlt-ttmap command.

   For this example, enter this command.

   dlt-ttmap:lsn=nc001:io=o:ett=016

   When this command has successfully completed, this message should appear.

   rlghncxa03w 07-05-25 09:57:41 GMT  EAGLE5 37.0.0
   DLT-TTMAP: MASP A - COMPLTD
   TTMAP table for nc001 is (5 of 64) 8% full

3. Verify the changes using the rtrv-ttmap command.

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:51 GMT  EAGLE5 37.0.0
   LSN       IO  ETT  MTT
   lsn01     I   001  250
   nc001     I   047  032
   nc001     I   128  055
   nc001     I   238  128
   nc001     I   254  016
   nc001     O   128  238

4. Backup the new changes using the chg-db:action=backup:dest=fixed command.

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

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

Figure 2-43 Remove a Mapped SS7 Message Translation Type

1. Display the mapped translation types in the database using the rtrv-ttmap command. This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:31 GMT  EAGLE5 37.0.0
   LSN       IO  ETT  MTT
   lsn01     I   001  250
   nc001     I   047  032
   nc001     I   128  055
   nc001     I   238  128
   nc001     I   254  016
   nc001     O   016  254
   nc001     O   128  238

2. Change the mapped translation type in the database using the chg-ttmap command. For this example, enter this command.

   chg-ttmap:lsn=lsn01:io=i:ett=001:mtt=255

   When this command has successfully completed, this message should appear.

   rlghncxa03w 07-05-25 09:57:41 GMT  EAGLE5 37.0.0
   CHG-TTMAP: MASP A - COMPLTD
   
   TTMAP table for lsn01 is (1 of 64) 1% full

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

   rlghncxa03w 07-05-25 09:57:51 GMT  EAGLE5 37.0.0
   LSN       IO  ETT  MTT
   lsn01     I   001  255
   nc001     I   047  032
   nc001     I   128  055
   nc001     I   238  128
   nc001     I   254  016
   nc001     O   016  254
   nc001     O   128  238

4. Backup the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.

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

1. Display the CSPC group names in the database using the rtrv-cspc command. This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:31  GMT  EAGLE5 37.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   grp01      ANSI                     6%
   grp02      ITU-I                    9%
   grp03      ITU-N                   12%
   grp04      ANSI                    15%

   If the ANSI/ITU SCCP Conversion feature is enabled, and multiple network point code types are assigned to CSPC groups, the network types of the point codes in each CSPC group are displayed in the rtrv-cspc output as follows in this example.

   rlghncxa03w 06-10-25 09:57:31  GMT  EAGLE5 36.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   grp01      ANSI, ITU-I, ITU-N        9%
   grp02      ITU-I                     9%
   grp03      ANSI,  ITU-N              6%
   grp04      ANSI                     15%

   Note:

   If the point code is being added to a new CSPC group, continue the procedure with 3.
2. Display the point codes in the CSPC group that the new point code is being added to by entering the rtrv-cspc command with the CSPC group name.

   For this example, enter this command.

   rtrv-cspc:grp=grp01

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp01         002-002-002
                 003-003-003

   If the ANSI/ITU SCCP Conversion feature is enabled, then point codes of multiple network types can be displayed, if point codes of multiple network types are assigned to the CSPC group, as shown in this example.

   rlghncxa03w 07-05-25 09:57:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PC            TYPE
   grp01         003-003-003   A
                 3-003-3       I
                 00112         N

3. Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the ent-cspc command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

   rtrv-rte:dpca=002-002-002

   This is an example of the possible output.

   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      002-002-002 ---------- --------------   ls02       10    002-002-002
                                                  RTX:No  CLLI=ls02clli

   rtrv-rte:dpca=008-008-008

   This is an example of the possible output.

   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      008-008-008 ---------- --------------   ls20       10    008-008-008
                                                  RTX:No  CLLI=ls20clli

   rtrv-rte:dpca=009-009-009

   This is an example of the possible output.

   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      009-009-009 ---------- --------------   ls09       10    009-009-009
                                                  RTX:No  CLLI=ls09clli

   If the point code is not shown in the rtrv-rte output, perform one the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. The route must contain a minimum of one active signaling link.

4. Display the signaling links that are in the linksets that are assigned to the route shown in 3 by entering the rtrv-ls command with the name of the linksets that are assigned to the route. For this example, enter these commands.

   rtrv-ls:lsn=ls02

   This is an example of the possible output.

   rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   ls02          002-002-002   none 1   1   no  A   2    off off off no    off
   
                 SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
              ---------------- ls02clli     1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA               no
   
                                     L2T               PCR  PCR
              LOC  PORT SLC TYPE     SET  BPS    ECM   N1   N2
              1211 A     0  LIMDS0   1    56000  BASIC ---  -----
              1211 B     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (12 of 1024) 1% full.

   rtrv-ls:lsn=ls20

   This is an example of the possible output.

   rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   ls20          008-008-008   none 1   1   no  A   2    off off off no    off
   
                 SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
              ---------------- ls20clli     1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA               no
   
                                     L2T               PCR  PCR
              LOC  PORT SLC TYPE     SET  BPS    ECM   N1   N2
              1212 A     0  LIMDS0   1    56000  BASIC ---  -----
              1212 B     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (12 of 1024) 1% full.

   rtrv-ls:lsn=ls09

   This is an example of the possible output.

   rlghncxa03w 09-07-17 11:43:04 GMT EAGLE5 41.1.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   ls09          009-009-009   none 1   1   no  A   2    off off off no    off
   
                 SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
              ---------------- ls09clli     1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA               no
   
                                     L2T               PCR  PCR
              LOC  PORT SLC TYPE     SET  BPS    ECM   N1   N2
              1213 A     0  LIMDS0   1    56000  BASIC ---  -----
              1213 B     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (12 of 1024) 1% full.

   If the linkset does not contain any signaling links, perform one of these procedures in these manuals to add the signaling link.

   • Database Administration – SS7 User's Guide
     • Adding an SS7 Signaling Link
     • Adding an E1 Signaling Link
     • Adding a T1 Signaling Link
     • Adding an ATM High-Speed Signaling Link
   • Database Administration – IP7 User's Guide
     • Adding an IPLIMx Signaling Link
     • Adding an IPGWx Signaling Link
     • Adding an IPSG M2PA Signaling Link
     • Adding an IPSG M3UA Signaling Link

   Make sure the signaling link is placed into service.

   Continue the procedure by performing one of these steps.

   • If signaling links were added to all the linksets displayed in this step, continue the procedure with 7.
   • If any of the linksets displayed in this step contain signaling links, continue the procedure with 5.
5. Display the status of the signaling links shown in 4 by entering the rept-stat-slk command with the signaling link displayed in 4. For this example, enter this command.

   rept-stat-slk:loc=1211:link=a

   This is an example of the possible output.

   rlghncxa03w 09-02-23 13:06:25 GMT EAGLE5 40.1.0
   SLK      LSN       CLLI        PST          SST       AST
   1211,A   ls02      ls02clli    OOS-MT-DSBLD Manual    ----
     ALARM STATUS       = **  0236 REPT-LKF: not aligned
     UNAVAIL REASON    = NA

   rept-stat-slk:loc=1211:link=b

   This is an example of the possible output.

   rlghncxa03w 09-02-23 13:06:25 GMT EAGLE5 40.1.0
   SLK      LSN       CLLI        PST          SST       AST
   1211,B   ls02      ls02clli    OOS-MT-DSBLD Manual    ----
     ALARM STATUS       = **  0236 REPT-LKF: not aligned
     UNAVAIL REASON    = NA

   rept-stat-slk:loc=1212:link=a

   This is an example of the possible output.

   rlghncxa03w 09-02-23 13:06:25 GMT EAGLE5 40.1.0
   SLK      LSN       CLLI        PST          SST       AST
   1212,A   ls20      ls20clli    IS-NR        Avail     ----
     ALARM STATUS       = No Alarms
     UNAVAIL REASON     = --

   rept-stat-slk:loc=1212:link=b

   This is an example of the possible output.

   rlghncxa03w 09-02-23 13:06:25 GMT EAGLE5 40.1.0
   SLK      LSN       CLLI        PST          SST       AST
   1212,B   ls20      ls20clli    IS-NR        Avail     ----
     ALARM STATUS       = No Alarms
     UNAVAIL REASON     = --

   rept-stat-slk:loc=1213:link=a

   This is an example of the possible output.

   rlghncxa03w 09-02-23 13:06:25 GMT EAGLE5 40.1.0
   SLK      LSN       CLLI        PST          SST       AST
   1213,A   ls09      ls09clli    IS-NR        Avail     ----
     ALARM STATUS       = No Alarms
     UNAVAIL REASON     = --

   rept-stat-slk:loc=1213:link=b

   This is an example of the possible output.

   rlghncxa03w 09-02-23 13:06:25 GMT EAGLE5 40.1.0
   SLK      LSN       CLLI        PST          SST       AST
   1213,B   ls09      ls09clli    IS-NR        Avail     ----
     ALARM STATUS       = No Alarms
     UNAVAIL REASON     = --

   Continue the procedure by performing one of these steps.

   • If the state of all the signaling links in a linkset displayed in this step is not IS-NR, continue the procedure with 6.
   • If the state of one or more of the signaling links in the linksets displayed in this step is IS-NR, continue the procedure with 7.
6. The linkset shown in 5 must contain at least active (IS-NR) signaling link. Enter the act-slk command to put into service one or more of the signaling links in the linkset. For this example, enter this command.

   act-slk:loc=1211:link=a

   When this command has successfully completed, this message should appear.

   rlghncxa03w 09-02-07 08:31:24 GMT  EAGLE5 40.1.0
   Activate Link message sent to card

   Continue the procedure by performing one of these steps.

   • If the network type of the point codes being added to the CSPC group will not be the same as the network type of the CSPC group, and multiple point code network types are not shown in the rtrv-cspc output in 1, continue the procedure with 7.
   • If the network type of the point codes being added to the CSPC group is the same as the network type of the CSPC group, or if multiple point code network types are shown in the rtrv-cspc output in 1, continue the procedure with 8.
7. Verify that the ANSI/ITU SCCP Conversion feature is enabled by entering the rtrv-ctrl-feat:partnum=893012001 command. The following is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   SCCP Conversion           893012001  on      ----
   
   The following features have been temporarily enabled:
   
   Feature Name              Partnum    Status  Quantity     Trial Period Left
   Zero entries found.
   
   The following features have expired temporary keys:
   
   Feature Name              Partnum
   Zero entries found.

   If the ANSI/ITU SCCP Conversion feature is not enabled, perform the Activating the ANSI/ITU SCCP Conversion Feature procedure and the ANSI/ITU SCCP Conversion feature.

8. Add the concerned signaling point code to the database using the ent-cspc command. For this example, enter these commands.

   ent-cspc:grp=grp05

   ent-cspc:grp=grp10

   ent-cspc:grp=grp15

   ent-cspc:grp=grp05:pca=002-002-002

   ent-cspc:grp=grp05:pca=008-008-008

   ent-cspc:grp=grp10:pca=008-008-008

   ent-cspc:grp=grp10:pca=009-009-009

   ent-cspc:grp=grp15:pca=002-002-002

   ent-cspc:grp=grp15:pca=009-009-009

   When each these commands have successfully completed, this message should appear.

   rlghncxa03w 07-05-25 09:57:41  GMT  EAGLE5 37.0.0
   ENT-CSPC:  MASP A - COMPLTD

9. Verify the changes using the rtrv-cspc command, with the CSPC group names specified in 8. For this example enter these commands.

   rtrv-cspc:grp=grp05

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:58:31  GMT  EAGLE5 37.0.0
   CSPC GRP      
   PCA
   grp05         002-002-002
                 008-008-008

   rtrv-cspc:grp=grp10

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:59:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp10         008-008-008
                 009-009-009

   rtrv-cspc:grp=grp15

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:57:41  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp15         002-002-002
                 009-009-009

   Note:

   If the ANSI/ITU SCCP Conversion feature is enabled, then point codes of multiple network types can be displayed in the rtrv-cspc output, if point codes of multiple network types are assigned to the CSPC group.
10. Backup the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.

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

1. Display the group names in the database using the rtrv-cspc command.

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:47:31  GMT  EAGLE5 37.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   grp01      ANSI                     6%
   grp02      ITU-I                    9%
   grp03      ITU-N                   12%
   grp04      ANSI                    15%
   grp05      ANSI                    15%
   grp10      ANSI                    15%
   grp15      ANSI                    15%

   If the ANSI/ITU SCCP Conversion feature is enabled, and multiple network point code types are assigned to CSPC groups, the rtrv-cspc output is displayed as follows in this example.

   rlghncxa03w 07-05-25 09:57:31  GMT  EAGLE5 37.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   grp01      ANSI, ITU-I, ITU-N        9%
   grp02      ITU-I                     9%
   grp03      ANSI,  ITU-N              6%
   grp04      ANSI                     15%
   grp05      ANSI                     15%
   grp10      ANSI                     15%
   grp15      ANSI                     15%

2. Display the point codes in the CSPC group that you wish to remove from that CSPC group using the rtrv-cspc command with the CSPC group name.

   For this example, enter this command.

   rtrv-cspc:grp=grp10

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp10         008-008-008
                 009-009-009

   If the ANSI/ITU SCCP Conversion feature is enabled, then point codes of multiple network types can be displayed, if point codes of multiple network types are assigned to the CSPC group, as shown in this example.

   rlghncxa03w 07-05-25 09:57:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PC            TYPE
   grp10         008-008-008   A
                 009-009-009   A
                 3-003-3       I
                 00112         N

   Note:

   If only a point code entry in the CSPC group is being removed, skip steps 3 and 4, and go to step 5.
3. Display the status of the Flexible GTT Load Sharing feature by entering the rtrv-ctrl-feat command with the Flexible GTTLoad Sharing feature part number.

   Enter this command.

   rtrv-ctrl-feat:partnum=893015401

   The following is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   Flexible GTT Load Sharing 893015401 on     ----
   
   The following features have been temporarily enabled:
   
   Feature Name              Partnum   Status Quantity   Trial Period 
   Left
   Zero entries found.
   
   The following features have expired temporary keys:
   
   Feature Name              Partnum
   Zero entries found.

   If the Flexible GTT Load Sharing feature is not enabled, skip step 4 and go to step 5.

   If the Flexible GTT Load Sharing feature is enabled, go to step 4.

4. Display the mated applications in the database using the rtrv-map command.

   This is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 250 10  SOL *Y  *Y  grp01    ON
   
   MAPSET ID=1
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 251 10  SHR *Y  *Y  grp01    OFF
                  253-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=2
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 252 10  SOL *Y  *Y  grp01    ON
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 253 10  SHR *Y  *Y  grp01    OFF
                  253-001-004  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=3
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-001                 255 10  DOM YES YES grp01    ON
                  253-001-005  254 20  DOM YES YES grp01    ON
   
   MAPSET ID=4
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-001                 250 10  DOM YES YES grp01    OFF
                  253-001-001  254 20  DOM YES YES grp01    OFF
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 251 10  SHR *Y  *Y  grp01    OFF
                  255-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=5
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 252 10  DOM YES YES grp01    ON
                  255-001-003  254 20  DOM YES YES grp01    ON
   
   MAPSET ID=6
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 253 10  SHR *Y  *Y  grp01    ON
                  255-001-004  254 10  SHR *Y  *Y  grp01    ON
   
   MAPSET ID=7
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-007                  50 10  COM YES *Y  grp01    OFF
                  002-002-008   30 10  COM YES *Y  grp01    OFF
                  002-002-009   30 10  COM YES *Y  grp01    OFF
                  002-002-010   30 20  COM YES *Y  grp01    OFF
                  002-002-011   30 20  COM YES *Y  grp01    OFF
   
   MAPSET ID=8
   PCI            Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
   2-001-2                     255 10  DOM NO  YES grp03    OFF
                  2-001-1      254 20  DOM NO  YES grp03    OFF
   
   MAPSET ID=9
   PCN            Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
   00347                       253 10  SHR *N  *N  grp05    OFF
                  01387        254 10  SHR *N  *N  grp05    OFF
   
   MAP TABLE IS  (20 of 36000)  1 % FULL

   If any of the following items are not shown in the rtrv-map output, then the feature corresponding to these items is not enabled, or turned on if required.

   • The MAPSET field - the Flexible GTT Load Sharing feature is not enabled.
   • The MRNSET and MRNPC fields - the GTT Load Sharing with Alternate Routing Indicator feature is not enabled.
   • The WT, %WT, THR columns - the Weighted GTT Load Sharing feature is not enabled and turned on.

   If the CSPC group being removed in this procedure is shown in the rtrv-map output, perform Changing the Attributes of a Mated Application to change the CSPC group assigned to the mated applications that are currently referencing the CSPC group being removed. After the CSPC group assignments have been changed, go to step 5.

   If the CSPC group being removed in this procedure is not shown in the rtrv-map output, go to step 5.

5. Remove the concerned signaling point code from the database using the dlt-cspc command.

   For this example, enter this command.

   dlt-cspc:grp=grp10:pca=008-008-008

   This message should appear.

   rlghncxa03w 07-05-25 09:49:31  GMT  EAGLE5 37.0.0
   DLT-CSPC:  MASP A - COMPLTD

   Note:

   If you wish to remove the entire CSPC group, enter the dlt-cspc command with the CSPC group name and the all=yes parameter. For this example, enter the dlt-cspc:grp=grp10:all=yes command.
6. Verify the changes using the rtrv-cspc command with the CSPC group name.

   For this example, enter this command.

   rtrv-cspc:grp=grp10

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:50:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp10         009-009-009

   Note:

   If the ANSI/ITU SCCP Conversion feature is enabled, then point codes of multiple network types can be displayed in the rtrv-cspc output, if point codes of multiple network types are assigned to the CSPC group.
7. Backup the new changes using the chg-db:action=backup:dest=fixed command.

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

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

Figure 2-49 Remove a Concerned Signaling Point Code - Sheet 1 of 3

Figure 2-50 Remove a Concerned Signaling Point Code - Sheet 2 of 3

Figure 2-51 Remove a Concerned Signaling Point Code - Sheet 3 of 3

New MAPSET Created : MAPSETID = <new MAP set ID>

1. Display the mated applications in the database using the rtrv-map command.

   This is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 250 10  SOL *Y  *Y  grp01    ON
   
   MAPSET ID=1
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 251 10  SHR *Y  *Y  grp01    OFF
                  253-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=2
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 252 10  SOL *Y  *Y  grp01    ON
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 253 10  SHR *Y  *Y  grp01    OFF
                  253-001-004  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=3
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-001                 255 10  DOM YES YES grp01    ON
                  253-001-005  254 20  DOM YES YES grp01    ON
   
   MAPSET ID=4
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-001                 250 10  DOM YES YES grp01    OFF
                  253-001-001  254 20  DOM YES YES grp01    OFF
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 251 10  SHR *Y  *Y  grp01    OFF
                  255-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=5
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 252 10  DOM YES YES grp01    ON
                  255-001-003  254 20  DOM YES YES grp01    ON
   
   MAPSET ID=6
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 253 10  SHR *Y  *Y  grp01    ON
                  255-001-004  254 10  SHR *Y  *Y  grp01    ON
   
   MAPSET ID=7
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-007                  50 10  COM YES *Y  grp01    OFF
                  002-002-008   30 10  COM YES *Y  grp01    OFF
                  002-002-009   30 10  COM YES *Y  grp01    OFF
                  002-002-010   30 20  COM YES *Y  grp01    OFF
                  002-002-011   30 20  COM YES *Y  grp01    OFF
   
   MAPSET ID=8
   PCI            Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
   2-001-2                     255 10  DOM NO  YES grp03    OFF
                  2-001-1      254 20  DOM NO  YES grp03    OFF
   
   MAPSET ID=9
   PCN            Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
   00347                       253 10  SHR *N  *N  grp05    OFF
                  01387        254 10  SHR *N  *N  grp05    OFF
   
   MAP TABLE IS  (25 of 36000)  1 % FULL

   If any of the following items are not shown in the rtrv-map output, then the feature corresponding to these items is not enabled, or turned on if required.

   • The MAPSET field - the Flexible GTT Load Sharing feature is not enabled.
   • The MRNSET and MRNPC fields - the GTT Load Sharing with Alternate Routing Indicator feature is not enabled.
   • The WT, %WT, THR columns - the Weighted GTT Load Sharing feature is not enabled and turned on.

   Continue the procedure by performing one of these steps.

   • If the maximum number of mated applications is 3000 and the current number of mated applications provisioned in the database is 3000, no mated applications with a new point code can be added. Continue the procedure with 3.
   • If the rtrv-map output in shows that the maximum number of mated applications is either 1024 or 2000, and the mated application being added increases the number beyond 1024 or 2000, perform the Enabling the XMAP Table Expansion Feature procedure to increase the maximum number of mated applications that can be in the database. After the Enabling the XMAP Table Expansion Feature procedure has been completed, continue the procedure with 3. If the maximum number of mated applications is not increased, no new point codes can be used to provision mated applications.
   • If the rtrv-map output in shows that the maximum number of mated applications is either 1024, 2000, or 3000 and the mated application being added will not increase the number beyond the quantity shown in the rtrv-map output in, continue the procedure with 3.
   • If the maximum number of mated applications is 36,000, continue the procedure with 2.
2. To verify the number of different point codes that can be provisioned for mated applications, enter the rtrv-tbl-capacity command.

   If the maximum number of mated applications shown in the rtrv-map output in 1 is 36000, the Flexible GTT Load Sharing feature is enabled.

   Note:

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

   Although the rtrv-map output shows there can be 36000 entries, a maximum of 1024, 2000, or 3000 different point codes (depending on whether the XMAP Table Expansion feature is enabled for 2000 or 3000 mated applications) can be provisioned for mated applications.

   The following is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   
   MAP table is (3000 of 3000) 100% full

   Continue the procedure by performing one of these steps.

   • If the maximum number of mated applications shown in this step is 3000 and the current number of mated applications provisioned in the database is 3000, no mated applications with a new point code can be added. Continue the procedure with 3.
   • If the maximum number of mated applications is either 1024 or 2000, and the mated application being added increases the number beyond 1024 or 2000, perform the Enabling the XMAP Table Expansion Feature procedure to increase the maximum number of mated applications that can be in the database. After the Enabling the XMAP Table Expansion Feature procedure has been completed, continue the procedure with 3. If the maximum number of mated applications is not increased, no new point codes can be used to provision mated applications.
   • If the maximum number of mated applications is either 1024, 2000, or 3000 and the mated application being added will not increase the number beyond the quantity shown in the rtrv-map output in, continue the procedure with 3.
3. A mated application can be provisioned with a point code that is assigned to other mated applications as long as the SSN is not assigned to other mated applications. A point code can be assigned to maximum of 12 different SSNs.

   Verify the number of SSNs assigned to the point code that will be specified for the mated application in this procedure by entering the rtrv-map command with the point code of the new mated application. For this example, enter this command.

   rtrv-map:pca=255-001-000

   This is an example of the possible output.

   PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000               250 10  SOL *Y  *Y  grp01    ON
   255-001-000               251 10  SHR *Y  *Y  grp01    OFF
                253-001-002  254 10  SHR *Y  *Y  grp01    OFF
   255-001-000               252 10  SOL *Y  *Y  grp01    ON
   255-001-000               253 10  SHR *Y  *Y  grp01    OFF
                253-001-004  254 10  SHR *Y  *Y  grp01    OFF

   If the Flexible GTT Load Sharing feature is enabled, the MAPSET IDs for the mated applications are shown in the rtrv-map output.

   If the Weighted GTT Load Sharing feature is enabled and turned, the WT, %WT, and THR columns are shown in the rtrv-map output.

   If the point code is assigned to less than 12 different SSNs, then the existing point code in the rtrv-map output can be used to provision the mated application. Continue the procedure with 4.

   If the point code is assigned to 12 different SSNs, another existing point code in the rtrv-map output or a new point code must be used to provision the mated application. If an existing point code in the rtrv-map output will be used to provision the mated application, repeat this step for that point code. Then continue the procedure with 4.

   If a new point code will be used to provision the mated application, continue the procedure with 4.

   If the point code is assigned to 12 different SSNs, and neither an existing point code in the rtrv-map output nor a new point code will be used to provision the mated application, then this procedure cannot be performed.

   Note:

   If a concerned signaling point code (CSPC) group is not being assigned to the mated application, continue the procedure with 6.
4. Display the point codes in the CSPC group that you wish to assign to the mated application by first entering the rtrv-cspc command with no parameters.

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   grp01      ANSI                     6%
   grp02      ITU-I                    9%
   grp03      ITU-N                   12%
   grp04      ANSI                    15%
   grp05      ANSI                    15%
   grp10      ANSI                    15%
   grp15      ANSI                    15%

   If the desired CSPC group is shown in the rtrv-cspc output, re-enter the rtrv-cspc command with the CSPC group name. For this example, enter these commands.

   rtrv-cspc:grp=grp05

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp05         005-005-005
                 007-007-007
                 008-008-008
                 009-009-009

   rtrv-cspc:grp=grp10

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:59:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp10         003-003-003
                 004-004-004
                 008-008-008
                 009-009-009

   rtrv-cspc:grp=grp15

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp15         005-005-005
                 006-006-006
                 008-008-008
                 009-009-009

   Note:

   If the ANSI/ITU SCCP Conversion feature is enabled, then point codes of multiple network types can be displayed in the rtrv-cspc output, if point codes of multiple network types are assigned to the CSPC group.

   If the CSPC group is not in the database, or if the required point code is not assigned to the CSPC group, perform the Adding a Concerned Signaling Point Code procedure to add the required CSPC group or point code to the database.

   Note:

   If the output of the rtrv-cspc command performed in4 shows CSPC groups containing a mixture of point code types, or if the new CSPC group that was added in 4 contains a mixture of point code types, continue the procedure with 6.
5. The format of the point codes in the CSPC group specified with the grp parameter must be the same as the primary point code specified with the ent-map command only if the ANSI/ITU SCCP Conversion feature is not enabled.

   If the ANSI/ITU SCCP Conversion feature is enabled, the CSPC group may contain a mixture of point code types (refer to the Adding a Concerned Signaling Point Code procedure), and the network type of the CSPC group can be different from the network type of the primary point code of the mated application.

   Verify the status of the ANSI/ITU SCCP Conversion feature by entering this command.

   rtrv-ctrl-feat:partnum=893012001

   The following is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   SCCP Conversion           893012001  on      ----
   
   The following features have been temporarily enabled:
   
   Feature Name              Partnum    Status  Quantity     Trial Period Left
   Zero entries found.
   
   The following features have expired temporary keys:
   
   Feature Name              Partnum
   Zero entries found.

   If the ANSI/ITU SCCP Conversion feature is not enabled, perform the Activating the ANSI/ITU SCCP Conversion Feature procedure to enable the ANSI/ITU SCCP Conversion feature.

6. If the MAPSET column is shown in the rtrv-map output in 1, the Flexible GTT Load Sharing feature is enabled. Continue the procedure with 7.

   If the MAPSET column is not shown in 1 and you do not wish to provision MAP sets in this procedure, continue the procedure with 7.

   If the MAPSET column is not shown in 1 and you wish to provision MAP sets in this procedure, perform the Activating the Flexible GTT Load Sharing Feature procedure to enable the Flexible GTT Load Sharing feature. After the Flexible GTT Load Sharing feature is enabled, continue the procedure with 7.

   Note:

   If the EAGLE’s point code and subsystem number are being assigned to the mated application, continue the procedure with 11.
7. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.

   rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
   Extended Processing Time may be Required
   
      DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
      001-207-000   ----------- no  --- --------------   --------------   SS7
      001-001-001   ----------- no  --- --------------   --------------   SS7
      001-001-002   ----------- no  --- --------------   --------------   SS7
      001-005-000   ----------- no  --- --------------   --------------   SS7
      001-007-000   ----------- no  --- --------------   --------------   SS7
      008-012-003   ----------- no  --- --------------   --------------   SS7
      003-002-004   ----------- no  --- --------------   --------------   SS7
      009-002-003   ----------- no  --- --------------   --------------   SS7
      010-020-005   ----------- no  --- --------------   --------------   SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
      1-207-0       ----------- no  --- --------------   --------------   SS7
      0-015-0       ----------- no  --- --------------   --------------   SS7
      0-017-0       ----------- no  --- --------------   --------------   SS7
      1-011-1       ----------- no  --- --------------   --------------   SS7
      1-011-2       ----------- no  --- --------------   --------------   SS7
   
   
   Destination table is (14 of 2000) 1% full
   Alias table is (0 of 12000) 0% full
   PPC table is (1 of 20) 5% full

   If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

   After the new point code has been added, skip 8 through 10 and perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 14.

8. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

   rtrv-dstn:dpca=010-020-005

   This is an example of the possible output.

   rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
   
      DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
      010-020-005   ----------- no  --- --------------   --------------   SS7
   
      PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
      009-002-003  ---- no      50     on    20       no     no    none
   
   Destination table is (14 of 2000) 1% full
   Alias table is (0 of 12000) 0% full
   PPC table is (1 of 20) 5% full

   If the adjacent point code is not shown in the rtrv-dstn command output, the following output is displayed.

   rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0
   
   No destinations meeting the requested criteria were found
   
   Destination table is (14 of 2000) 1% full
   Alias table is (0 of 12000) 0% full
   PPC table is (1 of 20) 5% full

   A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

   After the new point code has been added, skip 9 through 10 and perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 14.

9. Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the ent-map command to verify whether or not the point code is the DPC of a route.

   For this example, enter these commands.

   rtrv-rte:dpca=006-006-006

   This is an example of the possible output.

   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      006-006-006 ---------- --------------   ls06       10    006-006-006
                                                  RTX:No  CLLI=ls06clli

   rtrv-rte:dpca=007-007-007

   This is an example of the possible output.

   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      007-007-007 ---------- --------------   ls03       10    007-007-007
                                              ls02       30    150-150-150
                                              lsa2       50    200-200-200
                                              lsa5       50    066-030-100
                                                  RTX:No  CLLI=ls03clli

   If the point code is not shown in the rtrv-rte output, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After this step is performed, continue the procedure with by performing one of these steps.

   • If the mrnset and MRN point code parameters will not be specified for the mated application, continue the procedure with 14.
   • If the mrnset and MRN point code parameters will not be specified for the mated application, continue the procedure by performing one of these steps.
     • If the MRNSET and MRNPC fields are shown in the rtrv-map output in 1, continue the procedure with 10.
     • If the MRNSET and MRNPC fields are not shown in the rtrv-map output in 1, the GTT Load Sharing with Alternate Routing Indicator feature is not enabled. Perform the Activating the GTT Load Sharing with Alternate Routing Indicator Feature procedure to enable the GTT Load Sharing with Alternate Routing Indicator feature. After the Activating the GTT Load Sharing with Alternate Routing Indicator Feature procedure has been performed, continue the procedure with 10.
10. The MRN point code value must be assigned to an MRN set. The MRN set must be shown in the rtrv-mrn output. Display the MRN sets by entering the rtrv-mrn command. This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
       MRNSET MAPSET  MAPPC          MAPSSN      PC             RC WT %WT THR
       DFLT   7       002-002-007        50      005-005-005    10 10  14   1
                                                 006-001-001    10 10  14   1
                                                 006-001-002    10 20  28   1
                                                 006-001-003    10 30  42   1
                                                 006-001-004    20 40  23   1
                                                 006-001-005    20 40  23   1
                                                 006-001-006    20 40  23   1
                                                 006-001-007    20 50  29   1
    
       MRNSET MAPSET  MAPPC          MAPSSN      PC             RC WT %WT THR
       1      -----   -----------       ---      007-007-007    10 10  14   1
                                                 008-001-001    10 10  14   1
                                                 008-001-002    10 20  28   1
                                                 008-001-003    10 30  42   1
                                                 008-001-004    20 40  23   1 
                                                 008-001-005    20 40  23   1
                                                 008-001-006    20 40  23   1
                                                 008-001-007    20 50  29   1
    
    MRN table is (16 of 5990) 1% full

    If any of the following items are not shown in the rtrv-mrn output, then the feature corresponding to these items is not enabled, or turned on if required.

    • The MRNSET field - the Flexible GTT Load Sharing feature is not enabled.
    • The MAPSET, MAPPC and MAPSSN fields - the GTT Load Sharing with Alternate Routing Indicator feature is not enabled.
    • The WT, %WT, THR columns - the Weighted GTT Load Sharing feature is not enabled and turned on.

    If the MRN set that you wish to use, containing the desired point code, is shown in the rtrv-mrn output, continue the procedure with 14.

    Note:

    The network type of the pc/pca/pci/pcn/pcn24 and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter values must be compatible, as shown in Provisioning a Solitary Mated Application.

    If the MRN set that you wish to use is not shown in the rtrv-mrn output, add the required MRN set by performing the Provisioning MRN Entries procedure.

    After the MRN set has been added, continue the procedure with 14.

11. Display the EAGLE self-identification, using the rtrv-sid command.

    The EAGLE’s true point code is shown in either the PCA, PCI, PCN, or PCN24 fields. This is an example of the possible output.

    rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
       PCA             PCI          PCN                CLLI              PCTYPE
       010-020-030     1-023-1      12-0-14-1          rlghncxa03w       OTHER
                     s-1-023-1    s-12-0-14-1
       CPCA
       001-001-001       002-002-003       002-002-004      002-002-005
       002-002-006       002-002-007       002-002-008      002-002-009
       004-002-001       004-003-003       050-060-070
       
       CPCI
       1-001-1           1-001-2           1-001-3          1-001-4
       1-002-1           1-002-2           1-002-3          1-002-4
       2-001-1           7-222-7
       
       CPCN
       2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
       2-2-3-3           2-2-4-0           10-14-10-1

12. Verify whether or not either the LNP, ATINPQ, or ANSI41 AIQ feature is enabled, or the EIR, INP, V-Flex, or ANSI-41 INP Query feature is enabled and turned on by entering the rtrv-ctrl-feat command.
    This list shows the entries that are displayed in the rtrv-ctrl-feat output for the features that are enabled, and turned on if required.

    • LNP TNs with a quantity greater than zero - the LNP feature is enabled.
    • EIR with the status on - the EIR feature is enabled and turned on.
    • VFLEX with the status on - the V-Flex feature is enabled and turned on.
    • ATINP - the ATINP feature is enabled.
    • INP with the status on - the INP feature is enabled and turned on.
    • ANSI-41 INP Query with the status on - the ANSI-41 INP Query feature is enabled and turned on.
    • ANSI41 AIQ - the ANSI41 AIQ feature is enabled.

    If the LNP, ATINPQ, or ANSI AIQ feature is enabled, or if the EIR, INP, V-Flex, or ANSI-41 INP Query feature is enabled and turned on, continue the procedure with 14.

13. Enable either the INP, ANSI-41 INP Query, EIR, V-Flex, ATINPQ, ANSI AIQ, or LNP features, depending on which subsystem you wish to use.

    To use the INP subsystem, enable and turn on either the INP or ANSI-41 INP Query feature, perform the procedures in INP/AINPQ User's Guide.

    To use the LNP subsystem, enable the LNP feature, perform the procedures in ELAP Administration and LNP Feature Activation User's Guide.

    To use the EIR subsystem, enable and turn on the EIR feature, perform the procedures in EIR User's Guide.

    To use the V-Flex subsystem, enable and turn on the V-Flex feature, perform the procedures in V-Flex User's Guide.

    To use the ATINPQ subsystem, enable the ATINP feature, perform the procedures in ATINP User's Guide.

    To use the AIQ subsystem, enable the ANSI AIQ feature, perform the procedures in Analyzed Information Features User's Guide.

    Note:

    If the LNP feature is enabled, the INP, ANSI-41 INP Query, V-Flex, ATINPQ, or EIR features cannot be enabled.
14. Add the mated application to the database using the ent-map command. Use Table 2-41 as a guide for the parameters and values that can be specified with the ent-map command.

    Table 2-41 Solitary Mated Application Parameter Combinations

    Other Subsystems	LNP Subsystem	INP Subsystem	EIR Subsystem
    Mandatory Parameters
    :pc/pca/pci/pcn/pcn24 (See Notes a, j, and n)	:pc/pca (See Note b)	:pcn/pcn24 (See Notes c and j)	:pci/pcn/pcn24 (See Notes d and j)
    :ssn= <subsystem number, 2 - 255>	:ssn=<LNP subsystem number, 2 - 255>	:ssn=<INP subsystem number, 2 - 255>	:ssn=<EIR subsystem number, 2 - 255>
    Optional Parameters
    :rc=<0 - 99> (See Note g)	:rc=<0 - 99> (See Note g)	:rc=<0 - 99> (See Note g)	:rc=<0 - 99> (See Note g)
    :grp=<CSPC group name> (See Note h)	:grp=<CSPC group name> (See Note h)	:grp=<CSPC group name> (See Note h)	:grp=<CSPC group name> (See Note h)
    :mrc=<yes, no> (See Note k)	:mrc=<yes, no> (See Note k)	:mrc=<yes, no> (See Note k)	:mrc=<yes, no> (See Note k)
    :mapset=<new, dflt> (See Note i)	:mapset=dflt (See Note i)	:mapset=dflt (See Note i)	:mapset=dflt (See Note i)
    :srm=<yes, no> (See Note k)	:srm=<yes, no> (See Note k)
    :sso=<on, off>
    :mrnset = <MRN set ID from thertrv-mrn output> (See Note l)
    :mrnpc/mrnpca/ mrnpci/mrnpcn/ mrnpcn24=<the point code value in the MRN set> (See Notes l and m)

    V-FLEX Subsystem	ATINPQ Subsystem	AIQ Subsystem
    Mandatory Parameters
    :pc/pca/pci/pcn/pcn24 (See Notes e and j)	:pc/pca/pci/pcn (See Notes f and j)	:pc/pca/pci/pcn/pcn24 (See Notes j and n)
    :ssn=<V-Flex subsystem number, 2 - 255>	:ssn=<ATINPQ subsystem number, 2 - 255>	:ssn=<AIQ subsystem number, 2 - 255>
    Optional Parameters
    :rc=<0 - 99> (See Note g)	:rc=<0 - 99> (See Note g)	:rc=<0 - 99> (See Note g)
    :grp=<CSPC group name> (See Note h)	:grp=<CSPC group name> (See Note h)	:grp=<CSPC group name> (See Note h)
    :mrc=<yes, no> (See Note k)	:mrc=<yes, no> (See Note k)	:mrc=<yes, no> (See Note k)
    :mapset=dflt (See Note i)	:mapset=dflt (See Note i)	:mapset=dflt (See Note i)
    :srm=<yes, no> (See Note k)	:srm=<yes, no> (See Note k)	:srm=<yes, no> (See Note k)

    Note:

    1. The primary point code is an ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 from the rtrv-rte or rtrv-map outputs.
    2. The primary point code for the LNP subsystem is the ANSI point code from the rtrv-sid output.
    3. The primary point code for the INP subsystem is the ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output.
    4. The primary point code for the EIR subsystem is the ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. Perform this step as necessary to provision an ITU-I and either a 14-bit ITU-N or a 24-bit ITU-N mated application containing the EIR subsystem.
    5. The primary point code for the V-Flex subsystem is the ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. Perform this step as necessary to provision an ANSI, ITU-I, and either a 14-bit ITU-N or a 24-bit ITU-N mated application containing the VFLEX subsystem.
    6. The primary point code for the ATINPQ subsystem is the ANSI, ITU-I, ITU-I spare, ITU-N, or ITU-N spare point code from the rtrv-sid output. Perform this step as necessary to provision an ANSI, ITU-I, and a 14-bit ITU-N mated application containing the ATINPQ subsystem.
    7. The rc parameter can be specified for a solitary mated application, but does not have to be specified. If the rc parameter is not specified, its value will be 10.
    8. The format of the point codes in the CSPC group specified with the grp parameter must be the same as the primary point code specified with the ent-map command only if the ANSI/ITU SCCP Conversion feature is not enabled. If the ANSI/ITU SCCP Conversion feature is enabled, the CSPC group may contain a mixture of point code types (refer to the Adding a Concerned Signaling Point Code procedure), and the network type of the CSPC group can be different from the network type of the primary point code of the mated application.
    9. If the Flexible GTT Load Sharing is enabled, the mapset parameter must be specified with the ent-map command.

       If the Flexible GTT Load Sharing is not enabled, themapset parameter cannot be specified with theent-map command.

       To provision entries in the default MAP set, themapset=dflt parameter must be specified with theent-map command.

       To provision entries in a new MAP set, themapset=new parameter must be specified with theent-map command. When theent-map command is executed with the mapset=new parameter, the new MAP set ID is automatically generated and displayed in the output of theent-map command as follows.

       New MAPSET Created : MAPSETID = <new MAP set ID>

       The default MAP set can contain multiple MAP groups. Each group in the default MAP set can contain a maximum of 128 point code and subsystem entries.

       The point code and subsystem entry can appear only once in the default MAP set, so the point code and subsystem entry can appear in only one MAP group in the default MAP set.

       The point code and subsystem entry provisioned in a MAP set can be provisioned in multiple MAP sets. If a point code and subsystem entry is provisioned in different MAP sets, the relative cost value of the entry in each MAP set can be different. All the point code and subsystem entries in a MAP set, including the default MAP set, must be different.

       If the EAGLE’s point code and subsystem number is being assigned to the mated application, and if the Flexible GTT Load Sharing feature is enabled, the EAGLE’s point code and subsystem number can be assigned only to the default MAP set using themapset=dflt parameter.

    10. If the point code selected from either the rtrv-rte or rtrv-map outputs is a 14-bit ITU-N point code, then the pcn parameter must be specified. If the point code selected from either the rtrv-rte or rtrv-map outputs is a 24-bit ITU-N point code, then the pcn24 parameters must be specified.
    11. The srm=yes parameter can be specified only for solitary mated applications containing ANSI point codes. The srm parameter affects traffic only on dominant and combined dominant/load shared mated applications. The mrc parameter can be specified for a solitary mated application, but this parameter affects only the traffic for a dominant mated application. These are the default values for the srm and mrc parameters.
        • ANSI mated applications - srm=yes, mrc=yes
        • ITU mated applications - srm=no (for all ITU mated applications), mrc=yes (for ITU-I and ITU-N mated applications), mrc=no (for ITU-N24 mated applications)
    12. If either the mrnset or mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter is specified, then both parameters must be specified. The mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameters can be specified only if the GTT Load Sharing with Alternate Routing Indicator feature is enabled. Refer to the Activating the GTT Load Sharing with Alternate Routing Indicator Feature procedure for information about enabling the GTT Load Sharing with Alternate Routing Indicator feature. The mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 values must be shown in the rtrv-mrn output.
    13. The network type of the pc/pca/pci/pcn/pcn24 and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter values must be compatible, as shown in Provisioning a Solitary Mated Application.
    14. The primary point code for the AIQ subsystem is the ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. Perform this step as necessary to provision an ANSI, ITU-I, and either a 14-bit ITU-N or a 24-bit ITU-N mated application containing the AIQ subsystem.

    If the Flexible GTT Load Sharing feature is not enabled for this example, enter these commands.

    ent-map:pca=006-006-006:ssn=250:grp=grp15:sso=off

    ent-map:pca=007-007-007:ssn=251:grp=grp05:sso=on

    When each of these commands have successfully completed, this message should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    ENT-MAP:  MASP A - COMPLTD

    If the Flexible GTT Load Sharing feature is enabled for this example, enter these commands.

    ent-map:pca=006-006-006:ssn=250:grp=grp15:sso=off:mapset=new

    ent-map:pca=007-007-007:ssn=251:grp=grp05:sso=on:mapset=dflt

    If the GTT Load Sharing with Alternate Routing Indicator feature is enabled for this example, enter these commands.

    ent-map:pca=006-006-006:ssn=250:grp=grp15:sso=off:mapset=new :mrnset=1:mrnpc=007-007-007

    If the Flexible GTT Load Sharing feature is enabled when each of these commands have successfully completed, and a new MAP set was created, a message similar to the following should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    New MAPSET Created : MAPSETID = 9
    ENT-MAP:  MASP A - COMPLTD

    If the Flexible GTT Load Sharing feature is enabled when each of these commands have successfully completed, and the mated application was added to the default MAP set, this message should appear.

    lghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    ENT-MAP:  MASP A - COMPLTD

    Note:

    If the Weighted GTT Load Sharing feature is enabled, shown by the columnsWT,%WT, andTHR in thertrv-map output, the parameterswt,mwt, andthr cannot be specified for a solitary mated application.
15. Verify the changes using the rtrv-map command with the primary point code and subsystem specified in 14.

    If the mapset=dflt parameter was specified in 14, the mapset=dflt parameter should be specified with the rtrv-map command.

    If a new MAP set was created in 14, the mapset parameter should be specified with the rtrv-map command. The value for the mapset parameter should be the MAP set ID generated in 14. If the mated application was added to an existing MAP set in 14, the mapset parameter and value specified in 14 should be specified with the rtrv-map command.

    If the Flexible GTT Load Sharing feature is not enabled for this example, enter these commands.

    rtrv-map:pca=006-006-006:ssn=250

    This is an example of the possible output.

    rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
    
    PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
    006-006-006                  250 10  SOL *Y  *Y  grp15    OFF
    
    MAP TABLE IS  (37 of 1024)  4 % FULL

    rtrv-map:pca=007-007-007:ssn=251

    This is an example of the possible output.

    rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
    
    PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
    007-007-007                  251 10  SOL *Y  *Y  grp05    ON
    
    MAP TABLE IS  (37 of 1024)  4 % FULL

    Note:

    If the Weighted GTT Load Sharing feature is enabled, theWT,%WT, andTHR columns are shown in thertrv-map output.

    If the Flexible GTT Load Sharing feature is enabled for this example, enter these commands.

    rtrv-map:pca=006-006-006:ssn=250:mapset=10

    This is an example of the possible output.

    rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
    
    MAPSET ID=10    MRNSET=1        MRNPC=007-007-007
    PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
    006-006-006                  250 10  SOL *Y  *Y  grp15    OFF
    
    MAP TABLE IS  (37 of 36000)  1 % FULL

    rtrv-map:pca=007-007-007:ssn=251:mapset=dflt

    This is an example of the possible output.

    rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
    
    MAPSET ID=DFLT  MRNSET=----     MRNPC=-----------
    PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
    007-007-007                  251 10  SOL *Y  *Y  grp05    ON
    
    MAP TABLE IS  (37 of 36000)  1 % FULL

    If the Weighted GTT Load Sharing feature is enabled, the WT, %WT, and THR columns are shown in the rtrv-map output.

    If the GTT Load Sharing with Alternate Routing Indicator feature is not enabled, the MRNSET and MRNPC fields are not shown in the rtrv-map output.

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

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

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

Figure 2-52 Provision a Solitary Mated Application - Sheet 1 of 11

Figure 2-53 Provision a Solitary Mated Application - Sheet 2 of 11

Figure 2-54 Provision a Solitary Mated Application - Sheet 3 of 11

Figure 2-55 Provision a Solitary Mated Application - Sheet 4 of 11

Figure 2-56 Provision a Solitary Mated Application - Sheet 5 of 11

Figure 2-57 Provision a Solitary Mated Application - Sheet 6 of 11

Figure 2-58 Provision a Solitary Mated Application - Sheet 7 of 11

Figure 2-59 Provision a Solitary Mated Application - Sheet 8 of 11

Figure 2-60 Provision a Solitary Mated Application - Sheet 9 of 11

Figure 2-61 Provision a Solitary Mated Application - Sheet 10 of 11

Figure 2-62 Provision a Solitary Mated Application - Sheet 11 of 11

New MAPSET Created : MAPSETID = <new MAP set ID>

1. Display the mated applications in the database using the rtrv-map command.

   This is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 250 10  SOL *Y  *Y  grp01    ON
   
   MAPSET ID=1
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 251 10  SHR *Y  *Y  grp01    OFF
                  253-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=2
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 252 10  SOL *Y  *Y  grp01    ON
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 253 10  SHR *Y  *Y  grp01    OFF
                  253-001-004  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=3
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-001                 255 10  DOM YES YES grp01    ON
                  253-001-005  254 20  DOM YES YES grp01    ON
   
   MAPSET ID=4
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-001                 250 10  DOM YES YES grp01    OFF
                  253-001-001  254 20  DOM YES YES grp01    OFF
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 251 10  SHR *Y  *Y  grp01    OFF
                  255-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   MAPSET ID=5
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 252 10  DOM YES YES grp01    ON
                  255-001-003  254 20  DOM YES YES grp01    ON
   
   MAPSET ID=6
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-002                 253 10  SHR *Y  *Y  grp01    ON
                  255-001-004  254 10  SHR *Y  *Y  grp01    ON
   
   MAPSET ID=7
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-007                  50 10  COM YES *Y  grp01    OFF
                  002-002-008   30 10  COM YES *Y  grp01    OFF
                  002-002-009   30 10  COM YES *Y  grp01    OFF
                  002-002-010   30 20  COM YES *Y  grp01    OFF
                  002-002-011   30 20  COM YES *Y  grp01    OFF
   
   MAPSET ID=8
   PCI            Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO
   2-001-2                     255 10  DOM NO  YES grp03    OFF
                  2-001-1      254 20  DOM NO  YES grp03    OFF
   
   MAPSET ID=9
   PCN            Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO
   00347                       253 10  SHR *N  *N  grp05    OFF
                  01387        254 10  SHR *N  *N  grp05    OFF
   
   MAP TABLE IS  (25 of 36000)  1 % FULL

   If any of the following items are not shown in the rtrv-map output, then the feature corresponding to these items is not enabled, or turned on if required.

   • The MAPSET field - the Flexible GTT Load Sharing feature is not enabled.
   • The MRNSET and MRNPC fields - the GTT Load Sharing with Alternate Routing Indicator feature is not enabled.
   • The WT, %WT, THR columns - the Weighted GTT Load Sharing feature is not enabled and turned on.

   If the maximum number of mated applications shown in the rtrv-map output in 1 is 1024, 2000, or 3000, continue the procedure with 3.

2. If the maximum number of mated applications shown in the rtrv-map output in 1 is 36000, the Flexible GTT Load Sharing feature is enabled.

   Although the rtrv-map output shows there can be 36000 entries, a maximum of 1024, 2000, or 3000 different point codes (depending on whether the XMAP Table Expansion feature is enabled for 2000 or 3000 mated applications) can be provisioned for mated applications. To verify the number of different point codes that can be provisioned for mated applications, enter the rtrv-tbl-capacity command. The following is an example of the possible output.

   
   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   
   MAP table is (3000 of 3000) 100% full
   

   Note:

   Thertrv-tbl-capacity command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-tbl-capacity command, see the rtrv-tbl-capacity command description in Commands User's Guide.
3. Continue the procedure by performing one of these steps.
   • If the rtrv-map output in 1 or the rtrv-tbl-capacity output in 2 shows that the maximum number of mated applications is 3000, and the current number of provisioned mated applications is 3000, no new point codes can be used to provision mated applications. Continue the procedure with 4.
   • If the rtrv-map output in 1 or the rtrv-tbl-capacity output in 2 shows that the maximum number of mated applications is either 1024 or 2000, and the mated application being added increases the number beyond 1024 or 2000, perform Enabling the XMAP Table Expansion Feature to enable a greater quantity of mated applications. After the quantity of mated applications has been increased, continue the procedure with 4. If the maximum number of mated applications is not increased, no new point codes can be used to provision mated applications.
   • If the rtrv-map output in 1 or the rtrv-tbl-capacity output in 2 shows that the maximum number of mated applications is either 1024, 2000, or 3000 and the mated application being added will not increase the number beyond the quantity shown in the rtrv-map output in 1 or the rtrv-tbl-capacity output in 2, continue the procedure with 4.
4. A MAP group, without the Flexible GTT Load Sharing feature enabled, a MAP set, other than the default MAP set, and a MAP group contained in the default MAP set can contain a maximum of 32 entries.

   Verify the number of entries that the MAP group or MAP set contains by entering the rtrv-map command with the primary point code and SSN assigned to the MAP group or MAP set. If the Flexible GTT Load Sharing feature is enabled, the mapset parameter and MAP set ID of the MAP set that the new mated application will be added to.

   If the specified MAP set is not the default MAP set, only the mapset parameter needs to be specified with the rtrv-map command. The point code and SSN does not need to be specified. For this example, enter one of these commands.

   rtrv-map:pca=002-002-007:ssn=50

   The following is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-007                  50 10  COM YES *Y  grp01    OFF
                  002-002-008   30 10  COM YES *Y  grp01    OFF
                  002-002-009   30 10  COM YES *Y  grp01    OFF
                  002-002-010   30 20  COM YES *Y  grp01    OFF
                  002-002-011   30 20  COM YES *Y  grp01    OFF
   
   MAP TABLE IS  (25 of 1024)  2 % FULL

   rtrv-map:pca=002-002-007:ssn=50:mapset=dflt

   The following is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   MAPSET ID=DFLT
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-007                  50 10  COM YES *Y  grp01    OFF
                  002-002-008   30 10  COM YES *Y  grp01    OFF
                  002-002-009   30 10  COM YES *Y  grp01    OFF
                  002-002-010   30 20  COM YES *Y  grp01    OFF
                  002-002-011   30 20  COM YES *Y  grp01    OFF
   
   MAP TABLE IS  (25 of 36000)  1 % FULL

   rtrv-map:mapset=7

   The following is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   MAPSET ID=7
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-007                  50 10  COM YES *Y  grp01    OFF
                  002-002-008   30 10  COM YES *Y  grp01    OFF
                  002-002-009   30 10  COM YES *Y  grp01    OFF
                  002-002-010   30 20  COM YES *Y  grp01    OFF
                  002-002-011   30 20  COM YES *Y  grp01    OFF
   
   MAP TABLE IS  (25 of 36000)  1 % FULL

   If the MAP group or MAP set contains 32 entries, no more entries can be added to the specified MAP group or MAP set. One of these actions can be performed.

   • Entries can be added another MAP group or MAP set. Repeat this step for the other MAP group or MAP set.
   • Entries can be removed from the specified MAP group or MAP set. To remove entries from the specified MAP group or MAP set, perform Removing a Mated Application.
   • Entries can be added to a new MAP group or MAP set.

     Note:

     If none of these actions will be performed, then this procedure cannot be performed.

   If the MAP group or MAP set contains less than 32 entries, entries can be added to the MAP group or MAP set.

   After it has been determined which MAP group or MAP set that the new entries will be added to (a new MAP group or MAP set or an existing MAP group or MAP set), continue the procedure by performing one of these steps.

   • If an existing point code is being added to this MAP group or MAP set, continue the procedure with 5.
   • If a new point code is being added to this MAP group or MAP set, continue the procedure by performing one of these steps.
     • If a concerned signaling point code (CSPC) group is not being assigned to the mated application, continue the procedure with 8. If the mated point code is not assigned to a CSPC group, that point code will not be notified of the subsystem’s status.
     • If a concerned signaling point code (CSPC) group will be assigned to the mated application, continue the procedure with 6.
5. A mated application can be provisioned with a point code that is assigned to other mated applications as long as the SSN is not assigned to other mated applications.

   A point code can be assigned to maximum of 12 different SSNs. Verify the number of SSNs assigned to the point code that will be specified for the mated application in this procedure by entering the rtrv-map command with the point code of the new mated application. For this example, enter this command.

   rtrv-map:pca=255-001-000

   This is an example of the possible output.

   rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0
   
   PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   255-001-000                 250 10  SOL *Y  *Y  grp01    ON
   
   255-001-000                 251 10  SHR *Y  *Y  grp01    OFF
                  253-001-002  254 10  SHR *Y  *Y  grp01    OFF
   
   255-001-000                 252 10  SOL *Y  *Y  grp01    ON
   
   255-001-000                 253 10  SHR *Y  *Y  grp01    OFF
                  253-001-004  254 10  SHR *Y  *Y  grp01    OFF
   
   MAP TABLE IS  (25 of 1024)  2 % FULL

   If the Flexible GTT Load Sharing feature is enabled, the MAPSET IDs for the mated applications are shown in the rtrv-map output.

   If the Weighted GTT Load Sharing feature is enabled and turned on, the WT, %WT, and THR columns are shown in the rtrv-map output.

   If the point code is assigned to 12 different SSNs, and neither an existing point code in the rtrv-map output nor a new point code will be used to provision the mated application, then this procedure cannot be performed.

   If the point code is assigned to less than 12 different SSNs, then the existing point code in the rtrv-map output can be used to provision the mated application.

   If the point code is assigned to 12 different SSNs, another existing point code in the rtrv-map output or a new point code must be used to provision the mated application. If an existing point code in the rtrv-map output will be used to provision the mated application, repeat this step for that point code.

   After it has been determined which point code will be used to provision the mated application (a new point code or an existing point code), continue the procedure by performing one of these steps.

   • If a concerned signaling point code (CSPC) group is not being assigned to the mated application, continue the procedure with 8. If the mated point code is not assigned to a CSPC group, that point code will not be notified of the subsystem’s status.
   • If a concerned signaling point code (CSPC) group will be assigned to the mated application, continue the procedure with 6.
6. Display the point codes in the CSPC group that you wish to assign to the mated application by first entering the rtrv-cspc command with no parameters.

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   grp01      ANSI                     6%
   grp02      ITU-I                    9%
   grp03      ITU-N                   12%
   grp04      ANSI                    15%
   grp05      ANSI                    15%
   grp10      ANSI                    15%
   grp15      ANSI                    15%

   If the desired CSPC group is shown in the rtrv-cspc output, re-enter the rtrv-cspc command with the CSPC group name. For this example, enter these commands.

   rtrv-cspc:grp=grp05

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp05         005-005-005
                 007-007-007
                 008-008-008
                 009-009-009

   rtrv-cspc:grp=grp10

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:59:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp10         003-003-003
                 004-004-004
                 008-008-008
                 009-009-009

   rtrv-cspc:grp=grp15

   This is an example of the possible output.

   rlghncxa03w 07-05-25 09:48:31  GMT  EAGLE5 37.0.0
   CSPC GRP      PCA
   grp15         005-005-005
                 006-006-006
                 008-008-008
                 009-009-009

   Note:

   If the ANSI/ITU SCCP Conversion feature is enabled, then point codes of multiple network types can be displayed in thertrv-cspc output, if point codes of multiple network types are assigned to the CSPC group.

   If the CSPC group is not in the database, or if the required point code is not assigned to the CSPC group, perform the Adding a Concerned Signaling Point Code procedure to add the required CSPC group or point code to the database.

   Note:

   If the output of thertrv-cspc command performed in6shows CSPC groups containing a mixture of point code types, or if the new CSPC group that was added in6contains a mixture of point code types, continue the procedure with8.
7. The format of the point codes in the CSPC group specified with the grp parameter must be the same as the primary point code specified with the ent-map command only if the ANSI/ITU SCCP Conversion feature is not enabled.

   If the ANSI/ITU SCCP Conversion feature is enabled, the CSPC group may contain a mixture of point code types (refer to the Adding a Concerned Signaling Point Code procedure), and the network type of the CSPC group can be different from the network type of the primary point code of the mated application.

   Verify the status of the ANSI/ITU SCCP Conversion feature by entering this command.

   rtrv-ctrl-feat:partnum=893012001

   The following is an example of the possible output.

   rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   SCCP Conversion           893012001  on      ----
   
   The following features have been temporarily enabled:
   
   Feature Name              Partnum    Status  Quantity     Trial Period Left
   Zero entries found.
   
   The following features have expired temporary keys:
   
   Feature Name              Partnum
   Zero entries found.

   If the ANSI/ITU SCCP Conversion feature is not enabled, perform the Activating the ANSI/ITU SCCP Conversion Feature procedure to enable the ANSI/ITU SCCP Conversion feature.

8. If the MAPSET column is shown in the rtrv-map output in 1, the Flexible GTT Load Sharing feature is enabled. Continue the procedure with 9.

   If the MAPSET column is not shown in 1 and you do not wish to provision MAP sets in this procedure, continue the procedure with 9.

   If the MAPSET column is not shown in 1 and you wish to provision MAP sets in this procedure, perform the Activating the Flexible GTT Load Sharing Feature procedure to enable the Flexible GTT Load Sharing feature. After the Flexible GTT Load Sharing feature is enabled, continue the procedure with 9.

   Note:

   If thesso parameter will be specified for the mated application, continue the procedure with10. The EAGLE’s point code and LNP, EIR, V-Flex, ATINPQ, or INP subsystem cannot be assigned to a mated application using thesso parameter.
9. Display the EAGLE self-identification, using the rtrv-sid command.

   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
      PCA             PCI          PCN                CLLI              PCTYPE
      010-020-030     1-023-1      12-0-14-1          rlghncxa03w       OTHER
                    s-1-023-1    s-12-0-14-1
      CPCA
      001-001-001       002-002-003       002-002-004      002-002-005
      002-002-006       002-002-007       002-002-008      002-002-009
      004-002-001       004-003-003       050-060-070
      
      CPCI
      1-001-1           1-001-2           1-001-3          1-001-4
      1-002-1           1-002-2           1-002-3          1-002-4
      2-001-1           7-222-7
      
      CPCN
      2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
      2-2-3-3           2-2-4-0           10-14-10-1

   The EAGLE’s true point code is shown in either the PCA, PCI, PCN, or PCN24 fields. This is an example of the possible output.

   If the both point codes that will be specified for the mated application are point codes assigned to other mated applications, continue the procedure by performing one of these steps.

   • If the mrnset and mrnpc parameters will be specified for the mated application, continue the procedure with 15.
   • If the mrnset and mrnpc parameters will not be specified for the mated application, continue the procedure by performing one of these steps.
     • If a new mated application is being added, continue the procedure with 16.
     • If an entry is being added to an existing mated application, continue the procedure with 17.

   If the EAGLE’s point code will be specified for the mated application, and its mated point code is assigned to other mated applications, continue the procedure with 13.

   If only one of the point codes that will be specified for the mated application is assigned to other mated applications, perform 10 for the new point code that is not assigned to other mated applications.

10. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.

    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    Extended Processing Time may be Required
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       001-207-000   ----------- no  --- --------------   --------------   SS7
       001-001-001   ----------- no  --- --------------   --------------   SS7
       001-001-002   ----------- no  --- --------------   --------------   SS7
       001-005-000   ----------- no  --- --------------   --------------   SS7
       001-007-000   ----------- no  --- --------------   --------------   SS7
       008-012-003   ----------- no  --- --------------   --------------   SS7
       003-002-004   ----------- no  --- --------------   --------------   SS7
       009-002-003   ----------- no  --- --------------   --------------   SS7
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
       1-207-0       ----------- no  --- --------------   --------------   SS7
       0-015-0       ----------- no  --- --------------   --------------   SS7
       0-017-0       ----------- no  --- --------------   --------------   SS7
       1-011-1       ----------- no  --- --------------   --------------   SS7
       1-011-2       ----------- no  --- --------------   --------------   SS7
    
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, skip 11 through 14 and perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure by performing one of these steps.

    • If the mrnset and mrnpc parameters will be specified for the mated application, continue the procedure with 15.
    • If the mrnset and mrnpc parameters will not be specified for the mated application, continue the procedure by performing one of these steps.
      • If a new mated application is being added, continue the procedure with 16.
      • If an entry is being added to an existing mated application, continue the procedure with 17.
11. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output.

    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       009-002-003  ---- no      50     on    20       no     no    none
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    If the point code is not shown in the rtrv-dstn command output, the following output is displayed.

    rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0
    
    No destinations meeting the requested criteria were found
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    If the point code is not shown in the rtrv-dstn output, perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the point code to the destination point code table.

    After the new point code has been added, skip 12 through 14 and perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure by performing one of these steps.

    • If the mrnset and mrnpc parameters will be specified for the mated application, continue the procedure with 15.
    • If the mrnset and mrnpc parameters will not be specified for the mated application, continue the procedure by performing one of these steps.
      • If a new mated application is being added, continue the procedure with 16.
      • If an entry is being added to an existing mated application, continue the procedure with 17.
12. Enter the rtrv-rte command with the dpc parameter specifying the point codes to be used with the ent-map or chg-map commands to verify whether or not the point code is the DPC of a route.

    For this example, enter these commands.

    rtrv-rte:dpca=003-003-003

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       003-003-003 ---------- --------------   ls03       10    003-003-003
                                                   RTX:No  CLLI=ls07clli

    rtrv-rte:dpca=005-005-005

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       005-005-005 ---------- --------------   ls05       10    005-005-005
                                               ls15       30    089-047-123
                                               lsa8       50    077-056-000
                                                   RTX:No  CLLI=ls05clli

    rtrv-rte:dpca=008-008-008

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       008-008-008 ---------- --------------   ls20       10    008-008-008
                                                   RTX:No  CLLI=ls20clli

    rtrv-rte:dpca=031-049-100

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       031-049-100 ---------- --------------   ls10       10    031-049-100
                                                   RTX:No  CLLI=ls10clli

    rtrv-rte:dpca=040-040-040

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       040-040-040 ---------- --------------   ls11       10    040-040-040
                                                   RTX:No  CLLI=ls11clli

    rtrv-rte:dpca=056-113-200

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       056-113-200 ---------- --------------   ls12       10    056-113-200
                                                   RTX:No  CLLI=ls12clli

    rtrv-rte:dpca=060-060-060

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       060-060-060 ---------- --------------   ls13       10    060-060-060
                                                   RTX:No  CLLI=ls13clli

    rtrv-rte:dpca=070-070-070

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       070-070-070 ----------   --------------   ls15       10    070-070-070
                                                   RTX:No  CLLI=ls15clli

    rtrv-rte:dpca=179-183-050

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       179-183-050 ---------- --------------   ls18       10    179-183-050
                                                   RTX:No  CLLI=ls18clli

    If the point code is not shown in the rtrv-rte output, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database.

    If the EAGLE’s point code will not be specified for the mated application, continue the procedure by performing one of these steps.

    • If the mrnset and mrnpc parameters will be specified for the mated application, continue the procedure with 15.
    • If the mrnset and mrnpc parameters will not be specified for the mated application, continue the procedure by performing one of these steps.
      • If a new mated application is being added, continue the procedure with 16.
      • If an entry is being added to an existing mated application, continue the procedure with 17.

    If the EAGLE’s point code will be specified for the mated application, continue the procedure with 13.

13. Verify whether or not either the LNP, ATINPQ, or ANSI41 AIQ feature is enabled, or the EIR, INP, V-Flex, or ANSI-41 INP Query feature is enabled and turned on by entering the rtrv-ctrl-feat command.
    This list shows the entries that are displayed in the rtrv-ctrl-feat output for the features that are enabled, and turned on if required.

    • LNP TNs with a quantity greater than zero - the LNP feature is enabled.
    • EIR with the status on - the EIR feature is enabled and turned on.
    • VFLEX with the status on - the V-Flex feature is enabled and turned on.
    • ATINP - the ATINP feature is enabled
    • INP with the status on - the INP feature is enabled and turned on
    • ANSI-41 INP Query with the status on - the ANSI-41 INP Query feature is enabled and turned on.
    • ANSI41 AIQ - the ANSI41 AIQ feature is enabled.

    Continue the procedure by performing one of these steps.

    • If the LNP, ATINPQ, or ANSI41 AIQ feature is enabled, or if the EIR, INP, V-Flex, or ANSI-41 INP Query feature is enabled and turned on, continue the procedure with 16.
    • If the LNP, ATINPQ, or ANSI41 AIQ feature is not enabled, or if the EIR, INP, V-Flex, or ANSI-41 INP Query feature is not enabled or turned on, continue the procedure with 14.
14. Enable either the INP, ANSI-41 INP Query, EIR, V-Flex, ATINPQ, ANSI41 AIQ, or LNP features, depending on which subsystem you wish to use.

    To use the INP subsystem, enable and turn on either the INP or ANSI-41 INP Query feature by performing the procedures in INP/AINPQ User's Guide.

    To use the LNP subsystem, enable the LNP feature by performing the procedures in ELAP Administration and LNP Feature Activation User's Guide.

    To use the EIR subsystem, enable and turn on the EIR feature by performing the procedures in EIR User's Guide.

    To use the V-Flex subsystem, enable and turn on the V-Flex feature, perform the procedures in V-Flex User's Guide.

    To use the ATINPQ subsystem, enable the ATINP feature, perform the procedures in ATINP User's Guide.

    To use the AIQ subsystem, enable the ANSI AIQ feature, perform the procedures in Analyzed Information Features User's Guide.

    Note:

    If the LNP feature is enabled, the INP, ANSI-41 INP Query, V-Flex, ATINPQ, or EIR features cannot be enabled.
15. The MRN point code value must be assigned to an MRN set. The MRN set must be shown in the rtrv-mrn output. Display the MRN sets by entering the rtrv-mrn command. This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
       MRNSET MAPSET  MAPPC          MAPSSN      PC             RC WT %WT THR
       DFLT   7       002-002-007        50      005-005-005    10 10  14   1
                                                 006-001-001    10 10  14   1
                                                 006-001-002    10 20  28   1
                                                 006-001-003    10 30  42   1
                                                 006-001-004    20 40  23   1
                                                 006-001-005    20 40  23   1
                                                 006-001-006    20 40  23   1
                                                 006-001-007    20 50  29   1
    
       MRNSET MAPSET  MAPPC          MAPSSN      PC             RC WT %WT THR
       1      -----   -----------       ---      007-007-007    10 10  14   1
                                                 008-001-001    10 10  14   1
                                                 008-001-002    10 20  28   1
                                                 008-001-003    10 30  42   1
                                                 008-001-004    20 40  23   1 
                                                 008-001-005    20 40  23   1
                                                 008-001-006    20 40  23   1
                                                 008-001-007    20 50  29   1
    
    MRN table is (16 of 5990) 1% full

    If any of the following items are not shown in the rtrv-mrn output, then the feature corresponding to these items is not enabled, or turned on if required.

    • The MRNSET field - the Flexible GTT Load Sharing feature is not enabled.
    • The MAPSET, MAPPC and MAPSSN fields - the GTT Load Sharing with Alternate Routing Indicator feature is not enabled.
    • The WT, %WT, THR columns - the Weighted GTT Load Sharing feature is not enabled and turned on.

    Note:

    The network type of thepc/pca/pci/pcn/pcn24 andmrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter values must be compatible, as shown inTable 2-42

    If the MRN set that you wish to use, containing the desired point code, is not shown in the rtrv-mrn output, add the required MRN set by performing the Provisioning MRN Entries procedure.

    If the MRN set that you wish to use is shown in the rtrv-mrn output, or Provisioning MRN Entries was performed in this step, continue the procedure by performing one of these steps.

    • If a new mated application is being added, continue the procedure with 16.
    • If an entry is being added to an existing mated application, continue the procedure with 17.
16. Add the mated application to the database using the ent-map command. Use Table 2-44 as a guide for the parameters and values that can be specified with the ent-map command.

    Table 2-44 Dominant Mated Application Parameter Combinations for the ENT-MAP Command

    Other Subsystems	LNP Subsystem	INP Subsystem	EIR Subsystem
    Mandatory Parameters
    :pc/pca/pci/pcn/pcn24 (See Notes 1, 11, and 14)	:pc/pca (See Note 2)	:pcn/pcn24 (See Note 3)	:pci/pcn/pcn24 (See Note 4)
    :ssn= <subsystem number, 2 - 255>	:ssn=<LNP subsystem number, 2 - 255>	:ssn=<INP subsystem number, 2 - 255>	:ssn=<EIR subsystem number, 2 - 255>
    :rc=<0 - 99> (See Note 7)	:rc=<0 - 99> (See Note 7)	:rc=<0 - 99> (See Note 7)	:rc=<0 - 99> (See Note 7)
    :mpc/mpca/mpci/ mpcn/mpcn24 (See Notes 1, 9, 11, and 14)	:mpc/mpca (See Note 2)	:mpcn/mpcn24 (See Notes 3 and 11)	:mpci/mpcn/mpcn24 (See Notes 4 and 11)
    :mssn= <subsystem number of the mate, 2 - 255>	:mssn= <subsystem number of the mate, 2 - 255>	:mssn= <subsystem number of the mate, 2 - 255>	:mssn= <subsystem number of the mate, 2 - 255>
    :materc=<0 - 99> (See Note 7)	:materc=<0 - 99> (See Note 7)	:materc=<0 - 99> (See Note 7)	:materc=<0 - 99> (See Note 7)
    Optional Parameters
    :grp=<CSPC group name> (See Note 8)	:grp=<CSPC group name> (See Note 8)	:grp=<CSPC group name> (See Note 8)	:grp=<CSPC group name> (See Note 8)
    :mrc=<yes, no> (See Note 12)	:mrc=<yes, no> (See Note 12)	:mrc=<yes, no> (See Note 12)	:mrc=<yes, no> (See Note 12)
    :mapset=<new, dflt> (See Note 10)	:mapset=dflt (See Note 10)	:mapset=dflt (See Note 10)	:mapset=dflt (See Note 10)
    :srm=<yes, no> (See Note 12)	:srm=<yes, no> (See Note 12)
    :sso=<on, off>
    :mrnset = <MRN set ID from thertrv-mrn output> (See Note 13)
    :mrnpc/mrnpca/ mrnpci/mrnpcn/ mrnpcn24=<the point code value in the MRN set> (See Notes 13 and 14)

    V-FLEX Subsystem	ATINPQ Subsystem	AIQ Subsystem
    Mandatory Parameters
    :pc/pca/pci/pcn/pcn24 (See Note 5)	:pc/pca/pci/pcn (See Note 6)	:pc/pca/pci/pcn/pcn24 (See Note 15)
    :ssn=<V-Flex subsystem number, 2 - 255>	:ssn=<V-Flex subsystem number, 2 - 255>	:ssn=<V-Flex subsystem number, 2 - 255>
    :rc=<0 - 99> (See Note 7)	:rc=<0 - 99> (See Note 7)	:rc=<0 - 99> (See Note 7)
    :mpc/mpca/mpci/ mpcn/mpcn24 (See Notes 5 and 11)	:mpc/mpca/mpci/mpcn (See Notes 6 and 11)	:mpc/mpca/mpci/ mpcn/mpcn24 (See Notes 11 and 15)
    :mssn= <subsystem number of the mate, 2 - 255>	:mssn= <subsystem number of the mate, 2 - 255>	:mssn= <subsystem number of the mate, 2 - 255>
    :materc=<0 - 99> (See Note 7)	:materc=<0 - 99> (See Note 7)	:materc=<0 - 99> (See Note 7)
    Optional Parameters
    :grp=<CSPC group name> (See Note 8)	:grp=<CSPC group name> (See Note 8)	:grp=<CSPC group name> (See Note 8)
    :mrc=<yes, no> (See Note 12)	:mrc=<yes, no> (See Note 12)	:mrc=<yes, no> (See Note 12)
    :mapset=dflt (See Note 10)	:mapset=dflt (See Note 10)	:mapset=dflt (See Note 10)
    :srm=<yes, no> (See Note 12)	:srm=<yes, no> (See Note 12)	:srm=<yes, no> (See Note 12)
    Notes The primary point code is an ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 from the rtrv-rte or rtrv-map outputs. The mate point code is an ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-rte or rtrv-map outputs. The primary point code for the LNP subsystem is the ANSI point code from the rtrv-sid output. The mate point code is an ANSI point code from the rtrv-rte or rtrv-map outputs. The primary point code for the INP subsystem is the ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. The mate point code is an ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-rte or rtrv-map outputs. The primary point code for the EIR subsystem is the ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. The mate point code is an ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-rte or rtrv-map outputs. The primary point code for the V-Flex subsystem is the ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. The mate point code is an ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-rte or rtrv-map outputs. The primary point code for the ATINPQ subsystem is the ANSI, ITU-I, ITU-I spare, ITU-N, or ITU-N spare point code from the rtrv-sid output. The mate point code is an ANSI, ITU-I, ITU-I spare, ITU-N, or ITU-N spare point code from the rtrv-rte or rtrv-map outputs. The materc parameter value must be greater than the rc parameter value. The format of the point codes in the CSPC group specified with the grp parameter must be the same as the primary point code specified with the ent-map command only if the ANSI/ITU SCCP Conversion feature is not enabled. If the ANSI/ITU SCCP Conversion feature is enabled, the CSPC group may contain a mixture of point code types (refer to the Adding a Concerned Signaling Point Code procedure), and the network type of the CSPC group can be different from the network type of the primary point code of the mated application. For mated applications containing ANSI or 24-bit ITU-N point codes, or the EAGLE's true point code, the format of the point codes specified in the ent-map command must be the same. For example, if the primary point code is a 24-bit ITU-N point code (pcn24), the mate point code must be a 24-bit ITU-N point code (mpcn24). The mate point codes of mated applications containing either ITU-I, ITU-I spare, 14-bit ITU-N, or 14-bit ITU-N spare primary point codes do not have to be the same format as the primary point code. The mate point codes of these mated applications can be a mixture of ITU-I, ITU-I spare, 14-bit ITU-N, or 14-bit ITU-N spare point codes. If the Flexible GTT Load Sharing is enabled, the mapset parameter must be specified with the ent-map command. If the Flexible GTT Load Sharing is not enabled, themapset parameter cannot be specified with theent-map command. To provision entries in the default MAP set, themapset=dflt parameter must be specified with theent-map command. To provision entries in a new MAP set, themapset=new parameter must be specified with theent-map command. Themapset=new parameter can be specified only with theent-map command. When theent-map command is executed with the mapset=new parameter, the new MAP set ID is automatically generated and displayed in the output of theent-map command as follows. New MAPSET Created : MAPSETID = <new MAP set ID> A MAP set, other than the default MAP set, is a MAP group provisioned with the MAP set ID and can contain a maximum of 32 point code and subsystem entries. The default MAP set can contain multiple MAP groups. Each group in the default MAP set can contain a maximum of 32 point code and subsystem entries. The point code and subsystem entry can appear only once in the default MAP set, so the point code and subsystem entry can appear in only one MAP group in the default MAP set. The point code and subsystem entry provisioned in a MAP set can be provisioned in multiple MAP sets. If a point code and subsystem entry is provisioned in different MAP sets, the relative cost value of the entry in each MAP set can be different. All the point code and subsystem entries in a MAP set, including the default MAP set, must be different. If the point code selected from either the rtrv-rte or rtrv-map outputs is a 14-bit ITU-N point code, then the pcn/mpcn parameters must be specified. If the point code selected from either the rtrv-rte or rtrv-map outputs is a 24-bit ITU-N point code, then the pcn24/mpcn24 parameters must be specified. The srm=yes parameter can be specified only for mated applications containing ANSI point codes. These are the default values for the srm and mrc parameters. ANSI mated applications - srm=yes, mrc=yes ITU mated applications - srm=no, mrc=no The mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameters can be specified only if the GTT Load Sharing with Alternate Routing Indicator feature is enabled. Refer to the Activating the GTT Load Sharing with Alternate Routing Indicator Feature procedure for information about enabling the GTT Load Sharing with Alternate Routing Indicator feature. The mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 values must be shown in the rtrv-mrn output. The network type of the pc/pca/pci/pcn/pcn24 and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter values must be compatible, as shown in Table 2-42. The primary point code for the AIQ subsystem is the ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-sid output. The mate point code is an ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-rte or rtrv-map outputs.

    If the Flexible GTT Load Sharing feature is not enabled for this example, enter these commands.

    ent-map:pca=003-003-003:ssn=254:rc=10:mpc=040-040-040:mssn=254 :materc=20:grp=grp10:mrc=yes:srm=yes:sso=on

    ent-map:pca=005-005-005:ssn=250:rc=10:mpc=060-060-060:mssn=250 :materc=20:grp=grp15:mrc=yes:srm=yes:sso=off

    ent-map:pci=5-005-5:ssn=50:rc=10:mpcn=0257:mssn=50:materc=20 :grp=grp20:mrc=yes:sso=off

    When each of these commands have successfully completed, this message should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    ENT-MAP:  MASP A - COMPLTD

    If the Flexible GTT Load Sharing feature is enabled for this example, enter these commands.

    ent-map:pca=003-003-003:ssn=254:rc=10:mpc=040-040-040:mssn=254 :materc=20:grp=grp10:mrc=yes:srm=yes:sso=on:mapset=new

    ent-map:pca=005-005-005:ssn=250:rc=10:mpc=060-060-060:mssn=250 :materc=20:grp=grp15:mrc=yes:srm=yes:sso=off:mapset=dflt

    ent-map:pci=5-005-5:ssn=50:rc=10:mpcn=0257:mssn=50:materc=20 :grp=grp20:mrc=yes:sso=off:mapset=new

    If the GTT Load Sharing with Alternate Routing Indicator feature is enabled for this example, enter these commands.

    ent-map:pca=003-003-003:ssn=254:rc=10:mpc=040-040-040:mssn=254 :materc=20:grp=grp10:mrc=yes:srm=yes:sso=on:mapset=new:mrnset=dflt :mrnpc= 005-005-005

    ent-map:pca=005-005-005:ssn=250:rc=10:mpc=060-060-060:mssn=250 :materc=20:grp=grp15:mrc=yes:srm=yes:sso=off:mapset=dflt:mrnset=1 :mrnpc= 007-007-007

    If the Flexible GTT Load Sharing feature is enabled when each of these commands have successfully completed, and a new MAP set was created, a message similar to the following should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    New MAPSET Created : MAPSETID = 9
    ENT-MAP:  MASP A - COMPLTD

    If the Flexible GTT Load Sharing feature is enabled when each of these commands have successfully completed, and the mated application was added to the default MAP set, this message should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    ENT-MAP:  MASP A - COMPLTD

    If no other entries are being added to the mated application, or if the EAGLE's true point code was specified for the mated application, continue the procedure with 18.

    If other entries are being added to the mated application, continue the procedure with 17.

17. Add the mated point code and subsystem to the mated application using the chg-map command. Use Table 2-45 as a guide for the parameters and values that can be specified with the chg-map command.

    Table 2-45 Dominant Mated Application Parameter Combinations for the CHG-MAP Command

    Mandatory Parameters

    :pc/pca/pci/pcn/pcn24=<ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 primary point code that the mate point code will be assigned to> (See Notes 4 and 8)

    :ssn=<subsystem number assigned to the primary point code>

    :mpc/mpca/mpci/mpcn/mpcn24=<ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code of the mate from the rtrv-rte or rtrv-map outputs> (See Notes 2, 4, and 8)

    :mssn=<subsystem number of the mate, 2 - 255>

    :materc=<0 - 99> Thematerc parameter value must be greater than therc parameter value.

    Optional Parameters

    :grp=<CSPC group name> (See Notes 1 and 6)

    :sso=<on, off> (See Note 6)

    :srm=<yes, no> (See Notes 5 and 6)

    :mrc=<yes, no> (See Note 6)

    :mapset=<dflt or the number of an existing MAP set> (See Note 3)

    :mrnset = <MRN set ID from thertrv-mrn output> (See Note 7)

    :mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24=<the point code value in the MRN set> (See Notes 7 and 8)

    Notes The format of the point codes in the CSPC group specified with the grp parameter must be the same as the primary point code specified with the chg-map command only if the ANSI/ITU SCCP Conversion feature is not enabled. If the ANSI/ITU SCCP Conversion feature is enabled, the CSPC group may contain a mixture of point code types (refer to the Adding a Concerned Signaling Point Code procedure), and the network type of the CSPC group can be different from the network type of the primary point code of the mated application. For mated applications containing ANSI or 24-bit ITU-N point codes, or the EAGLE's true point code, the format of the point codes specified in the chg-map command must be the same. For example, if the primary point code is a 24-bit ITU-N point code (pcn24), the mate point code must be a 24-bit ITU-N point code (mpcn24). The mate point codes of mated applications containing either ITU-I, ITU-I spare, 14-bit ITU-N, or 14-bit ITU-N spare primary point codes do not have to be the same format as the primary point code. The mate point codes of these mated applications can be a mixture of ITU-I, ITU-I spare, 14-bit ITU-N, or 14-bit ITU-N spare point codes. If the Flexible GTT Load Sharing is enabled, the mapset parameter must be specified with the chg-map command. If the Flexible GTT Load Sharing is not enabled, themapset parameter cannot be specified with thechg-map command. To provision entries in the default MAP set, themapset=dflt parameter must be specified with thechg-map command. To provision entries in an existing MAP set, themapset parameter must be specified with the MAP set ID value of that MAP set. A MAP set, other than the default MAP set, is a MAP group provisioned with the MAP set ID and can contain a maximum of 32 point code and subsystem entries. The default MAP set can contain multiple MAP groups. Each group in the default MAP set can contain a maximum of 32 point code and subsystem entries. The point code and subsystem entry can appear only once in the default MAP set, so the point code and subsystem entry can appear in only one MAP group in the default MAP set. The point code and subsystem entry provisioned in a MAP set can be provisioned in multiple MAP sets. If a point code and subsystem entry is provisioned in different MAP sets, the relative cost value of the entry in each MAP set can be different. All the point code and subsystem entries in a MAP set, including the default MAP set, must be different. If the point code selected from either the rtrv-rte or rtrv-map outputs is a 14-bit ITU-N point code, then the pcn/mpcn parameters must be specified. If the point code selected from either the rtrv-rte or rtrv-map outputs is a 24-bit ITU-N point code, then the pcn24/mpcn24 parameters must be specified. The srm=yes parameter can be specified only for mated applications containing ANSI point codes. When the CSPC group name (grp), mrc, srm, or sso values for a specific point code and SSN in a mated application are changed, these parameter values for this specific point code and SSN in all applicable mated applications will be changed to the new values. The mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameters can be specified only if the GTT Load Sharing with Alternate Routing Indicator feature is enabled. Refer to the Activating the GTT Load Sharing with Alternate Routing Indicator Feature procedure for information about enabling the GTT Load Sharing with Alternate Routing Indicator feature. The mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 values must be shown in the rtrv-mrn output. The network type of the pc/pca/pci/pcn/pcn24 and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter values must be compatible, as shown in Table 2-42.

    If the Flexible GTT Load Sharing feature is not enabled for this example, enter these commands.

    chg-map:pca=005-005-005:ssn=250:rc=10:mpca=070-070-070 :mssn=251:materc=30:grp=grp05:mrc=yes:srm=yes:sso=on

    chg-map:pca=008-008-008:ssn=254:rc=10:mpca=031-049-100 :mssn=250:materc=40:grp=grp15:mrc=yes:srm=yes:sso=on

    chg-map:pca=008-008-008:ssn=254:rc=10:mpca=056-113-200 :mssn=251:materc=50:grp=grp05:mrc=yes:srm=yes:sso=off

    chg-map:pci=5-005-5:ssn=50:rc=10:mpci=s-5-005-6:mssn=50:materc=21 :grp=grp20:mrc=yes:sso=off

    chg-map:pci=5-005-5:ssn=50:rc=10:mpci=5-005-1:mssn=50:materc=22 :grp=grp20:mrc=yes:sso=off

    When each of these commands have successfully completed, this message should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    CHG-MAP:  MASP A - COMPLTD

    If the Flexible GTT Load Sharing feature is enabled for this example, enter these commands.

    chg-map:pca=005-005-005:ssn=250:rc=10:mpca=070-070-070 :mssn=251:materc=30:grp=grp05:mrc=yes:srm=yes:sso=on :mapset=dflt

    chg-map:pca=008-008-008:ssn=254:rc=10:mpc=179-183-050:mssn=250 :materc=11:grp=grp15:sso=off:mapset=12

    chg-map:pca=008-008-008:ssn=254:rc=10:mpca=031-049-100 :mssn=250:materc=40:grp=grp15:mrc=yes:srm=yes:sso=on:mapset=13

    chg-map:pca=008-008-008:ssn=254:rc=10:mpca=056-113-200 :mssn=251:materc=50:grp=grp05:mrc=yes:srm=yes:sso=off:mapset=13

    chg-map:pci=5-005-5:ssn=50:rc=10:mpci=s-5-005-6:mssn=50:materc=21 :grp=grp20:mrc=yes:sso=off:mapset=14

    chg-map:pci=5-005-5:ssn=50:rc=10:mpci=5-005-1:mssn=50:materc=22 :grp=grp20:mrc=yes:sso=off:mapset=14

    If the GTT Load Sharing with Alternate Routing Indicator feature is enabled for this example, and the mrnset and mrnpc parameters were not specified in 16, enter these commands.

    chg-map:pca=005-005-005:ssn=250:rc=10:mpca=070-070-070 :mssn=251:materc=30:grp=grp05:mrc=yes:srm=yes:sso=on :mapset=dflt:mrnset=1:mrnpc=007-007-007

    chg-map:pca=008-008-008:ssn=254:rc=10:mpc=179-183-050:mssn=250 :materc=11:grp=grp15:sso=off:mapset=12:mrnset=dflt:mrnpc=005-005-005

    When each of these commands have successfully completed, this message should appear.

    rlghncxa03w 07-05-07  11:44:13  GMT  EAGLE5 37.0.0
    CHG-MAP:  MASP A - COMPLTD

    Repeat this step for all new entries being added to the existing mated application.

    If the Flexible GTT Load Sharing feature is not enabled, the mated application can contain a maximum of 32 entries.

    If the Flexible GTT Load Sharing feature is enabled, and the MAP set is not the default MAP set, the MAP set can contain a maximum of 32 entries.

    If the Flexible GTT Load Sharing feature is enabled, and the MAP set is the default MAP set, the default MAP set can contain multiple MAP groups. Each group in the default MAP set can contain a maximum of 32 point code and subsystem entries.

18. Verify the changes using the rtrv-map command with the primary point code and subsystem specified in 16 and 17.

    If a new MAP set was created in 16, the mapset parameter should be specified with the rtrv-map command. The value for the mapset parameter should be the MAP set ID generated in 16.

    If the mated application was added to an existing MAP in 17, the mapset parameter and value specified in 17 should be specified with the rtrv-map command.

    If the Flexible GTT Load Sharing feature is not enabled for this example, enter these commands.

    rtrv-map:pca=003-003-003:ssn=254

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
    003-003-003                 254 10  DOM YES YES grp10    ON
                   040-040-040  254 20  DOM YES YES grp10    ON
    
    MAP TABLE IS  (38 of 1024) 4 % FULL

    rtrv-map:pca=005-005-005:ssn=250

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
    005-005-005                 250 10  DOM YES YES grp15    OFF
                   060-060-060  250 20  DOM YES YES grp15    OFF
                   070-070-070  251 30  DOM YES YES grp05    ON
    
    MAP TABLE IS  (38 of 1024)  4 % FULL

    rtrv-map:pca=008-008-008:ssn=254

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
    008-008-008                 254 10  DOM YES YES grp10    ON
                   031-049-100  250 40  DOM YES YES grp15    ON
                   056-113-200  251 50  DOM YES YES grp05    OFF
    
    MAP TABLE IS  (38 of 1024)  4 % FULL

    rtrv-map:pci=5-005-5:ssn=50

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    PCI       NET  Mate PC      SSN RC MULT SRM MRC GRP NAME SSO
    5-005-5                      50 10  DOM NO  YES grp20    OFF
              N    0257          50 20  DOM NO  YES grp20    OFF
              I  s-5-005-6       50 21  DOM NO  YES grp20    OFF
              I    5-005-1       50 22  DOM NO  YES grp20    OFF
    
    MAP TABLE IS  (38 of 1024)  4 % FULL

    Note:

    If the Weighted GTT Load Sharing feature is enabled, theWT,%WT, andTHR columns are shown in thertrv-map output.

    If the Flexible GTT Load Sharing feature is enabled for this example, enter these commands.

    rtrv-map:pca=003-003-003:ssn=254:mapset=11

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    MAPSET ID=11    MRNSET=DFLT     MRNPC=005-005-005
    PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
    003-003-003                  254 10  DOM YES YES grp10    ON
                   040-040-040   254 20  DOM YES YES grp10    ON
    
    MAP TABLE IS  (38 of 36000)  1 % FULL

    rtrv-map:pca=005-005-005:ssn=250:mapset=dflt

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    MAPSET ID=DFLT  MRNSET=1        MRNPC=007-007-007
    PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
    005-005-005                  250 10  DOM YES YES grp15    OFF
                   060-060-060   250 20  DOM YES YES grp15    OFF
                   070-070-070   251 30  DOM YES YES grp05    ON
    
    MAP TABLE IS  (38 of 36000)  1 % FULL

    rtrv-map:pca=008-008-008:ssn=254:mapset=13

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    MAPSET ID=13    MRNSET=DFLT    MRNPC=005-005-005
    PCA            Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
    008-008-008                 254 10  DOM YES YES grp10    ON
                   031-049-100  250 40  DOM YES YES grp15    ON
                   056-113-200  251 50  DOM YES YES grp05    OFF
    
    MAP TABLE IS  (38 of 36000)  1 % FULL

    rtrv-map:pci=5-005-5:ssn=50:mapset=14

    This is an example of the possible output.

    rlghncxa03w 09-02-07 00:34:31 GMT EAGLE5 40.1.0
    
    MAPSET ID=14    MRNSET ID=----  MRNPC=-----------
    PCI       NET  Mate PC       SSN RC MULT SRM MRC GRP NAME SSO
    5-005-5                       50 10  DOM NO  YES grp20    OFF
              N    0257           50 20  DOM NO  YES grp20    OFF
              I  s-5-005-6        50 21  DOM NO  YES grp20    OFF
              I    5-005-1        50 22  DOM NO  YES grp20    OFF
    
    MAP TABLE IS  (38 of 36000)  4 % FULL

    If the Weighted GTT Load Sharing feature is enabled, the WT, %WT, and THR columns are shown in the rtrv-map output.

    If the GTT Load Sharing with Alternate Routing Indicator feature is not enabled, the MRNSET and MRNPC fields are not shown in the rtrv-map output.

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

    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.