Nov 19

Cisco Prime Infrastructure 2.0 upgrade.

Over the past year I have struggled with Cisco’s Prime Infrastructure (PI). I have had problems with it slow performance, slow logins, maps not displaying wireless access points, maps not displaying the mesh links, taking a long time to load and parser error after parser error after parser error. I have upgraded from 1.1 to 1.2 to 1.3 for the simple fact that the performance was poor. At one point Google Chrome pushed out update 29 and that broke PI. FireFox was the only browser that would work and that gives an error stating that it’s not a supported browser.

After 2.0 was release on September 3, 2013, I waited a while before upgrading. I don’t like upgrading to a Dot Zero release. I was waiting for a patch to come soon after 2.0 was release. After two full months, there has yet to be a patch release for PI 2.0. In that time though, the performance of my two PI servers was degrading. More people from the help desk and the lobby admin were complaining that the product was not usable. I had to move to PI 2.0.

After reading the release notes, I found out that there was a patch to 1.3.0.20 to resolve the parser errors in Google Chrome version 29. Below is the patch details and name. This patch was release on September 4, 2013.

Apply this patch over existing Prime Infrastructure 1.3.0.20 to fix the issue introduced in Google Chrome 29 build, which broke Dojo Toolkits query interface.
PI_1_3_0_20-Update.1.12.CSCui77571-2.tar.gz

This patch took about 15 minutes to install. After the patch was installed, the product became usable again. The help desk staff and the lobby admin were able to perform their work in PI with out parser or any more rendering issues.

After you install this patch, the only way to know that it was installed is to issue the “show version” command at the CLI. At the bottom you will see the following line.

Cisco Prime Network Control System
——————————————
Version : 1.3.0.20
Patch: Cisco Prime Network Control System Version: Update.4.16

I had opened a case on this issue with Chrome and the Cisco TAC engineer informed me that this was a known bug and told me to use Firefox. It would have been nice to be put on a distribution list and notified when the patch was release. Maybe you can ask your Cisco Sales staff to add that feature in the future!!

Next was the upgrade to 2.0. On my appliance, it took about 75 minutes from the time I executed the install. I had around 1,000 APs in my server when I did the upgrade. I assume it will take longer with more maps and more APs. After the install the login screen showed version 2.0. The single command install worked very!! Maps loaded all of the APs in a timely manor, Mesh links on the map were displayed, the server lag was gone.

Here are the steps for installing the PI 2.0 upgrade from 1.3.0.20. Your upgrade may be different and I suggest you read the release notes to make sure you get the correct patch installed before going to 2.0.

Prime Upgrade from Version 1.3.0.20 to 2.0

1. Read Release notes for version 2.0
2. Perform a backup and copy the back up off to another server.
3. Download files from Cisco.com (Requires CCO account)
1. PI_1_3_0_20-Update.4-16.tar.gz
2. PI-Upgrade-2.0.0.0.294.tar.gz
4. Use SCP to transfer these files onto the Prime Infrastructure server
1. Log into Prime via the username you setup, not ROOT.
2. Place files in the defaultRepo folder
5. Install the patch PI_1_3_0_20-Update.4-16.tar.gz
6. Install the upgrade PI-Upgrade-2.0.0.0.294.tar.gz

———–PATCH INSTALL———–

CiscoPrime/Server# patch install PI_1_3_0_20-Update.4-16.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration…
Saved the ADE-OS running configuration to startup successfully
Initiating Application Patch installation…

** After about 15 minutes it was complete **

———–UPGRADE INSTALL———–

CiscoPrime/Server# application upgrade PI-Upgrade-2.0.0.0.294.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration…
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade…
Stage 1 of 7: Transferring file …
— complete.
Stage 2 of 7: Unpacking file …
— complete.
Stage 3 of 7: Executing pre-install …

[WARNING] System will reboot after a successful installation of this package (after Stage 7).
After reboot, please login again into the server to check status.
No action required at this time. Continuing with Stage 3.

— complete.
Stage 4 of 7: Upgrading binaries …
— complete.
Prime Infrastructure Application installation completed

