Information Technology Reference
In-Depth Information
Table18-2
Frame Relay: Cannot ping Remote Router (continued)
Possible Problem
Solution
The
frame-relay
map
command is
missing.
1.
Use the
show frame-relay map
privileged exec command
to see whether an address map is configured for the DLCI.
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.
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]
Syntax Description:
•
protocol
—Supported protocols: AppleTalk, DECnet, IP,
XNS, IPX, and VINES.
•
protocol-address
—Address for the protocol.
•
dlci
—DLCI number for the interface.
•
broadcast
—(Optional) Broadcasts should be forwarded to
this address when multicast is not enabled.
•
ietf
—(Optional) IETF form of Frame Relay encapsulation.
Use when the communication server is connected to
another vendor's equipment across a Frame Relay network.
•
cisco
—(Optional) Cisco encapsulation method.
Example:
The following example maps IP address 131.108.123.1 to DLCI
100:
interface serial 0
frame-relay map ip 131.108.123.1 100 broadcast
4.
Make sure that the DLCIs and next-hop addresses specified
in
frame-relay map
commands are correct. The specified
protocol address should be in the same network as your
local Frame Relay interface.
For complete information on configuring Frame Relay address
maps, refer to the Cisco IOS
Wide-Area Networking
Configuration Guide
.
