Go to primary content
Oracle® Communications EAGLE Database Administration - GTT User's Guide
Release 46.8
F11880-02
Go To Table Of Contents
Contents
Previous
Previous 		Next
Next

Changing the Attributes of a Mated Application

This procedure is used to change the values of the parameters of the existing mated application (MAP) group or MAP set, shown in Table 2-52, using the chg-map command.

Table 2-52 Mated Application Parameters

CSPC group name sso srm mrc rc

Changing the rc value of the mated application in this procedure is not performed to change the mated application type. If you wish to change the mated application type, perform the Changing the Mated Application Type procedure.

The chg-map command contains other parameters that are not used in this procedure. Perform these procedures as applicable to change the other parameter values.

The chg-map command can also be used to add point code/SSN entries to an existing MAP group or MAP set. This action is not covered in this procedure. If you wish to add point code/SSN entries to an existing MAP group or MAP set, perform one of these procedures.

The chg-map command in this procedure uses these parameters.

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

Note:

The point codes can be either an ANSI point code (pc/pca), ITU-I or ITU-I spare point code (pci), a 14-bit ITU-N or 14-bit ITU-N spare point code (pcn), or a 24-bit ITU-N (pcn24) 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.

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

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

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

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

: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 sso parameter cannot be specified if the pc/pca/pci/pcn/pcn24 value is the EAGLE’s true point code, shown in the rtrv-sid output.

:mapset – The MAP set ID that the mated applications are assigned to, shown in the rtrv-map output. MAP set IDs are shown only if the Flexible GTT Load Sharing feature is enabled. The mapset parameter value cannot be changed in this procedure. If the rtrv-map output shows the MAPSET field, the mapset parameter must be specified with the chg-map command. If the rtrv-map output does not show the MAPSET field, the Flexible GTT Load Sharing feature is not enabled. The mapset parameter cannot be specified with the chg-map command. The mapset parameter has two values.
  • dflt – to change the mated application in the default MAP set. The EAGLE’s true point code (shown in the rtrv-sid output) and subsystem can be assigned only to the default MAP set.
  • the specific number of an existing MAP set if you are changing the mated application in an existing MAP set.

:force=yes – This parameter must be specified if the rc parameter is specified with either the srm or mrc parameters.

At least one optional parameter must be specified.

The mated application to be changed must be in the database.

If the primary point code and subsystem are being changed, the current mated application must be removed from the database and a new mated application with the new primary point code and subsystem, containing the mated point codes and subsystems from the mated application that was removed, should be added to the database.

If the point code is entered with thepc or pca parameters, the specified point codes in the concerned point code broadcast group must have been entered with the pc or pca parameters of the ent-cspc command. If the point code is entered with the pci,pcn, or pcn24 parameters, the specified point codes in the concerned point code broadcast group must have been entered with thepci,pcn, or pcn24 parameters of the ent-cspc command, respectively.

If the mated application contains the EAGLE’s true point code, the relative cost value assigned to this point code must be the lowest value in the mated application.

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

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.

  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 WT %WT THR
002-002-002               250 10  SHR *Y  *Y  grp15    ON  10  33  20
             100-130-079  250 10  SHR *Y  *Y  grp15    ON  10  33  20
             068-135-094  251 10  SHR *Y  *Y  grp05    OFF 10  33  20

MAPSET ID=10
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
003-003-003               254 10  DOM YES YES grp10    ON  -- ---  --
             040-040-040  254 20  DOM YES YES grp10    ON  -- ---  --

MAPSET ID=11
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 -- ---  --

MAPSET ID=DFLT
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
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  -- ---  --

MAPSET ID=9
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
006-006-006               250 10  SOL *Y  *Y  grp15    OFF -- ---  --

MAPSET ID=DFLT
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
007-007-007               251 10  SOL *Y  *Y  grp05    ON  -- ---  --

MAPSET ID=12
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
008-008-008               254 10  COM YES *Y  grp10    ON  10  33  20
             200-147-100  254 10  COM YES *Y  grp10    ON  10  33  20
             179-183-050  250 10  COM YES *Y  grp15    OFF 10  33  20
             031-049-100  250 20  COM YES *Y  grp15    ON  10  50  20
             056-113-200  251 20  COM YES *Y  grp05    OFF 10  50  20

MAPSET ID=DFLT
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
255-001-000               250 10  SOL *Y  *Y  grp01    ON  -- ---  --

MAPSET ID=1
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
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 WT %WT THR
255-001-000               252 10  SOL *Y  *Y  grp01    ON  -- ---  --

MAPSET ID=DFLT
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
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 WT %WT THR
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 WT %WT THR
255-001-001               250 10  DOM NO  NO  grp01    OFF -- ---  --
             253-001-001  254 20  DOM NO  NO  grp01    OFF -- ---  --

MAPSET ID=DFLT
PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
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 WT %WT THR
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 WT %WT THR
255-001-002               253 10  SHR *Y  *Y  grp01    ON  -- ---  --
             255-001-004  254 10  SHR *Y  *Y  grp01    ON  -- ---  --

MAPSET ID=7
PCI          Mate PCI     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
2-001-2                   255 10  DOM YES YES grp03    OFF -- ---  --
             2-001-1      254 20  DOM YES YES grp03    OFF -- ---  --

MAPSET ID=8
PCN          Mate PCN     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
00347                     253 10  SHR *N  *N  grp05    OFF -- ---  --
             01387        254 10  SHR *N  *N  grp05    OFF -- ---  --

