Yes that doesn´t work anymore in 7 code. I am 7.0.220 atm, don´t know if it makes difference.
Show run-config and show running-config gives me the same output. It seems to me that more people are noticing it. show run-config Press Enter to continue... System Inventory NAME: "Chassis" , DESCR: "4400 Series WLAN Controller:50 APs" PID: AIR-WLC4402-50-K9, VID: V02, SN: xxxxxxxxxxxx Burned-in MAC Address............................ 00:21:55:07:B3: show running-config (Sensa-4402) >show running-config Notice: "show running-config" has been changed to be an alias to "show run-config". Use "show run-config commands" to display the configuration commands. Press Enter to continue or <Ctrl-Z> to abort... System Inventory NAME: "Chassis" , DESCR: "4400 Series WLAN Controller:50 APs" PID: AIR-WLC4402-50-K9, VID: V02, SN: xxxxxxxxxxxx no interfaces and vlan configuration commands as in 4.2 code. only when I TFTP upload the config and look at it from there. regards. Kristjan From: Jason Boyers [mailto:[email protected]] Sent: 8. júní 2012 11:58 To: Kristján Ólafur Eðvarðsson Cc: [email protected] Subject: Re: [OSL | CCIE_Wireless] CCIE_Wireless Digest, Vol 38, Issue 4 Have you tried the "show run-config commands" command for getting the interface config? That may help you. Jason Boyers On Jun 8, 2012 6:37 AM, "Kristján Ólafur Eðvarðsson" <[email protected]<mailto:[email protected]>> wrote: I am also in the process of re-evaluating my strategy since I have taken version 1 a couple of times and I am preparing for version 2. There are at least 2 things that I have to change as it seems to me. When configuring a lot of common interfaces/VLANs on the WLC´s I used to like the idea of creating the first set in GUI. Then take the show run copy/paste to notepad. Modify and paste to other WLCs. In version 7 however show-run doesn´t work as it used to. So it doesn´t show the config as it should be pasted in. The only way today (it seems to me at least) is to TFTP upload the config file and edit it from notepad. But that defeats the purpose of being faster :) So I am going to use CLI from the start to do as much as possible and notepad with the Controllers and of course with the autonomous. I onlny use the WEB gui on autonomous when there is something I don´t do that often like configuring specific QOS,TSPEC e.t.c then the autonomous might help you. Some people use the GUI in autonomous to create the VLANs to avoid typos in bridge groups, vlans e.t.c. another thing that I discovered was if you keep the interface names consistent in WLC. VLAN names and all names in lower cases when possible. According to requirements of course. When doing common configuration for many WLC´s from WCS. You may use the WCS template to tie WLANS to Interfaces which usually doesn´t work becusae the interfaces on each WLC is different and doesn´t get published in the WCS template configuration dialog. So by keeping the vlan names consistent in WLC´s it saves a lot of time instead of deploying a WLAN template that points to the managment interface of each WLC (that is usually the only common thing) and then go to each WLC and rectify the WLAN to the correct VLAN interface. That takes time and can´t be forgotten. Another good thing is the WISM´s are gone and replaced by 5508s. This probably means we are short of 2 controllers as each WISM has 2 controllers. This can be confusing when the time is ticking and after a long lab you easily make mistakes :D so I guess it is a little simpler with regards of creating many VLANs and intefaces. my 5 cents. regards. Kristjan -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of [email protected]<mailto:[email protected]> Sent: 7. júní 2012 16:00 To: [email protected]<mailto:[email protected]> Subject: CCIE_Wireless Digest, Vol 38, Issue 4 Send CCIE_Wireless mailing list submissions to [email protected]<mailto:[email protected]> To subscribe or unsubscribe via the World Wide Web, visit http://onlinestudylist.com/cgi-bin/mailman/listinfo/ccie_wireless or, via email, send a message with subject or body 'help' to [email protected]<mailto:[email protected]> You can reach the person managing the list at [email protected]<mailto:[email protected]> When replying, please edit your Subject line so it is more specific than "Re: Contents of CCIE_Wireless digest..." Today's Topics: 1. Lab strategy thoughts? (Jeff Rensink) 2. Re: Lab strategy thoughts? (Blake Krone) 3. Re: Lab strategy thoughts? (Jason Boyers) ---------------------------------------------------------------------- Message: 1 Date: Wed, 6 Jun 2012 12:29:17 -0500 From: Jeff Rensink <[email protected]<mailto:[email protected]>> To: [email protected]<mailto:[email protected]> Subject: [OSL | CCIE_Wireless] Lab strategy thoughts? Message-ID: <cag4_piu-tulfyx5d4wvovw5j0_z7-drwbv37wne23n9cycx...@mail.gmail.com<mailto:cag4_piu-tulfyx5d4wvovw5j0_z7-drwbv37wne23n9cycx...@mail.gmail.com>> Content-Type: text/plain; charset="iso-8859-1" I'm starting to think about lab strategy to help guide my hands-on practice. I have a few thoughts as to order of operations and config methods. But I wanted to see what the group thought and what has worked well for them. In terms of an order of operations, what have you found to be useful? Obviously, to start things off you will want to read through the lab, write out your own diagrams and any other initial notes to help organize the information in a meaningful way. I'm more looking to see which sections/technologies should be done first and which can wait until later. When it comes to picking your sections/tasks to work on, what has been your order of operations? Another area that I wonder about is what is the most efficient way to make your configurations. On the WCS and autonomous APs, we have both CLI and GUIs. We also have the WCS that can be used to configure WLCs and their associated APs. What have you found to be the most efficient method to make your configurations? Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: </archives/ccie_wireless/attachments/20120606/dba9bce8/attachment-0001.html> ------------------------------ Message: 2 Date: Wed, 6 Jun 2012 14:07:38 -0500 From: Blake Krone <[email protected]<mailto:[email protected]>> To: Jeff Rensink <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [OSL | CCIE_Wireless] Lab strategy thoughts? Message-ID: <CAE8-+duKo2JwNw3xaA7=1bu-kc3pq-vo_weo-xfaxoz1i6b...@mail.gmail.com<mailto:[email protected]>> Content-Type: text/plain; charset="iso-8859-1" Jeff when I went through the lab I started off like you suggested reading the entire workbook and paraphrasing in my own way. I also circled things that required radios to be done or should be done together. WCS can be used to do similar tasks on the WLCs and I would suggest using that if you are comfortable with it. I also used the CLI heavily, most of my tasks were done in notepad and then copy/pasted over. Learn autonomous CLI inside and out, seen as the GUI is so slow you'll be wasting time for page loads. Without breaking NDA can't really offer much as to which sections/tasks to do first, but there will be a very obvious order that you should complete the lab in, or at least I thought there was. On Wed, Jun 6, 2012 at 12:29 PM, Jeff Rensink <[email protected]<mailto:[email protected]>> wrote: > I'm starting to think about lab strategy to help guide my hands-on > practice. I have a few thoughts as to order of operations and config > methods. But I wanted to see what the group thought and what has > worked well for them. > > In terms of an order of operations, what have you found to be useful? > > Obviously, to start things off you will want to read through the lab, > write out your own diagrams and any other initial notes to help > organize the information in a meaningful way. I'm more looking to see > which sections/technologies should be done first and which can wait until > later. > > When it comes to picking your sections/tasks to work on, what has been > your order of operations? > > > Another area that I wonder about is what is the most efficient way to > make your configurations. On the WCS and autonomous APs, we have both > CLI and GUIs. We also have the WCS that can be used to configure WLCs > and their associated APs. What have you found to be the most > efficient method to make your configurations? > > > Jeff > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, > please visit www.ipexpert.com<http://www.ipexpert.com> > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com<http://www.PlatinumPlacement.com> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </archives/ccie_wireless/attachments/20120606/d598d5af/attachment-0001.html> ------------------------------ Message: 3 Date: Wed, 6 Jun 2012 15:33:28 -0400 From: Jason Boyers <[email protected]<mailto:[email protected]>> To: Jeff Rensink <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [OSL | CCIE_Wireless] Lab strategy thoughts? Message-ID: <calo5k2tiings37t1cnuc6w_3cebch4elrkayyjunudct9my...@mail.gmail.com<mailto:calo5k2tiings37t1cnuc6w_3cebch4elrkayyjunudct9my...@mail.gmail.com>> Content-Type: text/plain; charset="iso-8859-1" In general, here are my recommendations: 1) Quickly review the test doc and diagram while reading 2) Configure the switched network/routing/wired QoS/multicast section, since everything is dependent on that working properly. 3) Configure autonomous APs section. You should finish these (#1-3) in about 3 hours. In San Jose, that gets you to lunch. Be sure to save configs regularly! Then, I rebooted before going to lunch. 4) Do a minimal config of the WLCs. Basically, items that are individually applicable to a controller (interfaces), items that are easy to copy and paste (mobility and rf group names), and anything that would require the WLCs to be rebooted (adding certs, SNMPv3, etc.) Notepad is your friend, with copy and paste. Be careful to change things as necessary for each WLC. 5) Import the WLCs into WCS. Then configure WLCs using templates, but don't use WLC Config Groups - they take too much time for the test. This would also include configuring the video and voice section. 6) Finish configuring WCS and add the MSE. 7) Configure clients for connectivity. 8) You should have 1-2 hours left at this point to validate the configurations. Now, there should be some general validation going on throughout (can you ping??) This is doing full validations. This was a successful process for me. One key is to figure out how to do each part of the process the fastest for you. I listed what worked for me. Another is to have that time at the end. You will misread and fat finger things. You need time to review what you've configured. Hope this helps. Jason Boyers, CCIE #26024 (Wireless) Blog: netboyers.wordpress.com<http://netboyers.wordpress.com> On Wed, Jun 6, 2012 at 1:29 PM, Jeff Rensink <[email protected]<mailto:[email protected]>> wrote: > I'm starting to think about lab strategy to help guide my hands-on > practice. I have a few thoughts as to order of operations and config > methods. But I wanted to see what the group thought and what has > worked well for them. > > In terms of an order of operations, what have you found to be useful? > > Obviously, to start things off you will want to read through the lab, > write out your own diagrams and any other initial notes to help > organize the information in a meaningful way. I'm more looking to see > which sections/technologies should be done first and which can wait until > later. > > When it comes to picking your sections/tasks to work on, what has been > your order of operations? > > > Another area that I wonder about is what is the most efficient way to > make your configurations. On the WCS and autonomous APs, we have both > CLI and GUIs. We also have the WCS that can be used to configure WLCs > and their associated APs. What have you found to be the most > efficient method to make your configurations? > > > Jeff > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, > please visit www.ipexpert.com<http://www.ipexpert.com> > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com<http://www.PlatinumPlacement.com> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </archives/ccie_wireless/attachments/20120606/218afb5d/attachment-0001.html> ------------------------------ _______________________________________________ CCIE_Wireless mailing list [email protected]<mailto:[email protected]> http://onlinestudylist.com/cgi-bin/mailman/listinfo/ccie_wireless End of CCIE_Wireless Digest, Vol 38, Issue 4 ******************************************** _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com<http://www.ipexpert.com> Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com<http://www.PlatinumPlacement.com>
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
