Oracle® Communications EAGLE Database Administration - GTT User's Guide Release 46.7 E97332-02 |
|
![]() Previous |
![]() Next |
This procedure is used to provision a dominant mated
application in the database using the
ent-map
and
chg-map
commands. A dominant mated
application is a mated application containing entries whose RC (relative cost)
values are unique. The
ent-map
and
chg-map
commands use these parameters
to provision a dominant 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 ANSI point 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 (CSPC) 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.
:mrc
– Message routing
under congestion – defines the handling of Class 0 messages during congestion
conditions. The value for this parameter is
yes
or
no
. The default value for ANSI
dominant mated applications is
yes
. The default value for ITU
dominant mated applications is
no
.
:srm
– Subsystem
routing messages – defines whether subsystem routing messages (SBR, SNR) are
transmitted between the 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. 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.
chg-map
command.
Refer to the Provisioning a MAP Set section for information on provisioning MAP sets.
: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-41.
Table 2-41 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 ( 2. If the network type of the MAP point code parameter is
ITU-N ( |
If the Weighted GTT Load Sharing feature is enabled,
shown by the columns
WT
,
%WT
, and
THR
in the
rtrv-map
output, the parameters
wt
,
mwt
, and
thr
cannot be specified for a dominant
mated application. If you wish to use these parameters to provision a mated
application, perform one of these procedures:
A dominant 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 dominant 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 dominant mated application using the
chg-map
command.
All the point codes and subsystems in a dominant mated application have different relative cost values, with the primary point code and subsystem having the lowest relative cost value. All traffic is routed to the primary point code and subsystem, if it is available. If the primary point code and subsystem becomes unavailable, the traffic is routed to highest priority backup point code and subsystem that is available. When the primary point code and subsystem becomes available again, the traffic is then routed back to the primary point code and subsystem.
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 or the EAGLE’s true point code. 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 is shown in the
PCA
,
PCI
,
PCN
, or
PCN24
fields of the
rtrv-sid
command output.
A dominant 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.
If the EAGLE’s true point code is specified in the mated application, it must be the primary point code. The relative cost value assigned to this point code must be the lowest value in the mated application. If the Flexible GTT Load Sharing feature is enabled, the mated application containing the EAGLE’s true point code can be assigned only to the default MAP set.
A mated application containing the LNP subsystem can
contain only ANSI point codes. The primary point code (pc
or
pca
) must be the EAGLE’s true ANSI
point code. The LNP feature must be enabled for a quantity greater than zero.
A mated application containing the INP subsystem can
contain only 14-bit ITU-N point codes, 14-bit ITU-N spare point codes, or
24-bit ITU-N point codes. The primary point code (pcn
or
pcn24
) must be the EAGLE’s true 14-bit
ITU-N point code, 14-bit ITU-N spare point code, or 24-bit ITU-N point code.The
INP or ANSI-41 INP Query feature must be enabled and turned on. The EAGLE can
contain either 14-bit ITU-N point codes (spare or non-spare point codes) or
24-bit ITU-N point codes. Both types of point codes cannot be present on the
EAGLE at the same time.
A mated application containing the EIR subsystem can
contain only ITU-I point codes, ITU-I spare point codes, 14-bit ITU-N point
codes, 14-bit ITU-N spare point codes, or 24-bit ITU-N point codes. The primary
point code (pci
,
pcn
, or
pcn24
) must be the EAGLE’s true ITU-I
point code, ITU-I spare point code, 14-bit ITU-N point code, 14-bit ITU-N spare
point code, or 24-bit ITU-N point code. The EIR feature must be enabled and
turned on. The EAGLE can contain either 14-bit ITU-N point codes (spare or
non-spare point codes) or 24-bit ITU-N point codes. Both types of point codes
cannot be present on the EAGLE at the same time.
A mated application containing the VFLEX subsystem can
contain any type of point code. The primary point code (pc
,
pca
,
pci
,
pcn
, or
pcn24
) must be the EAGLE’s true point
code. The V-Flex feature must be enabled and turned on.The EAGLE can contain
either 14-bit ITU-N point codes (spare or non-spare point codes) or 24-bit
ITU-N point codes. Both types of point codes cannot be present on the EAGLE at
the same time.
A mated application containing the ATINPQ subsystem can
contain only ANSI point codes, ITU-I point codes, ITU-I spare point codes,
14-bit ITU-N point codes, or 14-bit ITU-N spare point codes. The primary point
code (pc
,
pca
,
pci
, or
pcn
) must be the EAGLE’s true ANSI
point code, ITU-I point code, ITU-I spare point code, 14-bit ITU-N point code,
or 14-bit ITU-N spare point code. The ATINP feature must be enabled.
A mated application containing the AIQ subsystem can contain any of the EAGLE’s true point codes. The ANSI41 AIQ feature must be enabled. The EAGLE can contain either 14-bit ITU-N point codes (spare or non-spare point codes) or 24-bit ITU-N point codes. Both types of point codes cannot be present on the EAGLE at the same time.
The EAGLE can contain multiple entries that contain the
EAGLE's true point code, shown in the
rtrv-sid
output.
Table 2-42
shows the numbers of entries that can be provisioned based on the type of point
code.
Table 2-42 Maximum Number of True Point Code Entries
True Point Code Type | Maximum Number of Entries |
---|---|
ANSI |
1 - for the LNP subsystem 2 - one entry for the LNP subsystem and one entry for the AIQ subsystem 3 - one entry for the ATINPQ subsystem, one entry for the V-FLEX subsystem, and one entry for the AIQ subsystem The LNP subsystem cannot be used if the ATINPQ, EIR, INP, and V-FLEX subsystems are used. |
ITU-I |
4 - one entry for the ATINPQ subsystem, one entry for the EIR subsystem, one entry for the V-FLEX subsystem, and one entry for the AIQ subsystem |
ITU-N |
5 - one entry for the ATINPQ subsystem, one entry for the EIR subsystem, one entry for the INP subsystem, one entry for the V-FLEX subsystem, and one entry for the AIQ subsystem |
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 32 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 code and subsystem number combinations in a MAP set must be different.
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.
F9
function key on the keyboard at
the terminal where the
rtrv-map
command was entered.
canc-cmd
without the
trm
parameter at the terminal where
the
rtrv-map
command was entered.
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.
Figure 2-62 Provision a Dominant Mated Application- Sheet 1 of 17
Figure 2-63 Provision a Dominant Mated Application - Sheet 2 of 17
Figure 2-64 Provision a Dominant Mated Application - Sheet 3 of 17
Figure 2-65 Provision a Dominant Mated Application - Sheet 4 of 17
Figure 2-66 Provision a Dominant Mated Application - Sheet 5 of 17
Figure 2-67 Provision a Dominant Mated Application - Sheet 6 of 17
Figure 2-68 Provision a Dominant Mated Application - Sheet 7 of 17
Figure 2-69 Provision a Dominant Mated Application - Sheet 8 of 17
Figure 2-70 Provision a Dominant Mated Application - Sheet 9 of 17
Figure 2-71 Provision a Dominant Mated Application - Sheet 10 of 17
Figure 2-72 Provision a Dominant Mated Application - Sheet 11 of 17
Figure 2-73 Provision a Dominant Mated Application - Sheet 12 of 17
Figure 2-74 Provision a Dominant Mated Application - Sheet 13 of 17
Figure 2-75 Provision a Dominant Mated Application - Sheet 14 of 17
Figure 2-76 Provision a Dominant Mated Application - Sheet 15 of 17
Figure 2-77 Provision a Dominant Mated Application - Sheet 16 of 17
Figure 2-78 Provision a Dominant Mated Application - Sheet 17 of 17