Overview

System Requirements

Connecting C-Series Server in Direct Connect Mode

Connecting C-Series Server in Scalability Port Mode

Physical Connectivity Illustrations

Managing the Rack-Mount Server in Cisco UCS Manager after Integration

Upgrading the C-Series Server Firmware

Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

Overview

This guide contains information and procedures for installing Cisco UCS Rack Mount Servers for integration with Cisco UCS Manager release 3.0, for Cisco UCS Mini.

Cisco UCS C-Series Rack-Mount Servers are managed by the built-in standalone software, Cisco Integrated Management Controller (CIMC) . When a C-Series Rack-Mount Server is integrated with Cisco UCS Manager, the CIMC does not manage the server anymore. Instead it is managed with the Cisco UCS Manager software. You will manage the server using the Cisco UCS Manager GUI or Cisco UCS Manager CLI.

Important:
If your server is not factory new, make sure to reset the server and Cisco IMC to factory default settings before integrating the server with Cisco UCS Manager.

Connection Modes

You can connect up to seven C-Series server with Cisco UCS Mini for integrated management with Cisco UCS Manager in the following two ways:

- Direct Connect: Connect the C-Series rack mount server directly to the uplink port using supported cable. You can enable uplink ports as server ports and connect up to 3 rack servers to the uplink ports. One of the four uplink ports functions as an upstream switch.

- Scalability Port: Use a supported QSFP+Breakout cable in one scalability port to connect up to four servers.

Note

Using the scalability port requires a license.

See System requirements for more information on supported servers and cables. You can integrate Cisco UCS C-Series Rack-Mount Servers with Cisco UCS Manager in either one of the following setup options:

- Non-cluster setup: Connecting the C-Series Rack-Mount Server with one FI-IOM.

- Cluster setup: Connecting the C-Series Rack-Mount Server with both FI-IOMs .

- System Requirements

- Connecting C-Series Server in Direct Connect Mode

- Connecting C-Series Server in Scalability Port Mode

- Physical Connectivity Illustrations

- Managing the Rack-Mount Server in Cisco UCS Manager after Integration

- Upgrading the C-Series Server Firmware

- Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

System Requirements

You must have the following items to connect C-Series Rack-Mount Server with Cisco UCS Mini for integrated management with Cisco UCS Manager 3.0.

- A Cisco UCS Mini system that is running Cisco UCS Manager 3.0 or above.

- One of the supported C-Series Rack-Mount Servers and corresponding CIMC and BIOS versions listed in the following table:

Server

CIMC

BIOS

Cisco UCS C220 M3 Server

1.5(4)

1.5.4f

Cisco UCS C240 M3 Server

1.5(4)

1.5.4f

Cisco UCS C220 M4 Server

2.0(3f)

2.0.3d

Cisco UCS C240 M4 Server

2.0(3f)

2.0.3d

- The server must have the Cisco UCS VIC 1225 or Cisco UCS VIC 1227 installed. The Firmware and Boot Loader versions are:

- Recommended — 2.1(0.457a)

- Minimum required — 2.1(0.367e)

- The Cisco UCS VIC 1225 or Cisco UCS VIC 1227 must be installed in the correct slot in each server as mentioned in the following table:

Note

The Cisco UCS VIC 1227 is supported only on the Cisco UCS C220 M4 Server or Cisco UCS C240 M4 Server, and can only be installed in the MLOM slot.

Server

PCIe Slot

Cisco UCS C220 M3 Server

1

Cisco UCS C240 M3 Server

2

Cisco UCS C220 M4 Server

MLOM, 1

Cisco UCS C240 M4 Server

MLOM, 1, 2, 4, 5

Note

When both PCIe slots are populated, priority is given to the MLOM slot.

- Cables:

- For Direct Connect, you must have any one of the following supported AOC or Twinax cables. If you are connecting in cluster mode, make sure you have two of the same cables.

- SFP-10G-AOC1M

- SFP-10G-AOC3M

- SFP-10G-AOC5M

- SFP-10G-AOC7M

- SFP-10G-AOC10M

- SFP-H10GB-CU1M

- SFP-H10GB-CU3M

- SFP-H10GB-CU5M

- SFP-H10GB-ACU7M

- SFP-H10GB-ACU10M

- DS-SFP-FC8G-LW

- SFP-10G-LR

