show mpls lsp
List of Syntax
SyntaxSyntax (EX Series Switches)
Syntax
Syntax (EX Series Switches)
Release Information
Command introduced before Junos OS Release 7.4.
defaults option added in Junos OS Release 8.5.
Command introduced in Junos OS Release 9.5 for EX Series switches.
Statement introduced in Junos OS Release 12.3X50 for the QFX Series.
Description
Display information about configured and active dynamic Multiprotocol Label Switching (MPLS) label-switched paths (LSPs).
Options
none | — | Display standard information about all configured and active dynamic MPLS LSPs. |
brief | detail | extensive | terse | — | (Optional) Display the specified level of output. The extensive option displays the same information as the detail option, but covers the most recent 50 events. |
bidirectional | unidirectional | — | (Optional) Display bidirectional or unidirectional LSP information, respectively. |
bypass | — | (Optional) Display LSPs used for protecting other LSPs. |
count-active-routes | — | (Optional) Display active routes for LSPs. |
defaults | — | (Optional) Display the MPLS LSP default settings. |
descriptions | — | (Optional) Display the MPLS label-switched path (LSP) descriptions. To view this information, you must configure the description statement at the [edit protocol mpls lsp] hierarchy level. Only LSPs with a description are displayed. This command is only valid for the ingress routing device, because the description is not propagated in RSVP messages. |
down | up | — | (Optional) Display only LSPs that are inactive or active, respectively. |
logical-system (all | logical-system-name) | — | (Optional) Perform this operation on all logical systems or on a particular logical system. |
lsp-type | — | (Optional) Display information about a particular LSP type:
|
name name | — | (Optional) Display information about the specified LSP or group of LSPs. |
p2mp | — | (Optional) Display information about point-to-multipoint LSPs. |
statistics | — | (Optional) (Ingress and transit routers only) Display accounting information about LSPs. Statistics are not available for LSPs on the egress routing device, because the penultimate routing device in the LSP sets the label to 0. Also, as the packet arrives at the egress routing device, the hardware removes its MPLS header and the packet reverts to being an IPv4 packet. Therefore, it is counted as an IPv4 packet, not an MPLS packet.
|
transit | — | (Optional) Display LSPs transiting this routing device. |
Required Privilege Level
view
List of Sample Output
show mpls lsp defaultsshow mpls lsp descriptions
show mpls lsp detail
show mpls lsp extensive
show mpls lsp ingress extensive
show mpls lsp p2mp
show mpls lsp p2mp detail
show mpls lsp detail count-active-routes
show mpls lsp statistics extensive
Output Fields
Table 1 describes the output fields for the show mpls lsp command. Output fields are listed in the approximate order in which they appear.
Table 1: show mpls lsp Output Fields
Field Name | Field Description | Level of Output |
|---|---|---|
Ingress LSP | Information about LSPs on the ingress routing device. Each session has one line of output. | All levels |
Egress LSP | Information about the LSPs on the egress routing device. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. Each session has one line of output. | All levels |
Transit LSP | Number of LSPs on the transit routing devices and the state of these paths. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. | All levels |
P2MP name | Name of the point-to-multipoint LSP. Dynamically generated P2MP LSPs used for VPLS flooding use dynamically generated P2MP LSP names. The name uses the format identifier:vpls:router-id:routing-instance-name. The identifier is automatically generated by Junos OS. | All levels |
P2MP branch count | Number of destination LSPs the point-to-multipoint LSP is transmitting to. | All levels |
P | An asterisk (*) under this heading indicates that the LSP is a primary path. | All levels |
address | (detail and extensive) Destination (egress routing device) of the LSP. | detail extensive |
To | Destination (egress routing device) of the session. | brief |
From | Source (ingress routing device) of the session. | brief detail |
State | State of the LSP handled by this RSVP session: Up, Dn (down), or Restart. | brief detail |
Active Route | Number of active routes (prefixes) installed in the forwarding table. For ingress LSPs, the forwarding table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the forwarding table is the primary MPLS table (mpls.0). | detail extensive |
Rt | Number of active routes (prefixes) installed in the routing table. For ingress RSVP sessions, the routing table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the routing table is the primary MPLS table (mpls.0). | brief |
P | Path. An asterisk (*) underneath this column indicates that the LSP is a primary path. | brief |
ActivePath | (Ingress LSP) Name of the active path: Primary or Secondary. | detail extensive |
LSPname | Name of the LSP. | brief detail |
Statistics | Displays the number of packets and the number of bytes transmitted over the LSP. These counters are reset to zero whenever the LSP path is optimized (for example, during an automatic bandwidth allocation). | extensive |
Aggregate statistics | Displays the number of packets and the number of bytes transmitted over the LSP. These counters continue to iterate even if the LSP path is optimized. You can reset these counters to zero using the clear mpls lsp statistics command. | extensive |
Packets | Displays the number of packets transmitted over the LSP. | brief extensive |
Bytes | Displays the number of bytes transmitted over the LSP. | brief extensive |
DiffServeInfo | Type of LSP: multiclass LSP (multiclass diffServ-TE LSP) or Differentiated-Services-aware traffic engineering LSP (diffServ-TE LSP). | detail |
LSPtype | Type of LSP:
Also indicates if the LSP is a Penultimate hop popping LSP or an Ultimate hop popping LSP. | detail extensive |
Bypass | (Bypass LSP) Destination address (egress routing device) for the bypass LSP. | All levels |
LSPpath | Indicates whether the RSVP session is for the primary or secondary LSP path. LSPpath can be either primary or secondary and can be displayed on the ingress, egress, and transit routing devices. | detail |
Bidir | (GMPLS) The LSP allows data to travel in both directions between GMPLS devices. | All levels |
Bidirectional | (GMPLS) The LSP allows data to travel both ways between GMPLS devices. | All levels |
FastReroute desired | Fast reroute has been requested by the ingress routing device. | detail |
Link protection desired | Link protection has been requested by the ingress routing device. | detail |
LoadBalance | (Ingress LSP) CSPF load-balancing rule that was configured to select the LSP's path among equal-cost paths: Most-fill, Least-fill, or Random. | detail extensive |
Signal type | Signal type for GMPLS LSPs. The signal type determines the peak data rate for the LSP: DS0, DS3, STS-1, STM-1, or STM-4. | All levels |
Encoding type | LSP encoding type: Packet, Ethernet, PDH, SDH/SONET, Lambda, or Fiber. | All levels |
Switching type | Type of switching on the links needed for the LSP: Fiber, Lamda, Packet, TDM, or PSC-1. | All levels |
GPID | Generalized Payload Identifier (identifier of the payload carried by an LSP): HDLC, Ethernet, IPv4, PPP, or Unknown. | All levels |
Protection | Configured protection capability desired for the LSP: Extra, Enhanced, none, One plus one, One to one, or Shared. | All levels |
Upstream label in | (Bidirectional LSPs) Incoming label for reverse direction traffic for this LSP. | All levels |
Upstream label out | (Bidirectional LSPs) Outgoing label for reverse direction traffic for this LSP. | All levels |
Suggested label received | (Bidirectional LSPs) Label the upstream node suggests to use in the Resv message that is sent. | All levels |
Suggested label sent | (Bidirectional LSPs) Label the downstream node suggests to use in the Resv message that is returned. | All levels |
Autobandwidth | (Ingress LSP) The LSP is performing autobandwidth allocation. | detail extensive |
MinBW | (Ingress LSP) Configured minimum value of the LSP, in bps. | detail extensive |
MaxBW | (Ingress LSP) Configured maximum value of the LSP, in bps. | detail extensive |
AdjustTimer | (Ingress LSP) Configured value of the bandwidth adjustment timer, indicating the total amount of time allowed before bandwidth adjustment will take place, in seconds. | detail extensive |
MaxAvgBW util | (Ingress LSP) Current value of the actual maximum average bandwidth utilization, in bps. | detail extensive |
Overflow limit | (Ingress LSP) Configured value of the threshold overflow limit. | detail extensive |
Overflow sample count | (Ingress LSP) Current value for the overflow sample count. | detail extensive |
Bandwidth Adjustment in nnn second(s) | (Ingress LSP) Current value of the bandwidth adjustment timer, indicating the amount of time remaining until the bandwidth adjustment will take place, in seconds. | detail extensive |
Underflow limit | (Ingress LSP) Configured value of the threshold underflow limit. | detail extensive |
Underflow sample count | (Ingress LSP) Current value for the underflow sample count. | detail extensive |
Underflow Max AvgBW | (Ingress LSP) The highest sample bandwidth among the underflow samples recorded currently. This is the signaling bandwidth if an adjustment occurs because of an underflow. | detail extensive |
Active path indicator | (Ingress LSP) A value of * indicates that the path is active. The absence of * indicates that the path is not active. In the following example, “long” is the active path. *Primary long Standby short | detail extensive |
Primary | (Ingress LSP) Name of the primary path. | detail extensive |
Secondary | (Ingress LSP) Name of the secondary path. | detail extensive |
Standby | (Ingress LSP) Name of the path in standby mode. | detail extensive |
State | (Ingress LSP) State of the path: Up or Dn (down). | detail extensive |
COS | (Ingress LSP) Class-of-service value. | detail extensive |
Bandwidth per class | (Ingress LSP) Active bandwidth for the LSP path for each MPLS class type, in bps. | detail extensive |
Priorities | (Ingress LSP) Configured value of the setup priority and the hold priority respecitively (the setup priority is displayed first), where 0 is the highest priority and 7 is the lowest priority. If you have not explicitly configured these values, the default values are displayed (7 for the setup priority and 0 for the hold priority). | detail extensive |
OptimizeTimer | (Ingress LSP) Configured value of the optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds. | detail extensive |
SmartOptimizeTimer | (Ingress LSP) Configured value of the smart optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds. | detail extensive |
Reoptimization in xxx seconds | (Ingress LSP) Current value of the optimize timer, indicating the amount of time remaining until the path will be reoptimized, in seconds. | detail extensive |
Computed ERO (S [L] denotes strict [loose] hops) | (Ingress LSP) Computed explicit route. A series of hops, each with an address followed by a hop indicator. The value of the hop indicator can be strict (S) or loose (L). | detail extensive |
CSPF metric | (Ingress LSP) Constrained Shortest Path First metric for this path. | detail extensive |
Received RRO | (Ingress LSP) Received record route. A series of hops, each with an address followed by a flag. (In most cases, the received record route is the same as the computed explicit route. If Received RRO is different from Computed ERO, there is a topology change in the network, and the route is taking a detour.) The following flags identify the protection capability and status of the downstream node:
| detail extensive |
Index number | (Ingress LSP) Log entry number of each LSP path event. The numbers are in chronological descending order, with a maximum of 50 index numbers displayed. | extensive |
Date | (Ingress LSP) Date of the LSP event. | extensive |
Time | (Ingress LSP) Time of the LSP event. | extensive |
Event | (Ingress LSP) Description of the LSP event. | extensive |
Created | (Ingress LSP) Date and time the LSP was created. | extensive |
Resv style | (Bypass) RSVP reservation style. This field consists of two parts. The first is the number of active reservations. The second is the reservation style, which can be FF (fixed filter), SE (shared explicit), or WF (wildcard filter). | brief detail extensive |
Labelin | Incoming label for this LSP. | brief detail |
Labelout | Outgoing label for this LSP. | brief detail |
LSPname | Name of the LSP. | brief detail |
Time left | Number of seconds remaining in the lifetime of the reservation. | detail |
Since | Date and time when the RSVP session was initiated. | detail |
Tspec | Sender's traffic specification, which describes the sender's traffic parameters. | detail |
Port number | Protocol ID and sender or receiver port used in this RSVP session. | detail |
PATH rcvfrom | Address of the previous-hop (upstream) routing device or client, interface the neighbor used to reach this router, and number of packets received from the upstream neighbor. | detail |
PATH sentto | Address of the next-hop (downstream) routing device or client, interface used to reach this neighbor, and number of packets sent to the downstream routing device. | detail |
RESV rcvfrom | Address of the previous-hop (upstream) routing device or client, interface the neighbor used to reach this routing device, and number of packets received from the upstream neighbor. The output in this field, which is consistent with that in the PATH rcvfrom field, indicates that the RSVP negotiation is complete. | detail |
Record route | Recorded route for the session, taken from the record route object. | detail |
Soft preempt | Number of soft preemptions that occurred on a path and when the last soft preemption occurred. Only successful soft preemptions are counted (those that actually resulted in a new path being used). | detail |
Soft preemption pending | Path is in the process of being soft preempted. This display is removed once the ingress router has calculated a new path. | detail |
MPLS-TE LSP Defaults | Default settings for MPLS traffic engineered LSPs:
| defaults |
The XML tag name of the bandwidth tag under the auto-bandwidth tag has been updated to maximum-average-bandwidth . You can see the new tag when you issue the show mpls lsp extensive command with the | display xml pipe option. If you have any scripts that use the bandwidth tag, ensure that they are updated to maximum-average-bandwidth.
Sample Output
show mpls lsp defaults
user@host> show mpls lsp defaults MPLS-TE LSP Defaults
LSP Holding Priority 0
LSP Setup Priority 7
Hop Limit 255
Bandwidth 0
LSP Retry Timer 30 seconds
show mpls lsp descriptions
user@host> show mpls lsp descriptionsIngress LSP: 3 sessions To LSP name Description 10.0.0.195 to-sanjose to-sanjose-desc 10.0.0.195 to-sanjose-other-desc other-desc Total 2 displayed, Up 2, Down 0
show mpls lsp detail
user@host> show mpls lsp detailIngress LSP: 1 sessions
192.168.0.4
From: 192.168.0.5, State: Up, ActiveRoute: 0, LSPname: E-D
ActivePath: (primary)
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
10.0.0.18 S 10.0.0.22 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
10.0.0.18 10.0.0.22
Total 1 displayed, Up 1, Down 0
Egress LSP: 1 sessions
192.168.0.5
From: 192.168.0.4, LSPstate: Up, ActiveRoute: 0
LSPname: E-D, LSPpath: Primary
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: -
Resv style: 1 FF, Label in: 3, Label out: -
Time left: 157, Since: Wed Jul 18 17:55:12 2012
Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
Port number: sender 1 receiver 46128 protocol 0
PATH rcvfrom: 10.0.0.18 (lt-1/2/0.17) 3 pkts
Adspec: received MTU 1500
PATH sentto: localclient
RESV rcvfrom: localclient
Record route: 10.0.0.22 10.0.0.18 <self>
Total 1 displayed, Up 1, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0show mpls lsp extensive
user@host> show mpls lsp extensiveIngress LSP: 1 sessions
192.168.0.4
From: 192.168.0.5, State: Up, ActiveRoute: 0, LSPname: E-D
ActivePath: (primary)
LSPtype: Static Configured, Ultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
10.0.0.18 S 10.0.0.22 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
10.0.0.18 10.0.0.22
11 Sep 20 15:54:35.032 Make-before-break: Switched to new instance
10 Sep 20 15:54:34.029 Record Route: 10.0.0.18 10.0.0.22
9 Sep 20 15:54:34.029 Up
8 Sep 20 15:54:20.271 Originate make-before-break call
7 Sep 20 15:54:20.271 CSPF: computation result accepted 10.0.0.18 10.0.0.22
6 Sep 20 15:52:10.247 Selected as active path
5 Sep 20 15:52:10.246 Record Route: 10.0.0.18 10.0.0.22
4 Sep 20 15:52:10.243 Up
3 Sep 20 15:52:09.745 Originate Call
2 Sep 20 15:52:09.745 CSPF: computation result accepted 10.0.0.18 10.0.0.22
1 Sep 20 15:51:39.903 CSPF failed: no route toward 192.168.0.4
Created: Thu Sep 20 15:51:08 2012
Total 1 displayed, Up 1, Down 0
Egress LSP: 1 sessions
192.168.0.5
From: 192.168.0.4, LSPstate: Up, ActiveRoute: 0
LSPname: E-D, LSPpath: Primary
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: -
Resv style: 1 FF, Label in: 3, Label out: -
Time left: 148, Since: Thu Sep 20 15:52:10 2012
Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
Port number: sender 1 receiver 49601 protocol 0
PATH rcvfrom: 10.0.0.18 (lt-1/2/0.17) 27 pkts
Adspec: received MTU 1500
PATH sentto: localclient
RESV rcvfrom: localclient
Record route: 10.0.0.22 10.0.0.18 <self>
Total 1 displayed, Up 1, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0show mpls lsp ingress extensive
user@host> show mpls lsp ingress extensive Ingress LSP: 1 sessions
50.0.0.1
From: 10.0.0.1, State: Up, ActiveRoute: 0, LSPname: test
ActivePath: (primary)
LSPtype: Static Configured
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Priorities: 7 0
OptimizeTimer: 300
SmartOptimizeTimer: 180
Reoptimization in 240 second(s).
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 3)
1.1.1.2 S 4.4.4.1 S 5.5.5.2 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
1.1.1.2 4.4.4.1 5.5.5.2
17 Aug 3 13:17:33.601 CSPF: computation result ignored, new path less avail bw[3 times]
16 Aug 3 13:02:51.283 CSPF: computation result ignored, new path no benefit[2 times]
15 Aug 3 12:54:36.678 Selected as active path
14 Aug 3 12:54:36.676 Record Route: 1.1.1.2 4.4.4.1 5.5.5.2
13 Aug 3 12:54:36.676 Up
12 Aug 3 12:54:33.924 Deselected as active
11 Aug 3 12:54:33.924 Originate Call
10 Aug 3 12:54:33.923 Clear Call
9 Aug 3 12:54:33.923 CSPF: computation result accepted 1.1.1.2 4.4.4.1 5.5.5.2
8 Aug 3 12:54:33.922 2.2.2.2: No Route toward dest
7 Aug 3 12:54:28.177 CSPF: computation result ignored, new path no benefit[4 times]
6 Aug 3 12:35:03.830 Selected as active path
5 Aug 3 12:35:03.828 Record Route: 2.2.2.2 3.3.3.2
4 Aug 3 12:35:03.827 Up
3 Aug 3 12:35:03.814 Originate Call
2 Aug 3 12:35:03.814 CSPF: computation result accepted 2.2.2.2 3.3.3.2
1 Aug 3 12:34:34.921 CSPF failed: no route toward 50.0.0.1
Created: Tue Aug 3 12:34:35 2010
Total 1 displayed, Up 1, Down 0show mpls lsp p2mp
user@host> show mpls lsp p2mp
Ingress LSP: 2 sessions P2MP name: p2mp-lsp1, P2MP branch count: 1 To From State Rt P ActivePath LSPname 10.255.245.51 10.255.245.50 Up 0 * path1 p2mp-branch-1 P2MP name: p2mp-lsp2, P2MP branch count: 1 To From State Rt P ActivePath LSPname 10.255.245.51 10.255.245.50 Up 0 * path1 p2mp-st-br1 Total 2 displayed, Up 2, Down 0 Egress LSP: 0 sessions Total 0 displayed, Up 0, Down 0 Transit LSP: 0 sessions Total 0 displayed, Up 0, Down 0
show mpls lsp p2mp detail
user@host> show mpls lsp p2mp detailIngress LSP: 2 sessions
P2MP name: p2mp-lsp1, P2MP branch count: 1
10.255.245.51
From: 10.255.245.50, State: Up, ActiveRoute: 0, LSPname: p2mp-branch-1
ActivePath: path1 (primary)
P2MP name: p2mp-lsp1
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary path1 State: Up
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 25)
192.168.208.17 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
192.168.208.17
P2MP name: p2mp-lsp2, P2MP branch count: 1
10.255.245.51
From: 10.255.245.50, State: Up, ActiveRoute: 0, LSPname: p2mp-st-br1
ActivePath: path1 (primary)
P2MP name: p2mp-lsp2
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary path1 State: Up
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 25)
192.168.208.17 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
192.168.208.17
Total 2 displayed, Up 2, Down 0
show mpls lsp detail count-active-routes
user@host> show mpls lsp detail count-active-routesIngress LSP: 1 sessions
213.119.192.2
From: 156.154.162.128, State: Up, ActiveRoute: 1, LSPname: to-lahore
ActivePath: (primary)
LSPtype: Static Configured
LoadBalance: Random
Autobandwidth
MinBW: 5Mbps MaxBW: 250Mbps
AdjustTimer: 300 secs
Max AvgBW util: 0bps, Bandwidth Adjustment in 102 second(s).
Overflow limit: 0, Overflow sample count: 0
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Priorities: 7 0
Bandwidth: 5Mbps
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 4)
10.252.0.177 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
10.252.0.177
Total 1 displayed, Up 1, Down 0
Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0show mpls lsp statistics extensive
user@host> show mpls lsp statistics extensiveIngress LSP: 1 sessions
192.168.0.4
From: 192.168.0.5, State: Up, ActiveRoute: 0, LSPname: E-D
Statistics: Packets 302, Bytes 28992
Aggregate statistics: Packets 302, Bytes 28992
ActivePath: (primary)
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
10.0.0.18 S 10.0.0.22 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
10.0.0.18 10.0.0.22
6 Oct 3 11:18:28.281 Selected as active path
5 Oct 3 11:18:28.281 Record Route: 10.0.0.18 10.0.0.22
4 Oct 3 11:18:28.280 Up
3 Oct 3 11:18:27.995 Originate Call
2 Oct 3 11:18:27.995 CSPF: computation result accepted 10.0.0.18 10.0.0.22
1 Oct 3 11:17:59.118 CSPF failed: no route toward 192.168.0.4[2 times]
Created: Wed Oct 3 11:17:01 2012
Total 1 displayed, Up 1, Down 0
