ent-rte

Use this command to add a route to the system.

Caution:

When using the Network Routing feature, limited network management is provided for point codes not covered by full point code routing, Cluster Routing, or Nested Cluster Routing.

Parameters

Note:

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

lsn (mandatory)

The linkset name associated with this route.

Range:: ayyyyyyyyy
1 alphabetic character followed by 9 alphanumeric characters

rc (mandatory)

The relative cost of the route

Range:: 0 - 99

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=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.

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

dpci (optional)

ITU international 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).

Range:

s-, p-, ps-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-, p-, ps

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

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: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, 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).

Range:

s-, p-, ps-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-, p-, ps

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

dpcn24 (optional)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix indicates a private point code (prefix-msa-ssa-sp).

Range:

p-, 000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—p

msa—000–255

ssa—000–255

sp—000–255

dpcn16 (optional)

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

Range:: p--, 000---127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; prefix---p; un---000---127; sna---000---15; mna---000---31

force (optional)

This parameter allows a route to be added to the database even if the linkset to be assigned to the route does not have any signaling links in it.

Range:: yes

Example

Adds route for DPC 1 to linkset WE123642:

ent-rte:dpc=1-1-1:lsn=we123642:rc=25

Adds route for DPC 21-*-* to linkset WE123642:

ent-rte:dpc=21-*-*:lsn=we123642:rc=25

Adds route for DPCN24 10-100-14 to linkset WE123624:

ent-rte:dpcn24=10-100-14:lsn=we123624:rc=10

Adds route for private DPC p-1-1-1 to linkset WE123642:

ent-rte:dpc=p-1-1-1:lsn=we123642:rc=25

Adds route for private and spare DPCN ps-4082-ge to linkset E1NITUN:

ent-rte:dpc=ps-4082-ge:lsn=e1ntitun:rc=10

Adds route for private DPCN24 p-10-100-14 to linkset WE123642:

ent-rte:dpcn24=p-10-100-1:lsn=we123642:rc=10

Adds route for private and spare DPCI s-1-100-1 to linkset UE123642:

ent-rte:dpci=s-10-100-1:lsn=ue123642:rc=10

Adds route for DPCN16 121-10-15 to linkset WE123642:

ent-rte:dpcn16=121-10-15:lsn=we123642:rc=10

Dependencies

The value of the lns parameter must exist in the STP database.

The DPC must be in the Destination Point Code table.

The destination point code of a route must be a full point code (ni-nc-ncm), a cluster point code (ni-nc-*), or a network point code (ni-*-*).

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 ordered routes can be assigned is determined by the destination address’s NCAI (nested cluster allowed indicator). The ncai=yes/no parameter is set with the ncai parameter of the ent/chg-dstn commands.

If the ncai=no parameter is specified, destinations comprising a cluster inherit their ordered routes from the cluster.
If the ncai=yes parameter is specified, then the destination address is a member of a provisioned nested cluster where ordered routes can be assigned to a provisioned member.

If the specified destination address is a network cluster address (ni-nc-*), the assignment of the specified ordered route attributes is determined by the setting of the destination address’s NCAI (nested cluster allowed indicator). The ncai=yes/no parameter is set with the ncai parameter of the ent/chg-dstn commands.

If the ncai=no parameter is specified, the collection of signaling point codes having the same network identifier (the ni parameter) and network cluster (the nc parameter) code are assigned the specified ordered route.
If the ncai=yes parameter is specified, then the specified destination is a network cluster address where provisioned members’s signaling point codes can be assigned the same or different ordered routes from the cluster.

If the dpcn parameter is specified, the format of the point code(s) must match the format that was assigned with chg-stpopts:npcfmti.

The dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot be specified with a private point code (-p) unless the route is an IPGW route.

The route destination’s type must match the route’s linkset adjacent point code or the route’s linkset secondary adjacent point code type.

If the ipgwapc=yes parameter is specified for the linkset, then the associated dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot have a cluster route assigned.

The linkset must be defined with at least one link. To override this requirement, specify force=yes.

The 6-Way Loadsharing on Routesets feature must be turned on before more than 2 routes can be provisioned with the same relative cost.

A linkset can be entered only once as a route for each destination or for a routeset.

If the specified destination address is a network address (ni-*-*), or network cluster address (ni-nc-*), the linkset type (see the chg-ls command) used in the route must be b, c, or d.

All routes with ANSI DPCs must use ANSI linkset APCs. A route with an ITU-I DPC can go over an ITU-N APC and an ITU-N DPC can go over an ITU-I APC.

If the link set name (the lsn parameter) references a link set that has the ipgwapc=yes parameter specified, the DPC must not be a cluster route.

The NRT feature must be turned on before the dpc/dpca parameter can be specified using the asterisk (*) in the nc or ncm subfields.

When using network routing, if the DPC 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 STP Site ID table is corrupt or cannot be found.

The Linkset table is corrupt or cannot be found.

The value of the dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot be the same as the EAGLE point code.

The value of the dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot be the same as the EAGLE capability point code.

The value of the dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot have already been assigned to an APC or SAPC for an IPGWx linkset. The entered route must include the APC or SAPC’s linkset with the destination equal to the APC or SAPC.

If dpcn is specified then the format of dpcn must match the format dictated by the chg-stpopts:npcfmti command

The ITU-N ordered route destination’s group code must match the route’s Link Set Adjacent PC’s group code for all linksets other than IPGWI and IPLHC.

The group code must match for all linksets because the ITU Duplicate Point Code feature is on.

All linksets in a routeset must have the same network type. The network type of the routeset must be the same as the network type of the destination point code.

If multiple routes are defined for the destination point code, and if a proxy point code is assigned to the destination point code, then the first route defined in the ent-rte command must use the proxy linkset.

If the dpc parameter has a network cluster address (ni-nc-*) or network address (ni-*-*), then the lst=prx 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

ent-rte:dpc=1-1-1:lsn=we123642:rc=25


    rlghncxa03w 04-01-07 11:11:28 EST  EAGLE 31.3.0
    ENT-RTE: MASP A - COMPLTD 
;

4.334 ent-rte