4.104 chg-mrn

Use this command to add new point codes, modify existing point codes and relative costs, and add or modify Alternate RI Mate data in the Mated Relay Node (MRN) table. The Intermediate GTT Load-Sharing (IGTTLS) feature must be on to enter this command. The GTT Load Sharing with Alternate Routing Indicator Feature (GTT LS ARI) must be enabled to provision an Alternate RI Mate.

If the IGTTLS feature is on, and the Flexible GTT Load Sharing feature (FGTTLS) is enabled, then entries are added to or changed in existing MRN sets in the MRN table.

If the IGTTLS feature is on, and the FGTTLS feature is not enabled, then the MRN table can contain a maximum of 3000 entries. If both the IGTTLS and FGTTLS features are on, then the MRN table can contain a maximum of 6000 entries.

Caution:

If any entries are provisioned in the SCCP-SERV table, the maximum number of entries that the MRN table can contain is reduced by that amount. Enter the rtrv-sccp-serv command to see if entries exist in the SCCP-SERV table. See the Notes section for additional information on multiplicity modes.

Parameters

Note:

See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.

Note:

The mapset, mappc, and mapssn parameters indicate whether an Alternate RI Mate search is performed in the MAP table if all PCs provisioned in a given MRN Set are unavailable or congested.
pc (mandatory)
ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
pca
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc/pca/pci/pcn/pcn24/pcn16 (mandatory)
Post-GTT-translated point code.
pci (mandatory)
ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pcn (mandatory)
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn24 (mandatory)
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn16 (mandatory)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000--127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un--000--127
sna--000--15
mna--000--31
eswt (optional)
Entity set weight. The weight assigned to each PC in a weighted entity set.

Note:

This parameter cannot be specified when adding PCs to a weighted entity set or when modifying RC or weight values for an individual PC.
Range:
1 - 99, none

none —Changes a weighted entity set to a non-weighted entity set.

force (optional)
This parameter must be specified to modify the rc, rc1, rc2, rc3, or rc4 parameter and the wt, wt1, wt2, wt3, or wt4 parameter in the same command.

Modification of the wt, wt1, wt2, wt3, or wt4 parameters depends on the parameter's current multiplicity state, which depends on the RC value. Changing the rc parameter value can change the multiplicity state, which can then cause any of the weight parameter values to become invalid.

Range:
yes
grpwt (optional)
Group weight. The weight assigned to each PC in a weighted RC group.

Note:

This parameter cannot be specified when adding PCs to a weighted entity set or when modifying RC or weight values for an individual PC.
Range:
1 - 99
mappc (optional)
ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
mappca
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

Default:
000
mappc/mappca/mappci/mappcn/mappcn24/mappcn16 (optional)

Alternate RI Mate point code.

mappci (optional)
ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

Default:
0-000-0
mappcn (optional)
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

Default:
00000
mappcn24 (optional)
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

Default:
000
mappcn16 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000--127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un---000---127
sna---000---15
mna---000---31
Default:
000
mapset (optional)
Alternate RI Mate MAP Set ID. The MAP set where Alternate Routing Indicator searches are performed.
Range:
1 - 36000, dflt

dflt—Default MAP Set

If the mappc and mapssn parameters are specified, and the mapset parameter is not specified, then the mapset parameter is automatically set to a value of dflt.

Default:
No change to the current value
mapssn (optional)
Alternate RI Mate Subsystem Number. The subsystem number used for the Alternate Routing Indicator search.
Range:
2 - 255, *, none

If the mapssn=* parameter is specified, then the values specified for the mapset and mappc parameters must already exist in the MAP table.

Default:
No change to the current value
mrnset (optional)
MRN set ID.
Range:
1 - 3000, dflt

dflt -default MRN set

