Information Technology Reference
In-Depth Information
4.
IETF = Internet Engineering Task Force
5.
DLCI = Data link connection identifier
6.
PVC = permanent virtual circuit
Frame Relay: Cannot ping Remote Router
Symptom:
Attempts to
ping
the remote router across a Frame Relay connection fail.
Table 18-2 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table18-2
Frame Relay: Cannot ping Remote Router
Possible Problem
Solution
Encapsulation
mismatch has
occurred.
1.
When connecting Cisco devices with non-Cisco devices,
you must use IETF encapsulation on both devices. Check
the encapsulation type on the Cisco device with the
show
frame-relay map
exec command.
2.
If the Cisco device is not using IETF encapsulation, use the
encapsulation frame-relay ietf
interface configuration
command to configure IETF encapsulation on the Cisco
Frame Relay interface.
For information on viewing or changing the configuration of
the non-Cisco device, refer to the vendor documentation.
DLCI is inactive or
has been deleted.
Use the
show frame-relay pvc
exec command to view the
status of the interface's PVC.
1.
If the output shows that the PVC is inactive or deleted,
there is a problem along the path to the remote router.
Check the remote router, or contact your carrier to check
the status of the PVC.
2.
DLCI is assigned to
the wrong
subinterface.
Use the
show frame-relay pvc
privileged exec command
to check the assigned DLCIs. Make sure that the correct
DLCIs are assigned to the correct subinterfaces.
1.
If the DLCIs appear to be correct, shut down the main
interface using the
shutdown
interface configuration
command, and then bring the interface back up using the
no
shutdown
command.
2.
