From: Janto Cin (jantocin@datacomm.co.id)
Date: Wed Mar 19 2003 - 08:59:24 GMT-3
Chuck,
Can we use secondary address on both interfaces then include it in EIGRP
routing process?
TIA,
Janto
----- Original Message -----
From: "Charles Church" <cchurch@wamnet.com>
To: "Janto Cin" <jantocin@datacomm.co.id>; <ccielab@groupstudy.com>
Sent: Wednesday, March 19, 2003 6:49 PM
Subject: RE: EIGRP Neighbor not on common subnet
> Yes, it is a problem. I pretty much tells you the problem. R1 is seeing
> hellos from R2 with an address that falls outside of the address/mask pair
> you defined on R1 for that interface. R2 is complaining about the same
> thing. Either change your masks on both interfaces so that 172.150.1.0
and
> 172.150.2.0 fall on the same subnet, or change the address on one side to
a
> common subnet.
>
> Chuck Church
> CCIE #8776, MCNE, MCSE
> Wam!Net Government Services
> 13600 EDS Dr.
> Herndon, VA 20171
> cell 585-233-2706
> cchurch@wamnet.com
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Janto Cin
> Sent: Wednesday, March 19, 2003 3:44 AM
> To: ccielab@groupstudy.com
> Subject: EIGRP Neighbor not on common subnet
>
>
> Dear All,
>
> Will it be a problem if I got this error message?
>
> R1#
> 05:14:10: IP-EIGRP: Neighbor 172.150.1.1 not on common subnet for
Serial3/1
> (172.150.2.1 255.255.255.0)
>
> R2#
> 05:15:14: IP-EIGRP: Neighbor 172.150.1.1 not on common subnet for Serial1
>
> TIA,
> Janto
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:42 GMT-3