From: A.Steinbock (anja10@xxxxxxx)
Date: Sat Dec 29 2001 - 03:50:35 GMT-3
Jim Brown, you are the King.
Among all the answers, only yours solved the problem.
Frame relay had covertly built another map between R2 & R3.
As soon as I put the "no frame inver" command on the R2 & R3's interface,
EIGRP stopped complaining.
I don't understand why so many of you concluded that the subnetmask is wrong.
R1's subinterface #2 with the IP address of 10.155.1.1/30 connects to R2's
serial interface that has 10.155.1.2/30 address.
Again,
R1's subinterface #3 with the IP address of 10.155.1.5/30 connects to
R3's serial interface that has 10.155.1.6/30 address.
Thanks and Happy New Year,
Akim
Jim Brown <Jim.Brown@CaseLogic.com> wrote:
> The frame switch configuration appears to be a full mesh and more. While
you
> are only statically creating a map from R2-R1 and R3-R1 the wonderful
> frame-relay inverse arp facility is also creating a map between R2-R3
> without your help.
>
> If you do a show frame map, I believe you will see a dynamic mapping
between
> R2-R3 in addition to the static ones you created.
>
> This additional mapping is why you are observing the EIGRP on different
> network errors. Routers R2 and R3 are on different subnets so they are
> wondering why they are seeing hellos that aren't on their subnet....
>
> This error is a result of the they dynamic frame map.
>
> Disable auto mapping with no frame inverse arp under the physical
interface,
> reload, and you should be good to go.
>
>
>
> -----Original Message-----
> From: A.Steinbock [mailto:anja10@usa.net]
> Sent: Friday, December 28, 2001 8:37 AM
> To: ccielab@groupstudy.com
> Subject: EIGRP: Neighbor not on common subnet
>
>
> I am yet to figure out why I am getting this message on a very simple
> frame-relay+Eigrp setting.
>
>
> Here is the diagram and router configs: http://24.234.55.18/out/eigrp.jpg
>
> The frame switch config is:
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> clockrate 56000
> frame-relay lmi-type cisco
> frame-relay intf-type dce
> frame-relay route 912 interface Serial2 921
> frame-relay route 913 interface Serial3 931
> frame-relay route 914 interface Serial4 941
> frame-relay route 915 interface Serial5 951
> frame-relay route 916 interface Serial6 961
> frame-relay route 917 interface Serial7 971
> !
> interface Serial2
> no ip address
> encapsulation frame-relay
> clockrate 56000
> frame-relay lmi-type cisco
> frame-relay intf-type dce
> frame-relay route 921 interface Serial1 912
> frame-relay route 923 interface Serial3 932
> frame-relay route 924 interface Serial4 942
> frame-relay route 925 interface Serial5 952
> frame-relay route 926 interface Serial6 962
> frame-relay route 927 interface Serial7 972
> !
> interface Serial3
> no ip address
> encapsulation frame-relay
> clockrate 56000
> frame-relay lmi-type cisco
> frame-relay intf-type dce
> frame-relay route 931 interface Serial1 913
> frame-relay route 932 interface Serial2 923
> frame-relay route 934 interface Serial4 943
> frame-relay route 935 interface Serial5 953
> frame-relay route 936 interface Serial6 963
> frame-relay route 937 interface Serial7 973
> !
> on R2 I get the message:
> 01:38:16: IP-EIGRP: Neighbor 10.155.1.6 not on common subnet for Serial0
>
> on r3 I get the message:
> 01:38:53: IP-EIGRP: Neighbor 10.155.1.2 not on common subnet for Serial0
>
> I've checked CCO. although there is an explanation for it at
> http://www.cisco.com/warp/public/103/15.html
>
> but I can not relate.
> Can some one shed a light Please?
>
> TIA
> Akim
>
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:49 GMT-3
