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

    Performing a Functional Audit

    A functional audit determines whether a deployed service instance is functioning. It checks the control plane to ensure connectivity among endpoints and that the UNIs are functioning correctly. It also checks the data plane to verify packet transmission between each valid pair of endpoints in the service.

    The functional audit provides both a CLI verification and a troubleshooting feature that allows you to check the status of interfaces, LDP sessions, neighbor links, and endpoints of point-to-point services. The Functional Audit tab on the Functional Audit Results window displays information about the service statistics for the link you are monitoring. The Troubleshooting tab displays status of the interfaces, LDP sessions, neighbor links, and endpoints.

    Performing the Functional Audit

    To perform a functional audit:

    1. In the Network Activate task pane, select Service Provisioning > Manage Services to display the Manage Services inventory page.
    2. On the Manage Services page, select the service you want to audit.
    3. Right-click a service or open the Actions menu to display the list of possible functions.

      Select Perform Functional Audit. From the Monitoring window you may choose either the functional audit or troubleshooting.

    4. In the Schedule Functional Audit dialog box, do one of the following:
      1. Select Audit Now, then click OK.

        The Job Details dialog box appears for you to click the Job ID link to see the functional results. The Job Management page displays the functional audit details by job ID, name, percentage complete, state, job type, summary, scheduled start time, user, and recurrence.

      2. Select Audit Later, enter a date and time, then click OK.

        To monitor the progress of an audit after selecting Audit Later, after the scheduled time of the audit:

        1. In the Network Activate task pane, select Jobs.
        2. On the Jobs statistics page, select the Functional Audit segment of the Job Types pie chart.

          The Job Management page appears filtered by functional audit jobs.

        3. Select the functional audit job that you want.

          Summary information about the audit appears in the quick look panel.

        4. In the filter bar, select the table view icon to see additional information about the job. If the service failed the audit, information about the failure appears in the Summary field.
    5. Click the Job ID link in the Audit Information window. The Job Management page shows information about the functional audit job.

      The State field indicates whether the service passed or failed the audit. If the service failed the audit, then the Summary field provides information about the failure.

    6. To view additional details about the functional audit, including results from checking the control plane and the data plane, see Viewing Functional Audit Results .

    CLI Verification

    The CLI verification feature of a functional audit works by running commands that perform verification and reporting relevant information.

    The following table shows the commands that are used for each service type.

    XML Commands

     

    CLI Commands

     

    Service Type/

    Device Type

    Control Plane

    Data Plane

    Control Plane

    Data Plane

    ELINE Martini/

    M Series and MX Series

    <get-l2ckt-connection-information>

    <neighbor>neighborIP</neighbor>

    <interface>interfaceName </interface>

    </get-12-ckt-connection-information>

    <request-ping-l2circuit-virtual-circuit>

    <neighbor>neighborIP</neighbor>

    <virtual-circuit-id>VCID</virtual-circuit-id>

    </request-ping-l2circuit-virtual-circuit>

    show l2circuit connections neighbor neighborIP interface interfaceName

    show ppp interface mlppp group1 members

    ping mpls l2circuit virtual-circuit VCID neighbor neighborIP

    Where:

    neighborIP = Address of remote neighbor

    VC ID = Virtual Circuit ID

    interfaceName = Name of interface

    BX Series

    Not supported.

    <get-l2circuit-information> <l2circuit-name> name<l2circuit-name> <brief/> </get-l2circuit-information>

    Not supported.

    show l2circuit name brief

    Where:

    Name = name of the l2 circuit ID

    VPLS/

    M Series

    <get-vpls-connection-information> <instance> routing_instance_name

    </instance> <local-site> local-siteID </local-site> <remote-site> remote-siteID

    </remote-site> </get-vpls-connection-information>

    <request-ping-vpls-instance> <instance-name> routing_instance_name

    </instance-name> <destination-mac> destMacValue

    </destination-mac> <source-ip> sourceIp

    </source-ip> <learning-vlan-id> learning-vlan-id

    < /learning-vlan-id> </request-ping-vpls-instance>

    show vpls connections instance routing_instance_name local-site local-siteID remote-site remote-siteID

    ping vpls instance routing_instance_name destination-mac destMacValue source-ip sourceIpValue learning-vlan-id learningVlanID

    Where:

    routing_instance_name = Routing instance name

    destMacValue = Destination MAC address

    sourceIP = Source IP address

    local-SiteID = Name or ID of VPLS local site

    remote-SiteID = ID of VPLS remote site

    learning-vlan-id = Learning VLAN identifier

    L3VPN/

    Junos

    <get-route-information> <table> bgp.l3vpn.0</table> <rd-prefix>destinationRDprefix</rd-prefix> </get-route-information>

    <ping><routing-instance> routingInstanceValue </routing-instance> <count>5 </count>

    show route table bgp.l3vpn.0 rd-prefix destinationRDprefix

    ping routing-instance routiingInstanceValue count

    Where:

    routingInstanceValue = Routing instance name

    destinationRDprefix = Route Distinguisher: remote UNI IP address

    destinationUniInterfaceIP = Destination UNI IP address

    For the data plane, the Junos Space software places a static MAC address in the forwarding table of the remote endpoint, which it uses to verify correct packet transfer.

    Note: Data plane validation of a VPLS service works for MX Series devices running Junos Release 9.4 or later. If the service under audit contains an M Series device or an N-PE device running Junos Release 9.2 or 9.3, the functional audit does not complete successfully and generates a message stating that functional audit is not supported on that platform.

    The following table shows the commands for VPLS service type:

    Service Type

    Device Family

    XML Commands

    CLI Commands

    Category

    VPLS

    M Series

    <get-vpls-connection-information> <instance>instanceValue</instance> </get-vpls-connection-information>

    show vpls connection instance instanceValue

    Route

    <get-mpls-lsp-information> <ingress/> </get-mpls-lsp-information>

    show mpls lsp ingress

    MPLS

    <get-mpls-lsp-information> <egress/> </get-mpls-lsp-information>

    show mpls lsp egress

    MPLS

    <get-mpls-static-lsp-information> <ingress/> </get-mpls-static-lsp-information>

    show mpls static-lsp ingress

    MPLS

    <get-rsvp-session-information> </get-rsvp-session-information>

    show rsvp session

    Route

    <get-route-information> <table>inet.3</table> </get-route-information>

    show route table inet.3

    Route

    <get-interface-information> <terse/><interface-name>interfaceValue</interface-name> </get-interface-information>

    show interface interfaceValue terse

    UNI

    <get-interface-information> <statistics/> <interface-name>interfaceValue</interface-name> </get-interface-information>

    show interface interfaceValue statistics

    UNI

    <get-route-information> <table>instanceValue</table> <protocol>bgp</protocol> </get-route-information>

    show route protocol bgp table instanceValue.l2vpn.0

    Route

    Where:

    instanceValue= Name of the service

    neighborIP= Address of the remote neighbor

    interfaceValue= Name of the interface

      
       

    The following table shows the commands for L3VPN service type:

    Service Type

    Device Family

    XML Commands

    CLI Commands

    Category

    L3VPN

    M Series

    <get-mpls-lsp-information> <ingress/> </get-mpls-lsp-information>

    show mpls lsp ingress

    MPLS

    <get-mpls-lsp-information> <egress/> </get-mpls-lsp-information>

    show mpls lsp egress

    MPLS

    <get-interface-information> <terse/> <interface-name>interfaceValue</interface-name> </get-interface-information>

    show interfaces instancevalue.initvalue terse

    Route

    <get-forwarding-table-information> <vpn>instance </vpn> </get-forwarding-table-information>

    show route forwarding-table vpn instance

    Route

    <get-rsvp-session-information> </get-rsvp-session-information>

    show rsvp session

    Route

    <get-interface-information> <statistics/> <interface-name>instance</interface-name> </get-interface-information>

    show interfaces instance statistics

    UNI

    <get-mpls-static-lsp-information> <ingress/> </get-mpls-static-lsp-information>

    show mpls static-lsp

    MPLS

    <get-ospf-neighbor-information> </get-ospf-neighbor-information>

    show ospf neighbor

    Route

    <get-route-information> <table>bgp.l3vpn.0 </table> <rd-prefix>destinationRDprefix</rd-prefix> </get-route-information>

    show route table bgp.l3vpn.0

    Route

    <get-lacp-interface-information>
    <interface-name>
    lagInterface
    </interface-name>
    </get-lacp-interface-information>

    show lacp interfaces

    UNI

    <get-mc-ae-interface-information>
    </get-mc-ae-interface-information>

    show interfaces mc-ae

    UNI

    <get-inter-chassis-control-protocol-information>
    </get-inter-chassis-control-protocol-information>

    show iccp

    UNI

    <get-vrrp-interface-information>
    <interface-name>
    lnterface
    </interface-name>
    </get-vrrp-interface-information>

    Show vrrp interfaceName

    UNI

    <get-bridge-instance-information>
    <bridge-domain-name>
    domainName
    </bridge-domain-name>
    </get-bridge-instance-information>

    Show bridge domain domainName

    UNI

    Where:

    instanceValue= Name of the service

    neighborIP= Address of the remote neighbor

    interfaceValue= Name of the interface

     

    Troubleshooting Point-to-Point Service

    From the Troubleshooting tab you can check status of the interfaces, LDP sessions, neighbor links, and endpoints of a point-to-point service. To select the status you want to check, click on the device from the device list on the left, and select the show command from the Command list. This figure shows the routing table for the selected device in the Point-to-Point service.

    The following figure shows the interface status window. The status shows that the interface is up.

    The following figure shows the status of the LDP session for the selected device.

    The following figure shows the LDP neighbor status.

    Troubleshooting VPLS Service

    From the Troubleshooting tab you can check status of the interfaces, LDP sessions, neighbor links, connection instances, and endpoints of a VPLS service. To select the status you want to check, click on the device from the device list on the left, and select the show command from the Command list. This figure shows the routing table for the selected device in the VPLS service.

    Troubleshooting L3VPN Service

    From the Troubleshooting tab you can check status of the interfaces, LDP sessions, neighbor links, and endpoints of a L3VPN service. To select the status you want to check, click on the device from the device list on the left, and select the show command from the Command list. This figure shows the routing table for the selected device in the L3VPN service.

    Modified: 2017-02-02