Provisioning a Load Shared Mated Application

This procedure is used to provision a load shared mated application in the database using the ent-map and chg-map commands. A load shared mated application is a mated application containing entries whose RC (relative cost) values are equal. The ent-map and chg-map commands use these parameters to provision a load shared mated application.

:pc/pca/pci/pcn/pcn24 – The point code of the primary signaling point that is to receive the message.

:mpc/mpca/mpci/mpcn/mpcn24 – The point code of the backup signaling point that is to receive the message.

Note:

The point codes can be either an ANSIpoint code (pc/pca, mpc/mpca), ITU-I or ITU-I spare point code (pci, mpci), a 14-bit ITU-N or 14-bit ITU-N spare point code (pcn, mpcn), or a 24-bit ITU-N (pcn24, mpcn24) point code.

Note:

Refer to Chapter 2, Configuring Destination Tables in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

:ssn – Subsystem number – the subsystem address of the primary point code that is to receive the message. The value for this parameter is 2 to 255.

:mssn – Mate subsystem number – the subsystem address of the backup point code that is to receive the message. The value for this parameter is 2 to 255.

:rc – The relative cost value of the primary point code and subsystem, defined by the pc/pca/pci/pcn/pcn24 and ssn parameters. The rc parameter has a range of values from 0 to 99, with the default value being 10.

:materc – The relative cost value of the backup point code and subsystem, defined by the mpc/mpca/mpci/mpcn/mpcn24 and mssn parameters. The materc parameter has a range of values from 0 to 99, with the default value being 50.

:grp – The name of the concerned signaling point code group that contains the point codes that should be notified of the subsystem status. This parameter applies to both RPCs/SSNs. The value for this parameter is shown in the rtrv-cspc output. If the desired value is not shown in the rtrv-cspc output, perform the Adding a Concerned Signaling Point Code procedure to add the desired group. If this parameter is not specified, then a CSPC group name is not specified for the mated application.

:sso – Subsystem Status Option – defines whether the subsystem status option is on or off. This parameter allows the user the option to have the specified subsystem marked as prohibited even though an MTP-RESUME message has been received by the indicating that the specified point code is allowed. The value for this parameter is on or off. The default value is off.

:mapset – The MAP set ID that the mated applications are assigned to. This parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. This parameter must be specified if the Flexible GTT Load Sharing feature is enabled. If the Flexible GTT Load Sharing feature is enabled, the point code and subsystem specified for the global title translation must be assigned to the MAP set specified by this parameter. The status of the Flexible GTT Load Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTT Load Sharing feature, perform the Activating the Flexible GTT Load Sharing Feature procedure.

The mapset parameter has three values.

dflt – to assign the MAP to the default MAP set. This value can be specified with both the ent-map and chg-map commands.
new – to assign the mated application to a new MAP set. This value can be specified only with the ent-map command.
The specific number of an existing MAP set if you are assigning the mated application to an existing MAP set. This value can be specified only with the chg-map command.
Refer to the Provisioning a MAP Set section for information on provisioning MAP sets.

:wt – The weight value assigned to the pc/pca/pci/pcn/pcn24 parameter value. The value of this parameter is from 1 - 99.

:mwt – The weight value assigned to the mpc/mpca/mpci/mpcn/mpcn24 parameter value. The value of this parameter is from 1 - 99.

:thr – The in-service threshold assigned to the MAP group or MAP set. The in-service threshold is the minimum percentage (from 1 - 100) of weight that must be available for an RC group (a group of entries in the MAP group or MAP set that have the same RC value assigned) to be considered available to carry traffic. If the percentage of the available weight is less than the in-service threshold, then the entire RC group is considered unavailable for traffic. If the percentage of the available weight is equal to or greater than the in-service threshold, then the RC group is considered available, and traffic can be sent to any available entity in the RC group. The value of the thr parameter is assigned to all entries that have the same RC (relative cost) value in the MAP group or MAP set that contain the point code specified in the ent-map or chg-map command.

