Re: VMWare ESXi 4.0 registration issues (was Re: Errors creating reservation with new bulk-added computers)

2010-02-24 Thread Aaron Peeler
Right, we're working on adding support for vmware 2.0 and have not fully 
tested ESXi 4


On the SOAP fault output, I suspect the problem is related to a license 
issue using the free license. Can you put the license into the demo mode 
and retest the vmregister.pl cmd? To see if there are any differences.


Aaron



On 2/24/10 12:17 AM, Jeffrey Wisman wrote:

Actually, just realized that VCL is using version 1.6 of the VI Toolkit:

[r...@vclmgmt vm]# /usr/lib/vmware-viperl/apps/vm/vmregister.pl --server
'vclvm1' --username root --password '***' --version
VI Perl Toolkit version: 1.6
Script 'vmregister.pl' version: 1.0

Should I update to the vSphere SDK for Perl 4.0?  Is this even this same
thing?  Will it break other things if I do?

I'm in uncharted territory here, and appreciate the help.  Thanks for
reading all these messages and assisting.

Jeff



On Tue, Feb 23, 2010 at 9:10 PM, Jeffrey Wisman
wrote:

   

After digging into this more, I've narrowed down the issues to the
vmregister.pl, part of the Vsphere perl toolkit.  I get the same error
when running the command manually.  We're running VMWare ESXi 4.0.0 and VCL
2.0.  Are there any known issues or incompatibilities between ESXi 4.0.0 and
VCL 2.0?  Anyone have any insight into this registration issue?  Please see
below for the command run manually, and also the version command.

 
 

[r...@vclmgmt vm]# /usr/lib/vmware-viperl/apps/vm/vmregister.pl --server
'vclvm1' --username root --password '***' --vmxpath
'[VCL]/inuse/csuvm10/vmwarewinxp-base7-v0.vmx' --operation register --vmname
csuvm10 --pool Resources --hostname 'vclvm1.csueastbay.edu' --datacenter
'ha-datacenter'

SOAP Fault:
---
Fault string: fault.RestrictedVersion.summary
Fault detail: RestrictedVersionFault
 
 
 
 

[r...@vclmgmt vm]# /usr/lib/vmware-viperl/apps/general/viversion.pl--server 
'vclvm1' --username root --password '**'

This is  HostAgent 4.0

This is VMware ESXi 4.0.0 build-208167 running on x86 ESX Server
microkernel
The product Line ID is a unique identifier for a product line. product line
id is embeddedEsx
Short form of the product name is VMware ESXi having version 4.0.0

System is running on x86 ESX Server microkernel
 
 


Thanks,
Jeff



On Sun, Feb 21, 2010 at 9:50 PM, Jeffrey Wisman<
jeff.wis...@csueastbay.edu>  wrote:



--

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
aaron_pee...@ncsu.edu
919-513-4571



Re: VMWare ESXi 4.0 registration issues (was Re: Errors creating reservation with new bulk-added computers)

2010-02-23 Thread Jeffrey Wisman
Actually, just realized that VCL is using version 1.6 of the VI Toolkit:

[r...@vclmgmt vm]# /usr/lib/vmware-viperl/apps/vm/vmregister.pl --server
'vclvm1' --username root --password '***' --version
VI Perl Toolkit version: 1.6
Script 'vmregister.pl' version: 1.0

Should I update to the vSphere SDK for Perl 4.0?  Is this even this same
thing?  Will it break other things if I do?

I'm in uncharted territory here, and appreciate the help.  Thanks for
reading all these messages and assisting.

Jeff



On Tue, Feb 23, 2010 at 9:10 PM, Jeffrey Wisman
wrote:

