vnxe_monitor Polling Overrun Errors (Error 0x100000a)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Users monitoring EMC VNXe storage arrays with the vnxe_monitor probe (v1.03 or higher) may observe the following symptoms in the probe logs or as alarms in DX UIM:

• Alarm Message: Polling interval was less than the collection time (600 <= 932) for system DataCollector(probe)
• Log Error: Operation failed. Error code: 0x100000a, The system was unable to connect to the storage server.
• Execution Failure: uemcli.exe exits with non-zero exit code: 1.

Environment

• Product: DX Unified Infrastructure Management (UIM)
• Probe: vnxe_monitor (Any version utilizing uemcli.exe)
• Target: EMC VNXe / Unisphere storage resources

Cause

The error 0x100000a indicates a network timeout or connection failure between the UIM Robot hosting the probe and the storage server over port 443.

When multiple storage resources are configured in a single probe instance, and one or more of those resources are decommissioned or unreachable, the uemcli.exe command waits for a network timeout for each sequential command path (e.g., /sys/general, /sys/lic, /env/ps). These cumulative timeouts can cause the total data collection time to exceed the configured polling interval (default 600 seconds), leading to "polling overrun" errors.

Resolution

To resolve the polling overruns, the unreachable or decommissioned resources must be removed from the probe configuration.

1. Identify the Failing Resources: Review the vnxe_monitor.log at level 3 or higher. Search for the string Error code: 0x100000a and note the IP addresses associated with those failures.

2. Verify Resource Status: Confirm with your Storage or Network team if the identified IP addresses are decommissioned or if there is a firewall block on port 443.

3. Remove Profiles:

   • Open the vnxe_monitor configuration GUI.
   • Locate the profiles for the decommissioned IP addresses.
   • Right-click and select Delete or uncheck Active to stop monitoring those specific resources.

4. Apply and Restart:

   • Click Save/Apply.
   • Deactivate and then Reactivate the probe to clear any hung uemcli threads and reset the polling cycle.

5. Validation: Verify in the logs that the DataCollector now completes its cycle in less than the polling interval (e.g., collection time < 600).

Additional Information

Configuring VNXE_MONITOR probe - error — Guidance on handling inventory and connectivity failures.