Cisco C4200 User manual

Maintaining the Server Chassis
This chapter contains information about system LEDs and supported component installation or replacement.
•Status LEDs and Buttons, on page 1
•Preparing For Component Installation, on page 6
•Opening the Chassis Compartment Covers, on page 9
•Removing and Replacing Components, on page 11
Status LEDs and Buttons
This section contains information for interpreting LED states.
Front-Panel LEDs
Figure 1: Front Panel LEDs
Maintaining the Server Chassis
1

Table 1: Front Panel LEDs, Definition of States
StatesLED Name
• Off—No node is detected in the node bay.
• Green—The node is operating normally.
•Amber, steady—The node is in a degraded operational
state (minor fault). For example:
• Power supply redundancy is lost.
• CPUs are mismatched.
• At least one CPU is faulty.
• At least one DIMM is faulty.
•At least one drive in a RAID configuration failed.
• Amber, blinking—The node is in a critical fault state.
For example:
• Boot failure
• Fatal processor and/or bus error detected
• Over-temperature condition detected
Node health
The numbers 1 - 4 correspond to the numbered node
bays.
1
• Green—All power supplies are operating normally.
• Amber, steady—One or more power supplies are in
a degraded operational state.
• Amber, blinking—One or more power supplies are
in a critical fault state.
Power supply status2
Activating the locator beacon on any installed compute
node activates this chassis locator beacon.
• Off—The unit identification function is not in use.
• Blue, blinking—The unit identification function is
activated.
Locator beacon3
• Green—The system is operating at normal
temperature.
• Amber, steady—One or more temperature sensors
breached the critical threshold.
• Amber, blinking—One or more temperature sensors
breached the non-recoverable threshold.
Temperature status4
Maintaining the Server Chassis
2
Maintaining the Server Chassis
Front-Panel LEDs

• Green—All fan modules are operating properly.
• Amber, steady—One fan has a fault.
• Amber, blinking—Two or more fan modules have a
fault.
Fan status5
• Off—The hard drive is operating properly.
• Amber—Drive fault detected.
• Amber, blinking—The device is rebuilding.
• Amber, blinking with one-second interval—Drive
locate function activated in the software.
SAS/SATA drive fault
NVMe solid state drive (SSD) drive tray
LEDs have different behavior than
SAS/SATA drive trays.
Note
6
SAS
• Off—There is no hard drive in the hard drive tray (no
access, no fault).
• Green—The hard drive is ready.
•Green, blinking—The hard drive is reading or writing
data.
SAS/SATA drive activity
NVMe solid state drive (SSD) drive tray
LEDs have different behavior than
SAS/SATA drive trays.
Note
7
SAS
• Off—The drive is not in use and can be safely
removed.
• Green—The drive is in use and functioning properly.
• Green, blinking—the driver is initializing following
insertion or the driver is unloading following an eject
command.
• Amber—The drive has failed.
• Amber, blinking—A drive Locate command has been
issued in the software.
NVMe drive fault6
NVMe
• Off—No drive activity.
• Green, blinking—There is drive activity.
NVMe drive activity LED7
NVMe
Rear-Panel LEDs
The power supply LEDs are the only rear-panel LEDs native to the chassis. Compute node LEDs that repeat
on each compute node are also described below. The rear ports and LEDs vary, depending on which adapter
card and PCIe cards are installed.
Maintaining the Server Chassis
3
Maintaining the Server Chassis
Rear-Panel LEDs

Figure 2: Rear Panel LEDs
Table 2: Rear Panel LEDs, Definition of States
StatesLED Name
• Green—The node is operating normally.
•Green, Blinking—The node is in standby power mode.
• Amber—The node is in a degraded condition (for
example, one or more of the following conditions):
• Faulty or mismatched CPUs
• DIMM failure
• Failed drive in a RAID configuration
• Amber, Blinking—The node is in a critical condition
(for example, one or more of the following
conditions):
• Boot failure
• Fatal CPU and/or bus errors detected
• Fatal uncorrectable memory errors
• Excessive thermal conditions
Node Health Status1
• Off—There is no AC power to the node.
• Amber—The node is in standby power mode. Power
is supplied only to the Cisco IMC and some
motherboard functions.
• Green—The node is in main power mode. Power is
supplied to all node components.
Node Power button/Node Power status
(One each node)
2
• Off—Link speed is 10 Mbps.
• Amber—Link speed is 100 Mbps.
• Green—Link speed is 1 Gbps.
Node 1-Gb Ethernet dedicated management link speed
(One each node)
3
Maintaining the Server Chassis
4
Maintaining the Server Chassis
Rear-Panel LEDs

