Cisco apologizes for the inconvenience. Prime Infrastructure 18.104.22.168 is now available.
As well, due to the timing of releases of different product lines, NCS 22.214.171.124 cannot be migrated into Prime Infrastructure 126.96.36.199. NCS 188.8.131.52 will be able to be migrated into a later release of Prime Infrastructure. The situation is similar with NCS 184.108.40.206, 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 220.127.116.11 or NCS 18.104.22.168 installation, don't assume that upgrading to Prime Infrastructure will fix them. Consider upgrading to NCS 22.214.171.124 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-126.96.36.199.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 188.8.131.52 has been released, PI_184.108.40.206_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
I have a few AIR-CAP3502E-A-K9 access points that I want to change to Lightweight mode. I did a lot of researching and found that I needed the ap3g1-k9w7-tar.153-3.JAB.tar file or a similar version of it.I do have that file and I was able to upload ...
Hallo,I have a switch SG350 with its basic configuration, I am still building my network. In the meantime I got WAP571 which is directly connected to the switch. I did initial configuration and I can connect to access point but there is NO INTERNET ACCESS...
I'm trying to modify an existing DHCP servers configuration on a wireless interface in a Cisco WLC, however, once I Apply the change the below message prompts: "Error: Invalid IP address. The IP address entered is a Broadcast IP address".Obviously there i...
Is it possible to perform the "config 802.11a disable network" and "config 802.11b disable network" or the GUI equivalent on a select group of APs? We currently have several sites all terminating on the same WLC with APs organized into separate AP g...
Hi, I'm using DNA Spaces and some options appear greyed out, like BLE Manager, Location SDK and Detect and Locate. Why is that? How can I gain access to them? I read on the configuration documents that I can locate devices conected to the network, that wo...