Video Screencast Help

Virtual Machine Management Solution and vSphere Versions

Created: 15 Sep 2011 • Updated: 08 Nov 2011 | 9 comments
This issue has been solved. See solution.

I haven't been able to find a support listing for this solution, so I figured I'd throw it out to the community. We are running SMP 7.0 SP5 MR4 with Virtual Machine Management at build 7.0.1013. Our VMware vSphere environment is 4.1. I am having difficulty performing the initial discovery process for vSphere 4.1. However, scanning / discovering the individual ESX 4.1 hosts is not a problem.

Does the above version of virtual machine management support vSphere 4.1?

The credentials being used to connect are vSphere admin and have been tested against VMware's web console with success.

My thanks for the versioning information.

Comments 9 CommentsJump to latest comment

Joseph_Carson's picture

Hi MonitorMan,

That version of VMM supports ESX 3.5 and ESX/ESXi 4.0.  It did not support 4.1. but i believe you should be able to get it to work by reclassifying the Resource Type correctly and then this should allow you to run the Inventory Task on it.

Official support for both ESX/ESXi 4.1 and 5 is coming in the upcoming release due end of year.

Hope this helps.

Kind Regards,

MonitorMan's picture

but i believe you should be able to get it to work by reclassifying the Resource Type correctly and then this should allow you to run the Inventory Task on it.

I'll bite. What do you mean reclassify the resource type? The vSphere 4.1 server is classified as a managed computer resource type. When going through the SMP server logs, I see the process connecting, but nothing is returned when the vSphere server is queried. However, if I scan individual ESX 4.1 servers, they are their guests do come back. Obviously I am attempting to follow best practice by scanning vSphere instead of the individual hosts. Joseph, does this make sense? My apologies if I murkied the waters.

Third Floor Garage Door Operator

Joseph_Carson's picture

It depends on what network discovery classified the device as, a network device, Computer or virtual computer.  From what you have said below it looks to have classified it correctly as a computer resource.

Network Discovery should run against either the vCenter or ESX/ESXi though today the Run Inventory portion run directly against the ESX/ESXi server.  This is changing in the upcoming release in which we always go through vCenter first and then fall back to the ESX/ESXi directly when vCenter is not available or the ESX/ESXi host is orphaned.

It might be worth raising a support Incident to check on what is going on.  On most cases so far it has been a problem with the correct credentials being configured in Credential Management.

Hope this info helps.

Nobby Clarke's picture

"Network Discovery should run against either the vCenter or ESX/ESXi though today the Run Inventory portion run directly against the ESX/ESXi server. This is changing in the upcoming release in which we always go through vCenter first and then fall back to the ESX/ESXi directly when vCenter is not available or the ESX/ESXi host is orphaned."

 

 

Will this be the same for 7.1 ?? Currently I have to run inventory against each of our ESX 4.0 and 4.1 hosts directly, rather than go through vCentre. It would be much preferable if VMM inventory just ran against the vCentre, not least because I don't want to have to create userids on each of our (hundreds) of ESX hosts.

If this will be changed in a new release, can you say when this release will be out ??

 

regards,

 

Nobby

MonitorMan's picture

Thanks for the help Joseph. I opened a case with support and will report back my findings. I'll have a good laugh if its creds.

Cheers

Third Floor Garage Door Operator

Joseph_Carson's picture

Hello Nobby,

Regarding your question.  This is changing in our upcoming release 7.1 SP2 tentatively due end of this year.  So everything will go via vCenter including Discovery and Inventory.  This makes the credential portion much easier as you mentioned.

Hope this helps.

Kind Regards,

Falquian's picture

I'll be waiting for this new release for checking this :)

It will help us dramatically.

 

Regards:

          Falquian

Kind regards:

     Falquian

If this post is useful to you, remember to mark it as a solution ;)

MonitorMan's picture

Hey - who hijacked my thread. cool

Just to relay what support said, the version of VMM bundled in 7.0 SP5 MR 4 is not supported with vSphere 4.1. It is a shame, as the webservices that perform the calls between 4.0 and 4.1 have not dramatically changed.

Joseph - thanks for the information even though we were unable to come to a positive resolution. It is appreciated.

Third Floor Garage Door Operator

SOLUTION