Refer to the Provisioning Weights and In-Service Thresholds for Mated Applications section for information on provisioning MAP groups or MAP sets with weight and in-service threshold values.

:mrnset – The MRN set ID that is being assigned to the mated application. This is the MRN set from which alternate routing indicator searches are performed.

:mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 – The point code assigned to the mrnset that is being assigned to the MAP set.

The current values of the mrnset and :mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameters are shown in the rtrv-map output only if the Flexible GTT Load Sharing and the GTT Load Sharing with Alternate Routing Indicator features are enabled.

The new values for the mrnset and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameters 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-45.

Table 2-45 MAP and MRN Point Code Parameter Combinations

MAP Point Code Parameter	MRN Point Code Parameter
pc/pca	mrnpc/mrnpca
pci or pcn (See Notes 1 and 2)	mrnpci or mrnpcn (See Notes 1 and 2)
pcn24	mrnpcn24
Notes: 1. If the network type of the MAP point code parameter is ITU-I (`pci`), the network type of the MRN point code parameter can be either ITU-I (`mappci`) or ITU-N (`mappcn`). 2. If the network type of the MAP point code parameter is ITU-N (`pcn`), the network type of the MRN point code parameter can be either ITU-I (`mappci`) or ITU-N (`mappcn`).

:mrc – Message routing under congestion – specifies whether Class 0 messages are routed during congestion conditions. The values for this parameter are yes and no. This parameter can be specified for any type of mated application, but this parameter affects only the traffic for a dominant mated application. The default value for ANSI load shared mated applications is yes. The default value for ITU load shared mated applications is no.

:srm – Subsystem routing messages – defines whether subsystem routing messages (SBR, SNR) are transmitted between the mated applications. The values for this parameter are yes and no. The srm=yes parameter can be specified only for ANSI mated applications. This parameter affects traffic only on dominant and combined dominant/load shared mated applications. The default value for ANSI load shared mated applications is yes. The default value for ITU load shared mated applications is no.

A load shared mated application can contain up to 128 point codes and subsystems, a primary point code and subsystem, and up to 31 mated point codes and subsystems. When a new load shared mated application is added to the database, the first two entries, the primary point code and subsystem and a mate point code and subsystem are added using the ent-map command. All other mated point code and subsystem entries that are being assigned to the primary point code and subsystem are added to the load shared mated application using the chg-map command.

All the point codes and subsystems in a load shared mated application have the same relative cost value. Traffic is shared equally between the point codes and subsystems in this mated application.

If the Flexible GTT Load Sharing feature is not enabled, the primary point code and subsystem number or the mate point code and mate subsystem number combination can be in the database only once. If the Flexible GTT Load Sharing feature is enabled, the primary point code and subsystem number or mate point code and mate subsystem number combination can be in multiple MAP sets, but can be in the default MAP set only once.. Refer to the Provisioning a MAP Set section for information on provisioning MAP sets.

The point codes specified in the ent-map or chg-map commands (pc/pca, pci, pcn, or pcn24, and mpc/mpca, mpci, mpcn, or mpcn24) must be either a full point code in the routing point code table. Cluster point codes or network routing point codes cannot be specified with this command. The rtrv-rte command can be used to verify the point codes in the routing table. The point codes in the routing table are shown in the DPCA, DPCI, DPCN, or DPCN24 fields of the rtrv-rte command output. The EAGLE’s true point code, shown in the PCA, PCI, PCN, or PCN24 fields of the rtrv-sid command output, cannot be specified for a load shared mated application.

A load shared 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.

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.

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. The status of the ANSI/ITU SCCP Conversion feature can be verified with the rtrv-ctrl-feat command.

The values for the primary point code and subsystem combination (pc/ssn) cannot be the same as the mated point code and subsystem combination (mpc/mssn). However, the primary and mated point codes can be the same as long as the subsystem numbers are different.

If a mate point code (mpc/mpca/mpci/mpcn/mpcn24) is specified, the mssn parameter must be specified.

