OME 2.1 and Erroneous System Down Alerts

Hi,

One thing to check when you are getting system down alerts. Are you able to ping the iDRAC IP from the OME system when during the polling cycle you are observing this?

Thanks,
Vijay

I have observed no connectivity issues. Pings are consistent, with zero packet loss and less than 1ms latency.

Is your status poll still set to the original default value?  I think it might be 60 minutes.

Also, there are timeout values and retries in the discovery wizard on the WSMan page.  Perhaps bumping those up a bit might help.

Regards,

Rob

Yes, status polling schedule is the default 60 minutes.

The WS-Man configuration for the discovery range is still the default:

• 60 second timeout
• 3 retries
• Port 443
• Secure mode enabled
• Skip common name check enabled
• Trusted Site enabled

Is there a log anywhere that would indicate the reason for the system down alert? Is the status check truly timing out?

Hi,

You can enable the schedule poll logs by modifying dconfig.ini file for following flag:

[TASK_AUDIT]
AUDIT_ENABLED=true

After you modify this setting in dconfig.ini, you need to restart OME Services for settings to take effect. Right click the status poll that executed for that range/device and see the detailed logs.

Note: Please disable the audit logs after you have analyzed/collected the logs as performance will be degraded with enabled audit logs.

Also, can you confirm whether you are enabling both WSMAN/SNMP or only WSMAN for that device discovery?

Thanks,
Vijay

Just wanted to follow up...

I haven't changed anything, but it seems to have settled down about a week ago (several days after I last posted). I'm not sure why additional time would have had any impact on anything. I'm going to keep an eye on things nonetheless.

Thanks!