Cisco UCS C220 M5 Server Installation and Service Guide: Americas Headquarters
Cisco UCS C220 M5 Server Installation and Service Guide: Americas Headquarters
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 following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15
of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of
the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio
frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference
will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on, users are
encouraged to try to correct the interference by using one or more of the following measures:
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product.
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.
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.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1721R)
© 2017 Cisco Systems, Inc. All rights reserved.
CHAPTER 1
Overview
• Overview, on page 1
• External Features, on page 1
• Serviceable Component Locations, on page 4
• Summary of Server Features, on page 6
Overview
The server is orderable in different versions, each with a different front panel/drive-backplane configuration.
• Cisco UCS C220 M5 (UCSC-220-M5SX)—Small form-factor (SFF) drives, with 10-drive backplane.
Supports up to 10 2.5-inch SAS/SATA drives. Drive bays 1 and 2 support NVMe SSDs.
• Cisco UCS C220 M5 (UCSC-220-M5SN)—SFF drives, with 10-drive backplane. Supports up to 10
2.5-inch NVMe-only SSDs.
• Cisco UCS C220 M5 (UCSC-220-M5L)—Large form-factor (LFF) drives, with four-drive backplane.
Supports up to four 3.5-inch SAS/SATA drives. Drive bays 1 and 2 support NVMe SSDs. A size-converter
drive sled is required to hold 2.5-inch SSDs.
External Features
This topic shows the external features of the server versions.
2 Drive bays 1 and 2 support NVMe PCIe SSDs. 8 Power supply status LED
A size-converter drive sled is required if 2.5-inch
SSDs are used.
3 Dual 1-Gb/10-Gb Ethernet ports (LAN1 and 9 PCIe riser 2/slot 2 (x16 lane)
LAN2)
Includes PCIe cable connectors for front-loading
The dual LAN ports can support 1 Gbps and 10 NVMe SSDs (x8 lane)
Gbps, depending on the link partner capability.
4 VGA video port (DB-15 connector) 10 PCIe riser 1/slot 1 (x16 lane)
5 1-Gb Ethernet dedicated management port 11 Threaded holes for dual-hole grounding lug
1 Front-loading drive bays 1–10 support SAS/SATA 10 Power supplies (hot-swappable when redundant as
drives. 1+1)
• UCSC-220-M5SX: Drive bays 1 and 2
support NVMe PCIe SSDs.
• UCSC-220-M5SN: Drive bays 1 – 10 support
only NVMe PCIe SSDs.
• UCSC-220-M5L: Drive bays 1 and 2 support
NVMe PCIe SSDs.
2 Cooling fan modules (seven, hot-swappable) 11 Trusted platform module (TPM) socket on
motherboard (not visible in this view)
3 Supercap unit mounting bracket (RAID backup) 12 PCIe riser 2/slot 2 (half-height, x16 lane)
Includes PCIe cable connectors for front-loading
NVMe SSDs (x8 lane)
4 DIMM sockets on motherboard (12 per CPU) 13 PCIe riser 1/slot 1 (full-height, x16 lane)
Includes socket for Micro-SD card
5 CPUs and heatsinks (up to two) 14 Modular LOM (mLOM) card bay on chassis floor
(x16 PCIe lane), not visible in this view
6 Mini storage module socket 15 Modular RAID (mRAID) riser, can optionally be a
riser that supports either:
Supports either an SD card module with two SD
card slots; or an M.2 module with two NVMe or • Hardware RAID controller card
SATA M.2 SSD slots.
• Interposer card for embedded SATA RAID
7 Chassis intrusion switch (optional) 16 PCIe cable connectors for front-loading NVMe SSDs
on PCIe riser 2
8 Internal USB 3.0 port on motherboard 17 Micro-SD card socket on PCIe riser 1
The Technical Specifications Sheets for all versions of this server, which include supported component part
numbers, are at Cisco UCS Servers Technical Specifications Sheets (scroll down to Technical Specifications).
Feature Description
Central Processor Up to two CPUs from the Intel Xeon Processor Scalable Family.
This includes CPUs from the following series:
• Intel Xeon Bronze 3XXX Processors
• Intel Xeon Silver 4XXX Processors
• Intel Xeon Gold 5XXX Processors
• Intel Xeon Gold 6XXX Processors
• Intel Xeon Platinum 8XXX Processors
Feature Description
Front panel:
• One front-panel keyboard/video/mouse (KVM) connector
that is used with the KVM cable, which provides two USB
2.0, one VGA, and one DB-9 serial connector.
Modular LOM One dedicated socket (x16 PCIe lane) that can be used to add an
mLOM card for additional rear-panel connectivity.
WoL The two 1-Gb/10-Gb BASE-T Ethernet LAN ports support the
wake-on-LAN (WoL) standard.
PCIe I/O Two horizontal PCIe expansion slots on a PCIe riser assembly.
See PCIe Slot Specifications, on page 77 for specifications of the
slots.
InfiniBand The PCIe bus slots in this server support the InfiniBand
architecture.
Feature Description
Storage, front-panel The server is orderable in three different versions, each with a
different front panel/drive-backplane configuration.
• Cisco UCS C220 M5 (UCSC-220-M5SX)—Small
form-factor (SFF) drives, with 10-drive backplane. Supports
up to 10 2.5-inch SAS/SATA drives. Drive bays 1 and 2
support NVMe SSDs.
• Cisco UCS C220 M5 (UCSC-220-M5SN)—SFF drives, with
10-drive backplane. Supports up to 10 2.5-inch NVMe-only
SSDs in drive bays 1-10.
• Cisco UCS C220 M5 (UCSC-220-M5L)—Large form-factor
(LFF) drives, with four-drive backplane. Supports up to four
3.5-inch SAS/SATA drives. Drive bays 1 and 2 support
NVMe SSDs. A size-converter drive sled is required to hold
2.5-inch SSDs.
Storage management The server has a dedicated internal mRAID riser that supports
one of the following storage-controller options:
• A PCIe-style Cisco modular RAID controller card
(SAS/SATA).
• A PCIe-style interposer card for the server’s embedded
SATA RAID controller.
RAID backup The server has a mounting bracket near the cooling fans for the
supercap unit that is used with the Cisco modular RAID controller
card.
Note Before you install, operate, or service a server, review the Regulatory Compliance and Safety Information for
Cisco UCS C-Series Servers for important safety information.
Warning To prevent the system from overheating, do not operate it in an area that exceeds the maximum
recommended ambient temperature of: 35° C (95° F).
Statement 1047
Warning The plug-socket combination must be accessible at all times, because it serves as the main disconnecting
device.
Statement 1019
Warning This product relies on the building’s installation for short-circuit (overcurrent) protection. Ensure that
the protective device is rated not greater than: 250 V, 15 A.
Statement 1005
Warning Installation of the equipment must comply with local and national electrical codes.
Statement 1074
Warning This unit is intended for installation in restricted access areas. A restricted access area can be accessed
only through the use of a special tool, lock, and key, or other means of security.
Statement 1017
Caution To ensure proper airflow it is necessary to rack the servers using rail kits. Physically placing the units on top
of one another or “stacking” without the use of the rail kits blocks the air vents on top of the servers, which
could result in overheating, higher fan speeds, and higher power consumption. We recommend that you mount
your servers on rail kits when you are installing them into the rack because these rails provide the minimal
spacing required between the servers. No additional spacing between the servers is required when you mount
the units using rail kits.
Caution Avoid uninterruptible power supply (UPS) types that use ferroresonant technology. These UPS types can
become unstable with systems such as the Cisco UCS, which can have substantial current draw fluctuations
from fluctuating data traffic patterns.
• Ensure that there is adequate space around the server to allow for accessing the server and for adequate
airflow. The airflow in this server is from front to back.
• Ensure that the air-conditioning meets the thermal requirements listed in the Environmental Specifications,
on page 103.
• Ensure that the cabinet or rack meets the requirements listed in the Rack Requirements, on page 11.
• Ensure that the site power meets the power requirements listed in the Power Specifications, on page 104.
If available, you can use an uninterruptible power supply (UPS) to protect against power failures.
Rack Requirements
The rack must be of the following type:
• A standard 19-in. (48.3-cm) wide, four-post EIA rack, with mounting posts that conform to English
universal hole spacing, per section 1 of ANSI/EIA-310-D-1992.
• The rack-post holes can be square 0.38-inch (9.6 mm), round 0.28-inch (7.1 mm), #12-24 UNC, or #10-32
UNC when you use the Cisco-supplied slide rails.
• The minimum vertical rack space per server must be one rack unit (RU), equal to 1.75 in. (44.45 mm).
Warning To prevent bodily injury when mounting or servicing this unit in a rack, you must take special
precautions to ensure that the system remains stable. The following guidelines are provided to ensure
your safety:
This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the
heaviest component at the bottom of the rack.
If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing the
unit in the rack.
Statement 1006
Step 2 Open the front securing plate on both slide-rail assemblies. The front end of the slide-rail assembly has a spring-loaded
securing plate that must be open before you can insert the mounting pegs into the rack-post holes.
On the outside of the assembly, push the green-arrow button toward the rear to open the securing plate.
1 Front mounting pegs 3 Securing plate shown pulled back to the open
position
Step 5 (Optional) Secure the server in the rack more permanently by using the two screws that are provided with the slide rails.
Perform this step if you plan to move the rack with servers installed.
With the server fully pushed into the slide rails, open a hinged slam latch lever on the front of the server and insert a
screw through the hole that is under the lever. The screw threads into the static part of the rail on the rack post and prevents
the server from being pulled out. Repeat for the opposite slam latch.
Note The cable management arm (CMA) is reversible left-to-right. To reverse the CMA, see Reversing the Cable
Management Arm (Optional), on page 15 before installation.
Step 1 With the server pushed fully into the rack, slide the CMA tab of the CMA arm that is farthest from the server onto the
end of the stationary slide rail that is attached to the rack post. Slide the tab over the end of the rail until it clicks and
locks.
Figure 8: Attaching the CMA to the Rear Ends of the Slide Rails
1 CMA tab on arm farthest from server attaches 3 CMA tab on width-adjustment slider attaches
to end of stationary outer slide rail. to end of stationary outer slide rail.
Step 2 Slide the CMA tab that is closest to the server over the end of the inner rail that is attached to the server. Slide the tab
over the end of the rail until it clicks and locks
Step 3 Pull out the width-adjustment slider that is at the opposite end of the CMA assembly until it matches the width of your
rack.
Step 4 Slide the CMA tab that is at the end of the width-adjustment slider onto the end of the stationary slide rail that is attached
to the rack post. Slide the tab over the end of the rail until it clicks and locks.
Step 5 Open the hinged flap at the top of each plastic cable guide and route your cables through the cable guides as desired.
Step 1 Rotate the entire CMA assembly 180 degrees, left-to-right. The plastic cable guides must remain pointing upward.
Step 2 Flip the tabs at the ends of the CMA arms so that they point toward the rear of the server.
Step 3 Pivot the tab that is at the end of the width-adjustment slider. Depress and hold the metal button on the outside of the tab
and pivot the tab 180 degrees so that it points toward the rear of the server.
Note This section describes how to power on the server, assign an IP address, and connect to server management
when using the server in standalone mode. To use the server in Cisco UCS Manager integration, specific
cabling and settings are required. See Installation For Cisco UCS Manager Integration, on page 139.
Connection Methods
There are two methods for connecting to the system for initial setup:
• Local setup—Use this procedure if you want to connect a keyboard and monitor directly to the system
for setup. This procedure can use a KVM cable (Cisco PID N20-BKVM) or the ports on the rear of the
server.
• Remote setup—Use this procedure if you want to perform setup through your dedicated management
LAN.
Note To configure the system remotely, you must have a DHCP server on the same
network as the system. Your DHCP server must be preconfigured with the range
of MAC addresses for this server node. The MAC address is printed on a label
that is on the pull-out asset tag on the front panel. This server node has a range
of six MAC addresses assigned to the Cisco IMC. The MAC address printed on
the label is the beginning of the range of six contiguous MAC addresses.
Step 1 Attach a power cord to each power supply in your server, and then attach each power cord to a grounded power outlet.
Wait for approximately two minutes to let the server boot to standby power during the first bootup. You can verify system
power status by looking at the system Power Status LED on the front panel. The system is in standby power mode when
the LED is amber.
Step 2 Connect a USB keyboard and VGA monitor to the server using one of the following methods:
• Connect an optional KVM cable (Cisco PID N20-BKVM) to the KVM connector on the front panel. Connect your
USB keyboard and VGA monitor to the KVM cable.
• Connect a USB keyboard and VGA monitor to the corresponding connectors on the rear panel.
Step 4 Continue with Setting Up the System With the Cisco IMC Configuration Utility, on page 19.
Note To configure the system remotely, you must have a DHCP server on the same network as the system. Your
DHCP server must be preconfigured with the range of MAC addresses for this server node. The MAC address
is printed on a label that is on the pull-out asset tag on the front panel. This server node has a range of six
MAC addresses assigned to the Cisco IMC. The MAC address printed on the label is the beginning of the
range of six contiguous MAC addresses.
Step 1 Attach a power cord to each power supply in your server, and then attach each power cord to a grounded power outlet.
Wait for approximately two minutes to let the server boot to standby power during the first bootup. You can verify system
power status by looking at the system Power Status LED on the front panel. The system is in standby power mode when
the LED is amber.
Step 2 Plug your management Ethernet cable into the dedicated management port on the rear panel.
Step 3 Allow your preconfigured DHCP server to assign an IP address to the server node.
Step 4 Use the assigned IP address to access and log in to the Cisco IMC for the server node. Consult with your DHCP server
administrator to determine the IP address.
Note The default user name for the server is admin. The default password is password.
Step 5 From the Cisco IMC Server Summary page, click Launch KVM Console. A separate KVM console window opens.
Step 6 From the Cisco IMC Summary page, click Power Cycle Server. The system reboots.
Step 7 Select the KVM console window.
Note The KVM console window must be the active window for the following keyboard actions to work.
Step 8 When prompted, press F8 to enter the Cisco IMC Configuration Utility. This utility opens in the KVM console window.
Note The first time that you enter the Cisco IMC Configuration Utility, you are prompted to change the default
password. The default password is password. The Strong Password feature is enabled.
Step 9 Continue with Setting Up the System With the Cisco IMC Configuration Utility, on page 19.
Step 1 Set the NIC mode to choose which ports to use to access Cisco IMC for server management:
• Shared LOM EXT (default)—This is the shared LOM extended mode, the factory-default setting. With this mode,
the Shared LOM and Cisco Card interfaces are both enabled. You must select the default Active-Active NIC
redundancy setting in the following step.
In this NIC mode, DHCP replies are returned to both the shared LOM ports and the Cisco card ports. If the system
determines that the Cisco card connection is not getting its IP address from a Cisco UCS Manager system because
the server is in standalone mode, further DHCP requests from the Cisco card are disabled. Use the Cisco Card
NIC mode if you want to connect to Cisco IMC through a Cisco card in standalone mode.
• Shared LOM—The 1-Gb/10-Gb Ethernet ports are used to access Cisco IMC. You must select either the
Active-Active or Active-standby NIC redundancy setting in the following step.
• Dedicated—The dedicated management port is used to access Cisco IMC. You must select the None NIC redundancy
setting in the following step.
• Cisco Card—The ports on an installed Cisco UCS Virtual Interface Card (VIC) are used to access the Cisco IMC.
You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.
See also the required VIC Slot setting below.
• VIC Slot—Only if you use the Cisco Card NIC mode, you must select this setting to match where your VIC is
installed. The choices are Riser1, Riser2, or Flex-LOM (the mLOM slot).
Step 2 Set the NIC redundancy to your preference. This server has three possible NIC redundancy settings:
• None—The Ethernet ports operate independently and do not fail over if there is a problem. This setting can be
used only with the Dedicated NIC mode.
• Active-standby—If an active Ethernet port fails, traffic fails over to a standby port. Shared LOM and Cisco Card
modes can each use either Active-standby or Active-active settings.
• Active-active (default)—All Ethernet ports are utilized simultaneously. The Shared LOM EXT mode must use
only this NIC redundancy setting. Shared LOM and Cisco Card modes can each use either Active-standby or
Active-active settings.
Step 3 Choose whether to enable DHCP for dynamic network settings, or to enter static network settings.
Note Before you enable DHCP, you must preconfigure your DHCP server with the range of MAC addresses for
this server. The MAC address is printed on a label on the rear of the server. This server has a range of six
MAC addresses assigned to Cisco IMC. The MAC address printed on the label is the beginning of the range
of six contiguous MAC addresses.
Step 10 (Optional) Enable auto-negotiation of port settings or set the port speed and duplex mode manually.
Note Auto-negotiation is applicable only when you use the Dedicated NIC mode. Auto-negotiation sets the port
speed and duplex mode automatically based on the switch port to which the server is connected. If you disable
auto-negotiation, you must set the port speed and duplex mode manually.
What to do next
Use a browser and the IP address of the Cisco IMC to connect to the Cisco IMC management interface. The
IP address is based upon the settings that you made (either a static address or the address assigned by your
DHCP server).
Note The factory default username for the server is admin. The default password is password.
To manage the server, see the Cisco UCS C-Series Rack-Mount Server Configuration Guide or the Cisco UCS
C-Series Rack-Mount Server CLI Configuration Guide for instructions on using those interfaces for your
Cisco IMC release. The links to the configuration guides are in the Cisco UCS C-Series Documentation
Roadmap.
Dedicated None
This server has the following NIC mode settings that you can choose from:
• Shared LOM EXT (default)—This is the shared LOM extended mode, the factory-default setting. With
this mode, the Shared LOM and Cisco Card interfaces are both enabled. You must select the default
Active-Active NIC redundancy setting in the following step.
In this NIC mode, DHCP replies are returned to both the shared LOM ports and the Cisco card ports. If
the system determines that the Cisco card connection is not getting its IP address from a Cisco UCS
Manager system because the server is in standalone mode, further DHCP requests from the Cisco card
are disabled. Use the Cisco Card NIC mode if you want to connect to Cisco IMC through a Cisco card
in standalone mode.
• Shared LOM—The 1-Gb/10-Gb Ethernet ports are used to access Cisco IMC. You must select either the
Active-Active or Active-standby NIC redundancy setting in the following step.
• Dedicated—The dedicated management port is used to access Cisco IMC. You must select the None
NIC redundancy setting in the following step.
• Cisco Card—The ports on an installed Cisco UCS Virtual Interface Card (VIC) are used to access the
Cisco IMC. You must select either the Active-Active or Active-standby NIC redundancy setting in the
following step.
See also the required VIC Slot setting below.
• VIC Slot—Only if you use the Cisco Card NIC mode, you must select this setting to match where your
VIC is installed. The choices are Riser1, Riser2, or Flex-LOM (the mLOM slot).
• If you select Riser1, you must install the VIC in slot 1.
• If you select Riser2, you must install the VIC in slot 2.
• If you select Flex-LOM, you must install an mLOM-style VIC in the mLOM slot.
This server has the following NIC redundancy settings that you can choose from:
• None—The Ethernet ports operate independently and do not fail over if there is a problem. This setting
can be used only with the Dedicated NIC mode.
• Active-standby—If an active Ethernet port fails, traffic fails over to a standby port. Shared LOM and
Cisco Card modes can each use either Active-standby or Active-active settings.
• Active-active (default)—All Ethernet ports are utilized simultaneously. The Shared LOM EXT mode
must use only this NIC redundancy setting. Shared LOM and Cisco Card modes can each use either
Active-standby or Active-active settings.
Caution When you upgrade the BIOS firmware, you must also upgrade the Cisco IMC firmware to the same version
or the server does not boot. Do not power off the server until the BIOS and Cisco IMC firmware are matching
or the server does not boot.
Cisco provides the Cisco Host Upgrade Utility to assist with simultaneously upgrading the BIOS, Cisco IMC,
and other firmware to compatible levels.
The server uses firmware obtained from and certified by Cisco. Cisco provides release notes with each firmware
image. There are several possible methods for updating the firmware:
• Recommended method for firmware update: Use the Cisco Host Upgrade Utility to simultaneously
upgrade the Cisco IMC, BIOS, and component firmware to compatible levels.
See the Cisco Host Upgrade Utility Quick Reference Guide for your firmware release at the documentation
roadmap link below.
• You can upgrade the Cisco IMC and BIOS firmware by using the Cisco IMC GUI interface.
See the Cisco UCS C-Series Rack-Mount Server Configuration Guide.
• You can upgrade the Cisco IMC and BIOS firmware by using the Cisco IMC CLI interface.
See the Cisco UCS C-Series Rack-Mount Server CLI Configuration Guide.
For links to the documents listed above, see the Cisco UCS C-Series Documentation Roadmap.
Caution If your system is running Cisco IMC 4.0(1b) or later, and you have the latest NAND flash chip
MT29F4G08ABAFAWP-IT:F (M70A), do not downgrade the Cisco IMC to an earlier version. Earlier versions
of the BMC cannot detect this latest NAND Flash chip.
Cisco IMC 4.0(1a) supports only the original Micron BMC (MT29F4G08ABADAWP-IT:D).
Cisco IMC 4.0(1b) supports the original Micron BMC (MT29F4G08ABADAWP-IT:D) and the new Micron
BMC (MT29F4G08ABAFAWP-IT:F (M70A)).
Step 2 Use the arrow keys to select the BIOS menu page.
Step 3 Highlight the field to be modified by using the arrow keys.
Step 4 Press Enter to select the field that you want to change, and then modify the value in the field.
Step 5 Press the right arrow key until the Exit menu screen is displayed.
Step 6 Follow the instructions on the Exit menu screen to save your changes and exit the setup utility (or press F10). You can
exit without saving changes by pressing Esc.
Note You cannot switch to Cisco IMC CLI if the serial-over-LAN (SOL) feature is
enabled.
• After a session is created, it is shown in the CLI or web GUI by the name serial.
Note Any mouse or keyboard that is connected to the KVM cable is disconnected when
you enable Smart Access USB.
• You can use USB 3.0-based devices, but they will operate at USB 2.0 speed.
• We recommend that the USB device have only one partition.
• The file system formats supported are: FAT16, FAT32, MSDOS, EXT2, EXT3, and EXT4. NTFS
is not supported.
• The front-panel KVM connector has been designed to switch the USB port between Host OS and BMC.
• Smart Access USB can be enabled or disabled using any of the BMC user interfaces. For example, you
can use the Cisco IMC Configuration Utility that is accessed by pressing F8 when prompted during
bootup.
• Enabled: the front-panel USB device is connected to the BMC.
• In a case where no management network is available to connect remotely to Cisco IMC, a Device Firmware
Update (DFU) shell over serial cable can be used to generate and download technical support files to the
USB device that is attached to front panel USB port.
Front-Panel LEDs
Figure 10: Front Panel LEDs
2 SAS/SATA drive activity LED • Off—There is no hard drive in the hard drive tray (no
access, no fault).
SAS
• Green—The hard drive is ready.
• Green, blinking—The hard drive is reading or writing
data.
1 NVMe SSD drive fault • Off—The drive is not in use and can be safely
removed.
NVMe Note NVMe solid state drive (SSD) drive tray
LEDs have different behavior than • Green—The drive is in use and functioning properly.
SAS/SATA drive trays.
• 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.
Rear-Panel LEDs
Figure 11: Rear Panel LEDs
1 1-Gb/10-Gb Ethernet link speed (on both LAN1 and • Amber—Link speed is 100 Mbps.
LAN2)
• Amber—Link speed is 1 Gbps.
• Green—Link speed is 10 Gbps.
2 1-Gb/10-Gb Ethernet link status (on both LAN1 and • Off—No link is present.
LAN2)
• Green—Link is active.
• Green, blinking—Traffic is present on the active link.
6 Power supply status (one LED each power supply unit) AC power supplies:
• Off—No AC input (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-current, over-voltage,
or over-temperature failure).
DC power supplies:
• Off—No DC input (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-current, over-voltage,
or over-temperature failure).
1 Fan module fault LEDs (one behind each fan 3 DIMM fault LEDs (one behind each DIMM socket
connector on the motherboard) on the motherboard)
• Amber—Fan has a fault or is not fully seated. These LEDs operate only when the server is in
standby power mode.
• Green—Fan is OK.
• Amber—DIMM has a fault.
• Off—DIMM is OK.
• T-30 Torx driver (supplied with replacement CPUs for heatsink removal)
• #1 flat-head screwdriver (supplied with replacement CPUs for heatsink removal)
• #1 Phillips-head screwdriver (for M.2 SSD and intrusion switch replacement)
• Electrostatic discharge (ESD) strap or other grounding equipment such as a grounded mat
Caution After a server is shut down to standby power, electric current is still present in the server. To completely
remove power as directed in some service procedures, you must disconnect all power cords from all power
supplies in the server.
You can shut down the server by using the front-panel power button or the software management interfaces.
Step 3 If a service procedure instructs you to completely remove power from the server, disconnect all power cords from the
power supplies in the server.
Step 5 If a service procedure instructs you to completely remove power from the server, disconnect all power cords from the
power supplies in the server.
Step 3 If a service procedure instructs you to completely remove power from the server, disconnect all power cords from the
power supplies in the server.
Step 7 If a service procedure instructs you to completely remove power from the server, disconnect all power cords from the
power supplies in the server.
Step 8 If a service procedure instructs you to completely remove power from the server, disconnect all power cords from the
power supplies in the server.
• Hot-plug replacement—You must take the component offline before removing it for the following
component:
• NVMe PCIe solid state drives
Warning 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
Caution 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.
Tip You can press the unit identification button on the front panel or rear panel to turn on a flashing, blue unit
identification LED on both the front and rear panels of the server. This button allows you to locate the specific
server that you are servicing when you go to the opposite side of the rack. You can also activate these LEDs
remotely by using the Cisco IMC interface.
1 Front-loading drive bays 1–10 support SAS/SATA 10 Power supplies (hot-swappable when redundant as
drives. 1+1)
• UCSC-220-M5SX: Drive bays 1 and 2
support NVMe PCIe SSDs.
• UCSC-220-M5SN: Drive bays 1 – 10 support
only NVMe PCIe SSDs.
• UCSC-220-M5L: Drive bays 1 and 2 support
NVMe PCIe SSDs.
2 Cooling fan modules (seven, hot-swappable) 11 Trusted platform module (TPM) socket on
motherboard (not visible in this view)
3 Supercap unit mounting bracket (RAID backup) 12 PCIe riser 2/slot 2 (half-height, x16 lane)
Includes PCIe cable connectors for front-loading
NVMe SSDs (x8 lane)
4 DIMM sockets on motherboard (12 per CPU) 13 PCIe riser 1/slot 1 (full-height, x16 lane)
Includes socket for Micro-SD card
5 CPUs and heatsinks (up to two) 14 Modular LOM (mLOM) card bay on chassis floor
(x16 PCIe lane), not visible in this view
6 Mini storage module socket 15 Modular RAID (mRAID) riser, can optionally be a
riser that supports either:
Supports either an SD card module with two SD
card slots; or an M.2 module with two NVMe or • Hardware RAID controller card
SATA M.2 SSD slots.
• Interposer card for embedded SATA RAID
7 Chassis intrusion switch (optional) 16 PCIe cable connectors for front-loading NVMe SSDs
on PCIe riser 2
8 Internal USB 3.0 port on motherboard 17 Micro-SD card socket on PCIe riser 1
The Technical Specifications Sheets for all versions of this server, which include supported component part
numbers, are at Cisco UCS Servers Technical Specifications Sheets (scroll down to Technical Specifications).
Note You do not have to shut down the server or drive to replace SAS/SATA hard drives or SSDs because they
are hot-swappable. To replace an NVMe PCIe SSD drive, which must be shut down before removal, see
Replacing a Front-Loading NVMe SSD, on page 42.
Procedure
Step 1 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 Boot Mode to UEFI Mode.
Step 4 Under Boot Option Priorities, set your OS installation media (such as a virtual DVD) as your Boot Option #1.
Step 5 Press F10 to save changes and exit the BIOS setup utility. Allow the server to reboot.
Step 6 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.
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.
Figure 17: Replacing a Drive in a Drive Tray
HHHL form-factor SSDs is an invalid configuration. A valid configuration is two HGST NVMe SFF
2.5-inch SSDs and two HGST HHHL form-factor SSDs.
• UEFI boot is supported in all supported operating systems. Hot-insertion and hot-removal are supported
in all supported operating systems except VMWare ESXi.
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.
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.
Note 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 43.
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.
Step 1 Connect the two connectors on one end of the cable to the PCIE-A1 and PCIE-A2 connectors on the drive backplane.
Step 2 Route the cables through the chassis cable guides to the rear of the server as shown below.
Step 3 Connect the single connector on the other end of the cable to the PCIE-FRONT connector on PCIe riser 2.
Figure 19: PCIe Cabling to Drive Backplane
Step 1 Remove an existing HHHL form-factor NVME SSD (or a blank filler panel) from the PCIe riser:
a) Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33.
b) Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
c) Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
d) Use two hands to grasp the external riser handle and the blue area at the front of the riser.
e) Open the hinged, plastic card retainer that secures the rear-panel tab of the card.
f) Pull evenly on both ends of the HHHL form-factor NVME SSD to remove it from the socket on the PCIe riser.
If the riser has no SSD, remove the blanking panel from the rear opening of the riser.
1 PCIe slot 1 rear-panel opening 4 Hinged card retainer (one each slot)
Tip Each fan module has a fault LED next to the fan connector on the motherboard. This LED lights 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.
Caution You do not have to shut down or remove power from the server to replace fan modules because they are hot-
swappable. However, to maintain proper cooling, do not operate the server for more than one minute with
any fan module removed.
Caution DIMMs and their sockets are fragile and must be handled with care to avoid damage during installation.
Caution Cisco does not support third-party DIMMs. Using non-Cisco DIMMs in the server might result in system
problems or damage to the motherboard.
Note To ensure the best server performance, it is important that you are familiar with memory performance guidelines
and population rules before you install or replace DIMMs.
• Each channel has two DIMM sockets (for example, channel A = slots A1, A2).
• In a single-CPU configuration, populate the channels for CPU1 only (A, B, C, D, E, F).
• For optimal performance, populate DIMMs in the order shown in the following table, depending on the
number of CPUs and the number of DIMMs per CPU. If your server has two CPUs, balance DIMMs
evenly across the two CPUs as shown in the table.
Note The table below lists recommended configurations. Using 5, 7, 9, 10, or 11 DIMMs
per CPU is not recommended.
1 (A1) - (G1) -
8 (A1, B1); (D1, E1) (A2, B2); (D2, E2) (G1, H1); (K1, L1) (G2, H2); (K2, L2)
12 (A1, B1); (C1, D1); (A2, B2); (C2, D2); (G1, H1); (J1, K1); (G2, H2); (J2, K2);
(E1, F1) (E2, F2) (L1, M1) (L2, M2)
• The maximum combined memory allowed in the 12 DIMM slots controlled by any one CPU is 768 GB.
To populate the 12 DIMM slots with more than 768 GB of combined memory, you must use a
high-memory CPU that has a PID that ends with an "M", for example, UCS-CPU-6134M.
• Memory mirroring reduces the amount of memory available by 50 percent because only one of the two
populated channels provides data. When memory mirroring is enabled, you must install DIMMs in even
numbers of channels.
• The NVIDIA Tesla P-Series GPU can support more than 1 TB of memory in the server. All other NVIDIA
GPUs (M-Series) can support only 1 TB or less of memory in the server.
• Observe the DIMM mixing rules shown in the following table.
DIMM Parameter DIMMs in the Same Channel DIMMs in the Same Bank
DIMM Capacity You can mix different capacity You cannot mix DIMM capacities in
DIMMs in the same channel (for a bank (for example A1, B1). Pairs of
For example, 8GB, 16GB,
example, A1, A2). DIMMs must be identical (same PID
32GB, 64GB, 128GB
and revision).
DIMM speed You can mix speeds, but DIMMs You cannot mix DIMM speeds in a
will run at the speed of the slowest bank (for example A1, B1). Pairs of
For example, 2666 GHz
DIMMs/CPUs installed in the DIMMs must be identical (same PID
channel. and revision).
DIMM type You cannot mix DIMM types in a You cannot mix DIMM types in a
channel. bank.
RDIMMs or LRDIMMs
Memory Mirroring
The CPUs in the server support memory mirroring only when an even number of channels are populated with
DIMMs. If one or three channels are populated with DIMMs, memory mirroring is automatically disabled.
Memory mirroring reduces the amount of memory available by 50 percent because only one of the two
populated channels provides data. The second, duplicate channel provides redundancy.
Replacing DIMMs
Identifying a Faulty DIMM
Each DIMM socket has a corresponding DIMM fault LED, directly in front of the DIMM socket. See Internal
Diagnostic LEDs, on page 31 for the locations of these LEDs. When the server is in standby power mode,
these LEDs light amber to indicate a faulty DIMM.
b) Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
c) Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
d) Remove the air baffle that covers the front ends of the DIMM slots to provide clearance.
e) Locate the DIMM that you are removing, and then open the ejector levers at each end of its DIMM slot.
Step 2 Install a new DIMM:
Note Before installing DIMMs, see the memory population rules for this server: DIMM Population Rules and Memory
Performance Guidelines, on page 49.
a) Align the new DIMM with the empty slot on the motherboard. Use the alignment feature in the DIMM slot to correctly
orient the DIMM.
b) Push down evenly on the top corners of the DIMM until it is fully seated and the ejector levers on both ends lock
into place.
c) Replace the top cover to the server.
d) Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
See also Additional CPU-Related Parts to Order with RMA Replacement CPUs, on page 59.
Caution CPUs and their sockets are fragile and must be handled with extreme care to avoid damaging pins. The CPUs
must be installed with heatsinks and thermal interface material to ensure cooling. Failure to install a CPU
correctly might result in damage to the server.
e) Lift straight up on the CPU/heatsink assembly and set it heatsink-down on an antistatic surface.
Step 2 Separate the heatsink from the CPU assembly (the CPU assembly includes the CPU and the CPU carrier):
a) Place the heatsink with CPU assembly so that it is oriented upside-down as shown below.
Note the thermal-interface material (TIM) breaker location. TIM BREAKER is stamped on the CPU carrier next to
a small slot.
b) Pinch inward on the CPU-carrier inner-latch that is nearest the TIM breaker slot and then push up to disengage the
clip from its slot in the heatsink corner.
c) Insert the blade of a #1 flat-head screwdriver into the slot marked TIM BREAKER.
Caution In the following step, do not pry on the CPU surface. Use gentle rotation to lift on the plastic surface of the
CPU carrier at the TIM breaker slot. Use caution to avoid damaging the heatsink surface.
d) Gently rotate the screwdriver to lift up on the CPU until the TIM on the heatsink separates from the CPU.
Note Do not allow the screwdriver tip to touch or damage the green CPU substrate.
e) Pinch the CPU-carrier inner-latch at the corner opposite the TIM breaker and push up to disengage the clip from its
slot in the heatsink corner.
f) On the remaining two corners of the CPU carrier, gently pry outward on the outer-latches and then lift the
CPU-assembly from the heatsink.
Note Handle the CPU-assembly by the plastic carrier only. Do not touch the CPU surface. Do not separate the
CPU from the carrier.
Step 3 The new CPU assembly is shipped on a CPU assembly tool. Take the new CPU assembly and CPU assembly tool out of
the carton.
If the CPU assembly and CPU assembly tool become separated, note the alignment features shown below for correct
orientation. The pin 1 triangle on the CPU carrier must be aligned with the angled corner on the CPU assembly tool.
Caution CPUs and their sockets are fragile and must be handled with extreme care to avoid damaging pins.
Figure 24: CPU Assembly Tool, CPU Assembly, and Heatsink Alignment Features
2 CPU assembly (CPU in plastic carrier) 5 Triangle cut into carrier (pin 1 alignment
feature)
• If you are installing a new heatsink, it is shipped with a pre-applied pad of TIM. Go to step 5.
• If you are reusing a heatsink, you must remove the old TIM from the heatsink and then apply new TIM to the CPU
surface from the supplied syringe. Continue with step a below.
a) Apply the cleaning solution that is included with the heatsink cleaning kit (UCSX-HSCK=) to the old TIM on the
heatsink and let it soak for a least 15 seconds.
b) Wipe all of the TIM off the heatsink using the soft cloth that is included with the heatsink cleaning kit. Be careful to
avoid scratching the heatsink surface.
c) Using the syringe of TIM provided with the new CPU (UCS-CPU-TIM=), apply 4 cubic centimeters of thermal
interface material to the top of the CPU. Use the pattern shown below to ensure even coverage.
Figure 25: Thermal Interface Material Application Pattern
Caution Use only the correct heatsink for your CPUs to ensure proper cooling. There are two different heatsinks:
UCSC-HS-C220M5= for standard-performance CPUs 150 W and less; UCSC-HS2-C220M5= for
high-performance CPUs above 150 W. Note the wattage described on the heatsink label.
Step 5 With the CPU assembly on the CPU assembly tool, set the heatsink onto the CPU assembly. Note the pin 1 alignment
features for correct orientation. Push down gently until you hear the corner clips of the CPU carrier click onto the heatsink
corners.
Caution In the following step, use extreme care to avoid touching or damaging the CPU contacts or the CPU socket
pins.
2 CPU socket alignment post (two) 5 Angled corner on socket (pin 1 alignment
feature)
c) Set the heatsink with CPU assembly down onto the CPU socket.
d) Use the T-30 Torx driver that is supplied with the replacement CPU to tighten the four captive nuts that secure the
heatsink to the motherboard standoffs.
Caution Alternate tightening the heatsink nuts evenly so that the heatsink remains level while it is lowered. Tighten
the heatsink nuts in the order shown on the heatsink label: 1, 2, 3, 4. The captive nuts must be fully tightened
so that the leaf springs on the CPU socket lie flat.
e) Replace the top cover to the server.
f) Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
Note The following items apply to CPU replacement scenarios. If you are replacing a system chassis and moving
existing CPUs to the new motherboard, you do not have to separate the heatsink from the CPU. See Additional
CPU-Related Parts to Order with RMA Replacement System Chassis, on page 59.
Caution Use only the correct heatsink for your CPUs to ensure proper cooling. There are
two different heatsinks: UCSC-HS-C220M5= for CPUs 150 W and less;
UCSC-HS2-C220M5= for CPUs above 150 W.
• Heatsink: UCSC-HS-C220M5= for CPUs 150 W and less; UCSC-HS2-C220M5= for CPUs above
150 W
• Heatsink cleaning kit (UCSX-HSCK=)
• Scenario 3—You have a damaged CPU carrier (the plastic frame around the CPU):
• CPU Carrier: UCS-M5-CPU-CAR=
• #1 flat-head screwdriver (for separating the CPU from the heatsink)
• Heatsink cleaning kit (UCSX-HSCK=)
• Thermal interface material (TIM) kit for M5 servers (UCS-CPU-TIM=)
A CPU heatsink cleaning kit is good for up to four CPU and heatsink cleanings. The cleaning kit contains
two bottles of solution, one to clean the CPU and heatsink of old TIM and the other to prepare the surface of
the heatsink.
New heatsink spares come with a pre-applied pad of TIM. It is important to clean any old TIM off of the CPU
surface prior to installing the heatsinks. Therefore, even when you are ordering new heatsinks, you must order
the heatsink cleaning kit.
Note Unlike previous generation CPUs, the M5 server CPUs do not require you to separate the heatsink from the
CPU when you move the CPU-heatsink assembly. Therefore, no additional heatsink cleaning kit or
thermal-interface material items are required.
• The only tool required for moving a CPU/heatsink assembly is a T-30 Torx driver.
To move a CPU to a new chassis, use the procedure in Moving an M5 Generation CPU, on page 60.
Caution When you receive a replacement server for an RMA, it includes dust covers on all CPU sockets. These covers
protect the socket pins from damage during shipping. You must transfer these covers to the system that you
are returning, as described in this procedure.
Step 1 When moving an M5 CPU to a new server, you do not have to separate the heatsink from the CPU. Perform the following
steps:
a) Use a T-30 Torx driver to loosen the four captive nuts that secure the assembly to the board standoffs.
Note Alternate loosening the heatsink nuts evenly so that the heatsink remains level as it is raised. Loosen the
heatsink nuts in the order shown on the heatsink label: 4, 3, 2, 1.
b) Lift straight up on the CPU/heatsink assembly to remove it from the board.
c) Set the CPUs with heatsinks aside on an anti-static surface.
Step 2 Transfer the CPU socket covers from the new system to the system that you are returning:
a) Remove the socket covers from the replacement system. Grasp the two recessed finger-grip areas marked "REMOVE"
and lift straight up.
Note Keep a firm grasp on the finger-grip areas at both ends of the cover. Do not make contact with the CPU
socket pins.
b) With the wording on the dust cover facing up, set it in place over the CPU socket. Make sure that all alignment posts
on the socket plate align with the cutouts on the cover.
Caution In the next step, do not press down anywhere on the cover except the two points described. Pressing
elsewhere might damage the socket pins.
c) Press down on the two circular markings next to the word "INSTALL" that are closest to the two threaded posts (see
the following figure). Press until you feel and hear a click.
Note You must press until you feel and hear a click to ensure that the dust covers do not come loose during
shipping.
2 CPU socket alignment post (two) 5 Angled corner on socket (pin 1 alignment
feature)
b) On the new board, set the heatsink with CPU assembly down onto the CPU socket.
c) Use a T-30 Torx driver to tighten the four captive nuts that secure the heatsink to the board standoffs.
Note Alternate tightening the heatsink nuts evenly so that the heatsink remains level while it is lowered. Tighten
the heatsink nuts in the order shown on the heatsink label: 1, 2, 3, 4. The captive nuts must be fully tightened
so that the leaf springs on the CPU socket lie flat.
Step 1 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server, on
page 33.
Step 2 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 3 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 4 Remove a carrier from its socket:
a) Locate the mini-storage module carrier in its socket just in front of power supply 1.
b) At each end of the carrier, push outward on the clip that secures the carrier.
c) Lift both ends of the carrier to disengage it from the socket on the motherboard.
d) Set the carrier on an anti-static surface.
Step 5 Install a carrier to its socket:
a) Position the carrier over socket, with the carrier's connector facing down and at the same end as the motherboard
socket. Two alignment pegs must match with two holes on the carrier.
b) Gently push down the socket end of the carrier so that the two pegs go through the two holes on the carrier.
c) Push down on the carrier so that the securing clips click over it at both ends.
Step 6 Replace the top cover to the server.
Step 7 Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
2 Alignment pegs -
Step 1 Power off the server and then remove the mini-storage module carrier from the server as described in Replacing a
Mini-Storage Module Carrier, on page 65.
Step 2 Remove an SD card:
a) Push on the top of the SD card, and then release it to allow it to spring out from the socket.
b) Grasp and remove the SD card from the socket.
Step 3 Install a new SD card:
a) Insert the new SD card into the socket with its label side facing up.
b) Press on the top of the SD card until it clicks in the socket and stays in place.
Step 4 Install the mini-storage module carrier back into the server and then power it on as described in Replacing a Mini-Storage
Module Carrier, on page 65.
Note You cannot control M.2 SATA SSDs in the server with a HW RAID controller.
Step 1 Power off the server and then remove the mini-storage module carrier from the server as described in Replacing a
Mini-Storage Module Carrier, on page 65.
Step 2 Remove an M.2 SSD:
a) Use a #1 Phillips-head screwdriver to remove the single screw that secures the M.2 SSD to the carrier.
b) Remove the M.2 SSD from its socket on the carrier.
Step 3 Install a new M.2 SSD:
a) Angle the M.2 SSD downward and insert the connector-end into the socket on the carrier. The M.2 SSD's label must
face up.
b) Press the M.2 SSD flat against the carrier.
c) Install the single screw that secures the end of the M.2 SSD to the carrier.
Step 4 Install the mini-storage module carrier back into the server and then power it on as described in Replacing a Mini-Storage
Module Carrier, on page 65.
Caution To avoid data loss, we do not recommend that you hot-swap the Micro SD card while it is operating, as
indicated by its activity LED turning amber. The activity LED turns amber when the Micro SD card is updating
or deleting.
1 Location of Micro SD card socket on the top 3 Plastic retainer (push aside to access socket)
of PCIe riser 1
Caution We do not recommend that you hot-swap the internal USB drive while the server is powered on because of
the potential for data loss.
Step 1 Enter the BIOS Setup Utility by pressing the F2 key when prompted during bootup.
Step 2 Navigate to the Advanced tab.
Step 3 On the Advanced tab, select USB Configuration.
Step 4 On the USB Configuration page, select USB Ports Configuration.
Step 5 Scroll to USB Port: Internal, press Enter, and then choose either Enabled or Disabled from the dialog box.
Step 6 Press F10 to save and exit the utility.
Warning There is danger of explosion if the battery is replaced incorrectly. Replace the battery only with the same or
equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufacturer’s
instructions.
[Statement 1015]
The real-time clock (RTC) battery retains system settings when the server is disconnected from power. The
battery type is CR2032. Cisco supports the industry-standard CR2032 battery, which can be ordered from
Cisco (PID N20-MBLIBATT) or purchased from most electronic stores.
This section includes procedures for replacing AC and DC power supply units.
• Replacing AC Power Supplies, on page 73
• Replacing DC Power Supplies, on page 73
• Installing DC Power Supplies (First Time Installation), on page 75
• Grounding for DC Power Supplies, on page 76
Note If you have ordered a server with power supply redundancy (two power supplies), you do not have to power
off the server to replace a power supply because they are redundant as 1+1.
Note Do not mix power supply types or wattages in the server. Both power supplies must be identical.
Step 1 Remove the power supply that you are replacing or a blank panel from an empty bay:
a) Perform one of the following actions:
• If your server has only one power supply, shut down and remove power from the server as described in Shutting
Down and Removing Power From the Server, on page 33.
• If your server has two power supplies, you do not have to shut down the server.
b) Remove the power cord from the power supply that you are replacing.
c) Grasp the power supply handle while pinching the release lever toward the handle.
d) Pull the power supply out of the bay.
Step 2 Install a new power supply:
a) Grasp the power supply handle and insert the new power supply into the empty bay.
b) Push the power supply into the bay until the release lever locks.
c) Connect the power cord to the new power supply.
d) Only if you shut down the server, press the Power button to boot the server to main power mode.
Figure 35: Replacing AC Power Supplies
Note This procedure is for replacing DC power supplies in a server that already has DC power supplies installed.
If you are installing DC power supplies to the server for the first time, see Installing DC Power Supplies (First
Time Installation), on page 75.
Warning A readily accessible two-poled disconnect device must be incorporated in the fixed wiring.
Statement 1022
Warning This product requires short-circuit (overcurrent) protection, to be provided as part of the building
installation. Install only in accordance with national and local wiring regulations.
Statement 1045
Warning Installation of the equipment must comply with local and national electrical codes.
Statement 1074
Note If you are replacing DC power supplies in a server with power supply redundancy (two power supplies), you
do not have to power off the server to replace a power supply because they are redundant as 1+1.
Note Do not mix power supply types or wattages in the server. Both power supplies must be identical.
Step 1 Remove the DC power supply that you are replacing or a blank panel from an empty bay:
a) Perform one of the following actions:
• If you are replacing a power supply in a server that has only one DC power supply, shut down and remove power
from the server as described in Shutting Down and Removing Power From the Server, on page 33.
• If you are replacing a power supply in a server that has two DC power supplies, you do not have to shut down
the server.
b) Remove the power cord from the power supply that you are replacing. Lift the connector securing clip slightly and
then pull the connector from the socket on the power supply.
c) Grasp the power supply handle while pinching the release lever toward the handle.
d) Pull the power supply out of the bay.
Step 2 Install a new DC power supply:
a) Grasp the power supply handle and insert the new power supply into the empty bay.
b) Push the power supply into the bay until the release lever locks.
c) Connect the power cord to the new power supply. Press the connector into the socket until the securing clip clicks
into place.
d) Only if you shut down the server, press the Power button to boot the server to main power mode.
Note This procedure is for installing DC power supplies to the server for the first time. If you are replacing DC
power supplies in a server that already has DC power supplies installed, see Replacing DC Power Supplies,
on page 73.
Warning A readily accessible two-poled disconnect device must be incorporated in the fixed wiring.
Statement 1022
Warning This product requires short-circuit (overcurrent) protection, to be provided as part of the building
installation. Install only in accordance with national and local wiring regulations.
Statement 1045
Warning Installation of the equipment must comply with local and national electrical codes.
Statement 1074
Note Do not mix power supply types or wattages in the server. Both power supplies must be identical.
Caution As instructed in the first step of this wiring procedure, turn off the DC power source from your facility’s
circuit breaker to avoid electric shock hazard.
Step 1 Turn off the DC power source from your facility’s circuit breaker to avoid electric shock hazard.
Note The required DC input cable is Cisco part CAB-48DC-40A-8AWG. This 3-meter cable has a 3-pin connector
on one end that is keyed to the DC input socket on the power supply. The other end of the cable has no connector
so that you can wire it to your facility’s DC power.
Step 2 Wire the non-terminated end of the cable to your facility’s DC power input source.
Step 3 Connect the terminated end of the cable to the socket on the power supply. The connector is keyed so that the wires align
for correct polarity and ground.
Step 4 Return DC power from your facility’s circuit breaker.
Step 5 Press the Power button to boot the server to main power mode.
Figure 37: Installing DC Power Supplies
Step 6 See Installation Grounding, page 3-66 for information about additional chassis grounding.
Note The grounding points on the chassis are sized for M5 screws. You must provide your own screws, grounding
lug, and grounding wire. The grounding lug must be dual-hole lug that fits M5 screws. The grounding cable
that you provide must be 14 AWG (2 mm), minimum 60° C wire, or as permitted by the local code.
Note Cisco supports all PCIe cards qualified and sold by Cisco. PCIe cards not qualified or sold by Cisco are the
responsibility of the customer. Although Cisco will always stand behind and support the C-Series rack-mount
servers, customers using standard, off-the-shelf, third-party cards must go to the third-party card vendor for
support if any issue with that particular card occurs.
Slot Number Electrical Lane Connector Maximum Card Card Height (Rear Panel NCSI
Width Length Length Opening) Support
Slot Number Electrical Lane Connector Length Maximum Card Card Height (Rear NCSI Support
Width Length Panel Opening)
PCIe cable connector Gen-3 x8 Other end of cable connects to front drive backplane to support front-panel NVMe
for front-panel NVMe SSDs.
SSDs
Note If you are installing a Cisco UCS Virtual Interface Card, there are prerequisite considerations. See Cisco
Virtual Interface Card (VIC) Considerations, on page 80.
Note RAID controller cards install into a separate mRAID riser. See Replacing a SAS Storage Controller Card
(RAID or HBA), on page 84.
Step 1 Remove an existing PCIe card (or a blank filler panel) from the PCIe riser:
a) Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33.
b) Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
c) Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
d) Remove any cables from the ports of the PCIe card that you are replacing.
e) Use two hands to grasp the external riser handle and the blue area at the front of the riser.
f) Lift straight up to disengage the riser's connectors from the two sockets on the motherboard. Set the riser upside-down
on an antistatic surface.
g) Open the hinged plastic retainer that secures the rear-panel tab of the card.
h) Pull evenly on both ends of the PCIe card to remove it from the socket on the PCIe riser.
If the riser has no card, remove the blanking panel from the rear opening of the riser.
1 PCIe slot 1 rear-panel opening 4 Hinged card retainer (one each slot)
d) Position the PCIe riser over its two sockets on the motherboard and over the two chassis alignment channels.
e) Carefully push down on both ends of the PCIe riser to fully engage its two connectors with the two sockets on the
motherboard.
f) Replace the top cover to the server.
g) Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
Note If you use the Cisco Card NIC mode, you must also make a VIC Slot setting that matches where your VIC is
installed. The options are Riser1, Riser2, and Flex-LOM. See NIC Mode and NIC Redundancy Settings, on
page 21 for more information about NIC modes.
If you want to use the Cisco UCS VIC card for Cisco UCS Manager integration, see also the Cisco UCS
C-Series Server Integration with Cisco UCS Manager Guides for details about supported configurations,
cabling, and other requirements.
VIC How Many Slots That Primary Slot For Primary Slot For Minimum Cisco
Supported in Support VICs Cisco UCS Manager Cisco Card NIC IMC Firmware
Server Integration Mode
Carefully align the riser's edge connector with the motherboard socket at the same time you align the two channels
on the riser with the two pegs on the inner chassis wall. Press down evenly on both ends of the riser to fully engage
its connector with the motherboard socket.
e) Replace the top cover to the server.
f) Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
Figure 41: Location of the mLOM Card Socket Below the mRAID Riser
Note You cannot use a hardware RAID controller card and the embedded software RAID controller to control
front-panel drives at the same time. See Embedded SATA RAID Controller, on page 117 for details.
Note For servers running in standalone mode only: After you replace controller hardware, you must run the
Cisco Host Upgrade Utility (HUU) to update the controller firmware, even if the firmware Current Version
is the same as the Update Version. This is necessary to program the controller's suboem-id to the correct value
for the server SKU. If you do not do this, drive enumeration might not display correctly in the software. This
issue does not affect servers controlled in UCSM mode.
Note For servers running in standalone mode only: After you replace controller hardware (UCSC-RAID-M5 or
UCSC-SAS-M5), you must run the Cisco UCS Host Upgrade Utility (HUU) to update the controller firmware,
even if the firmware Current Version is the same as the Update Version. This is necessary to program the
controller's suboem-id to the correct value for the server SKU. If you do not do this, drive enumeration might
not display correctly in the software. This issue does not affect servers controlled in UCSM mode.
See the HUU guide for your Cisco IMC release for instructions on downloading and using the utility to bring
server components to compatible levels: HUU Guides.
Warning There is danger of explosion if the battery is replaced incorrectly. Replace the battery only with the
same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the
manufacturer’s instructions.
Statement 1015
Note You cannot use a hardware RAID controller card and the embedded software RAID controller at the same
time. See Embedded SATA RAID Controller, on page 117 for details about RAID support.
a) Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33.
b) Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
c) Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 2 Remove the mRAID riser (riser 3) from the server:
a) Using both hands, grasp the external blue handle on the rear of the riser and the blue finger-grip on the front end of
the riser.
b) Lift the riser straight up to disengage it from the motherboard socket.
c) Set the riser upside down on an antistatic surface.
Step 3 Remove any existing card from the riser:
a) Disconnect cables from the existing card.
b) Open the blue card-ejector lever on the back side of the card to eject it from the socket on the riser.
c) Pull the card from the riser and set it aside.
Step 4 Install a new card to the riser:
a) With the riser upside down, set the card on the riser.
b) Push on both corners of the card to seat its connector in the riser socket.
c) Close the card-ejector lever on the card to lock it into the riser.
Step 5 Return the riser to the server:
a) Align the connector on the riser with the socket on the motherboard. At the same time, align the two slots on the back
side of the bracket with the two pegs on the inner chassis wall.
b) Push down gently to engage the riser connector with the motherboard socket. The metal riser bracket must also engage
the two pegs that secure it to the chassis wall.
Step 6 Reconnect the cables to their connectors on the new card.
Step 7 Replace the top cover to the server.
Step 8 Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
TPM Considerations
• This server supports either TPM version 1.2 or TPM version 2.0.
• Field replacement of a TPM is not supported; you can install a TPM after-factory only if the server does
not already have a TPM installed.
• If there is an existing TPM 1.2 installed in the server, you cannot upgrade to TPM 2.0. If there is no
existing TPM in the server, you can install TPM 2.0.
Note Field replacement of a TPM is not supported; you can install a TPM after-factory only if the server does not
already have a TPM installed.
This topic contains the following procedures, which must be followed in this order when installing and enabling
a TPM:
1. Installing the TPM Hardware
2. Enabling the TPM in the BIOS
3. Enabling the Intel TXT Feature in the BIOS
Note For security purposes, the TPM is installed with a one-way screw. It cannot be removed with a standard
screwdriver.
Step 5 Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
Figure 47: Location of the TPM Socket
Step 6 Continue with Enabling the TPM in the BIOS, on page 93.
Note You must set a BIOS Administrator password before performing this procedure. To set this password, press
the F2 key when prompted during system boot to enter the BIOS Setup utility. Then navigate to Security >
Set Administrator Password and enter the new password twice as prompted.
b) Log into the BIOS Setup utility with your BIOS Administrator password.
c) Choose the Advanced tab.
d) Choose Trusted Computing to open the TPM Security Device Configuration window.
e) Verify that TPM SUPPORT and TPM State are Enabled.
Step 3 Continue with Enabling the Intel TXT Feature in the BIOS, on page 94.
Step 1 Reboot the server and watch for the prompt to press F2.
Step 2 When prompted, press F2 to enter the BIOS Setup utility.
Step 3 Verify that the prerequisite BIOS values are enabled:
a) Choose the Advanced tab.
b) Choose Intel TXT(LT-SX) Configuration to open the Intel TXT(LT-SX) Hardware Support window.
c) Verify that the following items are listed as Enabled:
• VT-d Support (default is Enabled)
• VT Support (default is Enabled)
• TPM Support
• TPM State
2 J38 pin 1 arrow printed on motherboard 7 J39 pin 1 arrow printed on motherboard
3 Clear CMOS: J38 pins 9 - 10 8 Boot Cisco IMC from alternate image: J39 pins 1 -
2
4 Recover BIOS: J38 pins 11 - 12 9 Reset Cisco IMC password to default: J39 pins 3 -
4
5 Clear password: J38 pins 13 - 14 10 Reset Cisco IMC to defaults: J39 pins 5 - 6
Caution Clearing the CMOS removes any customized settings and might result in data loss. Make a note of any
necessary customized settings in the BIOS before you use this clear CMOS procedure.
Step 1 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33. Disconnect power cords from all power supplies.
Step 2 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 3 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 4 Locate header block J38 and pins 9-10, as shown in Service Headers and Jumpers, on page 95.
Step 5 Install a two-pin jumper across pins 9 and 10.
Step 6 Reinstall the top cover and reconnect AC power cords to the server. The server powers up to standby power mode,
indicated when the Power LED on the front panel is amber.
Step 7 Return the server to main power mode by pressing the Power button on the front panel. The server is in main power
mode when the Power LED is green.
Note You must allow the entire server to reboot to main power mode to complete the reset. The state of the jumper
cannot be determined without the host CPU running.
Step 8 Press the Power button to shut down the server to standby power mode, and then remove AC power cords from the
server to remove all power.
Step 9 Remove the top cover from the server.
Step 10 Remove the jumper that you installed.
Note If you do not remove the jumper, the CMOS settings are reset to the defaults every time you power-cycle the
server.
Step 11 Replace the top cover, replace the server in the rack, replace power cords and any other cables, and then power on the
server by pressing the Power button.
Note As indicated by the message shown above, there are two procedures for recovering the BIOS. Try procedure
1 first. If that procedure does not recover the BIOS, use procedure 2.
Step 1 Download the BIOS update package and extract it to a temporary location.
Step 2 Copy the contents of the extracted recovery folder to the root directory of a USB drive. The recovery folder contains the
bios.cap file that is required in this procedure.
Note The bios.cap file must be in the root directory of the USB drive. Do not rename this file. The USB drive must
be formatted with either the FAT16 or FAT32 file system.
Step 3 Insert the USB drive into a USB port on the server.
Step 4 Reboot the server.
Step 5 Return the server to main power mode by pressing the Power button on the front panel.
The server boots with the updated BIOS boot block. When the BIOS detects a valid bios.cap file on the USB drive, it
displays this message:
Found a valid recovery file...Transferring to Cisco IMC
System would flash the BIOS image now...
System would restart with recovered image after a few seconds...
Step 6 Wait for server to complete the BIOS update, and then remove the USB drive from the server.
Note During the BIOS update, Cisco IMC shuts down the server and the screen goes blank for about 10 minutes.
Do not unplug the power cords during this update. Cisco IMC powers on the server after the update is complete.
Step 1 Download the BIOS update package and extract it to a temporary location.
Step 2 Copy the contents of the extracted recovery folder to the root directory of a USB drive. The recovery folder contains
the bios.cap file that is required in this procedure.
Note The bios.cap file must be in the root directory of the USB drive. Do not rename this file. The USB drive must
be formatted with either the FAT16 or FAT32 file system.
Step 3 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33. Disconnect power cords from all power supplies.
Step 4 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 5 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 6 Locate header block J38 and pins 11-12, as shown in Service Headers and Jumpers, on page 95.
Step 7 Install a two-pin jumper across pins 11 and 12.
Step 8 Reconnect AC power cords to the server. The server powers up to standby power mode.
Step 9 Insert the USB thumb drive that you prepared in Step 2 into a USB port on the server.
Step 10 Return the server to main power mode by pressing the Power button on the front panel.
The server boots with the updated BIOS boot block. When the BIOS detects a valid bios.cap file on the USB drive, it
displays this message:
Found a valid recovery file...Transferring to Cisco IMC
System would flash the BIOS image now...
System would restart with recovered image after a few seconds...
Step 11 Wait for server to complete the BIOS update, and then remove the USB drive from the server.
Note During the BIOS update, Cisco IMC shuts down the server and the screen goes blank for about 10 minutes.
Do not unplug the power cords during this update. Cisco IMC powers on the server after the update is complete.
Step 12 After the server has fully booted, power off the server again and disconnect all power cords.
Step 13 Remove the jumper that you installed.
Note If you do not remove the jumper, after recovery completion you see the prompt, “Please remove the recovery
jumper.”
Step 14 Replace the top cover, replace the server in the rack, replace power cords and any other cables, and then power on the
server by pressing the Power button.
Step 1 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33. Disconnect power cords from all power supplies.
Step 2 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 3 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 4 Locate header block J38 and pins 13-14, as shown in Service Headers and Jumpers, on page 95.
Step 5 Install a two-pin jumper across pins 13 and 14.
Step 6 Reinstall the top cover and reconnect AC power cords to the server. The server powers up to standby power mode,
indicated when the Power LED on the front panel is amber.
Step 7 Return the server to main power mode by pressing the Power button on the front panel. The server is in main power
mode when the Power LED is green.
Note You must allow the entire server to reboot to main power mode to complete the reset. The state of the jumper
cannot be determined without the host CPU running.
Step 8 Press the Power button to shut down the server to standby power mode, and then remove AC power cords from the
server to remove all power.
Step 9 Remove the top cover from the server.
Step 10 Remove the jumper that you installed.
Note If you do not remove the jumper, the password is cleared every time you power-cycle the server.
Step 11 Replace the top cover, replace the server in the rack, replace power cords and any other cables, and then power on the
server by pressing the Power button.
Using the Boot Alternate Cisco IMC Image Header (J39, Pins 1 - 2)
You can use this Cisco IMC debug header to force the system to boot from an alternate Cisco IMC image.
Step 1 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33. Disconnect power cords from all power supplies.
Step 2 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 3 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 4 Locate header block J39, pins 1-2, as shown in Service Headers and Jumpers, on page 95.
Step 5 Install a two-pin jumper across J39 pins 1 and 2.
Step 6 Reinstall the top cover and reconnect AC power cords to the server. The server powers up to standby power mode,
indicated when the Power LED on the front panel is amber.
Step 7 Return the server to main power mode by pressing the Power button on the front panel. The server is in main power
mode when the Power LED is green.
Note When you next log in to Cisco IMC, you see a message similar to the following:
'Boot from alternate image' debug functionality is enabled.
CIMC will boot from alternate image on next reboot or input power cycle.
Step 8 Press the Power button to shut down the server to standby power mode, and then remove AC power cords from the
server to remove all power.
Step 9 Remove the top cover from the server.
Step 10 Remove the jumper that you installed.
Note If you do not remove the jumper, the server will boot from an alternate Cisco IMC image every time that you
power cycle the server or reboot Cisco IMC.
Step 11 Replace the top cover, replace the server in the rack, replace power cords and any other cables, and then power on the
server by pressing the Power button.
Using the Reset Cisco IMC Password to Default Header (J39, Pins 3 - 4)
You can use this Cisco IMC debug header to force the Cisco IMC password back to the default.
Step 1 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33. Disconnect power cords from all power supplies.
Step 2 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 3 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 4 Locate header block J39, pins 3-4, as shown in Service Headers and Jumpers, on page 95.
Step 5 Install a two-pin jumper across J39 pins 3 and 4.
Step 6 Reinstall the top cover and reconnect AC power cords to the server. The server powers up to standby power mode,
indicated when the Power LED on the front panel is amber.
Step 7 Return the server to main power mode by pressing the Power button on the front panel. The server is in main power
mode when the Power LED is green.
Note When you next log in to Cisco IMC, you see a message similar to the following:
'Reset to default CIMC password' debug functionality is enabled.
On input power cycle, CIMC password will be reset to defaults.
Step 8 Press the Power button to shut down the server to standby power mode, and then remove AC power cords from the
server to remove all power.
Step 9 Remove the top cover from the server.
Step 10 Remove the jumper that you installed.
Note If you do not remove the jumper, the server will reset the Cisco IMC password to the default every time that
you power cycle the server. The jumper has no effect if you reboot Cisco IMC.
Step 11 Replace the top cover, replace the server in the rack, replace power cords and any other cables, and then power on the
server by pressing the Power button.
Step 1 Shut down and remove power from the server as described in Shutting Down and Removing Power From the Server,
on page 33. Disconnect power cords from all power supplies.
Step 2 Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
Step 3 Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
Step 4 Locate header block J39, pins 5-6, as shown in Service Headers and Jumpers, on page 95.
Step 5 Install a two-pin jumper across J39 pins 5 and 6.
Step 6 Reinstall the top cover and reconnect AC power cords to the server. The server powers up to standby power mode,
indicated when the Power LED on the front panel is amber.
Step 7 Return the server to main power mode by pressing the Power button on the front panel. The server is in main power
mode when the Power LED is green.
Note When you next log in to Cisco IMC, you see a message similar to the following:
'CIMC reset to factory defaults' debug functionality is enabled.
On input power cycle, CIMC will be reset to factory defaults.
Step 8 To remove the jumper, press the Power button to shut down the server to standby power mode, and then remove AC
power cords from the server to remove all power.
Step 9 Remove the top cover from the server.
Step 10 Remove the jumper that you installed.
Note If you do not remove the jumper, the server will reset the Cisco IMC to the default settiings every time that
you power cycle the server. The jumper has no effect if you reboot Cisco IMC.
Step 11 Replace the top cover, replace the server in the rack, replace power cords and any other cables, and then power on the
server by pressing the Power button.
Server Specifications
This appendix lists the physical, environmental, and power specifications for the server.
• Physical Specifications, on page 103
• Environmental Specifications, on page 103
• Power Specifications, on page 104
Physical Specifications
The following table lists the physical specifications for the server versions.
Description Specification
Environmental Specifications
The following table lists the environmental requirements and specifications for the server.
Description Specification
Power Specifications
Note Do not mix power supply types or wattages in the server. Both power supplies must be identical.
You can get more specific power information for your exact server configuration by using the Cisco UCS
Power Calculator:
http://ucspowercalc.cisco.com
The power specifications for the supported power supply options are listed in the following sections.
Description Specification
Description Specification
Description Specification
Description Specification
Note Only the approved power cords or jumper power cords listed below are supported.
R2XX-DMYMPWRCORD NA NA
No power cord; PID option for ordering server with no power cord
Note Do not mix controller types in the server. Do not use the embedded SATA controller and a hardware-based
RAID controller card at the same time. This combination is not supported and could result in data loss.
This server supports the RAID and HBA controller options and cable requirements shown in the following
table.
Embedded RAID (PCH This controller is supported only in these 0, 1, 10 No Use SAS/SATA cable included
SATA) server versions: with chassis to connect interposer
board to drive backplane.
• All server versions can use the
embedded SATA controller to control
two internal SATA M.2 drives.
• SFF 10-drives (C220M5SX):
8 front-loading SATA drives (drive
bays 1 - 8)
• LFF 4-drives (C220M5L):
4 front-loading SATA drives
Cisco 12G Modular RAID This controller is supported only in this 0, 1, 5, 6, 10, Yes Use SAS/SATA cable included
Controller server version: 50, 60 with chassis to connect controller
to drive backplane.
Controller is orderable only • LFF 4-drives (C220M5L):
as UCSC-MRAID1G-KIT
4 front-loading SAS/SATA drives
Cisco 12G Modular RAID This controller is supported only in these 0, 1, 5, 6, 10, Yes Use SAS/SATA cable included
Controller with 2-GB cache server versions: 50, 60 with chassis to connect controller
to drive backplane.
UCSC-RAID-M5 • SFF 10-drives (C220M5SX):
Includes 2-GB cache 10 front-loading SAS/SATA drives
Cisco 12G Modular SAS This controller is supported only in these Non-RAID No Use SAS/SATA cable included
HBA server versions: with chassis to connect controller
to drive backplane.
UCSC-SAS-M5 • SFF 10-drives (C220M5SX):
10 front-loading SAS/SATA drives
Cisco 12G 9400-8e HBA Supported in all server versions: Non-RAID No External drive cables not sold by
for external JBOD attach Cisco.
8 external SAS/SATA ports, controlling
UCSC-9400-8E up to 1024 external drives. NOTE: This HBA does not
support optical cables for
connection to external storage
(copper only).
Note For servers running in standalone mode only: After you replace controller hardware, you must run the
Cisco Host Upgrade Utility (HUU) to update the controller firmware, even if the firmware Current Version
is the same as the Update Version. This is necessary to program the controller's suboem-id to the correct value
for the server SKU. If you do not do this, drive enumeration might not display correctly in the software. This
issue does not affect servers controlled in UCSM mode.
HDD + SSD No
Starting RAID Controller Migrate to Hardware RAID Allowed? Migrate to Software RAID
Allowed?
Note The SFF 10-drive version UCSC-C220-M5SN supports NVMe drives only, and so does not use SAS or SATA
RAID. This version of the server comes with an NVMe-switch card factory-installed in the internal mRAID
riser and a PCIe cable connected to PCIe riser 2. The NVMe switch card is not orderable separately.
Embedded RAID
This SW RAID option can control up to 8 SATA drives in the SFF 10-drive version and up to 4 SATA drives
in the LFF 4-drive version.
This embedded RAID option requires that you have a SATA interposer card installed in internal mRAID riser
3. Use the SAS/SATA cables that came with the server.
1. Connect SAS/SATA cable A1 from the A1 interposer connector to the A1 backplane connector.
2. Connect SAS/SATA cable A2 from the A2 interposer connector to the A2 backplane connector.
Note See the following figures that illustrate cable connections and which drives are controlled by each cable. In
the SFF 10-drive version, drives 5 and 10 cannot be controlled by the embedded SATA RAID controller.
Figure 49: Embedded RAID Interposer Cable-to-Drive Backplane Mapping, LFF 4-Drive Version
Figure 50: Embedded RAID Interposer Cable-to-Drive Backplane Mapping, SFF 10-Drive Version
Note See the following figures that illustrate cable connections and which drives are controlled by each cable.
Figure 51: Hardware RAID Card Cable-to-Drive Backplane Mapping, LFF 4-Drive Version
Figure 52: Hardware RAID Card Cable-to-Drive Backplane Mapping, SFF 10-Drive Version
Note The VMware ESX/ESXi operating system is not supported with the embedded SATA MegaRAID controller
in SW RAID mode. You can use VMWare in AHCI mode.
Note The Microsoft Windows Server 2016 Hyper-V hypervisor is supported for use with the embedded MegaRAID
controller in SW RAID mode, but all other hyperviors are not supported. All Hypervisors are supported in
AHCI mode.
Note You cannot control the M.2 SATA SSDs in the server with a HW RAID controller.
Caution Data migration from software RAID (embedded RAID) to hardware RAID (a
controller card) is not supported and could result in data loss. Migrations from
software RAID to hardware RAID are supported only before there is data on the
drives, or when there are no drives in the server.
• The required drivers for this controller are already installed and ready to use with the LSI SWRAID
Configuration Utility. However, if you will use this controller with Windows or Linux, you must download
and install additional drivers for those operating systems. See Installing LSI MegaSR Drivers For Windows
and Linux, on page 120.
• The sSATA controller controls two internal SATA M.2 drives, when they are present in the M.2
mini-storage module option.
• If the M.2 mini-storage module is not present, or if M.2 NVMe drives are installed in the mini-storage
module, the sSATA controller is automatically disabled.
• Each controller is listed separately in the BIOS. You can enable or disable the controllers in the BIOS.
See Embedded SATA RAID: Two SATA Controllers, on page 118.
Note If you use an embedded RAID controller with Linux, both the pSATA and the sSATA controller must be set
to LSI SW RAID mode.
Step 1 Boot the server and press F2 when prompted to enter the BIOS Setup utility.
Step 2 Set the SATA mode:
a) Choose the Advanced tab, and then choose LOM and PCIe Slots Configuration.
b) For the primary pSATA controller, select pSATA and then choose one of the options from the dialog:
• LSI SW RAID—Enable the embedded pSATA RAID controller.
Note This menu option does not appear when the server is set to boot in Legacy mode (UEFI mode is
required). To change the boot mode, use the BIOS setting for Boot Options > Boot Mode.
c) For the secondary sSATA controller, select M.2 and then choose one of the options from the dialog:
• LSI SW RAID—Enable the embedded sSATA RAID controller for control of internal SATA M.2 drives.
Note This menu option does not appear when the server is set to boot in Legacy mode (UEFI mode is
required). To change the boot mode, use the BIOS setting for Boot Options > Boot Mode.
Note This menu option does not appear when the server has no M.2 mini storage module, or when no SATA
M.2 drive is installed in the mini-storage module.
• AHCI—Enable control of the internal SATA M.2 drives by AHCI through your OS rather than the embedded
RAID controller.
• Disabled—Disable the embedded sSATA RAID controller.
Step 3 Press F10 to save your changes and exit the utility.
Step 1 Boot the server and press F2 when prompted to enter the BIOS Setup utility.
Step 2 Choose the Advanced tab.
Step 3 Select the instance of the utility that is for the controller that you want to manage (primary or secondary):
• For the pSATA controller, select LSI Software RAID Configuration Utility (SATA).
• For the sSATA controller, select LSI Software RAID Configuration Utility (sSATA).
Note The required drivers for this controller are already installed and ready to use. However, if you will use this
controller with Windows or Linux, you must download and install additional drivers for those operating
systems.
This section explains how to install the LSI MegaSR drivers for the following supported operating systems:
• Microsoft Windows Server
• Red Hat Enterprise Linux (RHEL)
• SUSE Linux Enterprise Server (SLES)
For the specific supported OS versions, see the Hardware and Software Compatibility Matrix for your server
release.
Step 1 Find the drivers ISO file download for your server online and download it to a temporary location on your workstation:
a) See the following URL: http://www.cisco.com/cisco/software/navigator.html.
Step 1 Download the Cisco UCS C-Series drivers’ ISO, as described in Downloading the MegaSR Drivers, on page 120.
Step 2 Prepare the drivers on a USB thumb drive:
a) Burn the ISO image to a disk.
b) Browse the contents of the drivers folders to the location of the embedded MegaRAID drivers:
/<OS>/Storage/Intel/C600-M5/
c) Expand the Zip file, which contains the folder with the MegaSR driver files.
d) Copy the expanded folder to a USB thumb drive.
Step 3 Start the Windows driver installation using one of the following methods:
• To install from local media, connect an external USB DVD drive to the server and then insert the first Windows
installation disk into the drive. Skip to Step 6.
• To install from remote ISO, log in to the server’s Cisco IMC interface and continue with the next step.
Step 4 Launch a Virtual KVM console window and click the Virtual Media tab.
a) Click Add Image and browse to select your remote Windows installation ISO file.
b) Check the check box in the Mapped column for the media that you just added, and then wait for mapping to
complete.
Step 1 Click Start, point to Settings, and then click Control Panel.
Step 2 Double-click System, click the Hardware tab, and then click Device Manager. Device Manager starts.
Step 3 In Device Manager, double-click SCSI and RAID Controllers, right-click the device for which you are installing the
driver, and then click Properties.
Step 4 On the Driver tab, click Update Driver to open the Update Device Driver wizard, and then follow the wizard instructions
to update the driver.
Linux Drivers
Dowloading the Driver IMG or ISO File
See Downloading the MegaSR Drivers, on page 120 for instructions on downloading the drivers. The Linux
driver is included in the form of dud-[driver version].img (or .iso), which is the boot image for the embedded
MegaRAID stack.
Note The LSI MegaSR drivers that Cisco provides for RHEL and SLES are for the original GA versions of those
distributions. The drivers do not support updates to those OS kernels.
Alternatively, you can mount the dud.img file as a virtual floppy disk, as described in the installation procedures.
For RHEL and SLES, you can use a driver disk utility to create disk images from image files.
Step 1 Download the Cisco UCS C-Series drivers ISO, as described in Downloading the MegaSR Drivers, on page 120 and save
it to your Linux system.
Step 2 Extract the dud.img file:
a) Burn the ISO image to a disc.
b) Browse the contents of the drivers folders to the location of the embedded MegaRAID drivers:
/<OS>/Storage/Intel/C600-M5/
c) Expand the Zip file, which contains the folder with the driver files.
Step 3 Copy the driver update disk image dud-[driver version].img (or .iso) to your Linux system.
Step 4 Insert a blank USB thumb drive into a port on your Linux system.
Step 5 Create a directory and mount the DUD image to that directory:
Example:
mkdir <destination_folder>
mount -oloop <driver_image> <destination_folder>
Step 6 Copy the contents in the directory to your USB thumb drive.
Note If you use an embedded RAID controller with Linux, both the pSATA and the sSATA controller must be set
to LSI SW RAID mode.
Step 1 Prepare the dud.img (or .iso) file using one of the following methods:
• To install from physical drive, use the procedure in Preparing Physical Thumb Drive for Linux, on page 122, then
continue with step 4.
• To install from virtual disk, download the Cisco UCS C-Series drivers’ ISO, as described in Downloading the
MegaSR Drivers, on page 120, then continue with the next step.
Step 4 Launch a Virtual KVM console window and click the Virtual Media tab.
a) Click Add Image and browse to select your remote RHEL installation ISO file.
b) Click Add Image again and browse to select your dud.img file.
c) Check the check boxes in the Mapped column for the media that you just added, then wait for mapping to complete.
Step 5 Power-cycle the target server.
Step 6 Press F6 when you see the F6 prompt during bootup. The Boot Menu window opens.
Step 7 On the Boot Manager window, select the physical disk or virtual disk and press Enter.
The RHEL installation begins when the image is booted.
Step 8 Enter one of the following blacklist commands at the boot prompt:
• For RHEL 6.x (32- and 64-bit), enter:
linux dd blacklist=isci blacklist=ahci nodmraid noprobe=<atadrive number>
Note The noprobe values depend on the number of drives. For example, to install RHEL 6.x on a RAID 5
configuration with three drives, enter:
Linux dd blacklist=isci blacklist=ahci nodmraid noprobe=ata1 noprobe=ata2
Step 10 Use the arrow key to choose Yes, and then press Enter.
Step 11 Choose fd0 to indicate that you have a disk with the driver on it.
Step 12 Do one of the following actions:
• If you prepared the dud.img (or .iso) file on a physical thumb drive, insert the thumb drive to the target server and
then press Enter.
• If you mapped the dud.img (or .iso) file as a virtual disk, choose the location of the virtual disk.
The installer locates and loads the driver for your device. The following message appears:
Loading megasr driver...
Note If you use an embedded RAID controller with Linux, both the pSATA and the sSATA controller must be set
to LSI SW RAID mode.
Step 1 Prepare the dud.img file using one of the following methods:
• To install from physical disk, use the procedure in Preparing Physical Thumb Drive for Linux, on page 122, then
continue with step 4.
• To install from virtual disk, download the Cisco UCS C-Series drivers’ ISO, as described in Downloading the
MegaSR Drivers, on page 120, then continue with the next step.
• To install from remote ISO, log in to the server’s Cisco IMC interface. Then continue with the next step.
Step 4 Launch a Virtual KVM console window and click the Virtual Media tab.
a) Click Add Image and browse to select your remote RHEL installation ISO file.
b) Click Add Image again and browse to select your dud.img file.
c) Check the check boxes in the Mapped column for the media that you just added, then wait for mapping to complete.
Step 5 Power-cycle the target server.
Step 6 Press F6 when you see the F6 prompt during bootup. The Boot Menu window opens.
Step 7 On the Boot Manager window, select the physical disk or virtual disk and press Enter.
The SLES installation begins when the image is booted.
Step 14 At the menu, choose the driver update medium and press the Back button.
Step 15 Follow the SLES installation wizard to complete the installation.
Step 16 Reboot the target server.
If you need to change this setting, enter the BIOS Setup Utility by pressing F2 when prompted during
bootup.
• If the server is integrated with Cisco UCS Manager and is controlled by a service profile, this setting is
enabled by default in the service profile when a GPU is present.
To change this setting manually, use the following procedure.
Step 1 Refer to the Cisco UCS Manager configuration guide (GUI or CLI) for your release for instructions on configuring service
profiles:
Cisco UCS Manager Configuration Guides
Step 2 Refer to the chapter on Configuring Server-Related Policies > Configuring BIOS Settings.
Step 3 In the section of your profile for PCI Configuration BIOS Settings, set Memory Mapped IO Above 4GB Config to one of
the following:
• Disabled—Does not map 64-bit PCI devices to 64 GB or greater address space.
• Enabled—Maps I/O of 64-bit PCI devices to 64 GB or greater address space.
• Platform Default—The policy uses the value for this attribute contained in the BIOS defaults for the server. Use
this only if you know that the server BIOS is set to use the default enabled setting for this item.
b) Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach
cables from the rear panel to provide clearance.
Caution If you cannot safely view and access the component, remove the server from the rack.
c) Remove the top cover from the server as described in Removing the Server Top Cover, on page 35.
d) Use two hands to grasp the external riser handle and the blue area at the front of the riser.
e) Lift straight up to disengage the riser's connectors from the two sockets on the motherboard. Set the riser upside-down
on an antistatic surface.
f) Open the hinged plastic retainer that secures the rear-panel tab of the card.
g) Pull evenly on both ends of the GPU card to remove it from the socket on the PCIe riser.
If the riser has no card, remove the blanking panel from the rear opening of the riser.
a) With the hinged tab retainer open, align the new GPU card with the empty socket on the PCIe riser.
b) Push down evenly on both ends of the card until it is fully seated in the socket.
c) Ensure that the card’s rear panel tab sits flat against the riser rear-panel opening and then close the hinged tab retainer
over the card’s rear-panel tab.
1 PCIe slot 1 rear-panel opening 4 Hinged card retainer (one each slot)
d) Position the PCIe riser over its two sockets on the motherboard and over the two chassis alignment channels.
e) Carefully push down on both ends of the PCIe riser to fully engage its two connectors with the two sockets on the
motherboard.
f) Replace the top cover to the server.
g) Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.
Step 3 Optional: Continue with Installing Drivers to Support the GPU Cards, on page 137.
Note If you installed an NVIDIA Tesla M-series or P-Series GPU, you must install GRID licenses to use the GRID
features. See Using NVIDIA GRID License Server For M-Series and P-Series GPUs, on page 131.
There are three editions of GRID licenses, which enable three different classes of GRID features. The GRID
software automatically selects the license edition based on the features that you are using.
GRID Virtual GPU (vGPU) Virtual GPUs for business desktop computing
GRID Virtual Workstation – Extended Virtual GPUs for high-end workstation computing
Workstation graphics on GPU pass-through
Step 1 Select the Log In link, or the Register link if you do not already have an account.
The NVIDIA Software Licensing Center > License Key Registration dialog opens.
Step 2 Complete the License Key Registration form and then click Submit My Registration Information.
The NVIDIA Software Licensing Center > Product Information Software dialog opens.
Step 3 If you have additional PAKs, click Register Additional Keys. For each additional key, complete the form on the License
Key Registration dialog and then click Submit My Registration Information.
Step 4 Agree to the terms and conditions and set a password when prompted.
Step 1 Return to the NVIDIA Software Licensing Center > Product Information Software dialog.
Step 2 Click the Current Releases tab.
Step 3 Click the NVIDIA GRID link to access the Product Download dialog. This dialog includes download links for:
• NVIDIA License Manager software
• The gpumodeswitch utility
• The host driver software
• The hosting platform can be a physical or a virtual machine. NVIDIA recommends using a host that is
dedicated only to running the License Server.
• The hosting platform must run a supported Windows OS.
• The hosting platform must have a constant IP address.
• The hosting platform must have at least one constant Ethernet MAC address.
• The hosting platform’s date and time must be set accurately.
Installing GRID Licenses From the NVIDIA Licensing Portal to the License
Server
Accessing the GRID License Server Management Interface
Open a web browser on the License Server host and access the URL http://localhost:8080/licserver.
If you configured the License Server host’s firewall to permit remote access to the License Server, the
management interface is accessible from remote machines at the URL http://hostname:8080/licserver
Step 3 Select your License Server’s MAC address from the Server host ID pull-down.
Note It is important to use the same Ethernet ID consistently to identify the server when generating licenses on
NVIDIA’s Licensing Portal. NVIDIA recommends that you select one entry for a primary, non-removable
Ethernet interface on the platform.
Step 3 Use the License Server Configuration menu to install the .bin file that you generated earlier.
a) Click Choose File.
b) Browse to the license .bin file that you want to install and click Open.
c) Click Upload.
The license file is installed on your License Server. When installation is complete, you see the confirmation message,
“Successfully applied license file to license server.”
Step 1 Open the NVIDIA Control Panel using one of the following methods:
• Right-click on the Windows desktop and select NVIDIA Control Panel from the menu.
• Open Windows Control Panel and double-click the NVIDIA Control Panel icon.
Step 2 In the NVIDIA Control Panel left-pane under Licensing, select Manage License.
The Manage License task pane opens and shows the current license edition being used. The GRID software automatically
selects the license edition based on the features that you are using. The default is Tesla (unlicensed).
Step 3 If you want to acquire a license for GRID Virtual Workstation, under License Edition, select GRID Virtual Workstation.
Step 4 In the License Server field, enter the address of your local GRID License Server. The address can be a domain name or
an IP address.
Step 5 In the Port Number field, enter your port number of leave it set to the default used by the server, which is 7070.
Step 2 Edit the ServerUrl line with the address of your local GRID License Server.
The address can be a domain name or an IP address. See the example file below.
Step 3 Append the port number (default 7070) to the end of the address with a colon. See the example file below.
Step 4 Edit the FeatureType line with the integer for the license type. See the example file below.
• GRID vGPU = 1
• GRID Virtual Workstation = 2
The service automatically acquires the license edition that you specified in the FeatureType line. You can confirm this
in /var/log/messages.
Note After you configure licensing settings in the NVIDIA Control Panel, the settings persist across reboots.
Using gpumodeswitch
The command line utility gpumodeswitch can be run in the following environments:
Note Consult NVIDIA product release notes for the latest information on compatibility with compute and graphic
modes.
Switches to graphics mode. Switches mode of all supported GPUs in the server unless you specify
otherwise when prompted.
• --gpumode compute
Switches to compute mode. Switches mode of all supported GPUs in the server unless you specify
otherwise when prompted.
Note After you switch GPU mode, reboot the server to ensure that the modified resources of the GPU are correctly
accounted for by any OS or hypervisor running on the server.
Note You must do this procedure before you update the NVIDIA drivers.
Step 3 Click Cisco UCS C-Series Rack-Mount Standalone Server Software in the right-hand column.
Step 4 Click the name of your model of server in the right-hand column.
Step 5 Click Unified Computing System (UCS) Server Firmware.
Step 6 Click the release number.
Step 7 Click Download Now to download the ucs-server platform-huu-version_number.iso file.
Step 8 Verify the information on the next page, and then click Proceed With Download.
Step 9 Continue through the subsequent screens to accept the license agreement and browse to a location where you want to
save the file.
Step 10 Use the Host Upgrade Utility to update the server BIOS.
The user guides for the Host Upgrade Utility are at Utility User Guides.
Step 1 Install your hypervisor software on a computer. Refer to your hypervisor documentation for the installation instructions.
Step 2 Create a virtual machine in your hypervisor. Refer to your hypervisor documentation for instructions.
Step 3 Install the GPU drivers to the virtual machine. Download the drivers from either:
• NVIDIA Enterprise Portal for GRID hypervisor downloads (requires NVIDIA login):
https://nvidia.flexnetoperations.com/
• NVIDIA public driver area: http://www.nvidia.com/Download/index.aspx
• AMD: http://support.amd.com/en-us/download