background image
RFC 1490 357
RFC 1490
Upper-layer protocols such as Novell and AppleTalk interoperate with Frame Relay with RFC
1490, which is simply a multiprotocol encapsulation method over Frame Relay. RFC 1490 is a
specification for putting type codes into the Frame Relay headers and the ability to forward
different protocols over Frame Relay. It covers both bridged and routed traffic. RFC 1490 was
first supported in Cisco IOS version 10.3(1).
Frame Relay Mapping
Figure 10-18 shows how Frame Relay mapping works. A packet comes into Router A on the
left, which is trying to reach 192.168.200.1. The router strips the data link header Ethernet
encapsulation. It then looks at Layer 3 and recognizes it is an IP packet. The router looks at the
IP header, finds a destination address of 192.168.200.1, and says it is not a directly connected
interface. It looks in the IP routing table for the most explicit match, finds the next hop (in this
case, Router B or 192.168.1.2), and an interface to send the data out on (Serial 0). This has to
go via Frame Relay to Router B.
Figure 10-18
Frame Relay Mapping
Frame Relay Network
Router A
Router B
DLCI 100
DLCI 200
Ethernet
Ethernet
192.168.1.1
192.168.1.2
RouterA#sh frame-relay map
Serial0 (up): ip 192.168.1.2 dici 100(0x68,0x1880), static,
broadcast, CISCO, status defined, active
interface Serial0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay
ip ospf network broadcast
no ip mroute-cache
frame-relay map ip 192.168.1.2 100 broadcast
frame-relay interface-dici 100
no frame-relay inverse-arp
192.168.100.1
192.168.200.1
87200333.book Page 357 Wednesday, August 22, 2001 2:53 PM