Filter
Top Products
8. Troubleshooting
8-24 December 2002 9700-A2-GB20-20
IP Ping Test
An IP Ping can test connectivity between the management data path and the
FrameSaver unit and any FrameSaver unit, router, or NMS to which it has a route.
In addition, the test can be run to access a remote unit for configuration purposes.
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
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-29 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-29 to ping SNMP trap managers.
Ping Screen Example
main/test/ping 9783-C-SLV
Device Name: Node A 09/11/2002 06:12
IP PING
Target IP Address: 000.000.000.000
Destination Interface: Use Internal Route DLCI: 100 (Net1-ATM 15,255)
Source IP Address: Special 135.90.25.1
Encapsulation: Routed
TOS Byte User Defined 001101
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 MainMenu Exit