[no] interface ip-int-name
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command specifies MPLS protocol support on an IP interface. MPLS commands are not executed on an IP interface where MPLS is not enabled. An MPLS interface must be explicitly enabled (no shutdown).
The no form of this command deletes all MPLS commands, such as label-map, that are defined under the interface. The MPLS interface must first be shut down to delete the interface definition. If the interface is not shut down, the no interface ip-int-name command does nothing except issue a warning message on the console indicating that the interface is administratively up.
shutdown
Specifies the name of the network IP interface, up to 32 characters. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
[no] admin-group group-name [group-name...(up to 5 max)]
config>router>mpls>interface
Supported on all 7210 SAS platforms as described in this document.
This command configures administrative groups that this interface supports.
This information is advertised as part of OSPF and IS-IS to help CSPF compute constrained LSPs that must include or exclude specific administrative groups. An MPLS interface is assumed to belong to all the administrative groups unless the admin-group command is issued under the interface configuration. When the admin-group command is issued, the interface is assumed to belong to only the specifically listed groups for that command.
Each single operation of the admin-group command allows a maximum of five groups to be specified at a time. However, a maximum of 32 groups can be specified per interface through multiple operations.
no admin-group
Specifies the name of the group, up to 32 characters. The group names should be the same across all routers in the MPLS domain.
[no] srlg-group group-name [group-name...(up to 5 max)]
config>router>mpls>interface
Supported on all 7210 SAS platforms as described in this document.
This command associates an RSVP interface to SRLG groups. An interface can belong to up to 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of five groups to be specified at a time.
The no form of this command deletes the association of the interface to the SRLG group.
Specifies the name of the SRLG group, up to 32 characters, within a virtual router instance.
te-metric value
no te-metric
config>router>mpls>interface
Supported on all 7210 SAS platforms as described in this document.
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 IS-IS TE metric is encoded as sub-TLV 18 as part of the extended IS reachability TLV, and the metric value is encoded as a 24-bit unsigned integer. The OSPF TE metric is encoded as a sub-TLV Type 5 in the Link TLV, and the metric value is encoded as a 32-bit unsigned integer.
When the use of the TE metric is enabled for an LSP, CSPF first prunes 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 runs an SPF on the remaining links. The shortest path among all the 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 using the config>router>mpls>lsp>cspf>use-te-metric CLI command.
The TE metric is only used in CSPF computations for MPLS paths and not in the regular SPF computation for IP reachability. The value of the IGP metric is advertised in the TE metric sub-TLV by IS-IS and OSPF.
The no form of this command removes the configuration.
no te-metric
Specifies the metric value.