To verify the end-to-end connectivity of a service using Service Site Ping

Steps

Choose Tools→Service Test Manager (STM) from the NFM-P main menu. The Manage Tests form appears.

Click Create.

Choose Service→Create Service Site Ping from the Create contextual menu. The Service site ping (Create) form appears.

Note: You must use the Service Site Ping diagnostic to test the service in both directions for the connection.

Configure the required parameters for the diagnostic session and run the diagnostic.

The originating service tunnel for the Service Site Ping is from site ID 10.1.200.51/32 to site ID 10.1.200.53/32, the other end of the service using the network in Figure 6-1, Sample network.

Click on the Results tab to view the list of trace responses. Double-click on a row in the list to view its details.

Review the diagnostic results and assess whether the configuration meets the network requirements. The table below lists the displayed messages.

Table 6-3: Service Site Ping OAM diagnostic results

Displayed message	Description
Sent - Request Timeout	The request timed out with a reply.
Sent - Request Terminated	The request was not sent because the diagnostic was terminated by the operator.
Sent - Reply Received	The request was sent and a successful reply message was received.
Not Sent - Non-Existent Service-ID	The configured service ID does not exist.
Not Sent - Non-Existent SDP for Service	There is no SDP for the service tested.
Not Sent - SDP For Service Down	The SDP for the service is down.
Not Sent - Non-Existent Service Egress Label	There is a service label mismatch between the originator and the responder.

If the Service Site ping passes, the routes between the two sites are complete and in an operational state. If the MAC Ping performed in To verify connectivity for all egress points in a service using MAC Ping and MAC Trace failed:
1. Investigate the status of the two SAPs used for the circuit.
2. Correct the configuration issue related to the SAPs, if required.
  
  If there is no configuration problem with the SAPs, the service problem is related to the MAC addresses.
  The MAC address problem could be caused by the:
  - ACL MAC filter excluding the required MAC address
  - external customer equipment
If the Service Site Ping fails, there is a loss of connectivity between the two sites.
1. Log in to one of the sites using the CLI.
2. Enter the following command:
  
  ping <destination_site_ip_address> ↵
  
  where <destination_site_ip_address> is the address of the other site in the route
  
  If the CLI IP ping passes, go to Stage 7 b 2 of Workflow to troubleshoot a service or connectivity problem.

Use the CLI to verify that the IP address of the destination site is in the routing table for the originating site by entering:

show router route-table ↵

If the IP address for the destination site is not in the routing table for the originating site, there is an L3 or L2 problem.

Verify that the appropriate protocols are enabled and operational on the two sites.
Verify the administrative and operational states of the underlying L2 equipment, for example, ports and cards.

If the service problem persists, another type of service problem may be present. Perform the steps Workflow to troubleshoot a service or connectivity problem.

If the troubleshooting workflow does not identify the problem with your service, contact your technical support representative; see Chapter 1, NSP troubleshooting overview.

End of steps