UNSOLVED

FrancoisLaj

updated

7 years ago

0

8310

October 1st, 2019 12:00

Informationnal alert CDEV6131 Connection to the device was not successful. with OpenManage Enterprise

Hi,

I deploy OpenManage Enterprise V3.2.1 and discover my server in it. I sometime receive error

Online Status of Managed device
Connection to the device was not successful.
Message ID: CDEV6131

it is informational alert and when I connect to the OME it is up again without issue. It is happening on random servers,local and remote location servers and at random time.

The idrac have been discovered and add to the OME using name and Discover job.

Thank you

  • Daniel My

    12 Elder

    •

    6204 Posts

    6226

    0

    Posted October 1st, 2019 13:00

    Hello

    It sounds like a timeout issue. The agent may be busy or there may be network latency at the time of the discovery. If it was happening on the same device consistently then I would suspect a credential or network routing issue.

    Thanks

  • Daniel My

    12 Elder

    •

    6204 Posts

    6216

    0

    Posted October 1st, 2019 14:00

    I don't know of a way to modify retry or timeout values on the health job. You can modify discovery under Additional Settings below the user/pass fields.

  • 6219

    0

    Posted October 1st, 2019 14:00

    Thanks for your reply! 

    It is happening on multiple device and there is no constancy in wich devices give me the error.

    I seems to happen when a global health job run, but like I said never the same time of the day.

    Is there a way to increase the timeout threshold before it return an error?

  • 6112

    0

    Posted October 8th, 2019 06:00

    Hi,

    I try to change the interval of the Global Health job to 30 minutes against 1h, it change nothing but it is the only setting that I can modify for the health job.

    What else can I do to try to solve this issue?

  • 5957

    0

    Posted October 25th, 2019 11:00

    Any update for me?

  • tosaraja

    2 Intern

    •

    34 Posts

    4836

    0

    Posted November 24th, 2020 00:00

    We're facing the exact same issue. We have 30+ R430 servers and 3 x R640 servers which tend to pop out of existence and come back online an hour later. Some more than others. For example of those 3 R640 servers, I've only seen the second one go out, but not the other 2.

    They usually go out at 2:00am, but i've also seen random times like 9:51 pm and 11:19 pm, which are not at all consistent with a sharp 2:00am.

    I took the statistics of how many e-mails i've received during these 24 days of November. I'll give the servers arbitrary names, as they don't matter in this case:

    server#1: 4
    server#2: 4
    server#3: 6
    server#4: 5
    server#5: 4
    server#6: 5
    server#7: 5
    server#8: 1
    server#9: 1
    and that second R640 gave us 12 e-mails.

    But the rest 24 servers or so, not a single warning. They are all hooked up exactly the same and have the latest firmware. The idracs are connected to a HP J9775A 2530-48G Switch, revision YA.16.03.0004, ROM YA.15.19

     

  • DELL-Erman O

    Moderator

    •

    2984 Posts

    •

    14874 Points

    4807

    0

    Posted November 24th, 2020 06:00

    Hi,

    OpenManage Enterprise will periodically check the health of devices using the Global Health role. This will ensure that managed systems are online and accessible, as well as attract health from various monitors. A few things could cause this situation. I'll ask a colleague to take a look. By the way, if it is urgent for you, if you reach the software team, they can control it and connect remotely if they see it necessary.

     

    DELL-Erman O

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

  • tosaraja

    2 Intern

    •

    34 Posts

    4784

    0

    Posted November 24th, 2020 23:00

    Don't know about urgency.. setting these up is my day job, so perhaps there is an interest in getting things working sooner than later

    How would I get in contact with someone in the OME team then?

  • DELL-Erman O

    Moderator

    •

    2984 Posts

    •

    14874 Points

    4777

    0

    Posted November 25th, 2020 01:00

    Hi, 

    I got some pieces of information and I want to share them with you. I hope this info can help you. By the way, if you require help you can contact for support team via this link https://www.dell.com/support/contents/en-us/category/contact-information 

     

    The “CDEV6131 : Unable to perform the operation on the device because connection with the device is lost.” occurs when OM Enterprise attempts a connection to remote device but fails.

     

    This can happen if the connection is reset or times out.

     

    *Verify WSMAN communication from another VM on the same network as OM Enterprise appliance to the target system.

     

    Windows WINRM

    winrm e cimv2/root/dcim/DCIM_iDRACCardView -r:https://192.168.0.120/wsman -u:root -p:calvin -auth:basic -encoding:utf-8 -skipcncheck -skipcacheck -skiprevocationcheck

     

    Linux WSMANCLI

    wsman -o -m 512 -u root -h 192.168.0.120 -P 443 -j utf-8 -y basic -p calvin -V -v -c Dummy -N root/dcim enumerate 

     

    *Try Increasing the Retries/Timeout value for the connection settings by re-onboarding effected servers with updated connection settings.

     

    I would suggest they double the default values 6 and 120.

     

    but If it continues to see these messages after confirming and changing the connection settings, I suggest you open a support case that can be reviewed live.

     

    DELL-Erman O

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

  • tosaraja

    2 Intern

    •

    34 Posts

    1447

    0

    Posted November 25th, 2020 02:00

    Are you sure that wsman command for linux is up to date? I have two different distros with wsman, and neither accepts -N as an argument. Also every time I run that command, I get a Segmentation fault (core dumped).

    But with a bit of googling, I ended up with a command that actually ran through:

    wsman enumerate http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_MemoryView -h -V -v -c Dummy -P 443 -u root -p -j utf-8 -y basic

    Would the idea now be that I continuously run that command to see if it fails at the same time as OpenManage Enterprise fails to receive data? Which can literally take a day or two...