Step 1 |
Download the latest available Cisco Crosswork Optimization Engine image file (*.ova) to your system.
Warning
|
The default VMware vCenter deployment timeout is 15 minutes. The total time needed to deploy the OVA image file may take much
longer than 15 minutes, depending on your network speed and other factors. If vCenter times out during deployment, the resulting
VM will be not be bootable. To prevent this, Cisco recommends that you either set the vCenter deployment timeout to a much
longer period (such as one hour), or unTAR the OVA file before continuing and then deploy using the OVA's three separate Open
Virtualization Format and Virtual Machine Disk component files: cw.ovf, cw_rootfs.vmdk, and cw_dockerfs.vmdk.
|
|
Step 2 |
With VMware ESXi running, log in to the VMware vSphere Web Client. On the left side, choose the ESXi host on which you want
to deploy the VM, then select .
|
Step 3 |
The VMware Deploy OVF Template wizard appears and highlights the first step, 1 - Select template. Click Browse to navigate to the location where you downloaded the OVA image file and select it. Once selected, the file name is displayed
in the window.
|
Step 4 |
Click Next to go to 2 - Select a name and folder. Enter a name for the Cisco Crosswork Optimization Engine VM you are creating.
Cisco recommends that you include the Cisco Crosswork Optimization Engine version and build number in the name (for example: CW_COE-1.2.1_400).
|
Step 5 |
Click Next to go to 3 - Select a compute resource. Choose the VM’s host.
|
Step 6 |
Click Next. The VMware vCenter Server validates the OVA. Network speed will determine how long validation takes. When validation is
complete, the wizard moves to 4 - Review details. Take a moment to review the OVF template you are deploying. Note that this information is gathered from the OVF and cannot
be modified.
|
Step 7 |
Click Next to go to 5 - Accept license agreements. Review the End User License Agreement and click to accept the license agreements before you continue.
|
Step 8 |
Click Next to go to 6 - Configuration. Select the appropriate Network.
|
Step 9 |
Click Next to go to 7 - Select storage. Select the relevant option from the Select virtual disk format drop-down list. From the table, choose the datastore you want to use and review its properties to ensure there is enough
available storage.
Note
|
For production deployment, consider choosing Thick provision eager zeroed as it will not have a penalty of allocating and initializing disk space at runtime. For demo or testing purposes, Thin provision is recommended as it saves disk space.
|
|
Step 10 |
Click Next to go to 8 - Select networks. From the table, choose the appropriate destination network for the source Data Network and Management Network, respectively.
|
Step 11 |
Click Next to go to 9 - Customize template. Typically, the Crosswork Configuration settings are expanded by default. Make an entry in the Disclaimer field. The entry will be displayed when a user launches Cisco Crosswork Optimization Engine.
|
Step 12 |
Expand the Management Network settings. Enter the temporary IP address you want to be associated with the VM during the upgrade.
|
Step 13 |
Expand the Data Network settings. According to your deployment configuration, the fields displayed are different. Enter a temporary IP address and
other information for the data network.
|
Step 14 |
Expand the Deployment Type settings, select Upgrade, and make relevant entries for the following fields:
-
Original VM Management IPv4 Address: Management IPv4 address of Cisco Crosswork Optimization Engine 1.1 VM.
-
Original VM Password: Provide theCisco Crosswork Optimization Engine 1.1 VM password in the Enter Password and Confirm Password fields.
-
Original VM Username: Username of the Cisco Crosswork Optimization Engine 1.1 VM. Typically, it is cw-admin unless it has been changed by your system administrator.
Note
|
Switching the Management or Data IPv4 address is not supported during upgrade owing to restrictions in Cisco Crosswork Optimization Engine and Cisco Crosswork Data Gateway certificates.
|
|
Step 15 |
Expand the DNS and NTP Servers settings, as shown in the following figure. According to your deployment configuration, the fields displayed are different.
Make entries in three fields:
-
DNS IP Address: The IP addresses of the DNS servers you want the Cisco Crosswork Optimization Engine server to use. Separate multiple IP addresses with spaces.
-
DNS Search Domain: The name of the DNS search domain.
-
NTP Servers: The IP addresses or host names of the NTP servers you want to use. Separate multiple IPs or host names with spaces.
|
Step 16 |
Disk Configuration settings allows you to adjust the amount of storage space available to Cisco Crosswork Optimization Engine. The default settings should work for most environments. For assistance in adding additional storage, contact the Cisco Customer
Experience team.
|
Step 17 |
Expand the Crosswork Collection Configuration settings. Check this option if you plan to use Cisco NSO. For more guidance and information on which mode to select, see
Collection Considerations.
|
Step 18 |
Click Next to go to 10 - Ready to Complete, as shown in the following figure. Review your settings and then click Finish if you are ready to begin deployment.
|
Step 19 |
Wait for the deployment to finish before continuing. To check on the deployment
status:
-
Open a VMware vCenter client.
-
In the Recent Tasks tab for the host VM, view the
status for the Deploy OVF template and
Import OVF package jobs, as shown in the
following figure.
|
Step 20 |
After the deployment tasks are complete, check the host's VM settings to permit
boot from EFI Firmware:
-
On the host VM Summary tab, below the
VM Hardware table, click Edit
Settings, as shown in the following figure.
-
On the Edit Settings page, click the
VM Options tab.
-
Expand the Boot Options dropdown list and change
the Firmware setting to
EFI, if it not set by default. When you are
finished, click OK. You may want to take a
snapshot of the VM at this point.
|
Step 21 |
You can now power on the Cisco Crosswork Optimization Engine VM to complete the deployment process. Expand the host’s entry so you can click the VM and then choose .
From this point, the upgrade is automatically triggered. The Data and IP configurations are transferred from Cisco Crosswork Optimization Engine 1.1 to Crosswork Optimization Engine 1.2.1. Once the transfer is completed, Cisco Crosswork Optimization Engine 1.1 VM shuts down. It will take 30 minutes or more for the Crosswork Optimization Engine 1.2.1 VM to become operational. Please wait for the process to finish before continuing.
To get the current status of the upgrade, login as the super user and use the CLI upgrade status command on the VM.
Note
|
Each time the Cisco Crosswork Optimization Engine VM is re-imaged, you need to refresh the Cisco Crosswork Optimization Engine login page to accept the new certificate. Otherwise, the error message Http failure response for /crosswork/sso/v1/tickets: 0 Unknown Error is displayed on the login page.
|
|
Step 22 |
Move on to the next steps as documented in the Upgrade Workflow:
|