rtunisi Tracker

Re: Running a PowerCLI script against multiple vCenters at the same time

rtunisi — Tue, 15 Oct 2013 17:18:35 GMT

just to complete Luc post: when connecting to LinkedMode vCenters, use the '-AllLinked' parameter on Connect-VIServer

Re: Editor with Syntax Highlighting

rtunisi — Tue, 15 Oct 2013 17:11:26 GMT

you can use Powershell ISE and load powercli on the posh inside... just run the startup script on the screen or make an alias like

Function Load-PowerCli{

. "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1"

}

it loads all the current cmdlets into the autocomplete and syntax highlighter

Re: PowerCLI Help Needed With Retrieving ESXi Host Asset Tag Info

rtunisi — Mon, 14 Oct 2013 19:16:50 GMT

The issue i found is that 'OtherIdentifyingInfo' is a collection of objects (i suppose)... so you need to use -ExpandProperty on a select statement, like this:

$helper = $_.hardware.systeminfo | Select -ExpandProperty OtherIdentifyingInfo

$helper variable will get all the objects associated which OtherIdentifyingInfo, so you need a foreach to find the attribute needed. I think you should find what you need on 'IdentifierValue' and 'IdentifierType.Label' Attributes

see if this helps

Re: Disk Size Display Confusion

rtunisi — Tue, 01 Oct 2013 14:56:28 GMT

if you are using thin, there will be differences in provisionedSpace Size and usedSpace Size...on thick allocation, both will have the same values

When using snapsnots, the values will show the used size and plus the size of all disk deltas (as André said above)

about thin allocation:

not that this is a bad idea, the drawbacks on thin allocation lies at the more administrative overhead on your datastores. Some experts say thats a little bit of performance loss on thin allocation, which is a very discussable topic... you might want to find some articles about (try at Cormac Hogan blog. He's THE storage guy when the subject is virtualization).

and btw, dont think mr LucD Sleeps at all

Re: Weird issues on VM HardDisk information Script

rtunisi — Wed, 25 Sep 2013 19:05:54 GMT

simple code and trully brilliant... less than 1 second execution time

didnt know about the &{} construct... will look closely to this

Thanks really much for the PCLI lesson, Mr Dekens.. going back to study book

Re: Weird issues on VM HardDisk information Script

rtunisi — Wed, 25 Sep 2013 16:44:15 GMT

the issue does not occur when i substitute the command parameter, however, the execution time went thru the roof, as i expected.

Seconds : 24

Milliseconds : 93

(Measure-Command Statistic)

I believe thats because of the string parameter, that forces get-harddisk cmdlet to create a VirtualMachine object (i believe it calls Get-VM, which is very, VERY slow. Thats why i used the Get-View with -ViewType in the first place).

Luc, is there anyway i can make this quickier without the Get-VIObjectByVIView? I tested many options while creating this script and this proved to be the most efficient one, with runtimes around 1 to 2 seconds in the same environment (as i said, the script randomly fails with the disconnection issue, sometimes i can make it work and its pretty fast )

Re: Weird issues on VM HardDisk information Script

rtunisi — Wed, 25 Sep 2013 14:24:32 GMT

these are all vcenters, multiple versions (4.1, 5.0 and 5.1)

its really odd that i can use Get-VM on the same server that it claimed disconnection with no errors, something like this:

1) Connected to 3 vCenters: vc01, vc02 and vc03

2) Run script and i get the error 'vc01 is not connected'

3) Get-VM vm01 (which happens to be at 'vc01', that just disconnected) and it retrieves it normally

edit:

ran the command with the modifications to troubleshoot disconnection like you said, and no disconnections at all ! All the 15 vCenters still connected while running the command

The exception is below

Get-VIObjectByVIView : 25/09/2013 11:25:27 Get-VIObjectByVIView Server XXXXX is not connected.

Re: Is it possible to login to VM via powercli?

rtunisi — Wed, 25 Sep 2013 14:14:44 GMT

you can store your credentials in a variable and use invoke-vmscript command to run it into multiple VMs, like

(This will prompt the username/password dialog)

Invoke-VMScript -VM VM01 -ScriptText { commands } -GuestCredential (Get-Credential)

