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.
| Step 1 |
Edit the /opt/infra/dbMonitoringBackupRestore.sh script using vi. |
| Step 2 |
Remove the CHARGEBACK_HISTORY_ENTRY table name from the script. |
You can ping a hostname or IP address to test your connectivity by choosing the Ping Hostname/IP address option.
| Step 1 |
From the Cisco UCS Director Shell menu, choose the Ping Hostname/IP address option and press Enter. |
| Step 2 |
Enter your IP address and press Enter. |
| Step 3 |
Press Enter to exit out of the operation. |
| Step 1 |
From the Cisco UCS Director Shell menu, choose the Tail Inframgr Logs option and press Enter. |
| Step 2 |
To exit from the log file display, type Ctrl+C, then press Enter. |
| Step 1 |
From the Cisco UCS Director Shell menu, choose the Clean-up Patch Files option and press the Enter key. |
| Step 2 |
Enter y and press Enter to delete the patch files. The following information is displayed: |
| Step 3 |
Choose the required option to delete the patch file or directory and press Enter. The following information is displayed: |
| Step 4 |
If you are prompted to confirm that you want to delete the patch file or directory, enter y and then press Enter. The following information is displayed: |
| Step 5 |
Press the Enter key to return to the main menu. |
The Collect Logs from a Node option lets you collect logs from the local node or from a remote node.
| Step 1 |
From the Cisco UCS Director Shell menu, choose Collect Logs from a Node Status and press Enter. |
||
| Step 2 |
Enter the logs collection option and press Enter.
|
The Collect Diagnostics option helps to collect logs from a Multi-Node setup and a Standalone setup for debugging purposes.
| Step 1 |
From the Cisco UCS Director Shell menu, choose Collect Diagnostics.
|
||
| Step 2 |
If you choose Collect essential diagnostics option, a response similar to the following appears: |
||
| Step 3 |
If you choose Collect basic diagnostics option, a response similar to the following appears: |
||
| Step 4 |
If you choose Collect full diagnostics option, a response similar to the following appears: |
||
| Step 5 |
Enter the JDK path and press Enter. The following information is displayed.: |
||
| Step 6 |
If you choose Collect inframgr thread dump option, a response similar to the following appears: |
||
| Step 7 |
Enter the JDK path and press Enter. The following information is displayed.: |
||
| Step 8 |
If you choose Collect inframgr heap dump option, a response similar to the following appears: |
||
| Step 9 |
Enter the JDK path and press Enter. The following information is displayed.: |
||
| Step 10 |
If you choose Display Disk Speed option, a response similar to the following appears:
|
||
| Step 11 |
Enter y and press Enter. The following information is displayed.: |
User or TAC engineer can collect the basic diagnostics data using Collect basic diagnostics option in the shelladmin while reporting any issue. The diagnostics bundle contains the following diagnostics data that is used for troubleshooting the reported issues.
Summary file—Contains important and high level summary.
Diag file—Contains information such as version history with timestamp, average CPU utilization, infra services status, database status, and database size.
SummaryReport file—Contains summary report.
DiagOutput file—Contains detailed report.
UcsdExceptions file—Contains all exceptions found in the inframgr/logfile.txt.* and number of occurrences of each exception.
infra-env Directory—Contains the infra services configuration (<service>.env) files.
commands Directory—Contains the output of various system commands.
var-log-ucsd zip file—Contains the log files such as install.log, bootup.log, and services.log.
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.
|
In the Cisco UCS Director VM prompt after the VM is powered on, press Alt-F1. The VMware console screen is refreshed. |
By default, HTTPS access mode is enabled during initial OVF installation and Cisco UCS Director upgrade. When HTTP is enabled, you can log in to Cisco UCS Director, using both HTTP and HTTPS modes. When HTTPS is enabled, you can log in to the Cisco UCS Director only using HTTPS mode. Even when you try to log in to Cisco UCS Director using HTTP mode, you will be redirected to HTTPS user interface only.
| Step 1 |
From the Cisco UCS Director Shell menu, choose the Enable/Disable HTTP option and press Enter. |
| Step 2 |
Enter y and press Enter. |
| Step 3 |
Enter y and press Enter. The Cisco services are restarted. |
| Step 1 |
From the Cisco UCS Director Shell menu, choose the Reset MariaDB User password option and press Enter.
|
||||
| Step 2 |
Enter y and press Enter. |
||||
| Step 3 |
Enter y and press Enter. This option is applicable only for the primary and service nodes in a multi-node setup. |
||||
| Step 4 |
Enter y and press Enter. |
||||
| Step 5 |
Enter n and press Enter. |
||||
| Step 6 |
Enter a new MariaDB admin password and press Enter.
|
||||
| Step 7 |
Enter your new MariaDB admin password and press Enter.
|
| Step 1 |
From the Cisco UCS Director Shell menu, choose the Reset MariaDB User password option and press Enter. |
||||
| Step 2 |
Enter y and press Enter. |
||||
| Step 3 |
Enter y and press Enter. |
||||
| Step 4 |
Enter y and press Enter. |
||||
| Step 5 |
If you entered n, enter the new password for MariaDB admin user and press Enter.
|
||||
| Step 6 |
Enter y and press Enter. |
||||
| Step 7 |
Enter y and press Enter. |
||||
| Step 8 |
If you entered n, enter the new password for MariaDB root user and press Enter.
|
| Step 1 |
From the Cisco UCS Director Shell menu, choose Configure Network Interface and press Enter.
|
||||
| Step 2 |
Enter y to assign a new, unique, and unclaimed device ID to the cloned Cisco UCS Director, and press Enter. The following information is displayed.
|
Feedback