ent-mrn

4.328 ent-mrn

Use this command to assign point codes and Alternate RI Mates in the Mated Relay Node (MRN) table. The Intermediate GTT Loadsharing feature must be on before this command can be entered. The GTT Load Sharing with Alternate Routing Indicator (GTT LS ARI) feature must be enabled to provision Alternate RI Mates.

If the Flexible GTT Loadsharing feature is enabled, use this command to create a new MRN set, or to add entries to an existing MRN set in the MRN table. If the Flexible GTT Loadsharing feature is turned on, then MRN sets are used.

Note:

If only the Intermediate GTT Loadsharing feature is turned on, the MRN table can contain a maximum of 3000 entries. If the Intermediate GTT Loadsharing feature is on and the Flexible GTT Loadsharing feature is enabled, 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. Check the rtrv-sccp-serv command output to see if entries exist in the SCCP-SERV table.

Note:

An MRN set is a logical grouping of PCs that already exist in the EAGLE MRN table. The Intermediate GTT Loadsharing feature allows PCs to be part of more than one load-sharing group, with each PC defined by a different MRN set. If the Intermediate GTT Loadsharing feature is enabled, then all existing entries in the MRN table and all existing GTA translations in the GTT table with ri=gtare stored in default MRN sets. Additional MRN sets can be provisioned, and GTT entries can be associated to the MRN sets.

Parameters

Note:

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

If a point code is being added to an existing weighted entity set, and the dfltwt parameter is not specified, the wt1/wt2/wt3/wt4 parameter must be specified. The wt1/wt2/wt3/wt4 parameter can only be specified if at least two of the rc/rc1/rc2/rc3/rc4 parameters are equal, creating a weighted entity set.

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

dfltwt (optional)

Default weight. The weight to be assigned to a specified PC that is not assigned a weight with the wt/wt1/wt2/wt3/wt4 parameter.

Note:

If a PC weight is specified with the wt/wt1/wt2/wt3/wt4 parameter and the dfltwt parameter is specified, the default weight is ignored, and the PC is assigned the weight specified by its respective weight parameter.

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)

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 the Alternate RI Mate search is performed.

Range:: 1 - 36000, dflt
dflt—default MAP Set

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

mapssn (optional)

Alternate RI Mate subsystem number.

Range:: 2 - 255, *, none
Default:: none

mrnset (optional)

MRN set ID.

Range:

1 - 3000, dflt, new

dflt—default MRN set

new—create a new 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:

0-255

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

zone—0–7

area—000–255

id—0-7

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

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)

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)

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)

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

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

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. The Weighted GTT Loadsharing feature must be turned on before this parameter can be specified.

Note:

If a threshold value is not specified when creating a new RC group in an existing entity set, the new RC group is assigned a threshold value of 1%.

Range:: 1 - 100

wt (optional)

Weight. The weight assigned to the primary PC.

Note:

If PCs are being added to an existing entity set, the wt parameter cannot be specified. If a new entity set is being created, the wt parameter can only be specified if at least two of the specified RC values are equal, which creates 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. The Weighted GTT Loadsharing feature must be turned on before this parameter can be specified.

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

This example enters point code 1 into the MRN table with a relative cost of 10 and associates point code 1 with it as a point code with a relative cost of 20.

ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=20

This example updates the group containing point code 1 in the MRN table, to add point code 1 with relative cost of 20 and point code 1 with relative cost of 30 to the group.

ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=20:pc2=1-1-10:rc2=30

These examples include spare point codes:

ent-mrn:pci=s-2-2-1:rc=10:pci1=s-2-2-2:rc1=11:pci2=2-100-1:rc2=12

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

ent-mrn:pc=1-1-1:rc=10:pc1=1-1-2:rc1=10:mrnset=dflt

ent-mrn:pc=1-1-1:rc=10:pc1=1-1-2:rc1=20:pc2=1-1-3:rc2=30:apc3=1-1-4:rc3=40:apc4=1-1-5: rc4=50:mrnset=new

ent-mrn:pc=1-1-3:pc1=1-1-6:rc1=60:pc2=1-1-7:rc2=70:mrnset=111

These examples create a new weighted entity set:

ent-mrn:pc=1-1-0:rc=10:wt=30:pc1=1-1-1:rc1=10:wt1=10

ent-mrn:pc=1-1-0:rc=10:wt=30:pc1=1-1-1:rc1=10:wt1=10:thr=50

ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=10:pc2=1-3-2:rc2=20:wt2=30:pc3=1-10-2: rc3=20:dfltwt=20

ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=10:wt1=30:pc2=1-3-2:rc2=10:dfltwt=20:thr=60

ent-mrn:pc=1-1-0:pc1=2-2-2:rc1=20:pc2=1-1-10:rc2=30:pc3=1-3-2:rc3=10:wt3=20: dfltwt=30

ent-mrn:pc=1-1-0:pc1=2-2-2:rc1=20:wt1=10:pc2=1-1-10:rc2=20:wt2=40:thr=30

ent-mrn:pc=1-1-0:pc1=2-2-2:rc1=20:wt1=40:pc2=1-1-10:rc2=20:pc3=1-3-2:rc3=20: dfltwt=25:thr=30

ent-mrn:pc=1-1-0:pc1=2-2-2:rc1=20:wt1=10:pc2=1-1-10:rc2=30:wt2=40

ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=20:pc2=1-1-10:rc2=30:mapset=1: mappc=2-1-1:mapssn=*

ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=20:pc2=1-1-10:rc2=30:mappc=2-1-1:mapssn=*

