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 ME 220.127.116.11 setup with 4x3802s and 2x3702s. On the ME Controller's Network Summary screen for the APs I'm seeing Throughput from the 3702s with no clients associated. When I disable the radios on the 3702s the Throughput drops to zero. The 4x3802...
Hi Team, With two Cisco WLC’s added to Cisco DNA, Both WLC’s read as reachable / Managed & compliant. But every time we configure them as a HA pair the WLC always displays as Non-Compliant within DNA. How can we make the HA configuration complian...
Hello! So with help I got my "root" AP set up and working perfectly fine with 2 SSID's; House0fM vlan 10 and House0fMVPN vlan 11 and whichever SSID I connect to, goes to that vlan through the Catalyst Switch the AP is connected to, and works fine.The...
Hi All, Need your help on Wireless CCIE written exam code. As I passed Wireless CCIE exam 400-351 in year 2017. Now my certifications going to expire in May-2021, if I take Encore 350-401 exam in this case all my cisco certifications (CCNA (R&S),...