Prime infrastructure 1.3 failed to start

Hello,
I bought a brand new PI 1.3 appliance, i configured the network part and the password. When I tried to access to the web pages I can't get anything work.
After a quick look on the forum I saw, some command (ncs stop, ncs cleanup, and ncs db reinitdb) but with no success.
Here is the output from "show application status NCS"
srv-eps-ssi12/admini# sh application status NCS
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 running ...
DA Daemon is running ...
Syslog Daemon is running ...
status
I don't know what to do after tried everything. The PI version is PI 1.3.0.20, and it's installed on a Cisco appliance.
Does anyome as an idea on how get this appliance works?
Regards

Your best bet will be to reimage the appliance.
I'll send you a message asking for your CCO ID.
Reply back with that info and I'll publish an image of an ISO of 1.3.0.20::
You'll receive an email with instructions to download the image.
Burn that image to a Dual Layer DVD then reimage then go back through the setup and you'll be good to go...

Similar Messages

Prime Infrastructure 1.3 Can't start DB.Can't use WEB interface access

Hi,
Suddently, all services at prime infrastructure 1.3 are stopped. It's working fine previously. I try to restart the ncs service also doesn't help.
here is the ncs status:
PRIME01/netsvcsdm# ncs status
Health Monitor is running, with an error.
initHealthMonitor(): can not start DB
Reporting Server is Stopped
Ftp Server is Stopped
Database server is stopped
Tftp Server is Stopped
Matlab Server is Stopped
NMS Server is stopped.
SAM Daemon is not running ...
DA Daemon is not running ...
Syslog Daemon is not running ...
status
PRIME01/netsvcsdm# ncs start
Starting Network Control System...
Unable to verify hardware.
This may take a few minutes...
Health Monitor is already running.
Failure during Network Control System startup. Check launchout.log for details.
start
Note: I notice that the MEM LED at light path diagnostics panel components is lit. I check at cisco documentation, it indicate memory error. is it confirmed appliance issue?
Please advice. Thank you

Thank you for the reply. sorry for late update.
1. I try to reseat the memory card, MEM LED from diagnostic panel is not lit anymore. I think it solve the memory problem initially.
2. I use the following command to refresh the database
NCS stop
NCS DB reinitdb
NCS start
After reinitdb, I can login to prime infrastructure. it seems like the system is working fine. All of the configuration is gone. So, I proceed to restore the configuration.
3. Restore configuration
When I try to restore my configuration, I have the following error.
PRIME01/netsvcsdm# restore 2013-07-24_PRIME01-130724-1853.tar.gpg repository localftp application NCS
Restore may require a restart of application services. Continue? (yes/no) [yes] ? yes
Initiating restore. Please wait...
Stage 1 of 9: Transferring backup file ...
-- complete.
Stage 2 of 9: Decrypting backup file ...
-- complete.
Stage 3 of 9: Unpacking backup file ...
--complete.
ERROR : There is the mismatch in the following configuration parameter(s) of this machine when compared to the machine where the backup was generated: DB Memory Target, RAM Size -> can’t restore the configuration due to RAM size different.
ERROR : This may affect the performance of the current machine. Hence aborting restore process.
% Application restore failed
PRIME01/netsvcsdm#
PRIME01/netsvcsdm# show inventory
NAME: "PRIME-NCS-APL-K9 chassis", DESCR: "PRIME-NCS-APL-K9 chassis"
PID: PRIME-NCS-APL-K9 , VID: V02 , SN: KQ7T4TM
Total RAM Memory: 12141876 kB -> Appliance only detect the RAM memory as 12GB. Our Appliance has 16GB memory. I suspect 1 of 4 memory was spoiled.
I notice that the prime only detect 12GB RAM instead of 16GB. There is hardware failure (1 of 4 memory is spoil). Unit have to be RMA.
Thanks,

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

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****

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.

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.

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 config deployment (no copy run start)

I have deployed some CLI templates I have created to configure multiple local accounts on some switches. However the cli templete only appears to accept conf t commands, it will not accept 'write mem' or 'copy run start' at the end to save the altered running config to startup. this results in running and startup being 'out of sync' in the configuration archives, and runs the risk of a power failure causing the config to revert back to startup. Does anyone know how to ensure the altered running config is saved to startup during the config template deployment?

I don't know if this has been fixed in 2.0 or not. By the looks of the bug it hasn't. However, there is a workaround-
https://tools.cisco.com/bugsearch/search?kw=prime%20infrastructure%20copy%20run%20start&pf=prdNm&sb=anfr&srtBy=byRel&bt=custV
BugID
CSCuf89957
Prime Infrastructure - No option to save running config to startup
Conditions:
Prime Infrastructure 1.2/1.3
Workaround:
Create a Configuration Template that runs either:
"do write mem"
Or for devices which no longer support "write mem", use:
"file prompt quiet
do copy run start
no file prompt quiet"

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 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 2.0 - no traps/info are pushed from devices

