topic Re: Cisco Prime version 3.2.0 in Wireless

Cisco Prime version 3.2.0

usskenet — Mon, 05 Jul 2021 17:23:43 GMT

Hi guys,

we have Cisco Prime HW appliance. Since last week we have no connection to web interface.

CiscoPrime/admin# ncs status
Health Monitor is running, with an error. ( [Role] Primary [State] HA not Configured )
initHealthMonitor(): can not start DB
Database server is stopped
FTP Service is running
TFTP Service is running
Matlab Server is running
Matlab Server Instance 1 is running
Matlab Server Instance 2 is running
Matlab Server Instance 3 is running
NMS Server is stopped.
SAM Daemon is stopped.
DA Daemon is stopped.
Compliance engine is not running
CiscoPrime/admin#

I already tried ncs stop, ncs cleanup, ncs start but no change.

Any suggestion?

Thanks a lot.

Marek

Re: Cisco Prime version 3.2.0

Mark Elsen — Wed, 15 May 2019 08:52:09 GMT

- Reboot ?

Re: Cisco Prime version 3.2.0

usskenet — Wed, 15 May 2019 09:58:01 GMT

Thanks for reply.

Of course. I tried it. Without change.

Re: Cisco Prime version 3.2.0

superego — Wed, 15 May 2019 13:14:25 GMT

Hi,

Can you issue in CLI:
show clock

show ntp

show timezone

Nothing much can be done in CLI, but you can try:

ncs webroot disable

ncs webroot enable

Do a "show version"

show version

-------------------

Only other thing I can think of is do an application re-install. Make sure you have a backup before doing this.

I experienced before Web is not starting up. I did application remove... then application install... then restore the back up... After that it was good.

Re: Cisco Prime version 3.2.0

pieterh — Wed, 15 May 2019 14:38:08 GMT

check for free space on the disks.

if not available, the database cannot start because it cannot create the database transaction logs

Re: Cisco Prime version 3.2.0

EvgenyG — Thu, 16 May 2019 13:46:36 GMT

got same issue on esxi....no web gui access.
'ncs cleanup' command helped.

Re: Cisco Prime version 3.2.0

Sathiyanarayanan Ravindran — Thu, 16 May 2019 14:32:45 GMT

Generally this occurs while the booting process interrupts.

You have to map the ISO file of 3.2 through KVM and need to boot the server with that mapped file.

Involve TAC in this issue.