Here are a few other things to look for. Sounds like you checked 3.6.
Rob
--
Here are the important items to check when you are chasing down OME Discovery and Inventory issues.
1. Check FAQ 3.6 if inventory is not showing up.
2. Be sure OMSA is on the managed node (target) if you are using SNMP/WMI (#3.3)
3. Be sure you have “accept packets” checked on your managed node (#3.4)
4. If discovering a 2008 server, see item #3.5
5. Be sure you check the community string, remember they are *case sensitive* (#3.4). Did you type it in correctly in the discovery wizard? Did you type it in correctly in the managed node SNMP properties? Did you type it in correctly in the TS test screen?
6. Run the SNMP troubleshooting test for SNMP or WMI. For SNMP the results *must* include the version of OMSA in the table. For WMI the results *must* contain the words “Dell Server Agent” for the namespace returned.
The conditions you mentioned above have been met and it still cannot find them. All of our servers have these same settings and most have been inventoried. It's weird that 5 or 6 of them just don't seem to want to work with OME
DELL-Abhijit P
Community Manager
•
711 Posts
0
March 14th, 2012 14:00
Have you tried FAQ 3.6?
TradeVue
4 Posts
0
March 15th, 2012 07:00
Yes. DSM SA Data Manager is running. We also restarted the DSM SA Data Manager service and tried to discover/inventory again but still no luck
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
March 15th, 2012 08:00
Hi,
Here are a few other things to look for. Sounds like you checked 3.6.
Rob
--
Here are the important items to check when you are chasing down OME Discovery and Inventory issues.
1. Check FAQ 3.6 if inventory is not showing up.
2. Be sure OMSA is on the managed node (target) if you are using SNMP/WMI (#3.3)
3. Be sure you have “accept packets” checked on your managed node (#3.4)
4. If discovering a 2008 server, see item #3.5
5. Be sure you check the community string, remember they are *case sensitive* (#3.4). Did you type it in correctly in the discovery wizard? Did you type it in correctly in the managed node SNMP properties? Did you type it in correctly in the TS test screen?
6. Run the SNMP troubleshooting test for SNMP or WMI. For SNMP the results *must* include the version of OMSA in the table. For WMI the results *must* contain the words “Dell Server Agent” for the namespace returned.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
March 15th, 2012 09:00
Hmmmm...ok, let's dig a bit more :)
What protocols do you have enabled in the discovery wizard?
What version of OMSA is on the tricky servers?
Are there any environmental characteristics unique to these servers (e.g., diff network setup/limitations/firewall)?
When you go to one of the tricky servers, does the OMSA gui start up ok?
OME can ping the server and server can ping OME with full DNS name resolution?
Can you do a visual compare with one of the working servers? (e.g., SNMP properties, OMSA version, ping -a ipaddr behavior, running services)
thanks,
Rob
TradeVue
4 Posts
0
March 15th, 2012 09:00
Thanks for the help.
The conditions you mentioned above have been met and it still cannot find them. All of our servers have these same settings and most have been inventoried. It's weird that 5 or 6 of them just don't seem to want to work with OME
TradeVue
4 Posts
0
March 15th, 2012 10:00
-We are using ICMP, SNMP and WMI.
-Some are running 6.1 and some are running 6.2. The servers that were identified/inventoried are also running those same two versions.
-I'm continuing to work on this one. I'll update you if I find anything suspicious
-The OMSA GUI works fine on all of the servers.
-The servers can ping eachother and resolve DNS
-I have compered trouble servers and normal servers side-by-side and everything looks identical