Hi Tom,

Thanks for giving OME a try.

First:  When you say the Dell TS tool worked ok...can you tell me _exactly_ what showed up in the result set for the SNMP test?  It should have included the version of Server Administrator if the test worked ok.  I just want to be sure on that.

Second:  If you are discovering Windows via SNMP, you will need OMSA on the box.  You can try to discover via WMI and OMSA as well.

Third: Check your OMEAdmin and OMEUser groups in Windows and see if they look as you expect.

Hope this helps.

Rob

Follow Up THIRD Question:  Where can I change the authentication.  It seems like any user with an Active Directory account can log in, not sure what I did for this, but I want to make it so either one user name must be used for login, or maybe certain groups!  -Tom

So on one of the servers that I run the test on, here is the result:  

Openmanage shows the server with an unknown health status, and therefore shows it essentially being in an error state.

Openmanage seems really cool as far as how granular it can get with monitoring, but some things aren't as easy as I would've hoped.  I have servers showing in Warning state because they have outdated drivers, and I need to figure out how to ignore that, as I really don't care if the drivers are outdated since everything is working..however, I do want to know if something really is going wrong.    Maybe I just need to ignore driver errors, if possible, I will try to figure that out.

Thanks for the response!  If you know how I'm supposed to add Direct Attached Storage (MD3000) let me know, that also comes up under unknown status.

Hi Tom,

Good detail, thx.

Ok, so...

1. It _looks_ like OMSA is not running correctly on the managed node you are trying to discover.  

Is it Win or Linux?

If you go to that server, are you able to start up the OMSA gui on that box directly?

The reason I say this is that the TS result you attached are supposed to have a line in there for "Server Administrator" and show the OMSA version next to it.  If this is missing, then OME will not be able to discover and inventory it fully.  Sometimes for OMSA+Linux, the snmpd is not running and you see this.

2. I thought the MD3000 is a modular storage array and not just DAS.  But anyway, in your discovery wizard, there is a page for storage, and if you check Enable MD Array discovery.

If it is just DAS/JBOD, you have to be sure you install the OMSS (storage) component of OMSA.  I'm not an OMSA expert and can't recall if this is default or not.

3. Lastly, I"m not _positive_ if the SC series of PowerEdge supported OMSA (again, not an expert on OMSA).  But sometimes folks manage to shoehorn OMSA on a variety of systems/OSs.  

Hope this helps.

Rob

Rob, thanks again for the response.  I tried to log in to the server that showed it was failing today, and received couldn't log in, none of the credentials I tried seemed to work.  I even checked active directory authentication, and logged in with a working account, no luck.  So I think you are correct, I will need to try to re-install OMSA on that server, and than check it.  To further back up your point, when I go into the server reporting unknown health status, I see it as being discovered by WMI under Software Agent Information.  I just assumed since it was an old server that it wouldn't work, but I will need to do a reinstall to test that.  The server I am seeing that is a Windows Server 2003.  If it does not work, I'd still like to monitor it with a basic ping command and have that come back as showing online, rather than an unknown health status.  

2.  I'm an idiot.  You were right, as simple as checking the box for Powervault Storage Discovery.  Whoops!

3.  I swear I found that SC series did NOT work, but even if I can just put it in there with a simple ping test I'm ok with that.  If you could specify the specific tests on some devices that would make the product better, AKA if I could just realize I have an old server, still want to monitor ping, but want it to always show as "Green" unless it stopped responding to ping.

Ok, check out the OMSA install as you mention and let me know.  Even though it is an old server, I would think once you re-inst OMSA you should get it to work ok.  On your SC, if you determine that OMSA won't install on that series, you may be able to discover it via WMI and get it classified as a server with some limited inventory.  So give that a look too.

Let me know how the MD discovery goes.

thx

Rob

I did a reinstall of OMSA on the server.  However, it said it will only install the web client.  So, I went through the web client, and when I try to launch that I get a login screen asking to specify username and password.  

Is there a default username/password?  I did try to use WMI, and I believe I have that working since it found the CPU speed, amount of RAM, and some other details, but not everything.  It classifies it as a server, but health status is unknown.  

I was able to discover both of my MD3000 storage array's, and they are monitoring correctly, so that's cool.  

Hmmm....there seems to be something going on with the OMSA install on that server.  I'll see if I can find some more info.

Once it is installed correctly, you should be able to start the OMSA gui on the server itself to ensure it is ok.  AND the Dell troubleshooting tool (installed on the OME server) should return the version of Server Administrator in the result set when you do a WMI or SNMP test.

Often I use localhost\administrator when I discover via WMI.

Glad the MD are looking good.  Let's sort out the OMSA install.

thx!

Rob

Ok,

So I suppose OMSA is not installing since it's not on the OMSA support matrix.  I'm not sure myself if there is anyway around this...maybe google around a bit.

You might get some limited support  if you discover via WMI with no OMSA, but I'm not certain as we test with PowerEdge only.

Hope this helps.  Thanks,

Rob

support.dell.com/.../Support_matrix.pdf

Is there a username and password that it comes pre-installed with?  I get to the login page, on the one server and I can't log in, even using Active Directory authentication.  If I do the Dell troubleshooting, and than do the WMI test, it will pass.    I couldn't get it to work with localhost\administrator, but it passed with domain\administrator, so I used that instead for discovery.