Cisco Prime Infrastructure 2.2 DVD install fails

We want to migrate to Prime 2.2, but management doesn't want the downtime of the appliance. Trying to install Prime 2.2 via DVD onto a Dell R300 server, and then import config from our appliance to test for issues. However, the NCS install fails due to a file issue. Second burned DVD fails as well. Has anyone tried this? Using a VM (at this point) is not an option.

I've not tried it but would not expect that to work.
The .iso image (DVD) is custom-built for installation onto the Cisco NCS hardware appliance. To install onto any other hardware, you would have to first have VMware ESXi hypervisor and install using the .ova image.

Similar Messages

Cisco Prime Infrastructure 2.1 Express OVA failing to boot up

Hi all, i'm wondering if you can help me, i'm trying to deploy Cisco Prime Infrastructure in a lab envrionment but it's not working correctly.
I've deployed "PI-VA-2.1.0.0.87-Express.ova" to a VMware ESXI 5.1U2 hypervisor with 2x AMD 8128HE CPUs, 96GB RAM, ASUS KGPE-D16 motherboard. The installation works fine, I can answer all the questions and enter the IP address. Once the system reboots, it hangs at the following screen:
"Kernel direct mapping tables up to 340000000 @ 10000-1c000" is the last thing I see
Interestingly at this point I can actually ping the VM... I cant connect to the managemnet console on HTTPS though :(
I did find some related info on a blog https://deekayen.net/kernel-alive-lock which mentions booting with "noapic", however when I try to press "P" on the grub boot loader it prompts me to enter a password which I dont know! My normal admin passwords arent working.
Any help to ge tthis running would be greatly appreciated
Thanks in advance
Ben

The server takes about 30 mins to boot up, it's not actually broken it's just extremely slow .. I have found numerous people reporting this issue online, and our production system also does this! I guess my original problem is solved, although I would prefer this issue not to exist!

Cisco Prime Infrastructure 2.1: SNMP Connectivity Failed

Hi,
I have discharged all my Cisco devices within Cisco Prime and after a few days and when everything worked correctly one of the switches is displayed with the SNMP error Connectivity Failed, nothing has been changed.
I deleted and i have returned to create the object but it continues to be the same, I've also tried to create another SNMP community still receiving the same error.
This is the configuration of snmp in the switch WS-C3850-48P with version 03.02.02.SE
snmp-server community "community" RW
snmp-server location "location"
snmp-server contact "contact"
snmp-server host 10.180.5.22 version 2c "community"
Best regards.

Hi ,
check if you are getting these errors in "show log" again:
%SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
If yes , then either a lot of SNMP polling happening on the device
or
CPU utilization is going high sometime , being SNMP as a least priority process , you will see this issue. check for "show proc cpu history"
It is a device side issue definitely.
I would suggest to apply a Access-list on the SNMP community string allowing only the
valid NMS to poll the device
Thanks-
Afroz
***Ratings Encourages Contributors ***

Cisco Prime Infrastructure v2.1 - Delete device fails

Hi.
I'm trying out PI, but I have come across an error.
I'm trying to delete a device (a WLC 5508), but I keep getting this error every time I try:
Delete Device(s) Failed: 172.29.254.6. Please see log for more information.
But there are about 200 log files in Prime, so does anyone know where I should be looking?
I had 2 similar controllers in Prime, the first one got deleted without problems. Strange.
Thanks.

Thank you, that helped.
I found what I needed in ifm_intentory.log
It seems there was a problem deleting the AP's associated with the WLC.
So I deleted the WLC only first, and the AP's next, and now it's gone.
One strange thing though: The WLC could be seen correctly under the Virtual Domain I added it in, but the AP's could only be see in the root Virtual Domain.
I will try to re-add it now, to see if they all end up in the right place this time.
Thank you for your help.

Installing Certificate from Microsoft CA (.pfx) in Cisco Prime Infrastructure 1.2

Hello,
we are trying to install certificates from our CA on our Cisco Prime Infrastructure 1.2
What we get from our colleagues is a file in .pfx format, containing an exportable key and the whole certificate chain.
On the prime server, using openssl 0.9.8, we exportet the key and converted the file to .pem.
When trying to install the certificate, we get the following error code:
prime# ncs key importkey key-nopw.pem newcert.pem repository certificate
INFO: no staging url defined, using local space. rval:2
ERROR: dowload of key-nopw.pem failed. rval:-200
Does anyone have an idea what formats can be used for prime ssl certificates and how to install them?
The official guide has only little information on how to make a csr and install the certificate.
Best regards,
Joerg

I solved the same problem 5min ago.!
select the device and press syc ..that helped me ...

Can i install Cisco prime infrastructure 1.3 with 1.1 license.

Can i install Cisco prime infrastructure 1.3 with 1.1 license.To be more precise it will be fresh installation
but the licenses I have is of 1.1.As per my overview from Cisco prime Infrastructure 1.2 NCS and NCS(WAN)
has been bundled into one service.But both were seperate entities in Cisco Prime Infrastructure 1.1.

It doesn't matter if you want to make a new installation or an upgrade. The questions is the license.
The base license is necessary for network management nodes (devices). But to get updates for your system you need the additional to your Base License the Lifecycle License (which can be ordered for 12, 24 or 36 months).
The Lifycycle License is also based on the number of managed devices. In your case 50 devices. So you have that License - congratulations!
Otherwise order the Lifecycle License for 50 devices (L-N-PI12-50-M). This generates CON-PSUU-PI12LF50 for 12 months, list price 414,81$. Then Upgrade from 1.1 to 1.2, patch the system and upgrade to 1.3.
Have fun,
Chris

Getting past "Fetch VLAN configuration - Command failed" errors in Cisco Prime Infrastructure 2.0 - How?

I've got a handful of devices in Cisco Prime Infrastructure 2.0 which show up in the "Archive Failed Devices" view. The "Failure Reason" is some variation of "Fetch VLAN configuration - Command failed" sometimes including "TELNET: Failed to establish TELNET connection to x.x.x.x". What does this mean? How do I overcome this? In all cases, the device is configured to use SSH and has valid SSH credentials. In all cases, I can SSH from the command line of the NCS appliance to the devices listed in the "Archive Failed Devices" view.

Hi
I was able to fix the "Fetch VLAN configuration - Command failed" by allowing tftp from the device to PI server in firewall. See if this can help.

Cisco Prime Infrastructure 2.0 import image via WAN link failed.

Cisco Prime Infrastructure 2.0 behind NAT that can copy image on device to Cisco Prime infra but can not deploy from Cisco Prime Infra import image from device. How to solve problem,please ?

Have you downloaded and applied the latest Device Pack updates?
PI enhanced ASA support after the initial 2.0 release and the Device Packs incorporate that change.
The README file for Device Packs explains how to install them. (A bug currently does not allow the direct download in PI so you need to follow the method for installation from local storage after you manually download. Here is a link to the download location.

User Name and Password for Cisco Prime Infrastructure 2.1

Hi all:
I am stuck at the login page of Cisco Prime Infrastructure 2.1.
I have tried using the user name root and its password (when log in with root at Vsphere Client) and also the login user name "before" get into the appliance infrastructure, all cannot work.
Anybody knows what is the default username or password or any way to set the username and password for this Cisco Prime Infrastructure 2.1 website?
Thanks!
tangsuan

Hi Tangsuan,
Following is the documented procedure for password recovery..
In order to modify the GUI root user password, you will need to login to the NCS CLI
as an admin user, and enter the command
"ncs password root password <new password>" (without the quotes)
This should set the web interface root user password :
http://www.cisco.com/en/US/docs/wireless/ncs/1.1/configuration/guide/manag.html#wp1268889
If you have lost your CLI password , try the default logging that is ,
CLI user is admin and not root, so please try logging in as admin with
the password that was set during setup. If that does not work , you need
the install disk that came with the appliance to recover that password.
Follow these steps:
Recovering a Lost Admin Password
If you lose or forget the admin password for NCS appliance, follow these steps.
Step 1 Reboot the NCS appliance with the ISO DVD inserted. The Cisco Prime Network Control
System Welcome screen appears:
ISOLINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin
             Welcome to Cisco Prime Network Control System
To boot from hard disk, press <Enter>.
Available boot options:
   [1] Network Control System Installation (Keyboard/Monitor)
   [2] Network Control System Installation (Serial Console)
   [3] Recover administrator password. (Keyboard/Monitor)
   [4] Recover administrator password. (Serial Console)
<Enter> Boot existing OS from Hard Disk.
Enter boot option and press <return>.
boot:
Step 2 Select the desired recovery option, 3 or 4, depending on how you
are connected to the appliance and then follow the prompts.
Thanks-
Afroz
***Ratings Encourages Contributors ****

Cisco Prime Infrastructure 2.0 and Cisco ASA

Hello,
We've recently installed trial version of Cisco Prime Infrastructure 2.0 Express. We hoped that it already supports Cisco ASA 55xx series (especially 5505, we have pretty amount of them). But we had some problems with PI and asa durind the exploitation process.
First, I've added ASA to PI, and Inventory Collection Status is Completed, but I can't see CPU and RAM utilization graphs. Inventory.logs are non-informative.
Also, config backup is success, but when I try to watch the backuped configuration at Configuration Archive PI says "Failed to fetch raw configuration". And so on.
ASA version is 5505, image is 9.1(2).
So, I have a question: is it possible to manage ASAs with PI 2.0?
UPD: I've just tried to upgrade asa to 9.1(4), and behavior of the equipment is quite the same. Seems we shall wait for 9.2 to be released.

Have you downloaded and applied the latest Device Pack updates?
PI enhanced ASA support after the initial 2.0 release and the Device Packs incorporate that change.
The README file for Device Packs explains how to install them. (A bug currently does not allow the direct download in PI so you need to follow the method for installation from local storage after you manually download. Here is a link to the download location.

Cisco Prime Infrastructure patch 2.1.1 - HA issue

Hello,
I have a problem with the Cisco Prime Infrastructure patched to version 2.1.1. I did exactly what Installation Guidelines say:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1-1/release/notes/cpi_rn.html
– Install the Prime Infrastructure 2.1.1 patch by using the Administration > Software Updates page on the primary server.
– Restart the primary server.
– Verify that the patch installation is complete. If you find the installation complete, decommission and reinstall the secondary server and add it back to the primary server.
I reinstalled HA server and I'm trying to add it to HA but I get "Failed to authenticate - Primary(xx.xx.xx.xx) and Secondary(xx.xx.xx.xy) PI version does not match"
Can you help me with that? What I'm doing wrong? or maybe this patch is not prepared to work in HA mode?
Regards

Symptom:
The installation instructions of PI 2.1.1 patch in a High Availability environment are not accurate and following these steps will result in the inability to re-pair the Primary and Secondary servers.
Conditions:
If the instructions are followed, then when the user attempts to re-pair the servers, an error will be encountered:
"High Availability Registration Failed - Failed to authenticate - Primary (x.x.x.1) and Secondary (x.x.x.2) PI version does not match".
Instead, the following steps have proved to work correctly:
1. Upload and install patch on primary.
2. Upload and install patch on secondary.
3. Stop NCS services on secondary
4. Stop NCS services on primary
5. Start services on secondary
6. Start services on primary
7. Re-pair HA servers from primary
Workaround:
Workaround 1:
On the secondary, go under root and issue:
# cd /opt/CSCOlumos/bin/
# ./hamode.sh primary
Answer 'yes' when prompted.
Go to admin user and execute
# ncs stop
After the services are stopped:
# ncs start
When the services are back up, login to the secondary GUI as you would login to a primary server
Go under Administration > Software update, upload the patch and install it.
Go to admin user and execute
# ncs stop
After the services are stopped:
# ncs start
When the services are up, go under root and issue:
# cd /opt/CSCOlumos/bin/
# ./hamode.sh secondary
Answer 'yes' when prompted.
Go to admin user and execute
# ncs stop
After the services are stopped:
# ncs start
After the message that services started successfully on the secondary, initiate a new High Availability configuration from the primary. Now the synchronization between the two servers should succeed.
Workaround 2:
Redeploy or reinstall the Primary server, restore the backup which was taken prior to applying the patch, reconfigure the High Availability and continue with the steps described in the Conditions section.
Further Problem Description:
Release Notes have been updated with more precise instructions.
Known Affected Releases:
(1)
2.1(0.0.85)

CISCO PRIME INFRASTRUCTURE 1.2 NCS ERROR

Hi everyone,
can anyone put through on this, i'm having issue starting the ncs server on cisco prime infrastructure 1.2 .below is the message i get when i do show ncs status:
NGPHC-CPR001/admin# ncs status
Health Monitor is running, with an error.
failed to start NCS on startup Health Monitor
Reporting Server is running
Ftp Server is running
Database server is running
Tftp Server is running
Matlab Server is running
NMS Server is stopped.
SAM Daemon is not running ...
DA Daemon is not running ...
Syslog Daemon is not running ...
status
thanks.

Hi Marvin,
Its has never worked. This is the first time i am installing it.
I haved done as you adviced but still getting the same error as stated above.
Please is there another way out.
thanks.

Upgrade NCS 1.1.1.24 to Cisco Prime Infrastructure 1.2

Having a problem installing the ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz patch file on a virtual NCS before upgrading it to Cisco Prime Infrastructure 1.2.
I've followed the Cisco Prime Infrastructure 1.2 Quick Start Guide and did not had the same success as described in the document (see below):
gmsncs/admin# dir disk:defaultRepo/
Directory of disk:defaultRepo/
508376482 Sep 13 2012 05:38:25 backup-20120913-0530.tar.gpg
853768584 Sep 20 2012 05:40:17 backup-20120920-0530.tar.gpg
     127019 Sep 26 2012 16:40:58 ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz
           Usage for disk: filesystem
                 1544204288 bytes total used
                27185573888 bytes free
                30293413888 bytes available
gmsncs/admin# patch install disk:defaultRepo/ncs_patch-1.1.1.24-upgrade-pi_1.2.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...
% Local file not found
Anybody experience with this procedure.
Thank You
--- Update ---
Skipped Step 4 and followed Step 5 in the Quick Start Quide, however now I receive a diffrent error:
gmsncs/admin# dir disk:/defaultRepo
Directory of disk:/defaultRepo
926193986 Sep 26 2012 17:48:12 GRDbackup-120926-1736.tar.gpg
508376482 Sep 13 2012 05:38:25 backup-20120913-0530.tar.gpg
853768584 Sep 20 2012 05:40:17 backup-20120920-0530.tar.gpg
     127019 Sep 26 2012 16:40:58 ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz
           Usage for disk: filesystem
                 2471309312 bytes total used
                26258468864 bytes free
                30293413888 bytes available
gmncs/admin# patch install GRDbackup-120926-1736.tar.gpg 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...
% Manifest file not found in the bundle
gmsncs/admin#

Hi, Thank you again for your help, but I am still stuck. I have gathered the outputs from ncs start and a ncs status afterwards. Currently I am not able to access the web-UI of NCS..
deberncs01/admin# ncs startStarting Network Control System...This may take a few minutes...Dependency Check Failed: Matlab is not running.Dependency Check Failed: Ftp is not running.Dependency Check Failed: Tftp is not running.Failure during Network Control System startup. Check launchout.log for details.startdeberncs01/admin#deberncs01/admin#deberncs01/admin#deberncs01/admin#deberncs01/admin#deberncs01/admin# ncs statHealth Monitor is running, with an error.failed to start NCS on startup Health MonitorReporting Server is StartingFtp Server is FailureDatabase server is stoppedTftp Server is runningMatlab Server is runningNMS Server is stopped.SAM Daemon is not running ...DA Daemon is not running ...Syslog Daemon is not running ...statusdeberncs01/admin#
Anyone got a clue on that? and where can I find that launchout.log on NCS? Thank you

Trouble With Cisco Prime Infrastructure 1.3

Hi,
I have installed the Evaluation Version Cisco Prime Infrastructure 1.3.
There are a few problems that i am facing;
I am trying to push a simple configuration to WLC using Prime Infrastructure. But it is failing as PI doesnot have RW SNMP access.
My question is that can I use PI to push configs without using SNMP. Like do it using ftp or something.
Also do the Wired Devices also need SNMP RW access on PI's part.
2. I tried running discovery for WLC and it worked fine where all the controllers were discovered. But when I try to discover a Switch, the reachability tab says Reachable but in Collection Status tab it shows Unmanaged. When I click on the Unmanaged tab it says " Pre-collection check failed because: ". I have configured the SNMP correctly.
3. I have the CAD files for all the maps in our environment but when I try to upload it to Prime it converts it into GIF, so the maps are uploaded as plain image with no knowledge of walls and obstacles.
So we would have to add the walls and obstacles by ourselves. Is there any way it can automatically pick up on the walls and obstacles and thus provide a better way for predicting RF profiles.
All your help is greatly appreciated.

TAC Case! Sounds like a bug to me...
Sent from Cisco Technical Support iPad App

Cisco Prime Infrastructure 1.3 - TFTP backup WLC not working

I don;t get the the background task "Controller Configuration Backup" working. I want to use default TFTP.
When i look in the logging i see 2 of three WLC's succesfully backuped there logging. Is their a log file where you can see what is happening?
With kind regards,
Martijn.

Hi Martijn:
If you go to the controller's GUI to Commands > Upload File and manually trigger the TFTP Configuration backup, does the process complete as expected? If not, whatever's causing that problem needs to be addressed first.
When someone wants to do a config backup from the command line, they give a series of commands
transfer download datatype config
transfer download mode tftp
transfer download serverip x.x.x.x
transfer download path ./
transfer download filename myBackup.cfg
transfer download start
The Controller Config Backup background task is just the SNMP version of "transfer download filename " and "transfer download start". If these other required settings aren't already there, the task isn't going to set them (the humans have to). If there's a problem with writing out the file on the server, or packet routing issues to get to the server, the task isn't going to see those things, it just knows that the answer to "transfer download start" wasn't "Okay!"
As for watching this processing in logs, go to Administration > Logging, and set the logging level to Trace for the modules SNMP and System, and click Save. Then kick off your backup attempt, allowing it to fail. When it does, return to Administration > Logging, and click the Download button to retrieve the logs.zip file. The activity should be in the ncs-x-x.log file.
If you don't have the new Update-1 patch for Prime Infrastructure 1.3.0.20 (filename PI_1.3.0.20_Update_1-12.tar.gz) installed, I'd suggest you get it. While it's not going to specifically address this issue, there are a lot of really good fixes in it.
Release Notes for Update 1 for Cisco Prime Infrastructure 1.3.0.20

Cisco Prime Infrastructure 2.2 DVD install fails

Similar Messages

Maybe you are looking for