Good morning, good afternoon, and good evening. My name is Dustin.
I am a Subject Matter Expert in the systems management space. Today I will be going over
troubleshooting discovery in OpenManage Enterprise. So first let's start with
the most common device that you're going to see in OpenManage Enterprise and that is the iDRAC.
So the iDRAC, it uses WSMAN for discovery and it uses 443 to talk on WSMAN for discovery.
So what you want to do is, let's go ahead and do a discovery real quick.
Let's do an iDRAC9, I'm going to put the password in,
we're going to run it now.
So the first thing you're going to want to do is just look at the the job itself. Let's see what
OME says the reason for the failure is, and OME is telling me that it could resolve the IP, it can
ping it, but it couldn't reach it by WSMAN. So now we've got to start doing some troubleshooting so
the first thing you want to do is log into the iDRAC, make sure your credentials are correct.
All right, so we know our credentials are correct, and we don't think that's the issue,
so let's look at the next things we want to. First we're going to
talk to the firewall team and make sure that obviously 443 can be reached and everything.
The next thing we can do is a tool called the Troubleshooting Tool. This
is something that you can just Google and download that's provided by Dell.
And i already have it running, and when you're here you can go to protocols and choose WSMAN,
put in your iDRAC IP, make sure you 'Skip CA' and 'Skip CN',
and run your test. And what you'll see on this test are what looks like a couple failures, and
I'll talk through them real quick. First what's happening is it tries to reach it using TLS 1.0.
It can't, so then it tries using 1.1 and that one was successful so it stops there.
Then from there it finds the profiles, that's what we're expecting to see,
we want to see all these profiles. So from here we go okay, credentials work, i can talk to it
on 443, I'm seeing my profiles, what else could be the issue? One of the last things i like to
try is actually a WinRM command from a Windows system. It's important that we have this on
the same network for it, so it's kind of apples to apples and then we just can really test it.
And that's what we would expect to see. So this is all working correctly.
Let me try this again and make sure that I didn't put the wrong password in when I did it here.
Now I can go to 'Jobs' and it looks like it's already running, it's already gotten further
than before so that was probably the case but it was nice to be able to run through all of those
options for troubleshooting. One more thing to suggest if you ever have just one iDRAC out of
many that won't discover or is having issues with WinRM, just reset it and see if you have a better
experience. So now let's talk about chassis. Chassis are going to be pretty much the same.
Your WinRM command is going to look a little different but not too different.
I'll keep that posted up there for a moment while i talk through this real quick,
but basically you're going to do the same thing. You're going to want to test that WSMAN through
troubleshooting tool, it also uses 443. Nothing's changed and rather than reset the iDRAC if one is
affected you can always try a fail over the CMC. Another really important thing to note
for both iDRAC and chassis is you will want to check the support matrix for OpenManage
Enterprise and make sure that the chassis or iDRAC is at the correct firmware levels for discovery.
So now let's talk about Windows Server. So Windows Server discovery uses
SSH on port 22. And it's an Open SSH, and the biggest things you want to do is go to the Windows
Server and make sure everything is installed correctly. So you'll want to go to 'Settings',
'Apps', 'Manage optional features' and ensure that OpenSSH server is there. Secondly you
will want to check the services to make sure that that service is automatic, and started.
And it is manual see, so mine wouldn't have worked so i'm going to want to start that,
and I want to do 'Properties' change that to 'Automatic' and 'Apply'. This way it starts every
time the service starts, so every boot up the server doesn't lose communication with OpenManage,
and lastly, the biggest thing that you could do if this still wasn't working is you could do a packet
capture. Make sure that it actually is able to talk on port 22. Make sure that the firewall isn't
blocking port 22 as well. That's definitely, there is a firewall rule just for that.
And that rule looks like this, OpenSSH Server.
So another one that we discover in OME that's uh,
it doesn't happen very often we do, it's storage devices.
So storage devices are going to be using SNMP on port 161. So the biggest thing you want to do
is go to the storage device itself, and make sure you check that the SNMP configuration is correct.
You can use the Troubleshooting Tool to test SNMP as well.
Just here you put the IP address of your storage device, the community name you have
set and you'd run a test and that let you know if it can talk to it on SNMP or not.
And then lastly the network switches. So again we talked earlier about checking the support matrix.
There's not a lot of network switches that are currently supported, so you'll definitely want
to check that first so you don't waste any time. Network switches also use SNMP on port 161,
so again you could use the same Troubleshooting Tool that you did for the storage to check
to see if that's going there. Make sure your community string is right in the network switch
and then lastly if nothing else works you can go and export your console logs and you can
look in there as well to see if you have any extra information on why maybe the discovery is failing.
So that's it. I hope you enjoyed my video on discovery troubleshooting
and OpenManage Enterprise. Thank you, and have a wonderful day.