If the mssn parameter is specified, the mate point code (mpc/mpca/mpci/mpcn/mpcn24) must be specified.

If the grp, srm, mrc, and sso parameter values are specified, and the specified point code and SSN is assigned to multiple mated applications, the grp, srm, mrc, and sso values for all mated applications containing the specified point code and SSN will be changed to the values specified in this procedure.

The EAGLE can contain 1024, 2000, or 3000 mated applications. The EAGLE 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.

Provisioning a MAP Set

The Flexible GTT Load Sharing feature provides the ability to define multiple load sharing sets in the MAP table where the same point code and subsystem can be assigned to different load sharing sets.

The MAP table contains specific load sharing sets, designated by numbers, and a default MAP set.

Flexible Final GTT Load Sharing provides flexible load sharing for global title translations defined in the GTT table and not for the MPS-based features. The MPS-based features do not support the MAP set ID parameter. The MPS-based features perform lookups for load sharing in the default MAP set and the GTT table. The entries in the GTT table can be linked to a MAP set ID, allowing lookups in a specific MAP set other than the default MAP set.

Any MAP entries that were provisioned in the database before the Flexible GTT Load Sharing feature is enabled are placed in the default MAP set when the Flexible GTT Load Sharing feature is enabled.

To provision entries in the default MAP set, the mapset=dflt parameter must be specified with the ent-map or chg-map commands.

To provision entries in an existing MAP set other than the default MAP set, the mapset=<MAP set ID> parameter must be specified with the chg-map command. Provisioning entries in an existing MAP set can be performed only with the chg-map command.

To provision entries in a new MAP set, the mapset=new parameter must be specified with the ent-map command. The mapset=new parameter can be specified only with the ent-map command. When the ent-map command is executed with the mapset=new parameter, the new MAP set ID is automatically generated and displayed in the output of the ent-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 128 point codes.

The default MAP set can contain multiple MAP groups. The point code and subsystem number combination can appear only once in the default MAP set. The point code can appear in multiple MAP groups in the default MAP set with different subsystem numbers.

The point code and subsystem number combination provisioned in a MAP set can be provisioned in multiple MAP sets. All the point codes in a MAP set must be different.

Provisioning Weights and In-Service Thresholds for Mated Applications

Weighted GTT Load Sharing allows unequal traffic loads to be provisioned in MAP load sharing groups or MAP load sharing sets. This feature also allows provisioning control over load sharing groups or sets so that if insufficient capacity within the load sharing group or set is available, the load sharing group or set is not used.

To provision the weight values and in-service threshold values for MAP groups or MAP sets in this procedure, the wt, mwt, and thr parameters are used.

The wt, mwt, and thr parameters can be used only:

If the MAP group or MAP set is either a load shared or combined dominant/load shared MAP group or MAP set.
If the Weighted GTT Load Sharing feature is enabled and turned on.

The status of the Weighted GTT Load Sharing feature can be verified by entering the rtrv-ctrl-feat command. If the Weighted GTT Load Sharing feature is not enabled or not turned on, perform the Activating the Weighted GTT Load Sharing Feature procedure to enable and turn on the Weighted GTT Load Sharing feature.

If either the wt or mwt parameters are specified with the ent-map command, both parameters must be specified with the ent-map command.

To assign an in-service threshold value to the entries of a MAP group or MAP set that contains the point code value specified in the ent-map command, use the thr parameter with the wt and mwt parameters. When the thr parameter is specified with the ent-map command, the in-service threshold value is assigned to both entries specified in the ent-map command. The thr parameter cannot be specified with the chg-map command when adding additional entries to the MAP group or MAP set. When additional entries are added to the MAP group or MAP set with the chg-map command, the thr value that was specified in the ent-map command is assigned to the additional entries. For information on using the thr parameter with the chg-map command, refer to the Changing the Weight and In-Service Threshold Values of a Mated Application procedure.

The thr parameter does not have to be specified with the ent-map command. If the thr parameter is not specified with the ent-map command, the THR parameter value for the MAP group or MAP set is set to 1.

