Frame Relay strangeness

[Chris Driggers]

What do you guys make of this? Host router with a point to point frame relay subinterface with an IP address of 10.129.16.1 255.255.255.0. The frame relay is up up with LMI traffic being passed. Then you have a remote router with a frame relay p2p subinterface with an IP of 10.129.16.2 255.255.255.0. The frame relay is up up on this one as well, with LMI traffic being passed. Both of these routers are running EIGRP on this network.

Both the frames are up, but I can't ping across them. The host router has system message "neighbor 10.129.16.2 not on common subnet for serial0/0/0.280".

There are other remote routers with the EXACT same config (except IP addresses and DLCIs) that work fine.

Any ideas why the frame is not pingable?

[Harold Ritter]

Is se0/0/0.280 the interface where 10.129.16.1 is configured. If not, it looks like a PVC misconfiguration or the wrong DLCI configured on se0/0/0.280.

Hope this helps,

[Chris Driggers]

yeah that's the interface. the pvc's are right because this router setup is a direct replacement of some motorola routers using the same pvc's. show frame-relay pvc shows active pvc's on both sides.

[Harold Ritter]

Could you please post the configuration of the router on which you are getting the EIGRP error message.

Thanks,

[Chris Driggers]

The config is attached. Hope you see something I missed!

[Harold Ritter]

According to your configuration subinterface se0/0/0.280 has an IP address of 10.129.17.1 not 10.129.16.1. The EIGRP error message definitely indicates that DLCI 280 connects to the remote interface with the IP address 10.129.16.2. Se0/0/0.888 with its ip address 10.129.16.1 is the subinterface that should connect to that remote interface.

Please verify the DLCI to sub-interface assignement.

Hope this helps,

[Chris Driggers]

Good call. The list of DLCIs I had had a couple transposed. When I switched them, everything came up great.

Thanks!