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.
This chapter contains the following sections:
Step 1 | Log into the Hyper-V host. | ||
Step 2 | Choose Hyper-V Manager. to open | ||
Step 3 | In the Hyper-V Manager dialog box, choose . | ||
Step 4 | In the Before You Begin pane, click Next. | ||
Step 5 | In the Name and Location pane, in the Name field, edit the VM name. | ||
Step 6 | In the Name and Location pane, check the Store the virtual machine in a different location checkbox and specify the alternate location. | ||
Step 7 | Click Next. | ||
Step 8 | In the
Select
Generation pane, choose
Generation1.
With Generation1, this virtual machine provides the same virtual hardware to the virtual machine as in previous versions of Hyper-V. | ||
Step 9 | In the Assign Memory pane, enter the amount of memory to allocate to this VM (12 GB minimum) and click Next. | ||
Step 10 | In the Configure Networking pane, in the Connection field, accept the default option Not Connected by clicking Next. | ||
Step 11 | In the Connect Virtual Hard Disk pane, choose Attach a virtual disk later and click Next. | ||
Step 12 | In the Completing the New Virtual Machine Wizard pane, verify the settings and click Finish. | ||
Step 13 | In the Navigation pane, right-click the new VM and choose Settings. | ||
Step 14 | In the Navigation pane, choose IDE Controller 0. | ||
Step 15 | In the IDE Controller pane, choose Hard Drive and click Add. | ||
Step 16 | In the Hard Drive pane, choose the downloaded Cisco UCS Director .vhd file and click OK. | ||
Step 17 | Inspect the virtual hard drive properties. | ||
Step 18 | In the Navigation pane, choose Memory. | ||
Step 19 | In the Memory pane, enter the recommended value (minimum 12 GB). | ||
Step 20 | In the Navigation pane, choose Processor. | ||
Step 21 | In the Processor pane, enter the recommended value (4 vCPU). | ||
Step 22 | Remove the network adapter that was created when you created the new VM. | ||
Step 23 | In the Navigation pane, choose Add Hardware. | ||
Step 24 | In the Add Hardware pane, choose Network Adapter and click OK. | ||
Step 25 | In the Navigation pane, choose the network adapter. | ||
Step 26 | In the Network Adapter pane, in the Network field, choose your network and click OK. | ||
Step 27 | Verify that you have sufficient vCPU and Memory resources allocated. For the minimum resource requirements, see Minimum System Requirements for a Single Node Setup. | ||
Step 28 | Power on the VM.
Optionally you can configure network properties from the shelladmin. By default, this version of Microsoft Hyper-V uses DHCP by default. If you want to use a static IP address instead of DHCP, you can change this configuration through the shelladmin. | ||
Step 29 | After the appliance has booted up, copy and paste the Cisco UCS Director IP address that is displayed into a supported web browser to access the Login page. | ||
Step 30 | At the login
prompt, enter
admin for username and
admin for the password to log into
Cisco
UCS Director.
|
Update your license.
This procedure is optional.
Change the default password for administration after initial logging.
If you received a zipped license file by an email, extract and save the license (.lic) file to your local machine.
The default maximum packet (query) size for the Cisco UCS Director database queries is 4 MB. If one or more of your pods requires a larger size, we recommend that you increase the configuration of the maximum packet size to 100 MB. For example, the import of large open automation modules typically requires a larger packet size.
Note | For a multi-node setup, perform this configuration on the inventory database and monitoring database nodes. |