Oracle® Communications EAGLE Database Administration - GTT User's Guide Release 46.7 E97332-02 |
|
![]() Previous |
![]() Next |
This procedure is used to change the relative cost
attributes of entries in an existing Mated Relay Node (MRN) group or MRN set
using
rc
/rc1
/rc2
/rc3
/
rc4
parameters of the
chg-mrn
command.
The
chg-mrn
command can also be used to add
point code entries to an existing MRN group or MRN set. This action is not
covered in this procedure. If you wish to add point code entries to an existing
MRN group or MRN set, perform
Provisioning MRN Entries
.
If you wish to assign the same weight and threshold value
to all the MRN entries in the MRN group or MRN set with the
eswt
and
thr
parameters, or to remove the weight
and threshold values from all the MRN entries in the MRN group or MRN set with
the
eswt=none
parameter, perform
Changing MRN Entries with the ESWT Parameter.
The
eswt
and
thr
parameters cannot be used in this
procedure.
If you wish to change individual weight values for MRN
entries with the
wt
/wt1
/wt2
/wt3
/wt4
parameters, the
weight values for an RC group with the
grpwt
parameter, the threshold values
for an MRN group or MRN set with the thr parameter, or the relative cost and
weight values for an MRN group or MRN set with the
force=yes
parameter, perform
Changing the Weight and Threshold Values of MRN Entries.
The
wt
/wt1
/wt2
/wt3
/wt4
,
grpwt
,
thr
, and
force=yes
parameters cannot be used in
this procedure.
If you wish to change the MAP set, MAP point code, and
MAP SSN values assigned to an MRN set, using the
mapset
,
mappc/mappca/mappci/mappcn/mappcn24
,
and
mapssn
parameters, perform
Changing the MAPSET, MAP Point Code, and MAP SSN Values of MRN Entries.
The
mapset
,
mappc/mappca/mappci/mappcn/mappcn24
,
and
mapssn
parameters cannot be used in
this procedure.
An MRN group or MRN set contains alternate point codes, up to 32, that are used for load sharing between multiple nodes when the EAGLE is performing intermediate global title translation. This load sharing is performed after intermediate global title translation is performed on the message. The point code in the message is changed to the selected point code in the MRN table. If the translated point code is not found in the MRN table, the translated point code in the message is not changed, the message is routed using route for the translated point code.
These parameters are used with the
chg-mrn
command in this procedure.
:pc/pca/pci/pcn/pcn24
–
The point code in the message after intermediate global title translation has
been performed.
:rc
– The relative cost
value of point code in the message
:pc1/pca1/pci1/pcn1/pcn241
– The first alternate point
code value
:rc1
– The relative cost
value of the first alternate point code
:pc2/pca2/pci2/pcn2/pcn242
– The second alternate point
code value
:rc2
– The relative cost
value of the second alternate point code
:pc3/pca3/pci3/pcn3/pcn243
– The third alternate point
code value
:rc3
– The relative cost
value of the third alternate point code
:pc4/pca4/pci4/pcn4/pcn244
– The fourth alternate point
code value
:rc4
– The relative cost
value of the fourth alternate 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.:mrnset
– The MRN set ID
that the MRN is assigned to, shown in the
rtrv-mrn
output. MRN set IDs are shown
only if the Flexible GTT Load Sharing feature is enabled. The
mrnset
parameter value cannot be
changed in this procedure. For more information on the Flexible GTT Load
Sharing feature, refer to
Flexible GTT Load Sharing.
The relative cost parameter values (rc
/rc1
/rc2
/rc3
/rc4
) determine how the global title translation load is
to be shared among the alternate point codes. There are three types of load
sharing that can be performed: dominant, load shared, or combined dominant/load
shared.
All the point codes in a dominant MRN group or MRN set have different relative cost values. The translated point code in the message is the preferred point code that the message is routed on. The relative cost value assigned to the preferred point code does not have to be the lowest value in the MRN group or MRN set. All traffic is routed to the preferred point code, if it is available. If the preferred point code becomes unavailable, the traffic is routed to highest priority alternate point code that is available. When the preferred point code becomes available again, the traffic is then routed back to the preferred point code. For example, the MRN table contains the following entries.
PC RC 005-005-005 10 006-001-001 20 006-001-002 30 006-001-003 40 006-001-004 50 006-001-005 60 006-001-006 70 006-001-007 80
If the preferred point code is 006-001-001 and it becomes unavailable, the traffic will be routed to point code 006-001-002.
All the point codes in a load shared MRN group have the same relative cost value. Traffic is shared equally between the point codes in this MRN group.
A combined dominant/load shared MRN group or MRN set is a combination of the dominant and load sharing MRN groups or MRN sets. A combined dominant/load shared MRN group or MRN set must contain a minimum of two entries with the same relative cost value and a minimum of one entry with a different relative cost value. Traffic is routed to the point code or point codes with the lowest relative cost value. If more than one point code has the lowest relative cost value, the traffic is shared between these point codes. If the point code or point codes with the lowest relative cost value become unavailable, traffic is routed to the point code or point codes with the next higher relative cost value. If more than one point code has this relative cost value, the traffic is shared between these point codes. For example, the MRN table contains the following entries.
PC RC 005-005-005 10 006-001-001 10 006-001-002 10 006-001-003 20 006-001-004 20 006-001-005 20 006-001-006 20 006-001-007 20
If the preferred point code is 006-001-001, the traffic is shared equally between point codes 005-005-005, 006-001-001, and 006-001-002. If point codes 005-005-005, 006-001-001, and 006-001-002 become unavailable, the traffic will be shared equally between point codes, 006-001-003, 006-001-004, 006-001-005, 006-001-006, and 006-001-007.
Canceling the
RTRV-MRN
Command
Because the
rtrv-mrn
command used in this procedure
can output information for a long period of time, the
rtrv-mrn
command can be canceled and
the output to the terminal stopped. There are three ways that the
rtrv-mrn
command can be canceled.
Press the
F9
function key on the keyboard at
the terminal where the
rtrv-mrn
command was entered.
Enter the
canc-cmd
without the
trm
parameter at the terminal where
the
rtrv-mrn
command was entered.
Enter the
canc-cmd:trm=<xx>
, where
<xx>
is the terminal where
the
rtrv-mrn
command was entered, from
another terminal other that the terminal where the
rtrv-mrn
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.
Figure 2-140 Change the Relative Cost Values of MRN Entries