Would you confirm a couple things for me?
Is the device in question pingable?
Have you checked the device has power and a known good network connection?
Have you tried a rediscovery/inventory yet?
Lastly, what device is this happening to?
Depending on response I would start with pinging, then a virtual reseat, and then a physical reseat if this happens to be a blade.
Let me know.
Dell | Social Outreach Services - Enterprise
Get Support on Twitter @DellCaresPro
Download the Dell Quick Resource Locator app today to access PowerEdge support content on your mobile device! (iOS, Android, Windows)
When you set up your discovery range did you select WS-Man only and then enter the IP address of your iDRAC?
Is your network connection between your OMEnt appliance and your iDRAC over a LAN or WAN?
Also, we did just post a newer version of OMEnt that you may want to upgrade to as well.
I have been looking at this post with interest. I too have CDEV6131 error, but only after applying all outstanding updates on Firmware baseline. Before this server appeared fine.
OME - Updated to latest release
iDRAC - job queue cleared
System has been re-discovered and also as part of a single custom group WS-MAN only
Access over WAN. Responding fine to RACADM commands
There are a couple of points that have not taken me down this track:
1. Issue arouse after firmware update
2. I have 2 identical systems at this remote location. The non updated system still reports fine.
Created a new discovery. Job reported:
Login attempt alert for Administrator from xx.xx.xx.xx using REDFISH, IP will be blocked for 600 seconds.
|2018-09-18T07:39:56-0500||USR0031||Unable to log in for Administrator from xx.xx.xx.xx using REDFISH.|
Seems like i may be able to tell why you are getting EEMI ID: CDEV6131. When someone tried to connect to iDRAC from one IP with wrong credentials continuously, then iDRAC locks out access for that IP and you will not be able to connect to iDRAC from there. So, for OME, it would appear that iDRAC is not reachable as it will not ping from console.
What we need to look at is why the new discovery now fails with credentials error. Are you able to connect to iDRAC directly using the credentials that you have provided for discovery?