In the current release, CSM can only be upgraded using NSX CLI.
Prerequisites
- See Upgrading NSX Cloud Components to find the correct order to follow for upgrading CSM.
- You must have extracted the file VMware-NSX-unified-appliance-<version>.nub from the NSX Cloud master upgrade bundle (MUB) and hosted on an FTP server accessible from CSM.
Procedure
- Log in to NSX CLI with CSM admin credentials:
$ssh <csm-admin>@<NSX-CSM-IP>
and run the following NSX CLI command:
nsxcsm> copy url scp://<username>@<ftp-server-ip>/<path-to-file>/VMware-NSX-unified-appliance-<version>.nub
- Extract and verify the file VMware-NSX-unified-appliance-<version>.nub:
nsxcsm> verify upgrade-bundle VMware-NSX-unified-appliance-<version>
Example output:
Checking upgrade bundle /var/vmware/nsx/file-store/VMware-NSX-unified-appliance-<version>.nub contents
Verifying bundle VMware-NSX-unified-appliance-<version>.bundle with signature VMware-NSX-unified-appliance-<version>.bundle.sig
Moving bundle to /image/VMware-NSX-unified-appliance-<version>.bundle
Extracting bundle payload
Successfully verified upgrade bundle
Bundle manifest:
appliance_type: 'nsx-unified-appliance'
version: '<upgrade version>'
os_image_path: 'files/nsx-root.fsa'
os_image_md5_path: 'files/nsx-root.fsa.md5'
Current upgrade info:
{
"info": "",
"body": {
"meta": {
"from_version": "<current version>",
"old_config_dev": "/dev/mapper/nsx-config",
"to_version": "<post-upgrade version>",
"new_config_dev": "/dev/mapper/nsx-config__bak",
"old_os_dev": "/dev/xvda2",
"bundle_path": "/image/VMware-NSX-unified-appliance-<version>",
"new_os_dev": "/dev/xvda3"
},
"history": []
},
"state": 1,
"state_text": "CMD_SUCCESS"
}
- Start the upgrade:
nsxcsm> start upgrade-bundle VMware-NSX-unified-appliance-<version> playbook VMware-NSX-cloud-service-manager-<version>-playbook
Example output:
Validating playbook /var/vmware/nsx/file-store/VMware-NSX-cloud-service-manager-<version>-playbook.yml
Running "shutdown_csm_svc" (step 1 of 6)
Running "install_os" (step 2 of 6)
Running "migrate_csm_config" (step 3 of 6)
System will now reboot (step 4 of 6)
After the system reboots, use "resume" to start the next step, "start_csm_svc".
{
"info": "",
"body": null,
"state": 1,
"state_text": "CMD_SUCCESS"
}
Autoimport-nsx-cloud-service-manager-thin>
Broadcast message from root@Autoimport-nsx-cloud-service-manager-thin (Fri 2017-08-25 21:11:36 UTC):
The system is going down for reboot at Fri 2017-08-25 21:12:36 UTC!
- Wait for the upgrade to complete. CSM reboots during upgrade, and the upgrade is finalized when the CSM UI restarts after rebooting.
- Verify the version of CSM to confirm that it has upgraded:
Results
The
CSM appliance is upgraded and the
PCGs are automatically resized to 191 GB.
What to do next
- If you are upgrading from version 2.4.x to 2.5.0 or later, or from 3.0.x to later, follow the steps here for Post-Upgrade Tasks because you have already upgraded NSX-T Data Center.
- If you are upgrading from version 2.5.0 to later, proceed to Upgrading NSX-T Data Center.