- For connecting to the scalability port, you must have any one of the following supported cables. If you are connecting in cluster mode to the scalability port, make sure you have two of the same cables.

- 40GBASE-CR4 QSFP+ to four 10GBASE-CU SFP+ direct attach breakout cable assembly, 1 meter passive

- 40GBASE-CR4 QSFP+ to four 10GBASE-CU SFP+ direct attach breakout cable assembly, 3 meter passive

- 40GBASE-CR4 QSFP+ to four 10GBASE-CU SFP+ direct attach breakout cable assembly, 5 meter passive

- 40GBASE-CR4 QSFP+ to four 10GBASE-CU SFP+ direct attach breakout cable assembly, 7 meter active

- 40GBASE-CR4 QSFP+ to four 10GBASE-CU SFP+ direct attach breakout cable assembly, 10 meter active

- QSFP-4X10G-AOC1M QSFP to 4 x SFP 10Gbps Active Optical Cable 1m QSFP to 4 x SFP 10Gbps Active Optical Cable 1m

- QSFP-4X10G-AOC2M QSFP to 4 x SFP 10Gbps Active Optical Cable 1m QSFP to 4 x SFP 10Gbps Active Optical Cable 2m

- QSFP-4X10G-AOC3M QSFP to 4 x SFP 10Gbps Active Optical Cable 1m QSFP to 4 x SFP 10Gbps Active Optical Cable 3m

- QSFP-4X10G-AOC5M QSFP to 4 x SFP 10Gbps Active Optical Cable 1m QSFP to 4 x SFP 10Gbps Active Optical Cable 5m

- QSFP-4X10G-AOC7M QSFP to 4 x SFP 10Gbps Active Optical Cable 1m QSFP to 4 x SFP 10Gbps Active Optical Cable 7m

- QSFP-4X10G-AOC10M QSFP to 4 x SFP 10Gbps Active Optical Cable 1m QSFP to 4 x SFP 10Gbps Active Optical Cable 10m

Connecting C-Series Server in Direct Connect Mode

Before you connect the server, make sure the Cisco UCS VIC 1225 or Cisco UCS VIC 1227 is installed in the correct slot for integration with Cisco UCS Manager. If the card is not installed in the correct slot, Cisco UCS Manager will not be able to detect the server and server discovery will not initiate.

Before You Begin

Important:
If your server is not factory new, make sure to reset the server and Cisco IMC to factory default settings before integrating the server with Cisco UCS Manager.

Procedure

Step 1

Install the server in the rack. See the Install and Upgrade Guide for the server that you are using. The install guides are available at the following url: Install and Upgrade Guides.

Step 2

Configure uplink ports on the FI-IOM as server ports.

Step 3

For non-cluster setup, connect one supported cable from a VIC adapter in the server to one port on FI-IOM on one side in the Cisco UCS Mini chassis. You can use any port on FI-IOM, but the port must be enabled for server traffic.

Step 4

(Optional)If you are connecting the server in cluster set-up, connect a second cable from the server to the other FI-IOM on the other side of the Cisco UCS Mini chassis.

Step 5

Attach a power cord to each power supply in your server, and then attach the power cord to a grounded AC power outlet.

Server discovery begins when power is applied.

Connecting C-Series Server in Scalability Port Mode

Before you connect the server, make sure the Cisco UCS VIC 1225 or Cisco UCS VIC 1227 is installed in the correct slot for integration with Cisco UCS Manager. If the card is not installed in the correct slot, Cisco UCS Manager will not be able to detect the server and server discovery will not initiate.

Procedure

Step 1

Install the server in the rack. See the Install and Upgrade Guide for the server that you are using. The install guides are available at the following url: Install and Upgrade Guides.

Step 2

Configure the scalability port on FI-IOM as a server port.

Step 3

For non-cluster setup, connect one supported QSFP+ to four SFP breakout cables from the scalability port on FI-IOM on one side in the Cisco UCS Mini chassis to one port of the VIC adapter in the server.

Step 4

(Optional)If you are connecting the server in cluster set-up, connect a second cable from the server to the other FI-IOM on the other side of the Cisco UCS Mini chassis.

Step 5

Attach a power cord to each power supply in your server, and then attach the power cord to a grounded AC power outlet.

Server discovery begins when power is applied.