pc1 (optional)
ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
pca1
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc1/pca1/pci1/pcn1/pcn241/pcn161 (optional)
Alternate post-GTT-translated point code.
pc2 (optional)
ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
pca2
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc2/pca2/pci2/pcn2/pcn242/pcn162 (optional)
Alternate post-GTT-translated point code.
pc3 (optional)
ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
pca3
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc3/pca3/pci3/pcn3/pcn243/pcn163 (optional)
Alternate post-GTT-translated point code.
pc4 (optional)
ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
Synonym:
pca4
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc4/pca4/pci4/pcn4/pcn244/pcn164 (optional)
Alternate post-GTT-translated point code.
pci1 (optional)
ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pci2 (optional)
ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pci3 (optional)
ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pci4 (optional)
ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
Range:
s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pcn161 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000--127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un---000---127
sna---000---15
mna---000---31
pcn162 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000--127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un---000---127
sna---000---15
mna---000---31
pcn163 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000--127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un---000---127
sna---000---15
mna---000---31
pcn164 (optional)
16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
Range:
000--127
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
un---000---127
sna---000---15
mna---000---31
pcn1 (optional)
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn2 (optional)
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc,m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn241 (optional)
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn242 (optional)
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn243 (optional)
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn244 (optional)
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Range:
000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn3 (optional)
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc,m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn4 (optional)
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
Range:
s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

rc (optional)
Relative cost. The relative cost of the route for the primary PC.
Range:
0 - 99
rc1 (optional)
Relative cost 1. The relative cost of the route for mate PC 1.
Range:
0 - 99
rc2 (optional)
Relative cost 2. The relative cost of the route for mate PC 2.
Range:
0 - 99
rc3 (optional)
Relative cost 3. The relative cost of the route for mate PC 3.
Range:
0 - 99
rc4 (optional)
Relative cost 4. The relative cost of the route for mate PC 4.
Range:
0 - 99
thr (optional)
Threshold. The in-service threshold of all PCs in a weighted entity set or RC group.

This parameter cannot be specified when adding PCs to a weighted entity set or RC group or when modifying RC or weight values for an individual PC.

If this parameter is not specified, a value of 1% is assigned to each weighted PC.

Range:
1 - 100
wt (optional)
Weight. The new weight assigned to the primary PC.

Note:

This parameter cannot be specified when adding PCs to a weighted entity set.
Range:
1 - 99
wt1 (optional)
Weight 1. The weight assigned to the mate PC 1 that is being added to the weighted entity set.
Range:
1 - 99
wt2 (optional)
Weight 2. The weight assigned to the mate PC 2 that is being added to the weighted entity set.
Range:
1 - 99
wt3 (optional)
Weight 3. The weight assigned to the mate PC 3 that is being added to the weighted entity set.
Range:
1 - 99
wt4 (optional)
Weight 4. The weight assigned to the mate PC 4 that is being added to the weighted entity set.
Range:
1 - 99

Example

In this example, the system searches the MRN table for a point code of 1-1-0. If the point code is found, its relative cost is set to 40.

chg-mrn:pc=1-1-0:rc=40

In this example, the system searches the MRN table for point code 1-1-0. Having found it, the system searches the entity set for 1-1-10.  If 1-1-10 is not in the entity set, the command adds point code 1-1-10 is added to the entity set and assigned a relative cost of 30.

chg-mrn:pc=1-1-0:pc1=1-1-10:rc1=30

In this example, the system searches the MRN table for a point code of 1-1-0. Having found it, the system searches for each of the specified associated point codes in the entity set.  If neither associated point code is found, the specified point codes and their relative costs are inserted into the entity set in the MRN table.

chg-mrn:pc=1-1-0:pc1=1-1-1: rc1=10:pc2=1-1-10:rc2=20

These examples include spare point codes.

chg-mrn:pcn=s-1-1-1-123-aa:rc=1:pcn1=s-1-1-1-235-aa:rc1=2:pcn2=s-1-1-1-235-aa:rc2=3

chg-mrn:pci=s-2-2-1:rc=20:pci1=s-2-2-2:rc1=21:pci2=s-2-100-1:rc2=22

chg-mrn:pc=1-1-1:rc=30:mrnset=dflt

chg-mrn:pc=1-1-1:rc=20:pc1=2-2-2:rc1=20:mrnset=111

chg-mrn:pc=1-1-1:pc1=3-3-3:rc1=30:mrnset=111

This example changes a non-weighted entity set to a weighted entity set.

chg-mrn:pc=1-1-1:eswt=30

chg-mrn:pc=1-1-1:eswt=30:thr=50

This example changes a weighted entity set to a non-weighted entity set.

chg-mrn:pc=1-1-1:eswt=none

This example assigns a weight value to each PC in a weighted RC group within a weighted entity set.

chg-mrn:pc=1-1-1:grpwt=20

