Chapter 1. Cisco UCS C-Series Integration with Cisco UCS Manager

Overview

Integrating C-Series Rack Mount Server with Cisco UCS Manager

FEX Connection Mode and Discovery

Maximum Configurable vNICs/vHBAs Based on Number of FEX Uplinks

Supported RAID/Storage Controller Configurations

Chapter 2. Configuring SingleConnect

SingleConnect

Important Guidelines for SingleConnect

Management Connection Policy and Connection Mode

Requirements for SingleConnect Integration with Cisco UCS Manager

Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

Physical Connectivity Illustrations for SingleConnect Cluster Setup

Connecting the C-Series Server with UCS Domain in Non-cluster Setup

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

Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

Chapter 3. Configuring Direct Connect

Direct Connect Mode

Requirements for Direct Connect Mode Integration with Cisco UCS Manager 2.2

Management Connection Policy and Connection Mode

Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

Physical Connectivity Illustrations for Direct Connect Mode Cluster Setup

Connecting the C-Series Server with UCS Domain in Non-Cluster Setup

Migrating C-Series Servers from SingleConnect to Direct Connect Mode

Migrating C-Series Servers from Dual-wire Management to Direct Connect Mode

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

Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

Chapter 4. Configuring Dual-Wire Management

Dual-Wire Management

Requirements for Dual-wire Integration with Cisco UCS Manager

Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

Physical Connectivity Illustrations for Cluster Setup

Connecting the C-Series Server with UCS Domain in Non-cluster Setup

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

Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

Supported Network Adapter Cards for Dual-wire Integration

Supported Adapter Cards

Special Considerations for Integrated Servers

Supported FEX-to-FI Uplink Cable SFP Types

Integrated Server Power States vs Service Profile Power States

Cautions and Limitations for Adapter Cards

FEX Considerations

Chapter 5. Upgrading Earlier Release Version Servers for Cisco UCS Manager Integration

Required Items for Upgrade

Upgrading the C-Series Server Firmware

Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers

Migrating the Configuration to Release 2.2 or Later

Chapter 6. Troubleshooting

Replacing a Hardware Component on a Cisco UCS Manager Integrated C-Series Server

Preface

Audience

Conventions

Related Cisco UCS Documentation

Documentation Feedback

Copyright Page

Chapter 1. Cisco UCS C-Series Integration with Cisco UCS Manager

This chapter includes the following sections:

- Overview

- Integrating C-Series Rack Mount Server with Cisco UCS Manager

- FEX Connection Mode and Discovery

- Maximum Configurable vNICs/vHBAs Based on Number of FEX Uplinks

- Supported RAID/Storage Controller Configurations

Overview

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

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 CIMC to factory default settings before integrating the server with Cisco UCS Manager.

You can integrate Cisco UCS C-Series Rack-Mount Servers with Cisco UCS Manager in either one of the following setup:

- Cluster setup: Using two fabric extenders (FEXes) to connect the C-Series Rack-Mount Server with two fabric interconnects.

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

Integrating C-Series Rack Mount Server with Cisco UCS Manager

Cisco UCS Manager 2.2 provides three connectivity modes for Cisco UCS C-Series Rack-Mount Server management. The following are the connectivity modes:

- Dual-wire Management (Shared LOM): Shared LAN on Motherboard (LOM) ports on the rack server are used exclusively for carrying management traffic. A separate cable connected to one of the ports on the PCIe card carries the data traffic. Using two separate cables for managing data traffic and management traffic is also referred to as dual-wire management.

- SingleConnect (Sideband): Using Network Controller Sideband Interface (NC-SI), Cisco UCS VIC 1225 Virtual Interface Card (VIC) connects one cable that can carry both data traffic and management traffic. This feature is referred to as SingleConnect. For more information, see SingleConnect.

- Direct Connect Mode: Cisco UCS Manager release version 2.2 introduces an additional rack server management mode using direct connection (Sideband) to the Fabric Interconnect.

Note

The LOM ports on Cisco UCS C-Series Rack-Mount Servers integrated with Cisco UCS Manager can not be used for data traffic. The LOM ports are disabled when the C-Series Rack-Mount Servers are in Cisco UCS Manager mode.

The general prerequisites for Dual-wire integration with Cisco UCS Manager are built into the C-Series Rack-Mount Server CIMC release 1.4(6) or later. If you want to use the SingleConnect or direct connect modes you must have the following:

- Server CIMC release 1.4(6) or later

- Cisco UCS VIC 1225 Virtual Interface Card

- Cisco UCS VIC 1227 (MLOM)

- Cisco UCS VIC 1225T Virtual Interface Card

- Cisco UCS VIC 1227T (MLOM)

- Cisco UCS VIC 1387 (MLOM)

- Cisco UCS VIC 1385

Important:
For the third generation Cisco UCS VIC adapter or later (VIC 13xx), we recommend that you reset CIMC to factory default before connecting the Cisco VIC adapter to the UCS Fabric Interconnect switch.

Note

- The Cisco UCS VIC 1225T and 1227T adapters are supported only with Cisco Nexus 2232TM-E 10GE Fabric Extender using RJ45 Network cable.

- The Cisco UCS VIC 1385 and 1387 MLOM adapters are supported only on the C220 M4, C240 M4 and C460 M4 servers.

The following table lists theC-Series Rack-Mount Servers and supported management options:

Supported Management Options

Servers

SingleConnect

Direct Connect Mode

Dual-wire Management

Cisco UCS C22 M3 Server

Yes

Yes

Yes

Cisco UCS C24 M3 Server

Yes

Yes

Yes

Cisco UCS C200 M2 Server

No

No

Yes

Cisco UCS C210 M2 Server

No

No

Yes

Cisco UCS C220 M3 Server

Yes

Yes

Yes

Cisco UCS C220 M4 Server

Yes

Yes

Yes

Cisco UCS C240 M3 Server

Yes

Yes

Yes

Cisco UCS C240 M4 Server

Yes

Yes

Yes

Cisco UCS C250 M2 Server

No

No

Yes

Cisco UCS C260 M2 Server

Yes

Yes

Yes

Cisco UCS C420 M3 Server

Yes

Yes

Yes

Cisco UCS C460 M2 Server

Yes

Yes

Yes

Cisco UCS C460 M4 Server

Yes

Yes

Yes

Note

If you have a Cisco UCS Manager release earlier than 2.2(2a), integration is not supported for Cisco UCS C22 and C24 servers that have Intel E5-2400 v2 CPUs at this time. This integration is supported only with Intel E5-2400 v1 CPUs.

Based on your server model and CIMC version, you can use either one of these three integration options to connect the rack server withCisco UCS Manager 2.2.

Cisco UCS Manager runs within the fabric interconnect (FI). With earlier Cisco UCS Manager releases, you need to use Fabric Extenders to connect the c-series server with the Fabric Interconnect to enable management with Cisco UCS Manager. With Cisco UCS Manager release 2.2, you can directly connect the server adapter with the Fabric Interconnect without using the Fabric Extender.

You can use any of the interfaces available with this management service to access, configure, administer, and monitor the network and server resources for all chassis connected to the fabric interconnect. For information about the Cisco UCS 6100 Series or 6200 Series fabric interconnects, see the documentation at the following links:

- Cisco UCS 6100 Series Fabric Interconnect documentation

- Cisco UCS 6200 Series Fabric Interconnect documentation

For information about the Cisco Nexus 2232 fabric extenders (FEXes) in the configuration, see the documentation at the following link:

- Cisco Nexus 2000 Series Fabric Extender documentation

Hardware Maintenance

Replacing servers and certain adapter cards requires that the server be decommissioned and recommissioned. See the Decommissioning a Rack-Mount Server and Recommissioning a Rack-Mount Server sections in the appropriate Cisco UCS Manager Configuration Guide.

FEX Connection Mode and Discovery

You can connect the FEX to the FI in two ways. Cisco UCS Manager FI discovers the FEX based on the FEX/Chassis discovery mode. The FEX connection modes are:

- Hard-Pinning mode: The server facing FEX ports are pinned to the connected uplink ports when the FEX is discovered. Cisco UCS Manager pins the server-facing ports to the uplink ports based on the number of acknowledged uplink ports. After the pinning, if you add a new uplink or delete an existing uplink, you must manually acknowledge the FEX to apply the changes.

