May 28

Cisco Prime Infrastructure shows the wrong controller version

After upgrading 800+ Cisco Wireless LAN Controllers from Cisco Prime Infrastructure (PI) 2.0 I was left with about 50 controllers that still showed the old version of software. At first I thought that I had missed those controllers so I checked the box next to them and selected to perform an FTP download to them. After clicking GO, the next screen displayed their current software version and it was the correct version, 7.0.250.0. When I went back to the list of controllers, it still displayed 6.0.188.0.


I found that with the controller displaying 6.0.188.0 in PI, PI would not push any templates out to those controllers. I believe this is due to the fact that PI 2.0 does not support any version below 7.X. I was able to delete the controller from PI, then rediscover it and it came in correctly at version 7.0.250.0. I didn’t want to do this because it loses the history of what templates I have pushed to that controller. If PI loses the history of what template was pushed, you will then lose the ability to delete that part of the configuration on the controller.

The fix to this issue is in the Lifecycle theme. In the classic theme I have refreshed the config from the controller, but that didn’t fix the issue. You have to go into the Lifecycle theme, then find the controller under OPERATE –> DEVICE WORK CENTER. From the Device Work Center you can sort and find your device. Once you find the device, click the check box next to it and click the SYNC button. Once PI 2.0 is done with the SYNC, it should display the correct software version. This SYNC may a few minutes.

Has anybody else run into this same problem? If so, please let us know.

Apr 22

Mass upgrades with Cisco Prime Infrastructure 2.0

Cisco Prime Infrastructure (PI) is supposed to make managing your wireless controllers easy. One way that PI helps with the work load is with software upgrades on your wireless LAN controllers (WLC). If you only have a few controllers, the software upgrade is pretty easy and very manageable. Depending on your network, you could have 700 or more controllers to manage. When you have this many controllers, logging into each one to perform a software upgrade is not manageable.

If you have a lot of controllers to upgrade and have to do the upgrade after hours, PI can do it for you. The process is very simple,


STEPS
1. Select the controllers
2. Schedule the date, time, Reboot Type
3. Select the software image and FTP server (or TFTP)
4. Sleep through the upgrade

1. SELECT THE CONTROLLERS

Select similar controller models (CONFIGURE –> CONTROLLERS). Make sure the controllers you select can all go to the software version you are moving to. Selecting the controllers in PI could be a challenge. I prefer to sort the controllers by Software Version. If you are moving to 7.0.250.0 (Latest as of the writing of this post), then select the controllers at a lower version.

If you are using the PI Server/Appliance as the FTP server, I found 20 software downloads at a time is about all it can do. If you do more downloads at the same time, the failure rate increases. Do some testing on your network to see if it works better.

After you select your controllers, In the upper right select “DOWNLOAD SOFTWARE (FTP)” then click “GO”.

2. SCHEDULE THE DATA, TIME AND REBOOT TYPE

The next screen will list the controllers you have selected and the current software version.
– Click the radio button next to “Scheduled”.
– Enter a name in the “Task Name” Field
– To the right of “Reboot Type” Click the radio button next to “Automatic”
– This will cause the WLC to reboot after the software has been downloaded and installed.
– Select the Date and Time
– Enter the FTP Username
– Enter the FTP Password
– FTP port defaults to 21

3. SELECT SOFTWARE IMAGE AND FTP SERVER

I prefer to use FTP over TFTP because it is more reliable.
– To select an FTP server, click the radio button next to “FTP Server”
– Server Name, Default Server
– Enter the IP address of the FTP server, I use the PI appliance and it enters /localdisk/ftp for the location. That is the location where I have the file.
– No matter what FTP server you use, you need to make sure that it has the file and the username/password work.
– Enter the file name.
– Click “DOWNLOAD”

Now the job is scheduled and will run at the selected time. To view this task go to CONTROLLER –> SCHEDULED CONFIGURATION TASKS –> DOWNLOAD SOFTWARE. Once you are there, look for your task name. You can go to this same location after the job ran to see the results.

You need to do some testing to see how long the download takes. You may want to schedule 20 controllers every 15 minutes throughout your maintenance window. Maybe your FTP server can handle more or less and maybe it takes less or more time.

How do you know what WLC you already have scheduled when you go back to your list to schedule the next group? Cisco made it very simple, they put a little scheduled icon next to the current software version. When you list your controllers (CONFIGURE –> CONTROLLERS) you will see the following image next to the software version of controllers that are already scheduled.

PI Scheduled Job Icon

PI Scheduled Job Icon

I don’t advise doing this over the WAN with 4404 WLCs. I have had 4404s crash while performing an FTP image transfer over a T-1 connection. Cisco does recommend transferring the image over the LAN, not the WAN. On the flip side, I have upgraded hundreds of 2100s WLCs over the WAN with FTP.

Have you performed mass software upgrades with Prime Infrastructure and if so, how did it go?