Customer Service Center

8100 LTE Radio Access

CDMA TDII

If script declares Ping failure, we can test Ping manually to locate the issue:

After establish data connection, unplug LAN cable from Client PC, capture Wireshark logs on Client PC UE port, network emulator and Application Server, then issue Ping command to Application Server manually.

Note:

• There are two routes from Client PC to Application Server – one is 192.168.0.61, the other is air interface. With LAN cable on Client PC, ping command maybe through LAN “Local Area Connection”, not air interface. We should ensure Ping is through air interface, thus always unplug the LAN cable during manual test.
• Pay attention to the reply time: air interface reply time always >10ms, LAN reply time always <1ms. This way we also know the ping is through air interface or LAN.

If manual Ping works, this is system issue.

If manual Ping fails, continue to debug as below:

• Check Client PC UE port Wireshark log, if there's no Ping Request, means UE doesn't send out Ping Request, this is UE issue.
• If UE sends Ping Request, but Application Server doesn't receive Ping Request or Application Server doesn't reply Ping Response, this is system issue. We can check network emulator Wireshark log to see which node lost Ping packets.

For more infomation on Ping routes between Spirent racks, refer to FAQ13855.