show mpls oam echo statistics through snmp-server host
Available Languages
Table Of Contents
show mpls traffic tunnel backup
show mpls traffic-eng autoroute
show mpls traffic-eng auto-tunnel backup
show mpls traffic-eng auto-tunnel mesh
show mpls traffic-eng destination list
show mpls traffic-eng fast-reroute database
show mpls traffic-eng fast-reroute log reroutes
show mpls traffic-eng forwarding-adjacency
show mpls traffic-eng forwarding path-set
show mpls traffic-eng forwarding statistics
show mpls traffic-eng link-management admission-control
show mpls traffic-eng link-management advertisements
show mpls traffic-eng link-management bandwidth-allocation
show mpls traffic-eng link-management igp-neighbors
show mpls traffic-eng link-management interfaces
show mpls traffic-eng link-management summary
show mpls traffic-eng lsp attributes
show mpls traffic-eng process-restart iprouting
show mpls traffic-eng topology
show mpls traffic-eng topology path
show mpls traffic-eng tunnels statistics
show mpls traffic-eng tunnels summary
show running interface auto-template
show xtagatm cos-bandwidth-allocation
snmp-server enable traps (MPLS)
snmp-server enable traps mpls ldp
snmp-server enable traps mpls rfc ldp
snmp-server enable traps mpls rfc vpn
snmp-server enable traps mpls traffic-eng
snmp-server enable traps mpls vpn
status protocol notification static
show mpls oam echo statistics
To display statistics about Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) echo request packets, use the show mpls oam echo statistics command in privileged EXEC mode.
show mpls oam echo statistics [summary]
Syntax Description
summary
(Optional) Displays summary information about the echo request packets (that is, the type, length, values (TLVs) version and the return codes of echo packets are not displayed).
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can use the show mpls oam echo statistics command to display the following:
•
Currently configured TLV version for MPLS OAM operations.
•
•
If you enter the summary keyword, the Echo Reply count shows all the echo reply packets, regardless of whether they are valid responses to a sent request packet. Therefore, the number of return codes will not match the number of echo reply packets received.
Examples
The following example displays sample detailed output when the summary keyword is not specified:
Router# show mpls oam echo statisticsCisco TLV version: RFC 4379 CompliantReturn code distribution:!—Success (3) - 5 B—Unlabeled output interface (9) - 0 D—DS map mismatch (5) - 0 f—Forward Error Correction (FEC) mismatch (10) - 0 F—No FEC mapping (4) - 0 I—Unknown upstream interface index (6) - 0 L—Labeled output interface (8) - 0 m—Unsupported TLVs (2) - 0 M—Malformed echo request (1) - 0 N—No label entry (11) - 0 p—Premature termination of link-state packet (LSP) (13) - 0 P—No receive interface label protocol (12) - 0 U—Reserved (7) - 0 x—No return code (0) - 0 X—Undefined return code - 0Echo Requests: sent (5)/received (0)/timedout (0)/unsent (0) Echo Replies: sent (0)/received (5)/unsent (0)The following example displays sample output when the summary keyword is specified:
Router# show mpls oam echo statistics summary
Cisco TLV version: RFC 4379 CompliantEcho Requests: sent (5)/received (0)/timedout (0)/unsent (0) Echo Replies: sent (0)/received (5)/unsent (0)Table 121 describes the significant fields shown in the displays.
show mpls platform
To display platform-specific information, use the show mpls platform command in EXEC mode.
show mpls platform {common | eompls | gbte-tunnels | reserved-vlans vlan vlan-id | statistics [reset] | vpn-vlan-mapping}
Syntax Description
Defaults
This command has no default settings.
Command Modes
EXEC
Command History
12.2(17b)SXA
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Examples
This example shows how to display the counters for shared code between the LAN and WAN interfaces:
Router# show mpls platform commonCommon MPLS counters for LAN and WAN-------------------------------------No. of MPLS configured LAN interfaces = 12No. of cross-connect configured VLAN interfaces = 0Router#This example shows how to display the EoMPLS-enabled interface information:
Router# show mpls platform eomplsInterface VLANGigabitEthernet 101FastEthernet6/1 2022Router#This example shows how to display the GBTE-tunnels information:
Router# show mpls platform gbte-tunnelsTo From InLbl I/I/F kbps Kbits H/W InfoRouter#This example shows how to display the RP-reserved VLAN show commands:
Router# show mpls platform reserved-vlans vlan 1005
Note
This example shows how to display the information about the RP-control plane statistics:
Router# show mpls platform statisticsRP MPLS Control Plane Statistics:==================================================Reserved VLAN creates 0000000001Reserved VLAN frees 0000000000Reserved VLAN creation failures 0000000000Aggregate Label adds 0000000001Aggregate Label frees 0000000000Aggregate Labels in Superman 0000000001Feature Rsvd VLAN Reqs 0000000000Feature Gen Rsvd VLAN Reqs 0000000000Feature Rsvd VLAN Free Reqs 0000000000EoMPLS VPN# Msgs 0000000009EoMPLS VPN# Msg Failures 0000000000EoMPLS VPN# Msg Rsp Failures 0000000000EoMPLS VPN# Set Reqs 0000000010EoMPLS VPN# Reset Reqs 0000000008FIDB mallocs 0000000000FIDB malloc failures 0000000000FIDB frees 0000000000EoMPLS Req mallocs 0000000018EoMPLS Req malloc failures 0000000000EoMPLS Req frees 0000000018EoMPLS VPN# allocs 0000000010EoMPLS VPN# frees 0000000008EoMPLS VPN# alloc failures 0000000000GB TE tunnel additions 0000000000GB TE tunnel label resolves 0000000000GB TE tunnel deletions 0000000000GB TE tunnel changes 0000000000GB TE tunnel heads skips 0000000000gb_flow allocs 0000000000gb_flow frees 0000000000rsvp req creats 0000000000rsvp req frees 0000000000rsvp req malloc failures 0000000000gb_flow malloc failures 0000000000psb search failures 0000000000GB TE tunnel deleton w/o gb_flow 0000000000errors finding slot number 0000000000Router#This example shows how to reset the RP-control plane statistics counters:
Router# show mpls platform statistics resetResetting Const RP MPLS control plane software statistics ...GB TE tunnel additions 0000000000GB TE tunnel label resolves 0000000000GB TE tunnel deletions 0000000000GB TE tunnel changes 0000000000GB TE tunnel heads skips 0000000000gb_flow allocs 0000000000gb_flow frees 0000000000rsvp req creats 0000000000rsvp req frees 0000000000rsvp req malloc failures 0000000000gb_flow malloc failures 0000000000psb search failures 0000000000GB TE tunnel deleton w/o gb_flow 0000000000errors finding slot number 0000000000Router#This example shows how to display information about the VPN-to-VLAN mapping table:
Router# show mpls platform vpn-vlan-mappingVPN# Rsvd Vlan IDB Created Feature Has agg label In superman EoM data0 1025 Yes No No No No1 0 No No Yes Yes NoRouter#show mpls prefix-map
Note
To display the prefix map used to assign a quality of service (QoS) map to network prefixes that match a standard IP access list, use the show mpls prefix-map command in privileged EXEC mode.
show mpls prefix-map [prefix-map]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Not entering a specific prefix-map argument number causes all prefix maps to be displayed.
Examples
The following is sample output from the show mpls prefix-map command:
Router# show mpls prefix-map 2prefix-map 2 access-list 2 cos-map 2Table 122 describes the fields shown in the display.
Table 122 show mpls prefix-map Field Descriptions
prefix-map
Unique number of a prefix map.
access-list
Unique number of an access list.
cos-map
Unique number of a QoS map.
Related Commands
mpls prefix-map
Configures a router to use a specified QoS map when a label destination prefix matches the specified access-list.
show mpls static binding
To display Multiprotocol Label Switching (MPLS) static label bindings, use the show mpls static binding command in privileged EXEC mode.
show mpls static binding [ipv4 [vrf vrf-name]] [prefix {mask-length | mask}] [local | remote] [nexthop address]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
If you do not specify any optional arguments, the show mpls static binding command displays information about all static label bindings. Or the information can be limited to any of the following:
•
•
•
•
Examples
In the following output, the show mpls static binding ipv4 command with no optional arguments displays all static label bindings:
Router# show mpls static binding ipv410.0.0.0/8: Incoming label: none;Outgoing labels:10.13.0.8 explicit-null10.0.0.0/8: Incoming label: 55 (in LIB)Outgoing labels:10.0.0.66 260710.66.0.0/16: Incoming label: 17 (in LIB)Outgoing labels: NoneIn the following output, the show mpls static binding ipv4 command displays remote (outgoing) statically assigned labels only:
Router# show mpls static binding ipv4 remote10.0.0.0/8:Outgoing labels:10.13.0.8 explicit-null10.0.0.0/8:Outgoing labels:10.0.0.66 2607In the following output, the show mpls static binding ipv4 command displays local (incoming) statically assigned labels only:
Router# show mpls static binding ipv4 local10.0.0.0/8: Incoming label: 55 (in LIB)10.66.0.0/16: Incoming label: 17 (in LIB)In the following output, the show mpls static binding ipv4 command displays statically assigned labels for prefix 10.0.0.0 / 8 only:
Router# show mpls static binding ipv4 10.0.0.0/810.0.0.0/8: Incoming label: 55 (in LIB)Outgoing labels:10.0.0.66 2607In the following output, the show mpls static binding ipv4 command displays prefixes with statically assigned outgoing labels for next hop 10.0.0.66:
Router# show mpls static binding ipv4 10.0.0.0 8 nexthop 10.0.0.6610.0.0.0/8: Incoming label: 55 (in LIB)Outgoing labels:10.0.0.66 2607The following output, the show mpls static binding ipv4 vrf command displays static label bindings for a VPN routing and forwarding instance vpn100:
Router# show mpls static binding ipv4 vrf vpn100192.168.2.2/32: (vrf: vpn100) Incoming label: 100020Outgoing labels: None192.168.0.29/32: Incoming label: 100003 (in LIB)Outgoing labels: NoneRelated Commands
mpls static binding ipv4
Binds an IPv4 prefix or mask to a local or remote label.
show mpls static crossconnect
To display statically configured Label Forwarding Information Database (LFIB) entries, use the show mpls static crossconnect command in privileged EXEC mode.
show mpls static crossconnect [low label [high label]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify any label parameters, then all the configured static crossconnects are displayed.
Examples
The following output of the show mpls static crossconnect command shows the local and remote labels:
Router# show mpls static crossconnectLocal Outgoing Outgoing Next Hoplabel label interface45 46 pos5/0 point2pointTable 123 describes the significant fields shown in the display.
Related Commands
mpls static crossconnect
Configures an LFIB entry for the specified incoming label and outgoing interface.
show mpls tp
To display information about Multiprotocol Label Switching (MPLS) transport profile (TP) tunnels, use the show mpls tp command in user EXEC or privileged EXEC mode.
show mpls tp [link numbers]
show mpls tp [lsps [node-id [options]]] [detail]
show mpls tp [summary]
show mpls tp [tunnel-tp [tunnel-num [options]]] [detail]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following examples display MPLS TP link number information:
Router> show mpls tp link-numbersMPLS-TP Link Numbers:Link Interface Next Hop RX Macs1 Ethernet0/0 10.10.10.102 Ethernet0/1 0180.c200.0000 0180.c200.0000Router> show mpls tp tunnel-tpMPLS-TP Tunnels:Tunnel Peer Active Local Out Out OperNumber global-id::node-id::tun LSP Label Label Interface State------ ----------------------- ------ ----- ----- --------- -----1 1::104.10.1.1::1 work 211 112 Et0/0 up2 20::104.10.1.1::2 work 221 122 Et0/0 up3 1::104.10.1.1::3 work 231 132 Et0/1 up4 0::10.20.20.4::4 work 241 142 Et0/1 up5 1::104.01.1.1::5 work 251 152 Et0/0 upRelated Commands
show mpls traffic tunnel backup
To display information about the backup tunnels that are currently configured, use the show mpls traffic tunnel backup command in user EXEC or privileged EXEC mode.
show mpls traffic tunnel backup tunneltunnel-id
Syntax Description
Command Default
Information about currently configured backup tunnels is not displayed.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show mpls traffic tunnel backup tunnel tunnel-id command:
Router# show mpls traffic tunnel backup tunnel1000Tunnel1000 Dest: 10.0.0.9 State: Upany-pool cfg 100 inuse 0 num_lsps 0protects: ATM0.1Table 124 describes the significant fields shown in the display.
Related Commands
tunnel mpls traffic-eng backup-bw
Specifies what types of LSPs can use a backup tunnel, whether the backup tunnel should provide bandwidth protection, and if so, how much.
show mpls traffic-eng autoroute
To display tunnels announced to the Interior Gateway Protocol (IGP), including interface, destination, and bandwidth, use the show mpls traffic-eng autoroute command in user EXEC or privileged EXEC mode.
show mpls traffic-eng autoroute
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The enhanced shortest path first (SPF) calculation of the IGP has been modified so that it uses traffic engineering tunnels. This command shows which tunnels IGP is currently using in its enhanced SPF calculation (that is, which tunnels are up and have autoroute configured).
Examples
The following is sample output from the show mpls traffic-eng autoroute command.
Note that the tunnels are organized by destination. All tunnels to a destination carry a share of the traffic tunneled to that destination.
Router# show mpls traffic-eng autorouteMPLS TE autorouting enableddestination 0002.0002.0002.00 has 2 tunnelsTunnel1021 (traffic share 10000, nexthop 10.2.2.2, absolute metric 11)Tunnel1022 (traffic share 3333, nexthop 10.2.2.2, relative metric -3)destination 0003.0003.0003.00 has 2 tunnelsTunnel1032 (traffic share 10000, nexthop 172.16.3.3)Tunnel1031 (traffic share 10000, nexthop 172.16.3.3, relative metric -1)Table 125 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng auto-tunnel backup
To display information about dynamically created Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels, use the show mpls traffic-eng auto-tunnel backup command in user EXEC or privileged EXEC mode.
show mpls traffic-eng auto-tunnel backup
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show mpls traffic-eng auto-tunnel backup command.
Router# show mpls traffic-eng auto-tunnel backupState: EnabledTunnel Count: 3 (up:2, down: 1)Tunnel ID Range: 65436-65535Create Nhop only: YesSRLG: Not configuredDelete unused tunnels after: 50 SecondsConfig:Unnumbered i/f: Looback0Affinity: 0x2/0xFFFFTable 125 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng auto-tunnel mesh
To display the cloned mesh tunnel interfaces of each autotemplate interface and the current range of mesh tunnel interface numbers, use the show mpls traffic-eng auto-tunnel mesh command in user EXEC mode or privileged EXEC mode.
show mpls traffic-eng auto-tunnel mesh
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is output from the show mpls traffic-eng auto-tunnel mesh command that shows the cloned mesh tunnel interfaces for autotemplate1 and shows the range of mesh tunnel interface numbers. Information for only one autotemplate is displayed because only one autotemplate was configured.
Router# show mpls traffic-eng auto-tunnel meshAuto-Template1:Using access-list 1 to clone the following tunnel interfaces:Destination Interface----------- ---------10.2.2.2 Tunnel6433610.3.3.3 Tunnel64337Mesh tunnel interface numbers: min 64336 max 65337Table 127 describes the significant fields shown in the display.
Related Commands
interface auto-template
Creates the template interface.
mpls traffic-eng auto-tunnel mesh tunnel-num
Configures the range of mesh tunnel interface numbers.
show mpls traffic-eng destination list
To display an Multiprotocol Label Switching (MPLS) traffic engineering (TE) point-to-multipoint (P2MP) destination list, use the show mpls traffic-eng destination list command in user EXEC or privileged EXEC configuration mode.
show mpls traffic-eng destination list [name destination-list-name | identifier destination-list-identifier]
Syntax Description
name destination-list-name
(Optional) Specifies the name of a destination list.
identifier destination-list-identifier
(Optional) Specifies the number of a destination list.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
This command displays the information about any destination lists configured for an MPLS TE P2MP configuration.
Examples
The following example displays information about a destination list:
Router# show mpls traffic-eng destination-listDestination list: name p2mp-list1ip 10.3.3.3 path-option 1 dynamicip 10.4.4.4 path-option 15 explicit identifier 4ip 10.5.5.5 path-option 2 explicit name r1-r2-r4-r5Table 128 describes the significant fields shown in the display.
Related Commands
mpls traffic-eng destination-list
Creates a destination list for MPLS Point-to-Multipoint Traffic Engineering.
show mpls traffic-eng fast-reroute database
To display the contents of the Multiprotocol Label Switching (MPLS) traffic engineering (TE) Fast Reroute (FRR) database, use the show mpls traffic-eng fast-reroute database command in user EXEC or privileged EXEC mode.
Cisco IOS Release 15.0(1)M and Later
show mpls traffic-eng fast-reroute database [interface type number | labels low-label [-high-label]] [backup-interface {tunnel tunnel-number | unresolved}] [role {head | middle}] [state {active | ready | requested}] [detail] [vrf name]
Cisco IOS Releases 12.0S and 12.2S
show mpls traffic-eng fast-reroute database [destination-prefix slot slot-number | interface type number | labels low-label [-high-label]] [backup-interface {tunnel tunnel-number | unresolved}] [role {head | middle}] [state {active | ready | requested}] [detail] [vrf name]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
Sample Output for Cisco IOS Releases 12.0S and 12.2S
The following is sample output from the show mpls traffic-eng fast-reroute database command at a tunnel head link:
Router# show mpls traffic-eng fast-reroute database 10.0.0.0Tunnel head fast reroute information:Prefix Tunnel In-label Out intf/label FRR intf/label Status10.0.0.0/16 Tu111 Tun hd PO0/0:Untagged Tu4000:16 ready10.0.0.0/16 Tu449 Tun hd PO0/0:Untagged Tu4000:736 ready10.0.0.0/16 Tu314 Tun hd PO0/0:Untagged Tu4000:757 ready10.0.0.0/16 Tu313 Tun hd PO0/0:Untagged Tu4000:756 readyTable 129 describes the fields shown in the display.
The following is sample output from the show mpls traffic-eng fast-reroute database command with the detail keyword included at a tunnel head link:
Router# show mpls traffic-eng fast-reroute database 10.0.0.0. detailLFIB FRR Database Summary:Total Clusters: 2Total Groups: 2Total Items: 789Link 10:PO5/0 (Down, 1 group)Group 51:PO5/0->Tu4000 (Up, 779 members)Prefix 10.0.0.0/16, Tu313, activeInput label Tun hd, Output label PO0/0:773, FRR label Tu4000:773Prefix 10.0.0.0/16, Tu392, activeInput label Tun hd, Output label PO0/0:775, FRR label Tu4000:775Prefix 10.0.0.0/16, Tu111, activeInput label Tun hd, Output label PO0/0:16, FRR label Tu4000:16Prefix 10.0.0.0/16, Tu394, activeInput label Tun hd, Output label PO0/0:774, FRR label Tu4000:774Table 130 describes the significant fields when the detail keyword is used.
The following is sample output from the show mpls traffic-eng fast-reroute database command with the labels keyword specified at a midpoint link:
Router# show mpls traffic-eng fast-reroute database labels 250-255Tunnel head fast reroute information:Prefix Tunnel In-label Outintf/label FRR intf/label StatusLSP midpoint frr information:LSP identifier In-label Out intf/label FRR intf/label Status10.110.0.10 229 [7334] 255 PO0/0:694 Tu4000:694 active10.110.0.10 228 [7332] 254 PO0/0:693 Tu4000:693 active10.110.0.10 227 [7331] 253 PO0/0:692 Tu4000:692 active10.110.0.10 226 [7334] 252 PO0/0:691 Tu4000:691 active10.110.0.10 225 [7333] 251 PO0/0:690 Tu4000:690 active10.110.0.10 224 [7329] 250 PO0/0:689 Tu4000:689 activeMPLS Traffic Engineering Point-to-Multipoint Fast Reroute Information
The following example shows MPLS TE P2MP information as part of the command output.
Router> show mpls traffic-eng fast-reroute databaseP2P Headend FRR information:Protected tunnel In-label Out intf/label FRR intf/label Status--------------------------- -------- -------------- -------------- ------Tunnel1 Tun hd Et0/1:20 Tu777:20 readyP2P LSP midpoint frr information:LSP identifier In-label Out intf/label FRR intf/label Status--------------------------- -------- -------------- -------------- ------P2MP Sub-LSP FRR information:Sub-LSP identifiersrc_lspid[subid]->dst_tunid In-label Out intf/label FRR intf/label Status--------------------------- -------- -------------- -------------- ------10.1.1..201_1[1]->10.1.1..203_22 Tun hd Et0/0:20 Tu666:20 ready10.1.1..201_1[2]->10.1.1..206_22 Tun hd Et0/0:20 Tu666:20 ready10.1.1..201_1[3]->10.1.1..213_22 Tun hd Et0/0:20 Tu666:20 readyTable 131 describes the significant field shown in the display.
The detail keyword provides more information about the P2MP LSPs:
Router# show mpls traffic-eng fast-reroute database detailFRR Database Summary:Number of protected interfaces: 1Number of protected tunnels: 2Number of backup tunnels: 1Number of active interfaces: 0P2MP Sub-LSPs:Tun ID: 1, LSP ID: 9, Source: 10.2.0.1Destination: 10.2.5.3, Subgroup ID: 19State : ReadyInLabel : Tunnel HeadOutLabel : Se6/0:16FRR OutLabel : Tu100:16Related Commands
show mpls traffic-eng fast-reroute log reroutes
Displays contents of the Fast Reroute event log.
show mpls traffic-eng fast-reroute log reroutes
To display the contents of the Fast Reroute event log, use the show mpls traffic-eng fast-reroute log reroutes command in user EXEC mode.
show mpls traffic-eng fast-reroute log reroutes
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
user EXEC
Command History
Examples
The following example shows output from the show mpls traffic-eng fast-reroute log reroutes command:
Router# show mpls traffic-eng fast-reroute log reroutesWhen Interface Event Rewrites Duration CPU msecs Suspends Errors00:27:39 PO0/0 Down 1079 30 msecs 30 0 000:27:35 PO0/0 Up 1079 40 msecs 40 0 0Table 132 describes significant fields shown in the display.
show mpls traffic-eng forwarding-adjacency
To display traffic engineering (TE) tunnels that are advertised as links in an Interior Gateway Protocol (IGP) network, use the show mpls traffic-eng forwarding-adjacency command in user EXEC or privileged EXEC mode.
show mpls traffic-eng forwarding-adjacency [ip-address]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use the show mpls traffic-eng forwarding-adjacency command to display information about tunnels configured with the tunnel mpls traffic-eng forwarding-adjacency command.
Examples
The following is sample output from the show mpls traffic-eng forwarding-adjacency command:
Router# show mpls traffic-eng forwarding-adjacencydestination 0168.0001.0007.00 has 1 tunnelsTunnel7 (traffic share 100000, nexthop 192.168.1.7)(flags:Announce Forward-Adjacency, holdtime 0)Router# show mpls traffic-eng forwarding-adjacency 192.168.1.7destination 0168.0001.0007.00 has 1 tunnelsTunnel7 (traffic share 100000, nexthop 192.168.1.7)(flags:Announce Forward-Adjacency, holdtime 0)Related Commands
show mpls traffic-eng forwarding path-set
To display the sublabel switched paths (sub-LSPs) that originate from the headend router, use the show mpls traffic-eng forwarding path-set command in user EXEC or privileged EXEC mode.
show mpls traffic-eng forwarding path-set [brief | detail]
Syntax Description
brief
(Optional) Displays information about the sub-LSPs in a table format.
detail
(Optional) Displays detailed information about the sub-LSPs.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following example displays information about the sub-LSPs in a summary format, including the number of sub-LSPs and the number of paths from the headend router.
Router> show mpls traffic-eng forwarding path-setID Input I/F LSPID InLabel PathCnt subLSPCnt---- --------- ----- ------- ------- ---------9F000001 Tu22 1 none 2 6The following example shows six sub-LSPs originating at the headend router and going to different destinations. All the sub-LSPs belong to the same path set, which is a collection of paths. The path set is given a unique ID, which is shown in the PSID column of the example:
Router# show mpls traffic-eng forwarding path-set briefSub-LSP Identifiersrc_lspid[subid]->dst_tunid InLabel Next Hop I/F PSID--------------------------- ------- ------------- ------ ----10.1.1.201_1[1]->10.1.1.203_22 none 10.0.0.205 Et0/0 9F00000110.1.1.201_1[2]->10.1.1.206_22 none 10.0.0.205 Et0/0 9F00000110.1.1.201_1[3]->10.1.1.213_22 none 10.0.0.205 Et0/0 9F00000110.1.1.201_1[4]->10.1.1.214_22 none 10.0.1.202 Et0/1 9F00000110.1.1.201_1[5]->10.1.1.216_22 none 10.0.1.202 Et0/1 9F00000110.1.1.201_1[6]->10.1.1.217_22 none 10.0.1.202 Et0/1 9F000001The show mpls traffic-eng forwarding path-set detail command shows more information about the sub-LSPs that originate from the headend router. For example:
Router# show mpls traffic-eng forwarding path-set detailLSP: Source: 10.1.0.1, TunID: 100, LSPID: 7Destination: 10.2.0.1, P2MP Subgroup ID: 1Path Set ID: 0x30000001OutLabel : Serial2/0, 16Next Hop : 10.1.3.2FRR OutLabel : Tunnel666, 16LSP: Source: 10.1.0.1, TunID: 100, LSPID: 7Destination: 10.3.0.1, P2MP Subgroup ID: 2Path Set ID: 0x30000001OutLabel : Serial2/0, 16Next Hop : 10.1.3.2FRR OutLabel : Tunnel666, 16Table 133 describes the significant fields shown in the display.
Related Commands
ip path-option
Species an explicit or dynamic path option for a particular destination address in a destination list
show mpls traffic-eng forwarding statistics
To display information about Multiprotocol Label Switching (MPLS) traffic engineering (TE) point-to-pultipoint (P2MP) paths and sublabel switched paths (sub-LSPs), use the show mpls traffic-eng forwarding statistics command in user EXEC or privileged EXEC mode.
show mpls traffic-eng forwarding statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following example displays informtion about MPLS TE P2MP paths and sub-LSPs:
Router# show mpls traffic-eng forwarding statisticsTE P2MP:Statistics:Path Set Creation: 2Path Set Deletion: 0Input Label Allocation for Path Sets: 2Input Label Free: 0Current Label Allocated: 2PSI Nodes Allocated: 2PSI Nodes Freed: 0Add sub-LSP to Path Set: 5Delete sub-LSP from Path Set 0 (prune: 0, flush: 0)Update Path for FRR: 4Failures:NoneTable 134 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng forwarding path-set
Display the sub-LSPs that originate from the headend router.
show mpls traffic-eng link-management admission-control
To show which tunnels were admitted locally and their parameters (such as, priority, bandwidth, incoming and outgoing interface, and state), use the show mpls traffic-eng link-management admission-control command in user EXEC or privileged EXEC mode.
show mpls traffic-eng link-management admission-control [interface-name]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show mpls traffic-eng link-management admission-control command:
Router # show mpls traffic-eng link-management admission-controlSystem Information::Tunnels Count: 4Tunnels Selected: 4TUNNEL ID UP IF DOWN IF PRIORITY STATE BW (kbps)10.106.0.6 1000_1 AT1/0.2 - 0/0 Resv Admitted 010.106.0.6 2000_1 Et4/0/1 - 1/1 Resv Admitted 010.106.0.6 1_2 Et4/0/1 Et4/0/2 1/1 Resv Admitted 3000 R10.106.0.6 2_2 AT1/0.2 AT0/0.2 1/1 Resv Admitted 3000 RTable 135 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng link-management advertisements
To display local link information that Multiprotocol Label Switching (MPLS) traffic engineering link management is flooding into the global traffic engineering topology, use the show mpls traffic-eng link-management advertisements command in user EXEC or privileged EXEC mode.
show mpls traffic-eng link-management advertisements
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output from the show mpls traffic-eng link-management advertisements command:
Router# show mpls traffic-eng link-management advertisementsFlooding Status: readyConfigured Areas: 1IGP Area[1] ID:: isis level-1System Information::Flooding Protocol: ISISHeader Information::IGP System ID: 0001.0000.0001.00MPLS TE Router ID: 10.106.0.6Flooded Links: 1Link ID:: 0Link IP Address: 10.1.0.6IGP Neighbor: ID 0001.0000.0001.02Admin. Weight: 10Physical Bandwidth: 10000 kbits/secMax Reservable BW: 5000 kbits/secDownstream::Reservable Bandwidth[0]: 5000 kbits/secReservable Bandwidth[1]: 2000 kbits/secReservable Bandwidth[2]: 2000 kbits/secReservable Bandwidth[3]: 2000 kbits/secReservable Bandwidth[4]: 2000 kbits/secReservable Bandwidth[5]: 2000 kbits/secReservable Bandwidth[6]: 2000 kbits/secReservable Bandwidth[7]: 2000 kbits/secAttribute Flags: 0x00000000Table 136 describes the significant fields shown in the display.
The following is sample output from the show mpls traffic-eng link-management advertisements command with the enhanced output, which shows the "IGP recovering" status, from the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature:
Router# show mpls traffic-eng link-management advertisementsshow mpls traffic-eng link-management advertisementsFlooding Status: ready (IGP recovering)Configured Areas: 1IGP Area[1] ID:: ospf area nilSystem Information::Flooding Protocol: OSPFHeader Information::Table 137 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng link-management bandwidth-allocation
To display current local link information, use the show mpls traffic-eng link-management bandwidth-allocation command in user EXEC or privileged EXEC mode.
show mpls traffic-eng link-management bandwidth-allocation [summary] [interface-type interface-number]
Syntax Description
summary
(Optional) Displays summary of bandwidth allocation.
interface-type interface-number
(Optional) The specified interface that admitted tunnels.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Advertised information might differ from the current information, depending on how flooding was configured.
Examples
Interface Example
The following is sample output from the show mpls traffic-eng link-management bandwidth-allocation command for a specified interface:
Router# show mpls traffic-eng link-management bandwidth-allocation gigabitEthernet 4/0/1System Information::Links Count: 2Bandwidth Hold Time: max. 15 secondsLink ID:: Ge4/0/1 (10.1.0.6)Link Status:Physical Bandwidth: 10000 kbits/secMax Reservable BW: 5000 kbits/sec (reserved:0% in, 60% out)BW Descriptors: 1MPLS TE Link State: MPLS TE on, RSVP on, admin-up, floodedInbound Admission: reject-hugeOutbound Admission: allow-if-roomAdmin. Weight: 10 (IGP)IGP Neighbor Count: 1Up Thresholds: 15 30 45 60 75 80 85 90 95 96 97 98 99 100 (default)Down Thresholds: 100 99 98 97 96 95 90 85 80 75 60 45 30 15 (default)Downstream Bandwidth Information (kbits/sec):KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED0 0 0 0 01 0 0 3000 30002 0 0 0 30003 0 0 0 30004 0 0 0 30005 0 0 0 30006 0 0 0 30007 0 0 0 3000Table 138 describes the significant fields shown in the display.
Summary Example for Regular TE (or Russian Dolls Model [RDM] DiffServ-Aware TE) with Multiple Interfaces
The following is sample output from the show mpls traffic-eng link-management bandwidth-allocation summary command for all the configured interfaces:
Router# show mpls traffic-eng link-management bandwidth-allocation summaryinterface Intf Max Intf Avail Sub Max Sub Availkbps kbps kbps kbpsEt0/0 47000 42500 42000 40500Et1/0 7500 7500 0 0
Table 139 describes the significant fields shown in the display.
Summary Example for Regular TE (or Russian Dolls Model [RDM] DiffServ-Aware (DS) TE) with a Single Interface
The following is sample output from the show mpls traffic-eng link-management bandwidth-allocation summary command for one configured interface:
Router# show mpls traffic-eng link-management bandwidth-allocation summary Ethernet 0/0interface Intf Max Intf Avail Sub Max Sub Availkbps kbps kbps kbpsEt0/0 47000 42500 42000 40500See Table 139 for an explanation of the fields.
Summary Example with a Specified Interface for Maximum Allocation Model (MAM) DS-TE
The following is sample output from the show mpls traffic-eng link-management bandwidth-allocation summary command for all the configured interfaces:
Router# show mpls traffic-eng link-management bandwidth-allocation summaryinterface Intf Max BC0 Max BC0 Avail BC1 Max BC1 Availkbps kbps kbps kbps kbpsEt0/0 45000 40000 37000 30000 28500Et1/0 0 0 0 0 0Table 140 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng link-management igp-neighbors
To display Interior Gateway Protocol (IGP) neighbors, use the show mpls traffic-eng link-management igp-neighbors command in user EXEC or privileged EXEC mode.
show mpls traffic-eng link-management igp-neighbors [interface-type number | igp-id {isis isis-address | ospf ospf-id} | ip ip-address]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output from the show mpls traffic-eng link-management igp-neighbors command:
Router# show mpls traffic-eng line-management igp-neighborsLink ID:: Et0/2Neighbor ID: 0000.0024.0004.02 (area: isis level-1, IP: 10.0.0.0)Link ID:: PO1/0/0Neighbor ID: 0000.0026.0001.00 (area: isis level-1, IP: 172.16.1.2)Table 141 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng link-management interfaces
To display interface resource and configuration information, use the show mpls traffic-eng link-management interfaces command in user EXEC or privileged EXEC mode.
show mpls traffic-eng link-management interfaces [interface-name]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use this command to display resource and configuration information for all configured interfaces.
Examples
The following is sample output from the show mpls traffic-eng link-management interfaces command:
Router# show mpls traffic-eng link-management interfaces Et4/0/1System Information::Links Count: 2Link ID:: Et4/0/1 (10.1.0.6)Link Status:Physical Bandwidth: 10000 kbits/secMax Reservable BW: 5000 kbits/sec (reserved:0% in, 60% out)MPLS TE Link State: MPLS TE on, RSVP on, admin-up, floodedInbound Admission: reject-hugeOutbound Admission: allow-if-roomAdmin. Weight: 10 (IGP)IGP Neighbor Count: 1IGP Neighbor: ID 0001.0000.0001.02, IP 10.0.0.0 (Up)Flooding Status for each configured area [1]:IGP Area[1]: isis level-1: floodedThe following is sample output from the show mpls traffic-eng link-management interfaces command when SRLGs are configured:
Router# show mpls traffic-eng link-management interfaces pos3/1System Information::Links Count: 11Link ID:: PO3/1 (10.0.0.33)Link Status:SRLGs: 1 2Physical Bandwidth: 2488000 kbits/secMax Res Global BW: 20000 kbits/sec (reserved:0% in, 0% out)Max Res Sub BW: 5000 kbits/sec (reserved:0% in, 0% out)MPLS TE Link State: MPLS TE on, RSVP on, admin-up, floodedInbound Admission: allow-allOutbound Admission: allow-if-roomAdmin. Weight: 10 (IGP)IGP Neighbor Count: 1IGP Neighbor: ID 0000.0000.0004.00, IP 10.0.0.34 (Up)Flooding Status for each configured area [1]:IGP Area[1]: isis level-2: flooded
Table 142 describes the significant fields shown in the displays.
Related Commands
show mpls traffic-eng link-management summary
To display a summary of link management information, use the show mpls traffic-eng link-management summary command in user EXEC or privileged EXEC mode.
show mpls traffic-eng link-management summary [interface-name]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show mpls traffic-eng link-management summary command:
Router# show mpls traffic-eng link-management summarySystem Information::Links Count: 2Flooding System: enabledIGP Area ID:: isis level-1Flooding Protocol: ISISFlooding Status: data floodedPeriodic Flooding: enabled (every 180 seconds)Flooded Links: 1IGP System ID: 0001.0000.0001.00MPLS TE Router ID: 10.106.0.6IGP Neighbors: 1Link ID:: Et4/0/1 (10.1.0.6)Link Status:Physical Bandwidth: 10000 kbits/secMax Reservable BW: 5000 kbits/sec (reserved:0% in, 60% out)MPLS TE Link State: MPLS TE on, RSVP on, admin-up, floodedInbound Admission: reject-hugeOutbound Admission: allow-if-roomAdmin. Weight: 10 (IGP)IGP Neighbor Count: 1Link ID:: AT0/0.2 (10.42.0.6)Link Status:Physical Bandwidth: 155520 kbits/secMax Reservable BW: 5000 kbits/sec (reserved:0% in, 0% out)MPLS TE Link State: MPLS TE on, RSVP onInbound Admission: allow-allOutbound Admission: allow-if-roomAdmin. Weight: 10 (IGP)IGP Neighbor Count: 0Table 143 describes the significant fields shown in the display.
The following is sample output from the show mpls traffic-eng link-management summary command with the enhanced output, which shows the "IGP recovering" status, from the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature:
Router# show mpls traffic-eng link-management summarySystem Information::Links Count: 3Flooding System: enabled (IGP recovering)IGP Area ID:: ospf area nilFlooding Protocol: OSPFFlooding Status: data floodedPeriodic Flooding: enabled (every 180 seconds)Flooded Links: 0Table 144 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng lsp attributes
To display global label switched path (LSP) attribute lists, use the show mpls traffic-eng lsp attributes command in user EXEC or privileged EXEC mode.
show mpls traffic-eng lsp attributes [name string] [internal]
Syntax Description
name
(Optional) Identifies a specific LSP attribute list.
string
Describes the string argument.
internal
(Optional) Displays LSP atrribute list internal information.
Command Default
If no keywords or arguments are specified, all LSP attribute lists are displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use this command to display information about all LSP attribute lists or a specific LSP attribute list.
Examples
The following example shows output from the show mpls traffic-eng lsp attributes command:
Router# show mpls traffic-eng lsp attributesLIST list1affinity 0xFF mask 0xFFFFFFFFauto-bw collect-bwbandwidth 12protection fast-reroute bw-protectlockdownpriority 2 2record-route LIST 2bandwidth 5000LIST hiprioritypriority 0 0!Table 145 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng process-restart iprouting
To display the status of IP routing and Multiprotocol Label Switching (MPLS) traffic engineering synchronization after an IP routing process restart, use the show mpls traffic-eng process-restart iprouting command in user EXEC or privileged EXEC mode.
show mpls traffic-eng process-restart iprouting
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command displays information about the synchronization between the IP routing process and MPLS TE that you can provide to your technical support representative when you are reporting a problem.
All counters are set to zero when the system process initializes and are not reset no matter how often the IP routing process restarts.
The following is sample output from the show mpls traffic-eng process-restart iprouting command when an IP routing process has restarted normally:
Router# show mpls traffic-eng process-restart iproutingIP Routing Restart Statistics:Current State: NORMFlushing State: IDLEState Entered Count Timestamp Timestamp TimestampINIT 1 05/10/06-13:07:01NORM 3 05/10/06-13:07:10 05/10/06-13:10:45 05/10/06-13:11:5NORM-SPCT 0AWAIT-CFG 2 05/10/06-13:10:32 05/10/06-13:11:45CFG 2 05/10/06-13:10:32 05/10/06-13:11:45CMPL-FLSH 0NCMPL-FLSH 2 05/10/06-13:10:32 05/10/06-13:11:45NCMPL-FLSHD 2 05/10/06-13:10:32 05/10/06-13:11:45Stuck State Count Timestamp Timestamp TimestampNo Stuck states encounteredCounter Count Timestamp Timestamp TimestampReg Succeed 40 05/10/06-13:11:51 05/10/06-13:11:45 05/10/06-13:11:45Reg Fail 0Incarnation 5 05/10/06-13:11:45 05/10/06-13:11:45 05/10/06-13:10:37Flushing 2 05/10/06-13:10:32 05/10/06-13:11:45Table 146 describes the normal output of the significant fields shown in the display. You should contact your technical support representative if your display has values other than those described in the table.
Related Commands
debug mpls traffic-eng process-restart
Displays information about process restarts for reporting to your technical support representative.
show mpls traffic-eng topology
To display the Multiprotocol Label Switching (MPLS) traffic engineering global topology as currently known at the node, use the show mpls traffic-eng topology command in user EXEC or privileged EXEC mode.
show mpls traffic-eng topology [area area-id | level-1 | level-2] [ip-address [brief | internal] | igp-id {isis nsapaddr | ospf ip-address [network | router]} [brief] | srlg]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following example shows output from the show mpls traffic-eng topology command:
Router# show mpls traffic-eng topologyMy_System_id: 0000.0000.0001.00 (isis 1 level-2)My_System_id: 10.10.10.10 (ospf 100 area 0)My_BC_Model_Type: MAMSignalling error holddown: 10 sec Global Link Generation 56IGP Id: 0000.0000.0001.00, MPLS TE Id: 10.10.10.10 Router Node (isis 1 level-2)Link[0]:Point-to-Point, Nbr IGP Id:0000.0000.0002.00, Nbr Node Id:6, gen:56Frag Id:0, Intf Address:10.2.2.1, Intf Id:0Nbr Intf Address:10.2.2.2, Nbr Intf Id:0TE Metric:10, IGP Metric:10, Attribute Flags:0x0Switching Capability:, Encoding:BC Model ID:MAMPhysical BW:155520 (kbps), Max Reservable BW:1000 (kbps)BC0:600 (kbps) BC1:400 (kbps)Total Allocated ReservableBW (kbps) BW (kbps)--------------- -----------TE-class[0]: 0 600TE-class[1]: 0 400TE-class[2]: 0 0TE-class[3]: 0 0TE-class[4]: 0 600TE-class[5]: 0 400TE-class[6]: 0 0TE-class[7]: 0 0Link[1]:Point-to-Point, Nbr IGP Id:0000.0000.0002.00, Nbr Node Id:6, gen:56Frag Id:0, Intf Address:10.1.1.1, Intf Id:0Nbr Intf Address:10.1.1.2, Nbr Intf Id:0TE Metric:10, IGP Metric:10, Attribute Flags:0x0Switching Capability:, Encoding:BC Model ID:MAMPhysical BW:155520 (kbps), Max Reservable BW:1000 (kbps)BC0:600 (kbps) BC1:400 (kbps)Total Allocated ReservableBW (kbps) BW (kbps)--------------- -----------TE-class[0]: 10 590TE-class[1]: 0 400TE-class[2]: 0 0TE-class[3]: 0 0TE-class[4]: 0 600TE-class[5]: 0 400TE-class[6]: 0 0TE-class[7]: 0 0Table 147 describes significant fields shown in the display.
Related Commands
show mpls traffic-eng topology path
To show the properties of the best available path to a specified destination that satisfies certain constraints, use the show mpls traffic-eng topology path command in user EXEC or privileged EXEC mode.
show mpls traffic-eng topology path {tunnel-interface [destination address]
| destination address} [bandwidth value] [priority value [value]]
[affinity value [mask mask]]Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The specified constraints override any constraints obtained from a reference tunnel.
Examples
The following is sample output from the show mpls traffic-eng topology path command:
Router # show mpls traffic-eng topology path Tunnel1 bandwidth 1000Query Parameters:Destination:10.112.0.12Bandwidth:1000Priorities:1 (setup), 1 (hold)Affinity:0x0 (value), 0xFFFF (mask)Query Results:Min Bandwidth Along Path:2000 (kbps)Max Bandwidth Along Path:5000 (kbps)Hop 0:10.1.0.6 :affinity 00000000, bandwidth 2000 (kbps)Hop 1:10.1.0.10 :affinity 00000000, bandwidth 5000 (kbps)Hop 2:10.43.0.10 :affinity 00000000, bandwidth 2000 (kbps)Hop 3:10.112.0.12Table 148 describes the significant fields shown in the display.
show mpls traffic-eng tunnels
To display information about traffic engineering (TE) tunnels, use the show mpls traffic-eng tunnels command in user EXEC or privileged EXEC mode.
show mpls traffic-eng tunnels [[attributes list-name] [destination address] [down] [interface type number] [name name] [name-regexp reg-exp] [property {auto-tunnel {backup | mesh | primary} | backup-tunnel | fast-reroute}] [role {all | head | middle | remote | tail}] [source-id {ipaddress [tunnel-id]}] [suboptimal constraints {current | max | none}] [statistics] [summary] [up]] [accounting | backup | brief | protection]
Syntax Description
Command Default
General information about each MPLS TE tunnel known to the router is displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
To select the tunnels for which information is displayed, use the auto-tunnel, backup-tunnel, attributes, destination, interface, name, name-regexp, property, role, source-id, suboptimal constraints, up, and down keywords singly or combined.
To select the type of information displayed about the selected tunnels, use the accounting, backup, protection, statistics, and summary keywords.
The auto-tunnel, backup-tunnel, and property keywords display the same information, except that the property keyword restricts the display to autotunnels, backup tunnels, or tunnels that are FRR-protected.
The name-regexp keyword displays output for each tunnel whose name contains a specified string. For example, if there are tunnels named iou-100-t1, iou-100-t2, and iou-100-t100, the show mpls traffic-eng tunnels name-regexp iou-100 command displays output for the three tunnels whose name contains the string iou-100.
If you specify the name keyword, the command output is displayed only if the command name is an exact match, for example, iou-100-t1.
The nonbrief and nonsummary formats of the output contain the history of the LSP selection.
"Reroute Pending" State Changes in Cisco IOS Release 12.2(33)SRE
In releases earlier than Cisco IOS Release 12.2(33)SRE, MPLS TE P2P tunnels display "reroute pending" during reoptimization until the "delayed clean" status of the old path is complete. During the "delayed clean" process, the command output displays the following status:
Router# show mpls traffic-eng tunnels tunnel 534Name: Router_t534 (Tunnel534) Destination: 10.30.30.8Status:Admin: up Oper: up Path: valid Signalling: connectedpath option 10, type explicit PRIMARY_TO_8 (Basis for Setup, path weight 30)!!! path option 10 delayed clean in progress!!! Change in required resources detected: reroute pendingCurrently Signalled Parameters:Bandwidth: 300 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFFMetric Type: TE (default)In Cisco IOS Release 12.2(33)SRE and later releases, P2P and P2MP MPLS TE tunnels display "reroute pending" during reoptimization until the new path is used for forwarding. The "reroute pending" status is not displayed during the delayed clean operation. There is no change to data forwarding or tunnel creation. You might see the "reroute pending" status for a shorter time. In the following example, the "reroute pending" message appears, but the "delayed clean" message does not.
Router# show mpls traffic-eng tunnels tunnel 534Name: Router_t534 (Tunnel534) Destination: 10.30.30.8Status:Admin: up Oper: up Path: valid Signalling: connectedpath option 10, type explicit PRIMARY_TO_8 (Basis for Setup, path weight 30)Change in required resources detected: reroute pendingCurrently Signalled Parameters:Bandwidth: 300 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFFMetric Type: TE (default)Examples
The following is sample output from the show mpls traffic-eng tunnels brief command. It displays brief information about every MPLS TE tunnel known to the router.
Router# show mpls traffic-eng tunnels briefSignalling Summary:LSP Tunnels Process: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 3600 seconds, next in 1706 secondsTUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROTRouter_t1 10.112.0.12 - PO4/0/1 up/upRouter_t2 10.112.0.12 - unknown up/downRouter_t3 10.112.0.12 - unknown admin-downRouter_t1000 10.110.0.10 - unknown up/downRouter_t2000 10.110.0.10 - PO4/0/1 up/upDisplayed 5 (of 5) heads, 0 (of 0) midpoints, 0 (of 0) tailsTable 149 describes the significant fields shown in the display.
The following is sample output from the show mpls traffic-eng tunnels property fast-reroute brief command. It displays brief information about all MPLS TE tunnels acting as FRR backup tunnels (property backup-tunnel) for interfaces on the router.
Router# show mpls traffic-eng tunnels property fast-reroute briefSignalling Summary:LSP Tunnels Process: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 3600 seconds, next in 2231 secondsPeriodic FRR Promotion: every 300 seconds, next in 131 secondsPeriodic auto-bw collection: disabledTUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROTRouter_t2000 10.110.0.10 - PO4/0/1 up/upRouter_t2 10.112.0.12 - unknown up/downRouter_t3 10.112.0.12 - unknown admin-downDisplayed 3 (of 9) heads, 0 (of 1) midpoints, 0 (of 0) tailsThe following is sample output from the show mpls traffic-eng tunnels backup command. This command selects every MPLS TE tunnel known to the router and displays information about the FRR protection that each selected tunnel provides for interfaces on this router; the command does not generate output for tunnels that do not provide FRR protection of interfaces on this router.
Router# show mpls traffic-eng tunnels backupRouter_t578LSP Head, Tunnel578, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.88.88.88, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0, PO1/1, PO3/3Protected lsps: 1Backup BW: any pool unlimited; inuse: 100 kbpsRouter_t5710LSP Head, Tunnel5710, Admin: admin-down, Oper: downSrc 10.55.55.55, Dest 192.168.7.7, Instance 0Fast Reroute Backup Provided:Protected i/fs: PO1/1Protected lsps: 0Backup BW: any pool unlimited; inuse: 0 kbpsRouter_t5711LSP Head, Tunnel5711, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.7.7.7, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0Protected lsps: 2Backup BW: any pool unlimited; inuse: 6010 kbpsThe following is sample output from the show mpls traffic-eng tunnels property fast-reroute protection command. This command selects every MPLS TE tunnel known to the router that was signaled as a FRR-protected LSP (property fast-reroute) and displays information about the protection this router provides for each selected tunnel.
Router# show mpls traffic-eng tunnels property fast-reroute protectionRouter_t1LSP Head, Tunnel1, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.88.88.88, Instance 25Fast Reroute Protection: RequestedOutbound: FRR ReadyBackup Tu5711 to LSP nhopTu5711: out i/f: PO1/1, label: implicit-nullLSP signalling info:Original: out i/f: PO1/0, label: 12304, nhop: 10.1.1.7With FRR: out i/f: Tu5711, label: 12304LSP bw: 6000 kbps, Backup level: any unlimited, type: any poolRouter_t2LSP Head, Tunnel2, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.88.88.88, Instance 2Fast Reroute Protection: RequestedOutbound: FRR ReadyBackup Tu578 to LSP nhopTu578: out i/f: PO1/0, label: 12306LSP signalling info:Original: out i/f: PO3/3, label: implicit-null, nhop: 10.3.3.8With FRR: out i/f: Tu578, label: implicit-nullLSP bw: 100 kbps, Backup level: any unlimited, type: any poolr9_t1LSP Midpoint, signalled, connection upSrc 10.9.9.9, Dest 10.88.88.88, Instance 2347Fast Reroute Protection: RequestedInbound: FRR InactiveLSP signalling info:Original: in i/f: PO1/2, label: 12304, phop: 10.205.0.9Outbound: FRR ReadyBackup Tu5711 to LSP nhopTu5711: out i/f: PO1/1, label: implicit-nullLSP signalling info:Original: out i/f: PO1/0, label: 12305, nhop: 10.1.1.7With FRR: out i/f: Tu5711, label: 12305LSP bw: 10 kbps, Backup level: any unlimited, type: any poolThe following is sample output from the show mpls traffic-eng tunnels tunnel command. This command displays information about just a single tunnel.
Router# show mpls traffic-eng tunnels tunnel 1Name: swat76k1_t1 (Tunnel1) Destination: 10.0.0.4Status:Admin: admin-down Oper: down Path: not valid Signalling: Downpath option 1, type explicit gi7/4-R4Config Parameters:Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFFMetric Type: TE (default)AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-basedauto-bw: disabledShortest Unconstrained Path Info:Path Weight: 2 (TE)Explicit Route: 10.1.0.1 10.1.0.2 172.0.0.1 192.0.0.4History:Tunnel:Time since created: 13 days, 52 minutesNumber of LSP IDs (Tun_Instances) used: 0 swat76k1#swat76k1#sh mpls traf tun property ?auto-tunnel auto-tunnel created tunnelsbackup-tunnel Tunnels used as fast reroutefast-reroute Tunnels protected by fast reroute
The following is sample output from the show mpls traffic-eng tunnels accounting command. This command displays the rate of the traffic flow for the tunnels.Router# show mpls traffic-eng tunnels accountingTunnel1 (Destination 10.103.103.103; Name iou-100_t1)5 minute output rate 0 kbits/sec, 0 packets/secTunnel2 (Destination 10.103.103.103; Name iou-100_t2)5 minute output rate 0 kbits/sec, 0 packets/sec Tunnel100 (Destination 10.101.101.101; Name iou-100_t100)5 minute output rate 0 kbits/sec, 0 packets/sec Totals for 3 Tunnels5 minute output rate 0 kbits/sec, 0 packets/secWhen the MPLS TE P2MP feature is configured, the show mpls traffic-eng tunnels command categorizes the output as follows:
•
•
•
The following sample output of the show mpls traffic-eng tunnels brief command displays information about the P2MP tunnel and the sub-LSP:
Router# show mpls traffic-eng tunnels briefSignalling Summary:LSP Tunnels Process: runningPassive LSP Listener: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 60 seconds, next in 5 secondsPeriodic FRR Promotion: Not RunningPeriodic auto-bw collection: disabledP2P TUNNELS/LSPs:TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROTp2p-LSP 10.2.0.1 - Se2/0 up/upDisplayed 2 (of 2) heads, 0 (of 0) midpoints, 0 (of 0) tailsP2MP TUNNELS:DEST CURRENTINTERFACE STATE/PROT UP/CFG TUNID LSPIDTunnel2 up/up 3/10 2 1Tunnel5 up/down 1/10 5 2Displayed 2 (of 2) P2MP headsP2MP SUB-LSPS:SOURCE TUNID LSPID DESTINATION SUBID ST UP IF DOWN IF10.1.0.1 2 1 10.2.0.1 1 up head Se2/010.1.0.1 2 1 10.3.0.199 2 up head Et2/010.1.0.1 2 1 19.4.0.1 2 up head s2/010.1.0.1 2 2 1 9.4.0.1 2 up head s2/010.1.0.1 5 2 10.5.0.1 7 up head e2/0100.100.100.100 1 3 200.200.200.200 1 up ge2/0 s2/0100.100.100.100 1 3 10.1.0.1 1 up e2/0 tailDisplayed 7 P2MP sub-LSPs:5 (of 5) heads, 1 (of 1) midpoints, 1 (of 1) tails
The following is sample output from the show mpls traffic-eng tunnels command for a tunnel named t1. The output displays the following:•
•
•
•
Router# show mpls traffic-eng tunnels name t1Name:tagsw4500-9_t1 (Tunnel1) Destination:10.0.0.4Status:Admin:up Oper:up Path:valid Signalling:connectedpath option 1, type explicit pbr_south (Basis for Setup, path weight 30)path option 2, type dynamicConfig Parameters:Bandwidth:13 kbps (Global) Priority:7 7 Affinity:0x0/0xFFFFAutoRoute: disabled LockDown:disabled Loadshare:13 bw-basedauto-bw:(300/265) 53 Bandwidth Requested: 13Adjustment threshold: 5%Overflow Limit: 4 Overflow Threshold: 25%Overflow Threshold Crossed: 1Sample Missed: 1 Samples Collected: 1Active Path Option Parameters:State: dynamic path option 1 is activeBandwidthOverride: disabled LockDown: disabled Verbatim: disabledInLabel : -OutLabel : Serial3/0, 18RSVP Signalling Info:Src 10.0.0.1, Dst 10.0.0.4, Tun_Id 2, Tun_Instance 2RSVP Path Info:My Address: 10.105.0.1Explicit Route: 10.105.0.2 104.105.0.1 10.0.0.4Record Route: NONETspec: ave rate=13 kbits, burst=1000 bytes, peak rate=13 kbitsRecord Route: NONETspec: ave rate=13 kbits, burst=1000 bytes, peak rate=13 kbitsRSVP Resv Info:Record Route: NONEFspec: ave rate=13 kbits, burst=1000 bytes, peak rate=13 kbitsShortest Unconstrained Path Info:Path Weight: 128 (TE)Explicit Route: 10.105.0.2 104.105.0.1 10.0.0.4History:Tunnel:Time since created: 7 days, 4 hours, 42 minutesTime since path change: 54 secondsNumber of LSP IDs (Tun_Instances) used: 2SSO recovered <full|partial> (2 subLSP recovered, 0 failed)Current LSP: [ID: 2]Uptime: 54 secondsSelection: SSO recoveredPrior LSP: [ID: 1]Removal Trigger: signalling shutdownThe following sample output from the show mpls traffic-eng tunnels tunnel command for Cisco IOS Release 12.2(33)SRE shows path protection information. This command displays information about a single tunnel.
Router# show mpls traffic-eng tunnels tunnel 1Name: iou-100_t2 (Tunnel2) Destination: 10.10.0.2 Status: Admin: up Oper: up Path: valid Signalling: connected path option 10, type explicit primary1 (Basis for Setup, path weight 10) Path Protection: 0 Common Link(s), 0 Common Node(s) path protect option 10, type list name secondary-list Inuse path-option 10, type explicit secondary1 (Basis for Protect, path weight 20)Config Parameters: Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) AutoRoute announce: enabled LockDown: disabled Loadshare: 0 bw-based auto-bw: disabled Active Path Option Parameters: State: explicit path option 10 is active BandwidthOverride: disabled LockDown: disabled Verbatim: disabledInLabel : - OutLabel : Ethernet7/0, implicit-null RSVP Signalling Info: Src 100.100.100.100, Dst 10.10.0.2, Tun_Id 2, Tun_Instance 188 RSVP Path Info: My Address: 10.1.0.1 Explicit Route: 10.1.0.2 10.10.0.2 Record Route: NONE Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info: Record Route: NONE Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits Shortest Unconstrained Path Info: Path Weight: 10 (TE) Explicit Route: 10.1.0.1 10.1.0.2 10.10.0.2 History:Tunnel:Time since created: 7 days, 4 hours, 42 minutesTime since path change: 54 secondsNumber of LSP IDs (Tun_Instances) used: 2SSO recovered <full|partial> (2 subLSP recovered, 0 failed)Current LSP: [ID: 2]Uptime: 54 secondsSelection: SSO recoveredPrior LSP: [ID: 1]Removal Trigger: signalling shutdownThe following sample output from the show mpls traffic-eng tunnels command for
Cisco IOS Release 12.2(33)SRE shows autoroute destination information:Router# show mpls traffic-eng tunnel tunnel 109Name: PE-7_t109 (Tunnel109) Destination: 10.0.0.9 Status: Admin: up Oper: up Path: valid Signalling: connected path option 1, type explicit to_109 (Basis for Setup, path weight 64) path option 20, type explicit to_109_altConfig Parameters:Bandwidth: 0 kbps (Global Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) Autoroute announce: enabled LockDown: disabled Loadshare: 0 bx-based auto-bw: disabled AutoRoute destination: enabledTable 150 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng tunnels statistics
To display event counters for one or more Multiprotocol Label Switching (MPLS) traffic engineering tunnels, use the show mpls traffic-eng tunnels statistics command in user EXEC and privileged EXEC mode.
show mpls traffic-eng tunnels [tunnel tunnel-name] statistics [summary]
Syntax Description
tunnel tunnel-name
(Optional) Displays event counters accumulated for the specified tunnel.
summary
(Optional) Displays event counters accumulated for all tunnels.
Defaults
If you enter the command without any keywords, the command displays the event counters for every MPLS traffic engineering tunnel interface configured on the router.
Command Modes
User EXEC (>)
Privileged EXEC mode (#)Command History
Usage Guidelines
A label switching router (LSR) maintains counters for each MPLS traffic engineering tunnel headend that counts significant events for the tunnel, such as state transitions for the tunnel, changes to the tunnel path, and various signaling failures. You can use the show mpls traffic-eng tunnels statistics command to display these counters for a single tunnel, for every tunnel, or for all tunnels (accumulated values). Displaying the counters is often useful for troubleshooting tunnel problems.
Examples
The following are examples of output from the show mpls traffic-eng tunnels statistics command:
Router# show mpls traffic-eng tunnels tunnel tunnel1001 statisticsTunnel1001 (Destination 10.8.8.8; Name Router_t1001)Management statistics:Path: 25 no path, 1 path no longer valid, 0 missing ip exp path5 path changesState: 3 transitions, 0 admin down, 1 oper downSignalling statistics:Opens: 2 succeeded, 0 timed out, 0 bad path spec0 other abortsErrors: 0 no b/w, 0 no route, 0 admin0 bad exp route, 0 rec route loop, 0 otherRouter# show mpls traffic-eng tunnels statisticsTunnel1001 (Destination 10.8.8.8; Name Router_t1001)Management statistics:Path: 25 no path, 1 path no longer valid, 0 missing ip exp path5 path changesState: 3 transitions, 0 admin down, 1 oper downSignalling statistics:Opens: 2 succeeded, 0 timed out, 0 bad path spec0 other abortsErrors: 0 no b/w, 0 no route, 0 admin0 bad exp route, 0 rec route loop, 0 other.
.
.Tunnel7050 (Destination 10.8.8.8; Name Router_t7050)Management statistics:Path: 19 no path, 1 path no longer valid, 0 missing ip exp path3 path changesState: 3 transitions, 0 admin down, 1 oper downSignalling statistics:Opens: 2 succeeded, 0 timed out, 0 bad path spec0 other abortsErrors: 0 no b/w, 0 no route, 0 admin0 bad exp route, 0 rec route loop, 0 otherRouter# show mpls traffic-eng tunnels statistics summaryManagement statistics:Path: 2304 no path, 73 path no longer valid, 0 missing ip exp path432 path changesState: 300 transitions, 0 admin down, 100 oper downSignalling statistics:Opens: 200 succeeded, 0 timed out, 0 bad path spec0 other abortsErrors: 0 no b/w, 18 no route, 0 admin0 bad exp route, 0 rec route loop, 0 otherThe following show mpls traffic-eng tunnels statistics command displays status information about P2MP path and LSPs for Tunnel 100:
Router# show mpls traffic-eng tunnels statisticsTunnel100 (Name p2mp-1_t100)Management statistics:Path: 0 no path, 0 path no longer valid, 0 missing ip exp path97 path changes, 306 path lookups0 protection pathoption_list errors0 invalid inuse popt in pathoption list0 loose path reoptimizations, triggered by PathErrorsState: 1 transitions, 0 admin down, 0 oper downSignalling statistics:Opens: 1 succeeded, 0 timed out, 0 bad path spec0 other abortsLSP Activations: 97 succeededLast Failure: No path that satisfy tunnel constraintsFailures stats:5: No path that satisfy tunnel constraintsErrors: 0 no b/w, 288 no route, 0 admin, 0 remerge detected0 bad exp route, 0 rec route loop, 0 frr activated0 otherTable 151 describes the significant fields shown in the display.
Related Commands
clear mpls traffic-eng tunnel counters
Clears the counters for all MPLS traffic engineering tunnels.
show mpls traffic-eng tunnels summary
To display summary information about tunnels, use the show mpls traffic-eng tunnels summary command in user EXEC or privileged EXEC mode.
show mpls traffic-eng tunnels summary
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use the show mpls traffic-eng tunnels summary command to display the number of tunnel headends that were attempted and successful at being recovered following SSO.
Examples
The following is sample output from the show mpls traffic-eng tunnels summary command:
Router# show mpls traffic-eng tunnels summarySignalling Summary:LSP Tunnels Process: runningPassive LSP Listener: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 3600 seconds, next in 1420 secondsPeriodic FRR Promotion: Not RunningPeriodic auto-bw collection: every 300 seconds, next in 234 secondsP2P:Head: 1 interfaces, 1 active signalling attempts, 1 established1 activations, 0 deactivations1 SSO recovery attempts, 1 SSO recoveredMidpoints: 0, Tails: 0P2MP:Head: 1 interfaces, 2 active signalling attempts, 2 established2 sub-LSP activations, 0 sub-LSP deactivations1 LSP successful activations, 0 LSP deactivations1 SSO recovery attempts, LSP Recovered: 1 full, 0 partial, 0 failMidpoints: 0, Tails: 0Table 152 describes the significant fields shown in the display.
Related Commands
show mpls ttfib
To display information about the Multiprotocol Label Switching (MPLS) TTFIB table, use the show mpls ttfib command in EXEC mode.
show mpls ttfib [detail [hardware] | vrf instance [detail]]
Syntax Description
Defaults
This command has no default settings.
Command Modes
EXEC
Command History
Note
Examples
This example shows how to display information about the MPLS TTFIB table:
Router# show mpls ttfibLocal Outgoing Packets Tag LTL Dest. Destination OutgoingTag Tag or VC Switched Index Vlanid Mac Address Interface4116 21 0 0xE0 1020 0000.0400.0000 PO4/1*34 0 0x132 1019 00d0.040d.380a GE5/345 0 0xE3 4031 0000.0430.0000 PO4/44117 16 0 0x132 1019 00d0.040d.380a GE5/3*17 0 0xE0 1020 0000.0400.0000 PO4/118 0 0xE3 4031 0000.0430.0000 PO4/44118 21 0 0xE0 1020 0000.0400.0000 PO4/1*56 0 0xE3 4031 0000.0430.0000 PO4/44119 35 0 0xE3 4031 0000.0430.0000 PO4/4*47 0 0xE0 1020 0000.0400.0000 PO4/1show pw-udp vc
To display information about pseudowire User Datagram Protocol (UDP) virtual circuits (VCs), use the show pw-udp vc command in user EXEC or privileged EXEC mode.
show pw-udp vc [vcid id [max-vc]] [destination address] [detail | ssm id]
Syntax Description
Command Default
If no arguments or keywords are specified, information about all pseudowire UDP VCs is displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output for the show pw-udp vc command:
Router# show pw-udp vc 100 200 detailLocal intf Local circuit VC ID Status----------------- -------------------------- ---------- ---------------CE4/2/0:0 CESoPSN Basic 100 establishedLAddr: 10.1.1.151 LPort: 50100RAddr: 10.1.1.153 RPort: 50100VC statistics:transit packet totals: receive 770614, send 770613transit byte totals: receive 151040344, send 50089845transit packet drops: receive 0, send 0, seq error 0CE4/2/1:0 CESoPSN Basic 200 establishedLAddr: 10.1.1.151 LPort: 50200RAddr: 10.1.1.153 RPort: 50200VC statistics:transit packet totals: receive 770614, send 770613transit byte totals: receive 151040344, send 50089845transit packet drops: receive 0, send 0, seq error 0Table 153 describes the significant fields shown in the display.
Related Commands
encapsulation (pseudowire)
Specifies an encapsulation type for tunneling Layer 2 traffic over a pseudowire.
show running interface auto-template
To display configuration information for a tunnel's interface, use the show running interface auto-template command in privileged EXEC mode.
show running interface auto-template num
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The space before the num argument is optional.
Examples
The following is output from the show running interface auto-template command:
Router# show running interface auto-template 1interface auto-template1ip unnumbered Loopback0no ip directed-broadcastno keepalivetunnel destination access-list 1tunnel mode mpls traffic-engtunnel mpls traffic-eng autoroute announcetunnel mpls traffic-eng path-option 1 dynamicTable 154 describes the significant fields shown in the display.
Related Commands
show running-config vrf
To display the subset of the running configuration of a router that is linked to a specific Virtual Private Network (VPN) routing and forwarding (VRF) instance or to all VRFs configured on the router, use the show running-config vrf command in user EXEC or privileged EXEC mode.
show running-config vrf [vrf-name]
Syntax Description
Command Default
If you do not specify a vrf-name argument, the running configurations of all VRFs on the router are displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use the show running-config vrf command to display a specific VRF configuration or to display all VRF configurations on the router. To display the configuration of a specific VRF, enter the name of the VRF as an argument to the command.
This command displays the following elements of the VRF configuration:
•
•
•
Examples
The following is sample output from the show running-config vrf command. It includes a base VRF configuration for VRF vpn3 and Border Gateway Protocol (BGP) and Open Shortest Path First (OSPF) configurations associated with VRF vpn3.
Router# show running-config vrf vpn3Building configuration...Current configuration : 604 bytesip vrf vpn3rd 100:3route-target export 100:3route-target import 100:3!!interface Loopback1ip vrf forwarding vpn3ip address 10.43.43.43 255.255.255.255!interface Ethernet6/0ip vrf forwarding vpn3ip address 172.17.0.1 255.0.0.0no ip redirectsduplex half!router bgp 100!address-family ipv4 vrf vpn3redistribute connectedredistribute ospf 101 match external 1 external 2no auto-summaryno synchronizationexit-address-family!router ospf 101 vrf vpn3log-adjacency-changesarea 1 sham-link 10.43.43.43 10.23.23.23 cost 10network 172.17.0.0 0.255.255.255 area 1!endTable 155 describes the significant fields shown in the display.
Related Commands
show tech-support mpls
To generate a report of all Multiprotocol Label Switching (MPLS)-related information, use the show tech-support mpls command in privileged EXEC mode.
show tech-support mpls [vrf vrf-name]
Syntax Description
vrf vrf-name
(Optional) Displays MPLS information about the specified VPN routing and forwarding (VRF) instance.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful when you contact technical support personnel with questions regarding MPLS. The show tech-support mpls command generates a series of reports. The show tech-support mpls command is equivalent to issuing the following commands:
MPLS Forwarding Information Commands
show adjacency detail
show cef drop show cef events
show cef not-cef-switched
show cef state
show interface accounting | exclude sab
show interfaces statistic | exclude sabl
show ip cef adjacency discard
show ip cef adjacency drop
show ip cef adjacency glean
show ip cef adjacency null
show ip cef adjacency punt
show ip cef detail internal
show ip cef inconsistency
show ip cef summary
show ip cef unresolved internal
show ip interfaces
show ip route
show ip traffic
show mpls forwarding-table detail
show mpls interfaces all
show mpls interfaces all internal
show mpls label range
show mpls static bindingMPLS Forwarding: Cell Mode (LC-ATM) Commands
Note
show atm vc
show controller vsi descriptor
show controller vsi session
show controller vsi status
show XTagATM cross-connect
show XTagATM cross-connect traffic
show XTagATM vcMPLS Forwarding: Quality of Service (QoS) Commands
Note
show interfaces fair-queue
show interfaces mpls-exp
show interfaces precedenceMPLS Label Distribution Protocol (LDP) Commands
show mpls atm-ldp bindings
show mpls atm-ldp bindwait
show mpls atm-ldp capability
show mpls atm-ldp summary <===== Not supported on Cisco 10000 series routers
show mpls ip binding detail
show mpls ldp backoff
show mpls ldp discovery all detail
show mpls ldp neighbor all
show mpls ldp neighbor detail
show mpls ldp parametersMPLS LDP: Stateful Switchover/Nonstop Forwarding (SSO/NSF) Support and Graceful Restart Commands
show mpls checkpoint label-binding
show mpls ldp checkpoint
show mpls ldp graceful-restart
show mpls ldp neighbor graceful-restartMPLS Traffic Engineering Commands
show ip ospf database opaque-area
show ip ospf database opaque-link
show ip ospf mpls traffic-eng fragment
show ip ospf mpls traffic-eng link
show ip rsvp fast-reroute detail
show ip rsvp installed
show ip rsvp interface
show ip rsvp neighbor
show ip rsvp reservation
show ip rsvp sender
show isis mpls traffic-eng adjacency-log
show isis mpls traffic-eng advertisements
show isis mpls traffic-eng tunnel
show mpls traffic-end link-management interfaces
show mpls traffic-eng autoroute
show mpls traffic-eng fast-reroute database detail
show mpls traffic-eng fast-reroute log reroutes
show mpls traffic-eng forwarding adjacency
show mpls traffic-eng link-management admission-control
show mpls traffic-eng link-management advertisements
show mpls traffic-eng link-management bandwidth-allocation
show mpls traffic-eng link-management summary
show mpls traffic-eng topology
show mpls traffic-eng tunnels
show mpls traffic-eng tunnels brief
show mpls traffic-eng tunnels statics summaryMPLS VPN Commands
show ip bgp labels
show ip bgp neighbors
show ip bgp vpnv4 all
show ip bgp vpnv4 all labels
show ip bgp vpnv4 all summary
show ip vrf detail
show ip vrf interfaces
show ip vrf selectAny Transport over MPLS (AToM) Commands
show mpls l2transport binding
show mpls l2transport hw-capability
show mpls l2transport summary
show mpls l2transport vc detailMPLS VPN VRF-Specific Commands
show ip bgp vpnv4 vpn-name dampening flap-statistics
show ip bgp vpnv4 vpn-name labels
show ip bgp vpnv4 vpn-name peer-group
show ip bgp vpnv4 vpn-name summary
show ip bgp vpnv4 vrf vpn-name neighbors
show ip vrf detail vpn-name
show ip vrf interfaces vpn-name
show ip vrf select vpn-nameMPLS VPN VRF-Specific Forwarding Commands
show ip cef vrf vpn-name adjacency discard
show ip cef vrf vpn-name adjacency drop
show ip cef vrf vpn-name adjacency glean
show ip cef vrf vpn-name adjacency null
show ip cef vrf vpn-name adjacency punt
show ip cef vrf vpn-name inconsistency
show ip cef vrf vpn-name internal
show ip cef vrf vpn-name summary
show ip route vrf vpn-name
show ip vrf interfaces vpn-name
show mpls forwarding-table vrf vpn-name
show mpls interface vrfvpn-name detailMPLS LDP VRF-Specific Commands
show mpls ip binding vrf vpn-name atm detail
show mpls ip binding vrf vpn-name detail
show mpls ip binding vrf vpn-name local
show mpls ip binding vrf vpn-name summary
show mpls ldp discovery vrf vpn-name detail
show mpls ldp neighbor vrf vpn-name detailMPLS LDP VRF Graceful Restart-Specific Commands
show mpls ldp neighbor vrf vpn-name graceful-restart
These commands are documented in individual feature modules or Cisco IOS Release 12.2 command references. Refer to the individual commands for information about the output these commands generate.
Examples
The following example displays an abbreviated version of the show tech-support mpls command output:
Router# show tech-support mpls------------------ show version ------------------Cisco IOS Software, 7300 Software (C7300-P-M), Version 12.2(27)SBC, RELEASE SOF)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2005 by Cisco Systems, Inc.Compiled Sat 10-Sep-05 17:44 by ssearch...------------------ show running-config ------------------Building configuration...Current configuration : 1827 bytes...------------------ show mpls ldp graceful-restart ------------------LDP Graceful Restart is disabledNeighbor Liveness Timer: 120 secondsMax Recovery Time: 120 secondsForwarding State Holding Time: 600 secondsRelated Commands
show vfi
To display information related to a virtual forwarding instance (VFI), use the show vfi command in privileged EXEC mode.
show vfi [checkpoint [summary] | mac static address | memory [detail] | name vfi-name [checkpoint | mac static address] | neighbor ip-addr vcid vcid mac static address]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to verify VFI configurations and for troubleshooting.
Examples
The following example shows status for a VFI named VPLS-2. The VC ID in the output represents the VPN ID; the VC is identified by the combination of the destination address and the VC ID.
Router# show vfi name VPLS-2VFI name: VPLS-2, state: upVPN ID: 100Local attachment circuits:Vlan2Neighbors connected via pseudowires:Peer Address VC ID Split-horizon10.1.1.1 2 Y10.1.1.2 2 Y10.2.2.3 2 NTable 156 describes the significant fields shown in the display.
The following is sample output from the show vfi command. For the Virtual Private LAN Service (VPLS) autodiscovery feature, the command output includes autodiscovery information, as shown in the following example.
Note
Router# show vfiLegend: RT= Route-target, S=Split-horizon, Y=Yes, N=NoVFI name: VPLS1, state: up, type: multipointVPN ID: 10, VPLS-ID: 9:10RD: 9:10, RT: 10.10.10.10:150Local attachment circuits:Ethernet0/0.2Neighbors connected via pseudowires:Peer Address VC ID Discovered Router ID S10.7.7.1 10 10.7.7.1 Y10.7.7.2 10 10.1.1.2 Y10.7.7.3 10 10.1.1.3 Y10.7.7.4 10 10.1.1.4 Y10.7.7.5 10 - YVFI name: VPLS2 state: up, type: multipointVPN ID: 11, VPLS-ID: 10.9.9.9:2345RD: 10:11, RT: 10.4.4.4:151Local attachment circuits:Ethernet0/0.3Neighbors connected via pseudowires:Peer Address VC ID Discovered Router ID S10.7.7.1 11 10.7.7.1 Y10.7.7.2 11 10.1.1.5 YTable 157 describes the significant fields in the output related to VPLS autodiscovery.
The following is sample output from the show vfi command for a specified VFI named H-VPLS-A-VFI. Because the optional name keyword is entered, the checkpoint information for the specific VFI is displayed.
Router# show vfi name H-VPLS-A-VFI checkpointVFI Active RPCheckpointing: AllowedISSU Client id: 2092, Session id: 65543, Compatible with peerVFI VFI AC VFI PWBulk-sync 1 1 3Checkpoint failures: 0 3 21Recovered at switchover: 0 0 0Recovery failures: 0 0 0Legend: C=CheckpointedVFI name: H-VPLS-A-VFI, state: up, type: multipointVPN ID: 12, Internal ID 1 CLocal attachment circuits:Vlan200 16387 / 8195 CNeighbors connected via pseudowires:Peer ID VC ID SSM IDs10.0.0.12 12 4096 / 12292 C10.0.0.15 12 8193 / 16389 C10.0.0.14 12 12290 / 20486 CTable 158 describes the significant fields shown in the display.
The following is sample output from the show vfi command using the memory and detail keywords.
Router# show vfi memory detailVFI memory In-use Asked-For/Allocated Count Size Cfg/Max----------------------------------------------------------------------------VFI structs In-use Asked-For/Allocated Count Size Cfg/Max----------------------------------------------------------------------------vfi_context_t : -- --/-- -- 52 --/--vfi_circuit_retry : -- --/-- -- 24 --/--Total allocated: 0.000 Mb, 0 Kb, 0 bytesTable 159 describes the significant fields shown in the display.
.
Related Commands
show vrf
To display the defined Virtual Private Network (VPN) routing and forwarding (VRF) instances, use the show vrf command in user EXEC or privileged EXEC mode.
show vrf [ipv4 | ipv6] [interface | brief | detail | id | select | lock] [vrf-name]
Syntax Description
Command Default
If you do not specify any arguments or keywords, the command displays concise information about all configured VRFs.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use the show vrf command to display information about specified VRF instances or all VRF instances. Specify no arguments or keywords to display information on all VRF instances.
Examples
The following is the sample output from the show vrf command that displays brief information about all configured VRF instances:
Router# show vrfName Default RD Protocols InterfacesN1 100:0 ipv4,ipv6V1 1:1 ipv4 Lo1V2 2:2 ipv4,ipv6 Et0/1.1Et0/1.2Et0/1.3V3 3:3 ipv4 Lo3Et0/1.4Table 160 describes the significant fields shown in the display.
The following example displays output from the show vrf command with the detail keyword. The information shown is for a VRF named cisco1.
Router# show vrf detailVRF cisco1; default RD 100:1; default VPNID <not set>Interfaces:Ethernet0/0 Loopback10Address family ipv4 (Table ID = 0x1):Connected addresses are not in global routing tableExport VPN route-target communitiesRT:100:1Import VPN route-target communitiesRT:100:1No import route-mapNo export route-mapVRF label distribution protocol: not configuredAddress family ipv6 (Table ID = 0xE000001):Connected addresses are not in global routing tableExport VPN route-target communitiesRT:100:1Import VPN route-target communitiesRT:100:1No import route-mapNo export route-mapVRF label distribution protocol: not configuredTable 161 describes the significant fields shown in the display.
The following example displays output from the show vrf detail command when backup paths have been created either through the Prefix Independent Convergence or Best External feature. The output of the show vrf detail command displays the following line:
Prefix protection with additional path enabled
Router# show vrf detailVRF vpn1 (VRF Id = 1); default RD 1:1; default VPNID <not set>Interfaces:Et1/1Address family ipv4 (Table ID = 1 (0x1)):Export VPN route-target communitiesRT:1:1Import VPN route-target communitiesRT:1:1No import route-mapNo export route-mapVRF label distribution protocol: not configuredVRF label allocation mode: per-prefixPrefix protection with additional path enabledAddress family ipv6 not active.The following is the sample output from the show vrf lock command that displays VPN lock information:
Router# show vrf lockVRF Name: Mgmt-intf; VRF id = 4085 (0xFF5)VRF lock count: 3Lock user: RTMGR, lock user ID: 2, lock count per user: 1Caller PC tracebacks:Trace backs: :10000000+44DAEB4 :10000000+21E83AC :10000000+45A9F04 :108Lock user: CEF, lock user ID: 4, lock count per user: 1Caller PC tracebacks:Trace backs: :10000000+44DAEB4 :10000000+21E83AC :10000000+45A9F04 :10CLock user: VRFMGR, lock user ID: 1, lock count per user: 1Caller PC tracebacks:Trace backs: :10000000+44DAEB4 :10000000+21E83AC :10000000+21EAD18 :10CVRF Name: vpn1; VRF id = 1 (0x1)VRF lock count: 3Lock user: RTMGR, lock user ID: 2, lock count per user: 1Caller PC tracebacks:Trace backs: :10000000+44DAEB4 :10000000+21E83AC :10000000+45A9F04 :10CLock user: CEF, lock user ID: 4, lock count per user: 1Caller PC tracebacks:Trace backs: :10000000+44DAEB4 :10000000+21E83AC :10000000+45A9F04 :100Lock user: VRFMGR, lock user ID: 1, lock count per user: 1Caller PC tracebacks:Trace backs: :10000000+44DAEB4 :10000000+21E83AC :10000000+21EAD18 :10CRelated Commands
vrf definition
Configures a VRF routing table instance and enters VRF configuration mode.
vrf forwarding
Associates a VRF instance with an interface or subinterface.
show xconnect
To display information about xconnect attachment circuits and pseudowires, use the show xconnect command in user EXEC or privileged EXEC mode.
show xconnect {{all | interface type number} [detail] | peer ip-address {all | vcid vcid-value} [detail] | pwmib [peer ip-address vcid-value]}
Cisco IOS SR and S Trains
show xconnect {{all | interface type number | memory | rib} [detail] [checkpoint] | peer ip-address {all | vcid vcid-value} [detail] | pwmib [peer ip-address vcid-value]}
Cisco uBR10012 Router and Cisco uBR7200 Series Universal Broadband Routers
show xconnect {all | peer ip-address {all | vcid vcid-value} | pwmib [peer ip-address vcid-value]} [detail]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show xconnect command can be used to display, sort, and filter basic information about all xconnect attachment circuits and pseudowires.
You can use the show xconnect command output to help determine the appropriate steps required to troubleshoot an xconnect configuration problem. More specific information about a particular type of xconnect can be displayed using the commands listed in the "Related Commands" table.
Examples
The following example shows the show xconnect all command output in the brief (default) display format:
Router# show xconnect allLegend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 StateUP=Up, DN=Down, AD=Admin Down, IA=Inactive, SB=Standby, RV=Recovering, NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UPUP ac Se7/0(PPP) UP mpls 10.55.55.2:2175 UPUP pri ac Se6/0:230(FR DLCI) UP mpls 10.55.55.2:2230 UPIA sec ac Se6/0:230(FR DLCI) UP mpls 10.55.55.3:2231 DNUP ac Se4/0(HDLC) UP mpls 10.55.55.2:4000 UPUP ac Se6/0:500(FR DLCI) UP l2tp 10.55.55.2:5000 UPUP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UPUP pri ac Se6/0:225(FR DLCI) UP mpls 10.55.55.2:5225 UPIA sec ac Se6/0:225(FR DLCI) UP mpls 10.55.55.3:5226 DNIA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UPUP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UPUP ac Se6/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UPThe following example shows the show xconnect all command output in the detailed display format:
Router# show xconnect all detailLegend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 StateUP=Up, DN=Down, AD=Admin Down, IA=Inactive, SB=Standby, RV=Recovering, NH=No HardwareXCST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UPInterworking: ip Local VC label 16Remote VC label 16pw-class: mpls-ipUP ac Se7/0(PPP) UP mpls 10.55.55.2:2175 UPInterworking: ip Local VC label 22Remote VC label 17pw-class: mpls-ipUP pri ac Se6/0:230(FR DLCI) UP mpls 10.55.55.2:2230 UPInterworking: ip Local VC label 21Remote VC label 18pw-class: mpls-ipIA sec ac Se6/0:230(FR DLCI) UP mpls 10.55.55.3:2231 DNInterworking: ip Local VC label unassignedRemote VC label 19pw-class: mpls-ipSB ac Se4/0:100(FR DLCI) UP mpls 10.55.55.2:4000 SBInterworking: none Local VC label 18Remote VC label 19pw-class: mplsUP ac Se6/0:500(FR DLCI) UP l2tp 10.55.55.2:5000 UPInterworking: none Session ID: 34183Tunnel ID: 62083Peer name: pe-iou2Protocol State: UPRemote Circuit State: UPpw-class: l2tpUP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UPInterworking: ip Local VC label 17Remote VC label 20pw-class: mpls-ipUP pri ac Se6/0:225(FR DLCI) UP mpls 10.55.55.2:5225 UPInterworking: none Local VC label 19Remote VC label 21pw-class: mplsIA sec ac Se6/0:225(FR DLCI) UP mpls 10.55.55.3:5226 DNInterworking: none Local VC label unassignedRemote VC label 22pw-class: mplsIA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UPInterworking: none Interworking: noneUP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UPInterworking: none Local VC label 23Remote VC label 17pw-class: mplsUP ac Se6/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UPInterworking: none Interworking: noneSample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Brief Display Format
The following is sample output from the show xconnect command in the brief (default) display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router:
Router# show xconnect allLegend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 StateUP=Up DN=Down AD=Admin Down IA=InactiveSB=Standby RV=Recovering NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Bu254:2001(DOCSIS) UP mpls 10.76.1.1:2001 UPUP ac Bu254:2002(DOCSIS) UP mpls 10.76.1.1:2002 UPUP ac Bu254:2004(DOCSIS) UP mpls 10.76.1.1:2004 UPDN ac Bu254:22(DOCSIS) UP mpls 101.1.0.2:22 DNSample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Brief Display Format in Cisco IOS Release 12.2(33)SCF
The following is sample output from the show xconnect command in the brief (default) display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCF:
Router# show xconnect allLegend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 StateUP=Up DN=Down AD=Admin Down IA=InactiveSB=Standby RV=Recovering NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--DN ac Bu254:55(DOCSIS) DN mpls 10.2.3.4:55 DNUP ac Bu254:1000(DOCSIS) UP mpls 10.2.3.4:1000 UPUP ac Bu254:400(DOCSIS) UP mpls 10.76.2.1:400 UPDN ac Bu254:600(DOCSIS) DN mpls 10.76.2.1:600 DNUP ac Bu254:1800(DOCSIS) UP mpls 10.76.2.1:1800 UPDN ac Bu254:45454(DOCSIS) DN mpls 10.76.2.1:45454 DNSample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Detailed Display Format
The following is sample output from the show xconnect command in the detailed display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router:
Router# show xconnect all detailLegend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 StateUP=Up DN=Down AD=Admin Down IA=InactiveSB=Standby RV=Recovering NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Bu254:2001(DOCSIS) UP mpls 10.76.1.1:2001 UPInterworking: ethernet Local VC label 40Remote VC label 110pw-class:UP ac Bu254:2002(DOCSIS) UP mpls 10.76.1.1:2002 UPInterworking: ethernet Local VC label 41Remote VC label 88pw-class:UP ac Bu254:2004(DOCSIS) UP mpls 10.76.1.1:2004 UPInterworking: ethernet Local VC label 42Remote VC label 111pw-class:DN ac Bu254:22(DOCSIS) UP mpls 101.1.0.2:22 DNInterworking: ethernet Local VC label 39Remote VC label unassignedpw-class:Sample Output for All Xconnect Attachment Circuits and Pseudowires on a Cisco uBR10012 Router in the Detailed Display Format in Cisco IOS Release 12.2(33)SCF
The following is sample output from the show xconnect command in the detailed display format for all xconnect attachment circuits and pseudowires on a Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCF:
Router# show xconnect all detailLegend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 StateUP=Up DN=Down AD=Admin Down IA=InactiveSB=Standby RV=Recovering NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--DN ac Bu254:55(DOCSIS) DN mpls 10.2.3.4:55 DNInterworking: ethernet Local VC label unassignedRemote VC label unassignedpw-class:UP ac Bu254:1000(DOCSIS) UP mpls 10.2.3.4:1000 UPInterworking: ethernet Local VC label 33Remote VC label 36pw-class:UP ac Bu254:400(DOCSIS) UP mpls 10.76.2.1:400 UPInterworking: ethernet Local VC label 35Remote VC label 194pw-class:DN ac Bu254:600(DOCSIS) DN mpls 10.76.2.1:600 DNInterworking: ethernet Local VC label unassignedRemote VC label 120pw-class:UP ac Bu254:1800(DOCSIS) UP mpls 10.76.2.1:1800 UPInterworking: ethernet Local VC label 24Remote VC label 132pw-class:DN ac Bu254:45454(DOCSIS) DN mpls 10.76.2.1:45454 DNInterworking: ethernet Local VC label unassignedRemote VC label 54pw-class:Table 162 describes the significant fields shown in the display.
The additional fields displayed in the detailed output are self-explanatory.
VPLS Autodiscovery Feature Example
For the VPLS Autodiscovery feature, issuing the show xconnect command with the rib keyword provides RIB details, as shown in the following example:
Router# show xconnect ribLocal Router ID: 10.9.9.9Legend: O=Origin, P=Provisioned, TID=Target ID, B=BGP, Y=Yes, N=NoO P VPLS/VPWS-ID TID Next-Hop Route-Target-+-+---------------------+------------+---------------+---------------------B Y 10:123 192.0.2.0 192.0.2.5 10:123B N 10:123 192.0.2.1 192.0.2.6 10:123B Y 10.100.100.100:1234 192.0.2.3 192.0.2.7 10.111.111.111:12345192.0.2.8 10.8.8.8:345192.0.2.9B Y 192.0.3.1:1234 192.0.2.4 10.1.1.1 10.111.111.111:12345Table 163 describes the significant fields shown in the display.
For VPLS Autodiscovery, issuing the show xconnect command with the rib and detail keywords provides more information about the routing information base, as shown in the following example:Router# show xconnect rib detailLocal Router ID: 10.9.9.9VPLS-ID 10:123, TID 10.7.7.7Next-Hop: 10.7.7.7Hello-Source: 10.9.9.9Route-Target: 10:123Incoming RD: 10:10Forwarder: vfi VPLS1Origin: BGPProvisioned: YesVPLS-ID 10:123, TID 10.7.7.8Next-Hop: 10.7.7.8Hello-Source: 10.9.9.9Route-Target: 10:123Incoming RD: 10:11Forwarder: vfi VPLS1Origin: BGPProvisioned: NoVPLS-ID 10.100.100.100:1234, TID 0.0.0.2Next-Hop: 10.2.2.2, 10.3.3.3, 10.4.4.4Hello-Source: 10.9.9.9Route-Target: 10.111.111.111:12345, 10.8.8.8:345Incoming RD: 10:12Forwarder: vfi VPLS2Origin: BGPProvisioned: YesVPLS-ID 10.100.100.100:1234, TID 10.13.1.1Next-Hop: 10.1.1.1Hello-Source: 10.9.9.9Route-Target: 10.111.111.111:12345Incoming RD: 10:13Forwarder: vfi VPLS2Origin: BGPProvisioned: YesTable 164 describes the significant fields shown in the display.
L2VPN VPLS Inter-AS Option B Examples
The following is sample output from the show xconnect rib command when used in an L2VPN VPLS Inter-AS Option B configuration:
Router# show xconnect ribLocal Router ID: 10.9.9.9+- Origin of entry (i=iBGP/e=eBGP)| +- Provisioned (Yes/No)?| | +- Stale entry (Yes/No)?| | |v v vO P S VPLS-ID Target ID Next-Hop Route-Target-+-+-+------+---------------+---------------+---------------+-------------i Y N 1:1 10.11.11.11 10.11.11.11 1:1i Y N 1:1 10.12.12.12 10.12.12.12 1:1Table 165 describes the significant fields shown in the display.
The following is sample output from the show xconnect rib detail command when used in an ASBR configuration. On an ASBR, the show xconnect rib detail command displays the Layer 2 VPN BGP network layer reachability information (NLRI) received from the BGP peers. The display also shows the signaling messages received from the targeted Label Distribution Protocol (LDP) sessions for a given target attachment individual identifier (TAII).
Router# show xconnect rib detailLocal Router ID: 10.1.1.3VPLS-ID: 1:1, Target ID: 10.1.1.1Next-Hop: 10.1.1.1Hello-Source: 10.1.1.3Route-Target: 2:2Incoming RD: 10.0.0.0:1Forwarder:Origin: BGPProvisioned: YesSAII: 10.0.0.1, LDP Peer Id: 10.255.255.255, VC Id: 1001 ***SAII: 10.1.0.1, LDP Peer Id: 10.255.255.255, VC Id: 1002 ***After the passive TPE router receives the BGP information (and before the passive TPE router receives the LDP label), the peer information will be displayed in the output of the show xconnect rib command. The peer information will not be displayed in the show mpls l2transport vc command because the VFI AToM xconnect has not yet been provisioned.
Therefore, for passive TPEs, the entry "Passive : Yes" is added to the output from the show xconnect rib detail command. In addition, the entry "Provisioned: Yes" is displayed after the neighbor xconnect is successfully created (without any retry attempts).
In the sample output, the two lines beginning with "SAII" show that this ASBR is stitching two provider PE routers (10.0.0.1 and 10.1.0.1) to the TAII 10.1.1.1.
Table 166 describes the significant fields shown in the display.
The following is sample output from the show xconnect rib checkpoint command. Autodiscovered pseudowire information is checkpointed to the standby Route Processor (RP). The show xconnect rib checkpoint command displays that pseudowire information.
Router# show xconnect rib checkpointXconnect RIB Active RP:Checkpointing : AllowedCheckpoing epoch: 1ISSU Client id: 2102, Session id: 82, Compatible with peerAdd entries send ok : 0Add entries send fail : 0Delete entries send ok : 0Delete entries send fail: 0+- Checkpointed to standby (Y/N)?| +- Origin of entry (i=iBGP/e=eBGP)| |v vC O VPLS-ID Target ID Next-Hop Route-Target-+-+---------------------+---------------+---------------+----------------N e 1:1 10.1.1.2 10.1.1.2 2:2N e 1:1 10.1.1.1 10.1.1.3 2:2Table 167 describes the significant fields shown in the display.
Related Commands
show xtagatm cos-bandwidth-allocation
Note
To display information about quality of service (QoS) bandwidth allocation on extended Multiprotocol Label Switching (MPLS) ATM (XTagATM) interfaces, use the show xtagatm cos-bandwidth-allocation command in user EXEC or privileged EXEC mode.
show xtagatm cos-bandwidth-allocation [xtagatm interface-number]
Syntax Description
xtagatm
(Optional) Specifies the XTagATM interface number.
interface-number
Number of the XTagATM interface. Range: 0 to 2147483647.
Defaults
Available 50 percent, control 50 percent.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use this command to display QoS bandwidth allocation information for the following QoS traffic categories:
•
•
•
•
Examples
The following example shows output from this command:
Router# show xtagatm cos-bandwidth-allocation xtagatm 123CoS Bandwidth allocationavailable 25%standard 25%premium 25%control 25%Table 168 describes the significant fields shown in the display.
show xtagatm cross-connect
Note
To display information about the Label Switch Controller (LSC) view of the cross-connect table on the remotely controlled ATM switch, use the show xtagatm cross-connect command in user EXEC or privileged EXEC mode.
show xtagatm cross-connect [traffic] [interface interface [vpi vci] | descriptor descriptor
[vpi vci]]Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
Each connection is listed twice in the output from the show xtagatm cross-connect command, because it shows each interface that is linked by the connection.
The following is sample output from the show xtagatm cross-connect command:
Router# show xtagatm cross-connectPhys Desc VPI/VCI Type X-Phys Desc X-VPI/VCI State10.1.0 1/37 -> 10.3.0 1/35 UP 10.1.0 1/34 -> 10.3.0 1/33 UP 10.1.0 1/33 <-> 10.2.0 0/32 UP 10.1.0 1/32 <-> 10.3.0 0/32 UP 10.1.0 1/35 <- 10.3.0 1/34 UP 10.2.0 1/57 -> 10.3.0 1/49 UP 10.2.0 1/53 -> 10.3.0 1/47 UP 10.2.0 1/48 <- 10.1.0 1/50 UP 10.2.0 0/32 <-> 10.1.0 1/33 UP 10.3.0 1/34 -> 10.1.0 1/35 UP 10.3.0 1/49 <- 10.2.0 1/57 UP 10.3.0 1/47 <- 10.2.0 1/53 UP 10.3.0 1/37 <- 10.1.0 1/38 UP 10.3.0 1/35 <- 10.1.0 1/37 UP 10.3.0 1/33 <- 10.1.0 1/34 UP 10.3.0 0/32 <-> 10.1.0 1/32 UPTable 169 describes the significant fields shown in the display.
The following is sample output from the show xtagatm cross-connect command for a single endpoint:
Router# show xtagatm cross-connect descriptor 10.1.0 1 42Phys desc: 10.1.0Interface: n/aIntf type: switch control portVPI/VCI: 1/42X-Phys desc: 10.2.0X-Interface: XTagATM0X-Intf type: extended tag ATMX-VPI/VCI: 2/38Conn-state: UPConn-type: input/outputCast-type: point-to-pointRx service type: Tag COS 0Rx cell rate: n/aRx peak cell rate: 10000Tx service type: Tag COS 0Tx cell rate: n/aTx peak cell rate: 10000Table 170 describes the significant fields shown in the display.
show xtagatm vc
Note
To display information about terminating virtual circuits (VCs) on extended Multiprotocol Label Switching (MPLS) ATM (XTagATM) interfaces, use the show xtagatm vc command in user EXEC or privileged EXEC mode.
show xtagatm vc [vcd [interface]]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The columns marked VCD, VPI, and VCI display information for the corresponding private VC on the control interface. The private VC connects the XTagATM VC to the external switch. It is termed private because its VPI and VCI are only used for communication between the MPLS LSC and the switch, and it is different from the VPI and VCI seen on the XTagATM interface and the corresponding switch port.
Examples
Each connection is listed twice in the sample output from the show xtagatm vc command under each interface that is linked by the connection. Connections are marked as input (unidirectional traffic flow, into the interface), output (unidirectional traffic flow, away from the interface), or in/out (bidirectional).
The following is sample output from the show xtagatm vc command:
Router# show xtagatm vcAAL / Control Interface Interface VCD VPI VCI Type Encapsulation VCD VPI VCI StatusXTagATM0 1 0 32 PVC AAL5-SNAP 2 0 33 ACTIVEXTagATM0 2 1 33 TVC AAL5-MUX 4 0 37 ACTIVEXTagATM0 3 1 34 TVC AAL5-MUX 6 0 39 ACTIVETable 171 describes the significant fields shown in the display.
Related Commands
show atm vc
Displays information about private ATM VCs.
show xtagatm cross-connect
Displays information about remotely connected ATM switches.
snmp mib mpls vpn
To configure Simple Network Management Protocol (SNMP) controls for Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) notification thresholds, use the snmp mib mpls vpn command in global configuration mode. To disable SNMP controls for MPLS VPN thresholds, use the no form of this command.
snmp mib mpls vpn {illegal-label number | max-threshold seconds}
no snmp mib mpls vpn {illegal-label | max-threshold}
Syntax Description
Command Default
SNMP controls are not configured for MPLS VPN routing and forwarding (VRF) tables.
Command Modes
Global configuration (config)
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
Use this command to configure the number of illegal labels allowed for routes in the MPLS VRF before SNMP sends an illegal label threshold notification, or to configure the time elapsed before SNMP resends a maximum threshold notification.
Use the snmp mib mpls vpn illegal-label command to indicate how many illegal MPLS VPN labels you want to allow before you receive a notification. Once this number is exceeded, SNMP sends an illegal-label notification to a network management system (NMS), if you have one configured; otherwise, the router issues a syslog error message. If you do not configure this command, SNMP sends an illegal label notification on the first occurrence of an illegal label.
Use the snmp mib mpls vpn max-threshold command if you want to receive maximum threshold notifications periodically when attempts are made to add routes to the VRF after the maximum threshold is exceeded. If you do not configure this command, SNMP sends a single maximum threshold notification at the time that the maximum threshold is exceeded. Notifications are sent to an NMS if you configured one; otherwise, the router issues a syslog error message. Another notification is not sent until the number of routes goes below the maximum threshold and then exceeds the threshold again.
Examples
The following example shows how to configure an illegal label threshold of 50 labels:
configure terminal!smnp mib mpls vpn illegal-label 50The following example shows how to configure the time interval of 600 seconds for resending maximum threshold notifications:
configure terminal!smnp mib mpls vpn max-threshold 600Related Commands
snmp-server community
To set up the community access string to permit access to the Simple Network Management Protocol (SNMP), use the snmp-server community command in global configuration mode. To remove the specified community string, use the no form of this command.
snmp-server community string [view view-name] [ro | rw] [ipv6 nacl] [access-list-number | extended-access-list-number | access-list-name]
no snmp-server community string
Syntax Description
Command Default
An SNMP community string permits read-only access to all objects.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The no snmp-server command disables all versions of SNMP (SNMPv1, SNMPv2C, SNMPv3).
The first snmp-server command that you enter enables all versions of SNMP.
To configure SNMP community strings for the MPLS LDP MIB, use the snmp-server community command on the host network management station (NMS).
Note
The snmp-server community command can be used to specify only an IPv6 named access list, only an IPv4 access list, or both. For you to configure both IPv4 and IPv6 access lists, the IPv6 access list must appear first in the command statement.
Note
Examples
The following example shows how to set the read/write community string to newstring:
Router(config)# snmp-server community newstring rwThe following example shows how to allow read-only access for all objects to members of the standard named access list lmnop that specify the comaccess community string. No other SNMP managers have access to any objects.
Router(config)# snmp-server community comaccess ro lmnopThe following example shows how to assign the string comaccess to SNMP, allow read-only access, and specify that IP access list 4 can use the community string:
Router(config)# snmp-server community comaccess ro 4The following example shows how to assign the string manager to SNMP and allow read-write access to the objects in the restricted view:
Router(config)# snmp-server community manager view restricted rwThe following example shows how to remove the community comaccess:
Router(config)# no snmp-server community comaccessThe following example shows how to disable all versions of SNMP:
Router(config)# no snmp-serverThe following example shows how to configure an IPv6 access list named list1 and links an SNMP community string with this access list:
Router(config)# ipv6 access-list list1Router(config-ipv6-acl)# permit ipv6 any anyRouter(config-ipv6-acl)# exitRouter(config)# snmp-server community comaccess rw ipv6 list1Related Commands
snmp-server enable traps (MPLS)
To enable a label switch router (LSR) to send Simple Network Management Protocol (SNMP) notifications or informs to an SNMP host, use the snmp-server enable traps command in global configuration mode. To disable notifications or informs, use the no form of this command.
snmp-server enable traps [notification-type] [notification-option]
no snmp-server enable traps [notification-type] [notification-option]
Syntax Description
Defaults
If you issue this command on an LSR without specifying any notification-type keywords, the default behavior of the LSR is to enable all notification types controlled by the command (some notification types cannot be controlled by means of this command).
Command Modes
Global configuration
Command History
Usage Guidelines
To configure an LSR to send SNMP LDP notifications, you must issue at least one snmp-server enable traps command on the router.
To configure an LSR to send either notifications (traps) or informs to a designated network management station (NMS), you must issue the snmp-server host command on that device, using the keyword (traps or informs) that suits your purposes.
If you issue the snmp-server enable traps command without keywords, all SNMP notification types are enabled on the LSR. If you issue this command with specific keywords, only the notification types associated with those particular keywords are enabled on the LSR.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. You use the latter command to specify the NMS host (or hosts) targeted as the recipient(s) of the SNMP notifications generated by SNMP-enabled LSRs in the network. To enable an LSR to send such notifications, you must issue at least one snmp-server host command on the LSR.
Examples
In the following example, the router is enabled to send all notifications to the host specified as myhost.cisco.com. The community string is defined as public.
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com publicIn the following example, the router is enabled to send Frame Relay and environmental monitor notifications to the host specified as myhost.cisco.com. The community string is defined as public:
Router(config)# snmp-server enable traps frame-relayRouter(config)# snmp-server enable traps envmon temperatureRouter(config)# snmp-server host myhost.cisco.com publicIn the following example, notifications are not sent to any host. BGP notifications are enabled for all hosts, but the only notifications enabled to be sent to a host are ISDN notifications (which are not enabled in this example).
Router(config)# snmp-server enable traps bgpRouter(config)# snmp-server host host1 public isdnIn the following example, the router is enabled to send all inform requests to the host specified as myhost.cisco.com. The community string is defined as public.
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicIn the following example, HSRP MIB notifications are sent to the host specified as myhost.cisco.com. The community string is defined as public.
Router(config)# snmp-server enable hsrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c public hsrpRelated Commands
snmp-server host
Specifies the intended recipient of an SNMP notification (that is, the designated NMS workstation in the network).
snmp-server enable traps mpls ldp
To enable the sending of Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps mpls ldp command in global configuration mode. To disable the sending of MPLS LDP notifications, use the no form of this command.
snmp-server enable traps mpls ldp [pv-limit] [session-down] [session-up] [threshold]
no snmp-server enable traps mpls ldp [pv-limit] [session-down] [session-up] [threshold]
Syntax Description
Command Default
The sending of SNMP notifications is disabled. If you do not specify an optional keyword, all four types of LDP notifications are enabled on the label switching router (LSR).
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The MPLS LDP pv-limit (mplsLdpPathVectorLimitMismatch) notification provides a warning message that can be sent to the network management station (NMS) when two routers engaged in LDP operations have a dissimilar path-vector limits.
The value of the path-vector limit can range from 0 to 255; a value of 0 indicates that loop detection is off. Any value other than 0 up to 255 indicates that loop detection is on and specifies the maximum number of hops through which an LDP message can pass before a loop condition in the network is sensed.
The MPLS LDP threshold (mplsLdpFailedInitSessionThresholdExceeded) notification object provides a warning message that can be sent to an NMS when a local LSR and an adjacent LDP peer attempt to set up an LDP session between them, but fail to do so after a specified number of attempts. The default number of attempts is 8. This default value is implemented in Cisco IOS software and cannot be changed using either the command line interface (CLI) or an SNMP agent.
In general, Cisco routers support the same features across multiple platforms. Therefore, the most likely incompatibility to occur between Cisco LSRs is a mismatch of their respective ATM VPI/VCI label ranges. For example, if you specify a range of valid labels for an LSR that does not overlap the range of its adjacent LDP peer, the routers will try eight times to create an LDP session between themselves before the mplsLdpFailedInitSessionThresholdExceeded notification is generated.
The LSRs whose label ranges do not overlap continue their attempt to create an LDP session between themselves after the eight retry threshold is exceeded. In such cases, the LDP threshold exceeded notification alerts the network administrator to the existence of a condition in the network that may warrant attention.
RFC 3036, LDP Specification, details the incompatibilities that can exist between Cisco routers or other vendor LSRs in an MPLS network. Among these incompatibilities, for example, are the following:
•
•
•
•
The snmp-server enable traps mpls ldp command is used with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
If the pv-limit keyword is used, a message is generated when the router establishes an LDP session with its adjacent peer LSR, but the two LSRs have dissimilar path-vector limits.
If the session-down keyword is used, a session-down message is generated when an LDP session between the router and its adjacent LDP peer is terminated.
If the session-up keyword is used, a message is generated when the router establishes an LDP session with another LDP entity (an adjacent LDP peer in the network).
If the threshold keyword is used, a message is generated after eight failed attempts to establish an LDP session between the router and an LDP peer. The failures can be caused by any type of incompatibility between the devices.
All four keywords can be used in the same command in any combination.
Note
Examples
In the following example, LDP-specific informs are enabled and will be sent to the host myhost.cisco.com through use of community string defined as public:
Router(config)# snmp-server enable traps mpls ldpRouter(config)# snmp-server host myhost.cisco.com informs version 2c public mpls-ldpRelated Commands
snmp-server enable traps mpls rfc ldp
To enable the sending of Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) Simple Network Management Protocol (SNMP) notifications defined in RFC 3815, use the snmp-server enable traps mpls rfc ldp command in global configuration mode. To disable the sending of MPLS LDP notifications, use the no form of this command.
snmp-server enable traps mpls rfc ldp [pv-limit | session-down | session-up | threshold]
no snmp-server enable traps mpls rfc ldp [pv-limit | session-down | session-up | threshold]
Syntax Description
Command Default
The sending of SNMP notifications is disabled by default.
If you do not specify an optional keyword, all four types of MPLS RFC LDP notifications are enabled on the label switch router (LSR).Command Modes
Global configuration (config)
Command History
12.2(33)SRB
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
Use this command to enable the LDP notifications supported in Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), RFC 3815.
The MPLS LDP pv-limit (mplsLdpPathVectorLimitMismatch) notification provides a warning message that can be sent to the network management station (NMS) when two routers engaged in LDP operations have a dissimilar path vector limits. We recommend that all LDP-enabled routers in the network be configured with the same path vector limits.
The value of the path vector limit can range from 0 to 255; a value of 0 indicates that loop detection is off; any value other than 0 up to 255 indicates that loop detection is on and, in addition, specifies the maximum number of hops through which an LDP message can pass before a loop condition in the network is sensed.
The MPLS LDP threshold (mplsLdpFailedInitSessionThresholdExceeded) notification object provides a warning message that can be sent to an NMS when a local LSR and an adjacent LDP peer attempt to set up an LDP session between them, but fail to do so after a specified number of attempts. The default number of attempts is eight. This default value is implemented in Cisco IOS software and cannot be changed using either the command-line interface (CLI) or an SNMP agent.
In general, Cisco routers support the same features across multiple platforms. Therefore, the most likely incompatibility to occur between Cisco LSRs is a mismatch of their respective ATM Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) label ranges.
For example, if you specify a range of valid labels for an LSR that does not overlap the range of its adjacent LDP peer, the routers will try eight times to create an LDP session between themselves before the mplsLdpFailedInitSessionThresholdExceeded notification is generated.
The LSRs whose label ranges do not overlap continue their attempt to create an LDP session between themselves after the eight retry threshold is exceeded. In such cases, the LDP threshold exceeded notification alerts the network administrator to the existence of a condition in the network that may warrant attention.
RFC 3036, LDP Specification, details the incompatibilities that can exist between Cisco routers or between Cisco routers and other vendor LSRs in an MPLS network. Among these incompatibilities, for example, are the following:
•
•
•
•
The snmp-server enable traps mpls rfc ldp command is used with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
If the pv-limit keyword is used, a message is generated when the router establishes an LDP session with its adjacent peer LSR, but the two LSRs have dissimilar path vector limits.
If the session-down keyword is used, a session-down message is generated when an LDP session between the router and its adjacent LDP peer is terminated.
If the session-up keyword is used, a message is generated when the router establishes an LDP session with another LDP entity (an adjacent LDP peer in the network).
If the threshold keyword is used, a message is generated after eight failed attempts to establish an LDP session between the router and an LDP peer. The failures can be caused by any type of incompatibility between the devices.
Examples
In the following example, LDP-specific informs are enabled and will be sent to the host myhost.cisco.com through use of community string defined as public:
Router(config)# snmp-server enable traps mpls rfc ldpRouter(config)# snmp-server host myhost.cisco.com informs version 2c public mpls-ldpRelated Commands
snmp-server enable traps mpls rfc vpn
To enable the sending of Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) Simple Network Management Protocol (SNMP) notifications defined in RFC 4382, use the snmp-server enable traps mpls rfc vpn command in global configuration mode. To disable the sending of MPLS VPN notifications, use the no form of this command
snmp-server enable traps mpls rfc vpn [illegal-label] [max-thresh-cleared] [max-threshold] [mid threshold] [vrf-down] [vrf-up]
no snmp-server enable traps mpls rfc vpn [illegal-label] [max-thresh-cleared] [max-threshold] [mid threshold] [vrf-down] [vrf-up]
Syntax Description
Command Default
The sending of SNMP notifications is disabled by default.
Command Modes
Global configuration (config)
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
If this command is used without any of the optional keywords, all MPLS RFC VPN notification types are enabled.
The illegal-label keyword enables a notification for illegal labels received on a VRF interface. Labels are illegal if they are outside the legal range, do not have a Label Forwarding Information Base (LFIB) entry, or do not match table IDs for the label.
When the max-thresh-cleared keyword is used and you attempt to create a route on a VRF that already contains the maximum number of routes, the mplsL3VpnVrfNumVrfRouteMaxThreshExceeded notification is sent (if enabled). When you remove routes from the VRF so that the number of routes falls below the set limit, the mplsL3VpnNumVrfRouteMaxThreshCleared notification is sent. You can clear all routes from the VRF by using the clear ip route vrf command.
The max-threshold keyword enables a notification that a route creation attempt was unsuccessful because the maximum route limit was reached. Another notification is not sent until the number of routes falls below the maximum threshold and reaches the maximum threshold again. The max-threshold value is determined by the maximum routes command in VRF configuration mode. If both IPv4 and IPv6 address-family configurations are present in the VRF, the threshold is an aggregate of the maximum threshold values. An mplsL3VpnVrfNumVrfRouteMaxThreshExceeded notification is not sent until the second address family reaches its maximum route threshold. Routes are not added to the address family that has already reached its maximum route threshold.
Note
The warning that the mid-threshold keyword enables is sent only at the time the warning threshold is exceeded. If both IPv4 and IPv6 address-family configurations are present in the VRF, the threshold is an aggregate of the middle or warning threshold values. An mplsL3VpnVrfRouteMidThreshExceeded notification is not sent until the second address family reaches its warning threshold.
The values for the mid-threshold and max-threshold keywords are set using the maximum routes limit {warn-threshold | warning-only} VRF command in configuration mode.
The maximum routes command gives you two options in the VRF address family configuration mode:
•
If you use the maximum routes limit warning-only command with the snmp-server enable traps mpls rfc vpn command, a mid-threshold SNMP notification is generated when the limit value is reached or exceeded. No max-threshold SNMP notification is generated.
•
If you use the maximum routes limit warn-threshold command with the snmp-server enable traps mpls rfc vpn command, a mid-threshold SNMP notification is generated when the warn-threshold value is reached. A max-threshold notification is generated when the limit value is reached.
Note
The notification types described are defined in the following MIB objects of the MPLS-L3-VPN-STD-MIB:
•
•
•
•
•
•
Examples
In the following example, MPLS RFC VPN trap notifications are sent to the host specified as 172.31.156.34 using the community string named public if a VRF transitions from an up or down state:
Router(config)# snmp-server host 172.31.156.34 traps public mpls-vpnRouter(config)# snmp-server enable traps mpls rfc vpn vrf-down vrf-upRelated Commands
snmp-server enable traps mpls traffic-eng
To enable Multiprotocol Label Switching (MPLS) traffic engineering tunnel state-change Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps mpls traffic-eng command in global configuration mode. To disable MPLS traffic engineering tunnel state-change SNMP notifications, use the no form of this command.
snmp-server enable traps mpls traffic-eng [up | down | reroute]
no snmp-server enable traps mpls traffic-eng [up | down | reroute]
Syntax Description
Command Default
SNMP notifications are disabled.
When this command is used without keywords, all available trap types (up, down, reroute) are enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command enables or disables MPLS traffic engineering tunnel notifications. MPLS tunnel state-change notifications, when enabled, will be sent when the connection moves from an "up" to "down" state, when a connection moves from a "down" to "up" state, or when a connection is rerouted. If you do not specify a keyword in conjunction with this command, all three types of MPLS traffic engineering tunnel notifications are sent.
When the up keyword is used, mplsTunnelUp notifications are sent to a network management system (NMS) when an MPLS traffic engineering tunnel is configured and the tunnel transitions from an operationally "down" state to an "up" state.
When the down keyword is used, mplsTunnelDown notifications are generated and sent to the NMS when an MPLS traffic engineering tunnel transitions from an operationally "up" state to a "down" state.
When the reroute keyword is used, mplsTunnelRerouted notifications are sent to the NMS under the following conditions:
•
•
–
–
–
The mplsTunnelReoptimized notification is not generated when an MPLS traffic engineering tunnel is reoptimized. However, an mplsTunnelReroute notification is generated. Thus, at the NMS, you cannot distinguish between a tunnel reoptimization and a tunnel reroute event.
The snmp-server enable traps mpls traffic-eng command is used with the snmp-server host command. Use the snmp-server host command to specify which hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example shows how to enable the router to send MPLS notifications to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps mpls traffic-engRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server host
Specifies the recipient of an SNMP notification operation.
snmp-server trap-source
Specifies the interface that an SNMP trap should originate from.
snmp-server enable traps mpls vpn
To enable the router to send Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN)-specific Simple Network Management Protocol (SNMP) notifications (traps and informs), use the snmp-server enable traps mpls vpn command in global configuration mode. To disable MPLS VPN specific SNMP notifications, use the no form of this command.
snmp-server enable traps mpls vpn [illegal-label] [max-thresh-cleared] [max-threshold] [mid-threshold] [vrf-down] [vrf-up]
no snmp-server enable traps mpls vpn [illegal-label] [max-thresh-cleared] [max-threshold] [mid-threshold] [vrf-down] [vrf-up]
Syntax Description
Command Default
This command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
If this command is used without any of the optional keywords, all MPLS VPN notification types are enabled.
The illegal-label keyword enables a notification for illegal labels received on a VRF interface. Labels are illegal if they are outside the legal range, do not have a Label Forwarding Information Base (LFIB) entry, or do not match table IDs for the label.
When the max-thresh-cleared keyword is used and you attempt to create a route on a VRF that already contains the maximum number of routes, the mplsNumVrfRouteMaxThreshExceeded notification is sent (if enabled). When you remove routes from the VRF so that the number of routes falls below the set limit, the cMplsNumVrfRouteMaxThreshCleared notification is sent. You can clear all routes from the VRF by using the clear ip route vrf command.
The max-threshold keyword enables a notification that a route creation attempt was unsuccessful because the maximum route limit was reached. Another notification is not sent until the number of routes falls below the maximum threshold and reaches the maximum threshold again. The max-threshold value is determined by the maximum routes command in VRF configuration mode.
The warning that the mid-threshold keyword enables is sent only at the time the warning threshold is exceeded.
For the vrf-up (mplsVrfIfUp) or vrf-down (mplsVrfIfDown) notifications to be issued from an ATM or Frame Relay subinterface, you must first configure the snmp-server traps atm subif command or the snmp-server traps frame-relay subif command on the subinterfaces, respectively.
The values for the mid-threshold and max-threshold keywords are set using the maximum routes limit {warn-threshold | warning-only} VRF command in configuration mode.
The maximum routes command gives you two options:
•
If you use the maximum routes limit warning-only command with the snmp-server enable traps mpls vpn command, a mid-threshold SNMP notification is generated when the limit value is reached or exceeded. No max-threshold SNMP notification is generated.
•
If you use the maximum routes limit warn-threshold command with the snmp-server enable traps mpls vpn command, a mid-threshold SNMP notification is generated when the warn-threshold value is reached. A max-threshold notification is generated when the limit value is reached.
The notification types described are defined in the following MIB objects of the PPVPN-MPLS-VPN-MIB:
•
•
•
•
•
The cMplsNumVrfRouteMaxThreshCleared notification type is defined in the CISCO-IETF-PPVPN-MPLS-VPN-MIB.
Examples
In the following example, MPLS VPN trap notifications are sent to the host specified as 172.31.156.34 using the community string named public if a VRF transitions from an up or down state:
Router(config)# snmp-server host 172.31.156.34 traps public mpls-vpnRouter(config)# snmp-server enable traps mpls vpn vrf-down vrf-upRelated Commands
snmp-server group
To configure a new Simple Network Management Protocol (SNMP) group, use the snmp-server group command in global configuration mode. To remove a specified SNMP group, use the no form of this command.
snmp-server group group-name {v1 | v2c | v3 {auth | noauth | priv}} [context context-name] [read read-view] [write write-view] [notify notify-view] [access [ipv6 named-access-list] [acl-number | acl-name]]
no snmp-server group group-name {v1 | v2c | v3 {auth | noauth | priv}} [context context-name]
Syntax Description
Command Default
No SNMP server groups are configured.
Command Modes
Global configuration
Command History
Usage Guidelines
When a community string is configured internally, two groups with the name public are autogenerated, one for the v1 security model and the other for the v2c security model. Similarly, deleting a community string will delete a v1 group with the name public and a v2c group with the name public.
No default values exist for authentication or privacy algorithms when you configure the snmp-server group command. Also, no default passwords exist. For information about specifying a Message Digest 5 (MD5) password, see the documentation of the snmp-server user command.
Configuring Notify Views
The notify-view option is available for two reasons:
•
•
Specifying a notify view when configuring an SNMP group is not recommended, for the following reasons:
•
•
Instead of specifying the notify view for a group as part of the snmp-server group command, use the following commands in the order specified:
1.
2.
3.
SNMP Contexts
SNMP contexts provide VPN users with a secure way of accessing MIB data. When a VPN is associated with a context, that VPN's specific MIB data exists in that context. Associating a VPN with a context enables service providers to manage networks with multiple VPNs. Creating and associating a context with a VPN enables a provider to prevent the users of one VPN from accessing information about users of other VPNs on the same networking device.
Use this command with the context context-name keyword and argument to associate a read, write, or notify SNMP view with an SNMP context.
Examples
Create an SNMP Group
The following example shows how to create the SNMP server group "public," allowing read-only access for all objects to members of the standard named access list "lmnop":
Router(config)# snmp-server group public v2c access lmnopRemove an SNMP Server Group
The following example shows how to remove the SNMP server group "public" from the configuration:
Router(config)# no snmp-server group public v2cAssociate an SNMP Server Group with Specified Views
The following example shows SNMP context "A" associated with the views in SNMPv2c group "GROUP1":
Router(config)# snmp-server context ARouter(config)# snmp mib community commARouter(config)# snmp mib community-map commA context A target-list commAVpnRouter(config)# snmp-server group GROUP1 v2c context A read viewA write viewA notify viewBRelated Commands
snmp-server host
To specify the recipient of a Simple Network Management Protocol (SNMP) notification operation, use the snmp-server host command in global configuration mode. To remove the specified host from the configuration, use the no form of this command.
snmp-server host {hostname | ip-address} [vrf vrf-name] [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port port] [notification-type]
no snmp-server host {hostname | ip-address} [vrf vrf-name] [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port port] [notification-type]
Syntax Description
Command Default
This command is disabled by default. A recipient is not specified to receive notifications.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
If you enter this command with no optional keywords, the default is to send all notification-type traps to the host. No informs will be sent to the host.
The no snmp-server host command with no keywords disables traps, but not informs, to the host. To disable informs, use the no snmp-server host informs command.
Note
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response protocol data unit (PDU). If the sender never receives the response, the inform request can be sent again. Thus, informs are more likely than traps to reach their intended destination.
Compared to traps, informs consume more resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Also, traps are sent only once; an inform may be tried several times. The retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. To configure the router to send SNMP notifications, you must enter at least one snmp-server host command. If you enter the command with no optional keywords, all trap types are enabled for the host.
To enable multiple hosts, you must issue a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap or inform), each succeeding command overwrites the previous command. Only the last snmp-server host command will be in effect. For example, if you enter an snmp-server host inform command for a host and then enter another snmp-server host inform command for the same host, the second command will replace the first.
The snmp-server host command is used in conjunction with the snmp-server enable command. Use the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to receive most notifications, at least one snmp-server enable command and the snmp-server host command for that host must be enabled.
Some notification types cannot be controlled with the snmp-server enable command. Some notification types are always enabled, and others are enabled by a different command. For example, the linkUpDown notifications are controlled by the snmp trap link-status command. These notification types do not require an snmp-server enable command.
The availability of a notification-type options depends on the router type and the Cisco IOS software features supported on the router. For example, the envmon notification type is available only if the environmental monitor is part of the system. To see what notification types are available on your system, use the command help ? at the end of the snmp-server host command.
The vrf keyword allows you to specify the notifications being sent to a specified IP address over a specific VRF. The VRF defines a VPN membership of a user so data is stored using the VPN.
In the case of the NMS sending the query having a correct SNMP community but that does not have a read or a write view, the SNMP agent returns the following error values:
•
•
Notification-Type Keywords
The notification-type keywords used in the snmp-server host command do not always match the keywords used in the corresponding snmp-server enable traps command. For example, the notification keyword applicable to Multiprotocol Label Switching Protocol (MPLS) traffic engineering tunnels is specified as mpls-traffic-eng (containing two hyphens and no embedded spaces). The corresponding parameter in the snmp-server enable traps command is specified as mpls traffic-eng (containing an embedded space and a hyphen).
This syntax difference is necessary to ensure that the command-line interface (CLI) interprets the notification-type keyword of the snmp-server host command as a unified, single-word construct, which preserves the capability of the snmp-server host command to accept multiple notification-type keywords in the command line. The snmp-server enable traps commands, however, often use two-word constructs to provide hierarchical configuration options and to maintain consistency with the command syntax of related commands. Table 172 maps some examples of snmp-server enable traps commands to the keywords used in the snmp-server host command.
Table 172 SNMP-server enable traps Commands and Corresponding Notification Keywords
snmp-server enable traps l2tun session
l2tun-session
snmp-server enable traps mpls ldp
mpls-ldp
snmp-server enable traps mpls traffic-eng1
mpls-traffic-eng
snmp-server enable traps mpls vpn
mpls-vpn
1 See the Cisco IOS Multiprotocol Label Switching Command Reference for documentation of this command.
Examples
If you want to configure a unique SNMP community string for traps but prevent SNMP polling access with this string, the configuration should include an access list. The following example shows how to name a community string comaccess and number an access list 10:
Router(config)# snmp-server community comaccess ro 10Router(config)# snmp-server host 192.20.2.160 comaccessRouter(config)# access-list 10 deny any
Note
The following example shows how to send RFC 1157 SNMP traps to a specified host named myhost.cisco.com. Other traps are enabled, but only SNMP traps are sent because only snmp is specified in the snmp-server host command. The community string is defined as comaccess.
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com comaccess snmpThe following example shows how to send the SNMP and Cisco environmental monitor enterprise-specific traps to address 192.30.2.160 using the community string public:
Router(config)# snmp-server enable traps snmpRouter(config)# snmp-server enable traps envmonRouter(config)# snmp-server host 192.30.2.160 public snmp envmonThe following example shows how to enable the router to send all traps to the host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but only the ISDN traps are enabled to be sent to a host. The community string is defined as public.
Router(config)# snmp-server enable traps bgpRouter(config)# snmp-server host myhost.cisco.com public isdnThe following example shows how to enable the router to send all inform requests to the host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicThe following example shows how to send HSRP MIB informs to the host specified by the name myhost.cisco.com. The community string is defined as public.
Router(config)# snmp-server enable traps hsrpRouter(config)# snmp-server host myhost.cisco.com informs version 2c public hsrpThe following example shows how to send all SNMP notifications to example.com over the VRF named trap-vrf using the community string public:
Router(config)# snmp-server host example.com vrf trap-vrf publicThe following example shows how to configure an IPv6 SNMP notification server with the IPv6 address 2001:0DB8:0000:ABCD:1 using the community string public:
Router(config)# snmp-server host 2001:0DB8:0000:ABCD:1 version 2c public udp-port 2012The following example shows how to specify VRRP as the protocol using the community string public:
Router(config)# snmp-server enable traps vrrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c public vrrpThe following example shows how to send all Cisco Express Forwarding informs to the notification receiver with the IP address 192.40.3.130 using the community string public:
Router(config)# snmp-server enable traps cefRouter(config)# snmp-server host 192.40.3.130 informs version 2c public cefThe following example shows how to enable all NHRP traps, and how to send all NHRP traps to the notification receiver with the IP address 192.40.3.130 using the community string public:
Router(config)# snmp-server enable traps nhrpRouter(config)# snmp-server host 192.40.3.130 traps version 2c public nhrpRelated Commands
status protocol notification static
To enable the timers set in the specified class name, use the status protocol notification static command in pseudowire-class configuration mode. To disable the use of the specified class, use the no form of this command.
status protocol notification static class-name
no status protocol notification static class-name
Syntax Description
class-name
Name of an Operations, Administration, and Maintenance (OAM) class that was created with the pseudowire-static-oam-class command.
Command Default
OAM classes are not specified.
Command Modes
Pseudowire-class configuration (config-pw-class)
Command History
Examples
The following example enables the timers set in the class oam-class3:
Router(config-pw-class)# status protocol notification static oam-class3Related Commands
pseudowire-static-oam class
Creates a class that defines the OAM parameters for the pseudowire.
status (pseudowire class)
To enable the router to send pseudowire status messages to a peer router, even when the attachment circuit is down, use the status command in pseudowire class configuration mode. To disable the pseudowire status messages, use the no form of this command.
status
no status
Syntax Description
This command has no arguments or keywords.
Command Default
Pseudowire status messages are sent and received if both routers support the messages.
Command Modes
Pseudowire class configuration
Command History
12.2(33)SRC
This command was introduced.
12.2(50)SY
This command was integrated into Cisco IOS Release 12.2(50)SY.
Usage Guidelines
Both peer routers must support the ability to send and receive pseudowire status messages in label advertisement and label notification messages. If both peer routers do not support pseudowire status messages, Cisco recommends that you disable the messages with the no status command.
Examples
The following example shows how to enable the router to send pseudowire status messages to a peer router:
enableconfigure terminalpseudowire-class test1statusencapsulation mplsRelated Commands
debug mpls l2transport vc
Displays debug messages about the pseudowire status.
show mpls l2transport vc detail
Displays pseudowire status messages.
status redundancy
To designate one pseudowire as the master or slave to display status information for both active and backup pseudowires, use the status redundancy command in pseudowire class configuration mode. To disable the pseudowire as the master or slave, use the no form of this command.
status redundancy {master | slave}
no status redundancy {master | slave}
Syntax Description
master
Designates one pseudowire to work as the master.
slave
Designates one pseudowire to work as the slave.
Command Default
The pseudowire is in slave mode.
Command Modes
Pseudowire-class configuration mode (config-pw)
Command History
Usage Guidelines
One pseudowire must be the master and the other must be assigned the slave. You cannot configure both pseudowires as master or slave.
Examples
The following example designates the pseudowire as the master:
Router(config-pw)# status redundancy masterRelated Commands
show xconnect
Displays information about xconnect attachment circuits and pseudowires
switching-point
To configure a switching point and specify a virtual circuit (VC) ID range, use the switching-point command in Layer 2 pseudowire routing configuration mode. To remove the switching point configuration, use the no form of this command.
switching-point vcid minimum-vcid-value maximum-vcid-value
switching-point vcid
Syntax Description
Command Default
If an Autonomous System Boundary Router (ASBR) has been configured as a switching point (accomplished by using the no bgp default route-target filter command), the default VC ID range is 1001 to 2147483647.
Command Modes
Layer 2 pseudowire routing (config-l2_pw_rtg)
Command History
Usage Guidelines
The switching-point command is used in Layer 2 pseudowire routing configuration mode. To enter Layer 2 pseudowire routing configuration mode, use the l2 pseudowire routing command.
Changing the VC ID Range on an ASBR
The switching-point command was introduced in the L2VPN VPLS Inter-AS Option B feature and is intended for use on an Autonomous System Boundary Router (ASBR). With the L2VPN VPLS Inter-AS Option B feature, VC IDs in the VC ID range of 1001 to 2147483647 are reserved for switching pseudowires. This command allows you to change this range if, for example, an existing xconnect VC is using one of the reserved VC IDs.
Examples
In the following example, the switching-point command has been used to specify a VCID range of 200 to 3500:
Router>Router# enableRouter(config)# configure terminalRouter(config)# l2 pseudowire routingRouter(config-l2_pw_rtg)# switching-point vcid 200 3500Router(config-l2_pw_rtg)# endRelated Commands
switching tlv
To advertise the switching point type-length variable (TLV) in the label binding, use the switching tlv command in pseudowire class configuration mode. To disable the display of the TLV, use the no form of this command.
switching tlv
no switching tlv
Syntax Description
This command has no arguments or keywords.
Command Default
Switching point TLV data is advertised to peers.
Command Modes
Pseudowire class configuration (config-pw-class)
Command History
Usage Guidelines
The pseudowire switching point TLV information includes the following information:
•
•
•
•
By default, switching point TLV data is advertised to peers.
Examples
The following example enables the display of the pseudowire switching TLV:
Router(config)# pseudowire-class atomRouter(config-pw-class)# switching tlvRelated Commands
show mpls l2transport binding
Displays switching point TLV information.
show mpls l2transport vc detail
Displays switching point TLV information.
Feedback