MAP TABLE IS   (37 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 you wish to change the point code and SSN of a mated application, record the data for the mated application. Remove the mated application by performing the Removing a Mated Application procedure. Add the mated application with the new point code and SSN by performing the one of these procedures.
    If the CSPC group name assigned to the mated application is not being changed, continue the procedure by performing one of these steps.
    • If the sso parameter value will not be changed, continue the procedure with 5.
    • If the sso parameter value will not be changed, continue the procedure with 4.

    If the CSPC group name assigned to the mated application is being changed, continue the procedure with 2.

  2. 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 09-07-25 09:48:31  GMT  EAGLE5 41.1.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 this command.

    rtrv-cspc:grp=grp05

    This is an example of the possible output. 

    rlghncxa03w 09-07-25 09:48:31  GMT  EAGLE5 41.1.0
CSPC GRP      PCA
grp05         005-005-005
              007-007-007
              008-008-008
              009-009-009
    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. If the format of the point codes that will be assigned to the CSPC group created by performing the Adding a Concerned Signaling Point Code procedure will be different from the primary point code of the mated application, the ANSI/ITU SCCP conversion feature must be enabled when the Adding a Concerned Signaling Point Code procedure is performed. Continue the procedure by performing one of these steps.
    • If the sso parameter value will not be changed, continue the procedure with 5.
    • If the sso parameter value will not be changed, continue the procedure with 4.
    If the CSPC group contains the required point codes, continue the procedure by performing one of these steps.
    • If the CSPC group displayed in this step contains point codes with different formats (the ANSI/ITU SCCP Conversion feature is enabled), or if the format of all the point codes in the CSPC group are the same as the primary point code of the mated application, continue the procedure by performing one of these steps.
      • If the sso parameter value will not be changed, continue the procedure with 5.
      • If the sso parameter value will not be changed, continue the procedure with 4.
    • If the CSPC group displayed in this step contains point codes with the same format and the format of the primary point of the mated application is different, continue the procedure with 3.
  3. 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 formats (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 09-07-28 21:15:37 GMT EAGLE5 41.1.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.

    Continue the procedure by performing one of these steps.
    • If the sso parameter value will not be changed, continue the procedure with 5.
    • If the sso parameter value will not be changed, continue the procedure with 4.
  4. The sso parameter cannot be specified for a mated application if the pc/pca/pci/pcn/pcn24 value is the EAGLE’s point code. A load shared or combined dominant/load shared mated application cannot contain the EAGLE’s point code. A dominant mated application containing the EAGLE’s point code can contain only one mate point code and SSN. The EAGLE’s point code in the dominant mated application must have the lowest RC value.

    Verify the EAGLE’s point code by entering the rtrv-sid command. The EAGLE’s point code is shown in the PCA, PCI, PCN, and PCN24 fields. This is an example of the possible output. 

    rlghncxa03w 09-07-10 11:43:04 GMT EAGLE5 41.1.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
  5. Change the rc, grp, sso, srm, or mrc parameter values, as applicable, in the mated application using the chg-map command with the point code and subsystem number from the rtrv-map command output shown in 1.

    If the MAPSET field is shown in the rtrv-map output in 1, the mapset parameter must be specified with the chg-map command. If the MAPSET field is not shown in the rtrv-map output in 1 the mapset parameter cannot be specified with the chg-map command.

    For this example, enter this command.

    chg-map:pca=255-001-001:ssn=250:grp=grp05:srm=yes:mrc=yes:sso=on:mapset=4

    This message should appear. 

    rlghncxa03w 09-07-25 09:43:31  GMT  EAGLE5 41.1.0
CHG-MAP:  MASP A - COMPLTD
  6. Verify the changes using the rtrv-map command with the primary point code and subsystem specified in 5.

    If the mapset parameter was specified in 5, the mapset parameter and value specified in 5 must be specified with the rtrv-map command in this step.

    If the mapset parameter was not specified in 5, the mapset parameter cannot be specified with the rtrv-map command in this step.

    For this example, enter this command.

    rtrv-map:pca=255-001-001:ssn=250:mapset=4

    This is an example of the possible output. 

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

   MAPSET ID=4
   PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
   255-001-001               250 10  DOM YES YES grp05    ON  -- ---  --
                253-001-001  254 20  DOM NO  NO  grp01    OFF -- ---  --

MAP TABLE IS  (37 of 36000)  1 % FULL
  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.

    If you do not wish to change the mated application type, the weights or in-service thresholds of the mated application, or the MRNSET and MRN point code of the mated application, this procedure is finished.

    If you wish to change the mated application type, the weights or in-service thresholds of the mated application, or the MRNSET and MRN point code of the mated application, perform these procedures as applicable.

Figure 2-106 Change the Attributes of a Mated Application - Sheet 1 of 6

Figure 2-107 Change the Attributes of a Mated Application - Sheet 2 of 6

Figure 2-108 Change the Attributes of a Mated Application - Sheet 3 of 6

Figure 2-109 Change the Attributes of a Mated Application - Sheet 4 of 6

Figure 2-110 Change the Attributes of a Mated Application - Sheet 5 of 6

Figure 2-111 Change the Attributes of a Mated Application - Sheet 6 of 6

Previous
Previous 		Next
Next
Go To Table Of Contents
Contents