Paradyne FrameSaver DSL, 9783 manual Procedure

Models: FrameSaver DSL 9783

1 233
Download 233 pages 22.17 Kb
Page 163
Image 163

Troubleshooting

"Procedure 2

To ping the NMS at the central site:

1.Verify that the central site NMS has the FrameSaver unit's IP address in its routing table so it can communicate with the FrameSaver unit.

2.Verify that the central site NMS's router has the FrameSaver unit's IP address in its routing table so it can communicate with the FrameSaver unit.

3.Verify that the central site NMS has been configured as an SNMP Trap Manager if the router is to route data, so a route has been configured within the FrameSaver unit.

Main Menu Configuration Management and Communication SNMP Traps

Or, for a local DLCI between the central site FrameSaver unit and its router, verify that a Default IP Destination route has been configured.

Main Menu Configuration Management and Communication Node IP Default IP Destination

Configure both SNMP Traps and a Default IP Destination when PVC Multiplexing is used, as when using the Auto-Configuration feature.

4. Select the IP Ping test.

Main Menu Test IP Ping

5.Enter the IP Address of the central site NMS, then select Start.

6.Verify the results of the IP Ping test.

ÐWhile the test is running, In Progress... appears in the Status field.

ÐWhen the test is finished, Alive. Latency = nn ms should appear as the Status (nn being the amount of time the test took in milliseconds).

If any other message is displayed, additional testing will be required.

9783-A2-GB20-00

July 2000

8-23

Page 163
Image 163
Paradyne FrameSaver DSL, 9783 manual Procedure