- Port-Channel mode: Port-Channel mode does not have pinning. A single port channel works as the uplink to all server-facing ports. And all uplink ports are members of this single port channel. If one of the uplink ports go down, the traffic is automatically distributed to another available uplink port.

Note

Port channel mode applies only to the 6200 series FIs.

In port-channel mode, when you cable between FEX and the FI, the available virtual interface (VIF) namespace varies, depending on where the uplinks are connected to the FI ports:

- When port-channel uplinks from the FEX are connected only within a set of eight ports managed by a single chip, Cisco UCS Manager maximizes the number of VIFs used in service profiles deployed on the servers.

- If uplink connections are distributed across ports managed by separate chips, the VIF count is decreased. For example, if you connect seven members of the port channel to ports 1–7, but the eighth member to port 9, this port channel can only support VIFs as though it had one member.

The Cisco UCS 6200 Series FI has six sets of eight contiguous ports. Each set of ports is managed by a single chip. For more information on FEX discovery policies and port-channel allocation, see the appropriate Cisco UCS Manager Configuration Guide.

Six Sets of Ports in Fabric Interconnect and Expansion Module

Maximum Configurable vNICs/vHBAs Based on Number of FEX Uplinks

The following table describes maximum configurable vNICs/vHBAs on a VIC adapter based on the number of FEX uplinks:

Cisco UCS 6100 Fabric Interconnect

Acknowledged link between FEX and FI

Maximum configurable vNICs/vHBA on a VIC adapter for the VIC adapter 1225, 1225T, 1227, 1227T, 1385, 1387T

Maximum configurable vNICs/vHBA on a VIC adapter for the adapter VIC P81E

1

Not supported

Not supported

2

3

4

4

9

10

8

21

22

Cisco UCS 6200 Fabric Interconnect

Acknowledged link between FEX and FI

Maximum configurable vNICs/vHBA on a VIC adapter for the VIC adapter 1225, 1225T, 1227, 1227T, 1385, 1387T

Maximum configurable vNICs/vHBA on a VIC adapter for the VIC adapter P81E

1

12

13

2

27

28

4

57

58

8

117

118

Supported RAID/Storage Controller Configurations

The following RAID/Storage controllers are supported for C-Series rack-mount servers integration with Cisco UCS Manager.

Supported RAID/Storage Controllers

Server

Supported RAID Controller

Cisco UCS C240 M3 (UCSC-C240-M3)

- Cisco UCSC RAID SAS 2008M-8i

- LSI MegaRAID SAS 9271-8i or 9271CV-8i 8-port PCIe RAID controller

- LSI MegaRAID 9286CV-8e 8-port PCIe RAID controller

- Cisco Nytro MegaRAID 200 GB PCIe RAID controller

Cisco UCS 220 M3 (UCSC-C220-M3)

- Cisco UCSC RAID SAS 2008M-8i

- LSI MegaRAID SAS 9271-8i or 9271CV-8i RAID 8-port PCIe RAID controller

- LSI MegaRAID 9286CV-8e PCIe RAID controller

Cisco UCS 22 M3 (UCSC-C22-M3)

- LSI MegaRAID 9270CV-8i

- LSI MegaRAID 9240-8i RAID 8-port PCIe RAID controller

- LSI MegaRAID 9220-8i RAID 8-port PCIe RAID controller

Cisco UCS C24 M3 (UCSC-C24-M3)

- LSI MegaRAID 9270CV-8i

- LSI MegaRAID 9240-8i RAID 8-port PCIe RAID controller

- LSI MegaRAID 9220-8i RAID 8-port PCIe RAID controller

Cisco UCS C240 M4 (UCSC-C240-M4)

- Embedded SATA-only storage controller

- Cisco 12G SAS Modular RAID controller

- Cisco 12 Gbps Modular SAS HBA RAID controller

- Cisco 9300-8E 12G SAS HBA RAID controller

Cisco UCS C220 M4 (UCSC-C220-M4)

- Embedded SATA-only storage controller

- Cisco 12G SAS Modular RAID controller

- Cisco 12 Gbps Modular SAS HBA RAID controller

- Cisco 9300-8E 12G SAS HBA RAID controller

Cisco UCS C460 M4 (UCSC-C460-M4)

- Cisco 12G SAS Modular RAID controller

- Cisco 12G SAS C460M4 RAID controller

- Cisco 12 Gbps Modular SAS HBA RAID controller

- Cisco 9300-8E 12G SAS HBA RAID controller

- LSI MegaRAID SAS 9361-8i RAID controller

Only servers without expanders can have more than one RAID controllers in the Cisco UCS Manager integrated mode. The following servers are allowed to have more than one RAID controllers in the Cisco UCS Manager integrated mode:

- Cisco UCS C24 M3 (UCSC-C24-M3S2)

- Cisco UCS C420 M3 (UCSC-C420-M3)

- Cisco UCS C240 M3 (UCSC-C240-M3S2)

- Cisco UCS C240 M3 NEBS (UCSC-C240-SNEBS)

- Cisco UCS C260 M2 (C260-BASE-2646)

Any server not on this list that has more than one RAID controllers installed fails discovery.

Note

The Embedded MegaRAID (Intel Corporation Patsburg Dual 4-Port SATA Storage Control Unit) controller is not supported in the Cisco UCS Manager integration.

Chapter 2. Configuring SingleConnect

This chapter includes the following sections:

- SingleConnect

- Important Guidelines for SingleConnect

- Management Connection Policy and Connection Mode

- Requirements for SingleConnect Integration with Cisco UCS Manager

- Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

- Physical Connectivity Illustrations for SingleConnect Cluster Setup

- Connecting the C-Series Server with UCS Domain in Non-cluster Setup

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

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

SingleConnect

Cisco UCS Manager 2.2 supports an option to integrate the C-Series Rack-Mount Server with Cisco UCS Manager using the NC-SI. This option enables Cisco UCS Manager to manage the C-Series Rack-Mount Servers using a single cable for both management traffic and data traffic. When you use the SingleConnect mode, one host facing port on the FEX is sufficient to manage one rack-mount server, instead of the two ports you will use in the Shared-LOM mode. So you can connect more number of rack-mount servers with Cisco UCS Manager for integrated server management. Make sure you have correct server firmware for integration with Cisco UCS Manager. If not, upgrade your server firmware before integrating the server with Cisco UCS Manager. See Upgrading the C-Series Server Firmware.

Note

C-Series Rack-Mount Servers C200, C210, and C250 do not support SingleConnect.

Important Guidelines for SingleConnect

SingleConnect has the following guidelines and limitations:

- To enable SingleConnect for the Cisco UCS Manager integration you must have the Cisco UCS VIC 1225, Cisco UCS VIC 1225T, Cisco UCS VIC 1227, Cisco UCS MLOM 1227T, Cisco UCS VIC 1385 and Cisco UCS MLOM 1387 installed in the specific slot assigned for SingleConnect in the rack server. If the VIC is not in the specific slot, SingleConnect does not work.

Important:
VIC 1225 refers specifically to UCSC-PCIE-CSC-02.

VIC 1225T refers specifically to UCSC-PCIE-C10T-02.

VIC 1227T MLOM refers specifically to UCSC-MLOM-C10T-02

VIC 1385 refers specifically to UCSC-PCIE-C40Q-03

VIC 1387 MLOM refers specifically to UCSC-MLOM-C40Q-03

- The Cisco UCS VIC 1225, Cisco UCS VIC 1225T, Cisco UCS VIC 1227, Cisco UCS VIC 1227T, Cisco UCS VIC 1385 and Cisco UCS MLOM 1387 also supports dual-wire management. If you have these VICs installed, you can select either SingleConnect or dual-wire management as your connection option. If you are selecting dual-wire, make sure LOM is also connected.

Note

Cisco VIC 1225T is supported only on C220-M3, C240-M3, C240-M4, C220-M4, and C460-M4 servers. Cisco MLOM 1227 and 1227T are supported only on C240-M4 and C220-M4 servers for integrated solutions. Cisco UCS VIC 1385 and Cisco UCS MLOM 1387 are supported only on C220 M4, C240 M4, and C460 M4 servers.

Management Connection Policy and Connection Mode

