What version of iDRAC hardware and firmware do you have? We will need to try to reproduce this in our lab in order to root cause - since nothing you have mentioned so far seems unusual, and we have not seen or heard of this issue so far, otherwise.

PPrabhu

Patrick  - I hope we can find the problem and solve it in this forum thread. Do not hesitate to open a support ticket if you think you need quicker attention.

For starters - do check the OME About box to ensure that the hotfix was applied and is correctly installed.

Next use the troubleshooting tool and point to one iDrac to see if you are getting a response. Then create a discovery range with a single iDrac to see if it gets discovered. Use the same protocols as you would in OME.

PPrabhu 

HI,

I can confirm that the hotfix was installed correctly. The HF was installed as per Dell instructions.

I can also confirm that I am able to connect to Drac using troubleshooting tool as per my initial question.

Any additional suggestions?

Patrick

Hi,

we use combination of iDrac6 and iDrac7. Mostly up to date firmware 1.95  I believe.

Patrick

Hi Patrifick,

Which protocol are you using for discovery and inventory of iDRAC? 

Are you discovering the server also along with the iDRAC? If yes, do you see the server getting discovered?

Will it be possible to delete the IP range from the OME discovery ranges and do an individual discovery of an iDRAC IP?

Patrick - we might be to determine the cause of the failure using the discovery log files. To enable the logs open the dconfig  file located at : C:\Program Files\Dell\SysMgt\Essentials\configuration\dconfig.ini

Then edit the setting as shown in bold below. After editing save the file and restart the services. After restarting the services the logs files will be generated at: c:\windows\temp

Note : Since the logs are enabled in trace mode they may reach the size of GB’s in a day. You might want to keep that in mind.

[LOGGING]

; The master switch (true/false).

LOG_ENABLED=true

; Log to file (true/false), if true Output file is $(LOG_FILE_PREFIX)$(SEPARATOR) $(LOG_FILE_SUFFIX).

LOG_TO_FILE=true

LOG_FILE_PREFIX=c:\windows\temp

LOG_FILE_SUFFIX=_log.txt

; Filter based on tags (true/false), if true  log only the statements with Tag name specified. 

LOG_FILTER=false

LOG_FILTER_TAG=PPA

; Log levels are on a scale 1-7 where 7 is full verbose, trace (7), debug (6), info (5), warning (4), error (3), fatal (2), and output (1),

; and range is from Minimum scale to Maximum scale of logging levels, you get all logging information between the range of levels specified.

LOG_LEVEL_MIN=trace

LOG_LEVEL_MAX=output

Hi,

I have done following:

- I have separate discovery ranges for servers and drac

- protocol used is 443

-  enabled logging on the server 

- delete discovery ranges and create a single server one

= this worked I was able to discover a single server

- I have deleted the single server range and created discovery group with some of our drac ranges

= this also worked, however few dracs are are showing unknown status, if possible I would like to have this looked into why is that

I will now be out of office until next Wednesday so if you have any suggestion please  don't hesitate and post them in here. 

I would like to send you the log files after the discovery, could you advise how?

thank you

Patrick

Hi Patrifick,

Sending log files over the forum would not be feasible, it would be great if you can log a trouble ticket for that.

For the iDRACs whose health state are coming as unknown, can you try with resetting one of the iDRACs and again perform a rediscovery in OME. Let us know how it goes.

Has there been any recent firmware updates on these iDRACs? 

So, when you for smaller group of IP ranges you were able to discover the iDRAC, can you confirm where exactly you are not able to get the iDRACs discovered? Is it an individual iDRAC or an IP range?

Patrick - Deleting the ranges and re-creating them doesn't change anything really. Is it possible that the first time around the discovery ranges had some invalid info - like password or protocol?

I suppose there is no good way to determine what happened before. All I can confirm is that creating the same range again doesn't really change anything when you attempt to re-discover.

If discovery is working now, then the logs will not have much debugging value to us. Hope you are able to turn off logging, so as not to fill up your C drive.

As for the Unknown iDRACs, go ahead and try what Pupul has suggested.

PPrabhu

Hi,

would you be able to advise for where can I logged the case for the OME?

I cannot find anything relevant on the website.

thanks

Patrick