FernandoGP
1 Nickel

EEMI ID: CDEV6131

 Hi

From OME constanly I received Alerts with this error "Online Status Of Managed Device - Connection to the devices was not successful  OpenManage Enterprise"

EEMI ID: CDEV6131
 
OME.JPG
 
Anyone knows what means?
 
Thanks
0 Kudos
Moderator
Moderator

Re: EEMI ID: CDEV6131

FernandoGP,

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. 

Chris Hawk

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)

0 Kudos
JennGibbs
1 Copper

Re: EEMI ID: CDEV6131

I am seeing the same error. I have a ESXi Host, Poweregde R910.

 

I have already tired to inventory and rediscover. The device is powered on and pingable.

0 Kudos

Re: EEMI ID: CDEV6131

Hi folks.

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.

https://marketing.dell.com/en/OpenManageEnterprise

Thanks much,

Rob

DELL-Rob C
Social Media Support
#IWork4Dell

0 Kudos
Careyl
1 Nickel

Re: EEMI ID: CDEV6131

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.

Server R730

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

 

Tags (1)
0 Kudos

Re: EEMI ID: CDEV6131

Hi,

Since you have mentioned that it is over WAN, is there a possibility that was network loss between OME and server or any disruption which would have caused OME to believe that the device is not reachable?

Thanks,
Pupul

0 Kudos
Careyl
1 Nickel

Re: EEMI ID: CDEV6131

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.

Deleted System

Created a new discovery. Job reported:

Messages:
Running
Unable to perform the requested action because the device management endpoint authentication failed.
Task Failed. Completed With Errors.
 
Ping to end point - Success no drops 80ms UK to US
Login to iDRAC direct using same credentials as discovery job - Success
Lifecycle log reports:
2018-09-18T07:39:56-0500USR0034
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. 
 

 

Prior to update Lifecycle log only reports access via WS-MAN
Tags (1)
0 Kudos

Re: EEMI ID: CDEV6131

Hi,

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?

Thanks,
Pupul

0 Kudos