Unsolved
This post is more than 5 years old
4 Posts
0
215253
April 11th, 2013 09:00
OPENMANAGE ESSENTIALS Unknown Device Type
Currently I have a PowerEdge R710 that continues to show Unknown Device Type. I used the TroubleShooting Tool to test SNMP. It returned the System Name, Mac, Server Admin Version 7.1.0, Storage Agent Version 4.1.0, and Inventory Agent Version 7.1.0. Do you have any suggestions on how to get this device to display as a Server?
No Events found!


DELL-Rob C
4 Apprentice
•
2.8K Posts
0
April 11th, 2013 09:00
Hi Anthony,
Here are a few things to consider (some you have already confirmed). And we'll go from there.
Regards
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
4 Apprentice
•
2.8K Posts
0
April 11th, 2013 12:00
Ok, so this really has me curious. 99 out of a 100 it is going to be that the OMSA service has failed on the managed node and is not running....OR, the user has typed in the SNMP community string with the wrong case (upper vs mixed vs lower case).
Do you have any other servers in this discovery range that _are_ classified correctly as a server?
Is SNMP the only protocol enabled?
For debugging purposes, can you create a new discovery range with just _one_ server (the problematic one) in it and SNMP as the protocol? Be sure that IP does not show up in any other range, etc.
Thanks,
Rob
anthony.lawson
4 Posts
0
April 11th, 2013 12:00
All these steps are setup correctly. The server still shows up as Unknown Device Type.
YoungyLives
29 Posts
0
January 6th, 2014 19:00
Holy thread revival I know - but this appears to be the closest to the situation I find myself in.
I have just added two new R720s to an already established range. One server has been added successfully and the other is still unknown.
I have checked the SNMP community name settings etc and that all looks ok.
However from the testing tool and what you have said above Rob I am missing something - just not sure what.
When I run the SNMP check with the troubleshooting tool I get a response with the Server hostname and MAC address of the interface correctly. However I do not get:
Server Administrator (Version)
Storage Management (Agent Version)
responses as I do with other working servers.
OMSA is installed on the 'unknown' machine:
]# omreport about
Product name : Dell OpenManage Server Administrator
Version : 7.3.2
Copyright : Copyright (C) Dell Inc. 1995-2013 All rights reserved.
Company : Dell Inc.
and I can see that OMSA is running:
# srvadmin-services.sh status
dell_rbu (module) is running
ipmi driver is running
dsm_sa_datamgrd (pid 32676 32615) is running
dsm_sa_eventmgrd (pid 32722) is running
dsm_om_shrsvcd (pid 32783) is running
dsm_om_connsvcd (pid 32809 32808) is running
I can also run omreport commands on the 'unknown' server without any issues and get expected results. The server itself is running Centos 6.5.
I hope someone can help me out here.
Thanks
YoungyLives
29 Posts
0
January 6th, 2014 22:00
Hi,
Thanks for the reply.
a) no firewall is in play on the unknown host
]# iptables -vL
Chain INPUT (policy ACCEPT 10989 packets, 1049K bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 506 packets, 63149 bytes)
pkts bytes target prot opt in out source destination
b) have done that already - did not appear to change the symptoms at all
c) I will assume that they are fine since the OME machine can see all other machines as part of the same range as the unknown machine.
Thanks for reply
DELL-Pupul M
2 Intern
•
1K Posts
0
January 6th, 2014 22:00
Hi,
Can you check for the following things:
DELL-Pupul M
2 Intern
•
1K Posts
0
January 6th, 2014 22:00
Okay. Can you try restarting the SNMP service and see how it goes? I am sure you have configured the SNMP service for both the servers same way so that the discovery happens properly. You can even use the SNMP configuration tool for linux and windows servers from http://en.community.dell.com/techcenter/extras/m/white_papers/20097170.aspx
cameronredux
2 Intern
•
615 Posts
0
January 7th, 2014 08:00
@YoungyLives
I am curious why you are using OME to gather data on these R720 machines via SNMP and OMSA and server IP rather than via WS-Man and DRAC IP?
YoungyLives
29 Posts
0
January 7th, 2014 17:00
Hi,
I have restarted the SNMP service. I have diffed the snmpd.conf files between this unknown server and a working server and there are zero differences.
Still no joy at this point.
@Cameron
In this specific case the DRACs are not connected and they won't be connected due to unusual environment setup. Given that I have 20 other servers all working with OMSA happily on the same IP range I think this might be a bit of a tangent.
YoungyLives
29 Posts
0
January 7th, 2014 19:00
Hi Rob,
That is exactly the issue - when I run the toll against the machine I do not see the Server Administrator version in the result - WHY is the million dollar question.
I can't see an issue with the setup so at this point I may just start over and uninstall all the OMSA blah etc
DELL-Rob C
4 Apprentice
•
2.8K Posts
0
January 7th, 2014 19:00
Hey there,
Sorry, I've not followed this entire thread. Have you run the Dell Troubleshooting Tool (installed on the OME desktop) and run the SNMP test against the server? You must see the Server Administrator version included in the result set. Otherwise the device won't be classified. If you don't see the SA (OMSA version, that indicates a setup problem on the target device. The OME first time setup tutorial may have some tips here. Or maybe one of the OME whitepapers or videos for Linux (I think we used to have one).
Not sure if that will help you. Good luck
Rob
DELL-Rob C
4 Apprentice
•
2.8K Posts
0
January 7th, 2014 20:00
ah yeah, ok. Right so as you say, looks like an OMSA config issue on the target box.
There is an OMSA DTC page here, not sure if that would help:
http://en.community.dell.com/techcenter/systems-management/w/wiki/1760.openmanage-server-administrator-omsa.aspx
And a general sys mgt forum here where some OMSA guys may hang out:
http://en.community.dell.com/techcenter/systems-management/f/4469.aspx
I think the tutoral page talks about some of the changes to the SNMP config file on Linux that have to be made, but I can't recall for sure. I know that OMSA can appear to work ok, but if the SNMP changes are not made correctly, then the instrumentation won't work right. I think we detail this on the video on our DTC/OME page.
Thx
Rob
YoungyLives
29 Posts
1
January 7th, 2014 22:00
Thanks.
So far I tried this:
a) yum erase $(rpm -qa | grep srvadmin)
b) yum erase $(rpm -qa | grep snmp)
c) yum install net-snmp
d) setup the conf file again
and what do you know when it starts I see this in the OME:
So SNMP is fine.
e) yum install srvadmin-all
f)
# srvadmin-services.sh status
dell_rbu (module) is running
ipmi driver is running
dsm_sa_datamgrd (pid 13143 13086) is running
dsm_sa_eventmgrd (pid 13192) is running
dsm_sa_snmpd (pid 13251) is running
dsm_om_shrsvcd (pid 13324) is running
dsm_om_connsvcd (pid 13350 13349) is running
but when running the tool I don't see the Server Administrator version.
I did a diff as I said between this hosts and another working hosts SNMP config and I am happy to say they are exactly the same.
YoungyLives
29 Posts
1
January 7th, 2014 22:00
Little footnote.
I then restarted the SNMP process and now everything is working as expected. I hope that helps someone else out at some point.
Thanks everyone
DELL-Pupul M
2 Intern
•
1K Posts
0
January 8th, 2014 21:00
Thanks for letting us know :) Great that it is working