The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
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) |
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 http://www.cisco.com/en/US/products/ps10493/products_user_guide_list.html
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.
Step 1 | Download the
HUU ISO file:
| ||
Step 2 | If you want to prepare the ISO for a local upgrade, complete this step; Otherwise, go to Step 3. | ||
Step 3 | Prepare the
ISO for a remote upgrade using the
KVM Console.
| ||
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:
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:
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.
| ||
Step 8 | If you want update specific components from the list, choose the components that you want to update. | ||
Step 9 | Click
Update.
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.
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. | ||
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.
| ||
Step 14 | Click
Exit to exit from the HUU.
|
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.
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.
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 |
|
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.
|
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. 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. |