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—You are unable to back up the monitoring database in a multi-node setup.
Recommended Solution—Edit the dbMonitoringBackupRestore.sh script.
You can ping a hostname or IP address to test your connectivity by choosing the Ping Hostname/IP address option.
The Collect Logs from a Node option lets you collect logs from the local node or from a remote node.
The Collect Diagnostics option generates a Summary Report (SummaryReport.txt) and a detail report (DiagOutput.txt) and stores these files under /opt/diagnostics.
SELECT> 27 *************** Diagnostic Tool *************** Please find the below files under /opt/diagnostics : Summary Report: SummaryReport.txt Diagnostics report: DiagOutput.txt /opt/diagnostics/rules Press return to continue... |
Problem—The VMware console does not display after an abrupt shutdown of the Cisco UCS Director VM from VMware vCenter.
Possible Cause—Occasionally after Cisco UCS Director VM is powered on, the VMware console prompt gets stuck after the process restart and does not return to the shelladmin.
Recommended Solution—After the VM is powered on, press Alt-F1 to refresh the VMware console.
The VMware console screen is refreshed. |