• Off—No link is present.
• Green—Link is active.
• Green, blinking—Traffic is present on the active link.
Node 1-Gb Ethernet dedicated management link status
(One each node)
4
• Off—The unit identification function is not in use.
• Blue, blinking—The unit identification function is
activated.
Node locator beacon
(One each node)
5
AC power supplies:
•Off—No AC input to any power supplies in the system
(12 V main power off, 12 V standby power off).
• Green, blinking—12 V main power off; 12 V standby
power on.
• Green, solid—12 V main power on; 12 V standby
power on.
• Amber, blinking—Warning threshold detected but 12
V main power on.
• Amber, solid—Critical error detected; 12 V main
power off (for example, over- or under-current,
over-voltage, or over-temperature failure).
• Amber, solid—If no AC input is supplied to one
power supply, the LED lights amber from the shared
system standby bus.
Power supply status
(One bi-color LED each power supply unit)
6
Internal Diagnostic LEDs in the Chassis
The fan tray in the chassis includes a fault LED for each of the fan modules. The four LEDs are numbered to
correspond to the four numbered fan modules.
Maintaining the Server Chassis
5
Maintaining the Server Chassis
Internal Diagnostic LEDs in the Chassis

Figure 3: Chassis Internal Diagnostic LED Location on Fan Tray
-Fan module fault LEDs on fan tray (one LED for
each fan module)
• Green—Fan is OK.
• Amber—Fan has a fault or is not fully seated.
1
Preparing For Component Installation
This section includes information and tasks that help prepare the chassis for component installation.
Required Equipment For Service Procedures
The replaceable components in the system chassis require the following tools for removal or installation:
• #1 Phillips-head screwdriver (for opening the supercap compartment cover)
• An electrostatic discharge (ESD) strap or other grounding equipment such as a grounded mat is
recommended to protect components.
Shutting Down and Removing Power From the System
Chassis Power
The C4200 system chassis does not include a physical power button. All of the component replacement in
the chassis can be performed without removing chassis power (assuming two power supplies with 1+1
redundancy).
Maintaining the Server Chassis
6
Maintaining the Server Chassis
Preparing For Component Installation

The chassis top covers are designed to allow access to replaceable components without exposing the user to
high voltages. However, to completely remove power when moving a chassis, you must disconnect all power
cords from the power supplies in the chassis.
Caution
Compute Node Power
Compute nodes include a physical power button so that you can shut down the individual node and any
installed operating system by using the power button on the node or the software interface.
To avoid data loss or damage to your operating system, you should always invoke a graceful shutdown.
Caution
The compute node can run in either of two power modes:
• Main power mode—Power is supplied to all server components and any operating system on your drives
can run.
• Standby power mode—Power is supplied only to the service processor and certain components. It is safe
for the operating system and data to remove the node from the chassis in this mode.
Shutting Down a Node Using the Power Button
Step 1 Check the color of the Power button/LED on the face of the compute node:
• Amber—The node is already in standby mode and you can safely remove it from the chassis.
• Green—The node is in main power mode and must be shut down before you can safely remove it from the chassis.
Step 2 Invoke either a graceful shutdown or a hard shutdown:
To avoid data loss or damage to your operating system, you should always invoke a graceful shutdown of the
operating system. Do not power off a node if any firmware or BIOS updates are in progress.
Caution
• Graceful shutdown—Press and release the Power button. The operating system performs a graceful shutdown and
the node goes to standby mode, which is indicated by an amber Power button/LED.
• Emergency shutdown—Press and hold the Power button for 4 seconds to force the main power off and immediately
enter standby mode.
Shutting Down a Node Using The Cisco IMC GUI
You must log in with user or admin privileges to perform this task.
Step 1 In the Navigation pane, click the Chassis tab.
Step 2 On the Chassis tab, click Summary.
Step 3 In the toolbar above the work pane, click the Host Power link.
Maintaining the Server Chassis
7
Maintaining the Server Chassis
Shutting Down a Node Using the Power Button

