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 showing egress and ingress bps over time for interface SFO 10.40.0.1 fe-0/0/2.0 with periodic spikes.

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 ReportVPN traffic report interface with a tree menu focusing on VPN Interface Traffic, a table showing VPN names, nodes, VRF, interfaces, and traffic data, plus toolbar and filtering options.

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 WindowNetwork management tool interface for IP VPNs showing hierarchy tree with categories like Layer3 VPN, customer groups, diagnostic panel for VPN_B with node names SFO and ATL, VRF details, and ping-trace route tools.

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 network management tool showing VPN_B details for routers and interfaces. Admin logged in with version 4.4.0.
Figure 5: View PE->CE Interface TrafficNetwork monitoring dashboard showing VPN_B connection details: Router SFO, VRF VPN-B-TPE3640, Layer 3, Route Distinguisher 1080:2, Protocol ospf/static. Interface details: PE re-0/0/0.0, PE IP 10.0.15.2/30, CE TPE3640, CE IP 10.0.15.1/30, Bandwidth 100.000M. Graph visualizes network traffic over time with lines for egress and ingress bps. Date Apr. 13.
Figure 6: Show PE StatusJuniper Networks router status: System Name SFO, CPU usage 1 percent, Memory usage 15 percent, Operating Temperature 33 degrees Celsius.
Figure 7: Access VPN Summary InformationWANDL IP/MPLSView interface showing VPN management with selected VPN_B_ details including PE List ATL and SFO and VRF VPN-B-NMX and VPN-B-TPE3640.