xcom3
Contributor
Contributor

Error when adding a 2.5.3 host into VC 2.5

Hi, I'm in the process of migrating 2 old ESX 2.5.3 servers into a Virtual Center 2.5 U4.

The new VC is already managing a single ESX 3.5 host I've installed the licensing server on the same server as VC.

The 2 old servers was managed trough and old VC 1.4.1. I removed one of the ESX 2.5 host and then I tried to add them into the new VC. Then I got an error after about 80-90% complete : "Error: There is not enough licenses installed to perform this operation".

I do have spare licenses available on the new VC for ESX hosts, so why is this happing?

Tags (3)
0 Kudos
3 Replies
VladN
Hot Shot
Hot Shot

How are old ESX servers licensed now? Can you point them to the new VC's license server?

What does License Servers say when you do "Perform Status Inquiry" in License Server Tools? Does it see that you have unused licenses?

0 Kudos
xcom3
Contributor
Contributor

This is the output:

-


Status

-


Flexible License Manager status on Thu 7/23/2009 23:22

http://Detecting lmgrd processes...

License server status: 27000@MGMM-DATACENT01

License file(s) on MGMM-DATACENT01: D:\Program Files\VMware\VMware License Server\Licenses\VMwareSoftware.lic:

MGMM-DATACENT01: license server UP (MASTER) v10.8

Vendor daemon status (on MGMM-DATACENT01):

VMWARELM: UP v10.8

Feature usage info:

Users of PROD_VC_EXPRESS: (Total of 1 license issued; Total of 1 license in use)

"PROD_VC_EXPRESS" v2005.05, vendor: VMWARELM

floating license

SYSTEM MGMM-DATACENT01 MGMM-DATACENT01 (v2005.05) (MGMM-DATACENT01/27000 302), start Wed 7/15 14:22

Users of PROD_ESX_FULL: (Total of 4 licenses issued; Total of 2 licenses in use)

"PROD_ESX_FULL" v2005.05, vendor: VMWARELM

floating license

root esx01.host.net /dev/tty (v2005.05) (MGMM-DATACENT01/27000 401), start Tue 7/14 10:05, 2 licenses

Users of ESX_FULL_BACKUP: (Total of 4 licenses issued; Total of 2 licenses in use)

"ESX_FULL_BACKUP" v2005.05, vendor: VMWARELM

floating license

root esx01.host.net /dev/tty (v2005.05) (MGMM-DATACENT01/27000 501), start Tue 7/14 10:05, 2 licenses

Users of VC_ESXHOST: (Total of 4 licenses issued; Total of 2 licenses in use)

"VC_ESXHOST" v2005.05, vendor: VMWARELM

floating license

SYSTEM MGMM-DATACENT01 MGMM-DATACENT01 (v2005.05) (MGMM-DATACENT01/27000 202), start Wed 7/15 14:22, 2 licenses

Users of VC_VMOTION: (Total of 4 licenses issued; Total of 2 licenses in use)

"VC_VMOTION" v2005.05, vendor: VMWARELM

floating license

SYSTEM MGMM-DATACENT01 MGMM-DATACENT01 (v2005.05) (MGMM-DATACENT01/27000 102), start Wed 7/15 14:22, 2 licenses

Users of VC_DAS: (Total of 4 licenses issued; Total of 0 licenses in use)

Users of VC_DRS: (Total of 4 licenses issued; Total of 0 licenses in use)

Eh... I just read that for ESX 2.x host, VMWare counts every core as needing a license, instead of just counting the CPU socket itself, as opposed to ESX 3.x. Does this mean that I have to get 2 new CPU licenses just so that I can do the migration?

Thanks for all help.

0 Kudos
VladN
Hot Shot
Hot Shot

Sorry, I totally missed 2.5.3 part...

You'll have to use host licensing for ESX 2.5.3 with VC 2.5. Or if you want centralized licensing for two old servers, you have to stay with VC 1.x.

0 Kudos