When establishing the physical connection for the C-Series Rack-Mount Server in the Cisco UCS Domain, you must specify the connection mode and management policy in Cisco UCS Manager GUI or Cisco UCS Manager CLI. The management policy is global to all connected C-Series Rack-Mount Servers. The connection mode determines the rack server discovery in Cisco UCS Manager. Direct connect supports only sideband connectivity.

You can specify either one of the following connection policies for the rack servers:

- Auto-acknowledged: This is the recommended and default connection mode for the C-Series Rack-Mount Server. If the connection mode is auto-acknowledged, immediately after establishing the physical connection, Cisco UCS Manager discovers the rack server and starts managing the server based on the specified management policy.

- User-acknowledged: If the connection mode is user-acknowledged, after establishing the physical connection, you must manually acknowledge the connection and specify the connection mode in the Cisco UCS Manager GUI or Cisco UCS Manager CLI to begin the discovery. Cisco UCS Manager does not begin the C-Series Rack-Mount Server discovery until you specify the connection mode.

Note

When rack servers are discovered and are managed by Cisco UCS Manager, if you want to change the existing connection mode for one C-Series Rack-Mount Server , you have to decommission the server, re-commission it and specify the new connection mode. Only then Cisco UCS Manager can discover the server in the new connection mode.

Requirements for SingleConnect Integration with Cisco UCS Manager

Requirements for Cluster Setup

You must have the following items to create a single-wire integration for C-Series Rack-Mount Server with Cisco UCS Manager in cluster setup:

- A Cisco UCS system that is running Cisco UCS Manager 2.2 and above.

- Any of the C-Series Rack-Mount Servers and corresponding CIMC and UCS Manager release versions listed in the following table:

Minimum Required Version of CIMC, BIOS and UCS Manager for SingleConnect Integration

Server

CIMC

BIOS

UCS Manager

Cisco UCS C22 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C24 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C220 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C220 M4 Server (requires 2.2.3 or above)

2.0(3d)

2.0.3

2.2(3a)

Cisco UCS C240 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C240 M4 Server (requires 2.2.3 or above)

2.0(3d)

2.0.3

2.2(3a)

Cisco UCS C260 M2 Server

1.4(6)

1.4.7

2.1(2a)

Cisco UCS C420 M3 Server

1.4(7)

1.4.8

2.1(2a)

Cisco UCS C460 M2 Server

1.4(6)

1.4.7

2.1(2a)

Cisco UCS C460 M4 Server

1.5(7a)

1.5.7

2.2(2a)

Note

For Cisco UCS C220 M4 and Cisco UCS C240 M4 servers you can use either MLOM or VIC to integrate with Cisco UCS Manager in SingleConnect or direct connect mode. The adapter for connectivity is selected as explained below:

- MLOM only: When only MLOM is present in the server, the connectivity adapter is by default MLOM,

- MLOM and VIC adapters: MLOM is the default connectivity adapter.

- No MLOM:

- If the Cisco UCS C220 M4 contains a VIC, it must be available in Riser1 - Slot 1 for SingleConnect or direct connect integration.

- If the Cisco UCS C240 M4 contains a VIC, it can be available MLOM or PCIe slot 2 for releases prior to 2.2(5), and for releases 2.2(5) onwards any x16 PCIe slot or MLOM.

- No MLOM and VIC: No SingleConnect or direct connect support.

Important:
The server must have Cisco UCS VIC 1225 or Cisco VIC 1227 or Cisco VIC 1225T or Cisco VIC 1227T or Cisco VIC 1385 or Cisco VIC 1387 MLOM installed. The Firmware and Boot Loader versions for Cisco UCS VIC 1225 or Cisco VIC 1227 are:

For the Cisco UCS 1225 and 1227 cards:

- Recommended — 2.1(0.457a)

- Minimum required — 2.1(0.367e)

For the Cisco UCS 1225T and 1227T cards:

- Recommended version — 4.0.4b

- Minimum version needed — 4.0.4b

For the Cisco UCS VIC 1385 and Cisco MLOM 1387 cards:

- Recommended version — 4.1.1a

- Recommended version — 4.1.1a

Cisco UCS 1225, Cisco UCS 1225T, Cisco UCS 1227T , Cisco UCS 1227, Cisco UCS 1385, and Cisco UCS 1387 VICs support single-connect. If you are using Cisco UCS VIC for single-connect, make sure the card is inserted in one of the slots as described in the following table:

Cisco UCS VIC Slot for SingleConnect Integration

Server

PCIe Slot

Cisco UCS C22 M3 Server

1

Cisco UCS C24 M3 Server

1

Cisco UCS C220 M3 Server

1

Cisco UCS C220 M4 Server

MLOM, 1

Cisco UCS C240 M3 Server

2

Cisco UCS C240 M4 Server

The supported slots are:

- For releases prior to 2.2(5)—MLOM or PCIe slot 2.

- For releases 2.2(5) onwards—any x16 PCIe slot or MLOM

Cisco UCS C260 M2 Server

7

Cisco UCS C420 M3 Server

4

Cisco UCS C460 M2 Server

1

Cisco UCS C460 M4 Server

4

- Note

Cisco UCS 1225, 1225T, and 1385 are PCIe based adapters and Cisco VIC 1227, Cisco VIC 1227T, Cisco VIC 1387 are MLOM based.

- Two Cisco UCS 6100 Series or 6200 Series FIs. The switch ports where Fabric Extenders (FEX) will be connected must be marked as server ports.

- Two Cisco Nexus 2232PP FEXes.

Note

You must plug a power cord into each of the two power supplies in the FEX. If the power is connected and there are issues in the hardware, you might see “Major” faults reported during the power-on self test (POST). For example, you might see this error: Power supply 1 in fex 6 power: error. You can clear errors by connecting any missing power cord to the FEX power supply.

- Four 10-Gb Small Form-Factor Pluggable (SFP) cables.

Note

- At least one cable to connect each FEX with corresponding FI.

- At least two cables to link the data traffic path between server and FEX.

- If you are using 6100 Series FI, you require two cables to connect each FEX to corresponding FI.

- At least four cables for uplinks from the FEX to FIs. You can either use 10-gb twinaxial cable or one of the following SFP type cables:

- SFP - 10GE-SR

- FET - 10GE

Important:
Do not mix SFP types on an uplink. If you mix the SFP types on an uplink, you will see Discovery Failed errors.

Requirement for Non-cluster Setup

If you are integrating the server in a non-cluster setup, along with the Cisco UCS Manager and C-series rack mount server, you will need the following components :

- One Cisco UCS 6100 Series or 6200 Series FIs. The switch ports where Fabric Extenders (FEX) will be connected must be marked as server ports.

- One Cisco Nexus 2232PP FEXes.

- Three 10-Gb SFP cables.

Note

- If you are using 6200 Series FI, the minimum requirement for SFP cable is 2.

- At least one cable for linking the data traffic path between server and FEX.

- At least two cables for uplinks from the FEX to FIs. Each of these two cables used for uplink from the FEX to FIs can either use 10-gb twinaxial cable or one of the following Small Form-Factor Pluggable (SFP) type cables:

- SFP - 10GE-SR

- FET - 10GE

Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

Before You Begin

Important:
Make sure the server CIMC is set to factory default settings to integrate with Cisco UCS Manager.

Before you connect the server, make sure the Cisco UCS VIC 1225 , Cisco UCS VIC 1225T, Cisco UCS VIC 1227T, Cisco UCS VIC 1227, Cisco UCS VIC 1385 or Cisco UCS VIC 1387 is installed in the correct slot for integration with Cisco UCS Manager. If the card is not installed in the correct slot, you cannot enable the single-wire management for the server.

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

Connect the path that carries both data traffic and management traffic to the FEXes:

1. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on the FEX that is connected to Fabric A. You can use any port on the FEX.

2. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on the FEX that is connected to Fabric B. You can use any port on the FEX.

Step 3

Connect the paths from the FEXes to the FIs.

1. Connect at least two 10-Gb SFP cables between FEX A and two ports on FI A. You can use any ports on FI A, but the ports must be enabled for server traffic.

2. Connect at least two 10-Gb SFP cables between FEX B and two ports on FI B. You can use any ports on FI B, but the ports must be enabled for server traffic.
Note:

- On the FEX, you can use only the right block of eight ports for uplinks. The maximum number of uplinks is eight

- Do not mix SFP types on an uplink. If you do, you will get Discovery Failed errors.

