Unable to discover using OpenManage enterprise

Hi Rob,

I have almost the same scenario, 2 R720 Servers, one was discovered and the other no. It says this:

Hi @GokuH12 and thanks for the question.

I see this error when there is not a good network route between OpenManage Enterprise and my iDRAC.

Can you confirm?

Thanks,

Rob

Hi @DELL-Rob C, thanks for the quick reply!.

All the 3 machines are in the same subnet (X.X.X.14, X.X.X.59, and the OME in X.X.X.20, the bolded is the one that wont work), and the same switch inclusive. I though about doing a ping from the OME but cannot find a way to get a console there.

Cannot think of anything more,

Hi @GokuH12

Hmmmm...ok, that's a puzzle.

Can you try the Dell Troubleshooting Tool and run the WSMan test against that box?  It is still a Windows based tool, but perhaps if you run it in the same network, it can be helpful.  

Did you enter IP or hostname in the Discovery Wizard? (maybe try IP?)

Assuming userid and password is the same as the 'good' ones...

Thanks,

Rob

http://en.community.dell.com/techcenter/systems-management/w/wiki/4172.dell-troubleshooting-tool

Just joining in for the feature requests for in band discovery.

We need it for both old hardware (8th/9th gen servers still gamely hanging on) and also because of limitations of parts of our network - some devices are only discoverable via the production network in environments where there is no out of band network avialable.

I can't believe such a fundamental requirement was omitted!

Yep, understand.  Will provide your comments to the right folks.

Thanks much,

Rob

To be honest if we wanted to discover via the Windows OS directly we'd just build our own discovery scripts.

The main benefit of using OMSA in-band is we can discover with SNMP (on a couple of ports) in isolated / secured environments where it's just not feasible to open up all the RPC ports needed by WMI. 

Also for independent windows servers (e.g. not in a domain) we don't need to maintain local credentials across many systems - we can just use a single SNMP community name.

Thanks, David

Hi Rob

We are testing OME in a lab with a PowerEdge T130 with iDRAC8 and Basic Management license. Until now no success because the job keeps fail with error message "Unable to connect to the device.Task Failed. Completed With Errors.". We have Redfish enable on iDRAC and we want to troubleshooting with standalone version of Dell Troubleshooting Tool but we cannot find this tool. Can you share the link to download the tool?

Regards,

José

Hi,

You can find the Dell Troubleshooting tool at this link: https://www.dell.com/support/article/us/en/04/sln311059/dell-troubleshooting-tool?lang=en

Also, when you are trying to perform discovery, are you using only Redfish or WSMAN and Redfish, both? Since you have a basic management license, i would recommend using WSMAN as that will gather more data for you

Hi Pupul,

Thanks for your reply. We are only testing with Redfish. To use WSMAN we have to install the iDRAC Service Module on the operating system DellEMC Customized Image ESXi 6.5U2 A04 of this server. 

When accessing to the Drivers and Downloads page for the PowerEdge T130 we can only find Dell EMC iDRAC Service Module (VIB) for ESXi 6.5 U1 & 6.7, v3.2.0. After installed this one, we get the warning on iDRAC Web GUI "RAC0690: The iDRAC Service Module is not installed on the operating system of the server. Install the Service Module and retry the operation."

Do we have to wait for the release compatible with the customized Image ESXi 6.5U2?

Regards,

José.

Sorry if this got digressed somewhere. Your first post looked like you are trying to discover the iDRAC for the server model T130, is that not correct?

If you are discovering iDRAC, you don't really need iSM installed. WSMAN discovery of iDRAC provides almost all the necessary details from a server.

Hi Pupul,

Thanks for your reply and sorry if I caused any confusion. Yes I'm trying to discover using WSMAN/Redfish the iDRAC for the server model T130 with the default Connection Settings (retries, timeout and port), but I'm always getting the error "Unable to connect to the device.Task Failed. Completed With Errors." when discovering the T130. If I try to discover the T130 by using ESXi I have success. My BIOS Version is 2.5.0 and Firmware Version is 2.50.50.50

Thanks

José

same here. inband isn't working for us for any Windows/HyperV/ESXi/Linux physical servers despite OMSA being installed and SNMP configured. Essentials worked like a charm, but with Enterprise, none of the inband options work for us, neither SNMP nor WSMAN, and it appears like Windows WMI was removed completely. In our environment, we cannot install IIS on every server just for the sake of monitoring as the manual suggests. It's not a feasible solution for us. I'll keep checking for enterprise updates but in the meantime, we've had to disable the inband monitoring cause openmanage enterprise was causing our 6.5 ESXi host's root passwords to be locked out. Please bring back inband monitoring. iDRAC isn't 100% reliable. it's a single point of failure for hardware monitoring. 

Hi @benitez and thanks for the post.

Yes, we are definitely more on the out-of-band/iDRAC side of things with the new product.  The lockout issue is a concern--is it possible one of your discovery jobs is hitting your ESXi with the wrong password?  I wonder if you were to put the ESXi in it's own discovery range.

We may need a support ticket to dig into the lockout issue further.

So other than the ESXi discovery, the in-band options are limited as we don't use SNMP or OMSA for discovery of servers any more.  I'm passing this note along to the right team to review your request for more in-band support.

Thanks,

Rob

--

I'll put the phone number here, but I need to enter it in a goofy format since this forum software strips out a lot of numbers.

8-0-0-9-4-5-3-3-5-5