Specifying the wt and mwt parameters assigns a weight value to the point codes specified in the ent-map command. The wt parameter value is assigned to the mpc/mpca/mpci/mpcn/mpcn24 parameter value and the mwt parameter value is assigned to the mpc/mpca/mpci/mpcn/mpcn24 parameter value.

When additional entries are added to the MAP group or MAP set with the chg-map command, and the MAP group or MAP set entries have weight and in-service threshold values assigned, a weight value must be assigned to the mpc/mpca/mpci/mpcn/mpcn24 parameter value using the mwt parameter.

The wt parameter does not have to be specified with the chg-map command. If the wt parameter is specified with the chg-map command, the weight value for the pc/pca/pci/pcn/pcn24 parameter is not changed.

If the wt parameter is specified with the chg-map command and the wt value is the same as the value currently assigned to the pc/pca/pci/pcn/pcn24 parameter, the weight value for the pc/pca/pci/pcn/pcn24 parameter is not changed.

If the wt parameter is specified with the chg-map command and the wt value is different from the value currently assigned to the pc/pca/pci/pcn/pcn24 parameter, the weight value for the pc/pca/pci/pcn/pcn24 parameter is changed to the new wt value.

The weight values assigned to the entires in the MAP group or MAP set are shown in the WT column in the rtrv-map output.

The in-service threshold values assigned to the entires in the MAP group or MAP set are shown in the THR column in the rtrv-map output.

The %WT column in the rtrv-map output shows the percentage of the traffic the particular entry in the MAP group or MAP set will handle.

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

For more information on the Weighted GTT Load Sharing feature, refer to the Weighted GTT Load Sharing section.

Canceling the RTRV-MAP Command

Because the rtrv-map command used in this procedure can output information for a long period of time, the rtrv-map command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-map command can be canceled.

Press the F9 function key on the keyboard at the terminal where the rtrv-map command was entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-map command was entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-map command was entered, from another terminal other that the terminal where the rtrv-map command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, refer to Commands User's Guide.

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.

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 06-10-28 21:15:37 GMT EAGLE5 36.0.0

MAP table is (3000 of 3000) 100% full
```
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.
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 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.
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 128 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 128 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 128 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.
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.
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 06-10-25 09:48:31  GMT  EAGLE5 36.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=grp05This is an example of the possible output.
```
rlghncxa03w 06-10-25 09:48:31  GMT  EAGLE5 36.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 06-10-25 09:59:31  GMT  EAGLE5 36.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 06-10-25 09:48:31  GMT  EAGLE5 36.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 in 6 shows CSPC groups containing a mixture of point code types, or if the new CSPC group that was added in 6 contains a mixture of point code types, continue the procedure with 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.
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 06-10-28 21:15:37 GMT EAGLE5 36.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.
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 you do not wish to assign weight and in-service threshold values to the MAP entries in the MAP group or MAP set, continue the procedure with 10.
If you wish to assign weight and in-service threshold values to the entries in the MAP group or MAP set, and the WT, %WT, and THR columns are shown in the rtrv-map output in 1, then the Weighted GTT Load Sharing feature is enabled and turned on.
If the WT, %WT, and THR columns are not shown in the rtrv-map output in 1, perform the Activating the Weighted GTT Load Sharing Feature procedure to enable and turn on the Weighted GTT Load Sharing feature.
If the Weighted GTT Load Sharing feature is enabled and turned on, or the Activating the Weighted GTT Load Sharing Feature procedure was performed in this step, continue this procedure by performing one of these steps.
- 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.
- 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 13.
  - 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 14.
    
    If an entry is being added to an existing mated application, continue the procedure with 15.

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 and 12, 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 13.
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 14.
- If an entry is being added to an existing mated application, continue the procedure with 15.

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.
After the new point code has been added, skip 12 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 13.
- 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 14.
  - If an entry is being added to an existing mated application, continue the procedure with 15.

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=008-008-008

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.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 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   031-049-100 ---------- ------------   ls10       10    031-049-100
                                               RTX:No  CLLI=ls10clli

