rolfbar's Posts

Can someone tell me how to remove or uninstall vRLCM 
I am hoping some one can help me here, We are trying to bring up VCF 4.1 and we are getting the following error Failed to validate reachability of Application Virtual Networks with gateway IPs [192... See more...
I am hoping some one can help me here, We are trying to bring up VCF 4.1 and we are getting the following error Failed to validate reachability of Application Virtual Networks with gateway IPs [192.168.31.1, 192.168.11.1] the bring up has successfully completed the BGP Peering and BGP Route Distribution,  but then fails at the above, Here are the logs from cloud builder which says the p's are not ping able, Am i missing something the AVN is suppose to be an overlay and the route ability should just work considering the reset of the configuration completed ?     2020-12-15T17:01:21.974+0000 [bringup,319339794a43e898,1d40] DEBUG [c.v.e.s.s.ValidateAvnConnectivityAction,pool-3-thread-17] Checking reachability of AVN gateway IP 192.168.11.1 2020-12-15T17:01:21.975+0000 [bringup,319339794a43e898,1d40] INFO [c.v.e.s.c.v.p.NetworkValidator,pool-3-thread-17] Trying to ping address 192.168.11.1 2020-12-15T17:01:21.975+0000 [bringup,319339794a43e898,1d40] DEBUG [c.v.e.s.c.util.HostValidationUtil,pool-3-thread-17] Trying to ping to 192.168.11.1 2020-12-15T17:01:21.975+0000 [bringup,319339794a43e898,1d40] DEBUG [c.v.e.s.c.util.HostValidationUtil,pool-3-thread-17] Verify ping connectivity to 192.168.11.1 with command ping 192.168.11.1 -c 3 2020-12-15T17:01:21.975+0000 [bringup,319339794a43e898,1d40] DEBUG [c.v.e.s.c.util.LocalProcessService,pool-3-thread-17] Executing the Local command: ping 192.168.11.1 -c 3 2020-12-15T17:01:34.008+0000 [bringup,319339794a43e898,34ff] DEBUG [c.v.e.s.c.v.p.NetworkValidator,pool-4-thread-15] PING 192.168.11.1 (192.168.11.1) 56(84) bytes of data. 2020-12-15T17:01:34.008+0000 [bringup,319339794a43e898,34ff] DEBUG [c.v.e.s.c.v.p.NetworkValidator,pool-4-thread-15] 2020-12-15T17:01:34.008+0000 [bringup,319339794a43e898,34ff] DEBUG [c.v.e.s.c.v.p.NetworkValidator,pool-4-thread-15] --- 192.168.11.1 ping statistics --- 2020-12-15T17:01:34.008+0000 [bringup,319339794a43e898,34ff] DEBUG [c.v.e.s.c.v.p.NetworkValidator,pool-4-thread-15] 3 packets transmitted, 0 received, 100% packet loss, time 31ms 2020-12-15T17:01:34.008+0000 [bringup,319339794a43e898,34ff] DEBUG [c.v.e.s.c.v.p.NetworkValidator,pool-4-thread-15] 2020-12-15T17:01:34.008+0000 [bringup,319339794a43e898,1d40] ERROR [c.v.e.s.c.util.LocalProcessService,pool-3-thread-17] Local Command Failed with exit value 1. Output Logs :LocalProcess Output: 2020-12-15 17:01:34 - PING 192.168.11.1 (192.168.11.1) 56(84) bytes of data. LocalProcess Output: 2020-12-15 17:01:34 - LocalProcess Output: 2020-12-15 17:01:34 - --- 192.168.11.1 ping statistics --- LocalProcess Output: 2020-12-15 17:01:34 - 3 packets transmitted, 0 received, 100% packet loss, time 31ms LocalProcess Output: 2020-12-15 17:01:34 - Error Logs are stored at 2020-12-15T17:01:44.016+0000 [bringup,319339794a43e898,1d40] DEBUG [c.v.e.s.c.v.util.ResponseUtil,pool-3-thread-17] Build validation response: {"errorCode":"IP_REACHABLE.error","arguments":["192.168.11.1" ],"context":{"severity":"ERROR","bundleName":"com.vmware.evo.sddc.common.validation.errors.messages","validation.taskId":"7f000001-7666-1ca0-8176-66bf51d30164"},"message":"IP 192.168.11.1 is not reachable with ping"} 2020-12-15T17:01:44.017+0000 [bringup,319339794a43e898,1d40] WARN [c.v.e.s.s.ValidateAvnConnectivityAction,pool-3-thread-17] Failed to validate reachability of AVN IP 192.168.11.1: {"errorCode":"IP_REACHABLE.error","arguments":["192.168.11.1"],"context":{"severity":"ERROR","bundleName":"com.vmware.evo.sddc.common.validation.errors.messages","validation.taskId":"7f000001-7666-1ca0-8176-66bf51d30164"},"message":"IP 192.168.11.1 is not reachable with ping"} 2020-12-15T17:01:44.019+0000 [bringup,319339794a43e898,1d40] ERROR [c.v.e.s.o.model.error.ErrorFactory,pool-3-thread-17] [TB9QLJ] AVN_VALIDATION_FAILED Failed to validate reachability of Application Virtual Networks with gateway IPs [192.168.31.1, 192.168.11.1] com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to validate reachability of Application Virtual Networks with gateway IPs [192.168.31.1, 192.168.11.1]  
You are a machine, thank you very much
Hey Guys, We have a script that collects metrics from VC for VM's, Hosts and Datastores This scrips collects among other stuff host metrics which include the following datastore.datastor... See more...
Hey Guys, We have a script that collects metrics from VC for VM's, Hosts and Datastores This scrips collects among other stuff host metrics which include the following datastore.datastoreReadBytes.latest datastore.datastoreWriteBytes.latest datastore.datastoreNormalReadLatency.latest datastore.datastoreNormalWriteLatency.latest datastore.read.average datastore.write.average Now for all our host connected to SAN storage that metric is still valid, but for all VSAN hosts if we run Get-StatType -Entity "VMHosts" Those stat types are no longer available. Why have they been removed/moved and if they have been move where did VMWare move them too ? Thanks
Hi Guys, We have a powercli script which we run scheduled using the windows system account, this worked fine until we uninstalled the PowerCLI exe 6.5 and install 11.0 via PSGallery ? Anyone ... See more...
Hi Guys, We have a powercli script which we run scheduled using the windows system account, this worked fine until we uninstalled the PowerCLI exe 6.5 and install 11.0 via PSGallery ? Anyone experienced this ? Thanks Rolf
Hey Luc, PowerShell 5.1.14409.1005 VMware PowerCLI 11.0.0 build 10380590 Just to give more details We call this fomr the VMPoll.PS1 $postdeployment = 'CP-PostDeployment.ps1' $sb = [... See more...
Hey Luc, PowerShell 5.1.14409.1005 VMware PowerCLI 11.0.0 build 10380590 Just to give more details We call this fomr the VMPoll.PS1 $postdeployment = 'CP-PostDeployment.ps1' $sb = [scriptblock]::create("$postdeployment $VmId $SCCMSite") start-job -ScriptBlock $sb In CP-PostDeployment.ps1 LogEvent ("CP-PostDeployment: Rebooting $Hostname VmID $VmID") $vm | Restart-GuestVM -Confirm:$False LogEvent ("CP-PostDeployment: Setting Status $Hostname VmID $VmID to 11") with the above the first log event is sent and the restart works the VM is rebooted but the 2nd send LogEvent is not captured and there are some email cmd's after that which never happen, the VMPoll.PS1 will wait till the CP-PostDeployment.ps1 completes and exits. In this case the PostDeployment.ps1 runs indefinitely If I run $vm | Restart-VM -Confirm:$False -RunAsync    instead of the Restart-GuestVM everything resumes as normal, Now I know I am adding -RunAsync which is fire and forget. If I open PowerCLI and manually run the CMD's it all works as expected, the VM's reboot and the system returns to the prompt. as we are running these via an automated process we don't see the output of any of the cmd's so adding $vm.ExtensionData.Guest so anywhere. I will see if we can't capture that in the LogEvent and see what it writes. Thanks for the help
Hello Everyone, I have a situation where we are calling a PS1 (PostDeployScript) scripts from within another PS1 script (VMPoll), and in the PostDeployScript we have the cmd .... "Log to sys... See more...
Hello Everyone, I have a situation where we are calling a PS1 (PostDeployScript) scripts from within another PS1 script (VMPoll), and in the PostDeployScript we have the cmd .... "Log to syslog server - Rebooting " $vm | Restart-GuestVM -Confrim:$Fasle "Log to syslog server - Rebooted " .... Now this use to work fine with PowerCLI 6.5 and PowerShell v4, Ever since we upgraded to PowerCLI 11.0.x and PowerShell v5 the PostdeployScript get's held up at the Restart-GuestVM and never continues further, the powershell thread is still running and the Postdeploy never completes, almost as if it's waiting from some feedback or response. The VM does actually reboot as this can be seen the VC tasks. If we change the line $vm | Restart-VM -Confirm:$Fasle -RunAsync Then the script continues as expected, but this now means the first login post the reboot we see the error "unexpected reboot" Any help wold be appreciated