chg-appl-rtkey

4.36 chg-appl-rtkey

Use this command to change static entries in the Routing Key table. Only one attribute can be changed at a time.

Parameters

Note:

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

Note:

See Table A-4 for valid CIC values for specified SI and MSU types.

cice (optional)

The end range of circuit identification codes assigned to the routing key. The cice and cics parameters identify the routing key to be changed.

Range:: 0 - 4294967295

cics (optional)

The start range of circuit identification codes assigned to the routing key. The cics and cice parameters identify the routing key to be changed.

Range:: 0 - 4294967295

dpc (optional)

ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:: dpca

dpc/dpca/dpci/dpcn/dpcn24/dpcn16 (optional): Destination point code.

dpci (optional): ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)

dpcn (optional): ITU national destination 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).

dpcn24 (optional): 24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

dpcn16 (optional)

16-bit ITU national point code with subfields unit number--sub number area--main number area (un-sna-mna).

Range:: un--000--127; sna--000--15; mna--000--31

ncics (optional)

The new start range of circuit identification codes assigned to the routing key. Specify the ncics and/or ncice parameter to change the range of the circuit identification codes assigned to the routing key.

Range:: 0 - 4294967295

ncice (optional)

The new end range of circuit identification codes assigned to the routing key. Specify the ncice and/or ncics parameter to change the range of the circuit identification codes assigned to the routing key.

Range:: 0 - 4294967295

nrcontext (optional)

This parameter modifies the routing context value assigned to this routing key.

Routing context is mandatory for routing keys associated with SUA Application Servers. Routing context is optional for routing keys associated with M3UA Application Servers.

An AS can be associated with only 1 routing key with routing context. An AS can be associated with multiple routing keys that do not contain routing context. An AS cannot be simultaneously assigned to a routing key with routing contexts and to routing keys without routing contexts.

Range:: 0 - 4294967295

opc (optional)

ANSI originating point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

opca

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.

opc/opca/opci/opcn/opcn24/opcn16 (optional): Originating point code. Valid only (and required) if si=4, 5, or 13.

opci (optional): ITU international originating point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)

opcn (optional): ITU national originating 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).

opcn24 (optional): 24-bit ITU national originating point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

