EIGRP stub router
A router is configured as stub inorder to prevent the queries (in the absence of Feasible successor) sent to that router.
Stub has following options
receive-only - Stub router only receives information static - advertises static routes (but first be redistributed in eigrp) connected - advertises connected routes summary - advertises summary routes configured on an interface redistributed - advertises those routes that are redistributed into eigrp (Redistribution is done on the stub router) Leak-map - Inorder to leak “D” and “DEX” routes present in the routing table,use leak-map option.
Yes, stub router acts as a regular eigrp neighbour.
HTH
Best regards, On 11/2/08, Rob Clav wrote: > > Hi, > at some labs I find that eigrp stub router is for act like rip passive > interface behavior. But at the solutions it add most of the time > connected and summary. > I understant that connected is necessary if you have some networks > that you wish to advetise but summary I don’t know which is the rule > to use it. > By other hand, if you are advertising connected areas, and summaries, > this router is working as regular eigrp nei, or not? > Thank you, > Roberto Clavero > > > Blogs and organic groups at http://www.ccie.net > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html > > > > > > > >
— Fahad Khan
Blogs and organic groups at http://www.ccie.net
