The Server Power Management dialog opens. This dialog lists all servers that are present in the system.
Step 4 In the Server Power Management dialog, select one of the following buttons for the server that you want to shut down:
To avoid data loss or damage to your operating system, you should always invoke a graceful shutdown of the
operating system. Do not power off a node if any firmware or BIOS updates are in progress.
Note
• Shut Down—Performs a graceful shutdown of the operating system.
• Power Off—Powers off the chosen node, even if tasks are running on that server.
It is safe to remove the node from the chassis when the Chassis Status pane shows the Power State as Off for the node
that you are removing.
The physical power button on the node also turns amber when it is safe to remove the node from the chassis.
Shutting Down Using The Cisco IMC CLI
You must log in with user or admin privileges to perform this task.
Step 1 At the server prompt, enter:
Example:
server# scope chassis
Step 2 At the chassis prompt, enter: scope server n
Example:
server/chassis# scope server 1
Step 3 At the chassis/server prompt, enter:
Example:
server/chassis/server# power shutdown
The operating system performs a graceful shutdown and the node goes to standby mode, which is indicated by an amber
Power button/LED.
Shutting Down a Node Using The Cisco UCS Manager Equipment Tab
You must log in with user or admin privileges to perform this task.
Step 1 In the Navigation pane, click Equipment.
Step 2 Expand Equipment > Chassis > Chassis Number > Servers.
Step 3 Choose the node that you want to shut down.
Step 4 In the Work pane, click the General tab.
Step 5 In the Actions area, click Shutdown Server.
Step 6 If a confirmation dialog displays, click Yes.
Maintaining the Server Chassis
8
Maintaining the Server Chassis
Shutting Down Using The Cisco IMC CLI

The operating system performs a graceful shutdown and the server goes to standby mode, which is indicated by an amber
Power button/LED.
Shutting Down a Node Using The Cisco UCS Manager Service Profile
You must log in with user or admin privileges to perform this task.
Step 1 In the Navigation pane, click Servers.
Step 2 Expand Servers > Service Profiles.
Step 3 Expand the node for the organization that contains the associated service profile.
Step 4 Choose the service profile of the node that you are shutting down.
Step 5 In the Work pane, click the General tab.
Step 6 In the Actions area, click Shutdown Server.
Step 7 If a confirmation dialog displays, click Yes.
The operating system performs a graceful shutdown and the server goes to standby mode, which is indicated by an amber
Power button/LED.
Opening the Chassis Compartment Covers
The server chassis has been designed so that only small compartment covers are opened to allow access to
replaceable components (cooling fans and supercap units for RAID backup).
Never remove the overall chassis cover; open only the compartment covers. The overall cover protects the
user from exposure to hazardous voltages that are present in the chasssis.
Caution
Maintaining the Server Chassis
9
Maintaining the Server Chassis
Shutting Down a Node Using The Cisco UCS Manager Service Profile

Figure 4: Fan and Supercap Compartment Covers
Supercap compartment cover3Fan compartment cover1
Supercap compartment cover securing screw4Fan compartment cover latch and lock2
Opening the Fan Compartment Cover
Step 1 Open the hinged cover:
a) If the cover latch is locked, use a screwdriver to turn the lock 90-degrees counterclockwise to unlock it.
b) Lift on the end of the latch that has the green finger grip. The cover is pushed back as you lift the latch.
c) Open the hinged cover.
Step 2 Close the hinged cover:
a) With the latch in the fully open position, close the hinged cover.
b) Press the cover latch down to the closed position. The cover is pushed forward.
Maintaining the Server Chassis
10
Maintaining the Server Chassis
Opening the Fan Compartment Cover

