PTN 3900s are used for deployment in an office. The networking at the core layer is A-B-C-D-E-F-A. The iManager U2000 V100R002C01SPC002 is used for equipment management. The software version of the PTN 3900 is 5.59.02.34. The versions of the ExtBIOS and BIOS are 9.24.43 and 8.24.21 respectively.
After tunnels are configured on the U2000, the LSP status is displayed as Local Available after query on both sides. After configuring a PWE3 service, a user right-clicks the service and chooses Manage PWE3 Service > Ethernet OAM > LB Test from the shortcut menu, and then clicks Run to perform a loopback (LB) test. When the progress reaches 100%, the user queries the number of transmitted packets and number of received packets in LB Statistic Information and finds that the number of received packets is zero.
In the NE Explorer, the user chooses MPLS Management > PW Management and sets OAM Status to Enable in PW OAM Parameter (the same operation is performed on the peer NE). The User right-clicks PW data, chooses Query OAM Status from the shortcut menu, and finds that Local Working Status is displayed as Local Available and Remote Working Status is displayed as Remote Available. It seems that the PW service is available. Nevertheless, different conclusions are obtained after the same PW service is tested.
Start the U2000 System Monitor. Switch to the U2000 server processes, locate PTN NE Manager_2924 in Process Monitor, and end and restart the process.
Restart the U2000 client, right-click a PWE3 service, choose Manage PWE3 Service > Ethernet OAM > LB Test from the shortcut menu, and then click Run. When the progress reaches 100%, view the number of transmitted packets and number of received packets in LB Statistic Information. It is found that the number of transmitted packets equals the number of received packets and the fault is rectified.
This fault can be rectified thoroughly after the U2000 is upgraded from V100R002C01SPC002 to V100R002C01SPC003.
Engineers query and confirm that the transmission link is available on the radio network controller (RNC) side and can ping equipment on the NodeB side successfully. It can be determined that the service is configured correctly. The possible cause is U2000 functions.