suitable for framing...

because of split horizon on point-to-point frame links,  a distance vector protocol needs to have broadcast added to it's map statement, like so...

frame-relay map ip 10.0.20.30 201 broadcast


remember the remote ip gets mapped to the local dlci...  the REMOTE ip gets mapped to the LOCAL dlci.. and the links have to be in the same subnet... in this case router 3 is receiving the rip route because only router 2 is advertising it...

r2620_02#sh ip route

Codes:

Gateway of last resort is not set

     2.0.0.0/24 is subnetted, 1 subnets
C       2.2.2.0 is directly connected, Loopback0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.20.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/0
r2620_02#

versus...

frame-relay map ip 10.0.20.2 301 (no broadcast statement)


r2620_03#sh ip route
Codes:

Gateway of last resort is not set

R    2.0.0.0/8 [120/1] via 10.0.20.2, 00:00:25, Serial0/0
     3.0.0.0/24 is subnetted, 1 subnets
C       3.3.3.0 is directly connected, Loopback0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.20.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/0
r2620_03#


once broadcast is added to the frame map,

r2620_03(config-if)#frame map ip 10.0.20.2 301 broadcast


(use clear ip route * to force an update)


r2620_02#sh ip route
Codes:

Gateway of last resort is not set

     2.0.0.0/24 is subnetted, 1 subnets
C       2.2.2.0 is directly connected, Loopback0
R    3.0.0.0/8 [120/1] via 10.0.20.30, 00:00:05, Serial0/0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.0.20.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/0
r2620_02#

naturally you could use no ip split-horizon or subinterfaces instead but this was more fun...