Stage 5 of 7: Retrieving system version …
— complete.
Stage 6 of 7: Updating Database Schema …
: This could take long time based on the existing data size.
Stage 1 of 5: Pre Migration Schema Upgrade …
— completed at: 2013-11-07 05:43:04.887, Time Taken : 0 hr, 4 min, 2 sec
Stage 2 of 5: Schema Upgrade …
: This could take long time based on the existing data size.
— completed at: 2013-11-07 05:54:42.908, Time Taken : 0 hr, 11 min, 37 sec
Stage 3 of 5: Post Migration Schema Upgrade …
— completed at: 2013-11-07 06:02:54.779, Time Taken : 0 hr, 8 min, 11 sec
Stage 4 of 5: Enabling DB Constraints …
— completed at: 2013-11-07 06:14:53.745, Time Taken : 0 hr, 11 min, 56 sec
Stage 5 of 5: Finishing Up …
— completed at: 2013-11-07 06:15:15.525, Time Taken : 0 hr, 0 min, 21 sec
— complete.
Stage 7 of 7: Re-enabling Database Settings …
— complete.
Upgrade Finished. Server is restarting . Please wait ..

% This application Install or Upgrade requires reboot, rebooting now…

Broadcast message from root (pts/1) :

The system is going down for reboot NOW!

Application upgrade successful

** After about 75 minutes it was complete **


Over time I will find more things that work and do not work in PI 2.0, I will try and add them to this post. I really hope that Cisco Prime Infrastructure 2.0 is a really great product. I could really use a great piece of software to manage my wireless networks.

Please reply and post the amount of time it takes you to upgrade to 2.0, Please include the following
– Version you are upgrading from
– Number of APs
– Number of Controllers
– Appliance or Virtual
– Time of install

Here is my information
Version = 1.3.0.20
APs = ~1,000
Controllers = 15
Appliance
Time of install = ~75 minutes

What success or failures have you had with Cisco Prime (Or NCS)?
Has PI 2.0 been stable and reliable for you?

Nov 05

“Network Busy” error on Cisco 7921G or 7925G IP Phone

I support wireless voice in multiple warehouses. These warehouses use the Cisco 7921G and the 7925G IP Phones. We started with the 7921Gs and moved to the 7925Gs when they became available. Many of the managers have become reliant on the use of these mobile IP Phones. As you can imagine, a warehouse is not the safest place for a mobile telephone. These phones often fall off of forklifts and golfs, unfortunately, I have to replace them more often then I would like.

Recently we made an order for some Cisco 7925G phones. I shipped four of them to the same location to replace broken phones. The onsite tech performed the initial configuration and added them to Cisco Unified Communications Manager (CUCM). I then received a call stating the new phones will not make a call and they give the following error “Network Busy”.


My first thought was Call Admission Control (CAC). I checked the phones to find that the location statement was wrong. I changed it and that didn’t resolve the issue. CUCM was not setup for CAC, all of the locations were given unlimited bandwidth between sites. I started looking into the CAC features on the wireless network. According to the configuration guides, everything looked correct.

After validating my configuration on CUCM and the Cisco 4404 Wireless LAN Controller (WLC), I decided to capture some debugs. Using the following debug command, I was able to figure out the issue.
debug cac all enable
I enabled the debug, then had the onsite tech try to make a call.

In the debug file, I did a search for deny, then fail.

I found the following fail entry.

*apfMsConnTask_0: Oct 30 14:28:40.566: 44:2b:03:55:FF:FF TSPEC from mobile (up = 6), Phy rate check failed.
*apfMsConnTask_0: Oct 30 14:28:40.566:
Not including un-operational rate 12 in TSRS IE

Phy rate check failed was the issue. The PHY is the minimum data rate that the phone will work at. This is a configurable item via the USB configuration through the phones web GUI. The phone was set to 12 Mbps, while the wireless network had a minimum data rate of 6 Mbps enabled. After changing the minimum PHY rate to 6 Mbps, the phone was able to make a phone call.

Minimum PHY Rate

Cisco 7925G IP Phone Network Profile Configuration

Everything pointed to a CAC issue, but the debug was the key to finding the problem with the data rates.

What issues have you had that resulted in a “Network Busy” error on the Phone?
Has anybody else found something other then CAC and the data rates to produce a “Network Busy” error on the IP Phone?
Has anybody run into this same issue?