Interface Commands

interface

Syntax

[no] interface ip-int-name

Context

config>router>mpls

Description

This command enables MPLS protocol support on an IP interface. MPLS commands are not executed on an IP interface where MPLS is not enabled.

The no form of this command deletes all MPLS commands that are defined under the interface, such as label-map. The interface must be shut down before it can be deleted. If the interface is not shut down, the no interface ip-int-name command issues a warning message on the console indicating that the interface is administratively up.

Default

shutdown

Parameters

ip-int-name

identifies the network IP interface. The interface name character string cannot be in the form of an IP address. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

admin-group

Syntax

[no] admin-group group-name [group-name...(up to 5 max)]

Context

config>router>mpls>interface

Description

This command associates admin groups with this interface. The admin group must already be defined in the config>router>if-attribute context (refer to the 7705 SAR Router Configuration Guide, ‟IP Router Command Reference”).

Up to five groups can be specified with one command. When an admin group is bound to one or more interfaces, its value cannot be changed until all bindings are removed.

When associated with MPLS interfaces, the interfaces can be included or excluded in the LSP path definition by matching on the admin-group name. CSPF will calculate a path that satisfies the admin-group include and exclude constraints.

The configured admin-group membership is applied in all levels or areas that the interface is participating in. The same interface cannot have different memberships in different levels or areas.

The admin groups bound to an MPLS interface are advertised area-wide in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.

The no form of this command deletes the association of this interface with one or more of the admin groups.

Default

no admin-group

Parameters

group-name

specifies the name of the group. The group names should be the same across all routers in the MPLS domain.

srlg-group

Syntax

[no] srlg-group group-name [group-name...(up to 5 max)]

Context

config>router>mpls>interface

Description

This command associates an MPLS interface with one or more SRLGs. The SRLG must already be defined in the config>router>if-attribute context (see the 7705 SAR Router Configuration Guide, ‟IP Router Command Reference”).

Up to five SRLGs can be specified with one command. When an SRLG is bound to one or more interfaces, its value cannot be changed until all bindings are removed.

When SRLGs are associated with MPLS interfaces, CSPF at an LER will exclude the SRLGs of interfaces used by the LSP primary path when calculating the route of the secondary path. CSPF at an LER or LSR will also exclude the SRLGs of the outgoing interface of the primary LSP path in the calculation of the path of the FRR backup LSP. This provides a path disjoint between the primary path and the secondary path or FRR backup path of an LSP.

The configured SRLG membership is applied in all levels or areas that the interface is participating in. The same interface cannot have different memberships in different levels or areas.

SRLGs bound to an MPLS interface are advertised area-wide in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.

The no form of this command deletes the association of this interface with one or more of the SRLGs.

Default

n/a

Parameters

group-name

specifies the name of the SRLG. The group names should be the same across all routers in the MPLS domain.

te-metric

Syntax

te-metric value

no te-metric

Context

config>router>mpls>interface

Description

This command configures the traffic engineering metric used on the interface. This metric is in addition to the interface metric used by IGP for the shortest path computation.

This metric is flooded as part of the TE parameters for the interface using an opaque LSA or an LSP. The OSPF-TE metric is encoded as a sub-TLV type 5 in the Link TLV. The metric value is encoded as a 32-bit unsigned integer. The IS-IS-TE metric is encoded as sub-TLV type 18 as part of the extended IS reachability TLV. The metric value is encoded as a 24-bit unsigned integer.

When the use of the TE metric is enabled for an LSP, CSPF will first prune all links in the network topology that do not meet the constraints specified for the LSP path. Such constraints include bandwidth, admin-groups, and hop limit. Then, CSPF will run an SPF on the remaining links. The shortest path among the all SPF paths will be selected based on the TE metric instead of the IGP metric, which is used by default.

The TE metric in CSPF LSP path computation can be configured by entering the command config>router>mpls>lsp lsp-name>cspf use-te-metric.

The TE metric is only used in CSPF computations for MPLS paths and not in the regular SPF computation for IP reachability.

The no form of the command reverts to the default value.

Default

no te-metric

Parameters

value

1 to 16777215