| Oracle® Communications EAGLE Database Administration - GTT User's Guide Release 46.7 E97332-02 |
|
 Previous |
 Next |
| Oracle® Communications EAGLE Database Administration - GTT User's Guide Release 46.7 E97332-02 |
|
|
Previous |
Next |
This procedure is used to provision a solitary mated
application in the database using the
ent-map command. A solitary mated
application contains only one entry. The
ent-map command use these parameters to
provision a solitary mated application.
:pc/pca/pci/pcn/pcn24 –
The point code of the 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 the 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 point code that is to receive the message. The
value for this parameter is 2 to 255.
: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.
: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.
new – to assign the
mated application to a new MAP set.
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-38.
Table 2-38 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 |
Note:
pci), the network
type of the MRN point code parameter can be either ITU-I
(mappci) or ITU-N (mappcn).
pcn), the network
type of the MRN point code parameter can be either ITU-I
(mappci) or ITU-N (mappcn).
: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. The default value for ANSI, ITU-I, and ITU-N
solitary mated applications is
yes. The default value for ITU-N24
solitary mated applications is
no.
: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. The default
value for ANSI solitary mated applications is
yes. The default value for ITU
solitary mated applications is
no.
The
ent-map command also contains other
parameters that can be used to provision mated applications, but cannot be used
to provision a solitary mated applications. These parameters are:
mpc/mpca/mpci/mpcn/mpcn24,
mssn,
rc,
materc. If you wish to use these
parameters to provision mated applications, perform one of these procedures.
The
rc parameter can be specified for a
solitary mated application, but since a solitary mated application contains
only one entry, the
rc parameter does not need to be
specified. If the
rc parameter is not specified, the
rc value is set to 10.
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 solitary
mated application. If you wish to use these parameters to provision a mated
application, perform one of these procedures:
If the Flexible GTT Load Sharing feature is not enabled, the point code and subsystem number combination can be in the database only once. If the Flexible GTT Load Sharing feature is enabled, the point code and 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 command (pc/pca,
pci,
pcn, or
pcn24) 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 solitary 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 and 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 the EAGLE's ANSI true point code. The LNP feature must be enabled for a quantity greater than zero.
A mated application containing the INP subsystem can contain only the EAGLE’s true14-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 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 of the EAGLE’s true point codes. 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 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-39
shows the numbers of entries that can be provisioned based on the type of point
code.
Table 2-39 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 |
The format of the point codes in the CSPC group specified
with the
grp parameter must be the same as the
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.
If the
grp and
sso parameter values are specified, and
the specified point code and SSN is assigned to multiple mated applications,
the
grp 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 values of the
ssn parameter must be from 2 to 255.
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 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>
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-51 Provision a Solitary Mated Application - Sheet 1 of 11
Figure 2-52 Provision a Solitary Mated Application - Sheet 2 of 11
Figure 2-53 Provision a Solitary Mated Application - Sheet 3 of 11
Figure 2-54 Provision a Solitary Mated Application - Sheet 4 of 11
Figure 2-55 Provision a Solitary Mated Application - Sheet 5 of 11
Figure 2-56 Provision a Solitary Mated Application - Sheet 6 of 11
Figure 2-57 Provision a Solitary Mated Application - Sheet 7 of 11
Figure 2-58 Provision a Solitary Mated Application - Sheet 8 of 11
Figure 2-59 Provision a Solitary Mated Application - Sheet 9 of 11
Figure 2-60 Provision a Solitary Mated Application - Sheet 10 of 11
Figure 2-61 Provision a Solitary Mated Application - Sheet 11 of 11