opcn16 (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

rcontext (optional)

This parameter specifies a routing key by its routing context when a routing key needs to be changed as an alternative to entering the dpc/si/ssn/opc/cics/cice/type parameters.

Split operations are invalid for routing keys with routing context.

Range:: 0 - 4294967295

si (optional)

The service indicator.

Range:: 0-15 or equivalent text values:; Number =Text—Description; 0=snm—Signaling network management messages; 1=regtest—Signaling network testing and maintenance regular; 2=spltest—Signaling network testing and maintenance special; 3= sccp —SCCP; 4= tup —Telephone user part; 5= isup —ISDN user part; 13= qbicc; See Table A-4 and Table 4-2 for valid si values in combination with other parameters.

split (optional)

The CIC value where the routing key with the specified CICS and CICE range will be split. The specified routing key is split into two entries with adjacent CIC ranges. The existing routing key retains the range of CICs that is lower than the split value. The value of split minus 1 is used as the end range for this entry. The range of CICs assigned to the original entry is the values of cics to split minus 1.

A new routing key entry is created with the high end of the original range. The split value is used as the start of the CIC range for this entry. The range of CICs assigned to the new entry is the values of split to cice.

This parameter is valid only if si=4, 5, or 13 and is not valid with ncics or ncice. See Table A-4 and Table 4-2.

Range:: 0 - 16363

ssn (optional)

Subsystem number.

Range:: 0 - 255

type (optional)

Type of routing key.

Range:

full
default
partial

Default:

full

Example

chg-appl-rtkey:dpc=123-230-245:si=5:opc=123-230-244:cics=1:cice=100:split=50

chg-appl-rtkey:dpc=123-230-245:si=5:opc=123-230-244:cics=1:cice=50:ncice=100

chg-appl-rtkey:dpcn24=10-100-10:si=5:opcn24=10-100-11:cics=1:cice=100:ncice=200

chg-appl-rtkey:dpc=8-8-8:si=3:ssn=5:rcontext=500

chg-appl-rtkey:dpci=s-3-11-1:si=5:opci=s-4-11-1:cics=1:cice=1000:ncice=500

chg-appl-rtkey:rcontext=5:ncice=100

chg-appl-rtkey:rcontext=1:nrcontext=2

chg-appl-rtkey:dpcn16=121-10-15:si=5:opcn16=121-10-15:cics=1:cice=50:ncice=100

Dependencies

Optional parameters that must be specified with the chg-appl-rtkey command depend on the type of routing key being changed. See Table 4-2 for valid parameter combinations.

For SS7IPGW and IPGWI applications running on E5-ENET-B cards, there is a limit of 2500 routing keys in the system. The srkq parameter (see the chg-sg-opts command) limits the maximum number of static routing keys that can be provisioned with the ent-appl-rtkey command.

The subsystem number is mandatory and valid only when the si=3 (or sccp) parameter is specified; if the si parameter does not equal 3 (or sccp), the ssn parameter cannot be specified.

The value entered for the starting circuit identification code (cics) must be less than or equal to the value entered for the ending circuit identification code (cice).

The value entered for the new starting circuit identification code (ncics) must be less than or equal to the value entered for the new ending circuit identification code (ncice).

A circuit identification code range (cics to cice) cannot be specified that overlaps an existing routing key.

When si=4, 5, or 13 (or tup, isup, or qbicc), the opc, cics, and cice parameters are required. The opc, cics, and cice parameters can be specified only if si=4, 5, or 13.

The value entered for the split parameter must be greater than the value entered for the cics parameter and less than or equal to the value entered for the cice parameter.

The value entered for the ncics parameter must be less than or equal to the value entered for the cice parameter when the ncice parameter is not specified.

The value entered for the ncice parameter must be greater than or equal to the value entered for the cics parameter when the ncics parameter is not specified.

The si parameter must have a value of 4, 5, or 13 (or tup, isup, or qbicc) before the split, ncics, and ncice parameters can be specified.

A DPC/SI routing key must be specified when the DPC is ANSI and the si=4 parameter is specified (TUP is used only in an ITU network).

Table A-4 shows valid CIC values for SI types 4, 5, and 13.

Partial point codes are not allowed; no asterisks can be specified in the point codes in the command.

Mixed point code types are not allowed; opc and dpc types must match.

If the type=partial or type=default parameter is specified, then the split and resize parameters cannot be specified.

If the type=default parameter is specified, then the dpc, si, ssn, opc, cics, and cice parameters cannot be specified.

When the type=full parameter is specified, the dpc and si parameters must be specified.

The following types of partial routing keys are supported:

DPC-SI-OPC (ignore CIC) can be used as a partial match key for CIC- based traffic.
DPC-SI (ignore all other fields) can be used as a partial match key for CIC- based traffic or SCCP traffic.
DPC only (ignore all other fields) can be used as a partial match for any type of traffic.
SI only (ignore all other fields) can be used as a partial match for any type of traffic.

If the rcontext parameter is specified, then the split, ncics and ncice parameters cannot be specified.

The rcontext parameter must be specified for routing keys that are associated with SUA Application Servers.

The specified rcontext parameter value must already exist in the database.

If specified, the service indicator parameter must be si=3 for routing keys that are associated with SUA Application Servers.

An AS cannot be simultaneously assigned to a routing key with routing contexts and routing keys without routing context. To assign an M3UA or SUA association to multiple routing keys with routing context, the M3UA/SUA association must be assigned to more than one AS, and each AS must be assigned to a routing key with routing context.

The AS name and parameters specified for a routing key must use an address format that is valid for the adapter type assigned to the AS.

The routing context value should be unique.

Table 4-2 Valid Parameter Combinations for chg-appl-rtkey Routing Key Types

Action	dpc	si	ssn	opc	cics	cice	ncics	ncice	split	type
Split CIC Range	X	X		X	X	X			X	full
Re-size CIC Range	X	X		X	X	X	X	X		full
Socket Name Override (SI=ISUP or 5)	X	X		X	X	X				full
Socket Name Override (SI = SCCP or 3)	X	X	X							full
Socket Name Override (SI = not 3, 4, 5, or 13)	X	X								full
Socket Name Override (SI = 4, 5, or 13)	X	X		X						partial
Socket Name Override (SI = 3, 4, 5 or 13)	X	X								partial
Socket Name Override SI-only key		X								partial
Socket Name Override DPC-only key	X									partial
Socket Name Overrride Default key										default

The value of the nrcontext parameter cannot be changed for a routing key if the rcontext parameter has not been configured for that routing key.

The attributes that are required to change a routing key must be specified in the command.

The maintenance data must be accessible.

J7 support feature must be enabled before the dpcn16/opcn16 parameter can be specified.

The opc, cics, and cice parameters can be specified with the si parameter only if the si parameter has a value of 4, 5, or 13 (or tup, isup, or qbicc).

Notes

A routing key entry associates a routing key with a socket name or Application Server (AS) name.

The dpc, si, ssn, opc, cics, and cice parameters are used to identify the routing key to be changed.

The split, ncics, and ncice parameters are used to specify new values for the routing key.

The opc, cics, and cice parameters are not required for partial routing keys.

The cics, cice, ncice, ncice, and split parameters are required when si=4 and ITU DPCs (dpci, dpcn) are specified. These parameters are not valid when an ANSI DPC (dpc, dpca) is specified and si=4.

The following changes can be made for routing keys. Only one of these changes is allowed per command.

A routing key can be split into two entries with adjacent CIC ranges. The resulting entries retain the socket associations of the original entry.
The range of CICs assigned to a routing key can be changed as long as it does not overlap another routing key. The new entry retains the socket associations of the original entry.

Group codes are required for ITU-N point codes (DPCN/OPCN) when the Duplicate Point Code feature is turned on.

Routing context is a routing key parameter that uniquely identifies routing keys. Routing context is mandatory for routing keys associated with SUA Application Servers and optional for routing keys associated with M3UA Application Servers.

An AS cannot be simultaneously assigned to a routing key with routing contexts and routing keys without routing contexts.

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

Output

chg-appl-rtkey:dpc=123-230-245:si=3:ssn=250:nsname=socket5


    rlghncxa03w 04-01-28 08:50:12 EST  EAGLE 31.3.0
    CHG-APPL-RTKEY: MASP A - COMPLTD 
;

dlt-appl-rtkey

ent-appl-rtkey

rtrv-appl-rtkey