Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Monitoring the Service Transport Details of Layer 3 VPN 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.

    Note: 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 L3VPN service:

    1. Select Service View from the View Selector.

      The workspaces that are applicable to routing and tunneling services are displayed on the View pane.

    2. 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.

    3. 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.

    4. Click the plus sign (+) beside Connectivity to view services based on protocols.

      The Connectivity tree is expanded and displayed on the View pane.

    5. Expand the L3VPN Services tree to select a Layer 3 VPN Ethernet service.
    6. Click the ServiceTransport tab.

      The Service Transport page is displayed.

    This widget provides details on Summary Monitors, which are shown in Service Summary Tab under Monitor functionality of “Service View”.

    Figure 1 shows the Service Transport tab for an L3VPN service.

    Figure 1: Service Transport Page for an L3VPN Service

    Service Transport Page for
an L3VPN Service

    Transport Statistics

    The Transport Statistics monitor shows the statistical counts for the selected data against time between the source device and the specified peer or destination device, and the LSP being used by the endpoint. The source device is the row selected in the Connection Matrix widget. The destination device is based on the device that you chose in the Traffic Statistics widget. By default, destination devices are empty. This monitor is valid for P2P services. A line graph is displayed with time on the horizontal axis and the type of statistical parameter on the vertical axis. In the Peer Device list, all Devices from the Connection Matrix except the source device are available for selection. In the Statistics Type list, you can select Ingress Packets or Ingress Bytes. Color-coded legends are used to indicate tunnel and device traffic. The purple line denotes tunnel traffic and the brown line signifies the device (service) traffic. Because the LSP does not provide any metric if it is down, there might be variations in the data point for the LSP and device.

    VPN Routes

    This widget displays information about the path through which the packets traverse in LSPs in a VPN tunnel. Select a node for which you want to view the VPN routing information from the Select Node list at the top of the monitor. Alternatively, enter the name of the node for which you want to view the VPN routing details as the match criterion in the Search box and click the Search icon. The page refreshes to display the nodes that match with the search criterion. Click Refresh to update the contents of the table.

    • Destination— Destination (egress routing device) of the session

    • Next Hop— 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

    • LSP/Label— Name of the LSP. For LDP signaling, NA is shown.

    Label/LSP Information

    Label Information

    For a destination address that you select in the VPN Routes monitor that contain LDP-established LSPs, the corresponding label details for active and backup LSPs are displayed in this monitor. The following fields are displayed:

    • Protocol—LDP is the mechanism used to establish LSPs

    • Next-hop—Network layer address of the directly reachable neighboring system.

    • via—Interface used to reach the next hop. If there is more than one interface available to the next hop, the name of the interface that is actually used is followed by the word Selected. This field can also contain the following information:

      • Weight—Value used to distinguish primary, secondary, and fast reroute backup routes. Weight information is available when MPLS label-switched path (LSP) link protection, node-link protection, or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight value is preferred. Among routes with the same weight value, load balancing is possible.

      • Balance—Balance coefficient indicating how traffic of unequal cost is distributed among next hops when a routing device is performing unequal-cost load balancing. This information is available when you enable BGP multipath load balancing.

    • Label Operation—MPLS label and operation occurring at this routing device. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label).

    • Label TTL Action—State of the TTL propagation attribute, such as prop-ttl (propagate the TTL value), prop-ttl (top) (propagate the TTL value of the outermost or top label), no-prop-ttl (do not propagate the TTRL value), or no-prop-ttl (top) (do not transmit the TTL value of the top label)

    • Load Balance label—Whether the load-balancing capability based on labels is enabled.

    LSP Information

    For a destination address that you select in the VPN Routes monitor that contain 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 Connection 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.

    Modified: 2017-07-20