Physical Connectivity Illustrations

The following images shows samples of physical connectivity for C-Series Rack-Mount Server with Cisco UCS Domain, Cisco UCS Manager, release 3.0.

Uplink Port

The following image shows the cabling configuration for integrating the C-Series rack mount server with Cisco UCS Manager 3.0, in Cisco UCS Mini, using the uplink ports The path shown in gold carry both management and data traffic.

Uplink Port

1

Uplink port in Cisco UCS Mini, FI-IOM.

2

C-Series Rack-Mount Server

3

Cisco UCS VIC 1225 in PCIe slot 1

Scalability Port

The following image shows the cabling configuration for integrating the C-Series rack mount server with Cisco UCS Manager 3.0, in Cisco UCS Mini, using the scalability port The path shown in gold carry both management and data traffic.

Scalability Port

1

Scalability port in Cisco UCS Mini, FI-IOM.

2

Cisco UCS VIC 1225 in PCIe slot 2.

3

C-Series Rack-Mount Servers

Managing the Rack-Mount Server in Cisco UCS Manager after Integration

You can manage and monitor all rack-mount servers that have been integrated with a Cisco UCS domain through Cisco UCS Manager. After the integration, you will perform all rack-mount server management tasks only through the service profiles from Cisco UCS Manager GUI or Cisco UCS Manager CLI. The C-Series Rack-Mount Server Cisco IMC is not accessible when you start managing the server with Cisco UCS Manager.

Cisco UCS Manager provides information, errors, and faults for each rack-mount server that it has discovered.

For more information on managing C-Series Rack-Mount Servers from Cisco UCS Manager, see the chapter on Managing Rack-Mount Servers in your release specific Cisco UCS Manager Configuration Guide.

Upgrading the C-Series Server Firmware

If your server CIMC release version does not meet the requirement for integration with Cisco UCS Manager, make sure to upgrade the server firmware before connecting the server with Cisco UCS domain. For more information on upgrading the C-Series server firmware, see the host upgrade utility quick start guide for your release Click Here

Important:
When you upgrade the C-Series server firmware for Cisco UCS C220 M4 or C240 M4 servers to Cisco UCS Manager 2.2(6c), you will see the following critical alarm:

Board controller upgraded, manual a/c power cycle required on server x

This alarm, documented in CSCuv45173, is incorrectly categorized as a critical alarm. It does not impact the functionality of the server, and can be ignored.

To avoid seeing this alarm, you can do one of the following:

- Create a custom host firmware package in Cisco UCS Manager to exclude the board controller firmware from the Cisco UCS Manager 2.2(6c) update and keep the older version.

- Upgrade Cisco UCS Manager infrastructure (A Bundle) to Release 2.2(6c) and continue to run the host firmware (C Bundle) on any Cisco UCS C220 M4 or C240 M4 server at a lower version, according to the mixed firmware support matrix in Table 2 of the Release Notes for Cisco UCS Manager, Release 2.2.

Procedure

Step 1

Download the HUU ISO file:

1. Navigate to the following URL: Click Here .

2. In the middle column, click Servers – Unified Computing.

3. In the right-hand column, click Cisco UCS C-Series Rack-Mount Standalone Server Software.

4. Choose the name of your model of server in the right column.

5. Click Unified Computing System (UCS) Server Firmware.

6. Choose the release number.

7. Click Download Now to download the ucs-server platform-huu-version_number.iso file.

8. Verify the information on the next page, and click Proceed With Download.

9. Continue through the subsequent screens to accept the license agreement and browse to a location where you want to save the file.

Step 2

If you want to prepare the ISO for a local upgrade, complete this step; Otherwise, go to Step Step 3.

1. Burn the ISO image onto a writable disk (CD).

2. Connect a VGA monitor and USB keyboard to the Cisco C-Series server.

3. Insert the disk into the USB DVD drive of the Cisco C-Series server.

4. Go to Step Step 4.

Step 3

Prepare the ISO for a remote upgrade using the KVM Console.

1. Use a browser to connect to the software on the server that you are upgrading.

2. in the address field of the browser, enter the IP address for that server, and then enter your username and password.

3. Click Launch KVM Console on the toolbar to launch the KVM Console.

4. In the KVM Console, click the Virtual Media.

5. Click Add Image and click the ucs-server-name-huu-version_number.iso file.

