Start a Conversation

Unsolved

This post is more than 5 years old

J

6105

July 11th, 2018 05:00

R610/R710 iDRAC6 discovery problems

Hi, We've recently started using OpenManage Enterprise and generally it seems to be going OK. However we're having quite a few problems getting it to talk to/recognise R610/R710 servers running iDRAC6. If we're really lucky then they are detected as being an R610/R710 with a health state of unknown. But the bulk of them show up with health state unknown and model unknown. And in the worst cases they won't be discovered at all even though we can log into them, and they pass the WSMAN test in the Troubleshooting Tool. The bulk of the R710/R610 are running iDRAC 2.91 firmware with OMSA 9.1 on CentOS 6.8 x64. I can't seem to figure out what makes them report all their info to OME. I have a suspiscion it may be something to do the with the system services or its config collector. Anyone got any ideas? Cheers, Jamie

Moderator

 • 

8.8K Posts

July 11th, 2018 06:00

Jshardlow, 

I would have also suggested updating them to 6.5 at least, or 6.6 which was released day before yesterday. I would also be certain that the iDracs not at 2.91 are also updated to current, as the iDrac is what is communicating with OME.

Let me know how your testing goes.

 

22 Posts

July 11th, 2018 06:00

At risk of looking a bit silly I think I've narrowed it down to the BIOS versions. It looks like the servers that are detected properly are on 6.5 and those that aren't or are not sicovered at all are on 6.3. I'll try and get some downtime to confirm this and report back.

22 Posts

July 16th, 2018 06:00

I'm not having much luck unfortunately. On the servers I've managed to upgrade (BIOS/iDRAC/OMSA) they fall into two groups. The first are discovered but have a health state of unknown and do not have a model listed. They pass both the Troubleshooting Tool WSMAN test and the winrm test. The second refuse to be discovered. They pass the Troubleshooting Tool WSMAN test, but not the winrm test (it returns to the command prompt with no output). In all cases the iDRACs are reachable and work fine. In some cases there are comparable partner servers of the same build/setup etc that work fine. I've tired rebooting, power-cycling and even unplugging the power completely. I've also tried turning system services and inventory collection on/off in the BIOS/iDRAC menus. In short I'm at a complete loss as to why some servers are OK and others not. It is quite purplexing and infuriating.

2 Intern

 • 

2.8K Posts

July 18th, 2018 08:00

Hi Jamie, thanks for the post.

Right, so....for our 11G servers like the 610's, our support is somewhat limited.  You can discover them and get a bit of inventory, but you will not get rollup health--likely it will show as unknown.  You _will_ get formatted SNMP traps in the Alert console.  Basically, the iDRAC instrumentation on 11G is slightly different from 12/13/14G and we are not able to show rollup health.  Hope this helps.

Rob

22 Posts

July 19th, 2018 00:00

Hi,

I'm not too bothered about the lack of health and showing up as unknown, I'm used to that and I appreciate it's a limitation of their design. I'm more worried about them either not being able to be discovered at all, or if they are they not being able to be recognised as an R610/R710.

Cheers, Jamie

2 Intern

 • 

2.8K Posts

July 19th, 2018 06:00

Hi Jamie,

Hmmm, is the iDRAC f/w for the 610/710 the latest and greatest?  And yes, you should keep inventory collector BIOS setting on.  If the WSMan troubleshooting test is working, I would think it should get discovered.  We may need a support ticket to take a closer look.

Thx

Rob

22 Posts

July 23rd, 2018 04:00

Hi, Yes in all these cases the iDRAC is at 2.91. Depending on the server then I'm aiming to get the BIOS to be 6.5 or 6.6. Cheers, Jamie

98 Posts

December 4th, 2019 07:00

Hi--

Aware that this is an old thread, but in view of Dell not supporting OM Essentials anymore, did you get OM Enterprise to inventory R610s reliably after you updated their Bios to v6.6?

If this worked for you, then I'll go that route.  It is a shame that OM Ent does not include OMSA as an inventory protocol like OM Essentials does.  I wonder why Dell did not include OMSA communication in OM Ent.  OMSA makes everything easier.

No Events found!

Top