System information

Troubleshooting Frame Relay Connections 18-405
Frame Relay: Cannot ping Remote Router
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.
Table 18-2 Frame Relay: Cannot ping Remote Router
Possible Problem Solution
Encapsulation mismatch
Step 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.
Step 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 inactive or deleted
Step 1 Use the show frame-relay pvc exec command to view the status of the
interface’s PVC.
Step 2 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.
DLCI assigned to wrong
subinterface
Step 1 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.
Step 2 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.
Misconfigured access list
Step 1 Use the show access-list privileged exec command to see whether there
are access lists configured on the router.
Step 2 If there are access lists configured, test connectivity by disabling access
lists using the no access-group global configuration command. Check
whether connectivity is restored.
Step 3 If connections work, reenable access lists one at a time, checking
connections after enabling each access list.
Step 4 If enabling an access list blocks connections, make sure that the access list
does not deny necessary traffic. Make sure to configure explicit permit
statements for any traffic you want to pass.
Step 5 Continue testing access lists until all access lists are restored and
connections still work.
frame-relay map command
missing
Step 1 Use the show frame-relay map privileged exec command to see whether
an address map is configured for the DLCI.
Step 2 If you do not see an address map for the DLCI, enter the clear
frame-relay-inarp privileged exec command and then use the show
frame-relay map command again to see whether there is now a map to
the DLCI.
Step 3 If there is no map to the DLCI, add a static address map. Use the
frame-relay map interface configuration command.
Syntax:
frame-relay map protocol protocol-address dlci [broadcast] [ietf | cisco]