> After digging into this more, I've narrowed down the issues to the
> vmregister.pl, part of the Vsphere perl toolkit.  I get the same error
> when running the command manually.  We're running VMWare ESXi 4.0.0 and VCL
> 2.0.  Are there any known issues or incompatibilities between ESXi 4.0.0 and
> VCL 2.0?  Anyone have any insight into this registration issue?  Please see
> below for the command run manually, and also the version command.
>
> >>
> [r...@vclmgmt vm]# /usr/lib/vmware-viperl/apps/vm/vmregister.pl --server
> 'vclvm1' --username root --password '***' --vmxpath
> '[VCL]/inuse/csuvm10/vmwarewinxp-base7-v0.vmx' --operation register --vmname
> csuvm10 --pool Resources --hostname 'vclvm1.csueastbay.edu' --datacenter
> 'ha-datacenter'
>
> SOAP Fault:
> ---
> Fault string: fault.RestrictedVersion.summary
> Fault detail: RestrictedVersionFault
> >>
>
> >>
> [r...@vclmgmt vm]# /usr/lib/vmware-viperl/apps/general/viversion.pl--server 
> 'vclvm1' --username root --password '**'
>
> This is  HostAgent 4.0
>
> This is VMware ESXi 4.0.0 build-208167 running on x86 ESX Server
> microkernel
> The product Line ID is a unique identifier for a product line. product line
> id is embeddedEsx
> Short form of the product name is VMware ESXi having version 4.0.0
>
> System is running on x86 ESX Server microkernel
> >>
>
>
> Thanks,
> Jeff
>
>
>
> On Sun, Feb 21, 2010 at 9:50 PM, Jeffrey Wisman <
> jeff.wis...@csueastbay.edu> wrote:
>
>> I was troubleshooting this error before as an issue with creating more
>> than one reservation at a time.  As it turns out, its really just an issue
>> with the new computers I added using the "add multiple" function.  In the
>> last thread, it was suggested that I configure dhcpd.conf and the database
>> with the appropriate MAC addresses, which I did.  Unfortunately, I'm still
>> not getting any further.
>>
>> I disabled the first computer (the one that works) and then tried to
>> create a reservation, and ended up with the following logs.  There are so
>> many warnings that I'm not sure what ones to care about.  Even when it works
>> with the original VM, I get a ton of warnings.
>>
>> It seems like the issue is the "SOAP fault" that gets returned when trying
>> to register the virtual machine.  Please note that we're running ESX 4.0.0.
>>
>> Can somebody take a look and let me know if its obvious what's wrong?  I'm
>> not really sure where to go from here.
>>
>> Thanks,
>> Jeff
>>
>>
>>
>>
>>
>> 2010-02-21 21:32:37|7225|vcld:main(165)|lastcheckin time updated for
>> management node 1: 2010-02-21 21:32:37
>> 2010-02-21 
>> 21:32:37|7225|13:13|new|utils.pm:reservation_being_processed(9616)|computerloadlog
>> 'begin' entry does NOT exist for reservation 13
>> 2010-02-21 
>> 21:32:37|7225|13:13|new|utils.pm:reservation_being_processed(9668)|reservation
>> is NOT currently being processed
>> 2010-02-21 21:32:37|7225|13:13|new|vcld:main(276)|reservation 13 is NOT
>> already being processed
>>
>> |7225|13:13|new|  WARNING 
>> |7225|13:13|new| 2010-02-21 
>> 21:32:37|7225|13:13|new|utils.pm:get_request_info(5209)|preferredimageid
>> is not set for computer id=19
>> |7225|13:13|new| ( 0) utils.pm, notify (line: 728)
>> |7225|13:13|new| (-1) utils.pm, get_request_info (line: 5209)
>> |7225|13:13|new| (-2) vcld, main (line: 280)
>>
>> 2010-02-21 21:32:37|7225|13:13|new|utils.pm:get_request_info(5349)|non-NCSU
>> user affiliation found: Local
>> 2010-02-21 
>> 21:32:37|7225|13:13|new|utils.pm:get_management_node_info(6797)|management
>> node info retrieved from database for vclmgmt
>> 2010-02-21 21:32:37|7225|13:13|new|vcld:main(281)|retrieved request
>> information from database
>> 2010-02-21
>> 21:32:37|7225|13:13|new|DataStructure.pm:is_parent_reservation(854)|returning
>> true: parent reservation ID for this request: 13
>> 2010-02-21 
>> 21:32:37|7225|13:13|new|utils.pm:update_request_state(2177)|request
>> 13 state updated to: pending, laststate to: new
>> 2010-02-21 21:32:37|7225|13:13|new|utils.pm:insertloadlog(4701)|inserted
>> computer=19, begin, beginning to process, state is new
>> 2010-02-21 21:32:37|7225|13:13|new|vcld:make_new_child(509)|loaded
>> VCL::new module
>> 2010-02-21 21:32:37|7958|13:13|new|vcld:make_new_child(582)|vcld
>> environment variable set to 0 for this process
>> 2010-02-21 21:32:37|7225|13:13|new|vcld:make_new_child(566)|curre