Tyson, Thank you for your email. One thing is for sure, IPexpert is a team of really really dedicated professionals.
2008/7/10 Suresh Mishra <[EMAIL PROTECTED]>: > Hello Scott, > > Besides all the confusion in the wording of the question, the tunnel > configuration itself is not correct. If you look at the config for the > first task 5.6 you will find that "switchport mode tunnel-dot1q" is > configured on the interfaces that are not facing the end switches. In > this task CAT1 needs to run 802.1Q tunnel with CAT3. The traffic > passes through CAT2 and CAT4. > > Now as per Cisco DOC, the tunnel mode config is only needed on the > interfaces that are facing cat1 and cat3 switches. There is no need to > set the tunnel mode on the ports connecting CAT2 and CAt4. > > Cisco Doc infact says that we can use any type of tunnel (including > ISL) internally to carry the traffic within the backbone(CAT2-CAT4). > Only the customer needs to be in tunnel mode (Which in this case would > be CAT1 and CAT3) > > The setup will still work but why to create a setup that is confusing > and technically incorrect. > > Now the frustration comes from the fact that the question is confusing > then after that we read a solution that is half accurate. > > Thanks > Suresh > > > On Wed, Jul 9, 2008 at 5:01 PM, Tyson Scott <[EMAIL PROTECTED]> wrote: >> John, >> >> Thank you for the email. I can understand your concern and wanted to >> go over just a few of your points below. >> >> I think you made some very good comments and I don't take any offense >> to what you are saying. It is always good to get candid feedback. So >> thank you. >> >> Going through the lab I did see some minor wording mistakes that I >> will have to go back and fix but looking at it they don't seem to >> affect the explanation of the lab. >> >> But I think a lot of your frustration is coming from a >> misunderstanding of the purpose/goal of the lab. >> >> As I read your email below It seems to be you saying you felt that >> this lab should be given as an introduction to l2-tunneling. I want >> to clarify that the technology focused labs are not an introduction >> but an in-depth look at the technology. The l2-tunneling portion of >> this lab is very complex. >> >> So to understand that the lab is not to introduce you to the >> technology but to take you into a in depth view of what you can do >> with the technology may change your frustration with the lab. It is >> good that you were able to go out on your own and configure the >> etherchannels from end to end. Infact you could also do a search in >> the proctor guide of one of the multiprotocol labs to find another >> example that you could configure to give more experience. But next >> take a shot at the lab again and I think you will appreciate the work >> that it is puting you through. >> >> In the multi protocol labs there is too much material to go into the >> technologies like we do in focused labs. >> >> So the hopes are, if you can complete the configuration requirements >> of the lab you should never run into another l2-tunneling scenario >> that you can't complete based on the lab. >> >> I do understand your frustration and that is why I am taking the time >> to comment. >> >> In the note you mentioned that you were not able to find a show >> etherchannel summary command. I guess that is something that could be >> added but the verification of the etherchannel is in the lab. Again >> since this is a technology focus we chose to use the show etherchannel >> detail so you could see the full status and protocol negotiation in >> the output. Again just another vantage point to understanding the >> technology better. >> >> >> Here is the output of the command as shown from Cat3 copied from the >> proctor guide. >> >> Cat3(config-if-range)#do sh eth >> Channel-group listing: >> ---------------------- >> >> Group: 13 >> ---------- >> Group state = L2 >> Ports: 3 Maxports = 8 >> Port-channels: 1 Max Port-channels = 1 >> Protocol: PAgP >> Minimum Links: 0 >> >> Cat3(config-if-range)#do sh eth det >> Channel-group listing: >> ---------------------- >> >> Group: 13 >> ---------- >> Group state = L2 >> Ports: 3 Maxports = 8 >> Port-channels: 1 Max Port-channels = 1 >> Protocol: PAgP >> Minimum Links: 0 >> Ports in the group: >> ------------------- >> Port: Fa0/19 >> ------------ >> >> Port state = Up Mstr In-Bndl >> Channel group = 13 Mode = Desirable-Sl Gcchange = 0 >> Port-channel = Po13 GC = 0x000D0001 Pseudo port-channel = Po13 >> Port index = 0 Load = 0x00 Protocol = PAgP >> >> >> Flags: S - Device is sending Slow hello. C - Device is in Consistent state. >> A - Device is in Auto mode. P - Device learns on physical port. >> d - PAgP is down. >> Timers: H - Hello timer is running. Q - Quit timer is running. >> S - Switching timer is running. I - Interface timer is running. >> >> Local information: >> Hello Partner PAgP Learning Group >> Port Flags State Timers Interval Count Priority Method Ifindex >> Fa0/19 SC U6/S7 H 30s 1 128 Any 5013 >> >> Partner's information: >> >> Partner Partner Partner Partner Group >> Port Name Device ID Port Age Flags Cap. >> Fa0/19 Cat1 000a.8a4b.a400 Fa0/19 0s SC D0001 >> >> Age of the port in the current state: 0d:00h:00m:23s >> >> Port: Fa0/21 >> ------------ >> >> Port state = Up Mstr In-Bndl >> Channel group = 13 Mode = Desirable-Sl Gcchange = 0 >> Port-channel = Po13 GC = 0x000D0001 Pseudo port-channel = Po13 >> Port index = 0 Load = 0x00 Protocol = PAgP >> >> Flags: S - Device is sending Slow hello. C - Device is in Consistent state. >> A - Device is in Auto mode. P - Device learns on physical port. >> d - PAgP is down. >> Timers: H - Hello timer is running. Q - Quit timer is running. >> S - Switching timer is running. I - Interface timer is running. >> >> Local information: >> Hello Partner PAgP Learning Group >> Port Flags State Timers Interval Count Priority Method Ifindex >> Fa0/21 SC U6/S7 H 30s 1 128 Any 5013 >> >> Partner's information: >> >> Partner Partner Partner Partner Group >> Port Name Device ID Port Age Flags Cap. >> Fa0/21 Cat1 000a.8a4b.a400 Fa0/21 26s SC D0001 >> >> Age of the port in the current state: 0d:00h:00m:25s >> >> Port: Fa0/22 >> ------------ >> >> Port state = Up Mstr In-Bndl >> Channel group = 13 Mode = Desirable-Sl Gcchange = 0 >> Port-channel = Po13 GC = 0x000D0001 Pseudo port-channel = Po13 >> Port index = 0 Load = 0x00 Protocol = PAgP >> >> Flags: S - Device is sending Slow hello. C - Device is in Consistent state. >> A - Device is in Auto mode. P - Device learns on physical port. >> d - PAgP is down. >> Timers: H - Hello timer is running. Q - Quit timer is running. >> S - Switching timer is running. I - Interface timer is running. >> >> >> Local information: >> Hello Partner PAgP Learning Group >> Port Flags State Timers Interval Count Priority Method Ifindex >> Fa0/22 SC U6/S7 H 30s 1 128 Any 5013 >> >> Partner's information: >> >> Partner Partner Partner Partner Group >> Port Name Device ID Port Age Flags Cap. >> Fa0/22 Cat1 000a.8a4b.a400 Fa0/22 2s SC D0001 >> >> Age of the port in the current state: 0d:00h:00m:27s >> >> Port-channels in the group: >> --------------------------- >> >> Port-channel: Po13 >> ------------ >> >> Age of the Port-channel = 0d:00h:00m:34s >> Logical slot/port = 2/13 Number of ports = 3 >> GC = 0x000D0001 HotStandBy port = null >> Port state = Port-channel Ag-Inuse >> Protocol = PAgP >> Port security = Disabled >> >> Ports in the Port-channel: >> >> Index Load Port EC state No of bits >> ------+------+------+------------------+----------- >> 0 00 Fa0/19 Desirable-Sl 0 >> 0 00 Fa0/21 Desirable-Sl 0 >> 0 00 Fa0/22 Desirable-Sl 0 >> >> Time since last port bundled: 0d:00h:00m:32s Fa0/22 >> >> Cat3(config-if-range)# >> >> >> >> -----Original Message----- >> From: John [mailto:[EMAIL PROTECTED] >> Sent: Sunday, July 06, 2008 2:29 PM >> To: Marvin Greenlee >> Cc: [email protected] >> Subject: Re: [OSL | CCIE_RS] Section 5 VolI version 1 etherchannel over >> dot1.q confusing explanation >> >> Marvin, >> >> >> 2008/7/6 Marvin Greenlee <[EMAIL PROTECTED]>: >>> I believe you are referring to section 5.9. >>> >>> Could you be a little more specific as to what part of the explanation is >>> confusing you? >> >> Yes, read ahead. >> >>> Is it that the section doesn't explicitly state that you should create an >>> etherchannel link? >> >> No, it is clear that an etherchannel has to be created. >> >> >>> Is it that the solution chose to demonstrate how to configure using PAgP >> and >>> LACP? >> >> No, a little variation is fine. >> >>> Marvin Greenlee, CCIE #12237 (R&S, SP, Sec) >>> Senior Technical Instructor - IPexpert, Inc. >>> Telephone: +1.810.326.1444 >>> Fax: +1.810.454.0130 >>> Mailto: [EMAIL PROTECTED] >>> >>> Progress or excuses, which one are you making? >> >> Progress :) >> >> I will explain to you the process which goes through my mind as I am >> reading section 5.0 >> I have to be totally honest with you to do this, so please don't get >> me wrong as I am not into >> offending anyone! >> >> Imagine you are a student, learning this for the first time. You want >> to concentrate on the >> technology and not on the topology because that is something for later >> on as you are making >> progress. >> >> Here comes the problem, the topology is too complex for the purpose it >> needs to serve. >> This makes the student having his/her attention distracted from the real >> meat. >> >> At page 139; "We also need to pick.... "ALL THREE" of the links! >> >> >From there on something happens with my thought process because I have >> to look once >> again to the topology to be able to see what you are referring to. >> What happens with my thought process is that the first block comes >> into play, I begin to find >> the example not to the point.. still I proceed. >> >> On page 140 you lost me, at that moment my mind tells me that it can't >> be such a hassle to >> configure an etherchannel through a dot1q tunnel and I lost the point >> you want to make. >> Then I see you say " Excellent!" and I didn't even see a "show >> etherchannel summary" at the >> end. At that moment I am all confused. >> >> My next action is to clarify things to myself as fast as possible to >> get rid of this confusion >> ( I don't like to be confused ;) ) >> So I pick four switches and build an end to end etherchannel between >> the two outer switches >> using dot1q tunneling in the middle. Then I say to myself, ok this is >> it.. it works, but then what is >> it that they wanted to tell me in the proctor guide?... What is the >> insight that I might have missed? >> >> Then I look at the example a couple of times, and then I think.. o >> well.. I know how to do it.. so I >> will stop pondering and move on. But still I can't let it loose so I >> write an email to the list. >> >> >> Regards, >> >> John >> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf Of John >>> Sent: Sunday, July 06, 2008 5:02 AM >>> To: [email protected] >>> Subject: [OSL | CCIE_RS] Section 5 VolI version 1 etherchannel over dot1.q >>> confusing explanation >>> >>> Volume I workbook Version 10 Section 5 Layer2 Tunneling >>> >>> I think that the explanation in particular when the etherchannel has >>> to be made over >>> 802.1q tunneling, can be confusing to (some) students. >>> >>> If I read it myself I can't see why it has been explained like it is >>> explained now. >>> It can be that the writer wants to show something which at this point >>> I don't see. >>> >>> To have a balance I took the internetworkxepert Vol I version 5 >>> Technology Workbook >>> >>> Here it is task 1.17. The task is is very clear and to the point. As a >>> student you will see >>> what you need to do to get an etherchannel working over a dot1.q link. >>> There is barely any explanation given, but granted, this is a beta >> product. >>> >>> >> >> >> >> >> -- >> Tyson Scott - CCIE #13513 R&S and Security >> Technical Instructor - IPexpert, Inc. >> >> Telephone: +1.810.326.1444 >> Fax: +1.810.454.0130 >> Mailto: [EMAIL PROTECTED] >> >> Join our free online support and peer group communities: >> http://www.IPexpert.com/communities >> >> IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On >> Demand and Audio Certification Training Tools for the Cisco CCIE R&S >> Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and >> CCIE Storage Lab Certifications. >> >
