From: CCIE 4 Me (ccie4me@inbox.lv)
Date: Sat Apr 29 2006 - 15:52:20 GMT-3
Faryar,
The cause of this error might not be the very obvious "lack of common
subnets".
You are likely to encounter this error as the last poster stated when your
EIGRP packets are sent on a subnet containing other EIGRP enabled routers
but having different IP subnet addresses.
Each EIGRP 10 enabled router got the packet, and spit it out because they do
not like the subnet information.
This type of error is likely to occur in Lab Workbooks, where to accomodate
many different scanarios, many ip addresses are configured on the same cable
subnet.
It is possible that authentication is required on that subnet for your ip
subnet but you did not enable authentication, hence the EIGRP packets sent
out from your router is being intercepted by all EIGRP speaking routers on
that subnet only for your router to reject the conversation because their ip
address is not on the same subnet.
When you enable authentication, the content of your EIGRP packets will only
be accurately decipher by a remote EIGRP enabled router with same key and
the error message will disappear, because the other EIGRP enabled router on
that cable subnet would not "understand" the conversation.
HTH
Godswill Oletu
----- Original Message -----
From: "Faryar Zabihi (fzabihi)" <fzabihi@cisco.com>
To: "Petr Lapukhov" <petrsoft@gmail.com>
Cc: <ccielab@groupstudy.com>
Sent: Saturday, April 29, 2006 1:55 PM
Subject: RE: EIGRP Neighbor error...
> what if I have to use the physical interface for my frame connection? Do
> I just create the sub-int and put all the other pvc's into it?
>
> Faryar
>
> ________________________________
>
> From: Petr Lapukhov [mailto:petrsoft@gmail.com]
> Sent: Saturday, April 29, 2006 12:53 PM
> To: Faryar Zabihi (fzabihi)
> Cc: ccielab@groupstudy.com
> Subject: Re: EIGRP Neighbor error...
>
>
> This is, actually, not an "error" by itself.
>
> Your backbone router send EIGRP multicast packets on multiple PVCs.
> Since all those PVCs are "linked" to physical interface by default,
> and you have IP enabled on the same interface, multicasts are delivered
> to EIGRP routing process.
>
> But because they have "incompatibe" source ip addresses (different ip
> subnets)
> EIGRP complains on "neighbor not on common subnet". Neighbor with
> correct IP will work okay with your router, though :)
>
> To get rid of that message completely, create a subinterface, and link a
> single
> DLCI to it.
>
> HTH
> Petr
>
>
> 2006/4/29, Faryar Zabihi (fzabihi) <fzabihi@cisco.com>:
>
> IP-EIGRP(Default-IP-Routing-Table:10): Neighbor 54.1.x.254 not
> on common
> subnet for Serial0/0/0 ---- where x is 2,3,10.
>
> Show ip eigrp neighbours
> IP-EIGRP neighbors for process 100
> H Address Interface Hold Uptime SRTT
> RTO Q
> Seq
> (sec) (ms)
> Cnt
> Num
> 0 130.1.26.2 Gi0/1 13 20:56:34 1
> 200 0
> 113
> IP-EIGRP neighbors for process 10
> H Address Interface Hold Uptime SRTT
> RTO Q
> Seq
> (sec) (ms)
> Cnt
> Num
> 0 54.1.1.254 Se0/0/0 13 00:01:12 364
> 2184 0
> 2
>
> Show frame-relay PVC | in DLCI
> DLCI = 51, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
> Serial0/0/0
> DLCI = 100, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE
> =
> Serial0/0/0
> DLCI = 101, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
> Serial0/0/0
> DLCI = 201, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE
> =
> Serial0/0/0
> DLCI = 301, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE
> =
> Serial0/0/0
> DLCI = 401, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE
> =
> Serial0/0/0
>
> interface Serial0/0/0
> ip address 54.1.1.6 255.255.255.0
> encapsulation frame-relay
> ip summary-address eigrp 100 130.1.0.0 255.255.0.0 5
> frame-relay map ip 54.1.1.254 101 broadcast
> no frame-relay inverse-arp
> !
>
>
> EIGRP CONFIG
>
> router eigrp 100
> network 130.1.26.6 0.0.0.0
> network 150.1.6.6 0.0.0.0
> no auto-summary
> eigrp router-id 150.1.6.6
> !
> router eigrp 10
> network 54.1.1.6 0.0.0.0
> no auto-summary
> !
>
> This is an ADJ to BB1 and on BB1 the eigrp network statement is
> 54.0.0.0
> 0.255.255.255
> Is this an IOS issue? PVCs are active but they are unused.
> Any suggestions would be appreciated,
>
>
>
> Faryar
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:59 GMT-3