Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.7 E97335 Revision 1 |
|
![]() Previous |
![]() Next |
This procedure is used to change the attributes of a cluster point code in the database, using the chg-dstn
command.
Note:
Cluster entries can be provisioned only as ANSI destination point codes. Cluster entries cannot be provisioned for ITU international or ITU national destination point codes, and cannot be provisioned as a proxy point code. The ANSI alias point code for an ITU international or ITU national destination point code must be a full point code. An ANSI private point code must be a full point code.To add a new cluster point code to the database, perform the Adding a Cluster Point Code procedure.
To remove a cluster point code from the database, perform the Removing a Destination Point Code procedure.
The cluster point code to be changed must be in the database.
The chg-dstn
command uses these parameters:
:dpc/dpca
– The destination point code in the database being changed
Note:
See Point Code Formats for a definition of the point code types that are used on the EAGLE.Note:
Alias point codes (aliasi
/aliasn
/aliasn24
) and secondary point codes (spc
/spca
) cannot be specified for a cluster point code.:clli
– The Common Language Location Identifier assigned to this point code
:domain
– The network in which the destination entity or node exists- SS7.
:bei
– Broadcast exception indicator that indicates whether transfer-prohibited (TFP) messages will be broadcast from this node. The bei=yes
parameter means TFPs will not be broadcast. The bei=no
parameter means TFPs will be broadcast.
:ipgwapc
– (ANSI networks only)IP Gateway Adjacent Point Code indicator. Specify ipgwapc=yes
to provide SS7 linkset definition compatibility for gateway connections to IP-SCPs. The default is ipgwapc=no
.
:elei
– For cluster point codes only. Specifies whether or not the EAGLE maintains a dynamic status exception list for each cluster route that may be used to reach the member signaling points making up the cluster. The elei=yes
parameter means the EAGLE does not maintain an exception list for the cluster point code specified by the dpc
parameter. The elei=no
parameter means the EAGLE does maintain an exception list for the cluster point code specified by the dpc
parameter.
:ncai
– The nested-cluster-allowed indicator specifies whether or not the route to the cluster point code can be different from the route to a point code that is a member of the cluster point code. A point code is a member of a cluster point code if it has the same network identifier (NI) and network cluster (NC) values as the cluster point code. This parameter can be specified only for cluster point codes.
If the ncai
parameter value is yes
, the cluster point code is a nested cluster point code. Point codes that are members of this cluster point code can be assigned to routesets that are different from the routeset assigned to the cluster point code.
If the ncai
parameter value is no
, the cluster point code is not a nested cluster point code. Point codes that are members of this cluster point code must be assigned to the same routeset assigned to the cluster point code.
Refer to the Nested Cluster Routing section for more information on the nested cluster routing feature.
:nprst
- NM bits reset. This parameter specifies whether the NM bits in an ITU IAM message should be set to 00. This parameter has two values. off
- Do not set NM bits to 00 in an ITU IAM message if the nptype
option value in the rtrv-tifopts
output is nm
. on
- Set the NM bits to 00 in an ITU IAM message if the nptype
option value in the rtrv-tifopts
output is nm
. The default value for this parameter is off
.
:rcause
- Release cause. This parameter specifies the condition that triggers the sending of a Release message. This parameter has these values. none
- use the values specified for the rcausenp
and rcausepfx
parameters in the rtrv-tifopts
output. The default value for this parameter is none
.
If the rlcopc
parameter value in the rtrv-tipopts
output is on and a value of 0-127 is specified for the rcause
parameter, then the rcause
parameter value overrides the values specified for the rcausenp
and rcausepfx
parameters in the rtrv-tifopts
output.
:splitiam
- This parameter specifies how and when to split an ITU IAM message into one IAM message and one SAM message. This parameter has these values. none
- the value specified for the splitiam
parameter in the rtrv-tifopts
output is used to determine when to split the IAM message. The default value for this parameter is none
.
nprst
or rcause
parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam
parameter, at least one of these features must be enabled. The status of these features is shown in the rtrv-ctrl-feat
output. Perform the procedures in TIF User's Guide to enable these features.
:sccpmsgcnv
- The sccpmsgcnv
parameter controls SCCP UDT(S)/XUDT(S) message conversion for the specified destination. This parameter can be specified only if the XUDT UDT Conversion feature is enabled and turned on. The rtrv-ctrl-feat
output shows the status of the XUDT UDT Conversion feature. If the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature. This parameter contains these values. The chg-dstn
command also contains the homescp
and homesmsc
parameters. The values for these parameters are yes
and no
. The value no
is the system default value for these parameters. The value yes
for these parameters cannot be specified for a cluster point code. To specify the value yes
for these parameters, perform the Adding a Destination Point Code or Changing a Destination Point Code procedures.
The value of the clli
parameter cannot be in the DPC table and cannot match the CLLI of the EAGLE. Verify this by entering the rtrv-dstn
and the rtrv-sid
commands, shown in 1 and 3. If the value of the clli
parameter matches any CLLI values in either of these outputs, choose another value for the clli
parameter that does not match any CLLIs shown in either of these command outputs.
If a nested cluster point code is changed to a non-nested cluster point code (the value of the ncai
parameter is changed from yes
to no
), any point codes that are members of this point code must be assigned to the same routeset as the cluster point code.
The elei
(exception list exclusion indicator) parameter can be specified only for a cluster destination point code. Cluster destination point codes and the elei
parameter can be specified only if the Cluster Routing and Management Diversity feature is turned on. Verify this with the rtrv-feat
command. If the Cluster Routing and Management Diversity feature is turned on, the CRMD
field should be set to on
. If the Cluster Routing and Management Diversity feature is not turned on, enter the chg-feat:crmd=on
command. For more information on the Cluster Routing and Management Diversity feature, refer to the Cluster Routing and Management Diversity (CRMD) section.
The ncai
parameter can be specified only if the Nested Cluster Routing feature is on. This can be verified with the entry NCR = on
in the rtrv-feat
command output. If the nested cluster routing feature is not turned on, enter the chg-feat:ncr=on
command. For more information on the nested cluster routing feature, refer to the Nested Cluster Routing section.
Note:
Once the Cluster Routing and Management Diversity and nested cluster routing features are turned on with thechg-feat
command, they cannot be turned off. The Cluster Routing and Management Diversity and nested cluster routing features must be purchased before you turn these features on with the chg-feat
command. If you are not sure if you have purchased the Cluster Routing and Management Diversity and nested cluster routing features, contact your Sales Representative or Account Representative.
The examples in this procedure are used to change the attributes of the cluster point code 030-003-*.
Canceling the RTRV-DSTN
and RTRV-RTE
Commands
Because thertrv-dstn
and rtrv-rte
commands used in this procedure can output information for a long period of time, the rtrv-dstn
and rtrv-rte
commands can be canceled and the output to the terminal stopped. There are three ways that the rtrv-dstn
and rtrv-rte
commands can be canceled:
F9
function key on the keyboard at the terminal where the rtrv-dstn
or rtrv-rte
command was entered. canc-cmd
without the trm
parameter at the terminal where the rtrv-dstn
or rtrv-rte
command was entered. canc-cmd:trm=<xx>
, where <xx>
is the terminal where the rtrv-dstn
or rtrv-rte
command was entered, from another terminal other than the terminal where the rtrv-dstn
or rtrv-rte
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-26 Changing the Attributes of a Cluster Point Code
Sheet 1 of 4
Sheet 2 of 4
Sheet 3 of 4
Sheet 4 of 4