
UNSOLVED
Closed
Discovering a Windows server messes up iDRAC entry
My servers use a dedicated iDRAC interface that has its own IP address and dns entry on different networks from the server, so for each server I end up with
servername-idrac 192.168.1.10
servername 10.100.20.50
and so on.
I've discovered the iDRAC interface of the server in OME, and it goes into the iDRAC folder as servername-idrac 192.168.1.10
The problem is that when I add the Windows OS interface (so that I can manage OS drivers) by discovering servername 10.100.20.50 it overwrites the idrac entry, so I end up with
idrac folder: servername-idrac 10.100.20.50
windows folder: servername-idrac 10.100.20.50
Which is really not what I want because it is incorrect.
I want OME to consider the iDRAC and Windows OS to be different devices. Is this possible to achieve?
Responses (0)
Solutions (0)