Step 4

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

Step 5

Reboot the server.

Physical Connectivity Illustrations for SingleConnect Cluster Setup

The following image shows a sample of SingleConnect physical connectivity for C-Series Rack-Mount Server with Cisco UCS Domain, Cisco UCS Manager, release 2.1 and above. This image shows the cabling configuration for Cisco UCS Manager integration with a C-Series Rack-Mount Server. The paths shown in gold carry both management traffic and data traffic.

SingleConnect Cabling Configuration

1

Cisco UCS 6100 Series or 6200 FI (Fabric A)

4

Cisco Nexus 2232PP FEX (Fabric B)

2

Cisco Nexus 2232PP FEX (Fabric A)

5

C-Series Rack-Mount Server

3

Cisco UCS 6100 Series or 6200 FI (Fabric B)

6

Cisco UCS VIC in supported PCIe or MLOM slot.

Note:

- MLOM based adapters (Cisco UCS VIC 1227 and 1227T) are supported only on C220 M4, and C240 M4 servers.

- While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G Qualified Security Assessor (QSA) converter but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

Connecting the C-Series Server with UCS Domain in Non-cluster Setup

You will follow the same steps explained in Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup. Instead of connecting two FIs and two FEXes, you will connect only one FI and one FEX.

Single-wire Non-Cluster Setup Example

The following illustration is an example of non-cluster setup in single-wire management.

1

Cisco UCS 6100 Series or 6200 FI (Fabric A)

4

C-Series Rack-Mount Server

2

Single Connect connection

5

Cisco UCS VIC in supported PCIe or MLOM slot.

Note:
While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G Qualified Security Assessor (QSA) converter but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

3

Cisco Nexus 2232PP FEX (Fabric A)

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.

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.

Chapter 3. Configuring Direct Connect

This chapter includes the following sections:

- Direct Connect Mode

- Requirements for Direct Connect Mode Integration with Cisco UCS Manager 2.2

- Management Connection Policy and Connection Mode

- Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

- Physical Connectivity Illustrations for Direct Connect Mode Cluster Setup

- Connecting the C-Series Server with UCS Domain in Non-Cluster Setup

- Migrating C-Series Servers from SingleConnect to Direct Connect Mode

- Migrating C-Series Servers from Dual-wire Management to Direct Connect Mode

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

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

Direct Connect Mode

Cisco UCS Manager 2.2 supports an option to connect the C-Series Rack-Mount Server directly to the Fabric Interconnects. You do not need the Fabric Extenders. This option enables Cisco UCS Manager to manage the C-Series Rack-Mount Servers using a single cable for both management traffic and data traffic.

Note

- After connecting the server with the FI, when the server is discovered, make sure to update the C-Series software bundle available for Cisco UCS Manager, release 2.2.

- While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G QSFP convertor but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

When you use direct connect mode, all Cisco UCS Managed adapters must be connected to the server ports on the Fabric Interconnects. Make sure you have server firmware as listed in the Requirements for Direct Connect Mode Integration with Cisco UCS Manager 2.2. If not, upgrade your server firmware before integrating the server with Cisco UCS Manager. See Upgrading the C-Series Server Firmware.

Note

C-Series Rack-Mount Servers C200, C210, and C250 do not support Direct Connect.

VIF Scalability

A maximum of 120 virtual interfaces will be allowed on each adapter in the server that is directly connected to the Fabric Interconnect.

Requirements for Direct Connect Mode Integration with Cisco UCS Manager 2.2

Requirements for Cluster Setup

You must have the following items to create a direct connect integration for C-Series Rack-Mount Server with Cisco UCS Manager in cluster setup:

- A Cisco UCS system that is running Cisco UCS Manager release 2.2 and above.

- Any of the following supported Cisco UCS C-Series servers and corresponding CIMC release versions listed in the following table:

Minimum Required Version of CIMC, BIOS and UCS Manager for Direct Connect Mode Integration

Server

CIMC

BIOS

UCS Manager

Cisco UCS C22 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C24 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C220 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C220 M4 Server (requires 2.2.3 or above)

2.0(3d)

2.0.3

2.2(3a)

Cisco UCS C240 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C240 M4 Server (requires 2.2.3 or above)

2.0(3d)

2.0.3

2.2(3a)

Cisco UCS C260 M2 Server

1.4(6)

1.4.7

2.1(2a)

Cisco UCS C420 M3 Server

1.4(7)

1.4.8

2.1(2a)

Cisco UCS C460 M2 Server

1.4(6)

1.4.7

2.1(2a)

Cisco UCS C460 M4 Server

1.5(7a)

1.5.7

2.2(2a)

Note

For Cisco UCS C220 M4 and Cisco UCS C240 M4 servers you can use either MLOM or VIC to integrate with Cisco UCS Manager in SingleConnect or direct connect mode. The adapter for connectivity is selected as explained below:

- MLOM only: When only MLOM is present in the server, the connectivity adapter is by default MLOM,

- MLOM and VIC adapters: MLOM is the default connectivity adapter.

- No MLOM:

- For Cisco UCS C220 M4, the VIC must be available in Riser1 - Slot 1 for direct connect integration.

- For Cisco UCS C240 M4, the VIC can be available on MLOM or PCIe slot 2 for releases prior to 2.2(5), and for releases 2.2(5) onwards any x16 PCIe slots or MLOM for direct connect integration.

- No MLOM and VIC: No SingleConnect or direct connect support.

Important:
Direct connect supports only the VIC firmware that supports SingleConnect. The server must have Cisco UCS VIC 1225 or Cisco UCS VIC 1227 or Cisco UCS 1225T or Cisco UCS 1227T or Cisco UCS VIC 1385 or Cisco UCS VIC 1387 MLOM installed. The Firmware and Boot Loader versions are:

For the Cisco UCS VIC 1225 or Cisco UCS VIC 1227 cards:

- Recommended — 2.1(0.457a)

- Minimum required — 2.1(0.367e)

For the Cisco UCS 1225T or Cisco UCS 1227T cards:

- Recommended — 4.0.4b

- Minimum required — 4.0.4b

For the Cisco UCS VIC 1385 or Cisco UCS VIC 1387 MLOM cards:

- Recommended — 4.1.1a

- Minimum required — 4.1.1a

The Cisco UCS VIC adapters must be installed in the correct slot in each server as mentioned in the following table:

Cisco UCS VIC Adapters Slot for Direct Connect Integration

Server

PCIe Slot

Cisco UCS C22 M3 Server

1

Cisco UCS C24 M3 Server

1

Cisco UCS C220 M3 Server

1

Cisco UCS C220 M4 Server

1

Cisco UCS C240 M3 Server

2

Cisco UCS C240 M4 Server

The supported slots are:

- For releases prior to 2.2(5)—MLOM or PCIe slot 2.

- For releases 2.2(5) onwards—any x16 PCIe slot or MLOM

Cisco UCS C260 M2 Server

7

Cisco UCS C420 M3 Server

4

Cisco UCS C460 M2 Server

1

Cisco UCS C460 M4 Server

4

- Two Cisco UCS 6100 Series or 6200 Series FIs. The ports must be configured as server ports.

- At least two 10-Gb Small Form-Factor Pluggable (SFP) cables for one card.

Requirement for Non-cluster Setup

If you are integrating the server in a non-cluster setup, along with the Cisco UCS Manager and C-series rack mount server, you will need the following components :

- One Cisco UCS 6100 Series or 6200 Series FIs. The ports where must be configured as server ports.

- At least one 10-Gb SFP cable for each card. You cannot connect the card to the same FI from both the ports.

Management Connection Policy and Connection Mode

When establishing the physical connection for the C-Series Rack-Mount Server in the Cisco UCS Domain, you must specify the connection mode and management policy in Cisco UCS Manager GUI or Cisco UCS Manager CLI. The management policy is global to all connected C-Series Rack-Mount Servers. The connection mode determines the rack server discovery in Cisco UCS Manager. Direct connect supports only sideband connectivity.

You can specify either one of the following connection policies for the rack servers:

- Auto-acknowledged: This is the recommended and default connection mode for the C-Series Rack-Mount Server. If the connection mode is auto-acknowledged, immediately after establishing the physical connection, Cisco UCS Manager discovers the rack server and starts managing the server based on the specified management policy.