rtrv-rte:dpca=056-113-200

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   056-113-200 ---------- ------------   ls12       10    056-113-200
                                               RTX:No  CLLI=ls12clli

rtrv-rte:dpca=179-183-050

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   179-183-050 ---------- ------------   ls18       10    179-183-050
                                               RTX:No  CLLI=ls18clli

rtrv-rte:dpca=002-002-002

This is an example of the possible output.

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

rtrv-rte:dpca=004-004-004

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   004-004-004 ---------- -------------   ls04     10 004-004-004
                                               RTX:No  CLLI=ls04clli
                                               RTX:No  CLLI=ls13clli

rtrv-rte:dpca=068-135-094

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   068-135-094 ---------- ------------   ls14       10    068-135-094
                                               RTX:No  CLLI=ls14clli

rtrv-rte:dpca=100-100-100

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   100-100-100 ---------- ------------   ls16       10    100-100-100
                                               RTX:No  CLLI=ls16clli

rtrv-rte:dpca=100-130-079

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   100-130-079 ---------- ------------   ls17       10    100-130-079
                                               RTX:No  CLLI=ls17clli

rtrv-rte:dpca=200-147-100

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   200-147-100 ---------- ------------   ls19       10    200-147-100
                                               RTX:No  CLLI=ls19clli

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.

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 13.
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 14.
- If an entry is being added to an existing mated application, continue the procedure with 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 the pc/pca/pci/pcn/pcn24 and mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24 parameter values must be compatible, as shown in Note 7 in Table 2-46 or in Note 8 in Table 2-47.

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 the Provisioning MRN Entries procedure 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 14.
If an entry is being added to an existing mated application, continue the procedure with 15.

Add the mated application to the database using the ent-map command. Use Table 2-46 as a guide for the parameters and values that can be specified with the ent-map command.

Table 2-46 Load Shared Mated Application Parameter Combinations for the ENT-MAP Command

Mandatory Parameters

:pc/pca/pci/pcn/pcn24=<ANSI, ITU-I, ITU-I spare, ITU-N, ITU-N spare, or ITU-N24 point code from the rtrv-rte or rtrv-map outputs> (See Notes 5 and 7)

:ssn=<subsystem number, 2 - 255>

:rc=<0 - 99> The rc and materc parameter values must be equal.

: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, 5, and 7)

:mssn=<subsystem number of the mate, 2 - 255>

:materc=<0 - 99> The rc and materc parameter values must be equal.

Optional Parameters

:wt=<1 - 99> (See Note 4)

:mwt=<1 - 99> (See Note 4)

:thr=<1 - 100> (See Note 4)

:grp=<CSPC group name> (See Note 1)

:sso=<on, off>

:mapset=<new, dflt> (See Note 3)

:mrnset = <MRN set ID from the rtrv-mrn output> (See Note 6)

:mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24=<the point code value in the MRN set> (See Notes 6 and 7)

:srm=<yes, no> (See Note 8)

