[c-nsp] Max number of EIGRP neighbors
Rodney Dunn
rodunn at cisco.com
Mon Jan 10 16:03:16 EST 2005
Correct.
You just can't (currently) have additional
neighbors behind your spokes.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a0080087026.html
Rodney
On Fri, Jan 07, 2005 at 05:13:36PM -0500, Luan Nguyen wrote:
> Not really. Stub connected means being able to advertise connected subnets.
> Stub means the hub won't query spoke for routing update = good for stability
>
> There is a bunch of other stub like eigrp stub static means you could
> redistribute static routes back to the hub. FYI, we also have dual hubs.
>
>
>
> -luan
>
>
>
> _____
>
> From: Cheung, Rick [mailto:Rick.Cheung at nextelpartners.com]
> Sent: Friday, January 07, 2005 4:15 PM
> To: Rodney Dunn; Luan Nguyen
> Cc: Cisco Mailing List (E-mail)
> Subject: RE: [c-nsp] Max number of EIGRP neighbors
>
>
>
> Thanks folks. Just to clarify, we wouldn't be able to configure it
> as a stub if it is dual/multihomed, correct?
>
>
>
> ___________________________________________________________________
>
> Thanks,
> Rick Cheung
> Desk: 585.350.2097
> DAP: 178*1*2097
> NPI Technical Analyst - WAN
>
>
>
> -----Original Message-----
> From: Rodney Dunn [mailto:rodunn at cisco.com]
> Sent: Friday, January 07, 2005 2:05 PM
> To: Luan Nguyen
> Cc: Cheung, Rick; Cisco Mailing List (E-mail)
> Subject: Re: [c-nsp] Max number of EIGRP neighbors
>
>
>
> You get the best EIGRP scalability for hub-n-spoke
> by configuring your spokes as stubs if they
> really are stubs.
>
> Rodney
>
> On Fri, Jan 07, 2005 at 11:02:12AM -0500, Luan Nguyen wrote:
> > I've seen 300 neighbors on 7206VXR 256M of DRAM NPE-400. Spokes have
> eigrp
> > stub connected configured.
> >
> > -luan
> > ----- Original Message -----
> > From: "Cheung, Rick" <Rick.Cheung at nextelpartners.com>
> > To: "Cisco Mailing List (E-mail)" <cisco-nsp at puck.nether.net>
> > Sent: Friday, January 07, 2005 10:53 AM
> > Subject: [c-nsp] Max number of EIGRP neighbors
> >
> >
> > >
> > > Now that we're on the topic, what is the max number of EIGRP
> > > neighbors?
> > >
> > > We are looking at a single core, dual hub DMVPN network, where 40
> > > spokes will connect to two 3745s. Each 3745 will see 40 neighbors across
>
> > the
> > > GRE tunnel interface, plus 10 additional neighbors off the inside GE
> > > network, for a total of 50.
> > >
> > > I seem to recall the number 35 off the CCDA design book, but our
> > > Cisco SE assures us of otherwise.
> > >
> > >
> > >
> > > ___________________________________________________________________
> > >
> > > Thanks,
> > > Rick Cheung
> > >
> > >
> > > This message, including any attachments, contains confidential
> information
> > intended for a specific
> > > individual and purpose and is protected by law. If you are not the
> > intended recipient, please contact
> > > sender immediately by reply e-mail and destroy all copies.
> > > You are hereby notified that any disclosure, copying, or distribution of
>
> > this message, or the taking
> > > of any action based on it, is strictly prohibited.
> > >
> > > WARNING: Computer viruses can be transmitted via email. The recipient
> > should check this email
> > > and any attachments for the presence of viruses. The sender accepts no
> > liability for any damage
> > > caused by any virus transmitted by this email. E-mail transmission
> cannot
> > be guaranteed
> > > to be secure or error-free as information could be intercepted,
> corrupted,
> > lost, destroyed, arrive
> > > late or incomplete, or contain viruses. The sender therefore does not
> > accept liability for any errors
> > > or omissions in the contents of this message, which arise as a result of
>
> > e-mail transmission.
> > > _______________________________________________
> > > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> This message, including any attachments, contains confidential information
> intended for a specific
> individual and purpose and is protected by law. If you are not the intended
> recipient, please contact
> sender immediately by reply e-mail and destroy all copies.
> You are hereby notified that any disclosure, copying, or distribution of
> this message, or the taking
> of any action based on it, is strictly prohibited.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should
> check this email
> and any attachments for the presence of viruses. The sender accepts no
> liability for any damage
> caused by any virus transmitted by this email. E-mail transmission cannot be
> guaranteed
> to be secure or error-free as information could be intercepted, corrupted,
> lost, destroyed, arrive
> late or incomplete, or contain viruses. The sender therefore does not accept
> liability for any errors
> or omissions in the contents of this message, which arise as a result of
> e-mail transmission.
>
More information about the cisco-nsp
mailing list