if you want to use it on multiple servers, create some txt file with all vm names and use something like this:

$cred = Get-Credential

gc text.txt | % { Invoke-VMScript -VM $_ -ScriptText { commands } -GuestCredential $cred }

EDIT: all machines must have VMWare tools installed for this to work

Weird issues on VM HardDisk information Script

rtunisi — Wed, 25 Sep 2013 14:02:37 GMT

hello everyone

i am designing some simple script to retrieve VM Hard Disk information with PowerCli and i got some pretty weird issue: i ocasionally get runtime execution errors with vc server disconnection, but after the error, i can retrieve info on the same vcenter with simple commands (like Get-VM for instance). The vc farms still available over viclient and powercli all the time, so it must be something on the code

the steps i use to reproduce the strange behavior:

(Using Powercli 5.5 and Powershell 3.0. Error still happens with Powercli 5.1)

- Connect to vcenter (multiple servers)

- run the command and it eventually gets stuck in line 12 ($ghd = Get-HardDisk (Get-VIObjectByVIView $VMView)) with the error 'Server XXXX is disconnected'

- Run some other command (like get-vm) to certify that server is still connected

sample script is below

Function Get-VMDiskInfo {
  [CmdletBinding()]
  Param (
  [Parameter(Mandatory=$true,
  ValueFromPipeline=$True,
  ValueFromPipelineByPropertyName=$true)]
  [Alias('Name')]
  $VM
  )
  PROCESS{
  $VMView = Get-View -ViewType VirtualMachine -Filter @{"Name" = $VM}
  $ghd = Get-HardDisk (Get-VIObjectByVIView $VMView)
    $output = @()
  ForEach ($VirtualSCSIController in ($VMView.Config.Hardware.Device | Where {$_.DeviceInfo.Label -match “SCSI Controller”})){
  ForEach ($VirtualDiskDevice in ($VMView.Config.Hardware.Device | Where {$_.ControllerKey -eq $VirtualSCSIController.Key})){
  $VMSummary = “” | Select  VM,Disk, SCSI, DiskType, DiskFormat, DiskSizeGB, DiskFile
  $VMSummary.VM = $VM
  $VMSummary.SCSI = [string]::Concat($VirtualSCSIController.BusNumber,":",$VirtualDiskDevice.UnitNumber)
  $VMSummary.Disk = $VirtualDiskDevice.DeviceInfo.Label

  #pegando info do Get-Harddisks
  $d = $ghd | ? {$_.Name -match $VirtualDiskDevice.DeviceInfo.Label}
  $VMSummary.DiskType = $d.DiskType
  $VMSummary.DiskSizeGB = [Math]::Round($d.capacityGB,2)
  $VMSummary.DiskFile = $d.filename

  if($d.Disktype -eq "Flat"){
  $VMSummary.DiskFormat = $d.StorageFormat
  }
     
  $output += $VMSummary
            }
  }
            Write-Output $output
  }
}

does anyone have any idea whats going on ?

almost forgot, sorry about the messy code and the poor english...

thanks in advance

NIC Teaming / Failover with Active/Passive Switching

rtunisi — Thu, 01 Mar 2012 15:43:46 GMT

Hello!

I have a question regarding nic teamming setup with active / passive cisco switching.

We have the current setup today: each esx4.1 host have two pnics connected to our cisco catalyst 4506 core as a teamming. Both pnics are configured with 802.1q trunking to enable multiple vlan ids. No issues so far as this setup is pretty simple.

Recently we are implementing a new switch core to function as a failover switch in active/passive layout. I tried to put another 2 pnics on each host (trunking enabled) on the secondary switch as standby cards, so our pretend-to-be setup is much like this:

PortGroups - vSwitches - 2 PNICS on SwitchCoreA (active teamming) - 2 PNICS on SwitchCoreB(Standby teamming)

However this setup brought me an issue. I won switch failover because when switch A goes down, both standby cards gets up on core B and network stands up OK, but i lost NIC failover, since when one active card goes down, ESX tries to put one standby card UP and messes up my entire teamming (nics at CORE B arent disable, the switch stays there at some sort of "passive mode")

i need to know if theres any setup which can make me achieve both NIC and Switch Failover at this setup

any help would be apreciated

Thanks

Rtunisi