This example assigns a threshold value to each PC in the RC group within a weighted entity set.

chg-mrn:pc=1-1-1:thr=70

This example assigns a weight and threshold to each PC in an RC group within a weighted entity set. 

chg-mrn:pc=1-1-1:grpwt=20:thr=70

This example assigns PC 1 a weight of 30.

chg-mrn:pc=1-1-1:wt=30

This example adds PC 1 to the weighted entity set containing PC 1 and assigns PC 1 an RC of 30 and a weight of 20.

chg-mrn:pc=1-1-0:pc1=1-1-10:rc1=30:wt1=20

This example assigns specified PCs and their associated RCs and weights to the weighted entity set that contains the point code 1.

chg-mrn:pc=1-1-0:pc1=1-1-1:rc1=10:wt1=35:pc2=1-1-10:rc2=20:wt2=20

This example modifies both RC values and weights for PCs in an existing weighted entity set.

chg-mrn:pc=1-1-0:rc=30:wt=10:pc1=1-1-10:rc1=20:pc2=1-1-2:wt2=5:force=yes

This example modifies only weights for PCs in an existing weighted entity set.

chg-mrn:pc=1-1-0:wt=10:pc1=1-1-10:wt1=20:pc2=1-1-2:wt2=5

chg-mrn:pc=1-1-1:mrnset=111:mapset=dflt:mappc=2-1-1:mapssn=10

chg-mrn:pc=1-1-1:mrnset=111:mapssn=*

chg-mrn:pc=1-1-1:mrnset=111:mapset=1:mappc=2-1-2:mapssn=12

chg-mrn:pci=1-002-1:mrnset=10:mapset=2:mappcn=00126:mapssn=12

Example for 16 bit PC entry:

chg-mrn:pcn16=1-14-0:rc=10:wt=30:pcn161=45-1-0:rc1=10:wt1=10:mrnset=dflt

Dependencies

The Intermediate Global Title Translation Load Sharing feature must be turned on before this command can be entered.

The apca and pcn24/pcn16 parameters cannot be specified for the same MRN set.

When a new point code is specified, its relative cost (rc) must be specified; a new point code and its relative cost must be entered together in the command.

A new point code that is specified in the command must not already exist in the MRN table.

The point codes cannot have the same value as the EAGLE SID.

The same point code value cannot be entered more than once in the MRN table.

Each point code group can contain a maximum of 128 point codes.

ITU-N point codes must be in the format set by the npcfmti parameter of the chg-stpopts command. (Use the rtrv-stpopts command to display the STP option settings).

Mate remote point codes must already exist as destinations in the Ordered Route entity set or reside in a cluster destination for which ordered routes are specified.

To change the relative cost for a point code, the point code must already exist in the MRN table.

The Flexible GTT Loadsharing feature must be enabled before the mrnset parameter can be specified.

If the Flexible GTT Loadsharing feature is enabled, the specified PC must already exist in the specified MRN set.

The specified MRN set must already exist in the MRN table.

If the IGTTLS feature is on, and the FGTTLS feature is not enabled, then the MRN table can contain a maximum of 3000 entries. If both the IGTTLS and FGTTLS features are on, then the MRN table can contain a maximum of 6000 entries.

The Weighted GTT Loadsharing feature must be turned on before the wt/wt1/wt2/wt3/wt4, eswt, grpwt, or thr parameter can be specified.

If the rc parameter is not specified, the wt parameter cannot be specified.

The eswt and grpwt parameters cannot be specified together in the command.

If the eswt=none parameter is specified, the thr parameter cannot be specified.

If the eswt, grpwt, or thr parameters are specified, the rc/rc1/rc2/rc3/rc4 and wt/wt1/wt2/wt3/wt4 parameters cannot be specified.

If the Weighted GTT Loadsharing feature is enabled, and individual PCs are being modified, the wt or rc parameter must be specified for each PC.

Alternate point codes cannot be specified when modifying an entity set or RC group.

If the pc1/pc2/pc3/pc4 parameter is specified for a weighted entity set, a corresponding wt1/wt2/wt3/wt4 parameter must be specified.

If the pc1/pc2/pc3/pc4 parameter is specified for a non-weighted entity set, the wt1/wt2/wt3/wt4 parameter cannot be specified.

