Start a Conversation

Unsolved

SM

1 Rookie

 • 

60 Posts

2719

October 19th, 2020 06:00

OME 3.5.0

Am I dreaming or has OME 3.5.0 just been released?

Any Lexington upgraders yet?

Moderator

 • 

3.7K Posts

October 19th, 2020 10:00

Hello Silver-mox,

 

We have just recently released OME 3.5. Below are a couple reference links.

 

Reference links:

https://dell.to/3o88028

 

https://dell.to/3m5HTY3

 

I hope this is helpful for you.

October 20th, 2020 00:00

We have updated to 3.5. But rolled back after a few days to 3.4. Experiencing massive critical errors "Unable to perform the operation on the device because connection with the device is lost." All devices are healthy though. You can try whatever you want, resetting idrac's even remove them from OMEnt, but the problem still resists. Tech support isn't very helpfull either. The've suggested to delete the OVA and redeploy it, that's no solution to me.
Didn't have this with 3.4, so we rolled back.

1 Rookie

 • 

60 Posts

October 21st, 2020 02:00

@RobintheKing - thanks for the heads up on that, after the challenges we had with v3.31, we've found v3.4 very stable so not in a great rush to update.

I might make a clone of ours and upgrade to v3.5 in our lab.. I did hear that clearing jobs and resetting the idrac were removed from firmware deployment process? - did you find that?

thanks in advance

 

1 Rookie

 • 

60 Posts

October 21st, 2020 03:00

@RobintheKing - thanks for the heads up on that.. yes, think we'll hold fire for a while! 

All the best

1 Rookie

 • 

60 Posts

October 21st, 2020 03:00

@Dell -Charles R - thanks for the info Charles

October 21st, 2020 03:00

@Silver-mox Correct, they have unnecessarily removed the " reset idrac and job queue" options from the device update process, if you were updating from the " Devices list" (like we did).
Now if you want to reset the idrac during the update process you will have to go to Configuration --> Firmware Complaince --> Select Baseline --> View Report --> Select Device --> Make Complaint. So from now on it will take you a few extra steps.

I also found out that the issue i was having with the " Device connection loss" was previously a warning, now it's a critical. So they have changed the severity. There's no way to manually define your own severity.

18 Posts

October 23rd, 2020 00:00

Spoiler
We have the same issue since upgrading to 3.5.

Massive amount of CDEV6131 alerts.

Message ID: CDEV6131, Unable to perform the operation on the device because connection with the device is lost
We have the same issue since upgrading to 3.5.Massive amount of CDEV6131 alerts.Message ID: CDEV6131, Unable to perform the operation on the device because connection with the device is lost

1 Message

December 15th, 2020 23:00

Yep we are also seeing floods of CDEV6131 messages after upgrading to 3.5.0

2 Posts

May 13th, 2021 07:00

same here, lots of CDEV6131 connection messages

No Events found!

Top