PowerEdge Hardware General

Last reply by 08-21-2022 Unsolved
Start a Discussion
2 Bronze
2 Bronze
4423

Virtual console not working after iDRAC update to 2.70.70.70

On both of our PowerEdge R730, after we upgraded iDRAC to version 2.70.70.70, we have issue with virtual console and virtual console preview. Both don't work.

The only workaround I have is to reset iDRAC. Then it works, but when I try the next day it doesn't work again. I have to reset iDRAC any time I need to connect.

This is an issue for us because we're doing tests, reinstalling OS, etc so we need this functionality.

We didn't have any issues like this prior to thi update.  

Replies (29)
3436

Luciusthe,

 

I would first make sure that the system is up to date on the BIOS as well, then I would rerun the 2.70.70.70 update on the iDrac. 

 

Let me know if that clears it up.

 


Chris Hawk
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#Iwork4Dell

Did I answer your query? Please click on ‘Accept as Solution’
‘Kudo’ the posts you like!
3358

Chris,
I keep systems up to date regularly. System was updated via LC, using DELL FTP repo.
Same process I did many times before. I update BIOS and everything else there is to update. With LC, I think BIOS update always happens before iDRAC update.

Anyway, BIOS is on version 2.11.0. Every time I have to use virtual console, I need to reboot iDRAC first.

3355

Hi luciusthe,

 

is there any specific error message showing up? What exactly is happening when you try to use the virtual console and which way do you use it  Java, ActiveX or HTML5? And have you tried a different way already?

Would be also interesting to take a look in the Lifecycle Log (https://dell.to/3accGgh) this may show errors that we can use to troubleshoot furthermore.

 

Thanks
Stefan

 



DellEMC

Stefan Richter
Community Manager
Brand certified, SMaC Professional


3275

Hi Stefan,
Sorry I didn't see your message sooner.

Before answering your questions, let me explain my setup. I might have a bit different situation than others, since my servers are are turned off most the time. At the moment these servers are used like in a lab setup. But the are still connected to power outlets, so iDRAC is running. With this in mind, the steps to reproduce are:
1. servers are off (they are normally off during off work hours, sometimes it's days, sometimes even weeks)
2. as soon as I login to iDRAC, on the main screen, the Virtual Console Preview shows "No Signal". That's ok since they are off.
3. I power any of the two servers on. Doesn't matter how. Let's say I do it using a Quick Launch task. It could be via Virtual console menu, or a power button, it doesn't matter.
4. servers are starting now. The Virtual Console Preview still shows "No Signal" and will continue to show "No Signal".

I can start Virtual console at any time. It doesn't matter If i use Java or HTML5. And it doesn't matter if I start the console before powering the servers on or after - both consoles will start without errors and it seems like it's connected. But the VC just shows "No Signal". Even though the server is booting. If I connect the VGA cable to the monitor I can see it booting.

This started to happen after iDRAC update - it didn't happen before.

Lifecycle log is very long, going back to 2016 when we bought the servers. So I focus on entries since the last iDRAC reboot. I see nothing significant here. No warnings or errors, no unusual entries. The server has finally booted to ESXi 6.5 and the last two iDRAC messages are this:
- The complete Lifecycle Log was successfully created for an export operation.
- The iDRAC Service Module has successfully started communication with iDRAC.

If I want to use virtual console, I have to restart iDRAC. Then it works for... unknown amount of time. When I power the server off and go home, the day after iDRAC virtual console will not connect again, until I reboot.

You should be able reproduce this. I have 2 servers, they are the same. This never happened before the update, now happens on both servers after the iDRAC update (well, iDRAC + BIOS update, I don't know if there was anything else in the update, I think there was the OS collector update too).

Regards,
David

2129

Mind you, I never received any further communication from Dell - and I still have this problem.

2116

Hello,

i will check about this issue and see if there is some internal article.

In the meantime can you please send me the service tag of the two server in private message?
Thanks

Marco


Marco B.
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#Iwork4Dell

Did I answer your query? Please click on ‘Accept as Solution’
‘Kudo’ the posts you like!
2106

Hi there. My suggestion on this would be to update the idrac to 2.75.100.75. I didnt see anything describing this issue in the release notes, but fixes for other items can affect various things in my experience. Secondly, after updating the idrac, I would power off the system, move the nvram_clr jumper so that it clears the nvram contents. Then power on the system and power it off when the system complains that the jumper has been enabled. Then move the jumper back to its original position, and you "should" be ok. I work for Dell and we have a lab of about 80 R730's, and we have yet to see this issue you're describing. 
Please check the Jumpers and connectors section of this page:
https://www.dell.com/support/manuals/en-us/poweredge-r730/r730_ompublication/dell-poweredge-r730-sys...

2053

Hello, thanks for answering. I've sent you the service tags in private message.

2051

Hello,
My thoughts as well on updating iDRAC. Done that already (several times as several version came out, this is an old topic). But the problem persists.

I don't feel keen on NVRAM reset though, I've configured so many things in BIOS and iDRAC. I'd have to go writing everything down, to configure it back the way it was - there's a ton of settings. A long shot, not sure if it would help and it's a lot of work to try it.

I'll give Marco B a shot at finding another way perhaps - if all else fails I could perhaps try with NVRAM reset.

Latest Solutions
Top Contributor