Comments on: dvSwitch scripting – Part 8 – Get and Set network adapters

By: Ed

Ed — Thu, 15 Oct 2015 18:24:23 +0000

Luc,

I was looking to use this to migrate several hundred VMs but the latest powercli includes several new fields. How would this be written for the current version of powercli? Or, how can I get powercli to build a NetworkAdapter from this?

By: JJ

JJ — Thu, 30 Apr 2015 14:06:45 +0000

Hello,
Is there anyway to call this using get-view instead of get-vm?
I’m trying to applied to all machines in the dvswitch but only to a determined hosts.
Regards,
JJ

By: shashi

shashi — Mon, 18 Nov 2013 10:30:19 +0000

Hello ,

First of all thanks for providing the script . Its very handy . But when I run the script it changes port group as expected but the NIC status would be disconnected . I.e . Connected and Connect at poweron checkbox are unchecked. Could you please help me to fix this .
thanks in advance !!!..

By: Batuhan

Batuhan — Thu, 22 Nov 2012 07:26:07 +0000

Hi, I know this is an old thread but this script has been great use to me. It works great, assigns the dvSwitch to the VM fine, but the script enters an infinite loop of errors after the configuration is done. The VM works fine, the network adapter is changed fine. The error is:

Exception calling “UpdateViewData” with “1” argument(s): “”
At line:83 char:25
+ $task.UpdateViewData <<<< ("Info")
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException

I am using this with PowerCLI 5 latest release. Maybe something deprecated as this is an old script. I tried to use the "Set-NetworkAdapter" command but it does not work with dvSwitch networks. Any help appreciated, thanks.

By: LucD

LucD — Wed, 09 Mar 2011 12:38:21 +0000

In reply to Ionut Nica. @Ionut, no not really, in PowerCLI 4.1 and 4.1.1 some existing cmdlets were extended with dvSwitch functionality. See the PowerCLI changelog. and search for 'distributed'.

By: Ionut Nica

Ionut Nica — Wed, 09 Mar 2011 12:02:38 +0000

Hi,

Did anything change with the introduction of powercli 4.1.1? do we still need these functions to get/set network information?
we have not upgraded to 4.1.1 yet so I was wondering about that.

Thanks
Ionut

By: Drunky

Drunky — Thu, 24 Feb 2011 12:46:32 +0000

@LucD
Great 🙂

at now i have to pars each vmx file of every vm (with help of awk/sed/grep ) on esx side, removing such lines as

ethernet0.dvs.switchId = “1d a1 2c 50 6d 7a ea 59-d0 cd b9 8a d2 a3 2d 37”
ethernet0.dvs.portId = “133”
ethernet0.dvs.portgroupId = “dvportgroup-367”
ethernet0.dvs.connectionId = “1842595141”

adding one line

ethernet0.networkName = “temp”

register those vm’s with your function “register-vm” and only after that changing portgroup from “temp” to what i need “dvportgroup”

and all of it is a part of “SRM on scripts” ^_^

By: LucD

LucD — Thu, 24 Feb 2011 11:47:10 +0000

In reply to Drunky. @Drunky, thanks for the feedback. I'll check if I can do something with the Register-VMX function for this.

By: Drunky

Drunky — Thu, 24 Feb 2011 10:55:48 +0000

@Drunky Never mind, i found the problem Unfortunately if you removing VM from inventory and than add it back (no matter form GUI or by your great function register-vm), it (VM) comes back with no (blank) portgroup, when using distributed switch

By: Drunky

Drunky — Thu, 24 Feb 2011 10:04:36 +0000

Hi Luc. Trying to use your function, but getting strange error

Get-VMHost | Get-Datastore -name “CX3_virtual_lab_lun2” | get-vm | Get-dvSwNetworkAdapter

Get-View : ?? ??????? ????????? ???????? ??? ????????? “VIObject”. ???????? ?????? ??? ???
?? ???????? NULL. ??????? ?? ?????? ????????, ?? ??????? ???????? NULL, ????? ???? ???????
?? ?????????? ???????.
C:\Scirpts5.ps1:158 ????:17
+ $VM | Get-View <<<< | %{
+ CategoryInfo : InvalidData: (:) [Get-View], ParameterBindingValidationExce
ption
+ FullyQualifiedErrorId : ParameterArgumentValidationError,VMware.VimAutomation.ViCor
e.Cmdlets.Commands.DotNetInterop.GetVIView