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:
Note | We recommend that you use VMware vCenter for OVF deployment. VMware vCenter versions 5.x and above are supported. OVF deployment wizards support only IPv4 addresses. If you require IPv6, you can deploy OVF and use the shelladmin option to configure IPv6 address. |
You need administrator privileges to connect to VMware vCenter. Cisco UCS Director requires a user account with system administrator privileges to discover, manage and automate VMware vCenter configuration from Cisco UCS Director. These operations include creating, deleting and modifying VMs, ESXi hosts and clusters, datastores and datastore clusters, standard and DV switches, and virtual network port groups.
Note | If you do not want to use DHCP, you need the following information: IPv4 address, subnet mask, and default gateway. |
This procedure is optional.
Step 1 | Log in to the
Cisco
UCS Director
VM console with the following credentials:
If you have already logged into the shelladmin and changed the default password, use your new password instead. After you have logged in, you can choose Change shelladmin password to change the default password. |
Step 2 | Choose Configure Network Interface. |
Step 3 | At the
Do
you want to Configure DHCP/STATIC IP [D/S] prompt, enter one of
the following choices:
|
Step 4 | Confirm when prompted. |
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.
For optimal performance, we recommend reserving extra system resources for Cisco UCS Director beyond the minimum system requirements listed in Minimum System Requirements for a Single-Node Setup.
Note | For more information about how to reserve system resources, see the VMWare documentation. |
Step 1 | Log in to VMware vCenter. |
Step 2 | Choose the VM for Cisco UCS Director. |
Step 3 | Shut down the VM. |
Step 4 | In VMware vCenter, click the Resource Allocation tab to view the current resource allocations, and click Edit. |
Step 5 | In the Virtual Machine Properties pane, edit resource allocations by choosing a resource and entering the new values. |
Step 6 | Verify that the new resource allocations have been made. |
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. |
Step 1 | In the shelladmin, choose Login as Root to log in to Cisco UCS Director. |
Step 2 | Navigate to the /etc folder. |
Step 3 | Open the my.cnf file and locate the max_allowed_packet parameter. |
Step 4 | Change the value of the max_allowed_packet parameter to max_allowed_packet=100M |
Step 5 | Save the my.cnf file. |
Step 6 | In the shelladmin, stop and restart the Cisco UCS Director services on every node, as follows: |