Cisco UCS C-Series Troubleshooting Tips
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Server
  5. UCS C Series
  6. Troubleshooting tips

Cisco UCS C-Series Troubleshooting Tips

Hide thumbs Also See for UCS C-Series:
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual
UCS C−Series Servers Troubleshooting Tips
Document ID: 111508
Contents
Introduction
Prerequisites
Requirements
Conventions
Introduction
The Cisco Integrated Management Controller (CIMC) is the management service for the UCS C−Series
server. CIMC runs within the server.
You can use a web−based GUI or SSH−based CLI to access, configure, administer, and monitor the server.
Almost all tasks can be performed in either interface. The results of tasks performed in one interface are
automatically displayed in another.
This document provides some CIMC troubleshooting tips and common troubleshooting scenarios for UCS
C−Series servers.
Prerequisites
Requirements
Cisco recommends that you:
•
Have a working knowledge of the Cisco UCS C−Series Server Blade hardware and software
administration.
•
Be familiar with UCS C−Series Servers Cisco Integrated Management Controller.
•
Understand the impact and implications of the different commands described in this document.
•
Be familiar with the UCS components and topology.

Advertisement

Table of Contents
loading

Related Manuals for Cisco UCS C-Series

Summary of Contents for Cisco UCS C-Series

  • Page 1: Table Of Contents

    Related Information Introduction The Cisco Integrated Management Controller (CIMC) is the management service for the UCS C−Series server. CIMC runs within the server. You can use a web−based GUI or SSH−based CLI to access, configure, administer, and monitor the server.

  • Page 2: Components Used

    Common troubleshooting tips on C−Series servers are provided in this section. Obtaining Showtech Support to TAC Perform this task when requested by the Cisco Technical Assistance Center (TAC). This utility creates a summary report containing configuration information, logs, and diagnostic data that will help TAC in troubleshooting and resolving a technical issue.
  • Page 3 When you enter this name, include the relative path for the file from the top of the TFTP tree to the desired location. Click Export. And via the CLI command: Generate show techsupport Generate show techsupport then provide the generated report file to Cisco TAC. SanDiego# scope cimc SanDiego /cimc # scope firmware network...

  • Page 4: Display Of System Event Log Events

    (Optional) Click <Newer and Older> to move backward and forward through the pages of system events, or click <<Newest to move to the top of the list. By default, the newest system events are displayed at the top if the list. Cisco CIMC.

  • Page 5: Display Of Sensor Readings

    Display of Sensor Readings Complete these steps in order to display the sensor readings: In the Navigation pane, click the Server tab. From the Server tab, click Sensors. View various sensors by clicking the desired sensor. Display of CIMC Log Complete these steps in order to display the CIMC log: In the Navigation pane, click the Admin tab.

  • Page 6: Run Debug Firmware Utility (Cli)

    Run Debug Firmware Utility (CLI) You can run Debug Firmware Utility (CLI) to view realtime CIMC debug status: Access to read−only shell to view realtime CIMC Debug status. CIMC Debug Utilities !−−− enter debug shell rtp−6100−A# SanDiego /cimc # connect debug−shell diags host...
  • Page 7 obfl post power sensors tasks update users version __________________________________________ Notes: "enter Key" will execute last command "COMMAND ?" will execute help for that command __________________________________________ [ help ]# !−−− view how many alarms in realtime [ help ]# alarms StatusLedControl: Setting LED to AMBER −...

  • Page 8: Run Diagnostics (Cli)

    RX packets:42862 errors:0 dropped:0 overruns:0 frame:0 TX packets:26968 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3786646 (3.6 MiB) TX bytes:12311980 (11.7 MiB) Interrupt:1 Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.255.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8137 errors:0 dropped:0 overruns:0 frame:0 TX packets:8137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:877033 (856.4 KiB)

  • Page 9: Common Troubleshooting Scenarios − Power−On Related

    Note: Diagnostics while designed to be safe to a running server should not be run with a load you cannot afford to lose. Please ensure critical server applications are off−line before running diagnostics. Diagnostics (CLI) • To view realtime CIMC Diagnostics status. CIMC Diags Shell !−−−...

  • Page 10: Common Troubleshooting Scenarios − Host Does Not Boot

    Technical Support & Documentation − Cisco Systems Contacts & Feedback | Help | Site Map © 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of Cisco Systems, Inc.
  • Page 11 Updated: Jan 08, 2010 Document ID: 111508...

Table of Contents