5.2.1 Polling checklist

(1) Example polling configuration

To help you understand the polling configuration process, consider this example. Suppose that your network contains multiple HP ProCurve 2810-48G devices. You must ensure that these devices can be reached, but SNMP monitoring of the switches is not required.

1. What can NNMi monitor?

   Because you can only monitor what has been discovered, you configure auto-discovery rules to ensure that NNMi's database contains your switches. For details about configuring discovery, see Chapter 4. NNMi Discovery.

2. What are the logical groups for monitored items?

   It makes sense to group the switches together and apply the same monitoring settings to all of them. Because you are not doing interface (SNMP) monitoring for the devices, you do not need any interface groups.

   You can also use this node group to filter views, to check the status of the switches as a group, and to place the group OUT OF SERVICE when you update firmware.

3. How often does NNMi need to monitor each group?

   For your service level agreements, a five-minute polling interval for the switches is sufficient.

4. What data needs to be collected?

   Here is where the monitoring configuration differs from other groups. For our example of switches, you enable ICMP fault monitoring and disable SNMP fault and polling monitoring. Without SNMP fault monitoring for the group, component health monitoring will not apply.

   For more detailed planning information concerning these configuration choices, see the following topics:

   • 5.2.2 Planning the objects to be monitored by state polling

   • 5.2.3 Creating node and interface groups

   • 5.2.4 Planning polling intervals

   • 5.2.5 Planning the data to be collected

To Page Top