Alam summary hung in Cisco Prime

[Aditya Dev]

Hi All,

Cisco Prime is not showing up the recent alarms in Alarm summary.

With an impression that disk might be full, I manually deleted some logs but no luck.

i have ensured that device is reachable, i even tried rebooting the server, but still no luck

Kindly assist me in troubleshooting this.

[Y C]

What exactly do you see? Does it show the Loading... with spinning wheel icon? If you leave it alone for a long time (say 1/2+ hour) will the alarms eventually show?

[Pari Thiagasundaram]

Well, you need to post the screenshot so we can see what the issue is. Just my initial thoughts on this issue:

- Check if PI is configured as a trap receiver on the WLC. 

- If you think that the disk is full, try doing a ncs cleanup. Before that, I would login as "root" and see whats going on in different folders.

[Aditya Dev]

Things were working fine in the past, no changes has been made recently.

i too suspect that this might be due to disk, but then i was wondering if ncs cleanup has some other impact too.

kindly help me in understanding the impact of this command

[Y C]

If the disk were full enough so that it won't even write logs then it would have thrown an alarm. But let's not guess if it is or not. SSH into the machine. Type shell and the password again. Then df -h and paste the results.

[Aditya Dev]

Thanks for the assistance.

Output shows /local disk is 94% utilized, does this causing an issue.

Kindly assist me in cleaning up the space.

ade # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/smosvg-rootvol 3.8G 312M 3.3G 9% /
/dev/mapper/smosvg-varvol 3.8G 1.6G 2.0G 45% /var
/dev/mapper/smosvg-optvol 612G 215G 365G 38% /opt
/dev/mapper/smosvg-tmpvol 1.9G 37M 1.8G 3% /tmp
/dev/mapper/smosvg-usrvol 6.6G 1.2G 5.1G 19% /usr
/dev/mapper/smosvg-recvol 93M 5.6M 83M 7% /recovery
/dev/mapper/smosvg-home 93M 5.6M 83M 7% /home
/dev/mapper/smosvg-storeddatavol 9.5G 151M 8.9G 2% /storeddata
/dev/mapper/smosvg-altrootvol 93M 5.6M 83M 7% /altroot
/dev/mapper/smosvg-localdiskvol 116G 103G 6.8G 94% /localdisk
/dev/sda2 97M 5.6M 87M 7% /storedconfig
/dev/sda1 485M 18M 442M 4% /boot
tmpfs 7.8G 2.6G 5.3G 33% /dev/shm

[Y C]

Is this a VM? If so, is the disk thick provisioned, and to the size recommended by the machine requirments?

/localdisk is used for things like the default repository. 103G seems big... just look through the folders and see if you have any big files on there. Are you keeping backups there? That's not what's causing your alarm issues though. Disk seems fine otherwise.

[Marvin Rhoads]

I've been seeing this on a customer system as well. PI has been installed and working fine for a couple of years. It appears the problem started around time of the upgrade to 3.1.5.

The system is now running 3.1.6 with Device Pack 11. It is getting alarms and changing the alarm icon count on home page etc. It is only when one drills down to look into specific alarms that the page hangs while loading.

I suspected it might have to do with the browser but a different browser gave the same results. I then investigated a possible browser cache issue. I found that using a new private browsing window did not have the issue. It also was not seen when logging in from a machine that hadn't previously access that server.

So I went to the primary host I use and cleared the browser cache. (I usually try to avoid that as the cache helps performance with many other systems.) Once I did that, the alarm pages all come up properly as expected.

Here's the "before" screen shot:

[Aditya Dev]

Actually logs are stuck till date (4th May), from 4th may onwards no logs are seen.

Spinning wheel does appears on intervals to refresh the logs.