Fail back unsuccessful in Prime Infrastructure 2.0

Fail back unsuccessful in Prime Infrastructure 2.0.
Getting foll error while starting NCS services:
health monitor running with an error....

Hi Yusuf,
there could be many reasons of the failure of the health monitor services ... could be a databases faulty..
If you have backup or if your PI was running on VM and you have some snap shot then I would suuggest you to Restore(backup) it.
***Try to reboot the server once before you try to restore the backup..
Thanks-
Afroz
****Ratings Encourages Contributors****

Similar Messages

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 1.2 - Remote FTPrepository Sizing Guide

Can anyone provide a link to a sizing guide for remote FTP repository for backing up Cisco Prime Infrastructure 1.2 to a remote FTP server?

A personal observation; In PI 1.1, with the small ova we were running around 300 AP's and I had noticable slowness and issues. At that time, TAC mentioned that I should go with the medium as it was a known problem Now, despite being on 1.2 and alot of the issues resolved (and now new ones), if faced with the need to start over and I could spare the hardware, I would still go with the medium. My personal opinion is that Cisco VM's require way to much. On the other hand, knowing that it's relying on a built in Oracle DB, which from my experience with virtual servers, databases in VM = bad, it's understandable. Not everyone agrees with this point from vm gurus to db geniuses, and I'm not a professional vm guy, just play one on tv, but personally i shove as much hardware as I can afford from my host at it if it's a db in a vm. This comes from being in an enterprise with multiple oracle db's in multiple vm environments. My 2cents.

Prime Infrastructure 2.1 - User add failed : Some unexpected internal error has occurred.

Setting up Prime Infrastructure to manage 2504 WLC, trying to add Lobby Ambassador and I get this error message:
User add failed : Some unexpected internal error has occurred. If the problem persists please report to the Tech Support.
Technically, this is my second attempt at setting up PI. I set it up initially with the wrong version of PI and created a lobby ambassador. I followed the instructions from the forum with a similar problem that said to remove the trap receiver on the WLC from my first attempt at installing PI.
https://supportforums.cisco.com/discussion/11110686/failed-add-device-wcs-reason-common-1-some-unexpected-internal-error-has-occured
I'm now able to add a Lobby Ambassador as long as its not the same username that I created on the previous PI setup. So I suspect this Lobby Ambassador username is somewhere on the 2504 WLC, but I can't find it anywhere to remove it.

I have just been struggling with a similar issue on a fresh install of Prime 2.1 Upgraded to 2.1.1.
If I try to create the user with lobby ambassador role it just fails with "unexpected internal error".
I eventually found that by creating the user as a normal admin user first - the user is added. You can then go in a remove the admin role and change the role to lobby ambassador. This works with no internal error and the lobby admin user is working fine.
I would say it is just a bug.

SCP IOS Image Upgrades in Prime Infrastructure 2.1 Failing

Hi I'm running PI 2.1 with all the latest patches and packs but I can't get SCP Image transfers to work.
When I check the suggested logs from the Jobs Dashboard (and jump into the CLI root) I see the following:
[SWITCH-DEVICE]=Switch Hostname
[SWITCH-ADMIN-LOGIN]=Level 15 username login to Switch, same username the is used in the Device Work Centre
[PRIME-INF-IP]=Prime Infrastructure Server
[SWITCH-DEVICE]#archive download-sw ............... archive download-sw /allow-feature-upgrade
/overwrite scp://[SWITCH-ADMIN-LOGIN]@[PRIME-INF-IP]//localdisk/tftp/c3560-ipbaselmk9-tar.122-55.SE9.tar
Password:
Password:
% Authentication failed.
Could not buffer tarfile...using multiple downloads
examining image...
Password:
Password:
% Authentication failed.
%Error opening scp://[SWITCH-ADMIN-LOGIN]@[PRIME-INF-IP]//localdisk/tftp/c3560-ipbaselmk9-tar.122-55.SE9.tar (Permission denied)
%Error opening flash:update/info (No such file or directory)
ERROR: Image is not a valid IOS image archive.
[SWITCH-DEVICE]#
It looks like the switch is trying to log into the PI server and download the software as opposed to PI sending the software to the switch.
I've used WinSCP to open up the URL, but none of the passwords I know or created work.
Do I need to SSH into the PI box and create a new CLI account (or Root CLI account) that matches up to the switch [SWITCH-ADMIN-LOGIN]?
Regards,

