cliffcahill's Posts

DNS is a hard requirement for VCSA NTP can be synced to esxi host to avoid setting up an NTP Server. vCenter Server Appliance 6.0 fails to deploy with the error: Firstboot script execution ... See more...
DNS is a hard requirement for VCSA NTP can be synced to esxi host to avoid setting up an NTP Server. vCenter Server Appliance 6.0 fails to deploy with the error: Firstboot script execution Error. The supplied System Name …
VCSA 6.5 installer no longer requires the Client Integration Plugin (CIP). Browser features such as OVA/OVF import that were dependent on CIP are now native to the VCSA 6.5 installer. Other CIP p... See more...
VCSA 6.5 installer no longer requires the Client Integration Plugin (CIP). Browser features such as OVA/OVF import that were dependent on CIP are now native to the VCSA 6.5 installer. Other CIP provided functions that are now native to the VCSA 6.5 installer include: New vCenter Server Appliance Deployment Walkthroughs - VMware vSphere Blog
From the Web client click on your VC instance from the left hand panel. Choose Monitor and Sessions Hope this Helps.
I would suggest deploying the VCSA appliance and using the embedded PSC configuration - thin provisioned if you are tight on space. I have a VCSA running and working for a few years and it curre... See more...
I would suggest deploying the VCSA appliance and using the embedded PSC configuration - thin provisioned if you are tight on space. I have a VCSA running and working for a few years and it currently datastore usage in at 22GB. 120GB is to allow for future growth. Check ut https://davidring.ie/2016/10/12/vsphere-vcsa-6-0-sizing/ for more details on VCSA Sizing.
Had the same issue of the weekend and this KB resolved it. Replacing the Lookup Service SSL certificate on a Platform Services Controller 6.0 (2118939) | VMware KB You should be able to view ... See more...
Had the same issue of the weekend and this KB resolved it. Replacing the Lookup Service SSL certificate on a Platform Services Controller 6.0 (2118939) | VMware KB You should be able to view your current cert at C:\ProgramData\VMware\vCenterServer\runtime\VMwareSTSService\conf\ssoserver.p12
Its been a  while but here is some updates to the syntax that is working for me . write-host -ForeGroundColor green "Setting Up Network on Host1" $esxcli = Get-EsxCli -VMHost Host1 write-ho... See more...
Its been a  while but here is some updates to the syntax that is working for me . write-host -ForeGroundColor green "Setting Up Network on Host1" $esxcli = Get-EsxCli -VMHost Host1 write-host -ForeGroundColor green "Adding portgroup Esx-l3vmotion to vSwitch0" $esxcli.network.vswitch.standard.portgroup.add("Esx-l3vmotion", "vSwitch0") write-host -ForeGroundColor green "Setting Portgroup Esx-l3vmotion to vSwitch0" $esxcli.network.vswitch.standard.portgroup.set("Esx-l3vmotion", "117") write-host -ForeGroundColor green "Adding vmotion stack to portgroup" $esxcli.network.ip.netstack.add($false, "vmotion") write-host -ForeGroundColor blue "Creating Esx-l3vmotion VMKernal on vSwitch0 with VMK Number vmk2" $esxcli.network.ip.interface.add($null, $null, "vmk2", $null, "1500", "vmotion", "Esx-l3vmotion") write-host -ForeGroundColor yellow "Assigning 10.10.117.10 to Esx-l3vmotion on vSwitch0" $esxcli.network.ip.interface.ipv4.set("vmk2", "10.10.117.10","255.255.255.0", $null, "static")
Let Me test this and ill get back to you .
I have done this recently to co-inside with Domain name change on a host Updated the DNS records disconnected the host and then removed the host, added in the host with the new FQDN  and all w... See more...
I have done this recently to co-inside with Domain name change on a host Updated the DNS records disconnected the host and then removed the host, added in the host with the new FQDN  and all worked away fine. I didnt even have to move the VM Workload off the Host.
Has anyone else noticed the DNS Setting from any non Default TCP/IP stack are removed from the configuration after reboot . I have attempted to set  via the Webclient and the Command line usin... See more...
Has anyone else noticed the DNS Setting from any non Default TCP/IP stack are removed from the configuration after reboot . I have attempted to set  via the Webclient and the Command line using esxcli command [root@ESXI01:~] esxcli network ip dns server add -N vmotion -s 10.108.1.1 [root@ESXI01:~] esxcli network ip dns server add -N vmotion -s 10.108.1.2 [root@ESXI01:~] esxcli network ip dns server list -N vmotion                             DNSServers: 10.108.1.1, 10.108.1.2 Post reboot [root@ESXI01:~] esxcli network ip dns server list -N vmotion                            DNSServers: Running ESXi 6.0.0 Build number 2809209 Regards Cliff
I'm looking to enable the vMotion TCP/IP Stack prior to migrating the VMK to use the Stack. Setting DNS Values, Domain Name and default gateway to allow for L3 capabilities I ma hoping to compet... See more...
I'm looking to enable the vMotion TCP/IP Stack prior to migrating the VMK to use the Stack. Setting DNS Values, Domain Name and default gateway to allow for L3 capabilities I ma hoping to compete this using using ESXCLI commands on the newly provisioned host that will read the command via a KS script as there are no CMDlets in PowerCli available as of yet. It seems pretty straight forward to create the fresh new stack and then add the VMK using this method. esxcli network ip netstack add --netstack new-vmotion esxcli network ip dns search  add  --netstack new-vmotion --domain test.domain esxcli network ip dns server  add  --netstack new-vmotion --server 192.168.5.5 esxcli network ip dns server  add  --netstack new-vmotion --server 192.168.5.6 esxcli network vswitch standard portgroup add --portgroup-name Vmotion_ESX --vswitch-name vSwitch0 esxcli network vswitch standard portgroup set --portgroup-name Vmotion_ESX --vlan-id 202 esxcli network ip interface add --interface-name vmk10 --portgroup-name Vmotion_ESX --netstack new-vmotion esxcli network ip interface ipv4 set --interface-name vmk10 --ipv4 192.168.111.100 --netmask 255.255.255.0 --type static esxcli network ip route ipv4 add --network 192.168.111.0/24 --netstack new-vmotion --gateway 192.168.111.1 But if i want to use the existing stacks (vMotion, Provisioning ) that are automatically created during install they don't seem to listed. With the exception of the defaultTcpipStack as per below. esxcli network ip netstack list defaultTcpipStack Key: defaultTcpipStack Name: defaultTcpipStack State: 4660 I manually created the VMK and Migrated to the system stack using the web client. Once i Did i re-ran the  esxcli network ip netstack list command  and both default and the vmotion netstack were listed defaultTcpipStack   Key: defaultTcpipStack   Name: defaultTcpipStack   State: 4660 vmotion   Key: vmotion   Name: vmotion   State: 4660 I tried using the "vmotion" Key/Name list from the above command to edit the dns setting etc but to no luck there either. One last thing i did try was to enable the Netstack as i noticed you could create them in disabled mode esxcli network ip netstack set --netstack vmotion --enable true Unable to find a Netstack instance vmotion Any ideas if it is possible to edit the system TCP/IP NetStacks via the esxcli prior to adding the Vmks ? Once the VMk has been migrated it is possible to edit the DNS setting etc via esxcli Any help or pointers appreciated
Yep i had a look through the release notes . No New relevant cmdlets unfortunately . I might have a look to complete it by using the ESXCLI in host install KS script
Script works fine one vSphere 6.0 aswell - I'm looking to update it in order to do all the new vMotion L3 Enhancements that were released in vSphere6.0
Hi tjurgens‌ Thanks for the reply - I have no issue creating vMotion on the any vSphere version that is Pre 6.0. Issue only arises when i need to create and new TCP/IP stack and assign tha... See more...
Hi tjurgens‌ Thanks for the reply - I have no issue creating vMotion on the any vSphere version that is Pre 6.0. Issue only arises when i need to create and new TCP/IP stack and assign that stack to the vMotion VMK - This is to allow for L3 vMotion Attached is sample of what i used to create vMotion VMk currently on anything pre vSphere6.0 ########################################################## # Add vMotion VMkernel port for all servers in a cluster # ########################################################## # # VERSION - 1.2 # param(     [Parameter(Mandatory=$true)]$vcenter,   $Subnet = "255.255.255.0",   $vMotionVLAN = "25",   $vMotionName = "Vmotion",   $vmotion_ip_start = "192.168.25.100",   $VMhost ="*",   $clusterName = '*' ) ##########################################################    $server = connect-viserver $vcenter # Start Creating vMotion Network ############################# $vmotion_ip_start_int=$vmotion_ip_start.split('.') $vmotion_ip_start_int=[int]$vmotion_ip_start_int[3] Write-Host -ForegroundColor Yellow "Start Creating vMotion Network".ToUpper() ForEach ($VMhostname in ($cluster | Get-VMHost -name $VMhost)| sort) {   if ($VMhostname | Get-VMHostNetworkAdapter -VMKernel | where {$_.PortGroupName -match $vMotionName}) {   Write-host -ForegroundColor yellow "WARNING : $VMhostname already has a VMkernel port named $vMotionName - Skipping"   }   else {   write-host -ForegroundColor green "Creating vMotion port group for $VMhostname"   $netIP = $vmotion_ip_start.split('.')   $IP = $netIP[0] + '.' + $netIP[1] + '.' + $netIP[2] + '.' + $vmotion_ip_start_int   $null = New-VMHostNetworkAdapter -VMHost $VMhostname -PortGroup $vMotionName -VirtualSwitch $(Get-VirtualSwitch -VMHost $VMhostname) -IP $IP -SubnetMask $Subnet -VMotionEnabled $true   $null = Get-VirtualPortGroup -Name $vMotionName -VMHost $VMhostname | Set-VirtualPortGroup -VLanId $vMotionVLAN   $vmotion_ip_start_int = $vmotion_ip_start_int +1   }   }   Write-Host -ForegroundColor Green "End Creating vMotion Network".ToUpper()   # End Creating vMotion Network ###############################
Hi all, Has anyone successfully automated the creation of the vMotion TCP/IP Stack on each host and then the creation of the vMotion VMK utilizing the newly created stack. Regards Cliff
Thanks Luc - Worked perfectly 
I always found with the custom specs that i needed to have a second NIC card in my initial template that i was cloning from This is what i have used successfully - Its pretty specific to my e... See more...
I always found with the custom specs that i needed to have a second NIC card in my initial template that i was cloning from This is what i have used successfully - Its pretty specific to my environment but i think you will get the idea. param(   $staging_vcenter = '192.168.101.101', $OrgName = "test", $VMPassword = "pass", ##### AMP Hosts ##### $Esxihost = 'esx01.build.local', $VMVER = 'v9', ##### Management ##### $MGMT='MGMT_VLAN', $MGMTVLAN='105', $VMSubnet ="255.255.255.0", $VMDefaultGateway ="192.168.105.1", ##### Customisation Specs ##### $OSCostumSpec_VC = "VC-Vcenter", ##### VM Templates ##### $vcenterTemplate = 'W2K12R2-STD-Template', ##### VM IP Addressing ##### $VCVMIP ="192.168.105.100", ##### VM Hostnames ##### $VCVM ="vc.domain.local", ##### VM License Keys ##### $WinProductKey_VC = "12345-12345-12345-12345-12345", ##### Domain, DNS, Timezone ##### $domainName = "build.local", $DNS = "192.168.101.253", $DNS2 = "192.168.101.252", $TimeZone = "090" ) #End Setting Paramters for Scripts #Connect to vCenter Write-Verbose "Connecting to vCenter" $server = Connect-VIServer $vCenter -credential $(get-credential) $myhost = Get-VMHost -Name $Esxihost $h1ds1 = $myhost | Get-Datastore -name *local New-OSCustomizationSpec -Name $OSCostumSpec_VC -OSType Windows -AdminPassword $VMPassword  -TimeZone $TimeZone -ProductKey $WinProductKey_VC -ChangeSid -OrgName $OrgName -NamingScheme Fixed -NamingPrefix $VCVM.split(".")[0] -fullname Administrator -Workgroup WORKGROUP New-OSCustomizationNicMapping -OSCustomizationSpec $OSCostumSpec_VC -IpMode UseStaticIP -IPAddress $VCVMIP -SubnetMask $VMSubnet -DefaultGateway $VMGefaultGateway -Dns $DNS,$DNS2 -Position 1 New-VM -VMHost $Esxihost -Name $VCVM -Datastore $h1ds1 -Template $vcenterTemplate -OSCustomizationSpec $OSCostumSpec_VC Get-VM -name $VCVM | Set-VM -Version $VMVER -confirm:$false Get-NetworkAdapter -VM $VCVM | where {$_.Name -eq "Network adapter 2"} | Remove-NetworkAdapter -confirm:$false Get-NetworkAdapter -VM $VCVM | where {$_.Name -eq "Network adapter 1"} | Set-NetworkAdapter -NetworkName $MGMT -confirm:$false -StartConnected:$true Remove-OSCustomizationSpec $OSCostumSpec_VC -confirm:$false Set-VM -VM $VCVM  -MemoryGB 24 -NumCpu 4  -Description "vCenter Server" -confirm:$false $VMdisk = Get-HardDisk -vm $VCVM  -Name "Hard Disk 1" Set-HardDisk -HardDisk $VMdisk -CapacityGB 60 -confirm:$false $VMdisk2 = Get-HardDisk -vm $VCVM  -Name "Hard Disk 2" Set-HardDisk -HardDisk $VMdisk2 -CapacityGB 40 -confirm:$false
Hi Luke, Thanks for the reply. Rather than calling an external .ps1 Would be possible to have all the commands listed internally in the initial .ps1. A Standalone script that wouldn't relay on... See more...
Hi Luke, Thanks for the reply. Rather than calling an external .ps1 Would be possible to have all the commands listed internally in the initial .ps1. A Standalone script that wouldn't relay on any external files. i tried something like this $create = "Add-DnsServerPrimaryZone $101zone -Zonefile $101zone.dns" $create = $create + "Add-DnsServerPrimaryZone $101zone -Zonefile $105zone.dns" $create = $create + "Add-DnsServerResourceRecordA -Name myhost -IPv$Address 192.168.101.55 -ZoneName build.local -CreatPtr" $create = $create + "Add-DnsServerResourceRecordA -Name myhost01 -IPv$Address 192.168.105.55 -ZoneName build.local -CreatPtr" Invoke-VMScript -ScriptText $create -VM $VCVM -GuestUser Administrator -GuestPassword pass But no luck
Hi all, Guys I am trying to install DNS via the Invoke-VMScript Command  ,  Create all relevant Zone and A Records and PTRs. Install the DNS is fine and so is added all the Primary Zones an... See more...
Hi all, Guys I am trying to install DNS via the Invoke-VMScript Command  ,  Create all relevant Zone and A Records and PTRs. Install the DNS is fine and so is added all the Primary Zones and A Records Etc #Start Setting Paramters for Scripts param(   [Parameter(Mandatory=$true)]$vCenter,   $VCVM = 'TestDNS',   $101Subnet = "192.168.101.0",   $105Subnet = "192.168.105.0",   $domain = "build.local" ) #End Setting Paramters for Scripts #Connect to vCenter $server = Connect-VIServer $vCenter -credential $(get-credential) $installdns = "Install-WindowsFeature DNS -includeManagementTools" Invoke-VMScript -ScriptText $installdns -VM $VCVM -GuestUser Administrator -GuestPassword pass Write-host -foregroundcolor Yellow "DNS Installed" $create = "Add-DnsServerPrimaryZone $101zone -Zonefile $101zone.dns" Invoke-VMScript -ScriptText $create -VM $VCVM -GuestUser Administrator -GuestPassword pass $create = "Add-DnsServerPrimaryZone $101zone -Zonefile $101zone.dns" Invoke-VMScript -ScriptText $create -VM $VCVM -GuestUser Administrator -GuestPassword pass $create = "Add-DnsServerPrimaryZone $101zone -Zonefile $105zone.dns" Invoke-VMScript -ScriptText $create -VM $VCVM -GuestUser Administrator -GuestPassword pass $create = "Add-DnsServerResourceRecordA -Name myhost -IPv$Address 192.168.101.55 -ZoneName build.local -CreatPtr" Invoke-VMScript -ScriptText $create -VM $VCVM -GuestUser Administrator -GuestPassword pass $create = "Add-DnsServerResourceRecordA -Name myhost01 -IPv$Address 192.168.105.55 -ZoneName build.local -CreatPtr" Invoke-VMScript -ScriptText $create -VM $VCVM -GuestUser Administrator -GuestPassword pass My Question is rather than calling out all the individual commands and invoking each line individually is it possible to invoke all the lines as above i there a way of calling a whole .Ps1 script that would have all the syntax included or call all the lines with having to write individual Invoke-VMScript commands ? Appreciate the help as allays Regards Cliff
Luc, -ExpandProperty I wasn't aware of this option. That worked perfectly. Thank you. Regards Cliff