Re: Trying to write a script which would change MA...

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

Carmageddon · ‎07-25-2010

William please note I did try running your script but got the error: Can't locate object method "network" via package "VirtualEthernetCardDistributedVirtualPortBackingInfo" at /usr/lib/vmware-vcli/apps/vm/vmNICManagement.pl line 123.

Which makes sense because there is no such attribute in the VirtualEthernetCard data type - I explained it all in the original post, perhaps it is a bit too lengthy though.

I am also looking for an explanation why mine doesn't work, and how yours is supposed to work - I wrote everything as per the documentation, I think, so what did I do wrong?

William is there any way to contact you? I cant seem to find email or anything beside tweeter but that's not a two way communication tool

lamw · ‎07-26-2010

First off, I don't do any personal email or PM support, post any questions or comments you have on the VMTN forums, that's what it is for.

Second, you're lacking quite a bit in your script to properly update a device. Take a look at the script I reference on a vNIC with standard portgroup and understand how to obtain the correct device and proper config spec to update the MAC. One you understand how that works, then you should be able to apply that to update a vNIC that is connected to a distributed portgroup.

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

Carmageddon · ‎07-26-2010

William, my issue with analyzing how your script works, it two-folded:

1) Due to the error I get on line 123, I cant reach the actual creation and watch it via debugger like I want

2) I found no documentation for a lot of things you use in your script, such as mo_ref => $vnic_device->backing->network

There is no documentation on mo_ref for vSphere 4 anywhere, also the whole section of: if($nictype eq 'VirtualE1000') {.....}

Uses things I am not sure where are they documented. If you look at page 29 of the SDK for Perl Programming Guide documentation, it's instructions on how to modify a property, are very different from how you do it. - thats why I am having troubles understanding that.

I will also point out, that your other script (which finds a machine name by its MAC), actually works exactly as per the documentation, eg it goes to $vm->config->hardware->device->VirtualEthernetCard and then accesses the macAddress property - simple, identical to what the API says about that object.

Now from here when I get back to 1 and 2, I cant understand why suddenly everything changes, the moment I want to modify the value of the field?

lamw · ‎07-26-2010

When you refer to documentation, the vSphere SDK for Perl programming guide only deal with the syntax using the Perl SDK. The actual vSphere API documentation in terms of the object names and properties, is what you'll need to use - http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/index.html

If you're new to vSphere API/SDK, I would recommend first off checking out -

If I understand you correctly, you're trying to update a MAC Address on a VMs vNIC? The script that I have provided does exactly that but only supports a VM that is connected to a standard portgroup and not a distributed portgroup. To better understand the script and the logic, I would recommend you start off with a simple example of updating a MAC Address on a VM with regular portgroup, if you feel that you fully understand that, then you should tackle the distributed portgroup task which is what you're trying to do.

Hopefully this makes more sense

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

Carmageddon · ‎07-26-2010

Thank you.

I've followed your links and started digging deeper, although a lot of the PDF documents seem very outdated using very old (2006-2007) versions of the Perl API.

About the ReferenceGuide - is there any way to present it in a UML like way, or some way I could comfortably print it out? I find it hard to link all the bits and pieces in my head, and it helps seeing who inherits what etc, when its printed and easy to follow from one page to the next. Or better yet, a nice printout of the entire VM object, the way debugger shows - I think this would help.

I have another idea for approaching this problem: Will creating a VM with custom MAC pre-defined, be easier than modifying? (I will need to do it anyway on the next step of the project..)

Yes you understood correctly I think - I will put it in my words: I need to change the VM's ethernet adapter's MAC, because this is how DHCP server handles out IPs etc. (Or alternatively and even better, create the VM with the right MAC from the start).

I am not sure what is standard portgroup, and distributed portgroup - is this part of the API? if not where do I check, which kind of ethernet adapter our VMs use?

I will try your suggestion and create a VM with standard default NIC tomorrow at work, and see if the change MAc works then, and take it from there.

Although I am beginning to think creating VM with the right mac from the start, should be easier?

