MPLS commands

authentication

Use the authentication command to enable cryptographic authentication. The no form and the default form of the command removes the cryptographic authentication.

Command Mode

MPLS RSVP sub-mode (mpls-rsvp)

Command Syntax

authentication [index 1-4294967295 [active | password ]|[sequence-number window 1-255]|[type [md5 | none]]]

no authentication [index 1-4294967295 [active | password ]|[sequence-number window 1-255]|[type [md5 | none]]]

default authentication [index 1-4294967295 [active | password ]|[sequence-number window 1-255]|[type [md5 | none]]]

Parameters
  • index 1-4294967295 - Specify the password index.
    • active - Use index as the active password.
    • password - Specify the password.
  • sequence-number - Specify the index in the sequence.
    • window 1-255 - Configure the reorder window size. The default value is 5. A value of 1 turns off support for packet reordering.
  • type - Specify the authentication mechanism.
    • md5 - Add the MD5 hash.
    • none - Indicates no authentication mechanism. Disables cryptographic authentication.

Examples
  • Enable Cryptographic Authentication (RFC 2747) by setting the authentication type to md5 and configuring an active password.
    (config-mpls-rsvp)# authentication type md5

  • Configure authentication secrets with an index. One of the indices should be chosen as the actively used password:
    (config-mpls-rsvp)# authentication index 1 password s3cr3t
    (config-mpls-rsvp)# authentication index 1 active

    Use the active password to authenticate outgoing messages. All configured passwords are accepted for authentication of incoming packets, which allows smooth key rollover.

  • Password encoding is available:
    (config-mpls-rsvp)# authentication index 1 password 7 07092E43

  • The size of the sequence number reorder window can be changed to accommodate a larger number of out-of-order packets. A value of N means that a packet is accepted if all earlier received packets with a higher sequence number are within the preceding N-1 packets.
    (config-mpls-rsvp)# authentication sequence-number window 5

    The default value is 5. A value of 1 effectively turns off support for packet reordering.

cspf delay

RSVP-TE uses CSPF to compute the FRR backup path. Throttle CSPF to avoid frequent path changes when frequent network events occur. Use the cspf delay command to specify how frequently CSPF runs after a network event by specifying the initial wait interval, back-off interval, and maximum wait interval for CSPF. The no form and the default form of the command remove the CSPF delay.

Command Mode

Router traffic engineering mode

Command Syntax

cspf delay [initial n back-off n] max n

no cspf delay [initial n back-off n] max n

default cspf delay [initial n back-off n] max n

Parameters
  • initial Specify initial wait interval for CSPF.
    • n - Specify the time in milliseconds. 1-300000.
      • back-off - Specify the back-off interval for CSPF.
        • n - Specify the time in milliseconds. 1-300000.

  • max - Specify the maximum wait interval for CSPF.
    • n - Specify the time in milliseconds. 1-300000.

entropy-label

The entropy-label command enables the MPLS LDP Entropy Label.

The no entropy-label command removes the MPLS LDP Entropy Label configurations from the running-config.

Command Mode

MPLS LDP Configuration Mode

Command Syntax

entropy-label

no entropy-label

Example

This command enables the MPLS LDP Entropy Label.
switch(config)# mpls ldp
switch(config-mpls-ldp)# entropy-label
switch(config-mpls-ldp)# exit

fast-reroute

Use the fast-reroute command to support Fast Reroute (FRR) link protection/NHOP (RFC 4090). You can enable FRR protection by setting the Fast Reroute mode to link-protection.

Command Mode

MPLS RSVP sub-mode (mpls-rsvp)

Command Syntax

