I'm standing up a test-server to replace our old essentials one. I've managed to install the server and login via the web. I set up NTP and now I'm looking to discover devices. However, I haven't been successful importing a variety of devices that existed on my essentials server, including servers (windows), idrac, and MD storage devices. I've tried using DNS and IP addresses. Domain accounts (for the windows hosts) as well as local accounts. I've attempted SNMP for the MD storage devices. Some are on the same network as the OM Enterprise server, others are not.
Each discovery log comes back with:
CGEN1013 : Unable to connect to the device over because a connection error occurred.
We have a support matrix published off of the DTC page that might help with the list of supported devices in this first release.
Just to get things started, let's make sure it can discover your iDRACs correctly. So if you go through the default path on the discovery wizard it should take you to the basic WSMan discovery where you can enter the IP addresses or range for your Servers/iDRACs.
This release does not have much support for in-band discovery like OM Essentials did. With that product, you could discover SNMP+OMSA or WMI+OMSA. Not so for Enterprise--it's more iDRAC (out-of-band or agent free) focused.
There is some basic SSH / Linux support, but the inventory is less compared with iDRAC/WSMan. There are some notes in the user guide / help I believe that could get you some in-band Windows discovery. But the setup on the end-node is burdensome.
For storage in this release, our support is limited to Compellent and we're evaluating interest in other storage products. So I'll definitely pass along the interest in MD.
To clarify, are you saying this product ONLY actually works with DRAC and not OMSA? If so, it's pretty much belly up for us, and I'm hard pressed to understand how this could be the case as it guts the product. I had zero success in discovering my servers, and now it seems the reason may be that it can't? For a product that's already a year overdue based on browser tech discontinuation, this is not encouraging.
Yes, that is correct. The product focus is mainly on iDRAC discovery although there is some ability to discover in-band Windows or in-band Linux/SSH.
I'll make sure I pass along your feedback on the h/w support level to the right folks. I'm assuming you are looking for support for pre-12G PowerEdge models, correct?
I've installed Dell OpenManage Enterprise yesterday. I can find and discover server via iDRAC discovery on the same subnet that OME but when a started discovery on other subnet i've the same error like other guys.
I've OpenManage Essential that run successfully on all iDRAC from all server of my compagny.
Ok, just to be clear, can you specify what model of PowerEdge server you are trying to discover?
In OM Essentials, we supported both SNMP and WSMan discovery of an iDRAC. For Enterprise, we are supporting only WSMan discovery of the iDRAC.
The different subnet should be ok. Did you put those in the same discovery task or a separate task? I wouldn't think it would matter, but for the purposes of troubleshooting, maybe create a new disc task and enter a known IP from that subnet just to check. And be sure to use just WSMan default settings.
You might try using the Dell Troubleshooting tool to double check the connection to one of the iDRACS. It kind of depends on your environment as to if that tool will be useful (it's Windows based, etc.). But in some cases it can help if you run the WSMan test.
Thanks for the post. As you point out, if the networking and f/w is set up the same on the 710/910, you should be good to go. I'm assuming you are using the default settings for the disc wizard (just WSMan only).
Sometimes, for debugging, it is helpful to create a new discovery task with just a single IP for one of the 710/910 servers.
Can you see if the troubleshooting tool can run a successful WSMan test to connect to one of the 710/910?
svepau
11 Posts
21024
0
Posted January 21st, 2018 22:00
i have also had the same issue.
this happens every time i try to discover windows hosts.
i have tried discovering with ip and fqdn.
it works fine with idrac and cmc for me, discovered by ip range