Hi rowansakul,
The work around for this particular issue involves having a user set up in the root cli and then from the the GUI navigate to Administration > System Settings > Image Management and set up the SSH Username with your new user account that you created under root cli. That is the credentials that Prime is looking for when it is attempting to access its own image repository.
Regards,
Brandon

Prime Infrastructure 2.0 and Nexus 5548, SSH credentials fail

Hi,
I'm having problem getting the Prime Infrastructure 2.0 to login with SSH to a Nexus 5548 to do an inventory. I get "Wrong Telnet/SSH credentials". But when I use the same credentials from another SSH-client it works fine. I also tested to SSH from the console of the Prime-server and that also works fine.
Any ideas???
Regards,
Stefan Lindkvist

I have PI 2.0 working against Nexus 5k's in two different installations. See below for an example (click to enlarge).
Have you put in an entry in both the login and enable fields (even though they are not separately required when logging in directly)?

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!

Prime Infrastructure v1.3 -- Boot fails, displays debug info

Prime website stopped responding so I logged onto the console (VM) and it had these debug errors on it. I rebooted and received same thing. This happened on a previous install as well.
However, I can SSH to the appliance, but the website doesn't load.
It's currently running on a VMware ESXI v5.0 host. The VM was setup using the PI-VA-1.3.0.20-medium.ova file. It was working fine since Friday, then after a little bit of using it this morning it crashed. It was managing three wireless controllers.

Hi Itregistrations:
The lines depicted are not actual "debugs" as if something had been turned on, they're actually messages thrown to the console by the Linux daemon whose name is "debugd" or debug daemon, that's watching what's going on as the Prime Infrastructure service starts up. They're not helpful at all in diagnosing a problem, but they will stay on screen a long, long time while the service is in the process of starting. Once it does completely start, a login prompt should appear.
What is helpful is connecting to an SSH session, checking the output of "ncs status" to know which of the listed services are running or stopped.
Also, a set of logs generated by running the command "backup-logs repository " is helpful. Logs always help, particularly the hm-0-0.log file that tells what the "mother hen" Health Monitor service encounters as it tries to start up all the subservices. Depending on which subservice is having trouble, the log of that subservice would be the next source of help. For example, if Health Monitor tells the database server to start, but the database server doesn't, one would want to check the dbadmin-0-0.log to see why the database server disobeyed Health Monitor.

Prime Infrastructure 1.3 new install web password fails

I just installed Prime Infrastructure v1.3 twice in our lab and the CLI access works but the web gui password does not. I know the CLI password is not the same as the web password so changing it there won't help. Where can I find this in the shell? What steps can I take to resolve this issue? Is there a troubleshooting guide that covers this?
Thanks, Karl

So you can login to the CLI using the admin login credentials?
So you can't login to the WebUI using the root login credentials?
If this is the case, try, from the CLI running ncs password root password

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.

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)

Using Windows Network Policy Server to authenticate Prime Infrastructure 1.4 admin access

I am using Prime Infrastructure 1.4 and I am needing to set up RADIUS Authencation. I am using Microsoft Network Policy Server. I have done all of the setup on both systems. I have matched up the settings the best I can on both systems. I am trying to use CHAP. I keep getting username or passwrod is not valid. In a effort to test I changed the Authentication type to PAP (I do not want to use this because it is not encrypted) But in a effort of testing I changed the setting on both the NPS and on Prime. I am now able to log in. Changing back to CHAP it fails and states the Username or Password is invalid. SO, PLEASE HELP!!!!

Ok, I was able to resolve this over the weekend. The actual fix is a little complicated. You can find the full explination here: http://technologyordie.com/windows-nps-radius-authentication-of-cisco-prime-infrastructure
The basics are that Prime (1.3 is the version I am using at this point) expects two AV pairs from radius. They are as as follows:
NCS:role0=Admin
NCS:virtual-domain0=ROOT-DOMAIN
"Admin" is the name of the group you would like your users to have access at and "ROOT-DOMAIN" is the name of the domain you would like them to have access to.
For TACACS+ I suspect the AV Pairs are going to be the same but I have not been able to test that.