ent-mrn:pci=1-001-0:rc=10:pci1=1-001-1:rc1=20:pci2=1-001-10:rc2=30:mapset=1: mappcn=00126:mapssn=12

ent-mrn:pcn16=1-14-0:rc=10:wt=30:pcn161=40-2-3:rc1=10:wt1=10:mrnset=dflt

Dependencies

The Intermediate Global Title Translation Loadsharing 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 point code parameter is specified, its relative cost parameter must be specified.

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.

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

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.

One or more point codes in the command will exceed the maximum number of point codes that can be entered into the MRN table (3000 if the IGTTLS feature is turned on and 6000 if the IGTTLS and FGTTLS features are turned on)..

The Flexible GTT Load-Sharing feature must be enabled before the mrnset parameter can be specified.

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

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

When creating a new weighted entity set, the mrnset=new or mrnset=dflt parameter must be specified.

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

The Weighted GTT Loadsharing feature must be turned on before the wt/wt1/wt2/wt3/wt4, thr, and dfltwt parameters can be specified.

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

When creating or modifying a weighted entity set, the dfltwt parameter must be specified, or an individual weight must be specified for each PC.

Entity sets in a solitary or dominant loadsharing mode cannot have weights assigned to the PCs. When creating an entity set, if all of the RC values are unique, the wt/wt1/wt2/wt3/wt4 and thr parameters cannot be specified.

If the thr parameter is specified, the rc1, rc2, rc3, and rc4 parameters must be of equal value.

If the thr parameter is specified, the associated wt/wt1/wt2/wt3/wt4 parameter or the dfltwt parameter must be specified.

At least one additional point code must be specified.

Any specified point code must be a full point code.

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 SID table is corrupt or could not be found by the system.

If a new point code is being added to the MRN table, the pc and rc parameters must be specified together in the command.

If the Flexible GTT Loadsharing feature is enabled, and the mrnset=new parameter is specified, the pc and rc parameters must be specified together in the command.

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

If the pc1/pc2/pc3/pc4 parameter is specified, the pc parameter value must already exist in the MRN table.

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

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

If PCs are being added to a weighted entity set, the wt/wt1/wt2/wt3/wt4 parameter or the dftwt parameter must be specified.

If PCs are being added to a non-weighted entity set, the wt/wt1/wt2/wt3/wt4 and the dfltwt parameters cannot be specified.

At least one optional parameter must be specified.

If the wt/wt1/wt2/wt3/wt4 parameters are specified, the dfltwt parameter cannot be specified.

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/mappca/mappci/mappcn/mappcn24/mappcn16 parameter must be a full point code.

The point codes and alternate RI Mate point codes must have the same network type 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 specified MAPSET must already exist in the MAP table.

If the mapset parameter is specified, then the mappc and mapssn parameters must be specified.

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

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 STP point code.

The ent-mrn command cannot be used to change an Alternate RI Mate that has already been specified for an MRN Set. Use the chg-mrn command to modify the Alternate RI Mate.

SSN configured for SFAPP cannot be used in any command for any configuration

Notes

For the -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.

The EAGLE supports the following modes for nodes and 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.

The ent-mrn command cannot be used to change the relative cost value for a point code; the chg-mrn command must be used.

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

If the ent-mrn command is used to add PCs to an existing weighted entity set, and the threshold is specified, all RC group values specified with rc/rc1/rc2/rc3/rc4 parameters for the alternate post-GTT-translated point codes must be equal.

The following rules apply when the ent-mrn command is used to add PCs to RC groups:

If a threshold value is specified and the PCs are being added to an existing RC group in the existing entity set, the RC group threshold is changed to the specified threshold value and both pre-existing and new PCs in the RC group assume the new threshold value.
If a threshold value is specified and the PCs are creating a new RC group in the existing entity set, the new RC group assumes the specified threshold value.
If a threshold value is not specified and the PCs are being added to an existing RC group in the existing entity set, the RC group threshold does not change and the PC assumes the threshold value of the existing RC group.

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.

Entries cannot be provisioned in the MRN table unless routes are also provisioned for corresponding point codes. However, an entry without a configured route may result from upgrading to a new EAGLE release. If such an entry occurs, then traffic will not be routed to the corresponding point code. The entry can be deleted, or a route for the entry can be configured.

When a node is marked congested in the MRN or MAP table, traffic continues to be routed to that node. When the congested node becomes prohibited, traffic is diverted to another node.

Output


		  ent-mrn:pc=1-1-1:rc=10:pc1=1-1-2:rc1=20:pc2=1-1-3:rc2=30:apc3=1-1-4:rc3=40:apc4=1-1-5:
		  rc4=50: mrnset=new


    tekelecstp 11-03-04 12:59:14 EST  EAGLE 44.0.0
    ent-mrn:pc=1-1-1:rc=10:pc1=1-1-2:rc1=20:pc2=1-1-3:rc2=30:apc3=1-1-4:rc3=40:apc4=1-1-5: rc4=50:mrnset=new
    Command entered at terminal #4.
    ENT-MRN: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED

    New MRNSET Created : MRNSETID = 112
    ENT-MRN: MASP A – COMPLTD 
;


		  ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=10:mrnset=dflt:mapset=dflt:mappc=1-1-2:mapssn=10


    tekelecstp 11-03-04 12:15:32 EST  EAGLE 44.0.0
    ent-mrn:pc=1-1-0:rc=10:pc1=1-1-1:rc1=10:mrnset=dflt:mapset=dflt:mappc=1-1-2:mapssn=10
    Command entered at terminal #4.
    ENT-MRN: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
    ENT-MRN: MASP A - COMPLTD 
;

Related Topics