I recently ran into a situation where a customer had removed a vcenter server from their environment and built another but had not decommissioned the first from the PSC. When they were trying to view some screens that showed data across the environment, the interface would time out looking for that vCenter.
There is a VMWare KB that talks about the process to follow in decommissioning a vCenter server that needs to be removed from the PSC. That process only succeeds if the vCenter server is still available.
Given that the fqdn of the vCenter server was VC1.corp.local
- SSH to the PSC.
- CD to /usr/lib/vmware-vmdir/bin/
- Run the command ./vdcleavefed -h VC1.corp.local -u administrator
- Enter the email@example.com password:
- If the command is successful, you are prompted with:
- ‘ vdcleavefd offline for server VC1.corp.local Leave federation cleanup done’
Some common errors:
“Leave federation cleanup failed. Error – Confidentiality required.”
Check the FQDN or try using the IP address in its place
“Error (9234) – User invalid credential”
Check the username and password. When I used the domain qualified user firstname.lastname@example.org, I received this error. Using only administrator with the password for email@example.com worked for me.
If you run into any unexpected errors the log can be found at
SNMP has been made more strait forward in vCLI5.1. We can now make all configuration changes in ESXCLI.
The namespace to set the SNMP server settings are under esxcli system snmp.
We can use the set get and test methods, but the methods are strait forward.
DirectPath I/O is available from vSphere 4.0 forward. It uses Intel VT-d and AMD-Vi to allow guests to directly access hardware devices. When using DirectPath a VM can’t use vMotion, snapshots or any feature which leverage them. The directly allocated device isn’t available to other VMs. The only change with vSphere5 is that you can vMotion a VM provided it is in a supported hardware configuration that allows that direct path to the host hardware to persist.
The benefit of DirectPath is very specific. You can offload CPU cycles that the VMM would need to perform to schedule those resources and expose hardware component features that are not yet available through virtualized drivers or that ESXi cannot recognize. There is a performance benefit available in some cases.
The tradeoff is to nearly nullify the benefit of agility inherent in virtualization, effectively tying a guest to a host.
There is a KB describing the configuration process.
I am starting to put together my notes for the VCAP5-DCA exam.
Some of this will be restated information from other sources, and I’ll try to site references where possible, but because I’m really just collecting my own thoughts here, your mileage may vary.
The plan is to review all of the information in the Blueprint http://mylearn.vmware.com/mgrReg/plan.cfm?plan=47316&ui=www_cert
I will post a description of each topic and notes about how to affect the topic. My goal is to have identified places where I rely heavily on documentation and would be hindered in the exam.
After I note each category I will take some highlights and recreate them in a video. This is new territory for me so I may not be quick to get these posted.
Let’s see how long this takes me to really get done.