The passive-interface command behaves differently for
different routing protocols. EIGRP with
passive-interface does not send hello packets and
therefore does not form adjacencies with neighbors.
Very useful when testing new WAN Links in live
environments.

regards,

Phil.

--- "Raul F. Fernandez" <[EMAIL PROTECTED]>
wrote: > Circusnuts,
> 
> Yes I too found this to be a bit different. I
> realize in most cases the passive-interface command
> can be used to keep an interface from sending
> routing information update but it can still take
> updates. I see no EIGRP updates on the stub router's
> routing table except for the default route "D*  
> 0.0.0.0/0 [90/160514560] via 10.139.248.133, 1d06h,
> Serial0/0.1". What is interesting to me is that it
> has formed a neighbor adjecency with hub router yet
> it does not seem to be sending any ipdates to the
> multicast address 224.0.0.10. Circusnut, the router
> is a 2600 mem and the IOS file is
> SF26AP-12.0.7T.BIN. I am looking for info now...but
> any input from you would be gladly received.
> 
> This is the EIGRP config, I am really not dreaming
> :)
> 
> router eigrp 64783
>  network 10.0.0.0
>  network 172.26.0.0
>  no auto-summary
>  eigrp stub connected
> 
> 
> 
> Sincerely,
> 
> Raul F. Fernandez
>   -----Original Message-----
>   From: Circusnuts <[EMAIL PROTECTED]>
>   To: Raul Fernandez <[EMAIL PROTECTED]>; 'Cisco
> group study' <[EMAIL PROTECTED]>
>   Date: Sunday, November 12, 2000 9:23 AM
>   Subject: Re: Question about eigrp 
> 
> 
> 
> 
>   Hmmm- a couple things you have described don't
> seem EIGRP-like.  The network @ the office is EIGRP
> & stubs are usually set as passive or not set EIGRP
> @ all.  In both cases they're alive & can transmit
> thought the network, but only "a little help from
> their friend" (their directly connected neighbor). 
> Now- the stub command may be needed when multiple
> connection run to a dead end or solo router (I have
> never had this issue).  With a default gateway, this
> surprises me...  EIGRP would not be doing it's job
> of discovering of a successor or feasible, with
> static commands.  Changing path cost I have seen,
> but default- anything I don't recommend.  If your
> network is small, this may not be issues.  My job
> deals with over 1300 EIGRP routers & we have to
> follow EIGRP to the letter or it things go crazy
> (which happens anyway from time to time :-)  If you
> ever get a chance, pick up EIGRP Network Design
> Solutions (Cisco Press).  As for the 12.7T, what
> model of router ???  We have been sooo leery with
> the 12.0's, especially in the 7500 series (when it
> comes to EIGRP).  I could check a few devices, but I
> can tell you DES, LANE, & EIGRP do not exist well
> beyond 11.2 (22a)...
> 
>   Let me know, I actually get to talk from some
> experience here :-)
> 
>   Good Luck !!!
>   Phil
>     ----- Original Message ----- 
>     From: Raul Fernandez 
>     To: 'Cisco group study' 
>     Sent: Saturday, November 11, 2000 8:36 PM
>     Subject: Question about eigrp 
> 
> 
>     I have been working with a system which has
> under its eigrp process this command "eigrp stub
> connected". From what I gather this perticular
> router acts as a stub and receives no eigrp updates
> to its routing table but does receive and send out
> hellos because it has established a neighbor
> relationship to the hub router. There is a default
> gateway which seem to route all packages out of the
> router and into the hub router. Anyone have any
> links or info on this. IOS version is 12.0(7)T and I
> have looked in the CCO but I see nothing so far.
> Anything on this for reading purposes would be much
> appreciated.
>      
>     Sincerely,
>      
>     Raul F. Fernandez
>      
>      
> 


____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to