:mrc=<yes, no> (See Note 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 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, 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, the mapset parameter cannot be specified with the ent-map command.

To provision entries in the default MAP set, the mapset=dflt parameter must be specified with the ent-map command.
To provision entries in a new MAP set, the mapset=new parameter must be specified with the ent-map command. The mapset=new parameter can be specified only with the ent-map command. When the ent-map command is executed with the mapset=new parameter, the new MAP set ID is automatically generated and displayed in the output of the ent-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 128 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 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.
Refer to the Provisioning Weights and In-Service Thresholds for Mated Applications section for information about using the weight (wt and mwt) and in-service threshold (thr) parameters.
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 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-45.
The srm=yes parameter can be specified only for load shared mated applications containing ANSI point codes, but this parameter affects traffic only on dominant and combined dominant/load shared mated applications. The mrc parameter can be specified for a load shared mated application, but this parameter affects traffic only 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, mrc=no

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

ent-map:pca=004-004-004:ssn=254:rc=10:mpc=100-100-100:mssn=254 :materc=10:grp=grp10:sso=off

ent-map:pca=002-002-002:ssn=250:rc=10:mpc=100-130-079:mssn=250 :materc=10:grp=grp15:sso=on:wt=10:mwt=10:thr=40

ent-map:pca=008-008-008:ssn=254:rc=10:mpc=200-147-100:mssn=254 :materc=10:grp=grp10:sso=on:wt=10:mwt=20

ent-map:pci=5-005-5:ssn=50:rc=10:mpcn=0257:mssn=50:materc=10 :grp=grp20:mrc=yes:sso=off

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

rlghncxa03w 06-10-07  11:44:13  GMT  EAGLE5 36.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=004-004-004:ssn=254:rc=10:mpc=100-100-100:mssn=254 :materc=10:grp=grp10:sso=off:mapset=new

ent-map:pca=002-002-002:ssn=250:rc=10:mpc=100-130-079:mssn=250 :materc=10:grp=grp15:sso=on:mapset=dflt:wt=10:mwt=10:thr=40

ent-map:pca=008-008-008:ssn=254:rc=10:mpc=200-147-100:mssn=254 :materc=10:grp=grp10:sso=on:mapset=new:wt=10:mwt=20

ent-map:pci=5-005-5:ssn=50:rc=10:mpcn=0257:mssn=50:materc=10 :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=004-004-004:ssn=254:rc=10:mpc=100-100-100:mssn=254 :materc=10:grp=grp10:sso=off:mapset=new:mrnset=dflt:mrnpc=005-005-005

ent-map:pca=002-002-002:ssn=250:rc=10:mpc=100-130-079:mssn=250 :materc=10:grp=grp15:sso=on:mapset=dflt:wt=10:mwt=10:thr=40: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 06-10-07  11:44:13  GMT  EAGLE5 36.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 06-10-07  11:44:13  GMT  EAGLE5 36.0.0
ENT-MAP:  MASP A - COMPLTD

If no other entries are being added to the mated application, continue the procedure with 16.

If other entries are being added to the mated application, continue the procedure with 15.

Add the mated point code and subsystem to the mated application using the chg-map command. Use Table 2-47 as a guide for the parameters and values that can be specified with the chg-map command.

Table 2-47 Load Shared 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 point code from the rtrv-rte or rtrv-map outputs> (See Notes 5 and 8)

:ssn=<subsystem number>

: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, 5, and 8)

:mssn=<subsystem number of the mate, 2 - 255>

:materc=<0 - 99> The rc and materc parameter values must be equal.

Optional Parameters

:wt=<1 - 99> (See Note 4)

:mwt=<1 - 99> (See Note 4)

:grp=<CSPC group name> (See Notes 1 and 6)

:sso=<on, off> (See Note 6)

:mapset=<dflt or the number of an existing MAP set> (See Note 3)

:mrnset = <MRN set ID from the rtrv-mrn output> (See Note 7)

:mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24=<the point code value in the MRN set> (See Notes 7 and 8)

:srm=<yes, no> (See Notes 6 and 9)

:mrc=<yes, no> (See Notes 6 and 9)

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, 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, the mapset parameter cannot be specified with the chg-map command.

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

To provision entries in an existing MAP set, the mapset 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 128 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 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.
Refer to the Provisioning Weights and In-Service Thresholds for Mated Applications section for information about using the weight (wt and mwt) parameters.
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 CSPC group name (grp) srm, mrc,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-45.
The srm=yes parameter can be specified only for load shared mated applications containing ANSI point codes, but this parameter affects traffic only on dominant and combined dominant/load shared mated applications. The mrc parameter can be specified for a load shared mated application, but this parameter affects traffic only 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, mrc=no

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

chg-map:pca=002-002-002:ssn=250:mpca=068-135-094:mssn=251 :materc=10:grp=grp05:sso=off:mwt=20

