ON THIS PAGE
Monitoring the Service Transport Details of E-Line Services for Easy Analysis
You can view the Service Transport page of a particular service to obtain detailed and granular information on the high-level statistics that are displayed on the Service Summary page. The VPN routes learned by a provider edge (PE) device from all other PE devices are displayed. The PE routers in the provider’s core network are the only routers that are configured to support VPNs and hence are the only routers to have information about the VPNs. From the point of view of VPN functionality, the provider (P) routers in the core—those P routers that are not directly connected to CE routers—are merely routers along the tunnel between the ingress and egress PE routers. The accounting information about configured and active label-switched paths (LSPs) is also displayed. 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.
The values and statuses of the parameters displayed in the graphs and tables of different widgets are refreshed, based on the polling interval configured on the Monitoring tab of the Preferences page (accessible by clicking the down arrow beside the System button on the Connectivity Services Director banner and selecting Preferences).
To view the Service Transport page for an E-Line service:
Select Service View from the View Selector.
The workspaces that are applicable to routing and tunneling services are displayed on the View pane.
From the Junos Space user interface, click the Monitor icon on the Connectivity Services Director banner.
The functionalities that you can configure in this mode are displayed on the task pane.
From the Service View pane, on the left, click the plus sign (+) next to Network Services to expand the tree and display the different service types that you can configure.
The Network Services tree is expanded and displayed on the View pane.
Click the plus sign (+) beside Connectivity to view services based on protocols.
The Connectivity tree is expanded and displayed on the View pane.
Expand the E-Line Services tree to select an E-Line service.
Click the ServiceTransport tab.
The Service Transport page is displayed.
Connections
This monitor shows the status of connections between peer devices. In the tabular view, the row represents the source device and the columns denote the neighboring and destination devices. This monitor is applicable for E-Line services. A green up-arrow in the indicates that the adjoining device in the network path to the destination device is operationally up. A red down-arrow indicates that the device is down. For the device for which the connection status is displayed, a value of NA is displayed under its own corresponding column to denote that it is not applicable.
LSP Information
For a destination address that contains LSP names, the corresponding LSP details, such as the name, state, and bandwidth of the LSP, are displayed in this monitor. The details displayed in this monitor depend on the device selected in the Connections Matrix widget. The following fields are displayed:
Name— Name of the LSP
State— State of the LSP handled by this RSVP session: Up, Dn (down), or Restart
Bandwidth—Specifies the bandwidth in bits per second for the LSP.
Primary State— State of the LSP that is a primary path: Up, Down, or Restart
Secondary State— State of the LSP that is a secondary path: Up, Down, or Restart
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:
0x01—Local protection available. The link downstream from this node is protected by a local repair mechanism. This flag can be set only if the Local protection flag was set in the SESSION_ATTRIBUTE object of the corresponding Path message.
0x02—Local protection in use. A local repair mechanism is in use to maintain this tunnel (usually because of an outage of the link it was routed over previously).
0x03—Combination of 0x01 and 0x02.
0x04—Bandwidth protection. The downstream routing device has a backup path providing the same bandwidth guarantee as the protected LSP for the protected section.
0x08—Node protection. The downstream routing device has a backup path providing protection against link and node failure on the corresponding path section. If the downstream routing device can set up only a link-protection backup path, the Local protection available bit is set but the Node protection bit is cleared.
0x09—Detour is established. Combination of 0x01 and 0x08.
0x10—Preemption pending. The preempting node sets this flag if a pending preemption is in progress for the traffic engine LSP. This flag indicates to the ingress legacy edge router (LER) of this LSP that it should be rerouted.
0xb—Detour is in use. Combination of 0x01, 0x02, and 0x08.
Total Packets—Total number of packets and Total number of bytes transmitted over the LSP. This counter is reset to zero whenever the LSP path is optimized (for example, during an automatic bandwidth allocation).
Total Bytes—Total number of bytes transmitted over the LSP. This counter is reset to zero whenever the LSP path is optimized (for example, during an automatic bandwidth allocation).
LSP Traffic
This widget displays a line chart with the bytes per second (bps) or rate on the y-axis and time on the x-axis to denote the LSP bandwidth utilization in bps.
From the Time Interval drop-down box, select 1 Hour, 8 Hours, 1 Day, 1 Week, 1 Month, 3 Months, 6 Months, 1 Year, or Custom to specify the duration for which the data polled from devices needs to be displayed. If you select the Custom option, the Time range popup dialog box is displayed. Specify the date from the calendar, and select the Time From (Start time in the 24-hour time format of collection of data), and Time To (End time in the 24-hour time format of collection of data). Click OK to save the settings. Else, click Cancel to discard the configuration.