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

    Viewing Service-Level Alarms

    The Junos Space Network Application Platform has integrated a third party tool, OpenNMS, to provide network monitoring capabilities. The OpenNMS network management application platform provides solutions for enterprises and carriers. OpenNMS is installed as part of Platform, which exposes some of OpenNMS’ functionality through the Network Monitoring workspace. The default performance management configuration of OpenNMS for Space supports generic counters, CPU, memory, temperature, and Mobility counters. For information on this default configuration, see the subset of the OpenNMS documentation included in this Junos Space Network Application Platform User Guide.

    Caution: Although additional OpenNMS functionality can be accessed by customizing its XML files, editing these files can affect the functionality of the Network Monitoring workspace. Juniper Networks does not support changes to OpenNMS.

    When certain types of events are persistent, or when the condition causing the event crosses a threshold, SNMP sends a notification, also called a trap to Connectivity Services Director. Connectivity Services Director correlates traps, describing a condition, into an alarm .SNMP also plays another role in Connectivity Services Director. Enabling devices for SNMP with the appropriate read-only V1/V2/V3 credentials, can speed up device discovery.

    To access the alarms page for a particular service:

    1. From the View selector, select Service View. The workspaces that are applicable to routing and tunnel services are displayed.
    2. From the Service View pane, which is the left pane in the window, click the plus sign (+) next to Network Services to expand the tree and display the different service types that you can configure.
    3. Click the plus sign (+) beside Connectivity to view services based on protocols.
      • Expand the L3VPN Services tree to select a Layer 3 VPN Ethernet service.

      • Expand the P2P Services tree to select a point-to-point service.

      • Expand the VPLS Services tree to select a VPLS service.

    4. From the task pane, select Service Provisioning > Deploy Services. The top part of the right pane displays the Manage Network Services page, with the table of services, and the bottom part of the right pane displays the Manage Service Deployment page, with the table of service orders.
    5. From the Manage Network Services page, select the check box next to the service for which you want to view alarms.

      Tip: In Build mode of Service View, from the View pane, if you select the Network Services node and do not expand the Network Services > Connectivity tree, the top pane displays a pie chart that enables you to view and examine the different services configured for devices, and the types of service protocols configured. The Services by Type graph displays the count of services for each type of service definition. Mouse over each segment of the pie to view the number corresponding to the percentage of service orders for each of the charts. This chart provides a visual overview of customers and service orders on your network, and enables you to quickly access related and commonly needed information. For example, you can check for failed service orders and then access a list of failed requests so you can begin to take restoration measure.

      The top pane displays information about the services that have been previously created, such as the name of the service, the functional audit status, the performance management status, and the status of the service. You can modify the properties of the service, conduct a functional or configuration audit, force-deploy or deactivate the service, and view alarms associated with a particular service order for debugging and corrective action. Services can be in one of the following service states:

      • Completed—The service order has been successfully deployed.

      • Scheduled for deployment—The service provisioner has scheduled the service order for deployment.

      • Deployment Failed—An attempted service deployment was not successfully completed or failed an audit.

      • In Progress—The Connectivity Services Director application is in the process of deploying the service.

      • Requested—The service provisioner has created the service order, but has not yet attempted to deploy it or schedule it for deployment.

      • Invalid—The service order is not valid.

    6. Click the View Alarms button. You are navigated to the Alarms page in Fault mode. See Alarm Detail Monitor (Service View) for more information.

    Modified: 2015-09-21