c) If desired, lock the latch by using a screwdriver to turn the lock 90-degrees clockwise.
Opening the Supercap Compartment Cover
Step 1 Open the supercap compartment cover:
a) Use a #2 Phillips-head screwdriver to loosen the single captive screw on the cover.
b) Lift on the end of the cover next to the captive screw and then completely remove the cover from the chassis.
Step 2 Replace the cover:
a) Set the cover in place. The end with the captive screw should be toward the chassis front.
b) Tighten the single captive screw on the cover.
Removing and Replacing Components
This section describes how to install or replace components in the Cisco UCS C4200 Server Chassis. For
information on replacing components inside an installed compute node, see the service note for your compute
node:
•Cisco UCS C125 Compute Node Service Note
Blank faceplates and cover panels serve three important functions: they prevent exposure to hazardous
voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might
disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the
system unless all cards, faceplates, front covers, and rear covers are in place.
Statement 1029
Warning
When handling server components, handle them only by carrier edges and use an electrostatic discharge (ESD)
wrist-strap or other grounding device to avoid damage.
Caution
Serviceable Components in the Chassis
The figure in this topic shows the locations of the serviceable components in the chassis.
For components inside a compute node, see the service note for your compute node:
•Cisco UCS C125 Compute Node Service Note
Maintaining the Server Chassis
11
Maintaining the Server Chassis
Opening the Supercap Compartment Cover

Figure 5: Cisco UCS C4200 Chassis Serviceable Component Locations
Cooling fan modules (four)
Each fan module contains two fans for redundancy.
5Front-loading drives
Node 1-controlled drive bays 1—6
All six bays support SAS/SATA drives; bays 1 and
2 also support NVME drives.
1
Maintaining the Server Chassis
12
Maintaining the Server Chassis
Serviceable Components in the Chassis

Supercap units (RAID backup)
Each supercap unit backs up one RAID controller in
the corresponding node (numbered 1—4).
6Front-loading drives
Node 2-controlled drive bays 1—6
All six bays support SAS/SATA drives; bays 1 and
2 also support NVME drives.
2
Compute node (up to four)7Front-loading drives
Node 3-controlled drive bays 1—6
All six bays support SAS/SATA drives; bays 1 and
2 also support NVME drives.
3
Power supplies (two, redundant 1+1)8Front-loading drives
Node 4-controlled drive bays 1—6
All six bays support SAS/SATA drives; bays 1 and
2 also support NVME drives.
4
Replacing Front-Loading SAS/SATA Drives
You do not have to shut down the drive or the corresponding compute node to replace SAS/SATA hard drives
or SSDs because they are hot-swappable.
Note
SAS/SATA Drive Population Guidelines
The chassis can hold up to 24 front-loading, 2.5-inch drives. Each installed compute node can control the six
drives that correspond to the node number in the chassis.
• The four compute node groups are marked on the bottom lip of the chassis (below the drives).
• In each of the four compute node groups, the drives are enumerated 1- 6.
• In each of the compute node groups, populate the lowest numbered bays first.
• Drives installed in front-panel bays that do not have a corresponding compute node are not seen by the
system.
• Keep an empty drive blanking tray in any unused bays to ensure proper airflow.
• You can mix SAS/SATA hard drives and SAS/SATA SSDs in the same server. However, you cannot
configure a logical volume (virtual drive) that contains a mix of hard drives and SSDs. That is, when
you create a logical volume, it must contain all SAS/SATA hard drives or all SAS/SATA SSDs.
Maintaining the Server Chassis
13
Maintaining the Server Chassis
Replacing Front-Loading SAS/SATA Drives

Figure 6: Drive Bay Numbering
Drive bays controlled by compute node 33Drive bays controlled by compute node 11
Drive bays controlled by compute node 44Drive bays controlled by compute node 22
4K Sector Format SAS/SATA Drives Considerations
• You must boot 4K sector format drives in UEFI mode, not legacy mode. See the procedures in this
section.
• Do not configure 4K sector format and 512-byte sector format drives as part of the same RAID volume.
• Operating system support on 4K sector drives is as follows: Windows: Win2012 and Win2012R2; Linux:
RHEL 6.5, 6.6, 6.7, 7.0, 7.2; SLES 11 SP3, and SLES 12. ESXi/Vmware is not supported.
Setting Up UEFI Mode Booting in the BIOS Setup Utility
Step 1 Boot the compute node and enter the BIOS setup utility by pressing the F2 key when prompted during bootup.
Step 2 Go to the Boot Options tab.
Step 3 Set UEFI Boot Options to Enabled.
Step 4 Under Boot Option Priorities, set your OS installation media (such as a virtual DVD) as your Boot Option #1.
Step 5 Go to the Advanced tab.
Step 6 Select LOM and PCIe Slot Configuration.
Step 7 Set the PCIe Slot ID: HBA Option ROM to UEFI Only.
Step 8 Press F10 to save changes and exit the BIOS setup utility. Allow the server to reboot.
Step 9 After the OS installs, verify the installation:
a) Enter the BIOS setup utility by pressing the F2 key when prompted during bootup.
b) Go to the Boot Options tab.
c) Under Boot Option Priorities, verify that the OS you installed is listed as your Boot Option #1.
Setting Up UEFI Mode Booting in the Cisco IMC GUI
Step 1 Use a web browser and the IP address of the compute node to log into the Cisco IMC GUI management interface.
Step 2 Navigate to Server > BIOS.
Step 3 Under Actions, click Configure BIOS.
Maintaining the Server Chassis
14
Maintaining the Server Chassis
4K Sector Format SAS/SATA Drives Considerations