Cannot add WLC 5508 v7.6.120.0 into Prime Infrastructure 2.1

Hi everyone
Hope you can help us with this issue.
We already configure the WLC using this guide: http://mrncciew.com/2013/02/14/configuring-snmp-on-wlc/
snmp v2: enable
snmp v1: enable
default port values
community: incaenic with ip and mask 0.0.0.0 to allow access from any network or ip
traps receiver: community: incaenic ip: 10.100.100.15
when we try to discover the WLC with the PI it gave the error "SNMP Connectivity Fail"
WLC is on subnet 10.100.102.0/24 and PI in 10.100.100.0/24; there is a Catalyst 3850 between then with no access list on then.
Did someone can guide us with this?
Best Regards.
Alvaro Rugama

Hi,
Which version of SNMP are you using?
If you are using v1/v2 you should be using community string rather than local database credentials?
Regarding the service port what is the ip address assigned on the service port. From the configuration guide "Prime Infrastructure uses the preferred management IP address from the loop back interface. If the device does not have a loopback interface, Prime Infrastructure uses similar logic to the OSPF algorithm to select the router’s preferred management IP address."
Hope that helps.
Regards
Najaf

Cisco Prime Infrastructure 1.2 Error

Hi,
I don't have any experience with Cisco Prime infrastructure. I am getting the below error
Unable to start secondary NCS server PRLPrimeNCS02 [10.140.xx.xx]
Reason: IO Error: could not resolve the connect identifier "wcss1"
Not sure exactly what the error means. Any help much appreciated.
Thanks
Nachi

Hi Scott,
Thank you for your email.
The HA is runing on the Cisco Prime. Runing Cisco Prime on a Virtual machine in VM.
The issue we are experiencing is that the system failed over to the secondary (HA) for unknown reasons. When we failed it back it didn’t fail back properly. Configured Manual failover. Managed to failback to primary but it complained HA was no longer configured.
Tried to remove HA and reconfigure it. The primary removed the HA configuration, but the secondary kept it. Here is some info on the secondary
PRLPrimeNCS02/admin# ncs ha status
[Server] prlprimencs01(10.xx.xx.xxx) [State] Secondary Lost Primary [Failover Type] manual
PRLPrimeNCS02/admin# ncs ha remove
High availability configuration will be removed
Do you wish to continue? (y/N) y
Removing secondary configuration will remove all database information
Do you wish to remove high availability configuration from primary? (y/N) y
Secondary is attempting to remove high availability configuration from both primary and secondary
Requesting primary to remove high availability configuration from both primary and secondary
Successfully removed high availability configuration
PRLPrimeNCS02/admin#
PRLPrimeNCS02/admin#
PRLPrimeNCS02/admin# ncs ha status
[Server] prlprimencs01(10.xx.xx.xxx) [State] Secondary Lost Primary [Failover Type] manual
PRLPrimeNCS02/admin#
And the primary
prlprimencs01/admin# ncs ha status
[State] Stand Alone
prlprimencs01/admin#
Below is the log
Starting Health Monitor as a secondary
Checking for Port 8082 availability... OK
truststore used is /opt/CSCOlumos/conf/truststore
truststore used is /opt/CSCOlumos/conf/truststore
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
java.lang.OutOfMemoryError: Java heap space
Dumping heap to logs/java_pid6044.hprof ...
Heap dump file created [249907589 bytes in 6.857 secs]
Thanks
Nachi

Running Prime Infrastructure in HA mode but the primary server won't take over from the secondary

We're running Cisco Prime Infrastructure 1.3 in High Availability mode, or atleast we're supposed to.
At first everything seemed fine. We were using the primary server and the failover worked without a hitch when we tried it.
Then the problems started. I think it was at the same time as we increased the disk-size and therefore had to fail over.
When looking into the primary server using CLI everything seems fine but the service doesn't fail back to it. We've even tried to restart the secondary server in order to force the primary server to take over but it didn't work.
In about 2 weeks we need to upgrade Prime and while doing that we would prefer to have our HA working so that we can continue monitoring our network.

Hello,
The below provided links might help you out :-
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/user/guide/maint_sys_health.html#wp1070549
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.3/release/notes/cpi_rn_13.html#wp79553

Fail back unsuccessful in Prime Infrastructure 2.0

Similar Messages

Maybe you are looking for