The eswt=none parameter cannot be specified for non-weighted entity sets.

The grpwt and thr parameters cannot be specified for non-weighted entity sets.

At least one additional point code must be specified.

If the wt/wt1/wt2/wt3/wt4 parameter is specified, the corresponding pc/pc1/pc2/pc3/pc4 parameter must be specified.

The pc/pc1/pc2/pc3/pc4 parameter values must be full point codes.

The SID table is corrupt or cannot be found by the system.

The Route table is corrupt or cannot be found by the system.

At least one optional parameter must be specified.

If the Weighted GTT Loadsharing feature is not enabled, and individual PCs are being modified, the rc parameter must be specified for each PC.

The eswt, grpwt, and thr parameters cannot be specified for solitary or dominant entity sets.

If the chg-sid:pctype=ansi command is entered, a value of ni=000 cannot be specified.

If the chg-sid:pctype=ansi command is entered, and a value of ni=001 – 005 is specified, a value of nc=000 cannot be specified.

The force=yes parameter must be specified before the rc, rc1, rc2, rc3, or rc4 parameter can be specified in the same command with the wt, wt1, wt2, wt3, or wt4 parameter.

The force parameter can be used only to specify the rc, rc1, rc2, rc3, or rc4 parameter and the wt, wt1, wt2, wt3, or wt4 parameter in the same command.

The value specified for the pc/pc1/pc2/pc3/pc4 parameter cannot be associated with a proxy point code.

The GTT LS ARI feature must be enabled before the mapset, mappc, or mapssn parameter can be specified.

The value specified for the mappc parameter must be a full point code.

The point codes and alternate RI Mate point codes must have compatible network types as shown:

  • ITUI, ITU-N, ITU-I spare, ITU-N-spare—ITUI, ITU-N, ITU-I spare, ITU-N-spare
  • ANSI—ANSI
  • ITUN-24—ITUN-24
  • ITUN-16---ITUN-16

The MAP table is corrupt or cannot be found.

The value specified for the mapset parameter must already exist in the MAP table.

The values specified for the mappc and mapssn parameters must already exist in the specified MAP Set.

The values specified for the mapset and mappc parameters must already exist in the MAP table.

The value specified for the mappc parameter cannot match an existing STP point code.

The mappc and mapssn parameters must be specified together in the command.

Notes

For MRN commands, an entity set consists of a group of PCs that are used for traffic distribution, and an RC group consists of PCs within an entity set that have the same RC. In loadsharing mode, an entity set contains 1 RC group. In combined/dominant loadsharing mode, an entity set can contain multiple loadsharing groups.

All of the point codes that are specified in one command must exist in the same point code group in the MRN table.

In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).

The EAGLE supports the following multiplicity modes for nodes/subsystems.

  • A group of replicated PCs are in dominant mode if each PC in the group has a unique RC. The specified subsystem with the lowest RC acts as the primary subsystem, while the mate subsystem acts as a backup. In the event of congestion, messages route to the mate subsystem. When the congestion subsides, messages are again routed to the primary (dominant) subsystem.
  • A group of replicated PCs are in load sharing mode if each PC in the group has the same RC. All messages are evenly distributed at the SCCP level to all nodes/subsystems in the group. In the event of congestion or failure, the non-affected subsystem assumes the load of its failed or congested mate.
  • The combined load sharing/dominant mode supports a combination of load sharing and dominant mode. A group of PCs are in combined load sharing/dominant mode when at least two of the PCs have the same RC and another node subsystem in the group has a different RC. A combination of node accessibility and RC determines the preferred PC.

When the Weighted GTT Loadsharing feature is turned on, weighted entity sets and RC groups are supported, and threshold values can be assigned to each PC. 

When the GTT LS ARI feature is enabled, the Alternate RI Mate for an MRN Set can be provisioned.

Output

chg-mrn:pci=1-1-2:mrnset=111:mapset=10:mappc=1-1-1:mapssn=*

    tekelecstp 11-03-22 15:43:00 EST  EAGLE 44.0.0
    chg-mrn:pci=1-1-2:mrnset=111:mapset=10:mappc=1-1-1:mapssn=*
    Command entered at terminal #4.
    CHG-MRN: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
    CHG-MRN: MASP A - COMPLTD 
;

Related Topics