Step 4 In the Configure BIOS Parameters dialog, select the Advanced tab.
Step 5 Go to the LOM and PCIe Slot Configuration section.
Step 6 Set the PCIe Slot: HBA Option ROM to UEFI Only.
Step 7 Click Save Changes. The dialog closes.
Step 8 Under BIOS Properties, set Configured Boot Order to UEFI.
Step 9 Under Actions, click Configure Boot Order.
Step 10 In the Configure Boot Order dialog, click Add Local HDD.
Step 11 In the Add Local HDD dialog, enter the information for the 4K sector format drive and make it first in the boot order.
Step 12 Save changes and reboot the server. The changes you made will be visible after the system reboots.
Replacing a Front-Loading SAS/SATA Drive
You do not have to shut down the server or drive to replace SAS/SATA hard drives or SSDs because they
are hot-swappable.
Note
Step 1 Remove the drive that you are replacing or remove a blank drive tray from the bay:
a) Press the release button on the face of the drive tray.
b) Grasp and open the ejector lever and then pull the drive tray out of the slot.
c) If you are replacing an existing drive, remove the four drive-tray screws that secure the drive to the tray and then lift
the drive out of the tray.
Step 2 Install a new drive:
a) Place a new drive in the empty drive tray and install the four drive-tray screws.
b) With the ejector lever on the drive tray open, insert the drive tray into the empty drive bay.
c) Push the tray into the slot until it touches the backplane, and then close the ejector lever to lock the drive in place.
Maintaining the Server Chassis
15
Maintaining the Server Chassis
Replacing a Front-Loading SAS/SATA Drive

Figure 7: Replacing a Drive in a Drive Tray
Drive tray screws (two on each side)3Ejector lever1
Drive removed from drive tray4Release button2
Replacing Front-Loading NVMe SSDs
This section is for replacing 2.5-inch NVMe solid-state drives (SSDs) in front-panel drive bays.
NVMe drives are not hot-swappable. You can replace them while the system is running, but you must shut
down the drive in the software or OS before removal.
Caution
Maintaining the Server Chassis
16
Maintaining the Server Chassis
Replacing Front-Loading NVMe SSDs

NVMe drives are supported only with Cisco IMC/BIOS 4.0(2) and later; they are supported with Cisco UCS
Manager 4.0(2) and later.
Note
Front-Loading NVMe SSD Population Guidelines
Each compute node in the chassis controls six drive bays. Drive bays 1 and 2 in each set of six bays support
NVMe SSDs. In the following figure only the drive bays outlined in red support NVMe drives.
• The four compute node groups are marked on the bottom lip of the chassis (below the drives). Drive
bays 1 and 2 in each group are marked with the drive bay numbers in squares to indicate that those bays
support NVMe drives.
• In each of the compute node groups, populate the lowest numbered bays first.
• Drives installed in front-panel bays that do not have a corresponding compute node are not seen by the
system.
• Keep an empty drive blanking tray in any unused bays to ensure proper airflow.
• In the following figure only the drive bays outlined in red support NVMe drives.
Figure 8: Drive Bay Numbering and NVMe Drive Support
Drive bays controlled by compute node 33Drive bays controlled by compute node 11
Drive bays controlled by compute node 44Drive bays controlled by compute node 22
Front-Loading NVME SSD Requirements and Restrictions
NVMe drives are not hot-swappable. You can replace them while the system is running, but you must shut
down the drive in the software or OS before removal.
Caution
Observe these requirements and restrictions:
• Cisco IMC/BIOS 4.0(2) and later; if using Cisco UCS Manager, release 4.0(2) and later.
• Hot-plug support must be enabled in the system BIOS. If you ordered the system with NVMe drives,
hot-plug support is enabled at the factory. See Enabling Hot-Plug Support in the System BIOS, on page
18.
Maintaining the Server Chassis
17
Maintaining the Server Chassis
Front-Loading NVMe SSD Population Guidelines