Good evening,
I have setup Cisco Prime Infrastructure 2.0 and, though I have added manually my 4 network cores as devices without any problem, I can't get a single trap or a single SNMP information to be pushed into my Cisco Prime Infra.
Here is my SNMP config on my core :
snmp-server user *edited* *edited* v3
snmp-server group *edited* v3 noauth notify *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF0F
snmp-server community *edited* RO
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps flowmon
snmp-server enable traps transceiver all
snmp-server enable traps call-home message-send-fail server-fail
snmp-server enable traps tty
snmp-server enable traps rf
snmp-server enable traps memory
snmp-server enable traps cpu_threshold
snmp-server enable traps eigrp
snmp-server enable traps ospf state-change
snmp-server enable traps ospf errors
snmp-server enable traps ospf retransmit
snmp-server enable traps ospf lsa
snmp-server enable traps ospf cisco-specific state-change nssa-trans-change
snmp-server enable traps ospf cisco-specific state-change shamlink interface
snmp-server enable traps ospf cisco-specific state-change shamlink neighbor
snmp-server enable traps ospf cisco-specific errors
snmp-server enable traps ospf cisco-specific retransmit
snmp-server enable traps ospf cisco-specific lsa
snmp-server enable traps flex-links status
snmp-server enable traps fru-ctrl
snmp-server enable traps entity
snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config
snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up
snmp-server enable traps ether-oam
snmp-server enable traps aaa_server
snmp-server enable traps flash insertion removal
snmp-server enable traps l2tc threshold sys-threshold
snmp-server enable traps power-ethernet police
snmp-server enable traps rep
snmp-server enable traps vswitch dual-active vsl
snmp-server enable traps udld link-fail-rpt status-change
snmp-server enable traps vtp
snmp-server enable traps vlancreate
snmp-server enable traps vlandelete
snmp-server enable traps auth-framework sec-violation
snmp-server enable traps dot1x auth-fail-vlan guest-vlan no-auth-fail-vlan no-guest-vlan
snmp-server enable traps envmon fan shutdown supply temperature status
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
snmp-server enable traps port-security
snmp-server enable traps ethernet evc status create delete
snmp-server enable traps energywise
snmp-server enable traps ipsla
snmp-server enable traps vstack
snmp-server enable traps bfd
snmp-server enable traps bgp
snmp-server enable traps bulkstat collection transfer
snmp-server enable traps cef resource-failure peer-state-change peer-fib-state-change inconsistency
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps config-ctid
snmp-server enable traps event-manager
snmp-server enable traps hsrp
snmp-server enable traps ipmulticast
snmp-server enable traps isis
snmp-server enable traps msdp
snmp-server enable traps pim neighbor-change rp-mapping-change invalid-pim-message
snmp-server enable traps bridge newroot topologychange
snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
snmp-server enable traps syslog
snmp-server enable traps isakmp policy add
snmp-server enable traps isakmp policy delete
snmp-server enable traps isakmp tunnel start
snmp-server enable traps isakmp tunnel stop
snmp-server enable traps ipsec cryptomap add
snmp-server enable traps ipsec cryptomap delete
snmp-server enable traps ipsec cryptomap attach
snmp-server enable traps ipsec cryptomap detach
snmp-server enable traps ipsec tunnel start
snmp-server enable traps ipsec tunnel stop
snmp-server enable traps ipsec too-many-sas
snmp-server enable traps errdisable
snmp-server enable traps ethernet cfm alarm
snmp-server enable traps vlan-membership
snmp-server enable traps mac-notification change move threshold
snmp-server enable traps vrfmib vrf-up vrf-down vnet-trunk-up vnet-trunk-down
snmp-server host *ip-address-edited* version 3 noauth *edited*
Basically all traps are enabled but absolutely nothing is showing up in my Prime Infra except that my 4 devices are "Reachable".
Here is a show snmp on the same device :
sh snmp
Chassis: *S/N Edited*
38554534 SNMP packets input
    0 Bad SNMP version errors
    14 Unknown community name
    0 Illegal operation for community name supplied
    0 Encoding errors
    38453185 Number of requested variables
    0 Number of altered variables
    17790703 Get-request PDUs
    20583581 Get-next PDUs
    0 Set-request PDUs
    0 Input queue packet drops (Maximum queue size 1000)
38490708 SNMP packets output
    0 Too big errors (Maximum packet size 1500)
    0 No such name errors
    0 Bad values errors
    0 General errors
    38371069 Response PDUs
    13 Trap PDUs
SNMP global trap: enabled
SNMP agent enabled
SNMP logging: enabled
    Logging to *edited*, 0/10, 13 sent, 0 dropped.
Can anyone point out what is wrong or missing in my configuration? I can't seem to single it out myself.
Thanks
Jeremy

Hi Jeremy,
SNMP traps are shown in the events and alerts section of PI.
SNMP config looks fine. Can you run the SNMP debug (debug snmp packets ) .check the logs and see if the device is actually sending the TRAPS to the PI server.
Thanks-
Afroz
[Do rate the useful post]
****Ratings Encourages Contributors ****

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.

Prime infrastructure 1.3 failed to start

Similar Messages

Maybe you are looking for