Q: 14
The administrator has to change the DRS automation level in preparation to upgrade the vCenter.
When making this change through VCF Operations, the following error occurs: 'Internal Error: Failed
to retrieve vim client'.
What is the possible cause of this error?
Options
Discussion
Option C makes sense, but if vCenter is being upgraded and some services get restarted briefly, you might see weird connection issues like this. So, connectivity isn't always just a firewall or DNS thing, could be due to vCenter state too. Anyone see that in practice?
Yeah that's C for sure.
C or B, but more likely C. That error usually means comms issue between VCF Ops and vCenter.
Probably C here since 'Failed to retrieve vim client' almost always shows up when VCF can't reach vCenter at all. Network or DNS hiccups are super common in these setups, so I'm leaning that way unless someone has seen B actually cause this error?
C is what I'd go with, since a "Failed to retrieve vim client" usually points to a basic communication problem between VCF and vCenter, like network or firewall issues. Not totally ruling out B, but pretty sure C fits the classic failure here. Agree?
Guessing B since I've seen similar errors pop up when vCenter gets hit with a bunch of API traffic, especially during busy upgrades. Not 100% sure, but seems plausible if VCF Operations is pushing lots of requests. Agree?
Honestly I see why folks go with C, but I'm picking B here. If vCenter is being hammered by too many API requests from VCF Operations, it could fail to return the vim client too-not just pure network issues. Could be a trap since both look similar on the surface. Anyone disagree?
I’d say a classic connectivity problem to me, so C.
C
C over B. Pretty sure B is a trap, since 'vim client' errors are network related, not API load.
Be respectful. No spam.