Monitoring MPLS Traffic Engineering Information

The J-Web interface provides information about MPLS label-switched paths (LSPs) and virtual private networks (VPNs).

This section contains the following topics:

Monitoring MPLS Interfaces
Monitoring MPLS LSP Information
Monitoring MPLS LSP Statistics
Monitoring RSVP Session Information
Monitoring MPLS RSVP Interfaces Information

Monitoring MPLS Interfaces

To view the interfaces on which MPLS is configured, including operational state and any administrative groups applied to an interface, select Monitor>MPLS>Interfaces, or enter the following CLI command:

show mpls interface

Table 106 summarizes key output fields in the MPLS interface information display.

Table 106: Summary of Key MPLS Interface Information Output Fields

Field	Values	Additional Information
Interface	Name of the interface on which MPLS is configured.
State	State of the specified interface: Up or Dn (down).
Administrative groups	Administratively assigned colors of the MPLS link configured on the interface.

Monitoring MPLS LSP Information

To view all label-switched paths (LSPs) configured on the services router, including all inbound (ingress), outbound (egress), and transit LSP information, select Monitor>MPLS>LSP Information, or enter the following CLI command:

show mpls lsp

Table 107 summarizes key output fields in the MPLS LSP information display.

Table 107: Summary of Key MPLS LSP Information Output Fields

Field	Values	Additional Information
Ingress LSP	Information about LSPs on the inbound device. Each session has one line of output.
Egress LSP	Information about the LSPs on the outbound device. Each session has one line of output.	MPLS learns this information by querying RSVP, which holds all the transit and outbound session information.
Transit LSP	Number of LSPs on the transit routers and the state of these paths.	MPLS learns this information by querying RSVP, which holds all the transit and outbound session information.
To	Destination (outbound device) of the session.
From	Source (inbound device) of the session.
State	State of the path. It can be Up, Down, or AdminDn.	AdminDn indicates that the LSP is being taken down gracefully.
Rt	Number of active routes (prefixes) installed in the routing table.	For inbound RSVP sessions, the routing table is the primary IPv4 table (inet.0). For transit and outbound RSVP sessions, the routing table is the primary MPLS table (mpls.0).
Active Path	Name of the active path: Primary or Secondary.	This field is used for inbound LSPs only.
P	An asterisk (*) in this column indicates that the LSP is a primary path.	This field is used for inbound LSPs only.
LSPname	Configured name of the LSP.
Style	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).	This field is used for outbound and transit LSPs only.
Labelin	Incoming label for this LSP.
Labelout	Outgoing label for this LSP.
Total	Total number of LSPs displayed for the particular type—ingress (inbound), egress (outbound), or transit.

Monitoring MPLS LSP Statistics

To display statistics for LSP sessions currently active on the device, including the total number of packets and bytes forwarded through an LSP, select Monitor>MPLS>LSP Statistics, or enter the following CLI command:

show mpls lsp statistics

Note: Statistics are not available for LSPs on the outbound device, because the penultimate device in the LSP sets the label to 0. Also, as the packet arrives at the outbound 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.

Table 108 summarizes key output fields in the MPLS LSP statistics display.

Table 108: Summary of Key MPLS LSP Statistics Output Fields

Field	Values	Additional Information
Ingress LSP	Information about LSPs on the inbound device. Each session has one line of output.
Egress LSP	Information about the LSPs on the outbound device. Each session has one line of output.	MPLS learns this information by querying RSVP, which holds all the transit and outbound session information.
Transit LSP	Number of LSPs on the transit routers and the state of these paths.	MPLS learns this information by querying RSVP, which holds all the transit and outbound session information.
To	Destination (outbound device) of the session.
From	Source (inbound device) of the session.
State	State of the path: Up, Down, or AdminDn.	AdminDn indicates that the LSP is being taken down gracefully.
Packets	Total number of packets received on the LSP from the upstream neighbor.
Bytes	Total number of bytes received on the LSP from the upstream neighbor.
LSPname	Configured name of the LSP.
Total	Total number of LSPs displayed for the particular type—ingress (inbound), egress (outbound), or transit.

Monitoring RSVP Session Information

To view information about RSVP-signaled LSP sessions currently active on the device, including inbound (ingress) and outbound (egress) addresses, LSP state, and LSP name, select Monitor>MPLS>RSVP Sessions, or enter the following CLI command:

show rsvp session

Table 109 summarizes key output fields in the RSVP session information display.

Table 109: Summary of Key RSVP Session Information Output Fields

Field	Values	Additional Information
Ingress LSP	Information about inbound RSVP sessions. Each session has one line of output.
Egress LSP	Information about outbound RSVP sessions. Each session has one line of output.	MPLS learns this information by querying RSVP, which holds all the transit and outbound session information.
Transit LSP	Information about transit RSVP sessions.	MPLS learns this information by querying RSVP, which holds all the transit and outbound session information.
To	Destination (outbound device) of the session.
From	Source (inbound device) of the session.
State	State of the path: Up, Down, or AdminDn.	AdminDn indicates that the LSP is being taken down gracefully.
Rt	Number of active routes (prefixes) installed in the routing table.	For inbound RSVP sessions, the routing table is the primary IPv4 table (inet.0). For transit and outbound RSVP sessions, the routing table is the primary MPLS table (mpls.0).
Style	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).	This field is used for outbound and transit LSPs only.
Labelin	Incoming label for this RSVP session.
Labelout	Outgoing label for this RSVP session.
LSPname	Configured name of the LSP.
Total	Total number of RSVP sessions displayed for the particular type—ingress (inbound), egress (outbound), or transit).

Monitoring MPLS RSVP Interfaces Information

To view information about the interfaces on which RSVP is enabled, including the interface name, total bandwidth through the interface, and total current reserved and reservable (available) bandwidth on the interface, select Monitor>MPLS>RSVP Interfaces, or enter the following CLI command:

show rsvp interface

Table 110 summarizes key output fields in the RSVP interfaces information display.

Table 110: Summary of Key RSVP Interfaces Information Output Fields

Field	Values	Additional Information
RSVP Interface	Number of interfaces on which RSVP is active. Each interface has one line of output.
Interface	Name of the interface.
State	State of the interface: Disabled—No traffic engineering information is displayed. Down—The interface is not operational. Enabled—Displays traffic engineering information. Up—The interface is operational.
Active resv	Number of reservations that are actively reserving bandwidth on the interface.
Subscription	User-configured subscription factor.
Static BW	Total interface bandwidth, in bits per second (bps).
Available BW	Amount of bandwidth that RSVP is allowed to reserve, in bits per second (bps). It is equal to (static bandwidth X subscription factor).
Reserved BW	Currently reserved bandwidth, in bits per second (bps).
Highwater mark	Highest bandwidth that has ever been reserved on this interface, in bits per second (bps).