Thank you, Abhijit.

Where can I access the troubleshooting tool?  I am using SNMP protocol.  The physical server has OpenManage Server Administrator Version 7.1.0 installed.  

I thought OME supported VMs (Microsoft Virtualization category under Devices).  Ok, thank you.

The OME server does have access to the Internet.  Do I need to make an exception under Internet Options?

Hi,

Thanks for your post.

OME does not support classification of VMs. The VMs will be classified as unknowns in the OME device tree. For the physical server, you can try using troubleshooting tool for the protocol you are using for discovery and it will help you isolate the problem in connectivity/credentials. Another thing to check would be, if you have OpenManage Server Administrator installed on that server.

Regarding the import catalog, I assume you are pointing at the default Dell FTP catalog. You can verify if you have internet access and if you need proxy, you have entered those credentials in the preferences tab.

Regards

Abhijit

Thanks for the updates. Can you try running the import catalog task again after deleting the devices under unknown group?

Regards

Abhijit

It is possible that the discovered VMs inventory may be interfering with the catlog import task. Is it possible for you to delete the devices under unknown group and then run the catalog import task?

Regards

Abhijit

Thank you Rob and Abhijit.

I have found the issue in the physical server (misspelled public) and now it works fine.  

Oh I see.  Thank you for the clarification.

Yes, I have done what you instructed by downloading the .cab file and importing it.  It now says "Current catalog version is the latest".  However, in the Task Execution History, I still get the same error as mentioned above.  

The TS tool is on the desktop of your OME server.  We install it by default.

There is a preferences screen in OME where you can enter proxy information.

Good luck,

Rob

Hi,

Thanks for the updates.

Troubleshooting tool is installed with OME. You can find the shortcut to launch the tool on the desktop or in the Start menu under Dell->Troubleshooting Tool. For SNMP, the community name is case sensitive. You can check the name specified in the discovery wizard and the one specified on the target server under SNMP service. The First Time Setup Tutorial located under Tutorials Menu will guide you through the steps for SNMP discovery.

OME supports discovery and classification of physical servers(hosts) running the VMs. This includes classic ESX/ESXi/Microsoft Hyper V servers but it doesn't support classification of the VMs running on those servers. The inventory of these physical servers will show the list of VMs running on those servers.

Are you able to download ftp.dell.com/.../catalog.cab using the browser on the same server? If so, you can try downloading that file and use Manage->System Update->Select a Catalog Source option and point to that downloaded catalog to import.

Regards

Abhijit

Thank you Abhijit.

I have deleted the unknown devices and tried reimporting the .cab file.  The error message still came up again.

Thanks for the update.

It does look like data issue. _Only_ do this process if you are familiar with SQL server management studio and comfortable with executing SQL scripts. You can try clearing old catalog data from the database.

1. Back up the database

2. Use SQL Server Management Studio to connect to the OMEssentials database and execute the script below.

USE OMEssentials

GO

Delete from Catalog.Manifest where SourceId = 1

GO

3.Try import catalog from ftp again

Otherwise you can open a support ticket and they can help you with the necessary steps. Here is the number 800-945-3355

Regards

Abhijit

Thanks for the update. I'm assuming you had only used FTP as the catalog source and have not imported catalogs from SUU or repository manager as a source. I'm also assuming that you ran the script and still see the same error.

In that case there is one last thing you can try before calling in support. If possible you can try deleting all the discovered devices and then run the catalog import. You can re-run the discovery and inventory to get the devices back in the tree.

Regards

Abhijit