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

    Understanding How to Monitor Customers in the Service Provider Workspace

    The subtasks under the Monitoring task group enable you to monitor network statistics, audit devices connected to cCPE access links, and view traffic usage graphically on a per-customer basis.

    From the Monitoring task group, you can set up the following tasks:

    • Perform functional audits
    • Monitor the status of your cCPE customers
    • View historical data
    • Monitor active devices

    Functional Audit Overview

    The Functional Audit task enables you to verify the connectivity between different cCPE customer sites. A functional audit verifies that a site is reachable by sending a series of pings from the source site’s access links to the destination site’s access links. You can select multiple sites for both the source and destination sites. The destination site does not send any pings. A site cannot ping itself, and the functional audit cannot be used if a customer has only one site.

    Figure 1 shows an example of a Functional Audit page.

    Figure 1: Example-Functional Audit Page

    Example-Functional Audit Page

    To perform a functional audit, select the customer from the Customer selection list, then select the source and destination sites between which you want to test the connectivity. The job for the functional audit is placed in Junos Space Network Management Platform Jobs queue. When the audit completes, the results display the following information:

    • Source access links that were tested
    • Destination access links that were tested
    • Connection status (up or down)
    • Percentage of packets dropped
    • Round trip time measured in milliseconds (ms)
    • Time the audit was scheduled

    If the connection status is down, or if one of the access links is configured incorrectly, the percent dropped is 100 and the round trip time is N/A. The system keeps a record of the last 10 scheduled audits. After performing 10 audits, the system drops information for the oldest audit after a new audit is performed. When you schedule a functional audit it is added to the Jobs queue. If the job fails, a failure message is displayed. Error messages differ depending on whether you are running cCPE Selfcare Application on Junos Space Network Management Platform or whether you have integrated cCPE Selfcare Application APIs with your OSS. Error messages are described in Table 1 and Table 2.

    Table 1: Job Failure Messages When Running cCPE Selfcare Application on Junos Space Network Management Platform

    Error Message

    Meaning

    Error when attempting to gather information of provided sites

    System was unable to gather and verify the site information for the selected source and destination sites.

    No links given to ping

    Destination site has no access links.

    The origin site has no access links

    Source site has no access links.

    Job failure on pinging access link access-link-name

    A ping was attempted, but an error occurred that stopped the job from succeeding. This error can occur if Junos Space Network Management Platform does not receive a response from the device or because the system was unable to add the result to the database.

    Job failure on pinging access links and updating job progress

    System tried to update the progress of the job, but failed.

    Job failure on setting up job

    System tried to get the customer and source site information from the database but failed, or the system was unable to reach the job manager. This error occurs prior to any pings being attempted.

    Table 2 describes the job failure messages if you integrate your OSS with cCPE Selfcare Application APIs.

    Table 2: Job Failure Messages When Using OSS and cCPE Selfcare Application APIs

    Error Message

    Meaning

    Error when attempting to gather information of provided sites

    System tried to check the provided sites, or when the system tried to retrieve a list of sites from the database, an error occurred. This error can occur if the sites you provided do not belong to the customer, or you did not provide an ID for every site.

    No links given to ping

    Destination site has no access links.

    The origin site has not access links

    Source site has no access links.

    Job failure on pinging access link access-link-name

    Ping was attempted, but an error occurred that stopped the job from succeeding. This error can occur if the OSS does not receive a response from the device or because the system was unable to add the result to the database.

    Job failure deleting old audits

    System tried to delete the older audits, but failed. In this case the new audits are added to the database, but the older audits remain.

    Job failure on pinging access links and updating job progress

    System tried to update the progress of the job, but failed.

    Job failure on setting up job

    System tried to retrieve the customer and source site information from the database but failed, or the system was unable to reach the job manager. This error occurs prior to any pings being attempted.

    Status Monitoring Overview

    The Status Monitoring task enables you to select a cCPE customer and a site and display traffic information for all access links associated with the site. The counters displayed are retrieved directly for the devices managed by Junos Space Network Management Platform and associated with the selected customer and site.

    Figure 2 shows an example of the Status Monitoring page.

    Figure 2: Example-Status Monitoring Page

    Example-Status Monitoring Page

    Historical Data Overview

    This Historical Data task enables you to select a cCPE customer and a site and generate various charts that show the customer data on the access link associated with the site. You can choose which graphical format you want to use to display this data based on the MIB selection and time interval for the graphed data. Charts are retrieved from OpenNMS in Junos Space Network Management Platform.

    Figure 3 shows an example of the Historical Data page.

    Figure 3: Example-Historical Data Page

    Example-Historical Data Page

    Active Devices Monitoring Overview

    The Active Devices Monitoring task enables you to select a cCPE customer and a site and view the MAC and IP addresses of client devices that are active in the network connected by the access link. This information is stored in the Address Resolution Protocol (ARP) tables of the device and retrieved through Junos Space Network Management Platform.

    Figure 4 shows an example of the Active Devices Monitoring page.

    Figure 4: Example-Active Devices Monitoring Page

    Example-Active Devices Monitoring
Page

    The Active Devices Monitoring page displays three columns:

    • Access link — Name of the access link.
    • IP address — IP address of the device.
    • MAC address — MAC address of the device.

    In the example shown in Figure 4, the access link called Primary is connected to a network with multiple client devices, each device has a unique IP address and MAC address. If no active clients are using the access link, there may be no information in the device’s ARP table and the results display No data found. If the application encounters an error, or is unable to reach the client device, the results display Problems accessing router configuration.

    Modified: 2015-11-09