I always assumed that this was the script that asked for the basic info when first booting and configuring a controller for the first time. Meaning it is a CLI only tool. I found a hint that there may be a web GUI version of this. Wanted to verify. I can't find any sign of this is the WLC user guide.
That is exactly what I expected. But one of the practice questions on the CD states otherwise. I am guessing it is time to chalk it up as yet another error in the practice questions.
CLI or GUI according to Cisco.
Configure the WLC for Basic Operation and Register the Lightweight APs to the Controller
Use the startup configuration wizard on the command-line interface (CLI) in order to configure the WLC for basic operation. Alternatively, you can also use the GUI in order to configure the WLC. This document explains the configuration on the WLC with the startup configuration wizard on the CLI.
After the WLC boots for the first time, it directly enters into the startup configuration wizard. Use the configuration wizard in order to configure basic settings. You can run the wizard on the CLI or the GUI.
The link took me to an EAP configuration link, not a Wizard Config tool page.... but, your statement seems to verify the practice question. I just didn't realize that I could use the GUI. I have always used the CLI when running the Wizard configuration tool.
Yup, there is a Web GUI version of the configuration wizzard for first time start up. Access it by connecting to "http://192.168.1.1" with a PC in the same subnet (/24) as the Service Port Interface, which is the 192.168.1.1 by default at first boot. Standard username/password of "admin/admin". It is all the same questions, just as a web page to step through instead. This is also available on the 526 by connecting directly from PC to the controllers port 1 which has a built in DHCP server which assign your PC 192.168.1.1 and you can then http to it at 192.168.1.1.
"... which has a built in DHCP server which assign your PC 192.168.1.1 and you can then http to it at 192.168.1.1."
Did you mean to say something on the order of, "...assign your PC an IP address in the same subnet ast 192.168.1.1...?"
It's more on the order of "I should go to bed and write these things in the morning when my brain is working." I missed two 0s...
The 526 has a built-in DHCP which will assign a PC that connects to it by standard Ethernet connection to its Port 1 the address 192.168.1.100. The 526 can then bereached at the web address http://192.168.1.1. So, the PC will be assigned 192.168.1.100, the 526 will be 192.168.1.1, and the PC can reach the controller to do the web based initial GUI by http://192.168.1.1. Note that it is http and not https... if you try https it will not redirect or work at all.
I guess another thing that has thrown me off is the fact that the only controllers I have really had hands on experience with are WiSM blades, which are slightly different as the have no physical service port.
When I have needed to "console" into one of these controllers, I just use the session command from my 6500 to "console" into a device. Same is true with my FWSM and CSM-S blades. I suspect any service module blade would be that way.
Along these lines, the WCS Config Guide at http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcs42cg.html contains some useful nuggets of information that fleshes out the book. I'm going through this and the 4402 Config Guide for the GUI stuff, among other things, but the system requirements section of the WCS doc also provides the standalone AP limits for the installations of the three server variants.
There are some nits that differ from the book not worth worrying about, but I've found reading the introductory paras of each section also provides different perspectives and different ways of explaining what's in Carroll's book, which helps to clarify my understanding.
Now that I've bragged about the WCS Config Guide ( http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcs42cg.html), on page 2-3, it says in a Note that screen resolution "should be set to 1024 x 76 pixels for both WCS and Navigator." I assume that's a typo for 1024 x 768 pixels?