An NSX administrator can change or deploy a new form factor or version of the service VM (SVM).
Note: In releases before
NSX 3.2, the
Change Appliance was called
Re-deploy Appliance.
This task can be done both from UI or API.
The API command to change or upgrade a SVM is
/POST https://<NSX_Manager_IPaddress>/api/v1/serviceinsertion/services/{{service_id}}/service-deployments /<service-deployment-id>?action=upgrade
.
{ "deployment_spec_name": "EW_DepSpec" }
Prerequisites
- Ensure that partners have registered multiple service VMs differentiated by versions and or form factor (disk, vCPU, or RAM). The Change Appliance is available only when multiple service VMs are deployed.
- Ensure that the SVM deployment status is Deployment Successful before changing the appliance. If the SVM is in a different state, go to Home → Alarms, and search for any open alarms of the event type EAM. Resolve errors before trying to change to a newer SVM.
- Ensure that all prereqiuistes required to deploy an endpoint service or a combined partner service (for example, endpoint protection service and network gateway firewall) are met before proceeding to change the appliance.
- Ensure that storage is available before you change the existing SVM with a new one.
- If there are workloads that are protected by the existing SVM, first perform vMotion to migrate the workload and then change or deploy the new SVM.
Procedure
Results
What to do next
To know the runtime status of a combined partner service, health status of an endpoint protection service, or deployment status, go to the Service Instances tab.
After changing the existing SVM to a new SVM, enable guest VMs that are to be protected by the endpoint protection policy service.