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 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.
Diagnostics Menu ================== Options: 1) Collect basic diagnostics 2) Collect inframgr thread dump and heap dump 3) Collect full diagnostics 4) Exit
| ||
Step 2 | If you choose Collect basic diagnostics option, a response similar to the following appears:
Type in option# : 1 Collecting basic diagnostics................ done Creating diagnostics archive /opt/infra/diags/standalone_diags_basic_12-19-2017-05-25-39.tgz.... done Press return to continue ... | ||
Step 3 | If you choose Collect inframgr thread dump and heap dump option, a response similar to the following appears:
Type in option# : 2 Pre-requisites: 1. Download JDK installer jdk-8u131-linux-x64.tar.gz from oracle.com JDK arvhive. 2. Copy the jdk-8u131-linux-x64.tar.gz under /opt/bin. 3. Install the JDK by running the following commands. cd /opt/bin tar -xzvf jdk-8u131-linux-x64.tar.gz Enter JDK path if it's already installed (e.g. /opt/bin/jdk1.8.0_131): /root/jdk1.8.0_131/ Collecting infradump diagnostics. This operation may take several minutes to complete. ........ done Creating diagnostics archive /opt/infra/diags/standalone_diags_infradump_12-19-2017-04-58-13.tgz......................................................... done Press return to continue ... | ||
Step 4 | If you choose Collect full diagnostics option, a response similar to the following appears:
Type in option# : 3 Pre-requisites: 1. Download JDK installer jdk-8u131-linux-x64.tar.gz from oracle.com JDK arvhive. 2. Copy the jdk-8u131-linux-x64.tar.gz under /opt/bin. 3. Install the JDK by running the following commands. cd /opt/bin tar -xzvf jdk-8u131-linux-x64.tar.gz Enter JDK path if it's already installed (e.g. /opt/bin/jdk1.8.0_131): /root/jdk1.8.0_131/ Collecting full diagnostics. This operation may take several minutes to complete. ....................... Creating diagnostics archive /opt/infra/diags/standalone_diags_full_12-19-2017-05-00-38.tgz........................................................... done Press return to continue ...
|
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.
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
HTTP/HTTPS option and press
Enter.
HTTPS is currently enabled. Do you want to enable HTTP [y/n]? : |
Step 2 | Enter
y and press
Enter.
The following information is displayed: UCS Director Services need to be stopped to proceed with the HTTP configuration. Do you want to continue [y/n]? |
Step 3 | Enter y and press Enter. The Cisco services are restarted. |
Step 1 | From the
Cisco UCS Director
Shell menu, choose the
Reset
MYSQL User password option and press
Enter.
The following
information is displayed:
This utility will restart the services after changing MYSQL user password, do you want to continue? [y/n]:
| ||||
Step 2 | Enter
y and press
Enter.
The following information is displayed: Stopping the infra services... The infra services are stopped. Do you want to change the password for MYSQL 'admin' user? [y/n]: | ||||
Step 3 | Enter
y and press
Enter.
The following
information is displayed:
Current Password (Type in current password or press enter key to use password from the existing credentials file): This option is applicable only for the primary and service nodes in a multi-node setup. | ||||
Step 4 | Enter
y and press
Enter.
The following
information is displayed:
Do you want to generate random password for MYSQL 'admin' user? [y/n]: | ||||
Step 5 | Enter
n and press
Enter.
The following
information is displayed:
Specify the new password for MYSQL 'admin' user: | ||||
Step 6 | Enter a new MYSQL admin password and press Enter. | ||||
Step 7 | Enter your new
MYSQL admin password and press
Enter.
The following
information is displayed:
MYSQL user password is updated. Checking if the database is running...yes. Stopping the database... The database is stopped. Starting the database... The database is started. Copying credential files to BMA appliance... Trying to get session to xxx.xxx.xxx.xxx .... Trying to connect... Successfully connected Uloaded file:/opt/certs/mysql/dbkeys.key Trying to get session to xxx.xxx.xxx.xxx... Trying to connect... Successfully connected Uploaded file:/opt/certs/mysql/dbcreds.properties Starting the infra services... Press return to continue...
|
Step 1 | From the Cisco UCS Director Shell menu, choose the Reset MYSQL User password option and press Enter. The following information is displayed: This utility will restart the services after changing MYSQL user password, do you want to continue? [y/n]: | ||
Step 2 | Enter y and press Enter. The following information is displayed: Stopping the infra services... The infra services are stopped. Do you want to change the password for MYSQL 'admin' user? [y/n]: | ||
Step 3 | Enter y and press Enter. The following information is displayed: Do you want to generate random password for MySQL 'admin' user? [y/n]: | ||
Step 4 | Enter y and press Enter. The following information is displayed: Generating Random Password....... done Do you want to change the password for MySQL 'root' user? [y/n]: | ||
Step 5 | If you entered n, enter the new password for MySQL admin user and press Enter. The following information is displayed: Specify the new password for MySQL 'admin' user: Confirm the new password for MySQL 'admin' user: Password update takes few minutes. Please wait..... done | ||
Step 6 | Enter y and press Enter. The following information is displayed: Do you want to generate random password for MySQL 'root' user? [y/n]: | ||
Step 7 | Enter y and press Enter. The following information is displayed: Generating Random Password....... done MySQL user password is updated. Checking if the database is running... yes. Stopping the database... ............. The database is stopped. Starting the database... Checking if MySQL database is running... .UP The database is started. Starting the infra services... | ||
Step 8 | If you entered n, enter the new password for MySQL root user and press Enter. The following information is displayed: Specify the new password for MySQL 'root' user: Confirm the new password for MySQL 'root' user: Password update takes few minutes. Please wait..................... done MySQL user password is updated. Checking if the database is running... yes. Stopping the database... .. The database is stopped. Starting the database... Checking if MySQL database is running... UP The database is started. Starting the infra services...
|