fast-reroute [mode [ link-protection | node-protection | none]|[reversion [global | local]]

Parameters
  • modeFast reroute mode.
    • link-protection - Protects against failure of the next link.
    • node-protection - Protects against failure of the next node.
    • none - Disables fast reroute.

  • reversionSelect reversion behavior.
    • globalGlobal revertive repair (default).
    • local Local revertive repair.

Examples
  • Enable support for Fast ReRoute (FRR) link protection/NHOP (RFC 4090) by setting the Fast Reroute mode to link-protection.
    (config-mpls-rsvp)# fast-reroute mode link-protection

  • To turn off FRR, change the mode to the default setting none.
    (config-mpls-rsvp)# fast-reroute mode none

  • You can change the revertive behavior of the FRR from the global revertive mode to the local revertive mode. In the global revertive mode, an LSR re-routed over a bypass tunnel because the downstream link keeps uses the bypass tunnel even after the link has recovered. This expects the headend router to set up a new LSP upon notification that a link became unavailable. In the local revertive mode, the LSR switches back to using the primary link after recovery.
    (config-mpls-rsvp)# fast-reroute reversion local

  • The default for reversion is global.
    (config-mpls-rsvp)# fast-reroute reversion global

fast-reroute reversion

You can change the revertive behavior of the FRR from the global revertive mode to the local revertive mode. In the global revertive mode, an LSR re-routed over a bypass tunnel because the downstream link became unavailable but keeps using the bypass tunnel after the link recovers. This expects the headend router to set up a new LSP upon notification that a link became unavailable.In the local revertive mode, the LSR switches back to using the primary link after recovery.

The default for reversion is global.

Command Mode

Configuration sub-mode for RSVP

Command syntax

fast-reroute reversion [global | local]

Parameters
  • global Global revertive repair.
  • localLocal revertive repair.

Examples
  • Set the fast-reroute reversion to local:

    (config-mpls-rsvp)# fast-reroute reversion local

  • The default for reversion is global.
    (config-mpls-rsvp)# fast-reroute reversion global

hello interval

The hello interval command sets the time between the hello packets. The no form of the command explicitly disables the Hello messages, while the default form of the command resets to the default setting of 10 seconds with a multiplier of 4.

Command Mode

Configuration sub-mode for RSVP.

Command Syntax

hello interval [interval [sec]] [multiplier [num]]

no hello interval [interval [sec]][multiplier [num]]

default hello interval [interval [sec]][multiplier [num]]

Parameters
  • interval secThe interval in units of seconds.
    • multiplier numThe number of missed hellos after which the neighbor is expired.

Examples
  • In this example, eos sends hello messages to all known neighbors every 10 seconds. If the switch does not receive hello responsesfrom a neighbor for 4*10=40 seconds, the switch loses communication and the neighbor resets.
    (config-mpls-rsvp)# hello interval 10 multiplier 4

  • In this example, the default of 10 seconds with multiplier 4 resets.
    (config-mpls-rsvp)# default hello interval

  • in this example, explicitly disable the Hello messages.
    (config-mpls-rsvp)# no hello interval

mpls icmp source-interface

The mpls icmp source-interface command permits the designation of a source interface as an ipv4 address or IPv6 address. Using the no parameter disables the designated interface.

Command Mode

Global Configuration

Command Syntax

mpls icmp [fragmentation-needed | ip | ipv6 ttl-exceeded]

no mpls icmp [fragmentation-needed | ip | ipv6 ttl-exceeded]

Parameters

  • fragmentation-needed tunneling - Specify fragmentation for larger packets and enable MPLS tunneling.
  • ip source-interface - Specify the source interface from the list of available interfaces:
    • Ethernet
    • Loopback
    • Management
    • Port-Channel
    • Tunnel
    • Vlan
  • ipv6 source-interface
    • Ethernet
    • Loopback
    • Management
    • Port-Channel
    • Tunnel
    • Vlan
  • ttl-exceeded tunneling - Time-to-live exceeded in transit and enable MPLS tunneling on the switch.

Example

Use the following command to enable a source interface, Loopback0, for ipv4:
switch(config)#mpls icmp ip source-interface Loopback0

mpls ip

The mpls ip command enables MPLS routing. Multiprotocol Label Switching (MPLS) provides a networking process that avoids complex lookups in a routing table by replacing complete network addresses with short path labels for directing data packets to network nodes. MPLS data paths are serviced through a tunnel encapsulation data structure that adds four-byte label headers to packets.

The no mpls ip and default mpls ip commands disable MPLS routing by removing the mpls ip command from running-config. When MPLS routing is disabled, routed MPLS packets are dropped and all MPLS routes and adjacencies are removed. MPLS routing is disabled by default.

Command Mode

Global Configuration

Command Syntax

mpls ip

no mpls ip

default mpls ip

Examples
  • This command enables MPLS routing. Previous commands enabled IP routing and configured MPLS static routes.
    switch(config)# mpls ip
    switch(config)# show running-config
    
    ! Command: show running-config
    
    !
    ip routing
    !
    mpls ip
    !
    mpls static top-label 3400 10.14.4.4 pop payload-type ipv4
    mpls static top-label 4400 10.15.46.45 pop payload-type ipv4
    !
    
    !
    end
    switch(config)#

  • This command disables MPLS routing.
    switch(config)# no mpls ip
    switch(config)# show running-config
    
    
    ! Command: show running-config
                     <-------OUTPUT OMITTED FROM EXAMPLE-------->
    !
    ip routing
    !
    mpls static top-label 3400 10.14.4.4 pop payload-type ipv4
    mpls static top-label 4400 10.15.46.45 pop payload-type ipv4
    !
    
    !
    end
    switch(config)#

mpls parsing speculative

Use the mpls parsing speculative command to configure parsing additional header types used by the load-balancing hash algorithm.

Command Mode

Global Configuration

Command Syntax

mpls parsing speculative [control-word | ethernet | ipv4 | ipv6]

Parameters

  • parsing - Configure parsing of MPLS packets.
  • speculative - Configure speculative parsing of different types of MPLS encapsulated packets for all data plane features.
  • control-word - Enable parsing of MPLS pseudowire packets with a control word.
  • ethernet - Enable parsing of MPLS encapsulated Ethernet packets.
  • ipv4 - Enable parsing of MPLS encapsulated ipv4 packets.
  • ipv6 - Enable parsing of MPLS encapsulated IPv6 packets.

Example

To enable MPLS speculative parsing on Ethernet packets, use the following command:

switch(config)#mpls parsing speculative ethernet

mpls shared index

The mpls shared index command configures an Ethernet-Segment (ES) shared-index to allocate an ESI label value based on the shared-index configuration.

The no mpls shared index command removes mpls shared index configuration from the running-config.

Command Mode

EVPN Ethernet-Segment Mode

Command Syntax

mpls shared index index-value

no mpls shared index index-value

Parameter
  • index-value Label index value. Value ranges from 1 to 1024.

Example
  • These commands place the switch on Ethernet-Segment (ES) configuration mode and configure an MPLS shared index value of 100.
    switch(config)# interface Ethernet4
    switch(config-if-Et1)# switchport access vlan 1000
    switch(config-if-Et1)# evpn ethernet-segment
    switch(config-evpn-es)# identifier 0022:2222:2222:2222:2222
    switch(config-evpn-es)# mpls shared index 100
    switch(config-evpn-es)# route-target import 00:02:00:02:00:02

mpls static

The mpls static command creates an MPLS rule that specifies the method of handling of inbound MPLS traffic. Multiprotocol Label Switching (MPLS) is a networking process that replaces complete network addresses with short path labels for directing data packets to network nodes.

Static rules specify these parameters:
  • MPLS filter: The top-label parameter specifies the 20-bit value that the MPLS packet’s top header label must match to be handled by the rule.
  • Nexthop location: Specifies the destination nexthop address (ipv4 or IPv6) and the interface through which the switch forwards the packet.
  • MPLS action: Specifies the MPLS label stack management action performed on the packet:
    • pop-payload: removes the top label from stack; this terminates an LSP (label-switched path).
    • swap-label: replaces top label with a specified new label; this passes a packet along an LSP.

  • Rule priority: Specifies the rule to be used when an MPLS packet matches multiple rules.

The no mpls static and default mpls static commands delete the specified MPLS rule from running-config.
  • commands that include only a top label tag remove all MPLS rules with the matching top label.
  • commands with no PRIORITY parameter remove all matching routes of every metric value.

Command Mode

Global Configuration

Command Syntax

mpls static top-label top_tag[ bgp peer [peer IP]] [DEST_INTF] NEXTHOP_ADDR ACTION [PRIORITY]

no mpls static top-label top_tag

no mpls static top-label top_tag [DEST_INTF] NEXTHOP_ADDR ACTION [PRIORITY]

default mpls static top-label top_tag

default mpls static top-label top_tag [DEST_INTF] NEXTHOP_ADDR ACTION [PRIORITY]

Parameters
  • top_tag      Top header’s label field contents. Value ranges from 0 to 1048575 (20 bits).
  • BGP peer peer IP The BGP peer identifier.
  • DEST_INTF Specifies interface through which NEXTHOP_ADDR is accessed. Options include:
    • no parameter      Any interface.
    • ethernet e_num       Ethernet interface specified by e_num.
    • loopback l_num      Loopback interface specified by l_num.
    • management m_num      Management interface specified by m_num.
    • port-channel p_num      Port-channel interface specified by p_num.
    • vlan v_num      VLAN interface specified by v_num.
    • VXLAN vx_num      VXLAN interface specified by vx_num.

  • NEXTHOP_ADDR      Nexthop address for MPLS for filtered MPLS packets. Options include:
    • ipv4_addr  ipv4 address.
    • ipv6_addr      IPv6 address.

  • ACTION MPLS header stack management action performed on packet. Options include:
    • pop payload-type ipv4 Removes top layer from stack. Payload is handled as ipv4 packet.
    • pop payload-type ipv6 Removes top layer from stack. Payload is handled as IPv6 packet.
    • swap-label 0 to 1048575      Replaces header label with specified label value (20 bits).

  • PRIORITY     Specifies rule priority when multiple rules match a packet. Options include:
    • no parameter      Assigns a metric value of 100 to the rule.
    • metric 1 to 255     Lower values denote higher priority. Value ranges from 1 to 255.

The mpls static command does not support push label actions.

Examples
  • These commands create an MPLS rule that matches packets with a top label value of 3400 and causes the removal of the top label from the header stack. The nexthop destination of the ipv4 payload is IP address 10.14.4.4 through Ethernet interface 3/3/3. This rule has a metric value of 100.
    switch(config)# mpls static top-label 3400 ethernet 3/3/3 10.14.4.4 pop payload-type ipv4
    switch(config)# show running-config
    
    !
    mpls static top-label 3400 Ethernet3/3/3 10.14.4.4 pop payload-type ipv4
    !
    
    end
    switch(config)#

  • These commands create a backup rule that forwards the packet through Ethernet interface 4/3. This rule’s metric value of 150 assigns it backup status prior to the first rule.
    switch(config)# mpls static top-label 3400 ethernet 4/3 10.14.4.4 pop payload-type ipv4 metric 150
    switch(config)# show running-config
    
    !
    mpls static top-label 3400 Ethernet4/3 10.14.4.4 pop payload-type ipv4 metric 150
    mpls static top-label 3400 Ethernet3/3/3 10.14.4.4 pop payload-type ipv4
    !
    
                        <-------OUTPUT OMITTED FROM EXAMPLE-------->
    end
    switch(config)#

  • These commands create an MPLS rule that forwards the packet to the nexthop address through any interface.
    switch(config)# mpls static top-label 4400 10.15.46.45 pop payload-type ipv4
    switch(config)# show running-config
    
                         <-------OUTPUT OMITTED FROM EXAMPLE-------->
    
    !
    mpls static top-label 3400 Ethernet4/3 10.14.4.4 pop payload-type ipv4 metric 150
    mpls static top-label 3400 Ethernet3/3/3 10.14.4.4 pop payload-type ipv4
    mpls static top-label 4400 10.15.46.45 pop payload-type ipv4
    !
    
    end
    switch(config)#

  • This command uses the BGP peer option to designate the nexthop..

    switch(config)#mpls static top-label 1001 100.1.1.1 bgp peer pop payload-type ipv4

  • When the peer IP is not specified, the next-hop is considered as the peer.
    switch(config)# mpls static top-label 1002 100.1.1.2 bgp peer 100.1.1.1 pop payload-type ipv4
    switch(config)# mpls static top-label 1002 100.1.1.3 bgp peer 100.1.1.1 pop payload-type ipv4

  • Multiple nexthops can be associated with the same BGP peer by explicitly specifying the BGP peer IP. This is useful in the case of third-party nexthops.
    switch(config)# mpls static top-label 1000 nexthop-group mygroup bgp peer 100.1.1.1 pop payload-type ipv4

mpls static vrf-label

Use the mpls static vrf-label command to configure a static VRF label route. The no and default versions of the command removes the configuration.

Command Mode

Global configuration mode

Command Syntax

mpls static vrf-label mpls-label [vrf vrf-name]

no mpls static vrf-label mpls-label [vrf vrf-name]

default mpls static vrf-label mpls-label [vrf vrf-name]

Parameters
  • mpls-labelValue of the MPLS label.
  • vrf vrf-nameVRF instance name.

Example
switch(config)# mpls static vrf-label 100 vrf default
switch(config)# mpls static vrf-label 200 vrf v1

mpls tunnel termination

Command Mode

Global configuration mode

Command Syntax

mpls tunnel termination [ model [php model][ttl [[pipe | uniform] dscp]| pipe | uniform]

no mpls tunnel termination [model [php model][ttl [[pipe | uniform] dscp]| pipe | uniform]

default mpls tunnel termination [model [php model][ttl [[pipe | uniform] dscp]| pipe | uniform]

Parameters
  • modelTunnel termination TTL and DSCP model.
  • phpPenultimate hop popping configuration.
  • ttlModel for TTL.
  • pipePreserve the inner value.
  • uniformPropagate value from outer header.
  • dscpmode for DSCP.

Example
switch(config)# mpls tunnel termination model ttl uniform dscp pipe

mpls tunnel termination (vrf qos map)

The mpls tunnel termination (vrf qos map) command changes configuration mode to allow the attachment of DSCP-to-traffic-class maps to specific VRFs. This is a group change command, so no changes are made to the running config until the exit command is issued.

MPLS tunnel termination mode has one subcommand, vrf. vrf is also a group change command, with the subcommand qos map dscp to traffic-class.

Command Mode

Global Configuration

Command Syntax

mpls tunnel termination

Subcommand

vrf

Example

These commands enter MPLS Tunnel Termination Configuration mode and attach the DSCP-to-traffic-class map map1 to the VRFs newVRF1 and newVRF2.
switch(config)# mpls tunnel termination
switch(config-mpls-tunnel-termination)# vrf newVRF1
switch(config-mpls-tunnel-termination-vrf-newVRF1)# qos map dscp to traffic-class map1
switch(config-mpls-tunnel-termination-vrf-newVRF1)# exit
switch(config-mpls-tunnel-termination)# vrf newVRF2
switch(config-mpls-tunnel-termination-vrf-newVRF2)# qos map dscp to traffic-class map1
switch(config-mpls-tunnel-termination-vrf-newVRF2)# exit
switch(config-mpls-tunnel-termination)# exit
switch(config)# exit

ping mpls rsvp session

LSP Ping allows the user to check if the remote endpoint of an RSVP session is reachable through the LSP. Running ping on an RSVP LSP creates an LSP Ping Request packet with the label programmed by RSVP and that packet will follow the MPLS path until it reaches the end of the tunnel. If the node that receives this Request is the intended destination, it replies with an RSVP Ping Reply through normal IP routing. When the source receives the Reply it indicates that there are no apparent data plane failures and that the endpoint of that LSP is reachable.

Command Mode

Configuration sub-mode for RSVP

Command Syntax

ping mpls rsvp session [id num | name word] [lsp | pad-reply | repeat | source | standard | tos | tos ]

Parameters
  • idSpecifies the session by ID
    • numRSVP session ID.
      • lspSpecifies LSP
      • pad-replyIndicates that the reply should copy the pad TLV.
      • repeatSpecifies repeat count.
      • sourceSpecifies source address.
      • standardSets the standard to comply with.
      • tos Specifies ToS value.
      • tos Specifies MPLS traffic class field.

  • nameSpecifies session by name.
    • wordRSVP session name.
      • lspSpecifies LSP
      • pad-replyIndicates that the reply should copy the pad TLV.
      • repeatSpecifies repeat count.
      • sourceSpecifies source address.
      • standardSets the standard to comply with.
      • tos Specifies ToS value.
      • traffic-class Specifies MPLS traffic class field.

Examples
  • A user can invoke the ping utility for a specific LSP by using the session and LSP IDs displayed in the CLI show commands.
    switch# ping mpls rsvp session id 1 lsp 1 repeat 3
    LSP ping to RSVP session #1 LSP #1
       timeout is 5000ms, interval is 1000ms
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=1, time=53.294ms, success: egress ok
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=2, time=75.329ms, success: egress ok
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=3, time=85.574ms, success: egress ok
    
    --- RSVP target fec 0.4.4.4 : lspping statistics ---
    Via 10.0.12.2, Ethernet1, label 100000
       3 packets transmitted, 3 received, 0% packet loss, time 2272ms
       3 received from 10.0.34.4, rtt min/max/avg 53.294/85.574/71.399 ms

  • For the ping mpls rsvp session command, the argument lsp is optional. If unspecified, the utility pings all LSPs within that session.
    switch# ping mpls rsvp session id 1 repeat 2
    LSP ping to RSVP session #1
       timeout is 5000ms, interval is 1000ms
    LSP 1
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=1, time=60.28ms, success: egress ok
    LSP 2
    Via 10.0.12.2, Ethernet1, label 100002
       Reply from 10.0.34.4: seq=1, time=81.701ms, success: egress ok
    LSP 1
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=2, time=52.807ms, success: egress ok
    LSP 2
    Via 10.0.12.2, Ethernet1, label 100002
       Reply from 10.0.34.4: seq=2, time=62.814ms, success: egress ok
    
    --- RSVP target fec 0.4.4.4 : lspping statistics ---
    LSP 1
    Via 10.0.12.2, Ethernet1, label 100000
       2 packets transmitted, 2 received, 0% packet loss, time 1262ms
       2 received from 10.0.34.4, rtt min/max/avg 52.807/60.280/56.544 ms
    
    LSP 2
    Via 10.0.12.2, Ethernet1, label 100002
       2 packets transmitted, 2 received, 0% packet loss, time 1262ms
       2 received from 10.0.34.4, rtt min/max/avg 62.814/81.701/72.257 ms

  • Similarly, the session can be specified by name and the utility pings all the LSPs within that session.
    switch# ping mpls rsvp session name Session1to4 repeat 2
    LSP ping to session Session1to4
       timeout is 5000ms, interval is 1000ms
    LSP 1
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=1, time=63.314ms, success: egress ok
    LSP 2
    Via 10.0.12.2, Ethernet1, label 100002
       Reply from 10.0.34.4: seq=1, time=75.639ms, success: egress ok
    LSP 1
    Via 10.0.12.2, Ethernet1, label 100000
       Reply from 10.0.34.4: seq=2, time=60.875ms, success: egress ok
    LSP 2
    Via 10.0.12.2, Ethernet1, label 100002
       Reply from 10.0.34.4: seq=2, time=77.135ms, success: egress ok
    
    --- RSVP target fec 0.4.4.4 : lspping statistics ---
    LSP 1
    Via 10.0.12.2, Ethernet1, label 100000
       2 packets transmitted, 2 received, 0% packet loss, time 1262ms
       2 received from 10.0.34.4, rtt min/max/avg 60.875/63.314/62.094 ms
    
    LSP 2
    Via 10.0.12.2, Ethernet1, label 100002
       2 packets transmitted, 2 received, 0% packet loss, time 1262ms
       2 received from 10.0.34.4, rtt min/max/avg 75.639/77.135/76.387 ms

preemption method

The preemption method command enables deferred failure of RSVP-TE LSPs on link oversubscription. Use a preemption timer value to configure a delay on a transit router to support LSPs signaled with soft preemption enabled by the headend (RFC 5712).

The default preemption method is soft preemption with a timer value of 30 seconds.

Command Mode

Configuration sub-mode for RSVP

Command Syntax

preemption method [hard | soft ] timer t

no preemption method [hard | soft ] timer t

default preemption method [hard | soft ] timer t

Parameters
  • hardHard preemption.
  • soft Soft preemption.
    • timerTime limit for LSP teardown.
      • t 1-65535 Timer value in units of seconds.

Examples
  • In this example, the preemption method is soft preemption with a timer value of 10 seconds.
    (config-mpls-rsvp)# preemption method soft timer 10

  • Setting the preemption method to hard preemption results in a timer value of 0 seconds and disables the feature.
    (config-mpls-rsvp)# preemption method hard

refresh method

Using the refresh method command with the bundled keyword enables the Refresh Overhead Reduction that supports the sending of message IDs and refreshing state with refresh messages.

Command Mode

Configuration sub-mode for RSVP

Command Syntax

refresh method [bundled | explicit ]

Parameters
  • bundled Refresh states using message identifiers lists. This is the default setting.
  • explicitSend each message individually.

Examples
  • Use the bundled keyword to enable the Refresh Overhead Reduction.

    (config-mpls-rsvp)# refresh method bundled

  • To turn off refresh overhead reduction, use the explicit keyword.
    (config-mpls-rsvp)# refresh method explicit

show mpls parsing speculative

The show mpls parsing speculative command displays information about the MPLS Speculative Parsing configuration.

Command Mode

Global Configuration

Command Syntax

show mpls parsing speculative

Parameters

  • parsing - Configure parsing of MPLS packets.
  • speculative - Configure speculative parsing of different types of MPLS encapsulated packets for all data plane features.
  • control-word - Enable parsing MPLS pseudowire packets with a control word.
  • ethernet - Enable parsing MPLS encapsulated Ethernet packets.
  • ipv4 - Enable parsing MPLS encapsulated ipv4 packets.
  • ipv6 - Enable parsing MPLS encapsulated IPv6 packets.

Example

Use the following command to display information about the MPLS configuration:

switch#show mpls parsing speculative
Packet Type        Status  
------------------ --------
Control Word       disabled
Ethernet           disabled
ipv4               enabled
IPv6               enabled

show mpls route summary

The show mpls route summary command displays statistics about the configuration and implementation of MPLS rules.

Command Mode

EXEC

Command Syntax

show mpls route summary

Example

This command displays a summary of MPLS rule implementation.
switch> show mpls route summary
Number of Labels: 1 (1 unprogrammed)
Number of adjacencies in hardware: 0
Number of backup adjacencies: 2
switch>

show mpls route

The show mpls config route command displays the switch’s MPLS static rule configuration for the specified routes and rules.

Command Mode

EXEC

Command Syntax

show mpls [INFO_LEVEL] route [header_label]

Parameters
  • INFO_LEVEL     Specifies the filters that are used to select the routes to display. Options include:
    • no parameter     Displays routes published by the forwarding agent.
    • config     Displays all configured routes.
    • lfib     Displays routes stored to the Label Forwarding Information Base (LFIB).

  • header_label Filters routes by MPLS top header label. Options include:
    • no parameter      Displays routes for all header values.

  • 0 to 1048575      Specifies header for which command displays information.

Examples
  • This command displays the MPLS rule configuration.
    switch# show mpls config route
    Codes: S - Static MPLS Route, IA - IS-IS SR Adjacency Segment,
           IP - IS-IS SR Prefix Segment, L - LDP,
           I>L - IS-IS SR Segment to LDP, L>I - LDP to IS-IS SR Segment, R - RSVP
    
    In-Label Out-Label Metric Payload NextHop   Egress-ACL Status Monitored     
    -------- --------- ------ ------- --------- ---------- ------ --------------
    1000     pop       100    ipv4    100.0.0.1 apply      up                   
    1001     pop       100    ipv4    20.0.0.2  apply      down                 
    1002     pop       100    ipv4    100.0.0.2 apply      down   100.0.0.2(Bgp)
    1003     pop       100    ipv4    20.0.0.2  apply      down   100.0.0.2(Bgp)
    1004     pop       100    ipv4    20.0.0.2  apply      up     20.0.0.2(Bgp) 
    1005     pop       100    ipv4    30.0.0.3  apply      up     200.0.0.3(Bgp)

    The status could be down if either of the following is true
    1. Nexthop is not resolved (show ip route nexthop - shows no route).
    2. The monitored BGP session is down (show ip bgp summary - shows the peer is not in established state).

  • The following example shows that the first route is down because the BGP peer session is down.
    switch# show mpls config route 
    Codes: S - Static MPLS Route, IA - IS-IS SR Adjacency Segment,
           IP - IS-IS SR Prefix Segment, L - LDP,
           I>L - IS-IS SR Segment to LDP, L>I - LDP to IS-IS SR Segment, R - RSVP
    
    In-Label Out-Label Metric Payload NextHop  Egress-ACL Status Monitored    
    -------- --------- ------ ------- -------- ---------- ------ -------------
    88886    pop       100    ipv4    14.0.0.4 apply      down   14.0.0.4(BGP)
    88887    pop       100    ipv4    15.0.0.5 apply      down 

  • The following example shows the status of label 88886 is down because the BGP peer session to 14.0.0.4 is down, but route exists for 14.0.0.4.
    switch# show ip bgp summary 
    BGP summary information for VRF default
    Router identifier 3.0.1.3, local AS number 3000
    Neighbor Status Codes: m - Under maintenance
      Neighbor V AS           MsgRcvd   MsgSent  InQ OutQ  Up/Down State   PfxRcd PfxAcc
      14.0.0.4 4 4000              16        18    0    0 01:04:42 Active
    
    switch# show ip route 14.0.0.4
    
    VRF: default
    Codes: C - connected, S - static, K - kernel, 
     O - OSPF, IA - OSPF inter area, E1 - OSPF external type 1,
           E2 - OSPF external type 2, N1 - OSPF NSSA external type 1,
           N2 - OSPF NSSA external type2, B - Other BGP Routes,
           B I - iBGP, B E - eBGP, R - RIP, I L1 - IS-IS level 1,
           I L2 - IS-IS level 2, O3 - OSPFv3, A B - BGP Aggregate,
           A O - OSPF Summary, NG - Nexthop Group Static Route,
           V - VXLAN Control Service, M - Martian,
           DH - DHCP client installed default route,
           DP - Dynamic Policy Route, L - VRF Leaked,
           G  - gRIBI, RC - Route Cache Route
    
     S        14.0.0.4/32 [1/0] via 2.0.1.4, Ethernet2

show mpls rsvp

Use the show mpls rsvp to display the overall state of the RSVP.

Command Mode

EXEC

Command Syntax

show mpls rsvp [bandwidth | counters | ip | ipv6 | neighbor | session]

Parameters
  • bandwidthDisplays RSVP bandwidth information.
  • countersDisplays RSVP message counters.
  • ipDisplays details related to ipv4.
  • ipv6Displays details related to IPv6.
  • neighborDisplays RSVP neighbors.
  • sessionDisplays RSVP session information.

Example
switch> show mpls rsvp   	 
Administrative state: enabled
Operational state: up
Refresh interval: 30 seconds
Refresh reduction: enabled
Hello messages: enabled
   Hello interval: 10 seconds
   Hello multiplier: 4
Fast Re-Route: disabled
   Mode: none
   Hierarchical FECs: enabled
Cryptographic authentication: disabled
MTU signaling: disabled
Number of sessions: 1
   Ingress/Transit/Egress: 0/1/0
Number of LSPs: 1
   Operational: 1
   Ingress/Transit/Egress: 0/1/0
   Currently using bypass tunnels: 0
Number of bypass tunnels: 0
Number of neighbors: 2
Number of interfaces: 2

show mpls rsvp counters

Use the show mpls rsvp counters command to display RSVP message counters, per interface.

Command Mode

EXEC

Command Syntax

show mpls rsvp counters [[interface [Ethernet |Fabric | Loopback | Management | Port-Channel | Switch | Tunnel | Vlan | Vxlan]]| ipv4 interface | ipv6 interface

Parameters
  • interface Filter by interface.
    • EthernetHardware Ethernet interface.
    • FabricFabric interfaces.
    • LoopbackHardware interface used for looping packets.
    • ManagementManagement interface.
    • Port-ChannelLag interface.
    • SwitchSwitch interface.
    • TunnelTunnel interface.
    • VlanLogical interface into a VLAN.
    • Vxlan VXLAN tunnel interface.

  • ipv4Filter by ipv4.
    • interface Filter by interface.

  • ipv6Filter by IPv6.
    • interface Filter by interface.

Example
switch> show mpls rsvp counters
Received Messages:

Interface  Path  PathTear  PathErr  Resv  ResvTear  ResvErr  Srefresh  Other  Errors  
---------  ----  --------  -------  ----  --------  -------  --------  -----  ------  
Ethernet1  5     0         0        0     0         0        8         51     1  	 
Ethernet2  0     0         0        14    0         0        0         0      0  	 

Sent Messages:

Interface  Path  PathTear  PathErr  Resv  ResvTear  ResvErr  Srefresh  Other  Errors  
---------  ----  --------  -------  ----  --------  -------  --------  -----  ------  
Ethernet1  0     0         0        4     0         0        9         49     0  	 
Ethernet2  13    0         0        0     0         0        0         4      0  	

show mpls rsvp neighbor

Use the show mpls rsvp neighbor command to display a summary of all RSVP neighbors, or the list of active LSPs for a specific neighbor.

Command Mode

EXEC

Command Syntax

show mpls rsvp neighbor [A.B.C.D | A:B:C:D:E:F:G:H | summary]

Parameters
  • A.B.C.DIP (v4 or v6) address of neighbor.
  • A:B:C:D:E:F:G:HIP (v4 or v6) address of neighbor.
  • summaryDisplays summarized information.

Examples
  • Use the show mpls rsvp neighbor command to display a summary of all RSVP neighbors.

    switch> show mpls rsvp neighbor
    Neighbor 10.0.1.1
       Upstream for
          Session #1 LSP #1
       Downstream for
       Neighbor uptime: 00:01:24
       Authentication type: disabled
       Last hello received: 1 seconds ago
       Last hello sent: 1 seconds ago
       Bypass tunnel: not requested
    Neighbor 10.0.2.2
       Upstream for
       Downstream for
      	Session #1 LSP #1
       Neighbor uptime: 00:01:24
       Authentication type: disabled
       Last hello received: -
       Last hello sent: 31 seconds ago
       Bypass tunnel: not requested

  • Use the show mpls rsvp neighbor summary command to display summarized information.

    switch> show mpls rsvp neighbor summary
    Neighbor             Role       Sessions LSPs
    ==================== ========== ======== ========
    10.0.1.1             Upstream   1    	1
    10.0.2.2             Downstream 1    	1

show mpls rsvp session detail

Use the show mpls rsvp session detail to display the detailed information of RSVP sessions.

Command Mode

EXEC

Command Syntax

show mpls rsvp session detail

Example
switch> show mpls rsvp session detail
Session #1
   Destination address: 0.4.4.4
   Tunnel ID: 0
   Extended Tunnel ID: 0.1.1.1
   Role: transit
  	LSP #1
        State: up
        [...]
        MTU Signaling: enabled
           Received Path MTU: 1800 bytes
           Sent Path MTU: 1500 bytes
  [...]

show mpls rsvp session summary

Use the show mpls rsvp session summary command to filter sessions in the show command and in LSP ping and traceroute commands. Sessions can further be filtered by name, destination, router role (transit/ingress/egress), and state.

Command Mode

EXEC

Command Syntax

show mpls rsvp session summary

Example
switch> show mpls rsvp session summary
Session  Destination        LSP      Name         Role    Bypass State
======== ================== ======== ============ ======= ====== =========
1        0.4.4.4             1        Session1    transit n/req  up

show mpls rsvp session

Use the show mpls rsvp session command to list the current RSVP sessions filtered by IP address.

Command Mode

EXEC

Command Syntax

show mpls rsvp session

Example
switch> show mpls rsvp session
Session #1
   Destination address: 0.4.4.4
   Tunnel ID: 0
   Extended Tunnel ID: 0.1.1.1
   Role: transit
  	LSP #1
        State: up
        Type: primary
        Source address: 0.1.1.1
        LSP ID: 1
        LSP uptime: 00:02:38
        Session name: Session1
        Local label: 100000
        Downstream label: 100000
        Upstream neighbor: 10.0.1.1
           Last refresh received: 17 seconds ago
           Last refresh sent: 10 seconds ago
        Downstream neighbor: 10.0.2.2
           Last refresh received: 7 seconds ago
           Last refresh sent: 9 seconds ago
        Bypass tunnel: not requested

show mpls tunnel termination qos maps

The show mpls tunnel termination qos maps command shows the DSCP to TC map associated with each VRF, or with a specified VRF.

Command Mode

Privileged EXEC mode

Command Syntax

show mpls tunnel termination qos maps [ vrf vrf_name ]

Parameter

vrf_name The VRF whose DSCP to TC map association is to be shown. If this parameter is omitted, all DSCP to TC maps associated with a VRF are shown.

Examples

This command shows the DSCP to TC maps associated with VRFs.
switch# show mpls tunnel termination qos maps
VRF newVRF1 DSCP to TC map: map1
VRF newVRF2 DSCP to TC map: map1
switch#

This command shows the DSCP to TC map associated with VRF newVRF2.
switch# show mpls tunnel termination qos maps vrf newVRF2
VRF newVRF2 DSCP to TC map: map1
switch#

show traffic-engineering cspf path

Use the show traffic-engineering cspf path command to display all the paths counted by CSPF.

Command Mode

EXEC

Command Syntax

show traffic-engineering cspf path [destination-IP]detail]

Parameters
  • A.B.C.D CSPF path to this destination IP address.
  • detail Show detailed path information.

Examples
  • In this example, the CSPF destination path 20.0.0.1 is selected to display.
    switch> show traffic-engineering cspf path 20.0.0.1
    
    Destination     Constraint                           Path
    20.0.0.1        exclude Ethernet1                    0.1.1.1
                    exclude SRLG of Ethernet1            0.1.1.2
                                                         0.2.2.2
                                                         3.3.3.2
                    exclude Ethernet2                    0.1.1.1
                                                         0.1.1.2
                                                         0.2.2.2
                                                         3.3.3.2

  • In this example, the CSPF destination path 20.0.0.1 is selected to display detailed information.
    switch> show traffic-engineering cspf path 20.0.0.1 detail
    
    Destination: 20.0.0.1
       Path Constraint: exclude Ethernet1
                        exclude SRLG of Ethernet1: orange-link (500), 
                           green-link (400), 100, red-link (200), 600
       Request Sequence number: 1
       Response Sequence number: 1
       Number of times path updated: 2
       Last updated: 00:01:58
       Reoptimize: Always
       Path:
      	0.1.1.1
      	0.1.1.2
      	0.2.2.2
      	3.3.3.2
    
       Path Constraint: exclude Ethernet2
       Request Sequence number: 2
       Response Sequence number: 2
       Number of times path updated: 3
       Last updated: 00:00:38
       Reoptimize: Always
       Path:
      	0.1.1.1
      	0.1.1.2
      	0.2.2.2
      	3.3.3.2

show traffic-engineering database

Use the show traffic-engineering database to display the topology used for CSPF computations. Starting from eos Release 4.23.1F, the SRLG group details of a neighbor are shown if it is advertised.

Command Mode

EXEC

Command Syntax

show traffic-engineering database

Special Considerations
  • Beginning with eos Release 4.23.1F, the SRLG group details of a neighbor are shown if it is advertised.
  • Beginning with eos Release 4.24.2F, information for the OSPFv2 topology is displayed if configured.

Example

switch# show traffic-engineering database

TE Router-ID: 1.0.0.2
  Source: IS-IS Level-1 ipv4 Topology Database
    IS-IS System-ID: 1111.1111.1001
      Number of Links: 2
        Network type: P2P 
          Neighbor: 1111.1111.1002
		 Administrative group (Color): 0x123a
            TE Metric: 30
            ipv4 Interface Addresses:
              20.20.20.1
              192.168.20.1
            ipv4 Neighbor Addresses:
              20.20.20.2
              192.168.20.2
            Maximum link BW: 25.00 Gbps
            Maximum reservable link BW: 10.00 Mbps
            Unreserved BW:
              TE class 0: 9.00 Mbps     TE class 1: 9.00 Mbps
              TE class 2: 8.5.00 Mbps   TE class 3: 8.00 Mbps
              TE class 4: 7.00 Mbps     TE class 5: 7.50 Mbps
              TE class 6: 6.00 Mbps     TE class 7: 6.00 Mbps                                                                                        
        Network Type: LAN  
          Neighbor: 1111.1111.1003.02
            TE Metric: 30    
        	Administrative Group: 0x12     
            ipv4 Local Addresses:
              30.30.30.1                                                                                                      
            Maximum Link BW: 10.00 Gbps                                                                                       
            Maximum Reservable Link BW: 10.50 Gbps                                                                             
            Unreserved BW:                                                                                                     
              TE-Class 0: 8.50 Gbps       TE-Class 1: 8.70 Gbps                                                               
              TE-Class 2: 7.50 Gbps       TE-Class 3: 7.25 Gbps                                                               
              TE-Class 4: 6.50 Gbps       TE-Class 5: 7.30 Gbps                                                               
              TE-Class 6: 3.50 Gbps       TE-Class 7: 7.20 Gbps
  Source: IS-IS Level-2 ipv4 Topology Database  
    IS-IS System-ID: 1111.1111.1003
      Number of Links: 1  
        Network Type: LAN
         Neighbor: 1111.1111.1003.16
           ipv4 Local Addresses:
             40.40.40.1
            Maximum link BW: 10.00 Gbps
            Maximum reservable link BW: 5.00 Gbps
            Unreserved BW:
              TE class 0: 4.00 Gbps     TE class 1: 4.00 Gbps
              TE class 2: 4.00 Gbps     TE class 3: 4.00 Gbps
              TE class 4: 3.00 Gbps     TE class 5: 3.00 Gbps
              TE class 6: 3.00 Gbps     TE class 7: 3.00 Gbps
  Source: OSPFv2 Instance ID 33 Area-ID 0.0.0.0 Topology Database
    OSPFv2 Router-ID: 1.2.3.4
      Number of Links: 2
        Network type: P2P
          Neighbor: 3.4.5.6
            Administrative group (Color): 0x123a
            TE metric: 30
            ipv4 Interface Addresses:
              20.20.20.1
              192.168.20.1
            ipv4 Neighbor Addresses:
              20.20.20.2
              192.168.20.1
            Maximum link BW: 25.00 Gbps
            Maximum reservable link BW: 10.00 Mbps
            Unreserved BW:
              TE class 0: 9.00 Mbps    TE class 1: 9.00 Mbps
              TE class 2: 8.50 Mbps    TE class 3: 8.00 Mbps
              TE class 4: 7.00 Mbps    TE class 5: 7.50 Mbps
              TE class 6: 6.00 Mbps    TE class 7: 6.00 Mbps
        Network type: LAN
          Neighbor: 2.3.4.5
            Administrative group (Color): 0x12
            TE metric: 30
            ipv4 Interface Addresses:
              30.30.30.1
            ipv4 Neighbor Addresses:
              0.0.0.0
            Maximum link BW: 10.00 Gbps
            Maximum reservable link BW: 10.5 Gbps
            Unreserved BW:
              TE class 0: 8.50 Gbps    TE class 1: 8.70 Gbps
              TE class 2: 7.50 Gbps    TE class 3: 7.25 Gbps
              TE class 4: 6.50 Gbps    TE class 5: 7.30 Gbps
              TE class 6: 3.50 Gbps    TE class 7: 7.20 Gbps                                                                                         
TE Router-ID: 1.0.0.3
  Source: IS-IS Level-1 ipv4 Topology Database
    IS-IS System-ID: 1111.1111.1004
      Number of Links: 2
        Network type: P2P
          Neighbor: 1111.1111.1002
          ipv4 Interface Addresses:
              1.0.5.1
            ipv4 Neighbor Addresses:
              1.0.5.2
            Maximum link BW: 50.00 Gbps
            Maximum reservable link BW: 10.00 Gbps
            Unreserved BW:
              TE class 0: 8.00 Gbps     TE class 1: 8.00 Gbps
              TE class 2: 8.00 Gbps     TE class 3: 8.00 Gbps
              TE class 4: 7.00 Gbps     TE class 5: 7.00 Gbps
              TE class 6: 7.00 Gbps     TE class 7: 7.00 Gbps
            Shared Risk Link Group:
              Group: 100
              Group: green-link (150)

shutdown

The shutdown command disables the RSVP-TE protocol instance or the RSVP-related functions for the interface. The RSVP-TE configuration information associated with the interface is retained.

RSVP-TE is enabled globally by issuing no shutdown in the configuration sub-mode. This is the only mandatory setting for RSVP-TE to work. There is no per-interface knob to enable or disable RSVP. However, RSVP is only enabled on interfaces on which MPLS is enabled.

Command Mode

Configuration sub-mode for RSVP

Command Syntax

shutdown

no shutdown

Examples
  • You can enable RSVP-TE globally by issuing the no shutdown command.
    (config-mpls-rsvp)# no shutdown

  • Similarly, it is disabled with the shutdown command, which is the default.
    (config-mpls-rsvp)# shutdown

srlg

The srlg command specifies if link SRLGs of a primary LSP are to be considered as constraints while creating a fast-reroute bypass tunnel with either link or node protection. When the srlg command is specified with strict keyword, then when a path for a bypass tunnel excluding SRLGs of next-hop interface of primary LSP can not be found, RSVP does not setup the bypass tunnel. When thesrlg command is specified without the strict keyword, then a bypass tunnel is setup with as many links as possible that exclude the SRLGs of next-hop interface of primary LSP and where such links are not available, links that have the least number of SRLGs which are to be excluded are used.

When this CLI is not configured, the behavior remains the same as before, which is to turn off SRLG processing. Therefore, the no and default versions of the command takes you back to the default of SRLG processing being turned off.

Command Mode

Configuration sub-mode for RSVP

Command Syntax

srlg strict

no srlg strict

default srlg strict

Parameters

strictApplies strict SRLG constraints.

Example

The SRLGs of an interface can be configured using the following traffic-engineering CLIs.
switch(config)# interface Et1
switch(config-if-Et1)# traffic-engineering srlg 100

switch(config)# interface Et2
switch(config-if-Et2)# traffic-engineering srlg 200

vrf (MPLS tunnel termination)

The vrf (MPLS tunnel termination) command places the switch in MPLS Tunnel Termination VRF Configuration mode. There is one command available in this mode: qos map dscp to traffic-class (MPLS tunnel termination VRF).

Command Mode

MPLS Tunnel Termination Configuration mode

Command Syntax

vrf vrf_name

Parameter

vrf_name The name of the VRF to configure. This does not create a VRF. The VRF must be created with the vrf command in Configuration mode.

Example

These commands place the switch in MPLS Tunnel Termination VRF Configuration mode for VRF newVRF1.
switch(config)# mpls tunnel configuration
switch(config-mpls-tunnel-configuration)# vrf newVRF1
switch(config-mpls-tunnel-configuration-vrf-newVRF1)#