Filter
Top Products
8. Troubleshooting
9128-A2-GB20-80 September 2002
8-35
IP Ping Test
An IP Ping test can be run to test connectivity between the FrameSaver unit and
any 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 in
the network to verify that the path is operational. Select
IP 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 FrameSaver
unit and the central site NMS. During a remote-site installation, an IP Ping test
is typically run from the remote site to ping the NMS at the central site. The
remote FrameSaver unit must have SNMP trap managers configured, and one
of those trap managers must be the central site NMS. Select
IP 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 site
FrameSaver unit. The remote FrameSaver unit must have configured the
SNMP trap managers to be sent the ping. Select
IP Ping Test – Procedure 2
on page 8-40 to ping SNMP trap managers.
Ping Screen Example
main/test/ping 9128-II
Device Name: Node A 06/05/2001 06:02
IP PING
Target IP Address: 000.000.000.000
Destination Interface: Use Internal Route DLCI: 16 EDLCI: 0
Source IP Address: Special
135.90.25.1
Encapsulation: Routed
Packet Size: 64
Iteration Count: 1
Inter-ping Delay (sec): 5
Response Timeout (sec): 2
Start
---------------------------------------------------
Status: Alive
Transmit Receive Lost Loss Ratio
Pings: 000000 000000 000000 0000 (%)
Current Minimum Maximum Average
Roundtrip Delay (ms): 0000 0000 0000 0000
--------------------------------------------------------------------------------
Ctrl-a to access these functions, ESC for previous menu M
ainMenu Exit