Step 1 |
Choose the host on which to deploy the Cisco VSG VM. |
Step 2 |
Choose . |
Step 3 |
In the Deploy OVF Template—Source window, do the following:
-
Browse to the path to the Cisco VSG OVA file in the Deploy from a file or URL field.
-
Click Next.
|
Step 4 |
In the Deploy OVF Template—OVF Template Details window, review the product information including the size of the file and the VM disk. |
Step 5 |
Click Next. |
Step 6 |
In the Deploy OVF Template—End User License Agreement window, do the following:
-
Review the end user license agreement and click Accept.
-
Click Next. The Name and Location window opens.
|
Step 7 |
In the Deploy OVF Template—Name and Location window, do the following:
-
In the Name field, enter a name for the Cisco VSG that is unique within the inventory folder and has up to 80 characters.
-
In the Inventory Location pane, choose the location that you would like to use for hosting the Cisco VSG.
-
Click Next. The Deployment Configuration window opens.
Figure 12. Deploy OVF Template—Deployment Configuration Window
q
|
Step 8 |
In the Deploy OVF Template—Deployment Configuration window, do the following:
-
From the Configuration drop-down list, choose Deploy Nexus 1000V as Standalone.
-
Click Next. The Datastore window opens.
|
Step 9 |
In the Deploy OVF Template—Datastore window, choose the data store for the VM and click Next. The Disk Format window opens. The storage can be local or shared remote such as the network file storage (NFS) or the storage area network (SAN).
Note |
If only one storage location is available for an ESX host, this window does not display and you are assigned to the one that is available. |
|
Step 10 |
In the Deploy OVF Template—Disk Format window, do the following:
-
Click either Thin provisioned format or Thick provisioned format to store the VM vdisks.
-
Click Next. The Network Mapping window opens.
The default is thick provisioned. If you do not want to allocate the storage immediately, use thin provisioned. Ignore the red text in the window.
Figure 13. Deploy OVF Template—Network Mapping
|
Step 11 |
In the Deploy OVF Template—Network Mapping window, do the following:
-
Choose VSG Data for the data interface port profile.
-
Choose Management for the management interface port profile.
-
Choose VSG-ha for the HA interface port profile .
-
Click Next. The Properties window opens.
Note |
In this example, for Cisco VSG-Data and Cisco VSG-ha port profiles created in the previous task, the management port profile is used for management connectivity and is the same as in the VSM and Cisco VNMC. |
Figure 14. Deploy OVF Template—Properties Window
|
Step 12 |
In the Deploy OVF Template—Properties window, do the following:
-
In the HaId field, enter the high-availability identification number for a Cisco VSG pair (value from 1 through 4095).
-
In the Password field, enter a password that contains at least one uppercase letter, one lowercase letter, and one number.
-
In the ManagementIpV4 field, enter the IP address for the Cisco VSG.
-
In the ManagementIpV4 Subnet field, enter the subnet mask.
-
In the Gateway field, enter the gateway name.
-
In the VnmcIpV4 field, enter the IP address of the Cisco VNMC.
-
In the SharedSecret field, enter the shared secret password defined during the Cisco VNMC installation.
-
In the ImageName field, enter the VSG VNM-PA image name (vnmc-vsgpa.2.0.1a.bin).
Note |
Follow these parameters for choosing the
shared secret password:
-
The password must be more than eight characters.
-
Characters not supported for the shared secret password: & ' " ` ( )< >| \ characters and all other characters supported on the keyboard.
-
The password should contain lowercase letters, uppercase letters, digits, and special characters.
-
The password should not contain characters, repeated three or more times consecutively.
-
The new shared secret passwords should not repeat or reverse the username
-
The password should not be cisco, ocsic, or any variant obtained by changing the capitalization of letters.
-
The password should not be formed by easy permutations of characters present in the username or Cisco.
|
Note |
In the following step, make sure that red text messages do not appear before you click Next. If you do not want to enter valid information in the red-indicated fields, use null values to fill those fields. If those fields are left empty or filled with invalid null values, the application does not power on. Ignore the VNMC Restore fields. |
|
Step 13 |
Click Next. The Ready to Complete window opens. |
Step 14 |
In the Ready to Complete window, review the deployment settings information .
Note |
Review the IP/mask/gateway information carefully because any discrepancies might cause the VM to have bootup issues. |
|
Step 15 |
Click Finish. The Deploying Nexus 1000VSG dialog box opens. The progress bar in the Deploying Nexus 1000VSG dialog box shows how much of the deployment task is completed before the Cisco VNMC is deployed. |
Step 16 |
Wait and click Close after the progress indicator shows that the deployment is completed successfully. |
Step 17 |
From your virtual machines, do one of the following:
-
Right click and choose Edit Settings.
-
Click the Getting Started tab from the menu bar and then click the link Edit Virtual Machine Settings.
The Virtual Machine Properties window opens.
|
Step 18 |
In the Virtual Machine Properties window, do the following:
-
From the CPUs drop-down list, choose the appropriate vCPU number.
For older version of ESXi hosts, you can directly select a number for the vCPUs.
-
From the Number of Virtual Sockets drop down list, choose the appropriate socket with cores.
For the latest version of ESXi hosts, you can directly select a number for the vCPUs.
Choosing 2 CPUs results in a higher performance. |
Step 19 |
Power on the Cisco VSG VM. |