barnette08's Posts

Update:  I haven't spent much time in 8.0 Host UI and didn't realize we can now revert snapshots at the ESXi level.  So, I changed things up a bit to work without a cron job or Windows task. Migrat... See more...
Update:  I haven't spent much time in 8.0 Host UI and didn't realize we can now revert snapshots at the ESXi level.  So, I changed things up a bit to work without a cron job or Windows task. Migrate vCenter to first host of cluster. Disconnect from vCenter Connect to first host Revert vCenter from snapshot on first host. Power on vCenter. Probe vCenter to be back online. Connect to vCenter.
I'm looking to revert vCenter from a snapshot, but as you might know this will disconnect you from the PowerCLI session.  I'd like to try and revert the snapshot and disconnect quickly so that the se... See more...
I'm looking to revert vCenter from a snapshot, but as you might know this will disconnect you from the PowerCLI session.  I'd like to try and revert the snapshot and disconnect quickly so that the session doesn't hang so that I can execute the rest of the steps (3-7).  Any ideas?  Mainly looking for getting around the session hang and figuring out the probe vCenter readiness. High level flow: Migrate vCenter to first host of cluster. Revert vCenter from snapshot. Disconnect from vCenter. Connect to first host. Power on vCenter. Probe vCenter to be back online Connect to vCenter.
Yep, tried that.  I'll keep digging and update if I find anything.  Thanks for the help as always @LucD !
Hmmmm....I've set to prompt and disconnected and reconnected and still the same error.  Also I've validated that the cert is using the FQDN and that's what I'm connecting with.  I tried to connect wi... See more...
Hmmmm....I've set to prompt and disconnected and reconnected and still the same error.  Also I've validated that the cert is using the FQDN and that's what I'm connecting with.  I tried to connect with IP to compare behaviors and I get the prompt for invalid cert there but accepted it, then ran the Invoke-SetAccessSsh -AccessSshSetRequestBody $AccessSshSetRequestBody again, but still get the same SSL error.
I set it to ignore:  
It looks to be set: PS C:\Windows\system32> [enum]::GetNames([Net.SecurityProtocolType]) SystemDefault Ssl3 Tls Tls11 Tls12 Tls13
Ran into some dependency issues but was able to uninstall and reinstall to the latest.  I do get an error though when running the invoke.   Invoke-ApiClient : The underlying connection was closed: ... See more...
Ran into some dependency issues but was able to uninstall and reinstall to the latest.  I do get an error though when running the invoke.   Invoke-ApiClient : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. At C:\Program Files\WindowsPowerShell\Modules\VMware.Sdk.vSphereRuntime\8.0.1111.21624264\Private\vSphereApiClient.ps1:128 char:9 + Invoke-ApiClient @invokeParams + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-ApiClient
I saw that but I've never used invoke before.  When I tried the example at Set SSH.  I get The term 'Initialize-AccessSshSetRequestBody' is not recognized as the name of a cmdlet, function, script fi... See more...
I saw that but I've never used invoke before.  When I tried the example at Set SSH.  I get The term 'Initialize-AccessSshSetRequestBody' is not recognized as the name of a cmdlet, function, script file, or operable program. PowerCLI Version ---------------- VMware.PowerCLI 12.3.0 build 17860403 --------------- Component Versions --------------- VMware Common PowerCLI Component 13.1 build 21605386 VMware Cis Core PowerCLI Component PowerCLI Component 13.1 build 21605976 VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 13.1 build 21606170
Man, I knew I was moving too fast...I meant enabling SSH on the vCenter appliance!  Apologies!
I'm positive this has been done by someone using the API since there don't seem to be any cmdlets for it.  Can someone please point me to a post I haven't been able to find any.
I've seen a few posts on this similar topic but I can't seem to narrow down the issue. Any ideas?   When I ssh into the supervisor node and issue the  kubectl get pods -A command and can see that I... See more...
I've seen a few posts on this similar topic but I can't seem to narrow down the issue. Any ideas?   When I ssh into the supervisor node and issue the  kubectl get pods -A command and can see that I'm getting a crashloop for coredns.   NAMESPACE NAME kube-system coredns-5dc469f6f-tvljf 0/1 CrashLoopBackOff     When I take a look into /var/log/vmware/wcp/wcpsvc.log, I can see that there's a timeout issue.   2021-07-15T19:01:40.58Z error wcp [opID=60f056b8-domain-c144] Error creating NSX resources. Err: Get https://supervisor-cluster-ip:0/apis/vmware.com/v1alpha1/nam espaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1050%29: dial tcp supervisor-cluster-ip:0: i/o timeout 2021-07-15T19:01:40.58Z error wcp [opID=60f056b8-domain-c144] Failed to create cluster network interface for MasterNode: VirtualMachine:vm-1050. Err: Get https://supervisor-cluster-ip:0/apis/vmware.com/v1alpha1/namespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1050%29: dial tcp 10.234. 146.171:0: i/o timeout 2021-07-15T19:01:40.58Z error wcp [opID=60f056b8-domain-c144] Error configuring cluster NIC on master VM vm-1050: Get https://supervisor-cluster-ip:0/apis/vmware .com/v1alpha1/namespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1050%29: dial tcp supervisor-cluster-ip:0: i/o timeout 2021-07-15T19:01:40.58Z error wcp [opID=60f056b8-domain-c144] Error configuring API server on cluster domain-c144 Error configuring cluster NIC on master VM. This operation is part of API server configuration and will be retried. 2021-07-15T19:01:40.629Z error wcp [opID=60f056b8-domain-c144] Error checking if NSX resources exist. Err: Get https://supervisor-cluster-ip:0/apis/vmware.com/v1 alpha1/namespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1049%29: dial tcp supervisor-cluster-ip:0: i/o timeout 2021-07-15T19:01:40.629Z error wcp [opID=60f056b8-domain-c144] Error checking if NSX resources exist for VMs: [vm-1049]. Err: Get https://supervisor-cluster-ip:0 /apis/vmware.com/v1alpha1/namespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1049%29: dial tcp supervisor-cluster-ip:0: i/o timeout 2021-07-15T19:01:40.629Z error wcp [opID=60f056b8-domain-c144] Error creating NSX resources. Err: Get https://supervisor-cluster-ip:0/apis/vmware.com/v1alpha1/na mespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1049%29: dial tcp supervisor-cluster-ip:0: i/o timeout 2021-07-15T19:01:40.629Z error wcp [opID=60f056b8-domain-c144] Failed to create cluster network interface for MasterNode: VirtualMachine:vm-1049. Err: Get https://supervisor-cluster-ip:0/apis/vmware.com/v1alpha1/namespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1049%29: dial tcp 10.234 .146.171:0: i/o timeout 2021-07-15T19:01:40.629Z error wcp [opID=60f056b8-domain-c144] Error configuring cluster NIC on master VM vm-1049: Get https://supervisor-cluster-ip:0/apis/vmwar e.com/v1alpha1/namespaces/kube-system/virtualnetworkinterfaces?labelSelector=vm-moid+in+%28vm-1049%29: dial tcp supervisor-cluster-ip:0: i/o timeout 2021-07-15T19:01:40.629Z error wcp [opID=60f056b8-domain-c144] Error configuring API server on cluster domain-c144 Error configuring cluster NIC on master VM. This operation is part of API server configuration and will be retried. 2021-07-15T19:01:40.629Z warning wcp [opID=60f056b8-domain-c144] Error configuring cluster NIC. Err <nil> 2021-07-15T19:01:40.629Z warning wcp [opID=60f056b8-domain-c144] Error configuring cluster NIC. Err <nil> 2021-07-15T19:01:40.629Z warning wcp [opID=60f056b8-domain-c144] Error configuring cluster NIC. Err <nil> 2021-07-15T19:01:40.629Z info wcp [opID=60f056b8-domain-c144] no single master succeeded - retrying 2021-07-15T19:02:54.238Z error wcp [opID=vapi] Authentication failed. 2021-07-15T19:02:54.238Z error wcp [opID=vapi] Unable to authenticate user 2021-07-15T19:02:54.238Z debug wcp [opID=vapi] Sending response with output {"error":{"ERROR":{"com.vmware.vapi.std.errors.unauthenticated":{"data":{"OPTI ONAL":null},"error_type":{"OPTIONAL":"UNAUTHENTICATED"},"messages":[{"STRUCTURE":{"com.vmware.vapi.std.localizable_message":{"args":[],"default_message":" Unable to authenticate user","id":"vapi.security.authentication.invalid","localized":{"OPTIONAL":null},"params":{"OPTIONAL":null}}}}]}}}}        
Right, I agree with all that, but there isn't a witness available to download for U1d (only U1c is available).  So it sounds like the intent is to deploy U1c and then upgrade to U1d.  It's just not s... See more...
Right, I agree with all that, but there isn't a witness available to download for U1d (only U1c is available).  So it sounds like the intent is to deploy U1c and then upgrade to U1d.  It's just not spelled out in the VCF BOM, instead it's in the VVD BOM as others have pointed out (assumedly because multi-az is considered a solution and is thus in the "VVD" documentation).
Thanks I hadn't looked over at the VVD BOM in a while.  Seems like specifically this component should be the same in both places.
I've noticed that VCF 4.2.1 makes use of ESXi 7.0U1d and vSAN is no longer listed as a line item on the BOM because it ties to the ESXi version.  However, only the witness appliance is available in 7... See more...
I've noticed that VCF 4.2.1 makes use of ESXi 7.0U1d and vSAN is no longer listed as a line item on the BOM because it ties to the ESXi version.  However, only the witness appliance is available in 7.0U2, 7.0U1c, etc. Is the desired outcome to deploy the witness as 7.0U1c and then upgrade or remain at the 7.0U1c witness that is available for download?
Thanks I spoke with @bo_busillo offline and he confirmed that GSS was only using it to isolate the issue and is not part of a workaround.  The true fix is coming in a feature patch release in the nea... See more...
Thanks I spoke with @bo_busillo offline and he confirmed that GSS was only using it to isolate the issue and is not part of a workaround.  The true fix is coming in a feature patch release in the near future.
Any ideas where to get version-2 of vmkusb driver?
What about systems with local SD boot, but /scratched placed on a remote datastore?  This would relieve some of the SD I/O wouldn't it? Or is it not enough to make a difference?  That's the default i... See more...
What about systems with local SD boot, but /scratched placed on a remote datastore?  This would relieve some of the SD I/O wouldn't it? Or is it not enough to make a difference?  That's the default installation we use.
Correct, it seemed to work just fine.  Of course, be sure to take a snapshot of SDDC Manager just in case!
@kivlintom, nope I was only able to get vRSLCM removed and start over from there by redeploying vRSLCM from SDDC Manager.
@MannyRodriguez1 any ideas on how to remove a WSA global environment from vRSLCM instead of removing vRSLCM from SDDC Mgr?  The delete button isn't available on the environment.