Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

VPN Monitoring and Diagnostics

The VPN Module together with the Online Module provides you with VPN monitoring and diagnostics capabilities for a live router network.

Note:

This feature requires the Online Module.

This feature requires the Online Module. First you would need to perform network data collection using the Task Manager . Upon completion of network configuration collection, the program constructs the network model that includes all the configured VPNs in the network.

For a PE router, you may run “show” commands (accessible via the Run CLI... menu by right-clicking on a node in the topology map). Click the arrow next to the Commands list to select a VPN category to view the available CLI commands for VPNs.

To observe the network traffic condition (e.g. between PE and CE), periodic sampling of interface traffic statistics is performed by the Task Manager. The collected interface data can then be accessed in the form or reports and charts. The following figure shows a PE->CE interface traffic chart for router SFO.

Figure 1: PE->CE Interface Traffic Chart (For PE Router SFO)Network traffic chart for interface SFO 10.40.0.1 fe-0/0/2.0 showing egress in blue and ingress in green with spikes up to 50 Mbps.

In the Report Manager, a VPN Interface Traffic report is available under Network Reports > VPN that lets you see the interface traffic for each node of each VPN, as shown in the following figure.

Figure 2: VPN Interface Traffic ReportReport Manager interface for VPN traffic analysis showing selected VPN Interface Traffic report with VPN names, associated nodes, VRF instances, network interfaces, traffic direction, and data metrics.

To verify connectivity and to measure delay and loss, you can also perform VPN diagnostics (e.g., CE-CE Ping and Traceroute) as shown in the following figures.

Figure 3: Ping/trace Route Between Routers from the IP VPN WindowScreenshot of a network tool displaying Layer 3 VPNs, customer groups, and PE devices. Top right panel shows VPN_B details including node names, VRF, interfaces, RD, protocols, and destination IPs. Bottom panel offers Ping and Trace Route tools for diagnostics.

From the right-click menu of the VPNView topology, you can many functions (e.g. path tracing, running CLI commands, and connect to device).

With Java Web Start installed, you may also perform VPN monitoring and diagnostic functions from a web browser, as well as to access VPN-related reports and charts. The following figures are meant illustrate just some of the web features available.

Figure 4: VPN View From the WebWANDL IP/MPLSView screenshot showing VPN_B info including router SFO, VRF VPN-B-TPE3640, Layer 3, route targets, and interface details.
Figure 5: View PE->CE Interface TrafficVPN performance dashboard for VPN_B showing router SFO, VRF VPN-B-TPE3640, Layer 3, ospf/static protocol. Interface details include PE IP 10.0.15.2/30 and CE IP 10.0.15.1/30 with 100 Mbps bandwidth. Graph displays network traffic over time with green for ingress, red for egress, blue and gray for references.
Figure 6: Show PE StatusStatus page for Juniper Networks M5 Router: General chassis info, version 7.2R2.4, CPU 1 percent, memory 15 percent, temp 33C.
Figure 7: Access VPN Summary InformationSummary of VPN_B_ in IP/MPLSView showing PE List, VRF, traffic details, and ping options via Internet Explorer on local network.