- User-acknowledged: If the connection mode is user-acknowledged, after establishing the physical connection, you must manually acknowledge the connection and specify the connection mode in the Cisco UCS Manager GUI or Cisco UCS Manager CLI to begin the discovery. Cisco UCS Manager does not begin the C-Series Rack-Mount Server discovery until you specify the connection mode.

Note

When rack servers are discovered and are managed by Cisco UCS Manager, if you want to change the existing connection mode for one C-Series Rack-Mount Server , you have to decommission the server, re-commission it and specify the new connection mode. Only then Cisco UCS Manager can discover the server in the new connection mode.

Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

Before You Begin

Important:
Make sure the server CIMC is set to factory default settings to integrate with Cisco UCS Manager.

- Make sure the FI ports are configured as server ports. If they are not, reconfigure the ports as server ports using the Cisco UCS Manager GUI.

- Before you connect the server, make sure the Cisco UCS VIC 1225 or Cisco VIC 1227 is installed in the correct slot for integration with Cisco UCS Manager. If the card is not installed in the correct slot, you cannot enable the direct connect management for the server.

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 server ports on the FI.

Step 3

Connect the paths from Cisco UCS VIC 1225 or Cisco VIC 1227 to the server ports on the FIs.

1. Connect one 10-Gb SFP cables between the server and one port on FI A. You can use any port on FI A, but the port must be enabled for server traffic.
Make sure to connect one cable from the VIC to the FI for one card. You cannot connect both ports in the same FI.

2. Connect one 10-Gb SFP cable between the server and one port on FI B. You can use any port on FI B, but the port must be enabled for server traffic.
Note:
Do not mix SFP types on an uplink. If you do, you will get Discovery Failed errors.

Step 4

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 for Direct Connect Mode Cluster Setup

The following images shows a sample of direct connect mode physical connectivity for C-Series Rack-Mount Server with Cisco UCS Domain, Cisco UCS Manager, release 2.2. This image shows the cabling configuration for Cisco UCS Manager integration with a C-Series Rack-Mount Server. The paths shown in gold carry both management traffic and data traffic.
Direct Connect Cabling Configuration

1

Cisco UCS 6100 Series or 6200 FI (Fabric A)

3

C-Series Rack-Mount Server

2

Cisco UCS 6100 Series or 6200 FI (Fabric B)

4

Cisco UCS VIC 1225 in supported PCIe slot.

Note:
While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G Qualified Security Assessor (QSA) converter but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

Connecting the C-Series Server with UCS Domain in Non-Cluster Setup

You will follow the same steps explained in Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup. Instead of using two FIs to connect two cables as you will do in cluster setup, you will connect only one FI and one cable to the adapter.

Physical Connectivity Illustration Example for Direct Connect Mode Non-Cluster Setup

The following image show the cabling configuration for Cisco UCS Manager integration with the server. The path shown in gold carry both management and data traffic.

1

Cisco UCS 6100 Series or 6200 FI (Fabric A)

2

C-Series Rack-Mount Server

3

Cisco VIC in supported PCIe slot.
Note:
While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G Qualified Security Assessor (QSA) converter but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

Migrating C-Series Servers from SingleConnect to Direct Connect Mode

Before performing the migration procedure, on the Cisco UCS Manager GUI, Global Policies page, make sure the Rack Discovery Policy and Rack Management Connection Policies are set to the defaults such as,Immediate and Auto Acknowledge. This will make sure after connecting the server directly to the FI, the server is discovered immediately and Cisco UCS Manager starts managing the server without waiting for your interaction.

Caution

Migrating from SingleConnect FEX connectivity to direct connect is a disruptive process. Make sure you do this during a scheduled outage window. You might need 15 to 20 minutes to complete this procedure.

Procedure

Step 1

Configure the server ports on the FI.

Step 2

Disconnect the cables from the FEX and connect them to the ports on Fabric Interconnect.

Step 3

On the Cisco UCS Manager GUI, right click the server, from the pop-up menu, select Recover Server or Server Maintenance.

Step 4

Click Re-acknowledge and select OK. This will cause server reboot.

After the server reboots, you can resume normal operations.

Migrating C-Series Servers from Dual-wire Management to Direct Connect Mode

Before performing the migration procedure, on the Cisco UCS Manager GUI, Global Policies page, make sure the Rack Discovery Policy and Rack Management Connection Policies are set to the defaults such as,Immediate and Auto Acknowledge. This will make sure after connecting the server directly to the FI, the server is discovered immediately and Cisco UCS Manager starts managing the server without waiting for your interaction.

Caution

- Migrating from Dual-wire FEX connectivity to direct connect is a disruptive process. Make sure you do this during a scheduled outage window. You might need 15 to 20 minutes to complete this procedure.

- You must decommission the server before performing the migration.

To enable direct connect mode to a server connected in dual-wire management mode, you will need to change the adapter. Changing the adapter may impact the PCIe numbering on a bare metal Windows system. If you had Adapters listed in the OS, after you change them they will be Adapter 3 and 4. If you are using static addressing, you will need to remove the previous adapters from the server. For more information, see Click Here

Procedure

Step 1

Configure the server ports on the FI.

Step 2

Decommission the server.

Step 3

If you are not using Cisco UCS VIC 1225 or Cisco UCS VIC 1227, change the Cisco UCS VIC physically in the server:

1. Unplug power cable, management LOMs and SFP twinax connections from the back of the server.

2. Slide the server out of the rack and remove the top cover.

3. Remove the PCIe riser card from the slot and remove the existing Adapter and then install Cisco UCS VIC 1225.

4. Reinstate the PCIe riser card into the slot, place the top cover back on the server and push the server back into the rack.

5. (Optional)If you would no longer require the FEX to connect any server in dual wire mode, unplug the FEX from Cisco UCS Manager, and power and remove the FEX from the rack server.

Step 4

Connect the SFP twinax cables from the Cisco VIC port to the FI ports.

Step 5

Reconnect the power cable to the server. CIMC has standby, so you need not power the server.

What to Do Next

Recommission the server from Cisco UCS Manager GUI. After the recommission is complete, the server is ready for operation and you can apply service profiles to the server.

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.

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.

Chapter 4. Configuring Dual-Wire Management

This chapter includes the following sections:

- Dual-Wire Management

- Requirements for Dual-wire Integration with Cisco UCS Manager

- Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

- Physical Connectivity Illustrations for Cluster Setup

- Connecting the C-Series Server with UCS Domain in Non-cluster Setup

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

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

- Supported Network Adapter Cards for Dual-wire Integration

- Special Considerations for Integrated Servers

Dual-Wire Management

Cisco UCS Manager version 2.2 supports the existing rack server integration and management option through Shared LOM, using two separate cables for data traffic and management traffic. The prerequisites for integration with Cisco UCS Manager are built into the C-Series servers. Make sure you have correct server firmware for integration with Cisco UCS Manager. If not, upgrade your server firmware before integrating the server with Cisco UCS Manager. See Upgrading the C-Series Server Firmware.

Requirements for Dual-wire Integration with Cisco UCS Manager

Requirements for Cluster Setup

The following are the requirements for C-series server integration with Cisco UCS Manager version 2.2 in cluster setup:

- A Cisco UCS system running Cisco UCS Manager software release 2.2.

- An adapter that supports dual-wire integration.

- Any of the Cisco UCS C-Series servers and corresponding Cisco UCS Manager release version:

Note

- If you install Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), and want to use this card for UCS integration, the minimum card-firmware level requirement is 2.0(2g). See the section on Special Considerations for the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), in Install and Upgrade Guides. For P81E UBOOT firmware update, see Updating Server Firmware and UBOOT.

- Cisco UCS 1225, Cisco UCS 1225T, Cisco UCS 1227T and Cisco UCS 1227 VICs also support dual-wire management. If you are using Cisco UCS 1225 VIC, Cisco UCS 1225T, Cisco UCS 1227T , Cisco UCS VIC 1385, Cisco UCS VIC 1387 or Cisco UCS 1227 for dual-wire management, make sure the card is inserted in one of the slots as described in the following table:

Cisco UCS VIC Slot for Dual-wire Integration

Server

PCIe Slot

Cisco UCS C22 M3 Server

1

Cisco UCS C24 M3 Server

1

Cisco UCS C220 M3 Server

1

Cisco UCS C220 M4 Server

