4.113 chg-rte
Use this command to change the “cost,” or priority of a route. The cost is based on whether this route is first choice, second choice, and so on. Prioritize routes in such a way that the most direct route (fewest intermediate signaling points) is highest priority.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- lsn (mandatory)
- Linkset name. The name of the linkset associated with the route.
Note:
The linkset name must be unique.
- dpc (optional)
- ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- dpca
- Range:
- p-, 000-255, *
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
The asterisk value (*) is not valid for the ni subfield.
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- dpci (optional)
- ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- dpcn (optional)
- ITU national 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:npcfmtiflexible 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, private point code, or private and 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). The prefix subfield indicates a private point code.
- dpcn16 (optional)
- 16-bit ITU national point code with subfields unit number sub number area main number area (un-sna-mna). The prefix subfield indicates a private point code.
- force (optional)
- This parameter allows the NLSN to be same as the ILSN in the exception routes of the destination or allows APC to be same as OPC in the exception routes of the destination.
Example
chg-rte:lsn=rlgh03:rc=0:dpc=244-003-001
chg-rte:dpc=25-*-*:lsn=myls:rc=10
This example changes route for DPCN 4084-aa using linkset E1M2ITUN to relative cost of 30:
chg-rte:dpcn=4085-aa:lsn=e1m2itun:rc=30
This example changes route for DPCN24, 10-100-14 using linkset WE123624 to a relative cost of 2:
chg-rte:dpcn24=10-100-14:lsn=we123624:rc=25
This example changes route for private point code DPC p-1-1-1 using linkset WE123642 to relative cost of 50:
chg-rte:dpc=p-1-1-1:lsn=we123642:rc=50
This example changes route for spare point code DPCN s-4085-aa using linkset E1M2ITUN to relative cost of 30:
chg-rte:dpc=s-4085-aa:lsn=e1m2itun:rc=30
This example changes route for private point code DPCN24 p-1-100-1 using linkset WE123624 to relative cost of 25:
chg-rte:dpcn24=p-1-100-1:lsn=we123624:rc=25
This example changes route for private and spare point code DPCI ps-1-104-1 using linkset E1M2ITUI to relative cost of 30:
chg-rte:dpci=ps-1-104-1:lsn=e1m2itui:rc=30
This example changes route for DPCN16, 121-10-15 using linkset WE123624 to a relative cost of 10:
chg-rte:dpcn16=10-100-14:lsn=we123624:rc=10
Dependencies
The 6-Way Loadsharing on Routesets feature must be turned on before more than 2 routes can be provisioned with the same relative cost.
If the ipgwapc=yes parameter is specified, then the associated dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot have a cluster route assigned.
If the identity of a route is being changed because of a change in the linkset name, the database must not already contain the new linkset name and destination address.
If the nlsn parameter is specified, the link set must already exist in the database and at least one link must be assigned to the link set.
If a new linkset name (nlsn parameter) is specified for an existing destination network address (ni-*-*), or destination network cluster address (ni-nc-*), the linkset type used in the route (see the chg-ls command) must be b, c, or d.
If the specified destination address is a full point code address (ni-nc-ncm) and is a member of a provisioned cluster (ni-nc-*), whether the attributes of the ordered routes assigned to the cluster can be changed is determined by the destination address’s NCAI (Nested Cluster Allowed Indicator). The NCAI is set with the ncai parameter of the ent/chg-dstn commands.
- If the ncai=no parameter is specified, the cluster point code is not a nested cluster point code and the attributes of the ordered routes assigned to the cluster cannot be changed.
- If the ncai=yes parameter is specified, the specified destination address is a member of a provisioned nested cluster where the attributes of the ordered routes assigned to the cluster can be changed.
If the specified destination address is a network cluster address (ni-nc-*), how the attributes of the specified ordered route are changed is determined by the setting of the destination address’s NCAI.
- If the ncai=no parameter is specified, the attributes of the specified ordered route are changed for each signaling point code having the same network identifier (ni) and network cluster (nc) codes.
- If the ncai=yes parameter is specified, the specified destination address is a nested cluster where changing the attributes of the ordered routes for the cluster does not affect the attributes of the ordered routes of the provisioned members.
The route destination’s type must match the route’s linkset adjacent point code or the route’s linkset secondary adjacent point code type.
Only IPGW routes are allowed for private point codes.
If the dpcn parameter is specified, its format must match the format that was assigned with the chg-stpopts:npcfmti parameter.
Network routing is valid only if the NRT feature is on.
When using network routing, if the destination point code has a value of * in the nc field, the ncm field must also be * (for example, dpc=21-*-*).
The Route table is corrupt or cannot be found.
The Linkset table is corrupt or cannot be found.
The nda, nz, nlsn, or nrc parameter must be specified.
The current destination address must be a full or a cluster point code.
All linksets that are currently assigned to a route set must still be equipped.
The linkset specified by the lsn parameter must exist in the routeset of the destination table entry.
If a new link set (nlsn parameter) is specified in the command, that link set name must exist in the active LINK SET entity.
The specified DPC must be in the database.
Only a single route is allowed for an APC or SAPC for an IPGWx linkset. The changed route must include the APC or SAPC’s IPGWx linkset with the destination equal to the APC or SAPC.
If a proxy linkset is used, then the nlsn parameter cannot be specified.
If a proxy linkset is used, then the value specified for the dpc parameter cannot be a network cluster address (ni-nc-*) or network address (ni-*-*).
The network type of the routeset must be same as the network type of the destination point code.
The value specified for the rc parameter must differ from the original routing cost of the associated linkset.
If the value specified for the dpc parameter refers to a Proxy Point Code in the Destination table, then the nlsn parameter cannot be specified.
The SAPC table is corrupt or cannot be found.
Notes
In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-) and the private and spare point code subtype prefix (ps-). All of the point code types support the private (internal) point code subtype prefix (p-).
Output
chg-rte:lsn=rlgh03:rc=0:dpc=244-003-001
rlghncxa03w 04-01-07 11:43:04 EST EAGLE 31.3.0
CHG-RTE: MASP A - COMPLTD
;
Related Topics