One or more Data Domain arrays can not be discovered in SRM. An error similar to the following is found in the collecting logs:
WARNING — [2017-04-03 19:20:14 EDT] — PollingUnitSnmpOid2$SingleOidPollingTask::call(): Time out while
WARNING — [2017-04-03 19:23:15 EDT] — TablePoller::logProblemOnRetry(): On retry: Time out while polling
table .220.127.116.11.18.104.22.168.3, column .1.2 on 10.120.xx.xx
WARNING — [2017-04-03 19:23:15 EDT] — TablePollingUnitHelper::handleIOException(): time out after retries
on agent Host=10.120.xx.xx, Port=161
WARNING — [2017-04-03 19:23:17 EDT] — PollingUnitPollingGroup::waitAtEndOfPollingCycle(): Polling group
The SNMP Credentials found in Administration->Modules->SNMP Device Discovery->Devices:
have been verified by ssh’ing to the Data Domain and running: snmp show config
The mibs files have also been found on the appropriate collector and on the frontend in:
For example, the oid mentioned in the above collecting log error, .22.214.171.124.126.96.36.199.3, appears to be for
hrStorageType in the HOST-RESOURCES-MIB:
Finally, a traceroute to the Data Domain from the collector works successfully. And an snmpwalk using the
Administration->Modules->MIB Browser times out,even after greatly increasing the timeout value
Cause: Check whether SNMP is enabled.
Resolution: If SNMP is disabled, enable it. This will not require a reboot of the Data Domain.
To enable SNMP:
Do this by logging into the Data Domain GUI.
If the Data Domain OS is 5.6.x.x., look for System Settings->SNMP and check if Enabled or Disabled is
highlighted. For Data Domain OS 5.7.x.x look for Administration->Settings->SNMP:
Note: from the GUI you can also check the community string and trap host information. You can also download
the mibs from the Data Domain to SRM, if you believe there might be a mismatch.