8. Troubleshooting9128-A2-GB20-80 September 2002 8-35IP Ping TestAn IP Ping test can be run to test connectivity between the FrameSaver unit andany FrameSaver unit, router, or NMS to which it has a route.Times when you might want to run an IP Ping test are: To test connectivity between the FrameSaver unit and any FrameSaver unit inthe network to verify that the path is operational. SelectIP Ping Test –Procedure 1 on page 8-39 to ping any far-end FrameSaver unit. To verify the entire path between a newly installed remote site FrameSaverunit and the central site NMS. During a remote-site installation, an IP Ping testis typically run from the remote site to ping the NMS at the central site. Theremote FrameSaver unit must have SNMP trap managers configured, and oneof those trap managers must be the central site NMS. SelectIP Ping Test –Procedure 2 on page 8-40 to ping the NMS at the central site. To test the path to the NMS trap managers during installation of the central siteFrameSaver unit. The remote FrameSaver unit must have configured theSNMP trap managers to be sent the ping. SelectIP Ping Test – Procedure 2on page 8-40 to ping SNMP trap managers.Ping Screen Examplemain/test/ping 9128-IIDevice Name: Node A 06/05/2001 06:02IP PINGTarget IP Address: 000.000.000.000Destination Interface: Use Internal Route DLCI: 16 EDLCI: 0Source IP Address: Special 135.90.25.1Encapsulation: RoutedPacket Size: 64Iteration Count: 1Inter-ping Delay (sec): 5Response Timeout (sec): 2Start---------------------------------------------------Status: AliveTransmit Receive Lost Loss RatioPings: 000000 000000 000000 0000 (%)Current Minimum Maximum AverageRoundtrip Delay (ms): 0000 0000 0000 0000--------------------------------------------------------------------------------Ctrl-a to access these functions, ESC for previous menu MainMenu Exit