6. In the Client View area, in the Mapped column, check the check box for the ISO file that you added and then wait for mapping to complete.

7. After the ISO file appears as a mapped remote device, go to Step Step 4.

Step 4

Boot the server and press F6 when prompted to open the Boot Menu screen.

Step 5

In the Boot Menu screen, choose the prepared ISO:

- For a local upgrade, choose the physical or externally connected CD/DVD device and then press Enter.

- For a remote upgrade, choose Cisco vKVM-Mapped vDVD1.22, and press Enter.

The server boots from the selected device.

Step 6

After the HUU boots, Cisco End User License Agreement (EULA) appears, read the EULA and click:

- I Agree to agree with the license agreement and proceed with the update.

- I Disagree to cancel.

After you accept the EULA, when the Cisco Host Upgrade Utility window appears with a list of all the components that are available for update.

Step 7

If you want to update all the listed components, click Update all.

Note:

- If you are updating to 2.0 (x) from versions 1.5(1l) and before, or from version 1.5.3 both the active and the backup versions of Cisco IMC will be updated to 2.0(x).

- During update the KVM connection will be lost, you have to reconnect to view the progress of the updates.

Step 8

If you want update specific components from the list, choose the components that you want to update.

Step 9

Click Update.
Note:

- We recommend you update the firmware on all components using the Update all option, unless you want to specifically update the firmware of a component.

- When you update the firmware of one of the following three components: BIOS, , or CMC, we recommend that you also update the firmware of the other two components.

- If you update the firmware, click Exit and then Ok to activate the firmware.

- If you choose to update and any other component with it and if you have not chosen BIOS, then on exit, you will be prompted to update the Chassis Firmware, click Yes in the confirmation box to update the chassis firmware.

This initiates the update and the status of the update is displayed in the Update Status column. You can also view a more detailed log of a series of activities and statuses that are involved while updating the firmware in the Execution Logs section.

Step 10

If you want to update the firmware of the hard disk of a server, click Update HDD Firmware. A window displays a list of hard disk drives on the server that support new firmware. Hard disk drives that do not support firmware upgrades are not listed.
Important:
Updating the firmware of the hard disk drive could result in data loss. Cisco recommends that you take a complete system backup prior to updating the firmware.

1. To update the firmware of all the hard disks, click Update All.
With this option, HDDs with the latest firmware installed are not updated.

2. To update a specific HDD, choose the HDD and click Update.

Step 11

Reboot the server.

Step 12

Reboot the server, and click Last Update Verify to verify if the update was successfully completed.
This action compares the previously updated firmware version for each component that was updated using the HUU with the current version of the firmware on the components and provides the status of the update.

Step 13

If you want to save the log files of the update status for later use, click Save Logs.
Log files that contain a detailed status of the update are saved to an external USB device that is connected to the server physically or through the KVM vMedia.

Note:
If an error occurs while updating the firmware, you are prompted to save the error log. Click Save Logs to save the log to an externally connected USB. This log can be used for identifying the cause of the error and troubleshooting.

Step 14

Click Exit to exit from the HUU.
Note:

- If you have updated the and not the BIOS, when you click Exit, gets activated and you lose connectivity to the and KVM.

- If you have selected LOM for update and you are on shared LOM mode, when you click Exit, you lose connectivity to the and KVM.

What to Do Next

After upgrading the server to the compatible server release version, you must establish the physical connection for the server to make it a part of Cisco UCS domain.To connect the server to your Cisco UCS FEXes and FIs, see Connecting C-Series Server in Direct Connect Mode.

Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

When you manage a Cisco UCS C-Series server with Cisco UCS Manager software, a UCS Manager service profile is associated with the server. If you want to revert a C-Series server to standalone mode (so that it can be managed by CIMC software), you must do the following actions in UCS Manager:

Procedure

Step 1

Disassociate the UCS Manager service profile from the server.

Step 2

Decommission the server.
Caution:
If you do not disassociate the service profile from the server, MAC and WWN numbers assigned by UCS Manager might be kept by the server. This can cause numbering duplication and conflicts with other servers that are managed by UCS Manager. Also, if you revert a server to standalone mode without disassociating its service profile, any LSI RAID controller will not show as a bootable device in the standalone server, preventing local booting.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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.

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: Click Here . 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. (1110R)