Re: NodeDown Incident not generated (279 Views)
Reply
Honored Contributor
ramesh9
Posts: 1,150
Registered: ‎04-19-2011
Message 1 of 5 (343 Views)
Accepted Solution

NodeDown Incident not generated

NNM 9.11.005 on HP Unix 

 

We had written few custom pollers to query bgpPeerState on a Cisco Device and if something fails we generate Critical Incident. In custom poller we had selected "Affect Node Status" and "Generate Incident" for changing status of device and generating incident.

 

Once Custom Poller generates critical incident and after few minutes when Cisco Device is down we are not receiving NodeDown Incident.

 

Cisco Device is kept in Important Nodes nodegroup but not sure why NodeDown Incident is not getting generated.


Can you please help

Respected Contributor
mostafa_hassan
Posts: 287
Registered: ‎12-11-2011
Message 2 of 5 (311 Views)

Re: NodeDown Incident not generated

Hello Ramesh , 

 

Just for My understanding , you have created Custom polling that will affect the Node status if something went wrong ! right .

 

So Custom Poller has created critical incident regarding the polling and after that the same device went down , but NNM didn't generate any Node Down incident , If so !

 

Is the Node Status Changed to Unknown or NNM didn't change the Status as well , it should be Changed with the Custom Polling to critical Staus when the Custom Polling condition fails ?!

 

 

All the best .
Saying Thanks by hitting Kudos :)

Regards
Mostafa Hassan
HP AIS NNM-NA-OO
CCNA-CCNP-ITIL-VCA-Cloud-VCA DataCenter
Frequent Advisor
kimo
Posts: 83
Registered: ‎09-10-2007
Message 3 of 5 (300 Views)

Re: NodeDown Incident not generated

Hi,

Please make sure that the node is being polled (Configurations --> Monitoring Configurations --> Node Group)

Just make sure you have created a polling policy for such noes.
Honored Contributor
ramesh9
Posts: 1,150
Registered: ‎04-19-2011
Message 4 of 5 (289 Views)

Re: NodeDown Incident not generated

The problem has happened because Custom Poller sets status of node to Critical.

 

When NodeDown is detected by NNM casual engine it finds allready status of node is critical, hence it skips sending NodeDown alarm to NNM

 

We changed the severity from Critical to Major and now NNM casual engine sends NodeDown event to NNM.

 

Now we need to revisit all our custom pollers to change the highest severity from Critical to Major.

Respected Contributor
mostafa_hassan
Posts: 287
Registered: ‎12-11-2011
Message 5 of 5 (279 Views)

Re: NodeDown Incident not generated

Thanks Ramesh for the feedback ,

 

I was thinking of the same >>

 

please consider to close the post .

All the best .
Saying Thanks by hitting Kudos :)

Regards
Mostafa Hassan
HP AIS NNM-NA-OO
CCNA-CCNP-ITIL-VCA-Cloud-VCA DataCenter
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.