The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
When you add a hard disk to a virtual machine, you can create a new virtual disk, add an existing virtual disk, or add a mapped Storage Area Network (SAN) Logical Unit Number (LUN).
In most cases, you can accept the default device node. For a hard disk, a non default device node is useful to control the boot order or to have different Small Computer System Interface (SCSI) controller types. For example, you might want to boot from an LSI Logic controller and use a Buslogic controller with bus sharing turned on to share a data disk with another virtual machine.
For more information, see: Add a Hard Disk to a Virtual Machine in the vSphere Client.
By default, the virtual machine uses the host network settings. Hence, there is no configuration required for Virtual Machine (VM) adapters on ESXi. If you have both public and private networks connected to the host and want the virtual machine to access to both the networks, then you must configure the VM adapters in the vSphere Client.
For more information, see: Configuring Networking for Host Machines in the vSphere Web Client.
After configuring the virtual appliance, you should treat it like a physical Cisco MSE appliance. Do not deploy a new OVA every time you upgrade to the latest MSE release, instead, you can download the appropriate installer image onto the appliance and follow the steps given for upgrading the physical appliance.
You can upgrade to 10.1, which will be the Cisco supported version of CMX by either:
1. Complete reinstallation of the new OVA.
2. Contact your local SE or Account team and get an RPM and procedure to upgrade from existing 10.0 to 10.1.