Re: NNMi 9 - System Health Monitoring (660 Views)
Reply
Valued Contributor
Sven Hruza
Posts: 229
Registered: ‎09-10-2007
Message 1 of 13 (2,192 Views)
Accepted Solution

NNMi 9 - System Health Monitoring

Hello,

I can't find any informations about the NNMi System Health Monitoring.

I have two problems:

1. Status Major
License Violation: HP NNMi Integration Module for Netcool Software: license expiring in 3 days

What can I do with that? I don't want to use the Netcool Module in NNMi, so I won't have a license for that.

2. Status Critical
Stale collections (41.483) has status Critical because there were more than 10 in the last 5 minutes.

What does this mean?

Basically, what can I do to get the status of the system back to Normal?
Is there anywhere a documentation about the meaning of all messages that can occur?

Thanks a lot!

Sven
Honored Contributor
mohan23
Posts: 252
Registered: ‎04-05-2010
Message 2 of 13 (2,169 Views)

Re: NNMi 9 - System Health Monitoring

Sven,
Regarding the Netcool Software, leave it as it is to expire. Once it expires it disappears automatically.

Valued Contributor
Sven Hruza
Posts: 229
Registered: ‎09-10-2007
Message 3 of 13 (2,167 Views)

Re: NNMi 9 - System Health Monitoring

Thanks for that replay.
So after the weekend it should get away...fine :-)


Sven
Honored Contributor
sekar sundaram
Posts: 615
Registered: ‎11-14-2008
Message 4 of 13 (2,167 Views)

Re: NNMi 9 - System Health Monitoring

2. Status Critical
Stale collections (41.483) has status Critical because there were more than 10 in the last 5 minutes.
- - - -
i think its related to Network Topology Autolayout Error. you need to remove some devices and rediscover them. i am having a document in which this info is present:

NNM will occasionally draw part of a network topology that varies with what you know is correct. This is NNMâ s way of telling you that it is having some sort of difficulty and is making the best of a bad situation. NNM is very conservative. It tends to make few assumptions and will retain old data that once was accurate over new data that is inconsistent or inconclusive. Usually, this is not a bug with NNM, and by exploring the circumstances surrounding the discovery and layout problems, the reason is almost always found. The remedy may not be as apparent.

Sometimes NNM doesnâ t lay out part of the network properly because it cannot get the information it needs from a buggy SNMP agent. For example, an Ethernet switch may not properly implement the bridge MIB, so NNM isnâ t able to correctly identify all of its ports. The discovery problem leads to an autolayout problem.

Since NNM tends to hang on to old configuration information, it may have difficulty when a device configuration radically changes. For example, inserting a new card into an Ethernet switch and restarting it often results in renumbered MIB instances for the ports. At the next configuration check, NNM may add all the new instances in but not delete the old ones. Sometimes the only way to rid the NNM database of this stale data is to delete the device and then ping it from the NNM system to force a rediscovery. Note that since maps wonâ t be affected by this until they are opened, the map count for this deleted object will be inconsistent.

NNMâ s IP-centric design will create a subnet container for every subnet it discovers. If a router interface has one primary address and three secondary addresses, then NNM will show the router as having four subnets attached. This is completely true from an IP viewpoint. Suppose that the additional subnets are needed to support an increasing number of devices. Each device discovered is situated into its proper subnet container. Now suppose that the switches are assigned IP address at random from the available four subnets. NNM will draw the physical topology in each subnet incorrectly. The fix is to readdress the switches to the same subnet. In this subnet, NNM will be able to correctly draw the physical topology. If some of the switches are addressed within the same subnet, they will be connected properly, but their peers will be lodged within the other subnet icons, ruining NNMâ s ability to lay out the correct topology.
Valued Contributor
Sven Hruza
Posts: 229
Registered: ‎09-10-2007
Message 5 of 13 (2,167 Views)

Re: NNMi 9 - System Health Monitoring

Thanks a lot!

Is it possible to get this document where the the alerts for system health are described?

So I will search for some wrong devices in my NNMi...

Should NNMi turn back to status normal if I found all wrong devices and correct them?


Sven
Occasional Advisor
harinder82
Posts: 8
Registered: ‎12-30-2011
Message 6 of 13 (2,099 Views)

Re: NNMi 9 - System Health Monitoring

Stale collections (41.483) has status Critical because there were more than 10 in the last 5 minutes

 

can some explain me, what is the exact reason of above message and where i foundl the log?

 

Please share if, some one have complete document for the above error message.

 

Regards

Harinder R

Senior Member
hrana
Posts: 3
Registered: ‎02-15-2012
Message 7 of 13 (2,047 Views)

Re: NNMi 9 - System Health Monitoring

Hi,

Can you please share this document.

Respected Contributor
asoloperto
Posts: 183
Registered: ‎03-10-2010
Message 8 of 13 (2,044 Views)

Re: NNMi 9 - System Health Monitoring

Hello,

 

is this document really for NNMi?

 

Kind regards

 

Allessandro

Occasional Advisor
Manoj KD
Posts: 10
Registered: ‎04-18-2011
Message 9 of 13 (1,884 Views)

Re: NNMi 9 - System Health Monitoring

Hi Sekar,

Can you please share the Solution Document for this issue.
For me also same issue was there.

Thanks in Advance,

Regards,
Manoj KD
Regular Visitor
Yahyakhdair
Posts: 1
Registered: ‎01-30-2012
Message 10 of 13 (1,558 Views)

Re: NNMi 9 - System Health Monitoring

Hi all;

 

I'm faceing the same problem

 

  NNMi System HealthStatus:Critical
Last Updated:2/13/13 10:59 AM

[Critical]  Stale collections (47) has status Critical because there were more than 10 in the last 5 minutes.

 

when I restarted the services (using OVStop/OVstart) the problem disappeared but after a while 1-2 hours the error will show again.

 

do we have a perminant solution?

 

Advisor
Christof Madoery
Posts: 29
Registered: ‎09-16-2003
Message 11 of 13 (1,031 Views)

Re: NNMi 9 - System Health Monitoring

I do have the same problem.

 

a) is it possible to get your document?

b) how to find out which Nodes are responsible for that?

 

Regards,

Christof

HP Expert
DSimon
Posts: 83
Registered: ‎04-04-2011
Message 12 of 13 (1,025 Views)

Re: NNMi 9 - System Health Monitoring

What version and patch level of NNMi are you running?  Patch 3 introduced a problem where bogus stale collections are reported.  This is corrected in the NNMi consolidated STATEPOLLER hotfix which is available from support.

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution, If you are satisfied with anyone’s response please remember to give them a KUDOS and show your appreciation.
Valued Contributor
bebu
Posts: 114
Registered: ‎06-14-2011
Message 13 of 13 (660 Views)

Re: NNMi 9 - System Health Monitoring

Hi Team,

 

I am also affected by the above mentioned issues " Stale collections (1) has status Minor because there were between 0 and 5 stale collections in the last 5 minutes."

 

It happens for me very frequently and solves itself in between the time of 10-15 mins.

 

I could not have enough information to trouble shoot the issue.

 

Am using NNM > 9.10,9.11.004. 

 

Please help me on this issue.

 

Regards,

Bebu

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.