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:
Problem—The primary node fails.
Possible Cause—A primary node failure may be caused by file system corruption on an external datastore on which the Cisco UCS Director VM is running.
Recommended Solution— Promote a service node to the primary node.
Problem—The master monitoring database fails.
Possible Cause—Database failures may be caused by:
A mysqld crash, which may occur if the VM is powered off abruptly.
A power failure on the node on which the Cisco UCS Director VM is running.
File system corruption on an external datastore on which the Cisco UCS Director VM is running.
Recommended Solution—Fail over the database by stopping the infrastructure services on the primary node and the service node, replacing the IP address of the master monitoring VM with that of the backup monitoring VM, and restarting services.
Problem—The master inventory database fails.
Possible Cause—Database failures may be caused by:
A mysqld crash, which may occur if the VM is powered off abruptly.
A power failure on the node on which the Cisco UCS Director VM is running.
File system corruption on an external datastore on which the Cisco UCS Director VM is running.
Recommended Solution—For a multi-node setup, fail over the database by stopping the infrastructure services on the primary node and the service node, replacing the IP address of the master inventory VM with that of the backup inventory VM, and restarting services.
Note | This solution is only applicable for a multi-node setup, and if you have a backup of the corrupted database node. |
For a single-node setup, deploy a new Cisco UCS Director appliance and restore the database backup using the shelladmin.
Problem—In a Cisco UCS Director multi-node deployment you may experience performance issues when using a service node to perform inventory collection.
Possible Cause—The execution duration can be directly affected by the following factors:
Poor disk I/O speed on the external datastore on which the Cisco UCS Director VM is deployed.
Poor network latency in a multi-node setup.
Insufficient CPU reservation in the hypervisor.
Insufficient memory reservation in the hypervisor.
Recommended Solution—Cisco recommends that you deploy Cisco UCS Director VMs in either a local datastore with 25Mbps I/O speed, or an external datastore with 50Mbps I/O speed. Cisco recommends that you reserve at least 3000MHz CPU for the Cisco UCS Director VM in addition to the default number of vCPUs. To troubleshoot any inventory collection performance issues, determine the I/O speed for the local datastore or the external datastore, and determine the round-trip time (RTT) between the following nodes: