Isn't OME supposed to be able to at least discover equipment through SNMP only? We have all Dell servers in our infrastructure, most are Windows. I still haven't gotten Linux to work at all but I'm taking things one step at a time and getting windows ironed out.
I understand that in order to get FULL inventory and management of a system, the OMSA needs to be installed on the windows system. However, if I have a dell server that I DID configure SNMP properly, but have not yet installed OMSA (with the intent that OME could push OMSA to it), OME will NOT discover it at all. Not as an unknown device or anything.
SNMP ports are open through all VLANS and I've run the test tool with what seems like successfull results:
the "Services" test using my Read Community Name does report back all of the currently running exe's on the system. And the "SNMP" test returns "MIB-II (System Name)" on the left and the actual server name on the right.
So it seems that communication is working properly, but OME just wont pull anything into inventory that doesn't already have OMSA installed on it... but it should shouldn't it?
Also, I had the same problem in IT Assistant. I was hoping that upgrading to OME would fix this problem but it didn't.
Once I get this squared away, I will continue to work on the Linux portion.
oh yeah, and I've seen this more with my linux tests - but another indication that SNMP is configured properly is because I am getting emails of traps from systems that aren't in inventory. When I was tring to get ESX working, we got it so that I was getting notifications that the guest OS's heartbeat was lost. Those notifications were going through IT Assistant (and now OME) - but still the host itself doesn't come into devices when doing discovery on SNMP only. (by the way, sorry for the typos above - I meant OMSA, not OSMA).
Please double check FAQ item #3.4. And two other points:
1. SNMP community strings are *case sensitive*
2. The SNMP test on the Dell Troubleshooting Tool should return the value of the OMSA version for a successful test. If the OMSA version is not there, you have a config issue to address.
Wow, changin that to "All Devices" did it. I never tried that option because I thought that would bring up even more stuff than just Dell Servers (which it did) - But there was my my missing test server that I only did SNMP without OMSA on - in addition to two other "Unclassified" devices.
I'm surprised that even though SNMP only was able to pull up enough info of it being a Dell PowerEdge Server and it's name and Service Tag - I still needed to turn on to All Devices rather than just Instrumented Devices.
I was hoping to leave that off because I didn't want to be cluttered with Printers and Switches and the like (they are all managed by other teams). But I guessI will just have to create filters to filter them out.
right, I can ping the server just fine, RDP to it, open windows shares... the lot - but no information shows up at all, not even in Unknown, after doing a discovery without OSMA. the only way I see ANYTHING at all in devices, is to have OMSA installed on the target. And that's just not cutting it for me. I need to be able to discover everything so I know what systems I still need to load OSMA onto.
Ok, I did read that section before, but I think I was confusing it with more of an OR statement. As in, select Instrumented Devices for OMSA, OMAM, PowerConnect, SNMP, WMI, WS-MAN...
Rather than it being OMSA *WITH* SNMP, WMI, WS-MAN...
I took it that as long as I had WMI login credentials and/or SNMP was set up properly, I could still be on Instrumented devices in order for basic discovery.
Thank you for the clarification. I think I'm all set and straightened out on this thread now. Again, thank you very much for your help.
victor_waelchli
91 Posts
1323
0
Posted January 26th, 2012 12:00
if you are able to ping the target you should get some information into Unknown on the device list.
if you want it to have the proper information for the server you must have Open manage and SNMP configured.