snmpcollector : Reachability shows 0 for accessible device

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

When Reachability metric is enabled for accessible Windows device (SNMP service enabled), you are getting the below incorrect alert.

QOS_REACHABILITY_REACHABILITY = 0.0 from source XXX targeting Reachability has crossed the critical static threshold of < 100.0

QoS value of Reachability metrics for the device is showing as 0% while device is online and SNMP service is up running.

Environment

• snmpcollector probe: Any version
• Windows device (SNMP service enabled) is being monitored
• SNMP V2 is selected for Windows device profile

Cause

• If you select SNMP V2 for profile, snmpcollector probe polls 20 oids in one snmp bulk request and SNMP service in Windows device is unable to respond to the request.

Resolution

Change SNMP version from V2 to V1 in profile for Windows device.

Note:
MAX_BATCH (default 20) parameter controls how many oids snmpcollector polls in one bulk request.

This problem may also be solved with lower number of MAX_BATCH.

However lowering this parameter should only be done very carefully, because it may slow the entire polling performance down in snmpcollector probe.

Additional Information

See this for more details about MAX_BATCH