Monitoring MPLS
Use the show commands in this section to monitor MPLS status.
You can set a statistics baseline for MPLS major interface statistics with the baseline mpls interface command. The following statistics are maintained for each MPLS major interface:
You can set a statistics baseline for MPLS forwarding table entries with the baseline mpls label command. You must first enable the statistics with the mpls statistics label command. When enabled, the following statistics are maintained for each forwarding table entry:
You can set a statistics baseline for MPLS next-hop table entries with the baseline mpls next-hop command. You must first enable these statistics with the mpls statistics next-hop command. When enabled, the following statistics are maintained for each next-hop table entry:
You can set a statistics baseline for MPLS tunnel statistics with the baseline mpls tunnel command.
You can enable collection of the following statistics for each policy attached to a tunnel by issuing the mpls statistics policy command:
You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. See JUNOSe System Basics Configuration Guide, Chapter 2, Command-Line Interface for details.
You can trace paths through the MPLS user plane with the traceroute command. ICMP extensions enable LSRs to append MPLS header information (the label stack) to ICMP destination unreachable and time exceeded messages. The traceroute display shows the label and EXP bits used to switch the ICMP packets:
host1:edge1#traceroute 10.90.101.9
Tracing route to 10.90.101.9, TTL = 32, timeout = 2 sec.
(Press ^c to stop.)
1 3ms 2ms 2ms 10.90.101.4 mplsLabel1=4009
mplsExpBits1=0
2 2ms 2ms 2ms 10.90.101.7 mplsLabel1=7004
mplsExpBits1=0
3 2ms 2ms 2ms 10.90.101.9
See JUNOSe IP, IPv6, and IGP Configuration Guide, Chapter 1, Configuring IP, for more information about using the traceroute command.
baseline mpls interface
- Use to set the baseline on all MPLS major interface statistics to zero on the specified interface.
- Example
host1#baseline mpls interface
baseline mpls label
- Use to set the baseline on all MPLS forwarding table statistics to zero on the specified interface or for the specified label.
- Example
host1#baseline mpls label
baseline mpls next-hop
- Use to set a statistics baseline for the specified MPLS next hop. Statistics for a next hop must be enabled with the mpls statistics next-hop command before they can be baselined. By default, the next-hop counters are baselined at zero.
- Example
host1#baseline mpls next-hop
baseline mpls tunnel
- Use to set a statistics baseline for the specified MPLS tunnel. By default, the tunnel counters are baselined at zero.
- Example
host1#baseline mpls tunnel tunnel5
mpls statistics label
- Use to enable statistics collection for MPLS in labels.
- By default, statistics are enabled for incoming labels and RSVP-TE or LDP outgoing labels, but not for others such as BGP outgoing labels. Statistics are not stored in NVS.
- Example
host1#mpls statistics label
mpls statistics next-hop
- Use to enable statistics collection for MPLS next hops.
- By default, statistics are enabled for next hops depending on the protocol that created the MPLS next hop. Statistics are not stored in NVS.
- Example
host1#mpls statistics next-hop 1046
mpls statistics policy
- Use to enable statistics collection for policies attached to an MPLS tunnel.
- Statistics are not stored in NVS.
- Example
host1#mpls statistics policy tunnel5
show atm vc
- Use to display a summary of all configured ATM VCs and reserved VC ranges.
- If you are using the interface label space for labels, the display includes ATM VCs used as MPLS LSPs and VPI/VCI ranges reserved for MPLS.
- You can specify one or more of the following keywords individually or in combination:
- vpi—Displays VCs on a specific VPI
- category—Displays VCs that have a specific service category
- status—Displays VCs with a certain status
- You can also specify the reserved keyword with no other keywords to display only a summary of all reserved VC ranges on the router. This includes VPI/VCI ranges reserved for use by MPLS.
- Field descriptions
- Interface—Interface type and number
- VPI—Virtual path identifier
- VCI—Virtual channel identifier
- VCD—Virtual circuit descriptor
- Type—Type of circuit: PVC
- Encap—Encapsulation method: AUTO, AAL5, MUX, SNAP, ILMI, F4-OAM
- Category—Service type configured on the VC: UBR, UBR-PCR, NRT-VBR, RT-VBR, CBR
- Rx/Tx Peak—Peak rate in Kbps
- Rx/Tx Avg—Average rate in Kbps
- Rx/Tx Burst—Maximum number of cells that can be burst at the peak cell rate
- Status—State of the virtual circuit: Up, Down
- Start VPI—Starting virtual path identifier (inclusive) of the reserved VC range
- Start VCI—Starting virtual circuit identifier (inclusive) of the reserved VC range
- End VPI—Ending virtual path identifier (inclusive) of the reserved VC range
- End VCI—Ending virtual circuit identifier (inclusive) of the reserved VC range
host1#show atm vc
Cate Rx/Tx Rx/Tx Rx/Tx Sta
Interface VPI VCI VCD Type Encap gory Peak Avg Burst tus
------------ --- ---- ---- ---- ----- ---- ----- ----- ----- ---
ATM 3/0.2 0 101 4375 PVC AUTO CBR 1000 0 0 UP
ATM 3/0.3 0 102 4376 PVC AUTO CBR 1000 0 0 DOWN
...
ATM 3/0.8099 1 8099 8099 PVC SNAP UBR 0 0 0 UP
ATM 3/0.8100 1 8100 8100 PVC SNAP UBR 0 0 0 DOWN
8000 circuit(s) found
Reserved VCC ranges:
Start Start End End
Interface VPI VCI VPI VCI
--------- ----- ----- --- ---
ATM 2/0 2 100 2 102
ATM 2/0 3 300 3 303
2 reservation(s) found
host1#show atm vc reserved
Reserved VCC ranges:
Start Start End End
Interface VPI VCI VPI VCI
--------- ----- ----- --- ---
ATM 2/0 2 100 2 102
ATM 2/0 3 300 3 303
2 reservation(s) found
show cac
host1#show cac
resource info flood interval 180
show cac interface
- Use to display all interfaces on which traffic engineering bandwidth accounting is configured, or information only for the specified interface.
- Use the brief keyword to display summary information.
- Field descriptions
- bandwidth—Maximum physical bandwidth in Kbps; line rate
- IP/MPLS reserveable bw—Total bandwidth in Kbps that can be reserved for MPLS; includes bandwidth that is already reserved as well as bandwidth not yet reserved
- current total available bw—Total bandwidth in Kbps that is available to be reserved
- MPLS TE flooding threshold up/down—Absolute percentages of total reservable bandwidth that trigger the flooding of the new bandwidth value throughout the network; flooding is triggered when bandwidth increases past any of the up threshold values and when bandwidth decreases past any of the down threshold values
- MPLS TE administrative weight—Weight assigned to the interface that supersedes a weight assigned by the IGP
- MPLS TE attribute flags—32-bit value that assigns the interface to a resource class and enables a tunnel to discriminate among interfaces by matching against tunnel affinity bits
- Available BW at 8 priority levels—Bandwidth in Kbps that is available at each priority level in the range 0–7
host1#show cac interface
atm2/0
bandwidth 10 kbps
IP/MPLS reserveable bw 10 kbps
current total available bw 10 kbps
MPLS TE flooding threshold:
up 15 30 45 60 75 80 85 90 95 96 97 98 99 100
down 100 99 98 97 96 95 90 85 80 75 60 45 30 15
MPLS TE administrative weight 0
MPLS TE attribute flags 0
Available BW at 8 priority levels:
0 10 kbps
1 10 kbps
2 10 kbps
3 10 kbps
4 10 kbps
5 10 kbps
6 10 kbps
7 10 kbps
show configuration
host1#show configuration virtual-router euro7
show ip tunnel-route
- Use to display the current state of the IPv4 or IPv6 tunnel routing table.
- You can display all routes, a specific route, best route to a resolved domain name, all routes beginning with a specified address, and routes for a particular protocol.
- Field descriptions
- Prefix—IPv4 or IPv6 address prefix of network destination
- Length—Network mask length for prefix
- Type—Type of route; protocol
- Next Hop—IP address of the next hop to the route, whether it is a local interface or another router; not displayed for IPv6 tunnel routing table
- Dst or Distance—Administrative distance for the route
- Met or Metric—Number of hops; metric
- Interface—Interface type and interface specifier
- Tag—Numeric tag that identifies route
- Class—Attribute of a route applied only as a result of set route-class clause in a table map
host1:vr2#show ip tunnel-route all
Protocol/Route type codes:
I1- ISIS level 1, I2- ISIS level2,
I- route type intra, IA- route type inter, E- route type external,
i- metric type internal, e- metric type external,
O- OSPF, E1- external type 1, E2- external type2,
N1- NSSA external type1, N2- NSSA external type2
L- MPLS label, V- VRF, *- via indirect next-hop
Prefix/Length Type Next Hop Dst/Met Interface
------------------ --------- --------------- ---------- ----------------------------------------
200.200.200.1/32 Ldp 111.111.1.1[L18 110/2 ATM5/1.1
]
Rsvp 200.200.200.1[L 110/2 ATM5/1.1
25]
host1:vr2#show ip tunnel-route 200.200.200.1/32 detail
Protocol/Route type codes:
I1- ISIS level 1, I2- ISIS level2,
I- route type intra, IA- route type inter, E- route type external,
i- metric type internal, e- metric type external,
O- OSPF, E1- external type 1, E2- external type2,
N1- NSSA external type1, N2- NSSA external type2
L- MPLS label, V- VRF, *- via indirect next-hop
200.200.200.1/32 Type: Ldp Distance: 110 Metric: 2 Tag: 0 Class: 0
MPLS next-hop: 3, label 18 on ATM5/1.1 (ip19000003.mpls.ip), nbr 111.111.1.1
host1:pe1:pe11#show ipv6 tunnel-route all
Protocol/Route type codes:
O- OSPF, E1- external type 1, E2- external type2,
N1- SSA external type1, N2- NSSA external type2
L- MPLS label, V- VRF, *- via indirect next-hop
Prefix/Length Type Dst/Met Interface
-------------------------------- --------- ---------- ----------------------------------------
::21.21.21.0/126 BgpTunnel 200/0 [L20,L26] ATM5/0.10
BgpTunnel 200/0 [L20,L34] ATM5/0.10
2::2/128 BgpTunnel 200/0 [L20,L26] ATM5/0.10
BgpTunnel 200/0 [L20,L34] ATM5/0.10
host1:pe1:pe11#show ipv6 tunnel-route ::21.21.21.0/126 detail all
Protocol/Route type codes:
O- OSPF, E1- external type 1, E2- external type2,
N1- SSA external type1, N2- NSSA external type2
L- MPLS label, V- VRF, *- via indirect next-hop
::21.21.21.0/126 Type: BgpTunnel Distance: 200 Metric: 0 Class: 0
MPLS next-hop: 18, label 20, VPN traffic, resolved by MPLS next-hop 13
MPLS next-hop: 13, resolved by MPLS next-hop 34, peer ::ffff:2.2.2.2
MPLS next-hop: 34, ECMP next-hop, leg count 2
MPLS next-hop: 17, resolved by MPLS next-hop 16, peer 2.2.2.2
MPLS next-hop: 16, primary(in use): label 26 on ATM5/0.10, secondary: resolved by MPLS next-hop 0
show ldp
- Use to display information about LDP.
- The mpls keyword is optional and is provided for compatibility with non–E-series implementations.
- Field descriptions
- LSR ID—IP address of label-switched router
- FEC Deaggregation—State of FEC deaggregation, on or off
- Egress label—Type of label advertised for the LSR that is the egress router for the prefix, implicit null, explicit null, or a non-null label
- Label distribution control mode—Label distribution control mode used by LDP for label distribution, independent control, or ordered control
- LDP session retry—Configured values for the number of LDP session retry attempts and the retry interval
- LDP session hold time—Configured value for the LDP session hold time
- LDP session keepalive interval—Interval at which LDP sends session keepalive messages, in seconds
- LDP targeted-hello hold time—LDP targeted-hello hold time, in seconds
- LDP targeted-hello interval—LDP targeted-hello interval, in seconds
- Topology Driven LSP—Status of topology-driven LSP, enabled or disabled
- LSPs used for IP forwarding—LSPs are placed in the IP routing table for forwarding plain IP traffic; displayed only when the mpls ldp ip-forwarding command has been configured. Indicates whether the LSPs that are used for IP forwarding are host only, subject to a specified access list, or subject to a specified prefix list.
- LDP proto stats—LDP protocol statistics
- totalPeersDiscovered—Number of LDP peers discovered
- totalAdjacenciesEstablished—Number of LDP adjacencies established
- totalSessionsEstablished—Number of LDP sessions established
- totalFECElements—Number of FEC elements
- totalFECs—Number of FECs
- totalInLabels—Number of in labels (sent to upstream neighbor)
- totalOutLabels—Number of out labels (received from downstream neighbor)
- totalCrLSPSetup—Number of constraint-based routed LSPs set up
- totalCrLSPDeleted—Number of constraint-based routed LSPs deleted
host1#show ldp
LDP
LSR ID is 80.0.0.2
FEC Deaggregation is off
Egress label: implicit-null
Label distribution control mode: ordered control
LDP session retry 0 times at interval 10
LDP session hold time: 180
LDP session keepalive interval: 20
LDP targeted-hello hold time: 45
LDP targeted-hello interval: 15
Topology Driven LSP enabled
LSPs used for IP forwarding
for host addresses only
show ldp binding
- Use to display label bindings from the MPLS label information base. You can use either the ldp keyword or the mpls keyword to display the same information with this command.
- Field descriptions
- In—Label sent to upstream neighbor for displayed route
- Out—Label received from downstream neighbor for displayed route
- neighbor—IP address of neighbor to which the label is sent or received
- stale—Label that indicates neighbor has restarted
host1#show mpls binding
Frame Relay over MPLS vc-id 50001 group-id 2
In 26 neighbor 10.9.1.3
Out 27 neighbor 10.9.1.3
VLAN over MPLS vc-id 240001 group-id 2
In 22 neighbor 10.9.1.3
Out 25 neighbor 10.9.1.3
10.1.1.1/32
In 10001 neighbor 10.3.11.2
Out 20001 neighbor 10.3.11.2
10.2.2.2/32
In 10002 neighbor 10.4.12.2 stale
Out 20002 neighbor 10.4.12.2 stale
10.3.3.3/32
In 10005 neighbor 10.4.12.2 stale
Out 20003 neighbor 10.4.12.2 stale
10.4.12.0/30
In 10003 neighbor 10.5.5.2
Out 20004 neighbor 10.5.5.2
10.4.23.0/30
In 10004 neighbor 10.5.5.2
Out 20005 neighbor 10.5.5.2
show ldp graceful-restart
- Use to display information about LDP graceful restart.
- The mpls keyword is optional and is provided for compatibility with non–E-series implementations.
- Field descriptions
- LDP Graceful Restart—State of graceful restart, enabled or disabled
- Helper Mode—State of graceful restart helper mode, enabled or disabled
- Reconnect Time—Locally configured value for reconnect time, in seconds
- Recovery Time—Locally configured value for recovery time, in seconds
- Max Recovery Time—Locally configured value for max-recovery timer, in seconds
- Neighbor Liveness Timer—Locally configured value for neighbor-liveness timer, in seconds
- Peer—Address, state, and LDP graceful restart state for neighbor
host1#show ldp graceful-restart
LDP Graceful Restart is enabled
Helper Mode is enabled
Reconnect Time: 220 sec
Recovery Time: 240 sec
Max Recovery Time: 260 sec
Neighbor Liveness Timer: 280 sec
Peer 80.0.1.1:0, State: operational, Restarter Mode: disabled, Helper Mode: enabled
Peer 80.0.3.3:0, State: operational, Restarter Mode: disabled, Helper Mode: enabled
show ldp igp-sync
- Use to display information about interfaces that are synchronizing with LDP or the specified interface that is synchronizing with LDP.
- Field descriptions
- LDP—State of LDP, configured, auto-configured, or not configured
- SYNC status—State of synchronization, enabled or disabled
- IGP holddown time—Value of IGP hold down time, infinite or number of milliseconds
- Peer LDP Ident—IP address of LDP peer
- IGP enabled—IGP protocol
host1#show ldp igp-sync
Atm 0/0:
LDP configured; SYNC enabled.
SYNC status: sync achieved; peer reachable.
IGP holddown time: infinite.
Peer LDP Ident: 10.130.0.1:0
IGP enabled: OSPF 1
show ldp interface
- Use to display information about all LDP interfaces or the specified LDP interface.
- The mpls keyword is optional and is provided for compatibility with non–E-series implementations.
- Use the brief keyword to display a brief summary of interface information.
- Field descriptions
- Interface—Identifier of the interface
- autoconfigured—LDP has been autoconfigured on the interface
- Interface address—IP address of the interface, with address mask
- Enabled with profile—Name of profile with which interface was enabled
- Configured hold time—Configured period for which a sending LSR maintains a record of link hello messages from the receiving LSR without receipt of another link hello message from that LSR, in seconds
- Hello interval—Negotiated interval between link-hello packets, in seconds
- Hold time—Lowest configured hold time among all neighbors on the same subnet, used as the effective hold time, in seconds
- Number of adjacencies—Number of LDP adjacencies for the interface
- Link hello adjacency—Address and transport address of the link hello adjacency; time adjacency has been up in hh:mm:ss; remaining hold time for the adjacency in seconds
- Session statistics
- label alloc—Number of labels allocated and advertised to this peer
- label learned—Number of labels received from this peer
- accum label alloc—Cumulative total number of labels allocated and advertised to this peer
- accum label learned—Cumulative total number of labels received from this peer
- last restart time—Time in hh:mm:ss since session last restarted
- notf—Number of notification messages received or received bad or sent
- msg—Number of messages received or received bad or sent
- mapping—Number of label mapping messages received or received bad or sent
- request—Number of label request messages received or received bad or sent
- abort—Number of label abort messages received or received bad or sent
- release—Number of label release messages received or received bad or sent
- withdraw—Number of label withdraw messages received or received bad or sent
- addr—Number of address messages received or received bad or sent
- addr withdraw—Number of address withdraw messages received or received bad or sent
- msgId—Number of message ID messages received or sent
- unknown msg type err—Number of unknown message type errors received
- hello recv—Number of hello messages received
- hello sent—Number of hello messages sent
- bad hello recv—Number of hello messages received bad
- adj setup time—Time in hh:mm:ss since adjacency set up
- last hello recv time—Time in hh:mm:ss since last hello message received
- last hello sent time—Time in hh:mm:ss since last hello message sent
- remaining hold time—Time in hh:mm:ss remaining of the hold time
host1#show ldp interface
Interface ATM6/0.120
Interface address: 192.168.12.1/28
Enabled with profile 'default'
Configured hold time: 15
Hello interval: 5
Hold Time: 1
242 hello received, 242 hello sent, 0 hello rejected
1 adjacency created, 0 adjacency deleted,
Number of adjacencies = 1
Link hello adjacency: Address: 10.10.12.2, Transport address: 80.0.2.2,
Up for 00:20:09, Remaining hold time: 11 sec
host1#show ldp interface
Interface FastEthernet0/0 (auto-configured)
Interface address: 10.60.1.1/24
Enabled with profile 'default'
Configured hold time: 15
Hello interval: 5
Hold Time: 5
60 hello received, 60 hello sent, 0 hello rejected
1 adjacency created, 0 adjacency deleted,
Number of adjacencies = 1
Link hello adjacency: Address: 12.60.1.2, Transport address: 12.60.1.2,
Up for 00:04:56, Remaining hold time: 14 sec
host1#show ldp interface brief
Interface IP-Address Protocol
ATM6/1.1 192.168.100.21/30 enabled
ATM6/1.3 192.168.100.17/30 enabled
ATM6/1.5 192.168.100.13/30 enabled
ATM6/0.7 172.16.100.1/30 enabled
ATM6/0.8 172.16.100.22/30 enabled
ATM6/0.9 172.16.100.14/30 enabled
show ldp neighbor
- Use to display LDP neighbor information.
- The mpls keyword is optional and is provided for compatibility with non–E-series implementations.
- If a password is configured for a peer, you can view the password with the show configuration command. This command displays the passwords in cleartext unless the service password-encryption command has been issued, in which case the passwords are displayed in encrypted format.
- You can issue the brief keyword to display only brief information about the LDP neighbors.
- You can issue the graceful-restart keyword to display information about graceful restart for neighbors; other detailed information about the neighbors is omitted.
- You can issue the statistics keyword to display information about LDP statistics for the session with each LDP neighbor
- Field descriptions
- LDP neighbor—IP address of LDP peer
- LSR—IP address of remote and local peers; the number following the colon is the platform label space ID, and is always 0
- Transport address—Transport remote and local address for the TCP session
- State—State of the session, nonexistent (session connection not established) or operational (has received keepalive message)
- LDP advertisement—Mode of label distribution, downstream-unsolicited or downstream-on-demand
- Up—Time that the adjacency has been up, in hh:mm:ss format
- Graceful Restart—State of graceful restart, enabled or disabled
- Helper Mode—State of graceful restart helper mode, enabled or disabled
- Reconnect Time—Value for reconnect time received from peer in FT TLV, in milliseconds
- Recovery Time—Value for recovery time received from peer in FT TLV, in milliseconds
- State—Status of the neighbor's graceful restart, one of the following:
- nonexistent—LDP session is not established
- restarting—Neighbor LSR is restarting
- recovering—Session with neighbor LSR has reestablished after the neighbor restarted; label bindings are being exchanged
- operational—LDP session is up
- Neighbor—IP address of LDP peer
- Initialization—Number of initialization messages received and sent
- Keepalive—Number of keepalive messages received and sent
- Notification—Number of notification messages received and sent
- Address—Number of address messages received and sent
- Address withdraw—Number of address withdraw messages received and sent
- Label mapping—Number of label mapping messages received and sent
- Label request—Number of label request messages received and sent
- Label withdraw—Number of label withdraw messages received and sent
- Label release—Number of label release messages received and sent
host1#show ldp neighbor 10.3.5.1
LDP Neighbor: 10.0.2.2
LSR: Remote 10.0.2.2:0, local 10.0.1.1:0
Transport address: remote 10.0.2.2, local 10.0.1.1
State: Operational
LDP advertisement: Unsolicited
Up for 00:20:03
Number of next-hop addresses received = 3
10.0.2.2 100.6.12.2 100.6.23.2
Number of adjacencies = 1
Link Hello adjacency: address 10.6.12.2, transport 10.0.2.2,
Up for 00:20:09, remaining hold time: 11 sec
host1#show ldp neighbor brief
Neighbor Transport Address State
10.0.2.2 10.0.1.1->80.0.2.2 Operational
host1#show ldp neighbor graceful-restart
LDP Neighbor: 10.0.1.1
Graceful Restart is disabled
Helper Mode is enabled
Reconnect Time: 0 msec
Recovery Time: 0 msec
State: operational
LDP neighbor 10.0.2.2
Graceful Restart is enabled
Helper Mode is enabled
Reconnect Time: 220000 msec
Recovery Time: 0 msec
State: operational
host1#show ldp neighbor statistics
LDP Neighbor: 10.0.2.2
Message type Received Sent
---------------- -------- ----
Initialization 1 1
Keepalive 85 85
Notification 0 0
Address 1 1
Address withdraw 0 0
Label mapping 5 5
Label request 0 0
Label withdraw 2 2
Label release 2 2
show ldp profile
- Use to display a specific LDP profile, or all LDP profiles.
- The mpls keyword is optional and is provided for compatibility with non–E-series implementations.
- Field descriptions
- profile—Number of interfaces that use the profile
- session retry—Number of attempts that will be made to set up an MPLS LDP session
host1:pe2#show ldp profile default
ldp profile default: used by 2 interfaces
session retry: 10 times at interval 10
show ldp statistics
- Use to display statistics for LDP on the current virtual router
- The mpls keyword is optional and is provided for compatibility with non–E-series implementations.
- Field descriptions
- Hello—Number of hello messages received and sent
- Initialization—Number of initialization messages received and sent
- Keepalive—Number of keepalive messages received and sent
- Notification—Number of notification messages received and sent
- Address—Number of address messages received and sent
- Address withdraw—Number of address withdraw messages received and sent
- Label mapping—Number of label mapping messages received and sent
- Label request—Number of label request messages received and sent
- Label withdraw—Number of label withdraw messages received and sent
- Label release—Number of label release messages received and sent
- Label abort—Number of label abort messages received and sent
- All UDP—Number of UDP messages received and sent
- All TCP—Number of TCP messages received and sent
- Sessions opened—Number of session opened events
- Sessions closed—Number of session closed events
- Topology changes—Number of topology change events
- No router id—Number of no router ID events
- No address—Number of no address events
- No interface—Number of no interface events
- No session—Number of no session events
- No adjacency—Number of no adjacency events
- Unknown version—Number of unknown version events
- Malformed PDU—Number of malformed PDU events
- Malformed message—Number of malformed message events
- Unknown message type—Number of unknown message type events
- Inappropriate message—Number of inappropriate message events
- Malformed tlv—Number of inappropriate message events
- Bad TLV value—Number of bad TLV value events
- Missing TLV—Number of missing TLV events
- PDU too large—Number of PDU too large events
- PDU too small—Number of PDU too small events
- No Memory—Number of no memory events
host1#show ldp statistics
Message type Received Sent
---------------- -------- -----
Hello 25733 25735
Initialization 2 2
Keepalive 9646 9646
Notification 0 0
Address 2 2
Address withdraw 0 0
Label mapping 8 8
Label request 0 0
Label withdraw 0 0
Label release 0 0
Label abort 0 0
All UDP 25733 25735
All TCP 9654 9654
Event type Total
--------------------- -----
Sessions opened 2
Sessions closed 0
Topology changes 5
No router id 0
No address 0
No interface 0
No session 0
No adjacency 0
Unknown version 0
Malformed PDU 0
Malformed message 0
Unknown message type 0
Inappropriate message 0
Malformed tlv 0
Bad TLV value 0
Missing TLV 0
PDU too large 0
PDU too small 0
No Memory 0
show ldp targeted session
- D—Targeted session created by layer 2 over MPLS connection; see JUNOSe IP Services Configuration Guide, Chapter 1, Configuring Routing Policy, for more information about layer 2 over MPLS
- S—Targeted session statically created by user
- A—Targeted session created by access list
- Used By—Letter representing source of targeted session
host1#show ldp targeted session
Mpls Target Session Status:
D = Dynamically, S = Statically, A = Access List Configured
D = Dynamically, S = Statically, A = Access List Configured
Targeted session sent to 10.9.1.3 is up Used By: D
indirect nexthop index 3, resolved
Targeted session sent to 10.9.1.6 is up Used By: S
indirect nexthop index 206, resolved
show mpls
- MPLS—Status of MPLS, administratively enabled or disabled, and configuration status
- LSR ID—IP address of label-switched router
- Re-optimization timer—Frequency at which LSPs are checked for better paths
- Label range—Range of platform label space
- retry—Retry behavior to be performed during LSP setup
- Loop Detect—Status of loop detection, enabled or disabled
- LDP—This field and the following fields are displayed only when LDP is enabled.
- LSR ID—IP address of label-switched router
- FEC Deaggregation—State of FEC deaggregation, on or off
- Egress label—Type of label advertised for the LSR that is the egress router for the prefix, explicit-null or a non-null label
- Label distribution control mode—Label distribution control mode used by LDP for label distribution, independent control or ordered control
- LDP session retry—Interval in seconds between attempts to set up an MPLS LDP session
- LDP session hold time—Period in seconds for which an LSR maintains the session with its LDP peer without receipt of any LDP message from that peer
- LDP session keepalive interval—Interval at which LDP sends session keepalive messages, in seconds
- LDP targeted hello hold time—LDP targeted-hello hold time, in seconds
- LDP targeted-hello interval—LDP targeted-hello interval, in seconds
- Topology Driven LSP—Status of topology-driven LSP, enabled or disabled
- LSPs used for IP forwarding—LSPs are placed in the IP routing table for forwarding plain IP traffic; displayed only when the mpls ldp ip-forwarding command has been configured. Indicates whether the LSPs that are used for IP forwarding are host only, subject to a specified access list, or subject to a specified prefix list.
- LSRID—IP address of label-switched router
- Re-optimization timer—Frequency at which LSPs are checked for better paths
- Tunnel retry—Retry behavior to be performed during LSP setup
- Refresh reduction—State of RSVP-TE summary refresh reduction, OFF or ON
- Message bundling—State of RSVP-TE summary refresh message bundling, OFF or ON
- Egress label—Type of label advertised for the LSR that is the egress router for the prefix, explicit-null or a non-null label
- Hellos—State of RSVP-TE hello feature, including the hello refresh interval and hello miss limit
- Graceful restart—State of RSVP-TE graceful restart, OFF or ON
- helper mode—Graceful restart helper mode is enabled when this field is displayed
- Restart time—Graceful restart time, in milliseconds
- Recovery time—Graceful restart recovery time, in milliseconds
host1#show mpls
MPLS administratively enabled
Current state is Config incomplete
LSR ID is 10.2.2.2
Re-optimization timer is 3600
Label range 3000 ~ 4000
retry forever at interval 30 during LSP setup if there is route
retry forever at interval 30 during LSP setup if there is no route
Loop Detect enabled
LDP
LSR ID is 80.0.0.2
FEC Deaggregation is off
Egress label: implicit-null
Label distribution control mode: ordered control
LDP session retry 0 times at interval 10
LDP session hold time: 180
LDP session keepalive interval: 20
LDP targeted-hello hold time: 45
LDP targeted-hello interval: 15
Topology Driven LSP enabled
LSPs used for IP forwarding
for host addresses only
RSVP is enabled
LSRID 10.1.1.1
Re-optimization timer is 3600
Tunnel retry forever at interval 5 if route is available
Tunnel retry forever at interval 5 if no route is available
Refresh reduction is OFF
Message bundling is OFF
Egress label is non-null
Hellos are on with an interval of 10000 and miss limit of 4
Graceful restart is ON
Restart time 60000 milliseconds
Recovery time 120000 milliseconds
RSVP is enabled
...
Graceful restart is ON (helper mode)
show mpls explicit-paths
- path name/identifier—Name or identifier of explicit path and status, enabled or disabled, followed by list of path links and the IP address for each link's next address
host1:pe2#show mpls explicit-paths
path name/identifier rx1-path enabled
1: next-address 70.70.70.2
2: next-address 30.30.30.1
not referenced by any options
path name/identifier rx1-path2 enabled
1: next-address 60.60.60.2
2: next-address 40.40.40.1
not referenced by any options
host1:pe2#show mpls explicit-paths name rx1-path2
path name/identifier rx1-path2 enabled
1: next-address 60.60.60.2
2: next-address 40.40.40.1
not referenced by any options
show mpls fast-reroute database
- Role—Role of the router in the LSP: core, head, or tail
- Name—Name of the primary LSP
- OutIntf / Label—Interface type and specifier of the outgoing interface, and the label associated with that interface
- BackupIntf / Label—Interface type and specifier of the backup interface, and the label associated with that interface
- Backup Status—Status of backup protection (bypass) for the LSP
host1(config-if)#show mpls fast-reroute database
OutIntf Backup
Role Name / Label BackupIntf / Label Status
---- --------------- ------------- ---------------------- -----------
Core LSP 10.1.1.1:6 ATM4/0.2 / 21 tun mpls:bypass23 / 21 Established
Core LSP 10.1.1.1:7 ATM4/0.2 / 26 tun mpls:bypass23 / 26 Established
Example on a tunnel ingress router
OutIntf Backup
Role Name / Label BackupIntf / Label Status
---- ---- ------------- ---------------------- -----------
Head 1 ATM4/0.1 / 27 tun mpls:bypass12 / 27 Established
Head p2 ATM4/0.1 / 21 tun mpls:bypass12 / 21 Established
show mpls forwarding
- In label—Label sent to upstream neighbor for route
- Out label—Label received from downstream neighbor for route
- Label space—Label space in which the label is assigned
- Owner—Signaling protocol that placed the label in the forwarding table: BGP, LDP, or RSVP-TE
- Spoof check—Type and location of spoof checking performed on the MPLS packet, router or interface
- Action—Action taken for MPLS packets arriving with that label
- in pkts—Number of packets sent with the label
- in Octets—Number of octets sent with the label
- in errors—Number of packets that are dropped for some reason before being sent
- in discardPkts—Number of packets that are discarded due to lack of buffer space before being sent
host1:vr2#show mpls forwarding
In label: 28
Label space: platform label space
Owner: ldp
Spoof check: router pe1
Action:
MPLS next-hop: 1, lookup on inner header/label
Statistics:
0 in pkts
0 in Octets
0 in errors
0 in discard pkts
host1:vr2#show mpls forwarding brief
Platform label space
In Label Owner Action
-------- -------- --------------------------------------
28 ldp lookup on inner header/label
29 ldp swap to 20 on ATM2/0.10, nbr 10.10.10.2
30 ldp lookup on inner header/label
31 ldp swap to 22 on ATM2/0.10, nbr 10.10.10.2
32 ldp swap to 23 on ATM2/0.10, nbr 10.10.10.2
show mpls interface
- Use to display status and configuration information about MPLS interfaces.
- Use the shim keyword to display information about shim interfaces (used for layer 2 over MPLS). Use the minor keyword to display information about minor interfaces. Use the state not-up keyword to display information about interfaces that are not in the up state.
- Field descriptions
- Interface—Specifier and status of each interface
- RSVP—Status of RSVP, configured or not, and profile used
- LDP—Status of LDP, configured or not configured, and profile used
- IP interfaces on this MPLS interface—IP address of IP interfaces and session status
- Condensed location—Internal, platform-dependent, 32-bit representation of the interface location, used by Juniper Networks Customer support for troubleshooting.
- Session statistics
- label alloc—Number of labels allocated and advertised to this peer
- label learned—Number of labels received from this peer
- accum label alloc—Cumulative total number of labels allocated and advertised to this peer
- accum label learned—Cumulative total number of labels received from this peer
- notf—Number of notification messages received or received bad or sent
- mapping—Number of label mapping messages received or received bad or sent
- msg—Number of messages sent or received
- request—Number of label request messages received or received bad or sent
- abort—Number of label request abort messages for downstream on demand received or received bad or sent
- release—Number of label release messages received or received bad or sent
- withdraw—Number of label withdraw messages received or received bad or sent
- addr—Number of address messages received or received bad or sent
- addr withdraw—Number of address withdraw messages received or received bad or sent
- msgId—Number of message IDs received or sent
- unknown message type err—Number or unknown message type errors received
- last info error code—Last received notification code
- loop detected—Loop detected; for downstream on demand
- hello recv—Number of hello messages received
- hello sent—Number of hello messages sent
- bad hello recv—Number of hello messages received bad
- adj setup time—Time in hh:mm:ss since adjacency set up
- last hello recv time—Time in hh:mm:ss since last hello message received
- last hello sent time—Time in hh:mm:ss since last hello message sent
- failed lbl lookup—Number of packets received whose labels are not recognized
- octets—Number of octets received or sent
- hcoctets—Number of high-capacity (64-bit) octets received or sent
- pkts—Number of packets received or sent
- hcpkts—Number of high-capacity (64-bit) packets received or sent
- errors—Number of packets that are dropped for some reason at receipt or before being sent
- discards—Number of packets that are discarded due to lack of buffer space at receipt or before being sent
- adjacency—Number of adjacencies currently established
- session—Number of sessions currently established
- accum adjacency—Cumulative total number of adjacencies established since interface is up
- accum session—Cumulative total number of sessions established since interface is up
- hello recv—Number of hello messages received
- hello sent—Number of hello messages sent
- hello rej—Number of hello messages rejected
- adj setup—Number of adjacencies set up
- adj deleted—Number of adjacencies deleted
host1:pe1#show mpls interface
MPLS major interface ATM2/0.10
ATM circuit type is 1483 LLC encapsulation
Administrative state is enabled
Operational state is up
Operational MTU is 9180
Received:
0 packets
0 bytes
0 errors
0 discards
0 failed label lookups
Sent:
0 packets
0 bytes
0 errors
0 discards
LDP information:
10.1.1.2/24
enabled with profile 'default'
0 hello recv, 1 hello sent, 0 hello rej
0 adj setup, 0 adj deleted,
RSVP
Enabled with profile default
Authentication is disabled
Authentication key: <none>
Hellos are on with an interval of 10000 and miss limit of 4
Hello settings are not inherited
MPLS minor interface pe1-to-pe2 (transmit)
Stacked on MPLS major ATM2/0.10
Operational state is up
Sent:
0 packets
0 bytes
queue 0: traffic class best-effort, bound to atm-vc ATM2/0.10
Queue length 0 bytes
Forwarded packets 0, bytes 0
Dropped committed packets 0, bytes 0
Dropped conformed packets 0, bytes 0
Dropped exceeded packets 0, bytes 0
MPLS minor interface lsp-02020202-1-4 (receive)
Stacked on MPLS major ATM2/0.10
Operational state is up
Statistics not enabled for this interface
host1:pe2#show mpls interface atm 5/1.1
Interface ATM5/1.1 Up
RSVP enabled with profile default
Authentication: enabled
Authentication Key: <a password has been configured>
LDP not configured
IP interfaces on this MPLS interface:
192.168.100.21/30
MPLS Statistics:
Rcvd: 0 failed lbl lookup, 0 octets, 0 hcOctets
0 pkts, 0 hcPkts, 0 errors, 0 discards
Sent: 0 octets, 0 hcOctets, 0 pkts
0 hcPkts, 0 errors, 0 discards
...
host1:pe2#show mpls interface atm 2/0.60
Interface atm2/0.60 Up
RSVP not configured
LDP enabled with profile default
IP interfaces on this MPLS interface:
60.60.60.1/16 Session to 4.4.4.4 is operational (active)
Session statistics:
12 label alloc, 12 label learned,
12 accum label alloc, 12 accum label learned,
last restart time = 00:04:44
Rcvd: 0 notf, 29 msg, 12 mapping, 0 request
0 abort, 0 release, 0 withdraw, 1 addr
0 addr withdraw, 29 msgId
0 bad mapping, 0 bad request, 0 bad abort, 0 bad release
0 bad withdraw, 0 bad addr, 0 bad addr withdraw
0 unknown msg type err
last info err code = 0x00000000, 0 loop detected
Sent: 0 notf, 29 msg, 12 mapping, 0 request
0 abort, 0 release, 0 withdraw, 1 addr
0 addr withdraw, 29 msgId
Adjacency statistics:
58 hello recv, 57 hello sent, 0 bad hello recv
adj setup time = 00:04:44
last hello recv time = 00:00:05, last hello sent time = 00:00:05
MPLS Statistics:
Rcvd: 0 failed lbl lookup, 0 octets, 0 hcOctets
0 pkts, 0 hcPkts, 0 errors, 0 discards
Sent: 0 octets, 0 hcOctets, 0 pkts
0 hcPkts, 0 errors, 0 discards
1 adjacency, 1 session, 3 accum adjacency, 3 accum session 14058 hello recv, 14063 hello sent, 0 hello rej 3 adj setup, 2 adj deleted
host1:vr2#show mpls interface atm 6/1.1
...
MPLS major interface ATM6/1.1
ATM circuit type is 1483 LLC encapsulation
Administrative state is enabled
Operational state is up
Operational MTU is 9180
Received:
0 packets
0 bytes
0 errors
0 discards
0 failed label lookups
Sent:
0 packets
0 bytes
0 errors
0 discards
LDP information:
10.1.1.1/24
enabled with profile 'default'
0 hello recv, 2 hello sent, 0 hello rej
0 adj setup, 0 adj deleted,
RSVP
Enabled with profile default
Authentication is disabled
Authentication key: <none>
Hellos are on with an interval of 10000 and miss limit of 4
Hello settings are not inherited
host1:pe1#show mpls interface detail
MPLS major interface ATM2/0.10
ATM circuit type is 1483 LLC encapsulation
Administrative state is enabled
Operational state is up
Operational MTU is 9180
MPLS major interface UID is 0x19000001
Lower interface UID is 0x0b000031
Uses platform label space
Peer IPv4 interface is ATM2/0.10 (UID 0x000000be)
No peer IPv6 interface
Upper IPv4 interface is ip19000001.mpls.ip (UID 0x000000bf, FEC index 0x0000003f)
No upper IPv4 VPN interface
No upper IPv6 interface
No upper IPv6 VPN interface
Condensed location is 0x00020000
Received:
0 packets
0 bytes
0 errors
0 discards
0 failed label lookups
Sent:
0 packets
0 bytes
0 errors
0 discards
RSVP
Enabled with profile default
Authentication is disabled
Authentication key: <none>
MPLS minor interface pe1-to-pe2 (transmit)
Stacked on MPLS major ATM2/0.10
Operational state is up
MPLS minor interface UID is 0x1a000001
Lower MPLS major interface UID is 0x19000001
Sent:
0 packets
0 bytes
queue 0: traffic class best-effort, bound to atm-vc ATM2/0.10
Queue length 0 bytes
Forwarded packets 0, bytes 0
Dropped committed packets 0, bytes 0
Dropped conformed packets 0, bytes 0
Dropped exceeded packets 0, bytes 0
MPLS minor interface lsp-02020202-1-4 (receive)
Stacked on MPLS major ATM2/0.10
Operational state is up
MPLS minor interface UID is 0x1a000004
Lower MPLS major interface UID is 0x19000001
Statistics not enabled for this interface
host1:pe1#show mpls interface brief
MPLS major interfaces
Admin Oper
Interface state state
--------- ------- -----
ATM2/0.10 enabled up
MPLS shim interfaces
Remote-PE Virtual Load
or Circuit Balancing Admin Oper
Interface LSP-name ID Group state state
--------- --------- ------- --------- ----- -----
MPLS minor interfaces
Lower Oper
Interface MplsMajor state Direction
---------------- --------- ----- ---------
pe1-to-pe2 ATM2/0.10 up transmit
lsp-02020202-1-4 ATM2/0.10 up receive
ERX-01-0c-d7:pe1#
host1:vr2#show mpls interface detail
MPLS major interface fastEthernet6/0
RSVP
Enabled with profile default
Authentication is disabled
Authentication key: <none>
Hellos are enabled
Hellos interval is 10000 milliseconds
Hellos miss limit is 4
Hello settings are not inherited
show mpls minor-interface
- Use to display status and configuration information about MPLS minor interfaces. You can display the same information with the show mpls interface minor command.
- Use the state not-up keyword to display information about interfaces that are not in the up state.
- Field descriptions
host1:pe1#show mpls minor-interface
MPLS minor interface pe1-to-pe2 (transmit)
Stacked on MPLS major ATM2/0.10
Operational state is up
Sent:
0 packets
0 bytes
queue 0: traffic class best-effort, bound to atm-vc ATM2/0.10
Queue length 0 bytes
Forwarded packets 0, bytes 0
Dropped committed packets 0, bytes 0
Dropped conformed packets 0, bytes 0
Dropped exceeded packets 0, bytes 0
MPLS minor interface lsp-02020202-1-4 (receive)
Stacked on MPLS major ATM2/0.10
Operational state is up
Statistics not enabled for this interface
host1:pe1#show mpls minor-interface detail
MPLS minor interface pe1-to-pe2 (transmit)
Stacked on MPLS major ATM2/0.10
Operational state is up
MPLS minor interface UID is 0x1a000001
Lower MPLS major interface UID is 0x19000001
Sent:
0 packets
0 bytes
queue 0: traffic class best-effort, bound to atm-vc ATM2/0.10
Queue length 0 bytes
Forwarded packets 0, bytes 0
Dropped committed packets 0, bytes 0
Dropped conformed packets 0, bytes 0
Dropped exceeded packets 0, bytes 0
MPLS minor interface lsp-02020202-1-4 (receive)
Stacked on MPLS major ATM2/0.10
Operational state is up
MPLS minor interface UID is 0x1a000004
Lower MPLS major interface UID is 0x19000001
Statistics not enabled for this interface
host1:pe1#show mpls minor-interface brief
Lower Oper
Interface MplsMajor state Direction
---------------- --------- ----- ---------
pe1-to-pe2 ATM2/0.10 up transmit
lsp-02020202-1-4 ATM2/0.10 up receive
ERX-01-0c-d7:pe1#
show mpls next-hop
- Use to display MPLS next hops and any available next-hop statistics.
- When one MPLS next-hop points to another MPLS next hop, the second next hop is displayed indented to the first one. This command also displays statistics for a next hop, if available.
- Next hops can be pointed to by MPLS forwarding entries on an LSR, IP or IPv6 routes on an LER, and VPLS bridge groups.
- Field descriptions
host1:vr2#show mpls next-hop
MPLS next-hop: index 1, lookup on inner header/label
Statistics are not collected for MPLS switch-context next-hops
MPLS next-hop: index 2, lookup in router pe1
Statistics are not collected for MPLS switch-context next-hops
MPLS next-hop: index 22, ECMP next-hop, leg count 2
MPLS next-hop: index 20, label 36 on FastEthernet1/1.120, neighbor 10.120.120.1
MPLS next-hop: index 21, label 36 on ATM2/1.20, neighbor 10.20.20.1
Statistics are not collected for MPLS ECMP next-hops
MPLS next-hop: index 24, label 17, resolved by MPLS nextHop index 10
MPLS next-hop: index 10, resolved by MPLS nextHop index 14, peer address 10.1.1.1
MPLS next-hop: index 14, ECMP next-hop, leg count 2
MPLS next-hop: index 12, label 32 on FastEthernet1/1.120, neighbor 10.120.120.1
MPLS next-hop: index 13, label 32 on ATM2/1.20, neighbor 10.20.20.1
Sent:
0 packets
0 bytes
0 errors
0 discards
MPLS next-hop: index 25, label 18, resolved by MPLS nextHop index 10
MPLS next-hop: index 10, resolved by MPLS nextHop index 14, peer address 10.1.1.1
MPLS next-hop: index 14, ECMP next-hop, leg count 2
MPLS next-hop: index 12, label 32 on FastEthernet1/1.120, neighbor 10.120.120.1
MPLS next-hop: index 13, label 32 on ATM2/1.20, neighbor 10.20.20.1
Sent:
0 packets
0 bytes
0 errors
0 discards
show mpls phb-id
- Use to display the configured mapping between PHB IDs and traffic class/color combinations.
- PHB IDs used for L-LSPs do not have color.
- Field descriptions
- phb-id—Per-hop behavior ID for which a traffic class/color combination is displayed
- traffic-class—Traffic class associated with traffic
- color—Color (drop precedence) associated with traffic, green, yellow, or red
host1#show mpls phb-id
Mpls PHB-ID traffic-class/color mappings:
-------- ------ -- ------------- ----------- ----- ------
standard phb-id 0 traffic-class best-effort color green
private phb-id 0 traffic-class best-effort color yellow
private phb-id 1 traffic-class 1 color red
private phb-id 2 traffic-class 2 color green
standard phb-id 1 traffic-class 1 color yellow
standard phb-id 2 traffic-class 2 color red
standard phb-id 3 traffic-class 3 color green
standard phb-id 4 traffic-class 4 color green
standard phb-id 6 traffic-class 6 color n/a
standard phb-id 7 traffic-class 7 color n/a
standard phb-id 10 traffic-class 5 color n/a
show mpls profile
- Use to display a specific RSVP-TE or tunnel profile, or all RSVP-TE or tunnel profiles.
- Field descriptions
- profile—Number of interfaces that use the profile
- refresh-period—Timeout period in seconds between generation of refresh messages
- timeout factor—Number of refresh messages that can be lost before the session is ended
host1:pe2#show mpls rsvp profile default
RSVP profile default: used by 0 interfaces
refresh period: 30000 ms
timeout factor: 3
host1#show mpls tunnels profile
MPLS Tunnel Profile tunnelProfile
LSP setup using rsvp-te
tunnel not announced to any IGP
(Global) Retry forever
at (Global) interval 5 during Lsp setup if there is route
(Global) Retry forever
at (Global) interval 5 during Lsp setup if there is no route
metric is relative 0
path option 2
path to be dynamically calculated by isis
destinations include: 1.1.1.1 2.2.2.2 3.3.3.3
ISIS Level 2 routers
OSPF border routers
show mpls rsvp
- Use to display RSVP path state control blocks, reservation state control blocks, or session information about the virtual router to assist in debugging.
- Sessions can be any of the following:
- ingress—Originating on the router
- egress—Terminating on the router
- transit—Travelling through the router
- PSB—Path state control block
- RSB—Reservation state control block
- Sender—IP address of PSB or RSB sender
- LSPId—ID of LSP
- timeout—Period of time in milliseconds before PSB/RSB times out if no refresh arrives.
- InLabel—Incoming label information
- Associated tunnel—Tunnel identifier for minor interface for which the RSVP information is displayed
- PHopIntf—Penultimate hop interface
- IncomingIntf—Incoming interface
- OutgoingIntf—Outgoing interface
- PHopAddr—Penultimate hop address
- m_ipNextHopAddr—Next hop address
- NextHop—Type of next hop (loose, strict, session)
- LabelRange—RSVP session label range
- SenderTSpec—Traffic parameters for the sender
- Token Bucket Rate—Sender's description of generated traffic, in kbps
- Token Bucket Size—Sender's description of generated traffic, in kbps
- Peak Data Rate—Lender's peak traffic generation rate
- Min Policed Unit—Minimum packet size generated by sender
- Max Packet Size—Maximum packet size generated by sender
- RRO—Record route object
- ADSPEC—Indicates presence of this QoS object
- IN ERO—Incoming explicit route object
- OUT ERO—Outgoing explicit route object
- SES ATTR—RSVP session attributes
- Setup Pri—Setup priority of tunnel
- Hold Pri—Hold priority of tunnel
- name—Name of the tunnel
- Flags—One or more of the IngressReRoute (the ingress router can reroute the LSP), Local Protection (routers can use local repair mechanism to fix the LSP; this fix might violate the explicit route object associated with the LSP), and MergingPermitted (LSPs can be merged) flags
- TTC—Indicates presence of the traffic trunk classifier object
- Policy Object—Indicates presence of the policy object
- Unknown Objects—Indicates presence objects not defined by the RSVP specification
- PSB Flags
- InUse—PSB in use
- Deleted—PSB deleted
- NonRsvp—Non-RSVP hop present
- RouteChangeNotify—Route change notification received
- EroChanged—Explicit route object changed
- NextHopChanged—Next hop has changed
- RtNextHopChanged—Routing table next hop changed
- EgressStatusChanged—PSB egress status has changed
- QosChanged—QoS characteristics have changed
- LabelChanged—Label has changed
- ResvRefreshNeeded—Reservation refresh needed
- PathRefreshNeeded—Path refresh needed
- RroRequired—Record route object required
- Egress—Session is egress
- PathRefreshSent—Path refresh sent
- EgressFilterFF—Egress filter reservation style Fixed Filter
- QosCorrectionNeeded—QoS correction needed
- IsPathTrigger—Has path refresh been triggered
- InUse—RSB in use
- Deleted—RSB deleted
- RcvdAck—Acknowledgment received
- StyleConverted— Reservation style converted to shared explicit
- IsPathTrigger—Reservation refresh triggered
- Destination—RSVP session destination address
- TunnelId—Number representing the RSVP session tunnel ID
- Extended Tunnel Id—IP address representing the RSVP session extended tunnel ID
host1#show mpls rsvp psb
PSB: Sender 223.10.1.1 LSPId 1 timeout -- InLabel --
PHopIntf
IncomingIntf
OutgoingIntf ATM2/0.1
PHopAddr 0.0.0.0 m_ipNextHopAddr 221.1.1.1
NextHop 221.1.1.1/255.255.255.255 (strict)
LabelRange --
SenderTSpec CType IntServ Controlled Load
Token Bucket Rate 0
Token Bucket Size 0
Peak Data Rate 0
Min Policed Unit 0
Max Packet Size 0
Flags : InUse
RroRequired
PathRefreshSent
host1#show mpls rsvp rsb
RSB: Timeout 157500 label 1/33
Flags : InUse
StyleConverted
host1:two#show mpls rsvp sessions
Destination 222.9.3.1 TunnelId 1 Extended Tunnel Id 223.10.1.1
PSB: Sender 223.10.1.1 LSPId 1 timeout 157500 InLabel 17
Associated Minor Interface: Tunnel 223.10.1.1:1
PHopIntf ATM2/0.1
IncomingIntf ATM2/1.1
OutgoingIntf ATM2/0.3
PHopAddr 221.1.1.2 m_ipNextHopAddr 122.1.1.1
NextHop 122.1.1.1/255.255.255.255 (strict)
LabelRange (generic) min 0 max 1048575
SenderTSpec CType IntServ Controlled Load
Token Bucket Rate 0
Token Bucket Size 0
Peak Data Rate 0
Min Policed Unit 0
Max Packet Size 0
RRO IPv4 hop 221.1.1.2 (strict)
ADSPEC --
IN ERO IPv4 hop 221.1.1.1 (strict)
IPv4 hop 122.1.1.1 (strict)
OUT ERO IPv4 hop 122.1.1.1 (strict)
SES ATTR Setup Pri 4, Hold Pri 4, name --
Flags : IngressReRoute
TTC --
Policy Object --
Unknown Objects --
Flags : InUse
PathRefreshSent
RSB: Timeout 157500 label 16
Associated Minor Interface: Tunnel 223.10.1.1:1
FlowSpec CType IntServ Controlled Load
Token Bucket Rate 0
Token Bucket Size 0
Peak Data Rate 0
Min Policed Unit 0
Max Packet Size 0
RRO IPv4 hop 122.1.1.1 (strict)
Policy Object --
Unknown Objects --
Flags : InUse
StyleConverted
ResvRefrSent
show mpls rsvp authentication
- Use to display information about RSVP MD5 authentication.
- For point-to-point interfaces, this command displays a single secure association with the single peer at the remote end. For multiaccess type interfaces (Ethernet), this command displays, if present, multiple secure associations from the various RSVP speakers.
- Field descriptions
- RSVP Authentication Secure Association with peer—IP address of a peer with which the router has a security association
- Receive Sequence Number—Sequence number of first authenticated packet from peer; subsequent packets from the peer must be greater than this base number
host1#show mpls rsvp authentication
Mpls interface FastEthernet2/4
RSVP Authentication Secure Association with peer 10.2.2.2
Receive Sequence Number 4592798942692985943
RSVP Authentication Secure Association with peer 10.3.3.3
Receive Sequence Number 4592798942692912623
Mpls interface ATM6/0.2
RSVP Authentication Secure Association with peer 102.2.2.2
Receive Sequence Number 4592798942692985934
Mpls interface ATM6/0.3
RSVP Authentication Secure Association with peer 10.2.2.2
Receive Sequence Number 4592798942692985956
show mpls rsvp bfd interfaces
- Use to display information about RSVP-TE major interfaces on which BFD is enabled.
- Field descriptions
- Interface—RSVP-TE major interface on which BFD is enabled
- Minimum Interval—Minimum interval in milliseconds, used when the minimum receive interval and minimum transmit intervals have the same value
- Minimum Rx-Interval—Minimum receive interval in milliseconds; minimum interval at which the local peer must receive BFD control packets from the remote peer
- Minimum Tx-Interval—Minimum transmit interval in milliseconds; interval at which the local peer proposes to transmit BFD control packets to the remote peer
- Multiplier—Detection multiplier value; roughly equivalent to the number of packets that can be missed before the BFD session is declared to be down
host1#show mpls rsvp bfd interfaces
Bfd Enabled RSVP interfaces
---------------------------
Minimum Minimum Minimum
Interface Interval Rx-Interval Tx-Interval Multiplier
--------- -------- ----------- ----------- ----------
ATM2/0.1 300 300 300 3
show mpls rsvp counters
- Use to display various counters for a particular RSVP interface or all RSVP interfaces.
- Field descriptions
- Path Sent—Number of path messages sent on the interface
- Path Rcvd—Number of path messages received on the interface
- Path Error Sent—Number of patherror messages sent on the interface
- Path Error Rcvd—Number of patherror messages received on the interface
- Path Tear Sent—Number of pathtear messages sent on the interface
- Path Tear Rcvd—Number of pathtear messages received on the interface
- Resv Sent—Number of resv messages sent on the interface
- Resv Rcvd—Number of resv messages received on the interface
- Resv Error Sent—Number of resverr messages sent on the interface
- Resv Error Rcvd—Number of resverr messages received on the interface
- Resv Tear Sent—Number of resvtear messages sent on the interface
- Resv Tear Rcvd—Number of resvtear messages received on the interface
- Resv Conf Sent—Number of resvconf messages sent on the interface
- Resv Conf Rcvd—Number of resvconf messages received on the interface
- Srefresh Conf Sent—Number of srefresh messages sent on the interface
- Srefresh Conf Rcvd—Number of srefresh messages received on the interface
- Ack Conf Sent—Number of resvconf messages sent on the interface
- Ack Conf Rcvd—Number of resvconf messages received on the interface
- Nack Objects Sent—Number of nack objects sent on the interface
- Nack Objects Rcvd—Number of nack objects received on the interface
- Msg Bundles Objects Sent—Number of message bundles sent on the interface
- Msg Bundles Rcvd—Number of message bundles received on the interface
- Error Msgs Rcvd—Number of error messages received on the interface
- Misordered Messages—Number of misordered messages received on the interface
- Send Failures—Number of failures to successfully send messages on the interface
- Path Triggers—Number of locally triggered path messages
- Resv Triggers—Number of locally triggered resv messages
- Forwarded Pkts—RSVP control packets that are forwarded through the router
- Hello Sent—Number of hello messages sent
- Hello Rcvd—Number of hello messages received
- Hello Ack Sent—Number of acknowledgments sent in response to hello requests received
- Hello Ack Rcvd—Number of acknowledgments received in response to hello requests sent
- Hello Discarded—Number of hello messages discarded
- Hello Ack Discarded—Number of hello ack messages discarded
- Hello Suppressed—Number of hello messages suppressed; message generation is suppressed when a hello request object is received from the destination node within the hello interval
host1#show mpls rsvp counters atm 6/0.1
Interface ATM6/0.1
Path Sent 247 Path Rcvd 0
Path Error Sent 0 Path Error Rcvd 0
Path Tear Sent 0 Path Tear Rcvd 0
Resv Sent 0 Resv Rcvd 245
Resv Error Sent 0 Resv Error Rcvd 0
Resv Tear Sent 0 Resv Tear Rcvd 0
Resv Conf Sent 0 Resv Conf Rcvd 0
SRefresh Sent 0 SRefresh Rcvd 0
Ack Sent 0 Ack Rcvd 0
Nack Objects Sent 0 Nack Objects Rcvd 0
Msg Bundles Sent 0 Msg Bundles Rcvd 0
Error Msgs Rcvd 0 Misordered Messages 0
Send Failures 0 Msgs not acked 0
Path Triggers 1 Resv Triggers 0
Forwarded Pkts 0
Hello Sent 7097 Hello Rcvd 7097
Hello Ack Sent 0 Hello Ack Rcvd 7097
Hello Discarded 0 Hello Ack Discarded 0
Hello Suppressed 0
show mpls rsvp hello graceful restart
- Graceful-restart—State of graceful restart, ON or Off
- Warning—State of graceful restart attributes
- Restart time—Graceful restart time, in milliseconds
- Recovery time—Graceful restart recovery time, in milliseconds
host1#show mpls rsvp hello graceful restart
Graceful restart is ON
Warning: Graceful restart is NOT active
Warning: Hellos not configured on all interfaces
Restart time 60000 milliseconds
Recovery time 120000 milliseconds
show mpls rsvp hello instance
- Use to display summary or detailed information about RSVP-TE hello adjacency instances.
- Field descriptions
- Peer Address—Address of the peer in the RSVP-TE hello adjacency
- Interface—Specifier and status of each interface
- Interval—Interval at which hellos are sent to the neighbor, in milliseconds
- Miss Limit—Number of hello messages from the neighbor that can be missed before the adjacency is considered to be down
- State—State of the adjacency with the neighbor:
- AdjLost—Adjacency has been lost. Hellos were received from the peer but have timed out. The peer is known to be capable of graceful restart, so the router is waiting for hellos to resume from the peer. The router is actively sending hellos to the peer.
The router declares the peer to be dead if it does not receive hellos from the peer during the peer's advertised recovery period.
The router declares the peer to be gracefully restarting if hellos are seen from the peer and its sequence number has changed.
The router declares the peer to be up if hellos are seen from the peer and its sequence number has not changed.
- Dead—Hellos were received from the peer but have timed out. The router is not in graceful restart helper mode. The router changes the local hello sequence number and does not send hellos to the peer. The router transitions to Down if new control traffic needs to be sent to the peer or if the peer starts sending control traffic.
- Down—No hellos have been received from the peer. The router is actively sending hellos to the peer.
- GR—Graceful restart in progress. The hello sequence number from the peer changed. The router is in graceful restart helper mode and actively sending hellos to the peer.
- Up—Hellos were received from the peer. The router is actively sending hellos to the peer.
- Neighbor—IP address of remote hello adjacency peer
- Local Address—IP address of the local hello adjacency peer
- Restart Time—Graceful restart time, in milliseconds
- Recovery Time—Graceful restart recovery time, in milliseconds
- SrcInstance—Nonzero 32-bit value that represents the sender's hello instance. The value is maintained on a per-neighbor basis. This instance value changes only when the sending peer resets, when the sender's router reboots, or when communication is lost between the hello adjacency peers.
- DstInstance—32-bit SrcInstance value most recently received from hello adjacency peer; value is zero when no instance has been received from that peer
- Hellos Sent—Number of hello messages sent
- Hellos Received—Number of hello messages received
- Hellos Suppressed—Number of hello messages suppressed; message generation is suppressed when a hello request object is received from the destination node within the hello interval
- Hellos Acks Sent—Number of acknowledgments sent in response to hello requests received
- Hellos Acks Received—Number of acknowledgments received in response to hello requests sent
host1#show mpls rsvp hello instance
Up – neighbor is up
GR – graceful restart is in progress
Peer
Address Interface Interval Miss Limit State
-------- --------- -------- ---------- ------
10.1.1.2 ATM6/1.1 10000 4 Up
10.3.1.2 ATM6/0.3 10000 4 GR
host1#show mpls rsvp hello instance
Up – neighbor is up
GR – graceful restart is in progress
Peer
Address Interface Interval Miss Limit State
-------- --------- -------- ---------- ------
10.1.1.2 <any> 10000 4 Up
10.3.1.2 <any> 10000 4 GR
11.2.3.1 Atm3/1.3 10000 4 GR
host1#show mpls rsvp hello instance detail
Neighbor 10.1.1.2 on interface ATM6/1.1
Local Address 10.1.1.1
Restart Time: 60000 msecs
Recovery Time: 120000 msecs
State: Up
SrcInstance 0x4379F084
DstInstance 0x4379EA19
Interval : 10000
Miss Limit : 4
Hellos Sent : 0
Hellos Received : 382
Hellos Suppressed : 381
Hello Acks Sent : 382
Hello Acks Received : 0
show mpls tunnels
- Use to display status and configuration for all tunnels or for a specific tunnel in the current router context.
- A result of Incomplete Configuration in the display indicates either no tunnel endpoint or no label distribution protocol.
- Field descriptions
- Label—Label prepended to packets before being sent across tunnel
- State—Status of tunnel: Establishing, Traffic Engineering Negotiation, Up, Down, Enabled with Incomplete Config, Disabled with Incomplete Config, Disabled, or Releasing
- on—Location of tunnel
- tunnel is announced to—Protocols to which the tunnel is announced
- metric—Metric type, relative or absolute
- phb-id—PHB ID supported by this tunnel; for E-LSPs an additional exp-bits entry is displayed after the phb-id entry
- Mpls Statistics
- pkts—Number of packets sent across tunnel
- hcPkts—Number of high-capacity (64-bit) packets sent across tunnel
- octets—Number of octets sent across tunnel
- hcOctets—Number of high-capacity (64-bit) octets sent across tunnel
- errors—Number of packets that are dropped for some reason before being sent
- discardPkts—Number of packets that are discarded due to lack of buffer space before being sent
In the output for Tunnel 2, the line phb-id 2 indicates that the tunnel is an L-LSP with PHB-ID 2. You can then display the output of the show mpls phb-id command to determine the corresponding PSC. For example, the show mpls phb-id command described previously in this section indicates that PHB-ID 2 is EF class.
host1#show mpls tunnels
Tunnel 1 to 0.0.0.0
State: Enabled with Incomplete Config
tunnel not announced to any IGP
(Global) Retry forever
at (Global) interval 5 during Lsp setup if there is route
(Global) Retry forever
at (Global) interval 5 during Lsp setup if there is no route
metric is relative 0
Tunnel 2 to 222.9.1.3
State: Up
Out label 24 on ATM3/0.1 nbr 10.10.11.5
14 pkts, 0 hcPkts, 2156 octets
0 hcOctets, 0 errors, 0 discardPkts
tunnel not announced to any IGP
(Global) Retry forever
at (Global) interval 5 during Lsp setup if there is route
(Global) Retry forever
at (Global) interval 5 during Lsp setup if there is no route
metric is relative 0
phb-id 2
path option 2
option is currently used - path is calculated by isis
10.10.11.5
10.10.12.3
222.9.1.3
next reoptimization in 1687 seconds
stacked labels:
FastEthernet2/4.1 222.9.1.3 R0 Out 18 on tun mpls:1
Tunnel tail-de090106-1-18a for 222.9.1.2
State: Up
In label 20 on ATM3/0.1
0 pkts, 0 hcPkts, 0 octets
0 hcOctets, 0 errors, 0 discardPkts
show mpls tunnels brief
- Use the brief keyword to display a summary of all MPLS tunnels for the current router context or summary information for a specific tunnel in the current router context.
- Field descriptions
- name/id—Tunnel identifier
- destination—Tunnel destination; router ID of egress router
- metric—Value of tunnel metric and whether the metric is relative (R) or absolute (A)
- state/label/intf—Functional state of tunnel, label for the tunnel, and interface where tunnel resides
host1:pe2#show mpls tunnels brief
name/id destination metric state/label/intf
vpnEgressLabel3 0.0.0.0 R0 Incoming 1048573 on stack
vpnEgressLabel4 0.0.0.0 R0 Incoming 1048572 on stack
pe2-to-pe1 1.1.1.1 R0 Outgoing 300 on atm2/0.60
2.2.2.2 R0 Incoming 3000 on atm2/0.70