I don't see any dependencies either, I'm sure you would have been OK but I agree with you about having Tyson or Marko weigh in on this one.
For me personally I use dot1q trunks wherever possible out of habit, especially since ISL is dying as a technology, but that's just a preference. Thank you, Steve Di Bias Network Engineer - Information Systems Valley Health System - Las Vegas Office - 702- 369-7594 Cell - 702-241-1801 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of marc abel Sent: Monday, April 04, 2011 7:02 AM To: Jason Maynard; [email protected] Subject: Re: [OSL | CCIE_RS] Vol 3 lab 2 config I understand that, this is just a case where it seems like they applied extra config for reasons that are unclear to me.If a question doesn't seem to ask for something, I don't want to apply extra config. I am just wondering if there is maybe a later dependency that I just can't see. It would be nice to have one of our experts weigh in on this topic. They seem to be quieter than usual lately. On Mon, Apr 4, 2011 at 8:37 AM, Jason Maynard <[email protected]> wrote: > Hey Marc, > Don't forget that there are at times more than one way to meet the > requirements. If you met the requirements and did not violate > any restriction then you would achieve the points. > The DSG will not show all possible solutions. > > On Sun, Apr 3, 2011 at 12:59 PM, marc abel <[email protected]> wrote: >> >> That is a good suggestion but I don't see it. Here are the requirements: >> >> >> Ensure that the lab switches are configured according to the layer 2 >> tables and diagrams (I don't see anything to indicate trunking >> encapsulation on any of the drawings or tables) >> >> All EtherChannel interfaces must be attempting to establish >> EtherChannel links using LACP. All inter-switch links should >> automatically negotiate trunking. Lower switch should wait >> higher-numbered switch before it starts trunking. >> >> Vlan-1112 should be allowed only links between Cat1 and Cat2. >> Vlan-1314 should be allowed only on links between Cat3 and Cat4. >> >> >> >> -Marc >> >> >> >> On Sun, Apr 3, 2011 at 11:48 AM, Don Lundquist <[email protected]> >> wrote: >> > To take a stab at this without review of the specific requirements >> > stated, my first question would be is there reference to how the tasks are >> > worded... Does it state "use industry standards"...? LACP is an industry >> > standard and so is D1Q..? >> > >> > Don >> > >> > >> > On Apr 3, 2011, at 12:21, "marc abel" <[email protected]> wrote: >> > >> >> Vol 3 lab 2 requires dynamic trunking between the switches, and makes >> >> certain requirements about LACP on the port channels. I get all of >> >> this but am curious about 1 thing. >> >> >> >> The solutions guide shows specifying Dot1q as the encapsulation type. >> >> I don't see a requirement for this. Is there some later task that >> >> makes this necessary? I haven't been able to spot it yet if so. >> >> >> >> Or is it just extra config? Personal preference? >> >> >> >> Thank you, >> >> >> >> Marc >> >> _______________________________________________ >> >> 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 > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com UHS Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient (s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this information is prohibited. If this was sent to you in error, please notify the sender by reply e-mail and destroy all copies of the original message. _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
