It is possible that this worked on an older version of code but no longer works. I seem to recall this but would have to look thru the archives. I wouldn't worry too much about this question.
Regards, Tyson Scott - CCIE #13513 R&S, Security, and SP Managing Partner / Sr. Instructor - IPexpert, Inc. Mailto: [email protected] Telephone: +1.810.326.1444, ext. 208 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE (R&S, Voice, Security & Service Provider) certification(s) with training locations throughout the United States, Europe, South Asia and Australia. Be sure to visit our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Aaron Moreck Sent: Tuesday, February 22, 2011 4:05 PM To: Daniel Gheorghe Cc: [email protected] Subject: Re: [OSL | CCIE_RS] WB 2 Lab 9 voice vlan Sorry i didn't see the last part about not modifying the router interfaces i dont see how you would do this while 1.) tagging all VLANS including the native and 2.) Not modifying the interfaces on R6 I think you are in a catch 22 here. If requirement #1 was not there you could simply interface FastEthernet0/6 switchport trunk encap dot1q switchport mode trunk switchport trunk allowed vlan 56,76 switchport trunk native vlan 56 On Tue, Feb 22, 2011 at 1:31 PM, Daniel Gheorghe <[email protected]>wrote: > The behavior is the same if the Cat port is dynamic or not. The strange > thing is that the 56 vlan has connectivity if I remove the voice vlan from > the port. I can't understand this. > > The restrictions of the task include all the vlans being tagged (so vlan > dot1g tag native) and only the port-channels between the switches should be > seen as trunks, So the ideea of the voice vlan appeared in order to avoid > using a trunk on Cat2 fa0/6. > > Also I confirm that the behavior is the same even if we use 2 subinterfaces > on the router (although the task prohibits the modification of the router > interface addressing). > > On Tue, Feb 22, 2011 at 10:24 AM, marc abel <[email protected]> wrote: > > > Actually from your output you are set to dynamic on f0/6 so it probably > is > > trunking. Can you confirm? If so you can either set the native vlan to 56 > on > > the the trunk, or change the router side to a sub-interface as I > suggested > > before. > > > > > > > _______________________________________________ > 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
