VMM with ESX 3

[AndySmith2]

Hi Dave,

We're working on the discovery issues. It doesn't seem to be consistent, so we're trying to get to the root cause. As for the licensing, could you provide a little more details on what is happening? Lastly, the disk alerting is being evaluated as a feature for the next release. It's high on my list, as you are not the only one asking for it.

Thanks,
Andy

[dave rowland_2]

Hi Andy,

Thanks for the prompt reply, i have the license key info off post.

The VM's are being discoved now (not sure if there all there yet), guess there is some daily task involved?

When will the disk threshold upgrade be released or shouldnt i ask...

Thanks

Dave

[Paul M. Ford]

I too am having a licensing issue. The server is running in our DMZ but most of the communications are permitted from our inside network.

-- Server is running ESX 3.0.1
-- mxagentconfig was run successfully
-- VMM agent 2.1 was installed
-- When deploying the license, it says that it successfully deployed.

However, when looking at the Manage Keys list, the single seat license now shows up as Version 1 and Seats Used remains at 0. Reran Deploy Keys and it says "Key already present at this system". Repeated this with a second key and it is also stuck in this state.

Tried the old trick of running Software Status Polling to pull back lost licenses and that did not work.

Any thoughts? Please?

[Ranganath]

We have tested the licensing and verified that it works. Here is the detailed steps to license VMM..

Steps To License any Host (ESX 3.0.1, ESX 2.5.4, MSVS R2, GSX 3.2, and VMware Server) in VMM 2.1



1. Discover any Host in All Systems Page of HPSIM.

2. Run mxagentconfig for the above discovered Host.

3. Deploy VMM Agents on the Host.(For ESX 3.0.1 & ESX 2.5.4 deploy Linux Agents and for MSVS R2, GSX 3.2, and VMware Server deploy windows VMM Agent.)

4. Verify whether the VMM Agents is registered successfully in Task Result Page.(If not check whether the old VMM Agents are running on that Host and remove them)

5. Verify after VMM Agents is registered successfully , the VM column in All Systems page is Informational.

6. Now assign the License to the registered Host and Identify that Host.

7. Verify the VM column in All Systems page should come to normal icon.

8. In Manage License keys page, the Licenses used column should be 1



Steps to get the VM host discovered with serial number



1. Click on HS column in All systems page, this will open up SMH page

2. Click on Settings->SNMP configurations UI Options, the SNMP settings page will be opened

3. Please delete the IP address i.e 127.0.0.1 and "localhost" strings from the first two lines

rwcommunity public 127.0.0.1 (delete 127.0.0.1)

rocommunity public localhost (delete localhost)

4. Restart snmp agent service i.e Click on change and Reset button

5. Identify the VM host

6. Now browse to VM host from all systems page to see the serial number of the VM host

If you still see issues with licensing please send the following log files to me (ranganath.gk@hp.com)


1. Please enable the debug mode in CMS.(Refer userguide to enable debug mode)

2. C:/Program Files/HP/HP System Insight Manager/log//mxdomainmgr.0.log

Thanks
Ranga