From: Petr Lapukhov (petrsoft@gmail.com)
Date: Sat Apr 29 2006 - 15:00:28 GMT-3
This is just a question of convenience :) Usually, you dont need
to create subinterfaces, only if lab specifically asks you to do that.
EIGRP will work fine even with all thouse "complains". Remember, they
are just because your backbone sends additional multicast packets,
along with "correct" one.
So your EIGRP process will drop "bad" packets, and accept correct ones.
Petr
2006/4/29, Faryar Zabihi (fzabihi) <fzabihi@cisco.com>:
>
> 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
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:59 GMT-3