Cisco apologizes for the inconvenience. Prime Infrastructure 22.214.171.124 is now available.
As well, due to the timing of releases of different product lines, NCS 126.96.36.199 cannot be migrated into Prime Infrastructure 188.8.131.52. NCS 184.108.40.206 will be able to be migrated into a later release of Prime Infrastructure. The situation is similar with NCS 220.127.116.11, which is FIPS compliant; it will not be able to be migrated into Prime Infrastructure until a FIPS compliant release of Prime Infrastructure becomes available.
If you have an HA setup, it's important to note that HA must be REMOVED (not just disabled) prior to starting an upgrade. Administration > High Availability > HA Configuration > Remove button.
If you're having trouble with your existing NCS 18.104.22.168 or NCS 22.214.171.124 installation, don't assume that upgrading to Prime Infrastructure will fix them. Consider upgrading to NCS 126.96.36.199 and stabilizing NCS before moving on to Prime Infrastructure.
Upgrading the database is a very intricate process and it takes a very long time on large databases. TAC has seen upgrades take 10-12 hours, and as long as 23 hours, particularly during the "Schema Upgrade" and "Enabling DB Constraints" steps. Please be patient and let the upgrade complete.
Upgrading is a 2 step process. Go to the NCS Patches page and choose the patch that coincides with the version of NCS you're running.
Then go to the Prime Infrastructure 1.3 Software page and choose the Prime Infrastructure upgrade file, PI-upgrade-bundle-188.8.131.52.tar.gz. Be sure to check the files' sizes and MD5sums before continuing. Nothing slows down an upgrade like corrupted downloads.
TAC has found that upgrades to Prime Infrastructure go much quicker when the files actually reside onboard the VM. To leverage the FTP server built into Prime Infrastructure, make the FTP server's root directory into a repository. You can use the commands
to create the repository. You can then use any FTP client application with the built-in user "ftp-user" to get the necessary files into the repository. Be sure to use a binary transfer to put the file into the FTP server.
Once the files are onboard (show repo localftp), the first step, patching the NCS installation, is initiated with the command
A patch for Prime Infrastructure 184.108.40.206 has been released, PI_220.127.116.11_Update_1-12.tar.gz, which fixes a number of backup/restore issues, reduced the size of the backup.tar.gpg that the backup process produces and several other fixes. It's highly recommended to upgrade to this newest patch with the command
Hi,I wonder if the community can advice on the problem below.I'm configuring a stack of C9800 16.12.1And I want to configure HTTP authorization via AAA.First it should ask Radius, then go Local.The Radius is not available now, but the WLC refuses to log i...
Is there a guide or any documentation regarding hosting a 5508 or any physical WLC in a colo? The Management IP and VLAN ID will change. All of the APs connection to it will be in Flex Connect mode. Do I need to worry about changing the I...
Somehow I did not receive an email notification about my eap certificate was expiring and now I have an expired EAP/admin certificate. What I need to know is what will be the production impact when I install the new certificate? I am going to ...
Working on an upgraded wireless deployment. Customer used to have 5508 WLCs and a mix of 3602 and 3502 AP. Recently upgraded them to new C9800 WLCs and 9117 APs. I have an SSID that iPad's connect to that is configured as WPA2/AES PSK wi...