One-click mechanisms for software (eg upgrades to AOS, hypervisor, NCC, Foundation etc) are the same for NX and XC. For the hardware side, it will be likely that NX will have h/w support for one-click upgrades a little faster than the OEM h/w, but the lag should be minimal.
For example, in LCM 1.1 (due this month), it will support updating SATADOM and HBA on NX, but only SATADOM on XC. In LCM 1.2 (approx 4-8 weeks after 1.1), it is expected that both NX and XC will be on parity on the h/w side for updates. Note that you don't need to upgrade AOS to get the latest LCM to 'unlock' newer updating features/mechanisms.
The intention of LCM is that you should be able to drive all updates to your Nutanix cluster (hardware and software) from the one place in Prism - no need for external tool sets.
Prism Element is a service running on your CVM. When nodes deployed as cluster you will access Prism Element to manage the cluster (Native)
Prism Central is VM running either on Nutanix or other host to manage multiple Nutanix cluster (you need to deploy it first and joining you Prism Element to Prism Central)
Do not think it is the hypervisor, because it is the same version as before upgrade, only thing changed was the upgrade to 5.0.2
My CVM:s only had 16 Gb or RAM and since v 5 the recommended amount is 32 Gb aparently. I have increased to 32 Gb so the error is not there any more.
But the general feeling is that the upgrade did not do any good for my cluster, only I higher memory consumtion. But it is not an big issue right now, I need to add a node soon anyway to the cluster.
Log onto their support site, portal.nutanix.com and under the downloads drop down there is a Hypervisor details which shows what versions are supported. I would also suggestion going to the Documentation drop down and look at the software documentation section. Inside that is a vSphere Administration Guide for Acropolis (using vSphere Web Client) that should answer most of your other questions.
You can have a other way to work around on this by using the internal network 192.168.5.0 between CVM and Host to execute the command remotely
By the way, you should check the connection to the desired host IP and SSH port as well
// Bạn đang ở VN?