There are a few ways to accomplish a back-to-back frame-relay connection.
A quick search returns the following options:
Your configuration is closer to hybrid switching, however, you're missing a few key elements.
Frame-Relay
Either R1 or R2 will need to have frame-relay switching enabled to act as the frame-relay switch.
R1(config)#frame-relay switching
The newly designated frame switch's Serial0/0 interface needs to be changed to the frame-relay interface type dce in order to provide LMI.
R1(config)#int s0/0
R1(config-if)#frame-relay intf-type dce
Finally you don't need to include the no keepavlive syntax when performing hybrid switching.
EIGRP
Your matching(required) static frame-relay map statements may include the broadcast statement in order for EIGRP to establish a neighbor adjacency.
R1(config)#int s0/0
R1(config-if)# frame-relay map ip 131.1.12.2 100 broadcast
R2(config)#int s0/0
R2(config-if)# frame-relay map ip 131.1.12.1 100 broadcast
IP: s=131.1.12.1 (local), d=224.0.0.10 (Serial0/0), len 60, sending broad/multicast
Serial0/0(o): dlci 100(0x1841), pkt type 0x800(IP), datagramsize 64
Serial0/0(o):Pkt sent on dlci 100(0x1841), pkt type 0x800(IP), datagramsize 64
Without the broadcast statement, EIGRP messages sent to the multicast address 224.0.0.10 will fail to be encapsulated.
IP: s=131.1.12.1 (local), d=224.0.0.10 (Serial0/0), len 60, sending broad/multicast
Serial0/0: broadcast search
Serial0/0:encaps failed on broadcast for link 7(IP)
IP: s=131.1.12.1 (local), d=224.0.0.10 (Serial0/0), len 60, encapsulation failed
Unicast EIGRP
Or, instead of using the broadcast keyword with your static frame-relay map statements to avoid encapsulation failures, you can specify EIGRP unicast neighbors under EIGRP process 100 and your adjacency should form.
R1(config-if)#router eigrp 100
R1(config-router)#neighbor 131.1.12.2 s0/0
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.1.12.2 (Serial0/0) is down: Static peer configured
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.1.12.2 (Serial0/0) is up: new adjacency
R2(config-if)#router eigrp 100
R2(config-router)#neighbor 131.1.12.1 s0/0
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.1.12.1 (Serial0/0) is down: Static peer configured
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.1.12.1 (Serial0/0) is up: new adjacency
Via (one of many) very old discussions on the Cisco Support Forums:
CDP will transit through the Frame Relay PVC carried by the FR switch. By default it's disabled on FR interfaces, but you can enable it. Then the end point routers will see one another, but you won't see the intermediate frame switch(es). [link]
Yes, CDP is layer-2. However, the frame switch is a frame switch. CDP isn't frame-relay, so it will ignore it. Once a PVC is created, CDP will flow through it, but not before. As there's no VCs, R1 and R2 aren't connected to each other.
Best Answer
Frame relay does not support real broadcast, it uses pseudo broadcast, meaning that it replicates incoming multicast/broadcast to all DLCIs that have the broadcast keyword on the frame-relay map statements. DLCIs learned via inverse ARP will always have broadcast enabled.
When you choose the network type you tell OSPF how to behave, is DR/BDR used and is multicast used?
With non-broadcast or point-to-multipoint non-broadcast (Cisco specific) you need to define neighbor statements. The reason being that you have told OSPF that you have no broadcast capability so you want to use unicast for the control plane traffic. OSPF therefore expects that you configure neighbor statements before it starts sending hellos.
I've had a few facepalm moments in the past studying for the CCIE where I did enable non-broadcast and no adjacencies were coming up. Debugs showed no hellos going out which is usually a sign you forgot a neighbor statement or are running passive-interface.