Troubleshooting

This chapter contains the following sections:

Backing up the Monitoring Database in a Multi-Node Setup

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.

    Pinging the Hostname and IP Address

    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.
      The following information is displayed: 
       Enter IP Address : 209.165.200.224
PING 209.165.200.224 (209.165.200.224) 56(84) bytes of data.
64 bytes from 209.165.200.224: icmp_seq=1 ttl=64 time=9.90 ms
64 bytes from 209.165.200.224: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 209.165.200.224: icmp_seq=3 ttl=64 time=0.254 ms
64 bytes from 209.165.200.224: icmp_seq=4 ttl=64 time=0.198 ms
64 bytes from 209.165.200.224: icmp_seq=5 ttl=64 time=0.267 ms

--- 209.165.200.224 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.198/2.187/9.901/3.857 ms
Press return to continue ...
      Step 3   Press Enter to exit out of the operation.

      Viewing Tail Inframgr Logs

      This Shell lets enables you to see inframgr (Infrastructure Manager) log data, which are generated behind the scenes by use of the Unix tail command. When you are debugging, you can trace problems by using this log data. You use the Tail Inframgr Logs option to immediately tail the most recent inframgr logs. The results are displayed on your screen directly after you select this option.
        Step 1   From the Cisco UCS Director Shell menu, choose the Tail Inframgr Logs option and press Enter.
        Following are a few sample lines, typical of the results displayed immediately after use of the Tail Inframgr Logs option: 
          
2014-07-20 23:17:43,500 [pool-23-thread-17] 
INFO  getBestAgent(SystemTaskExecutor.java:308) 
- No Agent available for remoting SnapMirrorHistoryStatusSchedulerTask
2014-07-20 23:17:43,502 [pool-23-thread-17] 
INFO  updateStatus(SystemTaskStatusProvider.java:181) 
- Task: task.SnapMirrorHistoryStatusSchedulerTask changed state to OK
2014-07-20 23:17:43,562 [pool-23-thread-17] 
INFO  executeLocally(SystemTaskExecutor.java:133) 
- Executing task locally: SnapMirrorHistoryStatusSchedulerTask
2014-07-20 23:17:43,562 [pool-23-thread-17] 
INFO  getClusterLeaf(ClusterPersistenceUtil.java:81) 
- Leaf name LocalHost
2014-07-20 23:17:43,571 [pool-23-thread-17]
        Step 2   To exit from the log file display, type Ctrl+C, then press Enter.

        Collecting Logs from a Node

        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 the Collect Logs from a Node Status option.
          The following list of services appears: 
                   Cisco UCS Director Shell Menu
Node:Standalone | Version:6.0.0.0 | UpTime:  19:57:52 up 2 days, 14:23

1) Change ShellAdmin password
2) Display Services Status
3) Stop Services
4) Start Services
5) Stop Database
6) Start Database
7) Backup Database
8) Restore Database
9) Time Sync
10) Ping Hostname/IP Address
11) Show version
12) Generate Self-Signed Certificate and Certificate Signing Request
13) Import CA/Self-Signed Certificate
14) Configure Network Interface
15) Display Network Details
16) Enable Database for Cisco UCS Director Baremetal Agent
17) Add Cisco UCS Director Baremetal Agent Hostname/IP
18) Tail Inframgr logs
19) Apply Patch
20) Shutdown Appliance
21) Reboot Appliance
22) Manage Root Access
23) Login as Root
24) Configure Multi Node Setup (Advanced Deployment)
25) Clean-up Patch Files
26) Collect logs from a Node
27) Collect Diagnostics
28) Quit

SELECT>
          Step 2   Enter the Logs Collection option.

          • If you choose to collect logs from the current node, a response similar to the following appears: 

            Collecting all feature logs....
==========================================================
                   Collection of Logs
==========================================================
Moving logs from /opt/infra/broker to common/logs
Moving logs from /opt/infra/client to common/logs
Moving logs from /opt/infra/controller to common/logs
Moving logs from /opt/infra/eventmgr to common/logs
Moving logs from /opt/infra/idaccessmgr to common/logs
Moving logs from /opt/infra/inframgr to common/logs
Moving logs from /opt/infra/web_cloudmgr to common/logs

Logs archive path:  /opt/infra/common/logs-07-31-2014-08-36-48.tar
You can also view individual feature logs under /opt/infra/common/logs

Logs collection done for current node
Do you want to collect logs from another node?  [y/n]: Collect Logs from a Node
            Note   

            To collect logs from another node, the best practice is to return to the Shell menu, select the Collect Logs from a Node option again, and choose the Remote Node option.

          • If you choose to collect logs from a remote node, a response similar to the following appears: 

            Please enter the remote server IP/Hostname from where we collect logs:

            Follow the onscreen instructions to provide the address of the remote log, establish a secure connection, and provide the required login credentials for that remote node.

          Collecting Diagnostics

          The Collect Diagnostics option generates a Summary Report (SummaryReport.txt) and a detail report (DiagOutput.txt) and stores these files under /opt/diagnostics.

          From the Cisco UCS Director Shell menu, choose Collect Diagnostics.
          Information similar to the following appears, advising you that the diagnostic files have been created: 
                 
              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...

          Troubleshooting VMware Console Display Issues

          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.