I would read the 'manage one-way links' task as requiring aggressive mode since it will not actively take down a link without that option being enabled.
I would also read that the task requires PAgP based on the wording "can not use an industry standard, but we must make sure these links can negotiate their setup" On Mon, Oct 18, 2010 at 10:55 AM, Terry Vinson <[email protected]>wrote: > Section 2.4 > > Configure any interfaces connecting the switches together to appear as > one link to STP per neighbor. > If either of the interfaces is damaged, the switches should manage > one-way links. Do not use industry > standards, but make sure these links can negotiate their setup. > > The task states that one-way links should be "managed" but the > solution guide states: > > "Finally, turn on UDLD to manage the one-way link detection. There's > no mention about anything > requiring aggressive mode, so that part is up to you." > > I guess my question is one regarding wording. The task states that > the switches should "manage" one-way > links. The prescribed solution seems only informational (at best) and > would do nothing to prevent Bridging- > Loops. Which I assume is what we are being asked to manage. > > Additionally, the task states that we can not use an industry > standard, but we must make sure these links > can "negotiate their setup". > > But the solution on page 43 states that we "end up either using PAgP > or just mode on" > > I thought that mode "on" didn't allow negotiation, am I incorrect? > > Any help/thoughts would be appreciated. > > Terry > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