Any x16 slot

Cisco UCS C240 M3 Server

2, 5

Cisco UCS C240 M4 Server

The supported slots are:

- For releases prior to 2.2(5)—MLOM or PCIe slot 2.

- For releases 2.2(5) onwards—any x16 PCIe slot or MLOM

Cisco UCS C260 M2 Server

1, 7

Cisco UCS C420 M3 Server

1, 4, 7

Cisco UCS C460 M2 Server

1, 2

Cisco UCS C460 M4 Server

2, 3, 4, 5, 7, 8, 9, 10

Note:
Slot 1 and 6 do not support installing Cisco VIC 1225.

- Two Cisco UCS 6100 Series or 6200 Series FIs. The switch ports that carry server traffic must be enabled as server ports.

- Two Cisco Nexus 2232PP FEXes.

Note

You must plug a power cord into each of the two power supplies in the FEX. If a power supply is not connected to power, you might see “Major” faults reported during power-on self test (POST). For example, Power supply 1 in fex 6 power: error. You can clear these errors by connecting the missing power cord to the FEX power supply.

- Two RJ-45 Ethernet cables. The RJ-45 Ethernet cables are used to connect the management traffic paths.

- Two 1000BASE-T SFP transceivers (GLC-T)

- Four 10-Gb Small Form-Factor Pluggable (SFP) cables.

Note

- At least one cable to connect each FEX with corresponding FI.

- At least two cables to link the data traffic path between server and FEX.

- If you are using 6100 Series FI, you require two cables to connect each FEX to corresponding FI.

- At least four cables for uplinks from the FEX to FIs. You can either use 10-gb twinaxial cable or one of the following SFP type cables:

- SFP - 10GE-SR

- FET - 10GE

Important:
Do not mix SFP types on an uplink. If you mix the SFP types on an uplink, you will see Discovery Failed errors.

Requirement for Non-cluster Setup

If you are integrating the server in a non-cluster setup, along with the Cisco UCS Manager and C-series rack mount server, you will need the following components :

- One Cisco UCS 6100 Series or 6200 Series FIs. The switch ports where Fabric Extenders (FEX) will be connected must be marked as server ports.

- One Cisco Nexus 2232PP FEXes.

- One RJ-45 Ethernet cable. The RJ-45 Ethernet cable connects the management traffic path.

- One 1000BASE-T SFP transceiver (GLC-T)

- Three 10-Gb SFP cables.

Note

- If you are using 6200 Series FI, the minimum requirement for SFP cable is 4.

- Two cables for linking the data traffic path between server and FEX.

- Four cables for uplinks from FEX to fabric interconnects. Each of these four cables used for uplink from FEX to FIs can either use supported 10-gb twinaxial cable or one of the following SFP type cables:

- SFP - 10GE-SR

- FET - 10GE

Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

To view illustrations on the connectivity for each C-Series Rack-Mount Server, see Physical Connectivity Illustrations for Cluster Setup.

Important:
Make sure the server CIMC is set to factory default settings to integrate 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

To connect the management traffic paths, do the following:

1. Insert one GLC-T transceiver into a port of the FEX that is connected to Fabric A. You can use any port on the FEX.

2. Insert one GLC-T transceiver into a port of the FEX that is connected to Fabric B. You can use any port on the FEX.

3. Connect an RJ-45 Ethernet cable between a 1-Gb port on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric A.

4. Connect an RJ-45 Ethernet cable between a 1-Gb port on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric B.

Step 3

To connect the data traffic paths, do the following:

1. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on a FEX in Fabric A. You can use any port on the FEX.

2. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on a FEX in Fabric B. You can use any port on the FEX.

Step 4

Connect the paths from the FEXes to the FIs. These paths carry both data and management traffic.

1. Connect two 10-Gb SFP cables between FEX A and two ports on FI A. You can use any ports on FI A, but the ports must be enabled for server traffic.

2. Connect two 10-Gb SFP cables between FEX B and two ports on FI B. You can use any ports on FI B, but the ports must be enabled for server traffic.
Note:

- On the FEX, you can use only the right block of eight ports for uplinks.

- The maximum number of uplinks is eight. Based on the Cisco UCS Manager FI discovery policy the port cabling requirement between the FEX and FI vary.

- Do not mix SFP types on an uplink. If you do, you will see Discovery Failed errors.

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.

Step 6

Reboot the server.

Physical Connectivity Illustrations for Cluster Setup

The following image shows a samples of the physical connectivity for C-Series Rack-Mount Server with Cisco UCS Domain, Cisco UCS Manager, release 2.0(2) and above.

This image shows the cabling configuration for Cisco UCS Manager integration with a C-Series Rack-Mount Server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

Cluster Setup Cabling Configuration

1

Cisco UCS 6100 Series or 6200 FI (Fabric A)

6

Cisco Nexus 2232PP FEX (Fabric B)

2

GLC-T transceiver in FEX port (Fabric A)

7

C-Series Rack-Mount Server

3

Cisco Nexus 2232PP FEX (Fabric A)

8

1-Gb Ethernet LOM ports

4

Cisco UCS 6100 Series or 6200 FI (Fabric B)

9

10-Gb Adapter card in supported PCIe slot

Note:
While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G Qualified Security Assessor (QSA) converter but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

5

GLC-T transceiver in FEX port (Fabric B)

Connecting the C-Series Server with UCS Domain in Non-cluster Setup

You will follow the same steps explained in Connecting the C-Series Server with Cisco UCS Domain in Non-cluster Setup. Instead of connecting two FIs and two FEXes, you will connect only one FI and one FEX.

Dual-wire Non-Cluster Setup Example

The following illustration is an example of non-cluster setup in dual-wire management.

1

Cisco UCS 6100 Series or 6200 FI (Fabric A)

4

Cisco UCS C-series server

2

GLC-T transceiver in FEX port (Fabric A)

5

1-Gb Ethernet LOM ports

3

Cisco Nexus 2232PP FEX (Fabric A)

6

10-Gb Adapters in supported slots

Note:
While using Cisco VIC 1385 and 1387 in a 10G connection you would a require a 40G to 10G Qualified Security Assessor (QSA) converter but you cannot use the 4x10 Breakout Small Form-Factor Pluggable (SFP) cables and 4x10 Active Optical (OAC) cables.

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.

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.

Supported Network Adapter Cards for Dual-wire Integration

The following Network Adapter cards support Cisco UCS Manager integration :

- Cisco Virtual Interface Cards (VICs)

- Converged Network Adapters (CNAs)

- Ethernet adapters

- Supported Adapter Cards

Supported Adapter Cards

The following table shows the officially supported adapter cards for C-Series Rack-Mount Servers integration with Cisco UCS Manager.

Note

- Cisco UCS Manager provides management support for up to four adapter cards from the following list.

- Make sure to check the number of supported VICs by server type from C-Series Hardware Installation Guide.

Supported Adapter Cards

Adapter/Server Model

C22
M3S

C24 M3S

C200 M2

C210 M2

C220 M3

C220 M4

C240 M3

C240 M4

C250 M2

C260 M2

C420 M3

C460 M2

C460 M4

Cisco UCS 1225 VIC

(UCSC-PCIE-CSC-02)

Y

Y

-

-

Y

Y

Y

Y

-

Y

Y

Y

Y

Cisco UCS 1225T VIC

(UCSC-PCIE-C10T-02)

-

-

-

-

Y

Y

Y

Y

-

-

-

-

Y

Cisco UCS P81E VIC

(N2XX-ACPCI01)

Y

Y

Y

Y

Y

-

Y

-

Y

Y

-

Y

-

Cisco UCS 1227 (mLOM )

UCSC-MLOM-CSC-02

-

-

-

-

-

Y

-

Y

-

-

-

-

-

Cisco MLOM 1227T

(UCSC-MLOM-C10T-02)

-

-

-

-

-

Y

-

Y

-

-

-

-

-

Cisco UCS 1385 VIC

(UCSC-PCIE-C40Q-03)

-

-

-

-

-

Y

-

Y

-

-

-

Y

Cisco MLOM 1387

(UCSC-MLOM-C40Q-03)

-

-

-

-

-

Y

-

Y

-

-

-

Y

Emulex OCe10102-F CNA

(N2XX-AEPCI01)

-

-

Y

Y

-

-

-

-

Y