chg-map:pca=008-008-008:ssn=254:mpc=179-183-050:mssn=250 :materc=10:grp=grp15:sso=off:mwt=30

chg-map:pca=008-008-008:ssn=254:mpca=031-049-100:mssn=250 :materc=10:grp=grp15:sso=on:mwt=40

chg-map:pca=008-008-008:ssn=254:mpca=056-113-200:mssn=251 :materc=10:grp=grp05:sso=off:mwt=50

chg-map:pca=255-001-000:ssn=251:mpca=255-001-001:mssn=56 :materc=10:grp=grp05:sso=off:wt=30:mwt=50

chg-map:pci=5-005-5:ssn=50:rc=10:mpci=s-5-005-6:mssn=50:materc=10 :grp=grp20:mrc=yes:sso=off

chg-map:pci=5-005-5:ssn=50:rc=10:mpci=5-005-1:mssn=50:materc=10 :grp=grp20:mrc=yes:sso=off

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

rlghncxa03w 06-10-07  11:44:13  GMT  EAGLE5 36.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=002-002-002:ssn=250:mpca=068-135-094:mssn=251 :materc=10:grp=grp05:sso=off:mapset=dflt:mwt=20

chg-map:pca=008-008-008:ssn=254:mpc=179-183-050:mssn=250 :materc=10:grp=grp15:sso=off:mapset=12:mwt=30

chg-map:pca=008-008-008:ssn=254:mpca=031-049-100:mssn=250 :materc=10:grp=grp15:sso=on:mapset=13:mwt=40

chg-map:pca=008-008-008:ssn=254:mpca=056-113-200:mssn=251 :materc=10:grp=grp05:sso=off:mapset=13:mwt=50

chg-map:pca=255-001-000:ssn=251:mpca=255-001-001 :mssn=56:materc=10:grp=grp05:sso=off:wt=30:mwt=50:mapset=1

chg-map:pci=5-005-5:ssn=50:rc=10:mpci=s-5-005-6:mssn=50:materc=10 :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=10 :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 14, enter these commands.

chg-map:pca=008-008-008:ssn=254:mpca=056-113-200:mssn=251 :materc=10:grp=grp05:sso=off:mapset=13:mwt=50:mrnset=1 :mrnpc=007-007-007

chg-map:pca=255-001-000:ssn=251:mpca=255-001-001 :mssn=56:materc=10:grp=grp05:sso=off:wt=30:mwt=50:mapset=1 :mrnset=dflt:mrnpc=005-005-005

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

rlghncxa03w 06-10-07  11:44:13  GMT  EAGLE5 36.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 128 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 128 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 128 point code and subsystem entries.

Verify the changes using the rtrv-map command with the primary point code and subsystem specified in 14 and 15.

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 15, the mapset parameter and value specified in 15 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=004-004-004:ssn=254

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 WT %WT THR
004-004-004                 254 10  SHR *Y  *Y  grp10    OFF -- ---  --
               100-100-100  254 10  SHR *Y  *Y  grp10    OFF -- ---  --

MAP TABLE IS   (37 of 1024)  4 % FULL

rtrv-map:pca=002-002-002: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 WT %WT THR
002-002-002                 250 10  SHR *Y  *Y  grp15    ON  10  50  40
               100-130-079  250 10  SHR *Y  *Y  grp15    ON  10  50  40
               068-135-094  251 10  SHR *Y  *Y  grp05    OFF 20 100  40

MAP TABLE IS   (37 of 1024)  4 % FULL

rtrv-map:pca=008-008-008:ssn=254

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 WT %WT THR
008-008-008                 254 10  SHR *Y  *Y  grp10    ON  10   6   1
               200-147-100  254 10  SHR *Y  *Y  grp10    ON  20  13   1
               179-183-050  250 10  SHR *Y  *Y  grp15    OFF 30  20   1
               031-049-100  250 10  SHR *Y  *Y  grp15    ON  40  26   1
               056-113-200  251 10  SHR *Y  *Y  grp05    OFF 50  33   1

