You must define specific parameters for Frame Relay operation. The parameters include LMI and DLCI
configuration. If you use a pre 11.2 release of IOS Software, you must specify the LMI type that is being
implemented. The Frame Relay service provider, or service provider, should provide the LMI information.
For IOS Software Release 11.2 and later, you need not configure the LMI type. To disable LMI completely,
use the no keepalive command to cease to transmit and receive LMI. However, keepalives must also be
disabled at the switch.
You can now configure address mapping, if necessary. In the case of point-to-point connections, mapping of
protocol addresses to DLCIs is dynamic and requires no intervention. However, if point-to-multipoint
connections are in use, manual mapping is necessary. Mapping is the same from protocol to protocol and
uses the frame-relay map protocol next_hop dlci [ broadcast ][ ietf | cisco ]command.
Protocols supported in the frame-relay map command include IP, IPX, AppleTalk, CLNS, DECnet, XNS,
and Vines. The next_hop argument in the command represents the next hop logical address for the router on
the remote end of the connection. The dlci argument represents the local DLCI, not that of the remote end.
The broadcast keyword specifies that routing updates traverse the network through this circuit. The final
option in the command specifies which Frame Relay implementation to utilize in communications with the
remote router. When communicating with a Cisco device on the remote side, the default value (cisco) can
be utilized. However, when communicating with non-Cisco gear on the remote end, it can be necessary to
specify that the IETF implementation of Frame Relay be used.