Y

-

Y

-

Emulex OCe11102-FX CNA

(UCSC-PCIE-ESFP)

Y

Y

-

-

Y

Y

Y

Y

-

-

Y

-

Y

Emulex OCe 14102

(UCSC-PCIE-E14102)

-

-

-

-

-

Y

-

Y

-

-

-

-

-

Emulex OCe 14102B

(UCSC-PCIE-E14102B)

-

-

-

-

-

Y

-

Y

-

-

-

-

-

QLogic QLE8152 CNA

(N2XX-AQPCI01)

-

-

Y

Y

-

-

-

-

Y

Y

-

Y

-

QLogic QLE8242 CNA

(UCSC-PCIE-QSFP)

Y

Y

-

-

Y

-

Y

-

-

-

Y

-

-

QLogic QLE8362 CNA

(UCSC-PCIE-Q8362)

Y

Y

-

-

Y

-

Y

-

-

-

Y

-

-

Qlogic 8442 SFP+

(UCSC-PCIE-QNICSFP)

Y

Y

Y

Y

Y

Y

Y

Y

Y

-

-

Qlogic 8442 10GBaseT

(UCSC-PCIE-QNICBT)

Y

Y

Y

Y

Y

Y

Y

Y

Y

-

-

Broadcom BCM57711 10Gb

(N2XX-ABPCI02)

-

-

Y

Y

-

-

-

-

Y

-

-

Y

-

Broadcom BCM57712 10Gb

UCSC-PCIE-BSFP

Y

Y

Y

Y

Y

-

Y

-

Y

Y

Y

Y

-

Broadcom BCM 57810 10Gb

UCSC-PCIE-B3SFP

-

-

-

-

Y

Y

Y

Y

-

Y

Y

-

Y

Intel X520 10Gb

(N2XX-AIPCI01)

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Nvidia M60

(UCSC-GPU-M60)

-

-

-

-

-

-

-

Y

-

-

-

Y

Special Considerations for Integrated Servers

When you connect the C-Series servers in Cisco UCS system, make sure to review the following information:

- Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers

- Integrated Server Power States vs Service Profile Power States

- Cautions and Limitations for Adapter Cards

- FEX Considerations

- Supported FEX-to-FI Uplink Cable SFP Types

- Integrated Server Power States vs Service Profile Power States

- Cautions and Limitations for Adapter Cards

- FEX Considerations

Supported FEX-to-FI Uplink Cable SFP Types

The C-Series UCSM integration requires six 10-Gb SFP cables for the following purposes:

- Linking the data traffic paths between server and FEX - 2 cables

- Uplinks from the FEXes to the FIs - 4 cables

Each of the four uplinks from the FEXes to the FIs can use either a Cisco 10-Gb twinax cable, or one of the following SFP types:

- SFP-10GE-SR

- FET-10GE

Caution

Do not mix SFP types on an uplink. If you mix SFP types on an uplink, you will get Discovery failed errors.

Integrated Server Power States vs Service Profile Power States

Using the power button or Cisco UCS Manager, if you set the desired power status to Down for an integrated C-Series server's associated service profile, when you try to rest the server to the desired power state, the server becomes out of sync with the actual power state. This may cause the server to shut down unexpectedly at a later time.

Use the Boot Server action in Cisco UCS Manager to safely reboot a server from a power-down state.

The following table shows how the physical server power states can differ from the Cisco UCS Manager service profile power states when the power button on the server is used.

Difference in Server Power State and Service Profile Power State

Initial Service Profile Power State

Server Initial Power State

Action From Physical Power Button

Actual Server Power State After the Action

Power State Under UCSM Equipment Tab

Desired Power State Under Service Profile

Down

Off

Push button to turn on

On

On

Down

Up

On

Push button to turn off

Off

Off

Up

Cautions and Limitations for Adapter Cards

Make sure to consider the following when using the adapter cards in Cisco UCS C-Series server integration with Cisco UCS Manager:

- Cisco UCS Manager supports only four UCS managed adapter cards in the integrated Cisco UCS C-series servers, even if the server has more than four PCI slots. If you have more than four adapter cards in the server, after integration, the rack server discovery fails in Cisco UCS Manager.

- When you add, remove, or replace an adapter card in a UCS-managed server, you must first decommission the server in Cisco UCS Manager. After the operation, you must then recommission the server.

- If an integrated server contains two Cisco UCS P81E Virtual Interface Cards, the vNICs/vHBAs on Adapter 1 might have a higher PCI order in Cisco UCS Manager than the vNICs/vHBAs on Adapter 2.

- In C200 or C210 servers, BIOS version 1.4(3c) and later, you have an option to enable or disable SR-IOV/ARI (single-root I/O virtualization/alternative routing-ID interpretation) bus reservation. Whenever you change the SR-IOV/ARI bus reservation settings on a UCS-managed server, you must re-acknowledge the server.

- If you install more than one adapter in the server each adapter in a cluster UCS Manager environment, each adapter must be connected to both path A and B. Attempting to connect both ports on an adapter to a single path results in a discovery failure due to an unsupported configuration. If you attempt to connect only one link from each adapter to the fabric, the server may reboot during a card failure to rediscover the data pathways. Neither of these scenarios are supported with connectivity options.

FEX Considerations

Re-acknowledge Attached Servers After a FEX Is Decommissioned/Recommissioned

Whenever you decommission or recommission a Cisco UCS FEX, all the servers that are connected to that FEX must be re-acknowledged in UCS Manager.

Chapter 5. Upgrading Earlier Release Version Servers for Cisco UCS Manager Integration

This chapter includes the following sections:

- Required Items for Upgrade

- Upgrading the C-Series Server Firmware

- Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers

- Migrating the Configuration to Release 2.2 or Later

Required Items for Upgrade

The following are the minimum Server CIMC version and Cisco UCS Manager version requirements for upgrade for C-Series server integration with Cisco UCS Manager:

Server

CIMC

BIOS

UCS Manager

Cisco UCS C22 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C24 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C220 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C220 M4 Server (requires 2.2.3 or above)

2.0(3d)

2.0.3

2.2(3a)

Cisco UCS C240 M3 Server

1.4(6)

1.4.7a

2.1(2a)

Cisco UCS C240 M4 Server (requires 2.2.3 or above)

2.0(3d)

2.0.3

2.2(3a)

Cisco UCS C260 M2 Server

1.4(6)

1.4.7

2.1(2a)

Cisco UCS C420 M3 Server

1.4(7)

1.4.8

2.1(2a)

Cisco UCS C460 M2 Server

1.4(6)

1.4.7

2.1(2a)

Cisco UCS C460 M4 Server

1.5(7a)

1.5.7

2.2(2a)

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 CIMC GUI software on the server that you are upgrading.

2. in the address field of the browser, enter the CIMC 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, CIMC, or CMC, we recommend that you also update the firmware of the other two components.

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

- If you choose to update CIMC 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 CIMC and not the BIOS, when you click Exit, CIMC gets activated and you lose connectivity to the CIMC 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 CIMC 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 the C-Series Server with Cisco UCS Domain in Cluster Setup for SingleConnect or Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup for dual-wire management.

Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers

If your Cisco UCS P81E VIC firmware and uboot version is earlier than 2.0(2g), when you integrate the server with any Cisco UCS Manager version, the UCS Manager software will return discovery and associate/disassociate failures. To avoid such failures you can do the following:

- Before you integrate the server with UCS System, upgrade your P81E VIC firmware and uboot image to the required minimum 2.0(2g) level in standalone mode.

- If your server is already integrated, you cannot upgrade the P81E VIC uboot image in the UCS Manager software. You have to remove the server from the integration and then use Cisco Host Upgrade Utility to upgrade the card and server firmware.

The following procedure provides the process to upgrade when your server is integrated with Cisco UCS Manager.

Procedure

Step 1

Decommission the server from UCS Manager.

Step 2

Disconnect the cables from the 1-Gb LOM ports on the server.

Step 3

Connect an Ethernet line from your LAN to one of the 1-Gb LOM ports (not to the dedicated management port, which is disabled in UCSM mode).

Step 4

Find the Host Upgrade Utility ISO file download for your server online and download it to a temporary location on your workstation:

1. See the following URL: http://www.cisco.com/cisco/software/navigator.html

2. Click Unified Computing and Servers in the middle column.