MAP TABLE IS   (37 of 1024)  4 % FULL

rtrv-map:pca=255-001-000: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 WT %WT THR
255-001-000                 251 10  SHR *Y  *Y  grp01    OFF 50  55  20
               253-001-002  254 10  SHR *Y  *Y  grp01    OFF 10  11  20
               255-001-001   56 10  SHR *Y  *Y  grp05    OFF 30  33  20

MAP TABLE IS   (37 of 1024)  4 % FULL

rtrv-map:pci=5-005-5:ssn=50

This is an example of the possible output.

rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0

PCI       NET  Mate PC      SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
5-005-5                      50 10  SHR *N  *N  grp20    OFF -- ---  --
          N    0257          50 10  SHR *N  *N  grp20    OFF -- ---  --
          I  s-5-005-6       50 10  SHR *N  *N  grp20    OFF -- ---  --
          I    5-005-1       50 10  SHR *N  *N  grp20    OFF -- ---  --

MAP TABLE IS   (37 of 1024)  4 % FULL

Note:

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

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

rtrv-map:pca=004-004-004:ssn=254: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=DFLT     MRNPC=005-005-005
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
004-004-004                  254 10  SHR *Y  *Y  grp10    OFF -- ---  --
               100-100-100   254 10  SHR *Y  *Y  grp10    OFF -- ---  --

MAP TABLE IS  (37 of 36000)  4 % FULL

rtrv-map:pca=002-002-002:ssn=250: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=1        MRNPC=007-007-007
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
002-002-002                  250 10  SHR *Y  *Y  grp15    ON  10  50  40
               100-130-079   250 10  SHR *Y  *Y  grp15    ON  10  50  40
               068-135-094   251 10  SHR *Y  *Y  grp05    OFF 20 100  40

MAP TABLE IS  (37 of 36000)  4 % FULL

rtrv-map:pca=008-008-008:ssn=254:mapset=11

This is an example of the possible output.

rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0

MAPSET ID=11    MRNSET=1        MRNPC=007-007-007
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
008-008-008                  254 10  SHR *Y  *Y  grp10    ON  10   6   1
               200-147-100   254 10  SHR *Y  *Y  grp10    ON  20  13   1
               179-183-050   250 10  SHR *Y  *Y  grp15    OFF 30  20   1
               031-049-100   250 10  SHR *Y  *Y  grp15    ON  40  26   1
               056-113-200   251 10  SHR *Y  *Y  grp05    OFF 50  33   1

MAP TABLE IS  (37 of 36000)  4 % FULL

rtrv-map:pca=255-001-000:ssn=251:mapset=1

This is an example of the possible output.

rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0

MAPSET ID=1     MRNSET=DFLT     MRNPC=005-005-005
PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
255-001-000                  251 10  SHR *Y  *Y  grp01    OFF 50  55  20
               253-001-002   254 10  SHR *Y  *Y  grp01    OFF 10  11  20
               255-001-001    56 10  SHR *Y  *Y  grp05    OFF 30  33  20

MAP TABLE IS   (37 of 36000)  4 % FULL

rtrv-map:pci=5-005-5:ssn=50:mapset=14

This is an example of the possible output.

rlghncxa03w 09-07-07 00:34:31 GMT EAGLE5 41.1.0

MAPSET ID=14    MRNSET=----     MRNPC=-----------
PCI       NET  Mate PC       SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
5-005-5                       50 10  SHR *N  *N  grp20    OFF -- ---  --
          N    0257           50 10  SHR *N  *N  grp20    OFF -- ---  --
          I  s-5-005-6        50 10  SHR *N  *N  grp20    OFF -- ---  --
          I    5-005-1        50 10  SHR *N  *N  grp20    OFF -- ---  --

MAP TABLE IS   (37 of 36000)  4 % FULL

If the Weighted GTT Load Sharing feature is not enabled, the WT, %WT, and THR columns are not 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.

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-79 Provision a Load Shared Mated Application - Sheet 1 of 11