About Monitor Mode in Service View of Connectivity Services Director

Monitor mode in Connectivity Services Director provides you visibility into the transmission of packets between peer devices, health and traffic-handling capacity, and consolidated statistical details of important packet metrics based on the services configured. The Connectivity Services Director application monitors its managed services on devices and maintains the information it collects from the devices in a database. Monitor mode displays this information in easy-to-understand graphs and in tables that you can sort and filter, allowing you to quickly visualize the state of your network, spot trends developing over time, and find important details.

Quick Access to Important Troubleshooting Details

The main purpose and benefit of monitoring functionalities is to allow the operators to quickly monitor the health (working condition), operating efficiency, traffic-handling capacity, and performance status of the managed devices and configured services. Several monitors or widgets are displayed to enable you to track, diagnose, and rectify problems and discrepancies associated with services configured on devices. For example, you might observe that an L3VPN service is reported as down from the summarized information presented for that service on the monitoring page. This high-level view enables you to navigate to the settings for that service and tune them properly to function properly.

Performance Monitoring

You can employ the ITU-T Y.1731 standard-compliant Ethernet loss measurement (ETH-LM), Ethernet synthetic loss measurement (ETH-SLM), and Ethernet delay measurement (ETH- DM) capabilities to analyze and examine the operating efficiency and performance status. These performance monitoring functionalities can be run for E-Line and E-LAN services. You can start and stop the collection of performance monitoring statistics on the services that you want to monitor. The retrieval and computation of statistical details are performed using SNMP MIBs.

View and Clear Interface Information

You can view the learned MAC address information for a device associated with a particular service, the interface statistical counters and metrics, and the status of an interface. The functionalities available in Monitor mode of Service View are equivalents to the operational commands you can run from the Junos CLI interface to view interface information or MAC address details. You can also clear the interface statistics maintained on a device.

View Interface Status

You can view the interface status to monitor interface bandwidth utilization and traffic statistics on the device. When you view the interface status for a particular service, all the interfaces configured on the different devices associated the service are retrieved and displayed.

View Routing Table

The Routing Table window enables you view the routing table information for the selected virtual routing instance. For L3VPN services, you can determine which LSPs or tunnels are being used by looking at the routing tables.

View MAC Table

You can view the learned MAC address information for a device associated with a particular service. You can manage MAC entries more efficiently by viewing the configured aging time for a MAC entry, which is the maximum time that an entry can remain in the MAC address table before it is deleted because it has reached its maximum age

Traceroute for an MPLS LSP

You can perform a traceroute operation to examine the network reachability and identify connection failures from a source or ingress host to a remote host for an MPLS LSP signaled by RSVP. It a debugging tool to locate MPLS label-switched path (LSP) forwarding issues in a network. (Currently supported for IPv4 packets only.)

MPLS Ping

You can use the MPLS ping application to examine the network reachability and identify any broken links for diagnostic purposes. In IP networks, the ping and traceroute functionalities enable you to verify network connectivity and find broken links or loops. In MPLS-enabled networks, you can use the ping capability to determine whether IP connectivity exists to a destination even when the ping packets must traverse multiple LSPs.