|
Note that one Commissioning VM can be used to deploy multiple node types. Thus, this step only needs to be performed once for all node types. |
|
The supported version of the Commissioning VM is version 1.16.3. Prior versions cannot be used. |
Planning for the procedure
Background knowledge
This procedure assumes that:
-
you are using a supported VMware version, as described in the 'Hardware Requirements' section of the Commissioning VM Documentation
-
you are installing into an existing VMware deployment which has pre-configured networks and VLANs; this procedure does not cover setting up a VMware deployment from scratch.
-
you know the IP networking information (IP address, subnet mask in CIDR notation, and default gateway) for the Commissioning VM.
Reserve maintenance period
This procedure does not require a maintenance period. However if you are integrating into a live network then it is recommended to implement measures to mitigate any unforeseen events.
Tools and access
You must have access to a local computer (referred to in this procedure as the local computer) with a network connection and the VMware vSphere Client Integration Plug-in installed. You can use various versions of VMware vSphere, including V5.5 through to V6.7.
For more information on installing the VMware vSphere Client Integration Plug-in, see the VMware documentation.
This document references an external document: the Commissioning VM Documentation. Ensure you have a copy available before proceeding.
Installation Questions
| Question | More information |
|---|---|
Do you have the correct Commissioning VM OVA? |
All Commissioning VM virtual appliances use the naming convention - |
Do you know the IP address that you intend to give to the Commissioning VM? |
The Commissioning VM requires one IP address, for management traffic. |
Method of procedure
Deploy and configure the Commissioning VM
Follow the Commissioning VM Documentation on how to deploy the Commissioning VM and set up the initial configuration.