• NVMe SSDs support booting only in UEFI mode. Legacy boot is not supported.
• UEFI boot is supported in all supported operating systems. Hot-insertion and hot-removal are supported
in all supported operating systems except VMWare ESXi.
• You cannot control NVMe SSDs with a SAS RAID controller because NVMe SSDs interface with the
server via the PCIe bus.
Enabling Hot-Plug Support in the System BIOS
Hot-plug (OS-informed hot-insertion and hot-removal) is disabled in the system BIOS by default.
• If the system was ordered with NVMe SSDs, the setting was enabled at the factory. No action is required.
• If you are adding NVMe SSDs after-factory, you must enable hot-plug support in the BIOS. See the
following procedures.
Enabling Hot-Plug Support Using the BIOS Setup Utility
Step 1 Enter the BIOS setup utility by pressing the F2 key when prompted during bootup.
Step 2 Navigate to Advanced > PCI Subsystem Settings > NVMe SSD Hot-Plug Support.
Step 3 Set the value to Enabled.
Step 4 Save your changes and exit the utility.
Enabling Hot-Plug Support Using the Cisco IMC GUI
Step 1 Use a browser to log in to the Cisco IMC GUI for the server.
Step 2 Navigate to Compute > BIOS > Advanced > PCI Configuration.
Step 3 Set NVME SSD Hot-Plug Support to Enabled.
Step 4 Save your changes.
Replacing a Front-Loading NVMe SSD
This topic describes how to replace 2.5-inch NVMe SSDs in the front-panel drive bays.
OS-surprise removal is not supported. OS-informed hot-insertion and hot-removal are supported on all
supported operating systems except VMware ESXi.
Note
OS-informed hot-insertion and hot-removal must be enabled in the system BIOS. See Enabling Hot-Plug
Support in the System BIOS, on page 18.
Note
Maintaining the Server Chassis
18
Maintaining the Server Chassis
Enabling Hot-Plug Support in the System BIOS

Step 1 Remove an existing front-loading NVMe SSD:
a) Shut down the NVMe SSD to initiate an OS-informed removal. Use your operating system interface to shut down
the drive, and then observe the drive-tray LED:
• Green—The drive is in use and functioning properly. Do not remove.
• Green, blinking—the driver is unloading following a shutdown command. Do not remove.
• Off—The drive is not in use and can be safely removed.
b) Press the release button on the face of the drive tray.
c) Grasp and open the ejector lever and then pull the drive tray out of the slot.
d) Remove the four drive tray screws that secure the SSD to the tray and then lift the SSD out of the tray.
Step 2 Install a new front-loading NVMe SSD:
a) Place a new SSD in the empty drive tray and install the four drive-tray screws.
b) With the ejector lever on the drive tray open, insert the drive tray into the empty drive bay.
c) Push the tray into the slot until it touches the backplane, and then close the ejector lever to lock the drive in place.
Step 3 Observe the drive-tray LED and wait until it returns to solid green before accessing the drive:
• Off—The drive is not in use.
• Green, blinking—the driver is initializing following hot-plug insertion.
• Green—The drive is in use and functioning properly.
Maintaining the Server Chassis
19
Maintaining the Server Chassis
Replacing a Front-Loading NVMe SSD

Figure 9: Replacing a Drive in a Drive Tray
Drive tray screws (two on each side)3Ejector lever1
Drive removed from drive tray4Release button2
Replacing Fan Modules
There are four fault LEDs on the fan tray, each numbered to a corresponding fan module. These LEDs light
green when the fan is correctly seated and is operating OK. The LED lights amber when the fan has a fault
or is not correctly seated.
Tip
Maintaining the Server Chassis
20
Maintaining the Server Chassis
Replacing Fan Modules