If I specify it in the config XML file I pass to create_VM method, how would I define this? can I simply take the elements names from a sample VMX file, add it to the XML file and it will understand what to do with the special elements? beside the trivial ones such as Disksize etc?

lamw · ‎07-26-2010

Before getting in too deep, I would recommend you spend some time looking at this documentation first -

You'll want to get a good understanding of the vSphere API object model before attempting to writing your own scripts, else it can potentially be confusing.

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

Carmageddon · ‎07-27-2010

Ok.. after thinking, perhaps it would be much easier to customize the MAC address, when I create the machine instead?

using vmware-vsphere-cli-distrib/apps/vm/vmclone.pl , I can ask it to clone the machine while customizing the VM using an XMLll file.

They give some examples in the documentation for things such as:

However, I cant find the corresponding settings in the VMX file.

What I want to do, is esentially clone from template (which works) BUT, I want to do it with customizing the VM using the XML file, which would contain configspecs equal to these from the VMX file:

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.dvs.switchId = "long HEX address"

ethernet0.dvs.portId = "510"

ethernet0.dvs.portgroupId = "dvportgroup-712"

ethernet0.dvs.connectionId = "1946534217"

ethernet0.addressType = "static"

ethernet0.address = "00:50:56:30:00:13"

Now, how do I find the equivalents of these for XML file? From all my searches and readings, the documentation is spread all over and in my cases not complete, I would love if you could point me to specifics - maybe I missed something?

Anyhow, of the above VMX settings, I think I only need to do ethernet0.present, ethernet0.virtualDev, ethernet0.dvs.switchId = "some HEX address", ethernet0.addressType and ethernet0.address, and everything else would be adjusted by VMware (as the port is unique per each VM).

Am I right? if not, how would you suggest I do it? and by the way, you were right William, we do indeed use Distributed Ports, but since I cant find such setting in the VMX file, I must assume it comes from the switch?

I not, how would you suggest I clone the template, using a custom MAC? (I can specify the template - it could be without a NIC, or with it, but seems much more difficult to change it).

Carmageddon · ‎07-28-2010

William I got it working, took a while but I changed your script a bit. I dont know why did you do stuff such as:

my $network = Vim::get_view(mo_ref => $vnic_device->backing->network, properties => );

Its not needed I disabled ALL of that stuff, and changed all 4 devices in the following fashion (your old setting commented out):

if($nictype eq 'VirtualE1000') {

#$newNetworkDevice = VirtualE1000->new(key => $vnic_device->key, unitNumber => $vnic_device->unitNumber, controllerKey => $vnic_device->controllerKey, backing => $backing_info, addressType => 'Manual', macAddress => $mac);

$newNetworkDevice = VirtualE1000->new(key => $vnic_device->key, unitNumber => $vnic_device->unitNumber, controllerKey => $vnic_device->controllerKey, backing => $vnic_device->backing, addressType => 'Manual', macAddress => $mac, deviceInfo => $vnic_device->deviceInfo, wakeOnLanEnabled => $vnic_device->wakeOnLanEnabled, connectable => $vnic_device->connectable);

As you can see, your old objects contained too few sub-objects, and I have no idea why did you read them to separate variables earlier, just to give them again here - doing backing => $vnic_device->backing is UNIVERSAL, and should work for any nic - why did you go to backing->network? you didn't need anything there in order to complete the script's task.

In any case, thanks again! although not a direct help, you did send me time and time again to look at your script

Hope you update your published one to be universal.

lamw · ‎07-28-2010

Glad you got it working, but I seriously no clue what you're trying to say.

Hope you update your published one to be universal.I'm not sure I follow this as well, what do you mean "universal". It supports all 4 types of vNIC (e1000,pcnet32,vmxnet2 and vmxnet3)

In any case, the script is provide as an example and has been tested against all 4 types of vNIC. I encourage users to modify and tweak these scripts to fit their operating environment. Regarding the limited sub-properties, if you look at the API docs, not all of them are required ... this really depends on what you need configured and again, it may vary based on your requirements.

Thanks

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators