Documente Academic
Documente Profesional
Documente Cultură
c o m
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Preface v
Audience v
Organization v
Related Documentation v
Introduction 1-1
Troubleshooting Information in Cisco UCS Manager GUI 1-1
Faults 1-2
Fault Severities 1-3
Fault States 1-3
Fault Types 1-4
Properties of Faults 1-4
Lifecycle of Faults 1-5
Faults in Cisco UCS Manager GUI 1-5
Faults in Cisco UCS Manager CLI 1-6
Fault Collection Policy 1-6
Fault Documentation 1-6
Events 1-6
Properties of Events 1-7
Events in Cisco UCS Manager GUI 1-7
Events in Cisco UCS Manager CLI 1-7
Core Files 1-7
Core Files in Cisco UCS Manager GUI 1-8
Core Files in Cisco UCS Manager CLI 1-8
Core File Exporter 1-8
Audit Log 1-8
Properties of Audit Log Entries 1-9
Audit Log in Cisco UCS Manager GUI 1-9
Audit Log in Cisco UCS Manager CLI 1-9
System Event Log 1-10
SEL File 1-10
SEL Policy 1-10
Syslog 1-10
Syslog Configuration 1-11
Syslog Location 1-11
Syslog Entry Format 1-11
Syslog Entry Severities 1-11
Syslog Entry Parameters 1-12
Syslog Services 1-13
Overview 8-1
INDEX
Preface
This preface describes the audience and organization of the Cisco UCS Manager Troubleshooting Guide.
It also provides information on how to obtain related documentation.
Audience
This troubleshooting guide is designed for users who are responsible for the following:
• Implementing Cisco UCS instances
• Managing Cisco UCS instances
Organization
This troubleshooting guide is organized into the following chapters:
• Chapter 1, “Introduction”
• Chapter 2, “Finite State Machine”
• Chapter 3, “General Troubleshooting Steps and Solutions”
• Chapter 4, “Troubleshooting Issues with Cisco UCS”
• Chapter 5, “Troubleshooting Cisco UCS Faults”
• Chapter 6, “Troubleshooting SAN Boot and SAN Connectivity Issues”
• Chapter 7, “Troubleshooting Server Hardware Issues”
• Chapter 8, “Cisco UCS Error Messages”
Related Documentation
Roadmaps that list all documentation for Cisco Unified Computing System (Cisco UCS) are available at
the following URL:
http://www.cisco.com/en/US/products/ps10477/products_documentation_roadmaps_list.html
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 1
Introduction
This chapter provides an overview of where to find faults, events, and other information that can help
you troubleshoot issues with Cisco Unified Computing System (Cisco UCS).
This chapter contains the following sections:
• Troubleshooting Information in Cisco UCS Manager GUI, page 1-1
• Troubleshooting Information in Cisco UCS Manager CLI, page 1-2
• Faults, page 1-2
• Events, page 1-6
• Core Files, page 1-7
• Audit Log, page 1-8
• System Event Log, page 1-10
• Syslog, page 1-10
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Faults
In Cisco UCS, a fault is a mutable object that is managed by Cisco UCS Manager. Each fault represents
a failure in the Cisco UCS instance or an alarm threshold that has been raised. During the lifecycle of a
fault, it can change from one state or severity to another.
Each fault includes information about the operational state of the affected object at the time the fault was
raised. If the fault is transitional and the failure is resolved, the object transitions to a functional state.
A fault remains in Cisco UCS Manager until the fault is cleared and deleted according to the settings in
the fault collection policy.
You can view all faults in a Cisco UCS instance from either Cisco UCS Manager CLI or Cisco UCS
Manager GUI. You can also configure the fault collection policy to determine how a Cisco UCS instance
collects and retains faults.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Fault Severities
A fault raised in a Cisco UCS instance can transition through more than one severity during its lifecycle.
Table 1-1 describes the fault severities that you may encounter.
Severity Description
Critical A service-affecting condition that requires immediate corrective
action. For example, this severity could indicate that the managed
object is out of service and its capability must be restored.
Major A service-affecting condition that requires urgent corrective action.
For example, this severity could indicate a severe degradation in the
capability of the managed object and that its full capability must be
restored.
Minor A nonservice-affecting fault condition that requires corrective
action to prevent a more serious fault from occurring. For example,
this severity could indicate that the detected alarm condition is not
degrading the capacity of the managed object.
Warning A potential or impending service-affecting fault that has no
significant effects in the system. Action should be taken to further
diagnose, if necessary, and correct the problem to prevent it from
becoming a more serious service-affecting fault.
Condition An informational message about a condition, possibly
independently insignificant.
Info A basic notification or informational message, possibly
independently insignificant.
Fault States
A fault raised in a Cisco UCS instance transitions through more than one state during its lifecycle.
Table 1-2 describes the possible fault states in alphabetical order.
State Description
Cleared The condition has been resolved and the fault has been cleared.
Flapping A fault was raised, cleared, and then raised again within a short time
interval, known as the flap interval.
Soaking A fault was raised and then cleared within a short time interval,
known as the flap interval. Since this may be a flapping condition,
the fault severity remains at its original active value, but this state
indicates the condition that raised the fault has cleared.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Fault Types
A fault raised in a Cisco UCS instance can be one of the types described in Table 1-3.
Type Description
fsm An FSM task has failed to complete successfully, or Cisco UCS
Manager is retrying one of the stages of the FSM.
equipment Cisco UCS Manager has detected that a physical component is
inoperable or has another functional issue.
server Cisco UCS Manager cannot complete a server task, such as
associating a service profile with a server.
configuration Cisco UCS Manager cannot successfully configure a component.
environment Cisco UCS Manager has detected a power problem, thermal
problem, voltage problem, or loss of CMOS settings.
management Cisco UCS Manager has detected a serious management issue, such
as one of the following:
• Critical services could not be started
• The primary switch could not be identified
• Components in the instance includes incompatible firmware
versions
connectivity Cisco UCS Manager has detected a connectivity problem, such as
an unreachable adapter.
network Cisco UCS Manager has detected a network issue, such as a link
down.
operational Cisco UCS Manager has detected an operational problem, such as a
log capacity issue or a failed server discovery.
Properties of Faults
Cisco UCS Manager provides detailed information about each fault raised in a Cisco UCS instance.
Table 1-4 describes the fault properties that you can view in Cisco UCS Manager CLI or Cisco UCS
Manager GUI.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Lifecycle of Faults
Faults in Cisco UCS are stateful. Only one instance of a given fault can exist on each object. If the same
fault occurs a second time, Cisco UCS increases the number of occurrences by one.
A fault has the following lifecycle:
1. A condition occurs in the system and Cisco UCS raises a fault. This is the active state.
2. When the fault is alleviated, it enters a flapping or soaking interval that is designed to prevent
flapping. Flapping occurs when a fault is raised and cleared several times in rapid succession.
During the flapping interval the fault retains its severity for the length of time specified in the fault
collection policy.
3. If the condition re-occurs during the flapping interval, the fault returns to the active state. If the
condition does not reoccur during the flapping interval, the fault is cleared.
4. The cleared fault enters the retention interval. This interval ensures that the fault reaches the
attention of an administrator, even if the condition that caused the fault has been alleviated, and that
the fault is not deleted prematurely. The retention interval retains the cleared fault for the length of
time specified in the fault collection policy.
5. If the condition reoccurs during the retention interval, the fault returns to the active state. If the
condition does not reoccur, the fault is deleted.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Each fault severity is represented by a different icon. The number below each icon indicates how many
faults of that severity have occurred in the system. If you click an icon, Cisco UCS Manager GUI opens
the Faults tab in the Work area and displays the details of all faults of that severity.
Tip For information on how to configure the fault collection policy, see the Cisco UCS configuration guides,
accessible through the Cisco UCS B-Series Servers Documentation Roadmap.
Fault Documentation
Documentation about Cisco UCS faults, including explanations and recommended actions, is available
in the Cisco UCS Faults Reference.
Events
In Cisco UCS, an event is an immutable object that is managed by Cisco UCS Manager. Each event
represents a non-persistent condition in the Cisco UCS instance. After Cisco UCS Manager creates and
logs an event, the event does not change. For example, if you power on a server, Cisco UCS Manager
creates and logs an event for the beginning and the end of that request.
You can view events for a single object, or you can view all events in a Cisco UCS instance from either
the Cisco UCS Manager CLI or the Cisco UCS Manager GUI. Events remain in Cisco UCS until the
event log fills up. When the log is full, Cisco UCS Manager purges the log and all events in it.
This section includes the following topics:
• Properties of Events, page 1-7
• Events in Cisco UCS Manager GUI, page 1-7
• Events in Cisco UCS Manager CLI, page 1-7
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Properties of Events
Cisco UCS Manager provides detailed information about each event created and logged in a Cisco UCS
instance. Table 1-5 describes the fault properties that you can view in Cisco UCS Manager CLI or Cisco
UCS Manager GUI.
Core Files
Critical failures in Cisco UCS Manager and some Cisco UCS components, such as a fabric interconnect
or an I/O module, can cause the system to create a core file. Each core file contains a large amount of
data about the system and the component at the time of the failure.
Cisco UCS Manager manages the core files from all components. You can configure Cisco UCS Manager
to export a copy of a core file to a location on an external TFTP server as soon as that core file is created.
This section includes the following topics:
• Core Files in Cisco UCS Manager GUI, page 1-8
• Core Files in Cisco UCS Manager CLI, page 1-8
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Tip For information on how to enable the exporter, see the Cisco UCS configuration guides, accessible
through the Cisco UCS B-Series Servers Documentation Roadmap.
Audit Log
The audit log records actions performed by users in Cisco UCS Manager, including direct and indirect
actions. Each entry in the audit log represents a single, non-persistent action. For example, if a user logs
in, logs out, or creates, modifies, or deletes an object such as a service profile, Cisco UCS Manager adds
an entry to the audit log for that action.
You can view audit log entries in Cisco UCS Manager CLI, Cisco UCS Manager GUI, or the output from
the show tech-support command.
This section includes the following topics:
• Properties of Audit Log Entries, page 1-9
• Audit Log in Cisco UCS Manager GUI, page 1-9
• Audit Log in Cisco UCS Manager CLI, page 1-9
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Tip For more information about the SEL, including how to view the SEL for each server and configure the
SEL policy, see the Cisco UCS configuration guides accessible through the Cisco UCS B-Series Servers
Documentation Roadmap.
SEL File
The SEL file is approximately 40KB in size, and no further events can be recorded when it is full. It must
be cleared before additional events can be recorded.
SEL Policy
You can use the SEL policy to backup the SEL to a remote server, and optionally clear the SEL after a
backup operation occurs. Backup operations can be triggered based on specific actions, or they can occur
at regular intervals. You can also manually backup or clear the SEL.
Cisco UCS Manager automatically generates the SEL backup file, according to the settings in the SEL
policy. The filename format is sel-SystemName-ChassisID-ServerID-ServerSerialNumber-Timestamp
For example, a file name could be sel-UCS-A-ch01-serv01-QCI12522939-20091121160736.
Syslog
Syslog provides a central point for collecting and processing system logs that you can use to troubleshoot
and audit the Cisco UCS instance. Cisco UCS Manager relies on the DCOS syslog mechanism and API
and on the syslog feature of the primary fabric interconnect to collect and process the syslog entries.
This section includes the following topics:
• Syslog Configuration, page 1-11
• Syslog Location, page 1-11
• Syslog Entry Format, page 1-11
• Syslog Entry Parameters, page 1-12
• Syslog Services, page 1-13
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Syslog Configuration
Cisco UCS Manager manages and configures the syslog collectors for the Cisco UCS instance and
deploys the configuration to the fabric interconnect or fabric interconnects. This configuration affects
all syslog entries generated in the Cisco UCS instance by DCOS or by Cisco UCS Manager.
Syslog Location
You can configure Cisco UCS Manager to do one or more of the following with the syslog and syslog
entries:
• Display the syslog entries in the console or on the monitor
• Store the syslog entries in a file
• Forward the syslog entries to up to three external log collectors where the syslog for the Cisco UCS
instance is stored
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Name Description
Facility The logging facility that generated and sent the syslog entry. The
facilities are broad categories that are represented by integers.
These sources can be one of the following standard Linux facilities:
• local0
• local1
• local2
• local3
• local4
• local5
• local6
• local7
Severity The severity of the event, alert, or issue that caused the syslog entry
to be generated. The severity can be one of the following:
• emergencies
• critical
• alerts
• errors
• warnings
• information
• notifications
• debugging
Hostname The hostname included in the syslog entry depends upon the
component where the entry originated, as follows:
• Fabric interconnect or Cisco UCS Manager, the hostname of
the Cisco UCS instance
• All other components, the hostname associated with the VIF
Timestamp The date and time when the syslog entry was generated.
Message A description of the event, alert, or issue that caused the syslog
entry to be generated.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Syslog Services
The following Cisco UCS components use the DCOS syslog services to generate syslog entries for
system information and alerts:
• I/O module—Runs syslogd. All syslog entries are sent to the fabric interconnect to which it is
connected.
• CIMC—All syslog entries are sent to the primary fabric interconnect in a cluster configuration.
• Adapter—Runs Nic-Tools/Syslog. All syslog entries are sent to both fabric interconnects.
• Cisco UCS Manager—Logs its own syslog entries according to the syslog configuration.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 2
Finite State Machine
This chapter provides an overview of the finite state machine (FSM) and how to use it to troubleshoot
issues with Cisco UCS.
This chapter contains the following sections:
• Overview of the FSM, page 2-1
• FSM Stage Names, page 2-2
• FSM in Cisco UCS Manager GUI, page 2-2
• FSM in Cisco UCS Manager CLI, page 2-3
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Multiple FSM tasks can be associated to an end point. However, only one FSM task at a time can run.
Additional FSM tasks for the same end point are placed in a queue and are scheduled to be run when the
previous FSM task either successfully completes or fails.
You can view the FSM details for a particular end point to determine if a task succeeded or failed. You
can also use the FSM to troubleshoot any failures.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
You can use the show fsm task command in the appropriate mode to view all pending tasks in the FSM
queue. The following example displays FSM task queue for the server in chassis 1, slot 6:
UCS-A# scope server 1/6
UCS-A /chassis/server # show fsm task
FSM Task:
Item ID Completion FSM Flags
---------------- -------- ------------ ---------
Powercycle 1154858 Scheduled
BiosRecovery 1154860 Scheduled
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 3
General Troubleshooting Steps and Solutions
This chapter provides some steps and possible solutions that you can implement when you troubleshoot
issues with Cisco Unified Computing System (Cisco UCS).
This chapter contains the following sections:
• Guidelines for Troubleshooting, page 3-1
• Gathering Information about a Cisco UCS Instance, page 3-2
Guideline Description
Check the release notes to see if the issue is a The release notes are accessible through the Cisco
known problem. UCS B-Series Servers Documentation Roadmap.
Take screenshots of the fault or error message These screenshots provide visual cues about the state
dialog box, the FSM for the component, and of Cisco UCS Manager when the problem occurred. If
other relevant areas. your computer does not have software to take
screenshots, check the documentation for your
operating system, as it may include this functionality.
Record the steps that you took directly before If you have access to screen or keystroke recording
the issue occurred. software, repeat the steps you took and record what
occurs in Cisco UCS Manager.
If you do not have access to that type of software,
repeat the steps you took and make detailed notes of
the steps and what happens in Cisco UCS Manager
after each step.
Execute the show tech-support command. The information about the current state of the Cisco
UCS instance is very helpful to Cisco support and
frequently provides the information needed to identify
the source of the problem.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Note You can only execute the show tech-support command in Cisco UCS Manager CLI.
CH A P T E R 4
Troubleshooting Issues with Cisco UCS
This chapter provides some steps and possible solutions that you can implement when you troubleshoot
issues with Cisco Unified Computing System (Cisco UCS).
This chapter contains the following sections:
• Troubleshooting Boot Issues, page 4-1
• Troubleshooting KVM Issues, page 4-3
• Troubleshooting VM Issues, page 4-5
• Troubleshooting Cisco UCS Manager Issues, page 4-6
• Troubleshooting Fabric Interconnect Issues, page 4-8
Problem
The system fails to produce a reboot warning listing dependencies.
Possible Cause
This problem can be caused by changes to a vNIC template or a vHBA template. Reboot warnings occur
when the back-end returns a list of dependencies. When you update the template type for a vNIC or
vHBA template and make changes to any boot-related properties without applying changes between
steps, back-end systems are not triggered to return a list of dependencies.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Recommended Action
Take the following actions in Cisco UCS Manager GUI:
Problem
The eUSB embedded inside the Cisco UCS server includes an operating system. However, the server
does not boot from that operating system.
Possible Cause
This problem can occur when, after associating the server with the service profile, the eUSB is not at the
top of the actual boot order for the server.
Recommended Action
To ensure that the server boots from the operating system on the eUSB, take the following actions in
Cisco UCS Manager GUI:
Procedure
Step 1 On the Servers tab, do the following to verify the boot policy configuration:
a. Navigate to the service profile associated with the server.
b. On the Boot Order tab, ensure that Local Disk is configured as the first device in the boot policy.
Step 2 On the Equipment tab, do the following to verify the actual boot order for the server:
a. Navigate to the server.
b. On the General tab, expand the Boot Order Details area and verify that the eUSB is listed as the
first device on the Actual Boot Order tab.
For example, the first device should be VM eUSB DISK.
Step 3 If the eUSB is not the first device in the actual boot order, do the following:
a. On the General tab for the server, click the following links in the Actions area:
– KVM Console to launch the KVM console
– Boot Server to boot the server
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
b. In the KVM console, while the server is booting, press F2 to enter the BIOS setup.
c. In the BIOS utility, navigate to the Boot Options tab.
d. Choose Hard Disk Order.
e. Configure Boot Option #1 to the eUSB.
For example, set this option to VM eUSB DISK.
f. Press F10 to save and exit.
Problem
A BadFieldException displays when the KVM viewer is launched.
Possible Cause
This problem can be occur because Java Web Start disables the cache by default when it is used in
conjunction with an application that uses native libraries.
Recommended Action
If you see this issue, take the following action:
Procedure
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Problem
The KVM Console fails to launch and the JRE displays the following message:
Unable to launch the application.
Possible Cause
This problem can be caused if several KVM Consoles are launched simultaneously.
Recommended Action
If you see this issue, take the following action:
Procedure
Problem
The first time you attempt to open it on a server, the KVM fails to launch.
Possible Cause
This problem can be caused by a JRE version incompatibility.
Recommended Action
If you see this issue, take the following action:
Procedure
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Troubleshooting VM Issues
This section includes the following topic:
• Currently connected network interface x uses Distributed Virtual Switch (uusid: y) which is
accessed on the host via a switch that has no free ports, page 4-5
Problem
The following error displays:
Currently connected network interface x uses Distributed Virtual Switch (uusid:y) which is accessed on
the host via a switch that has no free ports.
Possible Cause
This problem can be caused by one of the following issues:
• After powering off or migrating a VM from one host to another, the vSphere Server fails to
recompute the numPortsAvailable property in the hostProxySwitch object.
• The cumulative number of vNICs for the VMs powered on an ESX host matches or exceeds the
number of dynamic nVINCs configured in the server’s service profile.
• After migrating a VM from one data-store to another data-store on the same server, the server
incorrectly detects an increase in the number of DVS ports being used by all of the VMs powered
on the host.
Recommended Action
If you see this issue, take the following actions:
Procedure
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Step 3 If the error resulted from migrating a VM instance from one data-store to another data-store on the same
server, do the following:
a. Shut down all of the VMs on the ESX host.
b. Retry the migration.
Problem
After coming back from sleep mode, the following message appears:
Possible Cause
This problem can be caused if Cisco UCS Manager GUI was not shut down before the computer went to
sleep. Since the JRE does not have a sleep detection mechanism, the system is unable to retrack all of
the messages received before it went into sleep mode. After multiple retries, this event sequencing error
is logged.
Note Always shut down Cisco UCS Manager GUI before putting your computer to sleep.
Recommended Action
Step 1 In Cisco UCS Manager GUI, if a Connection Error dialog box is displayed, click one of the following:
• Re-login to log back in to Cisco UCS Manager GUI
• Exit to exit Cisco UCS Manager GUI
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Problem
After hot-swapping, removing, or adding a hard drive, updated HDD metrics do not display in Cisco
UCS Manager GUI.
Possible Cause
This problem can be caused because Cisco UCS Manager only gathers HDD metrics during a system
boot. If a hard drive is added or removed after a system boot, Cisco UCS Manager GUI does not update
the HDD metrics.
Recommended Action
Cisco UCS Manager Reports More Disks in Server than Total Slots Available
Problem
Cisco UCS Manager reports that a server has more disks than the total disk slots available in the server.
For example, Cisco UCS Manager reports three disks for a server with two disk slots as follows:
RAID Controller 1:
Local Disk 1:
Product Name: 73GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted
PID: A03-D073GC2
Serial: D3B0P99001R9
Presence: Equipped
Local Disk 2:
Product Name:
Presence: Equipped
Size (MB): Unknown
Local Disk 5:
Product Name: 73GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted
Serial: D3B0P99001R9
HW Rev: 0
Size (MB): 70136
Possible Cause
This problem is typically caused by a communication failure between Cisco UCS Manager and the server
that reports the inaccurate information.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Recommended Action
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Problem
The fabric interconnect fails to start.
Possible Cause
This problem can be caused by one of the following issues, which require you to use the boot loader
prompt to recover the fabric interconnect:
• Kickstart image is corrupted or non-functional for other reasons
• File system on the bootflash memory is corrupted
Recommended Action
If you see this issue, take the following action.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Procedure
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 5
Troubleshooting Cisco UCS Faults
Cisco UCS faults provide information that you can use to troubleshoot issues with a Cisco UCS instance.
Documentation about these faults, including explanations and recommended actions, are available in the
Cisco UCS Faults Reference.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 6
Troubleshooting SAN Boot and SAN Connectivity
Issues
This chapter contains information about how to troubleshoot SAN boot and SAN connectivity issues,
including the Storage Area Network (SAN) configuration in Cisco UCS Manager and the SAN array.
This chapter contains the following sections:
• SAN Connectivity Checklist, page 6-1
• SAN Array Configuration Checklist, page 6-2
• Recommended Solutions for Issues During SAN Boot, page 6-2
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 7
Troubleshooting Server Hardware Issues
This chapter contains information about how to troubleshoot hardware issues not specific to a given
model of UCS B-Series server.
This chapter contains the following sections:
• Diagnostics Button and LEDs, page 7-1
• DIMM Memory Issues, page 7-2
• CPU Issues, page 7-7
• Disk Drive and RAID Issues, page 7-9
• Adapter Issues, page 7-12
• Gathering Information Before Calling Support, page 7-14
• Related Documents, page 7-15
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Known Issues
Please rule out the following known issues before contacting Cisco Technical support with
DIMM-related issues:
Correctable DIMM error reporting in Cisco UCS Manager will not go away until BMC is rebooted.
Correctable DIMM errors report a DIMM as “Degraded” in Cisco UCS Manager, but the DIMMs will
still be available to the blade’s OS.
To correct this, use the following commands to clear the SEL logs from the BMC, then reboot the BMC
of the affected blade, or just remove and reseat the blade server from the chassis.
SAM-FCS-A# scope server x/y
SAM-FCS-A /chassis/server # scope bmc
SAM-FCS-A /chassis/server/bmc # reset
SAM-FCS-A /chassis/server/bmc* # commit-buffer
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
A single DIMM can cause other DIMMs to get marked as bad. POST fails.
The UCS blade will not complete its boot cycle, and FSM will stay stuck at 54%.
Upgrade to Cisco UCS Manager version 1.2.(1b) or later.
Resetting the BMC will not impact the OS running in the blade.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
You can check memory information via the CLI using the following commands:
scope server x/y -> show memory detail
scope server x/y -> show memory-array detail
scope server x/y -> scope memory-array x -> show stats history memory-array-env-stats
detail
Confirm that the amount of memory seen from the OS point-of-view matches what is listed for the
server’s associated service profile. Can the OS see all the memory or just part of the memory? If possible,
run a memory diagnostic tool from the OS.
The top of Figure 7-1 shows a DIMM that is correctly inserted and latched. Unless there happens to be
a small bit of dust blocking one of the contacts, this DIMM should function correctly. The next view
below it shows a DIMM mismatched with the key for its slot; the DIMM cannot be inserted in this
orientation and needs to be rotated to fit into the slot. In the next illustration down, the left side seems
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
to be correctly seated and the latch is fully connected, but the right side is just barely touching the slot
and the latch is not seated into the notch on the DIMM. In the bottom view, the left is again fully inserted
and seated, and the right side is partially inserted and incompletely latched.
279121
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CPU Issues
All UCS servers support 1-2 or 1-4 CPUs. A problem with a CPU can cause a server to fail to boot, run
very slowly, or cause serious data loss or corruption. If CPU issues are suspected, consider the following:
• All CPUs in a server should be the same type, running at the same speed and with the same number
and size DIMMs populated.
• If the CPU was recently replaced or upgraded, be certain the new CPU is compatible with the server
and that a BIOS supporting the CPU was installed. Refer to the server’s documentation for a list of
supported Cisco models and product IDs, and only use CPUs supplied by Cisco. BIOS version
information can be found in the release notes for a software release.
• When replacing a CPU, great care must be taken to correctly thermally bond the CPU and the heat
sink. An overheating CPU will produce fault messages visible in UCS Manager. It will also throttle
back on performance in order to prevent damage to itself.
• Check the baffles and airflow for all servers in a chassis if CPU overheating is suspected. Airflow
problems in adjacent servers have been known to cause improper CPU cooling in a server.
• CPU speed and memory speed should match. If they do not match, the server runs at the slower of
the two speeds.
• In the event of a failed CPU, the remaining active CPU or CPUs will not have access to memory
assigned to the failed CPU.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
You can check CPU information via the CLI using the following commands:
scope server x/y -> show cpu
scope server x/y -> show bios
scope server x/y -> show cimc
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
• UCS B440 servers have an LSI MegaRAID controller card (model varies by server). Depending on
the license key installed, these cards provide RAID 0, 1, 5, 6, 10, 50, and 60 support for up to four
SAS or SATA drives.
If you do not have a record of which option is used in the server, you can disable quiet boot and read the
on-screen messages that are displayed during system bootup.
• Information about the models of RAID controller installed are displayed as part of the verbose boot.
You are also prompted to press Ctrl-H to launch configuration utilities for those cards. See also How
to Disable Quiet Boot, page 7-10.
• If no models of card are displayed after you disable quiet boot but there is a RAID configuration,
your server is using the onboard ICH10R controller. You are also prompted to press Ctrl-M to launch
the configuration utilities for this controller (see Figure 7-2). See also How To Launch Option
ROM-Based Controller Utilities, page 7-11.
Figure 7-2 Startup Screen for the ICH10R Controller Configuration Utilities
Step 1 Boot the server and watch for the F2 prompt during bootup.
Step 2 Press F2 when prompted to enter the BIOS Setup utility.
Step 3 On the Main page of the BIOS Setup utility, set Quiet Boot to Disabled. This allows non-default
messages, prompts, and POST messages to display during bootup instead of the Cisco logo screen.
Step 4 Press F10 to save your changes and exit the utility.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Step 1 Keep both the starting and destination servers for the RAID cluster in the associated state and shut them
down. The Service Profiles for both servers must have an identical Local Disk Configuration Policy.
Note When using this procedure during an M1 to M2 upgrade or direct replacement within a slot, the
destination server will not be associated yet or have a disk policy, but instead will inherit the same
policies as the starting server when it is inserted into the same slot the starting server was in.
Step 2 Once they are powered-off, physically move the drives in the array to the destination server. If you are
changing servers but keeping the drives in the same slot, at this point, insert the new server into the slot
of the original server.
Step 3 Connect the KVM dongle and a monitor, keyboard, and mouse to the destination server.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Step 4 Boot the destination server, using the power switch on the front of the server. If necessary, disable quiet
boot and boot again. (See How to Disable Quiet Boot, page 7-10.)
Step 5 Wait for the LSI Configuration Utility banner.
Step 6 Enter the LSI Configuration Utility by selecting Ctrl-C.
Step 7 Select the SAS Adapter used in your server from the SAS Adapter List. In needed, refer to the “How to
Determine Which RAID Controller Is in Your Server” section on page 7-9.
Step 8 Select RAID Properties. This brings up the View Array screen.
Step 9 Select Manage Array. This brings up the Manage Array screen.
Step 10 Select ‘Activate Array’ from the Manage Array screen. Once the activation is complete, the RAID
status will change to ‘Optimal’.
Step 11 Select the ‘Synchronize Array’ option from the Manage Array screen.
Step 12 Wait for the Mirror Synchronization to complete, and monitor the progress bar that comes up. Please
note that the time to complete the Synchronization can vary depending upon the size of the disks in the
RAID array.
Step 13 Once the Mirror Synchronization is complete, press the ESC key several times to go back through each
of the windows (one at a time) and then exit the LSI Configuration Utility, selecting the “reboot” option
to implement the changes.
Adapter Issues
A problem with the Ethernet or FCoE adapter can cause a server to fail to connect to the network and
make it unreachable from UCS Manager. Mechanically, all adapters are unique Cisco designs and non-
Cisco adapters are not available, although it could be possible to counterfeit one. If adapter issues are
suspected, consider the following:
• Is the adapter a genuine Cisco Adapter? Where and from whom was it purchased?
• Is the adapter type supported in the software release you are using? The Internal Dependencies table
in the UCS Manager 1.3(1) Release Notes provides minimum and recommended software versions
for all adapters.
• Has the appropriate firmware for the adapter been loaded on the server? In software release versions
1.0(1) through 1.3(1), the UCS Manager version and the adapter firmware version need to match.
To update the Cisco UCS software and firmware, refer to the appropriate Upgrading Cisco UCS
from Release ____ to Release 1.3(1) document for your installation.
• If the software version update was incomplete, and the firmware version no longer matches the UCS
Manager version, try updating the Adapter firmware as described in the Cisco UCS Manager CLI
Configuration Guide’s “Managing Firmware“ chapter.
• To deploy two UCS M81KR Virtual Interface Cards on the UCS B250 Extended Memory Blade
Server running ESX 4.0 you must upgrade to patch 5 (ESX4.0u1p5) or later release of ESX 4.0.
• If you are migrating from one adapter type to another, as well as making sure the needed drivers for
the new adapter type are available, make sure that you update the Service profile to match the new
adapter type, and configure services appropriate to that adapter type.
• If you are using dual adapters, be aware there are certain restrictions on the combinations supported.
The following combinations are supported:
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Known Issues
There are a number of known issues and open bugs with Adapters called out in the Release Notes
documentation, refer to the document for your software release. The following is a persistent known
condition:
(CSCtd32884 and CSC71310) The type of adapter in a server impacts the maximum MTU supported.
Network MTU above the maximums may cause the packet to be dropped for the following adapters:
• The Cisco UCS CNA M71KR adapter supports a maximum MTU of 9216.
• The Cisco UCS 82598KR-CI adapter supports a maximum MTU of 14000.
You can check Adapter state information via the CLI using the following commands:
scope server x/y -> show adapter
scope server x/y -> show adapter detail
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Recommended Solutions
Table 7-3 contains a list of guidelines and recommended solutions that can assist you in troubleshooting
DIMM issues. These suggested solutions include those that are described in the “Known Issues” section
on page 7-2 and the “Troubleshooting DIMM Errors” section on page 7-4.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
When contacting Cisco TAC for UCS issues it is always important to capture the tech-support output
from the UCS Manager instance and chassis in question (for example):
UCS1-A# connect local-mgmt
UCS1-A(local-mgmt)# show tech chassis X all detail <--where X is the chassis having the
blade with the DIMM issue.
UCS1-A(local-mgmt)# show tech ucsm detail
Related Documents
Individual server models are documented in the Cisco UCS Blade Server Installation and Service Notes.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
CH A P T E R 8
Cisco UCS Error Messages
This chapter contains a list of error messages that you may see in a Cisco UCS instance. This chapter
contains the following sections:
• Overview, page 8-1
• Information and Warning Messages, page 8-2
• FSM Messages, page 8-19
This chapter does not contain information about Cisco UCS faults. Documentation about faults,
including explanations and recommended actions, are available in the Cisco UCS Faults Reference.
Overview
Cisco UCS error messages typically display in Cisco UCS Manager GUI and Cisco UCS Manager CLI.
These error messages are specific to the action that a user is performing or the object that a user is
configuring or administering. These messages can be the following:
• Informational messages, providing assistance and tips about the action being performed
• Warning messages, providing information about system errors related to an object, such as a user
account or service profile, that the user is configuring or administering
• FSM status messages, providing information about the status of an FSM stage
Many error messages contain one or more variables. What information that Cisco UCS Manager uses to
replace these variables depends upon the context in which you see the message. Some messages can be
generated by more than one type of error.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
RADIUS providers cannot be deleted while authentication realm is set to use RADIUS.
The order of RADIUS providers cannot be changed while authentication realm is set
to use RADIUS.
The order of TACACS providers cannot be changed while authentication realm is set
to use TACACS.
The order of LDAP providers cannot be changed while authentication realm is set
to use LDAP.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
System does not allow more than %d total privileges across all roles.
User %s’s privileges (admin, aaa, fault or operations) and locale assignment are
incompatible.
Admin privilege can be assigned to a user only by another user with admin
privilege.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Only Cisco TAC alert is allowed with built-in Cisco TAC profile.
%s
%d
%d
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Configuration for FC Port %u/%u does not exist for fabric interconnect %s.
VSAN %u (of network %s) and %u (of network %s) - both cannot share the FCoE VLAN %u.
Networks %s and %s - both cannot share same VSAN id (%u) with different FCoE VLAN
ids (%u and %u respectively).
Blade %s.
No chassis ID is available.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
GenerateKey failed.
GetCsrFilename Error.
GenerateCSR failed.
Modulus must be set before creating certificate request for key ring %s.
Incorrect MO access.
Trustpoint must be set before adding a certificate for key ring %s.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
A system user exists with the same name; choose a different name for the SNMP user.
SNMP MO is missing.
DNS MO is missing.
Invalid timezone.
DateTime MO is missing.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Image for Vendor %s, Model %s and Version %s not found. Download and try again.
A DVS named ’%s’ is under process of deletion, wait until deletion completes.
Deletion of vCenter ’%s’ with same host ’%s’ in in progress, wait until it gets
deleted.
Resource allocation error: Cannot claim any extension key resource for this DVS.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Maximum ports per DVS cannot exceed %u; you must reduce max-ports property of
port-profiles.
Cannot change extension key while there are pending DVS deletions.
A virtual network, IP address, netmask, and gateway must be configured for inband
configuration.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Only Ethernet best-effort class can match against ’any’ COS value.
Inconsistent pool definition - the IP address and default gateway must be in same
network.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Cannot resolve %s: class "%s" does not have a naming definition.
Blade is still physically present; removal is not permitted, ch: %u, slot: %u.
The same profile (%s) cannot be applied to multiple virtual switches under a common
organization.
Threshold class [%s] cannot contain threshold definition for property [%d].
Threshold definition [%s] cannot contain threshold for this property type [%s].
XML exception: %s
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Username is required.
Internal error. Installable was deleted while installation was in progress %s.
Internal error. CIMC Installable was deleted while installation was in progress
%s.
Unable to find CIMC Image for vendor %s, Model %s and version %s.
Unable to find IOM Image For Vendor %s, Model %s and version %s.
Internal error. Kernel Installable was deleted while installation was in progress.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Internal error. System Installable was deleted while installation was in progress.
Unable to find fabric interconnect kernel image for Vendor %s, Model %s and Version
%s
Unable to find fabric interconnect software image for Vendor %s, Model %s and
Version %s.
Server Profile has firmware policy. Modify the policy to execute activate.
Root is null.
lResponse is null.
NO MEMORY.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
No model prop meta object for model prop %u, prop name = %s
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Invalid State:
Null RN.
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Id=%u
%s NO PREFIX %p
Error: call to localtime_r() returned ’%s’ - while converting date value ’%llu’
aInProp == NULL!
No iterator
User is not privileged to config MO, class %s, MO mask: 0x%llx, Config mask: 0x%llx
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Non-existing property %d
No naming meta
Returning empty RN
No such class %u
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
DN IS EMPTY
No prop meta %u
FSM Messages
PathReset:Disable: CLASS MISMATCH(%s); fabric:LocaleEXPECTED: SKIPPING!
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
SKIPPING!
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
INDEX
troubleshooting 1-2
A
condition 1-3
Admin tab 1-1 configuration fault type 1-4
associating service profiles 6-2, 7-6, 7-8, 7-14 connectivity fault type 1-4
Audience ii-v Core File Exporter 1-8
audit log core files
about 1-8 about 1-7
Cisco UCS Manager CLI 1-9 Cisco UCS Manager CLI 1-8
Cisco UCS Manager GUI 1-9 Cisco UCS Manager GUI 1-8
exporting 1-8
critical 1-3
C
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
purpose 2-2
F
static view 2-3
fault collection policy 1-2, 1-6 fsm
faults fault type 1-4
about 1-2
active state 1-5
Cisco UCS Manager CLI 1-6
G
Cisco UCS Manager GUI 1-5 GUI
documentation 1-6 audit log 1-9
fault collection policy 1-6 core files 1-8
flapping 1-5 events 1-7
lifecycle 1-5 faults 1-5
properties 1-4 FSM 2-2
retention 1-5 troubleshooting 1-1
service profiles 5-1 guidelines
severities 1-3 security ii-vi
states 1-3 service profiles 6-2, 7-6, 7-8, 7-14
types 1-4 troubleshooting 3-1
Faults tab 1-5
Fault Summary area 1-5
fault types I
configuration 1-4 info 1-3
connectivity 1-4 interval
environment 1-4 flapping 1-5
equipment 1-4 retention 1-5
fsm 1-4 soaking 1-5
management 1-4
network 1-4
operational 1-4 L
server 1-4
lifecycle, faults 1-5
finite state machine
logs
See FSM
audit 1-8
flapping 1-3
event 1-6
flapping interval 1-5
syslog 1-10
FSM
system event 1-10
about 2-1
Cisco UCS Manager CLI 2-3
Cisco UCS Manager GUI 2-2
dynamic view 2-2
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m
SEL
M
about 1-10
major 1-3 policy 1-10
management fault type 1-4 server fault type 1-4
minor 1-3 service profiles
associating 6-2, 7-6, 7-8, 7-14
faults 5-1
N
severities
network fault type 1-4 cleared 1-3
condition 1-3
critical 1-3
O
info 1-3
obtaining major 1-3
documentation ii-vi minor 1-3
support ii-vi syslog 1-11
operational fault type 1-4 warning 1-3
show audit-logs 1-9
show cores 1-8
P show event 1-7
Se n d d o c u m e n t c o m m e n t s t o u c s - d o c f e e d b a ck @ c i s c o . c o m