3. Click Cisco UCS C-Series Rack-Mount Standalone Server Software in the right-hand column.

4. Click your model of server in the right-hand column.

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

6. Click the release number that you are downloading.

7. Click Download Now to download the ISO file.

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

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

Step 5

Prepare the ISO. For local upgrade, on a local media and for remote upgrade, as a virtual device:

Option

Description

Local upgrade

Perform the steps before going to Step 3:

1. Burn the ISO image onto a writable DVD.

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

3. Insert the DVD into the DVD drive of the Cisco C-Series server or an external DVD drive.

Remote upgrade

Perform the steps before going to Step 3:

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

2. Enter the CIMC IP address for that server in the address field of the browser, then enter your user name and password.

3. Launch a KVM Console window (click the KVM keyboard icon).

4. When the Virtual KVM Console window launches, select Tools > Launch Virtual Media.

5. In the Virtual Media Session window, click Add Image and navigate to the utility ISO file and select it. Navigate to the location where you downloaded the ISO. The ISO image is displayed in the Client View area.

6. In the Virtual Media Session window, select the check box in the Mapped column for the ISO file that you added, and then wait for mapping to complete. Observe the progress in the Details area.

Now the ISO image is mapped to the remote device.

Step 6

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

Step 7

On the Boot Menu screen, select the device where you prepared the ISO in Step 2:

- If you are upgrading locally, select the physical CD/DVD device and then press Enter (for example, SATA5:TSSTcorp CDDVDW TS-L633C).

- If you are upgrading remotely, select Cisco Virtual CD/DVD and then press Enter.

The server is rebooted from the device you choose.

Step 8

A screen appears with the server BIOS and CIMC firmware versions. Answer the prompt, Have you read the Cisco EULA (end user license agreement)?

- Press y to accept the EULA and continue the update.

- Press n to read the EULA. The EULA is displayed and you are prompted to press y to continue the update, or n to cancel. If you press n, the server will reboot without updating.

- Press q to exit without updating. This selection reboots the server.

The Host Upgrade Menu screen displays.

Step 9

Select the option to Update UCS P81E VIC. This will update the card firmware and uboot image to the required level.

Step 10

Select the option to Update CIMC Firmware. This will update the CIMC firmware.

Step 11

Verify the firmware levels on the next screen.

Step 12

Select the option to Reboot the machine.

Step 13

When you see the F8 prompt during rebooting, press F8 to open the CIMC Configuration Utility.

Step 14

In the CIMC Configuration Utility, select the option CIMC Factory Default, then press F10 to save your changes.

Step 15

Return the cables from the FEXes to the 1-Gb LOM ports on the server.

Step 16

Recommission the server in UCS Manager.

Migrating the Configuration to Release 2.2 or Later

When a Cisco UCS C-Series server is integrated with Cisco UCS Manager, discovered and associated with a service profile, you can migrate the configuration to a later version of Cisco UCS Manager.

Note

- This migration process causes server downtime.

- This procedure describes the scenario where management path from the server connects to the FEX and the data path connects directly to the FI.

Procedure

Step 1

Shut down the server OS.

Step 2

In Cisco UCS Manager, decommission all C-series servers from the Cisco UCS domain.

Step 3

Unconfigure all FI server ports that are connected to the Nexus 2248 FEX.

Issue an NX-OS show fex command to verify that the FEX is unconfigured. Wait until the command return does not list the FEX.

Step 4

Disconnect the cable that connects the FEX and the FI.

Step 5

In Cisco UCS Manager CLI, issue a remove fex fex_ID command to remove the FEX from the database.

Step 6

In Cisco UCS Manager GUI, Unconfigure all FI server ports that are connected to the server’s adapter card.

Step 7

Disconnect the cable that connects the FI and the server’s adapter card.

Step 8

Disconnect the cable that connects the FEX and the server’s LOM connector.

Step 9

Upgrade your Cisco UCS Manager software to or later and the FI firmware to the corresponding level.

Step 10

Repeat steps 3 through 9 on the second fabric interconnect in your configuration.

Step 11

Connect the C-Series server directly to your network and upgrade the firmware by using the standalone CIMC utility.

1. Connect an Ethernet line from your LAN to one of the 1-Gb LOM ports on the server. Do not use the dedicated management port, this is disabled in the Cisco UCS Manager integrated mode.

2. Follow the instructions in Upgrading the Firmware and Rebooting in UCSM Mode, then return to the next step in this procedure.

Step 12

Physically replace the Nexus 2248 FEX with a Nexus 2232PP FEX in your rack.

Step 13

Connect the cables as shown in the image. See Physical Connectivity Illustrations.
In this new configuration, the data and management paths both connect from the server to the FEX. The paths between the FEX and the FI carry both data and management traffic.

Important:
Issuing an NX-OS show fex command to verify the FEX. Wait until the command return lists the new Nexus 2232PP FEX. The FEX will automatically upgrade to the corresponding FI firmware version.

Step 14

After both fabric interconnects are cabled, from Cisco UCS Manager, re-commission the decommissioned C-series servers.
When the server is discovered in Cisco UCS Manager, the previously assigned service profile is automatically re-associated with the server.

Chapter 6. Troubleshooting

This chapter includes the following section:

- Replacing a Hardware Component on a Cisco UCS Manager Integrated C-Series Server

Replacing a Hardware Component on a Cisco UCS Manager Integrated C-Series Server

After you replace hardware with managed firmware component on a Cisco UCS Manager integrated C-Series server, the server may fail discovery. This could be due to a corrupt firmware on the hardware or incompatibility of the hardware component's firmware. Complete the following steps to ensure server does not fail discovery due to server firmware corruption or incompatibility after hardware replacement:

Procedure

Step 1

Right-click Server -> Server Maintenance > Decommission Server to decommission the server.

Step 2

Disconnect the cables connecting the VICs to the FI (or FEX, if applicable).

Step 3

Remove the server from Cisco UCS Manager:

1. Choose Equipment -> Decommissioned .

2. Right-click on the server and click Remove.

Step 4

Reboot the server and perform a CIMC Reset to Factory Defaults.

Step 5

Connect a 1G cable to the MGMT port on the server and configure it for standalone access.

Step 6

Re-image all the server firmware to match the Cisco UCS Manager firmware bundle CIMC version with the server:

1. Download the Host Upgrade Utility (HUU) from Cisco's software download site for the CIMC version that corresponds to the host firmware package applied to this server in the Cisco UCS Manager.

2. Boot the server with the standalone KVM and run the HUU package.

For information about steps to upgrade the firmware, refer to the Host Utility Upgrade User Guide that corresponds to the HUU CIMC version that was downloaded in the previous step.

Step 7

Reboot the server and perform a CIMC Reset to Factory Defaults.

Step 8

Unplug the power cables for 30 seconds.

Step 9

Reconnect the uplink cables.

Step 10

Connect the power cables and power on.

Step 11

Verify if the server displays on the Cisco UCS Manager, this may take a few minutes.

Step 12

After the server appears, re-acknowledge the server, if the rack server discovery policy is set to user acknowledge.

Preface

- Audience

- Conventions

- Related Cisco UCS Documentation

- Documentation Feedback

Audience

This guide is intended primarily for data center administrators with responsibilities and expertise in one or more of the following:

- Server administration

- Storage administration

- Network administration

- Network security

Conventions

Text Type

Indication

GUI elements

GUI elements such as tab titles, area names, and field labels appear in this font.

Main titles such as window, dialog box, and wizard titles appear in this font.

Document titles

Document titles appear in this font.

TUI elements

In a Text-based User Interface, text the system displays appears in this font.

System output

Terminal sessions and information that the system displays appear in this font.

CLI commands

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

[ ]

Elements in square brackets are optional.

{x | y | z}

Required alternative keywords are grouped in braces and separated by vertical bars.

[x | y | z]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

< >

Nonprinting characters such as passwords are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Tip

Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Caution

Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS

Related Cisco UCS Documentation

Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: Click Here .

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Click Here .

For information on supported firmware versions and supported UCS Manager versions for the rack servers that are integrated with the UCS Manager for management, refer to Release Bundle Contents for Cisco UCS Software.

Other Documentation Resources

Follow Cisco UCS Docs on Twitter to receive document update notifications.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-docfeedback@cisco.com. We appreciate your feedback.

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)