Unsolved
This post is more than 5 years old
1 Rookie
•
38 Posts
0
8839
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
Anyone knows what means?
Thanks
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
0
September 12th, 2018 07:00
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.
JennGibbs
1 Message
0
September 12th, 2018 10:00
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.
DELL-Rob C
2 Intern
2 Intern
•
2.8K Posts
0
September 14th, 2018 06:00
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
Careyl
5 Posts
0
September 18th, 2018 04:00
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
DELL-Pupul M
1K Posts
0
September 18th, 2018 05:00
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?
Careyl
5 Posts
0
September 18th, 2018 05:00
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:
DELL-Pupul M
1K Posts
0
September 19th, 2018 06:00
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?