BastiaanvanH's Posts

You have exedentely removed the vmstore powershell drive. I had done the same. Reinstall PowerCLI to solve this. PS C:\> get-psprovider vim* Name                 Capabilities              D... See more...
You have exedentely removed the vmstore powershell drive. I had done the same. Reinstall PowerCLI to solve this. PS C:\> get-psprovider vim* Name                 Capabilities              Drives ----                 ------------              ------ VimDatastore         ShouldProcess             {vmstores, vmstore} VimInventory         Filter                    {vis, vi}
Not true. It's not there by default, you can create it by going to the PVDC and add a new Storage Policy. There's defenetely a bug with New-orgVdc. You should be able to target a Storage Polic... See more...
Not true. It's not there by default, you can create it by going to the PVDC and add a new Storage Policy. There's defenetely a bug with New-orgVdc. You should be able to target a Storage Policy.
Hi, According to the documentation of VCD you need to restart all vApps when you make changes to the VDC resource allocations (CPU and Memory): These settings affect only vApps that you start... See more...
Hi, According to the documentation of VCD you need to restart all vApps when you make changes to the VDC resource allocations (CPU and Memory): These settings affect only vApps that you start from this point on. vApps that are already running are not affected. The usage information that vCloud Director reports for this organization VDC does not reflect the new settings until all running vApps are stopped and started again. We noticed when increasing the Memory or CPU we see an vCenter change to the VDC's resource pool settings. They are instant set. When looking at the Resource Pool information of VCD within the VDC previous values are shown, not the increased one's. Is have some questions regarding this and hope someone can help me understand this process better. Are the VM's able to use the increased resources without restarting the vApps? So is it only an cosmetic GUI thing? If we only restart the vApp which needs the extra resources, would that work? What actually happens when restarting a vApp, does it have resource allocations or some kind? Thank you in advance, much appreciated. Bastiaan
I got it already. NSX Edge GW is policy baes IPSEC VPN. So when adding the remote network 0.0.0.0/0 it automaticly created a routing entry for it. Thanks for the help.
Hello, yes, all points are correct. What steps do I need to go thru? Thanks.
Hello, I'm unable to find information regarding the IPSEC functionality of vCloud/NSX. We would like to pass all traffic (default gateway) thru an IPSEC tunnel, is this possible with vCloud 8.... See more...
Hello, I'm unable to find information regarding the IPSEC functionality of vCloud/NSX. We would like to pass all traffic (default gateway) thru an IPSEC tunnel, is this possible with vCloud 8.10 and NSX 6.2.7 ? Can this be done thru vCloud GUI or does it need configuration thru NSX edge GW config? Kind regards, Bastiaan
Hi, I'm unable to find any VSA related PowerCLI commands. Am I correct? I want to check the VSA status just like you can do with the "WSCLI.jar". I can write a wrapper, but native PowerCLI ... See more...
Hi, I'm unable to find any VSA related PowerCLI commands. Am I correct? I want to check the VSA status just like you can do with the "WSCLI.jar". I can write a wrapper, but native PowerCLI is preferable. Kind Regards, Bastiaan
I'm trying to accomplisch the same, any luck finding the IP allocations in PowerCLI?
Hello, In our vCloud setup, we are using Veeam's capability to restore files thru VIX. We notice a very slow restore transfer speed of about 500KB/s. I wanted to eliminate Veeams retore mechan... See more...
Hello, In our vCloud setup, we are using Veeam's capability to restore files thru VIX. We notice a very slow restore transfer speed of about 500KB/s. I wanted to eliminate Veeams retore mechanism in this, so I tested with PowerCLI to copy a file from a VM to the vCenter server with Copy-VMGuestFile, this want at max 1500KB/s. I can not find any reference in what transfer speed to expect from VixVM_CopyFileFromHostToGuest / Copy-VMGuestFile. So I do not know if this speed is as expected, or a problem. It would help If I had some reference material, I was hoping the community could help me out So what is your transfer speed against wirespeed when copying a file from or to a VM. The cmdlet does not give you transfer speed, you can check with Windows Resource Monitor, and then Disk and find the file you are copying (see screenshot). Copy-VMGuestFile - vSphere PowerCLI Cmdlets Reference Example: Copy-VMGuestFile -Source c:\temp\test.zip -Destination c:\temp -GuestToLocal -VM "SourceVMName" -GuestUser "domain\administrator" -GuestPassword xxxxxxxxxxx Thank you in advance! Regards, Bastiaan
If you initiate a manual vMotion, is it going well? Are your hosts seeing both datastores? If not host to host migration is used. This is not vCloud thing but just vSphere.
Hi, We are trying to get UDT transfer to work on our vCloud Connector setup. Both node's are behind NAT, and the vCloud public receiving node has UDP 8190 port forwarded. I would like to know ... See more...
Hi, We are trying to get UDT transfer to work on our vCloud Connector setup. Both node's are behind NAT, and the vCloud public receiving node has UDP 8190 port forwarded. I would like to know if this is supported, as there's a note on the documentation regarding UDT and both nodes cannot reside behind a firewall. VMware vCloud Connector 2.7 Documentation Center Kind Regards, Bastiaan
Hi, We would like to disable vsentracing on all hosts. If we disable vsantraces on a host and create a hostprofile from it, will it "capture" the setting? Would adding a profile in the "Ser... See more...
Hi, We would like to disable vsentracing on all hosts. If we disable vsantraces on a host and create a hostprofile from it, will it "capture" the setting? Would adding a profile in the "Service Configuration" object in the hostprofile with "vsantraced" set to off work? And other method? Kind Regards, Bastiaan
Hi, With PowerCLI 5.8 Release 1 this property field .ExtensionData.Summery.RunTime.BootTime is still empty with some VM's. So this bug hasn't been solved yet? Kind regards, Bastiaan van Ha... See more...
Hi, With PowerCLI 5.8 Release 1 this property field .ExtensionData.Summery.RunTime.BootTime is still empty with some VM's. So this bug hasn't been solved yet? Kind regards, Bastiaan van Haastrecht
Hi, We use ESXi auto deployment to deploy images to our clusters. We noticed as long as we keep the PowerlCLI command window open, the ImageProfile object is there to be used. A Get-EsximagePr... See more...
Hi, We use ESXi auto deployment to deploy images to our clusters. We noticed as long as we keep the PowerlCLI command window open, the ImageProfile object is there to be used. A Get-EsximageProfile lists all new created profiles. As soon as we close the PowerCLI command window and reopen it, all ImageProfiles are gone. A Get-EsximageProfile displays nothing. All is gone except the deployment rule. Deployment however keeps working. It's weird we need to recreate the EsxiImageProfile over and over again when we need to make adjustments to the image. Is this normal behavior, or a bug? Using ESXi and vCenter 5.5 u2, and PowerCLI 5.5 Release 1. Kind Regards, Bastiaan van Haastrecht
Anyone a solution/approuch for solving this?
Hi, We've got two resourcepools defined in our PVDC. We've decided to stop using elastic vDC's option. The VM's of all vDC;s are moved to one resource pool, so no vDC is spanned across the two... See more...
Hi, We've got two resourcepools defined in our PVDC. We've decided to stop using elastic vDC's option. The VM's of all vDC;s are moved to one resource pool, so no vDC is spanned across the two resource pools. The we switched of the Elastic option. Now, if you look at vCenter every vDC still has an vDC resource pool. They do not have any VM, but they arent removed by vCloud Director. Also, looking at the web administrative console, the vDC's have the number two in the resource pool collum. How can we remove/update the vDC's to remove their unused/spanned/elastic resource pool? Regards, Bastiaan
Hi, thank you for your reply's. We've been very busy with analysing this problem. We have narrowed it down to fast provisioned thin VM's. Just thin or thick a commit is 30 seconds. A VM fast prov... See more...
Hi, thank you for your reply's. We've been very busy with analysing this problem. We have narrowed it down to fast provisioned thin VM's. Just thin or thick a commit is 30 seconds. A VM fast provisioned VM takes something between 10 to 30 minutes.
Hi, we have a DC with 4x ESXi 5.1U1 with vCenter 5.1U1 and vCloud Director 5.1.2 . We use Veeam v7.0 to backup all VM's, and one of the VM's takes a very long time in deleting the snapshot. 12 mi... See more...
Hi, we have a DC with 4x ESXi 5.1U1 with vCenter 5.1U1 and vCloud Director 5.1.2 . We use Veeam v7.0 to backup all VM's, and one of the VM's takes a very long time in deleting the snapshot. 12 minutes with only 25MB to commit. The VM itself doenst have any pre-snapshots, and doesnt have any performance issue's. The VM is a Windows Server 2012 Domain Controller. No Windows Event logs around this issue. All VM's reside on the same clustered HP Lefthand storage. Removing small snapshots of other VM's on same ESXi, same VMFS takes few seconds. Any idea's what could be the issue here?
I have the same issue on a BL460 G6. Any update on this issue ?
Thank you for your reply. I've managed to fix the issue with the help of support. They pointed me to look into the BIOS of the HBA card. There i found the bogus target in the iSCSI target list... See more...
Thank you for your reply. I've managed to fix the issue with the help of support. They pointed me to look into the BIOS of the HBA card. There i found the bogus target in the iSCSI target list. When configuring targets in ESX they get pushed via the Emulex driver into the HBA card, so you can use them to boot of. Somehow something got wrong when the driver pushed a bogus entry into the HBA card. And ESX was not able to remove it again because the entry was not compliant with a iSCSI iqdn. So solution: boot into the HBA card bios via CTRL-S and remove the iSCSI target there.