February 27th, 2012 07:00

Clarification on this:  It will inventory as a Server, however, when going to System Update, I am not able to create update tasks for the server as it shows as being "non-inventoried".

Community Manager

 • 

711 Posts

February 27th, 2012 07:00

Thanks for the post. From your note it looks like troubleshooting tool is able to communicate to OMSA on the target server using SNMP. In that case the server should be discovered correctly.

Does the server show up as unknown in the device tree? In that case, can you delete it and try to discover it again?

Regards

Abhijit

Community Manager

 • 

711 Posts

February 27th, 2012 08:00

Glad to hear that the issue is resolved. Do let us know if you have any other feedback for OME.

February 27th, 2012 08:00

After deleting the device and re-adding, it is showing up as an Unknown Device now.  Before the deletion, it was showing as Server, however, machine was showing as 'non-inventoried' when trying to create a System Update Task.   Not sure what to try now.

Community Manager

 • 

711 Posts

February 27th, 2012 08:00

Can you try the troubleshooting tool again for the same server. It looks like there may be an intermittent issue while talking to the server using SNMP especially if it was detected as server earlier and coming up as unknown now.

The server shows up as non-inventoried when OME is not able to get the software inventory information from the server. This is related to server not being detected as server. Looks like OME is not able to communicate with OMSA on the server.

February 27th, 2012 08:00

I've been battling this issue for a few days now, and every time I run the troubleshoot tool it comes back with the correct version of OMSA.  I've probably ran the tool 25 times in the last 5 days, each time it is a success.  I appreciate the help so far, this one has stumped me.

February 27th, 2012 08:00

RESOLVED:  I've been spending so much time troubleshooting the OME side of this issue, I didn't look at the server closely.  The 'DSM SA Data Manager' service was stopped on the server.  I started that, then restarted the SNMP Service, did a re-inventory and now it's working correctly.  Glad it ended up being an easy fix, thank you for your time!

Community Manager

 • 

711 Posts

February 27th, 2012 12:00

Thanks again. We will add this information to the FAQ section

February 27th, 2012 12:00

For what its worth, I've had a few other odd inventory issues, all were solved by restarting the DSM SA Data Manager on the problem server

Community Manager

 • 

711 Posts

February 29th, 2012 11:00

Do you have OMSA installed and SNMP enabled on the target machines? Good place to start would be to run the troubleshooting tool and check if you get appropriate response over SNMP.

15 Posts

February 29th, 2012 11:00

I am having a similar but different issue. All of my machines are showing up as either not inventoried or in an Unknown status. And this is on a fresh new OME (production version) install that I just pulled down today. - Any ideas?

No Events found!

Top