07-29-2012 09:15 AM
As I know we get unknown status of node when following condition occur:
1)snmp agent not responding
2)nnm not able to ping device
Any suggestion on this?
07-30-2012 03:29 AM
You need to check the routing between the device and the NNMI server, step by step if need be. (ie traceroute x.x.x.x and then by FQDN see how close you can get before it stops)
You need to check the device for any Access Control Lists (ACL) that might prevent it from reaching its destination.
You need to check any firewalls in between the NNMI server and the device for proper authorization (ports 161 , 162)
Andy Kemp, CISSP
07-30-2012 07:16 PM
07-31-2012 06:15 AM - edited 07-31-2012 06:19 AM
The following is a workaround for "Unknown" status which doesn't send alerts.
Make sure all nodes are a part of the "Important Nodes" group. Any member of the Important Nodes group will not go into Unknown status if unavailable/down. Instead it will go into Minor/Major/Warning/Critical status.
In the Additional Filters tab in the Important Nodes group, create a rule to include any node you wish that will no longer go into unknown status.
Once those nodes are a part of the Important Nodes group, you will always recieve the critical alerts attributed to the group.
I've never been able to figure out why HP designed NNM this way.
07-31-2012 11:06 AM
If this solution ends up working (please test and verify in your environement), do the following.
1. Mark the corresponding answer in the forum as the solution, so others who may have the same issue, in the future, can reference.
2. Please give cudos to helpful answers :)
08-11-2012 08:25 PM
This soultion is fine,but I can implement it as we have approx 1000 devices and adding all the devices is not a good option.Thanks again for help.