HUM summary not in Device Center

Answered Question
Jan 7th, 2010

LMS 3.2.1 with HUM 1.2 . Devices being monitored in HUM do not have HUM summary data in Device Center. This used to be the case but I cannot recall whether has changed only since upgrading to LMS 3.2 or 3.2.1. The devices in question are definitely being monitored by HUM as it appears in device center view as a managing Application. Is this a known issue or can anyone point me in the right direction

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 6 years 10 months ago

The only thing that would explain this behavior is a problem in the PIDM mapping in the cmf database.  Your log doesn't show the Gosford 6509 Sw 2 device, but I assume one of the 6509s shows itself managed by HUM in Device Center.  In that case, given that the server name is correct, my guess is that the app version in the PIDM_app_device_map table is not 1.2 for these problem devices.  You should contact TAC, and have them walk you through getting this data.  The value in the database could help point to a root cause.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 01/07/2010 - 23:34

There is no LMS 3.2.1.  Do you mean you upgraded to HUM 1.2.1?  If you add a poller for a new device (i.e. one not being monitored by HUM) does Device Center have HUM options for it?

mburrell5 Sun, 01/10/2010 - 13:16

Sorry I meant HUM 1.2.1.

I added a poller for a new device to HUM and there are no HUM options in Device Center. In addition HUM does not show up as a managing Application for this device.

Joe Clarke Sun, 01/10/2010 - 14:42

You may have a problem with your PIDM data in the cmf database.  Post a screenshot of Device Center showing a device which has a poller configured in HUM.

mburrell5 Sun, 01/10/2010 - 16:47

No, no ACS integration for authentication to LMS. We do however use ACS to authenticate for Telnet access to some devices that are managed by LMS.

Joe Clarke Sun, 01/10/2010 - 16:57

Go to Common Services > Server > Home Page Admin > Application Registration, and unregsiter and reregister "Health and Utilization Monitor".  then see if you can see "Launch Device Dashboard" in Device Center.

mburrell5 Sun, 01/10/2010 - 17:34

no change after I followed your instructions. what i did notice when registering was that although I have HUM 1.2.1 installed, only HUM 1.2 was available as a template. The same goes for campus manager (5.2 when 5.2.1 is installed) and Cisco view (6.1 when 6.1.9 is installed)

Joe Clarke Sun, 01/10/2010 - 18:41

Post your NMSROOT/objects/data/cmf/cmic/mst-templates/upm.1.0.xml file.

Joe Clarke Sun, 01/10/2010 - 20:03

The forum isn't letting me download this file.  Compress it, and post again.

Joe Clarke Mon, 01/11/2010 - 20:19

Post the NMSROOT/MDC/tomcat/logs/stdout.log and stderr.log from this server after reproducing the problem.

mburrell5 Mon, 01/11/2010 - 21:11

Files as requested are attached.

I have had a look at devices that have pollers setup in HUM and both ASA-5510 firewalls are showing the Launch Device Dashboard link as well as the 24hr HUM summary data in Device Center. The other devices (the likes of 6509 switches, etc) in HUM have no such data in Device Center

Attachment: 
Correct Answer
Joe Clarke Mon, 01/11/2010 - 22:11

The only thing that would explain this behavior is a problem in the PIDM mapping in the cmf database.  Your log doesn't show the Gosford 6509 Sw 2 device, but I assume one of the 6509s shows itself managed by HUM in Device Center.  In that case, given that the server name is correct, my guess is that the app version in the PIDM_app_device_map table is not 1.2 for these problem devices.  You should contact TAC, and have them walk you through getting this data.  The value in the database could help point to a root cause.

Actions

This Discussion

Related Content