Maintaining the Node

Status LEDs and Buttons

This section contains information for interpreting LED states.

Front-Panel LEDs

Table 1. Front Panel LEDs, Definition of States
	LED Name	States
1 SAS	SAS/SATA drive fault	Off—The hard drive is operating properly. Amber—Drive fault detected. Amber, blinking—The device is rebuilding. Amber, blinking with one-second interval—Drive locate function activated in the software.
2 SAS	SAS/SATA drive activity LED	Off—There is no hard drive in the hard drive tray (no access, no fault). Green—The hard drive is ready. Green, blinking—The hard drive is reading or writing data.
3	Power button/LED	Off—There is no AC power to the server. Amber—The server is in standby power mode. Power is supplied only to the Cisco IMC and some motherboard functions. Green—The server is in main power mode. Power is supplied to all server components.
4	Unit identification	Off—The unit identification function is not in use. Blue, blinking—The unit identification function is activated.
5	System health	Green—The server is running in normal operating condition. Green, blinking—The server is performing system initialization and memory check. Amber, steady—The server is in a degraded operational state (minor fault). For example: Power supply redundancy is lost. CPUs are mismatched. At least one CPU is faulty. At least one DIMM is faulty. At least one drive in a RAID configuration failed. Amber, 2 blinks—There is a major fault with the system board. Amber, 3 blinks—There is a major fault with the memory DIMMs. Amber, 4 blinks—There is a major fault with the CPUs.
6	Power supply status	Green—All power supplies are operating normally. Amber, steady—One or more power supplies are in a degraded operational state. Amber, blinking—One or more power supplies are in a critical fault state.
7	Fan status	Green—All fan modules are operating properly. Amber, blinking—One or more fan modules breached the non-recoverable threshold.
8	Network link activity	Off—The Ethernet LOM port link is idle. Green—One or more Ethernet LOM ports are link-active, but there is no activity. Green, blinking—One or more Ethernet LOM ports are link-active, with activity.
9	Temperature status	Green—The server is operating at normal temperature. Amber, steady—One or more temperature sensors breached the critical threshold. Amber, blinking—One or more temperature sensors breached the non-recoverable threshold.

Rear-Panel LEDs

The rear panel LEDs are identical for SFF and LFF versions of the node. The rear drive bay numbering follows sequentially from the number of front drive bays.

Table 2. Rear Panel LEDs, Definition of States

LED Name

States

1-Gb/10-Gb Ethernet link speed (on both LAN1 and LAN2)

Off—Link speed is 100 Mbps.
Amber—Link speed is 1 Gbps.
Green—Link speed is 10 Gbps.

1-Gb/10-Gb Ethernet link status (on both LAN1 and LAN2)

Off—No link is present.
Green—Link is active.
Green, blinking—Traffic is present on the active link.

1-Gb Ethernet dedicated management link speed

Off—Link speed is 10 Mbps.
Amber—Link speed is 100 Mbps.
Green—Link speed is 1 Gbps.

1-Gb Ethernet dedicated management link status

Off—No link is present.
Green—Link is active.
Green, blinking—Traffic is present on the active link.

Rear unit identification

Off—The unit identification function is not in use.
Blue, blinking—The unit identification function is activated.

Power supply status (one LED each power supply unit)

AC power supplies:

Off—No AC input (12 V main power off, 12 V standby power off).
Green, blinking—12 V main power off; 12 V standby power on.
Green, solid—12 V main power on; 12 V standby power on.
Amber, blinking—Warning threshold detected but 12 V main power on.
Amber, solid—Critical error detected; 12 V main power off (for example, over-current, over-voltage, or over-temperature failure).

DC power supplies:

Off—No DC input (12 V main power off, 12 V standby power off).
Green, blinking—12 V main power off; 12 V standby power on.
Green, solid—12 V main power on; 12 V standby power on.
Amber, blinking—Warning threshold detected but 12 V main power on.
Amber, solid—Critical error detected; 12 V main power off (for example, over-current, over-voltage, or over-temperature failure).

SAS

SAS/SATA drive fault

Note

NVMe solid state drive (SSD) drive tray LEDs have different behavior than SAS/SATA drive trays.

Off—The hard drive is operating properly.
Amber—Drive fault detected.
Amber, blinking—The device is rebuilding.
Amber, blinking with one-second interval—Drive locate function activated in the software.

SAS

SAS/SATA drive activity LED

Off—There is no hard drive in the hard drive tray (no access, no fault).
Green—The hard drive is ready.
Green, blinking—The hard drive is reading or writing data.

NVMe

NVMe SSD drive fault

Note

NVMe solid state drive (SSD) drive tray LEDs have different behavior than SAS/SATA drive trays.

Off—The drive is not in use and can be safely removed.
Green—The drive is in use and functioning properly.
Green, blinking—the driver is initializing following insertion or the driver is unloading following an eject command.
Amber—The drive has failed.
Amber, blinking—A drive Locate command has been issued in the software.

NVMe

NVMe SSD activity

Off—No drive activity.
Green, blinking—There is drive activity.

Internal Diagnostic LEDs

The node has internal fault LEDs for CPUs, DIMMs, and fan modules.

The internal LEDs are identical for the SFF and LFF versions of the node.

Figure 4. Internal Diagnostic LED Locations


1	Fan module fault LEDs (one on the top of each fan module) Amber—Fan has a fault or is not fully seated. Green—Fan is OK.	3	DIMM fault LEDs (one behind each DIMM socket on the motherboard) These LEDs operate only when the server is in standby power mode. Amber—DIMM has a fault. Off—DIMM is OK.
2	CPU fault LEDs (one behind each CPU socket on the motherboard). These LEDs operate only when the server is in standby power mode. Amber—CPU has a fault. Off—CPU is OK.	-

Decommissioning the Node Using Cisco UCS Manager

Before replacing an internal component of a node, you must decommission the node to remove it from the Cisco UCS configuration. When you use this procedure to shut down an HX node, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.

Procedure

Step 1	In the Navigation pane, click Equipment.
Step 2	Expand Equipment > Rack Mounts > Servers.
Step 3	Choose the node that you want to decommission.
Step 4	In the Work pane, click the General tab.
Step 5	In the Actions area, click Server Maintenance.
Step 6	In the Maintenance dialog box, click Decommission, then click OK. The node is removed from the Cisco UCS configuration.

Shutting Down and Removing Power From the Node

The node can run in either of two power modes:

Main power mode—Power is supplied to all node components and any operating system on your drives can run.
Standby power mode—Power is supplied only to the service processor and certain components. It is safe for the operating system and data to remove power cords from the node in this mode.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node, as directed in the service procedures.

You can shut down the node by using the front-panel power button or the software management interfaces.

Shutting Down Using The Cisco UCS Manager Equipment Tab

When you use this procedure to shut down an HX node, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.

Note

If the Shutdown Server link is dimmed in the Actions area, the node is not running.

Procedure

Step 1	In the Navigation pane, click Equipment.
Step 2	Expand Equipment > Rack Mounts > Servers.
Step 3	Choose the node that you want to shut down.
Step 4	In the Work pane, click the General tab.
Step 5	In the Actions area, click Shutdown Server.
Step 6	If a confirmation dialog displays, click Yes. After the node has been successfully shut down, the Overall Status field on the General tab displays a power-off status.
Step 7	If a service procedure instructs you to completely remove power from the node, disconnect all power cords from the power supplies in the node.

Shutting Down Using The Cisco UCS Manager Service Profile

When you use this procedure to shut down an HX node, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.

Note

If the Shutdown Server link is dimmed in the Actions area, the node is not running.

Procedure

Step 1	In the Navigation pane, click Servers.
Step 2	Expand Servers > Service Profiles.
Step 3	Expand the node for the organization that contains the service profile of the node that you are shutting down.
Step 4	Choose the service profile of the node that you are shutting down.
Step 5	In the Work pane, click the General tab.
Step 6	In the Actions area, click Shutdown Server.
Step 7	If a confirmation dialog displays, click Yes. After the node has been successfully shut down, the Overall Status field on the General tab displays a power-off status.
Step 8	If a service procedure instructs you to completely remove power from the node, disconnect all power cords from the power supplies in the node.

Shutting Down Using vSphere With HX Maintenance Mode

Some procedures directly place the node into Cisco HX Maintenance mode. This procedure migrates all VMs to other nodes before the node is shut down and decommissioned from Cisco UCS Manager.

Procedure

Step 1

Put the node in Cisco HX Maintenance mode by using the vSphere interface:

Using the vSphere web client:
1. Log in to the vSphere web client.
2. Go to Home > Hosts and Clusters.
3. Expand the Datacenter that contains the HX Cluster.
4. Expand the HX Cluster and select the node.
5. Right-click the node and select Cisco HX Maintenance Mode > Enter HX Maintenance Mode.
Using the command-line interface:
1. Log in to the storage controller cluster command line as a user with root privileges.
2. Identify the node ID and IP address:
```
# stcli node list --summary 
```
3. Enter the node into HX Maintenance Mode:
```
# stcli node maintenanceMode (--id   ID  | --ip   IP Address  ) --mode enter 
```
  (See also stcli node maintenanceMode --help).
4. Log into the ESXi command line of this node as a user with root privileges.
5. Verify that the node has entered HX Maintenance Mode:
```
# esxcli system maintenanceMode get 
```

Step 2

Shut down the node using UCS Manager as described in Shutting Down and Removing Power From the Node.

Shutting Down Using the Power Button

Note

This method is not recommended for a HyperFlex node, but the operation of the physical power button is explained here in case an emergency shutdown is required.

Procedure

Step 1

Check the color of the Power Status LED:

Green—The node is in main power mode and must be shut down before you can safely remove power.
Amber—The node is already in standby mode and you can safely remove power.

Step 2

Invoke either a graceful shutdown or a hard shutdown:

Caution

To avoid data loss or damage to your operating system, you should always invoke a graceful shutdown of the operating system.

Graceful shutdown—Press and release the Power button. The operating system performs a graceful shutdown and the node goes to standby mode, which is indicated by an amber Power button/LED.
Emergency shutdown—Press and hold the Power button for 4 seconds to force the main power off and immediately enter standby mode.

Step 3

If a service procedure instructs you to completely remove power from the node, disconnect all power cords from the power supplies in the node.

Post-Maintenance Procedures

This section contains procedures that are referenced at the end of some maintenance procedures.

Recommissioning the Node Using Cisco UCS Manager

After replacing an internal component of a node, you must recommission the node to add it back into the Cisco UCS configuration.

Procedure

Step 1	In the Navigation pane, click Equipment.
Step 2	Expand Equipment > Rack Mounts.
Step 3	In the Work pane, click the Decommissioned tab.
Step 4	On the row for each node that you want to recommission, do the following: In the Recommission column, check the check box. Click Save Changes.
Step 5	If a confirmation dialog box displays, click Yes.
Step 6	(Optional) Monitor the progress of the server recommission and discovery on the FSM tab for the node.

Associating a Service Profile With an HX Node

Use this procedure to associate an HX node to its service profile after recommissioning.

Procedure

Step 1	In the Navigation pane, click Servers.
Step 2	Expand Servers > Service Profiles.
Step 3	Expand the node for the organization that contains the service profile that you want to associate with the HX node.
Step 4	Right-click the service profile that you want to associate with the HX node and then select Associate Service Profile.
Step 5	In the Associate Service Profile dialog box, select the Server option.
Step 6	Navigate through the navigation tree and select the HX node to which you are assigning the service profile.
Step 7	Click OK.

Exiting HX Maintenance Mode

Use this procedure to exit HX Maintenance Mode after performing a service procedure

Procedure

Exit the node from Cisco HX Maintenance mode by using the vSphere interface:

Using the vSphere web client:
1. Log in to the vSphere web client.
2. Go to Home > Hosts and Clusters.
3. Expand the Datacenter that contains the HX Cluster.
4. Expand the HX Cluster and select the node.
5. Right-click the node and select Cisco HX Maintenance Mode > Exit HX Maintenance Mode.
Using the command-line interface:
1. Log in to the storage controller cluster command line as a user with root privileges.
2. Identify the node ID and IP address:
```
# stcli node list --summary 
```
3. Exit the node out of HX Maintenance Mode:
```
# stcli node maintenanceMode (--id   ID  | --ip   IP Address  ) --mode exit 
```
  (See also stcli node maintenanceMode --help).
4. Log into the ESXi command line of this node as a user with root privileges.
5. Verify that the node has exited HX Maintenance Mode:
```
# esxcli system maintenanceMode get 
```

Removing the Node Top Cover

Procedure

Step 1

Remove the top cover:

If the cover latch is locked, use a screwdriver to turn the lock 90-degrees counterclockwise to unlock it.
Lift on the end of the latch that has the green finger grip. The cover is pushed back to the open position as you lift the latch.
Lift the top cover straight up from the node and set it aside.

Step 2

Replace the top cover:

With the latch in the fully open position, place the cover on top of the node about one-half inch (1.27 cm) behind the lip of the front cover panel. The opening in the latch should fit over the peg that sticks up from the fan tray.
Press the cover latch down to the closed position. The cover is pushed forward to the closed position as you push down the latch.
If desired, lock the latch by using a screwdriver to turn the lock 90-degrees clockwise.


1	Cover latch	3	Serial number label location
2	Cover lock

Removing and Replacing Components

Warning

Blank faceplates and cover panels serve three important functions: they prevent exposure to hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the system unless all cards, faceplates, front covers, and rear covers are in place.

Statement 1029

Caution

When handling node components, handle them only by carrier edges and use an electrostatic discharge (ESD) wrist-strap or other grounding device to avoid damage.

Tip

You can press the unit identification button on the front panel or rear panel to turn on a flashing, blue unit identification LED on both the front and rear panels of the node. This button allows you to locate the specific node that you are servicing when you go to the opposite side of the rack. You can also activate these LEDs remotely.

This section describes how to remove and replace node components.

HX240c SFF Drives Serviceable Component Locations

This topic shows the locations of the field-replaceable components and service-related items.

Note

The internal component locations are the same for the SFF and LFF versions of the node unless otherwise noted. The functions of the drives differ in SFF and LFF versions, as described in this document.

Figure 6. SFF Serviceable Component Locations


1	2.5-inch drive bays 2 – 24: Hybrid HX240C-M5SX: 6 to 23 persistent data HDDs All-Flash HXAF240C-M5SX: 6 to 23 persistent data SSDs	10	Rear drive bay 25: Caching SSD
2	Drive bay 1: Housekeeping SSD for logs	11	PCIe riser 2B (PCIe slots 4, 5, 6)
3	Cooling fan modules (six, hot-swappable)	12	Micro-SD card socket on PCIe riser 1
4	DIMM sockets on motherboard (up to 12 per CPU) Not visible under air baffle in this view.	13	PCIe riser 1 (PCIe slot 1, 2, 3)
5	CPUs and heatsinks (two) Not visible under air baffle in this view.	14	Modular LOM (mLOM) card bay on chassis floor (x16 PCIe lane), not visible in this view
6	Internal, vertical USB 3.0 port on motherboard	15	Cisco modular storage controller HBA slot (dedicated PCIe slot)
7	Mini-storage module for SATA M.2 SSD boot drive	16	RTC battery, vertical socket on motherboard
8	PCIe cable connector on PCIe riser 2B for rear-loading NVMe SSD	17	Securing clips for GPU cards on air baffle
9	Power supplies (hot-swappable when redundant as 1+1)	-

HX240c LFF Drives Serviceable Component Locations

This topic shows the locations of the field-replaceable components and service-related items for Hybrid HX240C-M5L.

Note

Figure 7. LFF Serviceable Component Locations


1	3.5-inch drive bays 1 – 12: Hybrid HX240C-M5L: 6 to 12 persistent data HDDs	10	Rear drive bay 13: Caching SSD
2	Cooling fan modules (six, hot-swappable)	11	PCIe riser 2B (PCIe slots 4, 5, 6)
3	DIMM sockets on motherboard (up to 12 per CPU) Not visible under air baffle in this view.	12	Micro-SD card socket on PCIe riser 1
4	CPUs and heatsinks (two) Not visible under air baffle in this view.	13	PCIe riser 1 (PCIe slot 1, 2, 3)
5	Internal, vertical USB 3.0 port on motherboard	14	Modular LOM (mLOM) card bay on chassis floor (x16 PCIe lane), not visible in this view
6	Mini-storage module for SATA M.2 SSD boot drive	15	Cisco modular storage controller HBA slot (dedicated PCIe slot)
7	PCIe cable connector on PCIe riser 2B for rear-loading NVMe SSD	16	RTC battery, vertical socket on motherboard
8	Power supplies (hot-swappable when redundant as 1+1)	17	Securing clips for GPU cards on air baffle
9	Rear drive bay 14: Housekeeping SSD for logs	-

Considerations For Upgrading Hardware in Multiple Nodes of a Cluster

This chapter contains removal and replacement procedures for components that are supported as field-replaceable. This topic describes additional considerations when multiple nodes in an existing cluster are upgraded with the addition or replacement of components.

The following procedure describes the general steps and considerations for upgrading hardware in the nodes of a cluster.

Note

Hot-swappable components can be replaced or added without shutting down the system as described below. Those include certain drives, the internal fan modules, and the power supplies. Check the procedure for the component in this chapter to verify whether the shutdown steps are required.

Procedure

Step 1

Verify that the existing cluster is healthy.

Step 2

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 3

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 4

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 5

Disconnect all power cables from all power supplies.

Step 6

Remove and replace the existing component or add a new component following the supported population rules. Use the specific procedure in this chapter for the component.

Step 7

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Ensure that ESXi boots. The node is auto-discovered by Cisco UCS Manager and the ESXi operating system recognizes the new components.

Step 8

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 9

Verify that ESXi is reconnected to HyperFlex vCenter.

Step 10

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Step 11

Verify within 30 minutes that the HX cluster is again in a healthy state.

Step 12

Move a test VM to the host. Ensure that it is working by performing tests.

Note

You must perform the hardware upgrade on the next node in the cluster within two hours after upgrading the prior node and verifying that the cluster is healthy. The HyperFlex Data Platform (HXDP) runs a data rebalance operation every two hours and this timer starts after the cluster is again in a healthy state.

Step 13

Repeat the steps above to upgrade the hardware component in each node until all node hardware is updated.

Replacing Drives

This section describes the supported drives by function and how to replace them.

Drive Population Rules

Drive bay numbering is shown in the following figure.

Figure 8. Front Drive Bay Numbering, SFF Versions

Figure 9. Front Drive Bay Numbering, LFF Versions

The numbering of the rear drive bays is sequential, following the number of front drive bays.

Figure 10. Rear Drive Bay Numbering, All Versions

Observe these drive population rules:

SFF Versions Drive Population Rules

Front bay 1: Housekeeping SSD for SDS logs only
Front bays 2 - 24:
- HX240c Hybrid: 6 to 23 persistent data HDDs
- HX240c All-Flash: 6 to 23 persistent data SSDs
Rear bay 25: Caching SSD only
When populating persistent data drives, add drives to the lowest-numbered bays first.
Keep an empty drive blanking tray in any unused bays to ensure proper airflow.
See HX240c M5 Drive Configuration Comparison for supported drive configurations.

LFF Versions Drive Population Rules

Front bays 1 - 12:
- Hybrid HX240C-M5L: 6 to 12 persistent data HDDs
Rear bay 13: Caching SSD only
Rear bay 14: Housekeeping SSD for SDS logs only
When populating persistent data drives, add drives to the lowest-numbered bays first.
Keep an empty drive blanking tray in any unused bays to ensure proper airflow.
See HX240c M5 Drive Configuration Comparison for supported drive configurations.

Note

Regarding drive capacity stated on drive labels vs reported capacity in software:

The capacity stated on the drive physical label and the capacity reported by the HyperFlex software differ because of the following reasons:

Drive label capacities are stated in decimal (base 10) notation, while the software-reported capacities are stated in binary (base 2) notation. For example, 1 TB in decimal notation would be reported as 909 GB in binary notation—these are actually the same capacity, similar to distance reported in miles vs kilometers being the same distance, but in different units. These examples show capacities stated as decimal notation vs binary notation:
- 500 GB (decimal) = 465.5 GB (binary)
- 1 TB (decimal) = 909 GB (binary)
- 2 TB (decimal) = 1.82 TB (binary)
- 3 TB (decimal) = 2.72 TB (binary)
Preinstalled software and partitions also reduce storage capacity.

HX240c M5 Drive Configuration Comparison

The following tables compare the drives supported by each function in the node. Also note the considerations listed after the tables.

Table 3. SFF Versions Drive Configuration Comparison
Component	HX240c M5 Hybrid SFF	HX240c M5 All-Flash SFF	HX240c M5 SED Hybrid SFF	HX240c M5 SED All-Flash SFF
Housekeeping SSD Slot 1	SSD: HX- SD240G61X-EV	SSD: HX- SD240G61X-EV	SSD: HX- SD240G61X-EV	SSD: HX- SD240G61X-EV
Persistent data drives Slots 2 - 24	HDD: HX- HD12TB10K12N	SSD: HX- SD960G61X-EV HX- SD38T61X-EV	SED HDD: HX- HD12T10NK9	SED SSD: HX- SD800GBENK9 HX- SD960GBE1NK9 HX- SD38TBE1NK9
Caching SSD Rear slot 25	SSD: HX- SD16T63X-EP HX- SD16T123X-EP	SSD: HX- NVMEHW-H1600 HX- SD400G12TX-EP HX-NVMEXP-I375	SED SSD: HX- SD16TBENK9	SED SSD: HX- SD800GBENK9

Table 4. LFF Versions Drive Configuration Comparison
Component	HX240c M5 Hybrid LFF
Persistent data drives Slots 1 - 12	HDD (3.5-inch): HX- HD6T7KL4KN HX- HD8T7KL4KN
Caching SSD Rear slot 13	SSD: HX- SD32T123X-EP
Housekeeping SSD Rear bay 14	SSD: HX- SD240G61X-EV

Note the following considerations and restrictions for All-Flash HyperFlex nodes:

The minimum Cisco HyperFlex software required for using Intel Optane NVMe SSD HX-NVMEXP-I375 is Release 3.0(1a) or later. If you use HX-NVMEXP-I375 as your caching drive in HX240c All-Flash nodes, all nodes in the cluster must use this same drive as the caching drive.
HX240c All-Flash HyperFlex nodes are ordered as specific All-Flash PIDs; All-Flash configurations are supported only on those PIDs.
Conversion from Hybrid HX240c configuration to All-Flash HX240c configuration is not supported.
Mixing Hybrid nodes with All-Flash nodes within the same HyperFlex cluster is not supported.

Note the following considerations and restrictions for SED HyperFlex nodes:

The minimum Cisco HyperFlex software required for SED configurations is Release 3.5(1a) or later.
Mixing HX240c Hybrid SED HyperFlex nodes with HX240c All-Flash SED HyperFlex nodes within the same HyperFlex cluster is not supported.

Drive Replacement Overview

The three types of drives in the node require different replacement procedures.

Housekeeping SSD

SFF: Front bay 1

LFF: Rear bay 14

The node must be put into Cisco HX Maintenance Mode before replacing the housekeeping SSD.

Note

After you replace the Housekeeping SSD, see Replacing Housekeeping SSDs in the Cisco HyperFlex Data Platform Administration Guide for additional software update steps.

Persistent data drives

SFF: Front bays 2 - 24

LFF: Front bays 1 - 12

Hot-swap replacement is supported. See Replacing Persistent Data Drives.

Note

Hot-swap replacement includes hot-removal, so you can remove the drive while it is still operating.

Caching SSD

SFF: Rear bay 25

LFF: Rear bay 13

Hot-swap replacement is supported.

Note

Hot-swap replacement for SAS/SATA drives includes hot-removal, so you can remove the drive while it is still operating.

Note

If an NVMe SSD is used as the Caching SSD, additional steps are required as described in the procedure.

Replacing the Housekeeping SSD

SFF versions: The Housekeeping SSD must be installed in front bay 1.
LFF versions: The Housekeeping SSD must be installed in rear bay 14.

Note

After you replace the Housekeeping SSD, see Replacing Housekeeping SSDs in the Cisco HyperFlex Data Platform Administration Guide for additional software update steps.

Note

Always replace the drive with the same type and size as the original drive.

Caution

Put the node in Cisco HX Maintenance mode before replacing the Housekeeping SSD, as described in the procedure. Hot-swapping the Housekeeping SSD while the node is running causes the node to fail.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Remove the Housekeeping SSD:

SFF versions: The Housekeeping SSD must be installed in front bay 1.
LFF versions: The Housekeeping SSD must be installed in rear bay 14.

Press the release button on the face of the drive tray.
Grasp and open the ejector lever and then pull the drive tray out of the slot.
Remove the four drive-tray screws that secure the drive to the tray and then lift the drive out of the tray.

Step 6

Install a new drive:

Place a new drive in the empty drive tray and install the four drive-tray screws.
With the ejector lever on the drive tray open, insert the drive tray into the empty drive bay.
Push the tray into the slot until it touches the backplane, and then close the ejector lever to lock the drive in place.

Figure 11. Replacing a Drive in a Drive Tray


1	Ejector lever	3	Drive tray screws (two on each side)
2	Release button	4	Drive removed from drive tray

Step 7

Replace power cables and then power on the node by pressing the Power button.

Step 8

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 9

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 10

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Note

After you replace the Housekeeping SSD, see Replacing Housekeeping SSDs in the Cisco HyperFlex Data Platform Administration Guide for additional software update steps.

Replacing Persistent Data Drives

SFF versions: The persistent data drives must be installed in front bays 2 - 24.
LFF versions: The persistent data drives must be installed in front bays 1 - 12.

Note

Always replace the drive with the same type and size as the original drive.

Note

Hot-swap replacement includes hot-removal, so you can remove the drive while it is still operating.

Procedure

Step 1

Remove the drive that you are replacing or remove a blank drive tray from the bay:

SFF versions: The persistent data drives must be installed in front bays 2 - 24.
LFF versions: The persistent data drives must be installed in front bays 1 - 12.

Press the release button on the face of the drive tray.
Grasp and open the ejector lever and then pull the drive tray out of the slot.
If you are replacing an existing drive, remove the four drive-tray screws that secure the drive to the tray and then lift the drive out of the tray.

Step 2

Install a new drive:

Place a new drive in the empty drive tray and install the four drive-tray screws.
With the ejector lever on the drive tray open, insert the drive tray into the empty drive bay.
Push the tray into the slot until it touches the backplane, and then close the ejector lever to lock the drive in place.

Figure 12. Replacing a Drive in a Drive Tray


1	Ejector lever	3	Drive tray screws (two on each side)
2	Release button	4	Drive removed from drive tray

Replacing the Caching SSD

SFF versions: The Caching SSD must be installed in rear bay 25.
LFF versions: The Caching SSD must be installed in rear bay 13.

Note the following considerations for NVMe SSDs, when used as the Caching SSD:

NVMe SSDs are supported only in All-Flash nodes. NVMe SSDs are not supported in Hybrid nodes.
NVMe SSDs are supported only in the Caching SSD position, in drive bay 13 for LFF versions or bay 25 for SFF versions. NVMe SSDs are not supported for persistent storage or as the Housekeeping drive.
The locator (beacon) LED cannot be turned on or off on NVMe SSDs.

Note

Always replace the drive with the same type and size as the original drive.

Note

Upgrading or downgrading the Caching drive in an existing HyperFlex cluster is not supported. If the Caching drive must be upgraded or downgraded, then a full redeployment of the HyperFlex cluster is required.

Note

When using a SAS/SATA drive, hot-swap replacement includes hot-removal, so you can remove the drive while it is still operating. NVMe drives cannot be hot-swapped.

Procedure

Step 1

Only if the caching drive is an NVMe SSD, enter the ESXI host into HX Maintenance Mode (see Shutting Down Using vSphere With HX Maintenance Mode). Otherwise, skip to step 2.

Step 2

Remove the Caching SSD:

SFF versions: The Caching SSD must be installed in rear bay 25.
LFF versions: The Caching SSD must be installed in rear bay 13.

Press the release button on the face of the drive tray.
Grasp and open the ejector lever and then pull the drive tray out of the slot.
Remove the four drive-tray screws that secure the drive to the tray and then lift the drive out of the tray.

Step 3

Install a new drive:

Place a new drive in the empty drive tray and install the four drive-tray screws.
With the ejector lever on the drive tray open, insert the drive tray into the empty drive bay.
Push the tray into the slot until it touches the backplane, and then close the ejector lever to lock the drive in place.

Step 4

Only if the Caching SSD is an NVMe SSD:

Reboot the ESXi host. This enables ESXi to discover the NVMe SSD.
Exit the ESXi host from HX Maintenance Mode (see Exiting HX Maintenance Mode).

Figure 13. Replacing a Drive in a Drive Tray


1	Ejector lever	3	Drive tray screws (two on each side)
2	Release button	4	Drive removed from drive tray

Replacing Fan Modules

Tip

There is a fault LED on the top of each fan module. This LED lights green when the fan is correctly seated and is operating OK. The LED lights amber when the fan has a fault or is not correctly seated.

Caution

You do not have to shut down or remove power from the server to replace fan modules because they are hot- swappable. However, to maintain proper cooling, do not operate the server for more than one minute with any fan module removed.

Procedure

Step 1

Remove an existing fan module:

Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the server from the rack.

Remove the top cover from the server as described in Removing the Node Top Cover.
Grasp and squeeze the fan module release latches on its top. Lift straight up to disengage its connector from the motherboard.

Step 2

Install a new fan module:

Set the new fan module in place. The arrow printed on the top of the fan module should point toward the rear of the server.
Press down gently on the fan module to fully engage it with the connector on the motherboard.
Replace the top cover to the server.
Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.


1	Fan module release latches	2	Fan module fault LED

Replacing Memory DIMMs

Caution

DIMMs and their sockets are fragile and must be handled with care to avoid damage during installation.

Caution

Cisco does not support third-party DIMMs. Using non-Cisco DIMMs in the server might result in system problems or damage to the motherboard.

Note

To ensure the best server performance, it is important that you are familiar with memory performance guidelines and population rules before you install or replace DIMMs.

DIMM Population Rules and Memory Performance Guidelines

This topic describes the rules and guidelines for maximum memory performance.

DIMM Slot Numbering

The following figure shows the numbering of the DIMM slots on the motherboard.

DIMM Population Rules

Observe the following guidelines when installing or replacing DIMMs for maximum performance:

Each CPU supports six memory channels.
- CPU 1 supports channels A, B, C, D, E, F.
- CPU 2 supports channels G, H, J, K, L, M.
Each channel has two DIMM sockets (for example, channel A = slots A1, A2).
In a single-CPU configuration, populate the channels for CPU1 only (A, B, C, D, E, F).

For optimal performance, populate DIMMs in the order shown in the following table, depending on the number of CPUs and the number of DIMMs per CPU. If your server has two CPUs, balance DIMMs evenly across the two CPUs as shown in the table.

Note

The table below lists recommended configurations. Using 5, 7, 9, 10, or 11 DIMMs per CPU is not recommended.

Table 5. DIMM Population Order
Number of DIMMs per CPU (Recommended Configurations)	Populate CPU 1 Slot		Populate CPU2 Slots
Number of DIMMs per CPU (Recommended Configurations)	Blue #1 Slots	Black #2 Slots	Blue #1 Slots	Black #2 Slots
1	(A1)	-	(G1)	-
2	(A1, B1)	-	(G1, H1)	-
3	(A1, B1, C1)	-	(G1, H1, J1)	-
4	(A1, B1); (D1, E1)	-	(G1, H1); (K1, L1)	-
6	(A1, B1); (C1, D1); (E1, F1)	-	(G1, H1); (J1, K1); (L1, M1)	-
8	(A1, B1); (D1, E1)	(A2, B2); (D2, E2)	(G1, H1); (K1, L1)	(G2, H2); (K2, L2)
12	(A1, B1); (C1, D1); (E1, F1)	(A2, B2); (C2, D2); (E2, F2)	(G1, H1); (J1, K1); (L1, M1)	(G2, H2); (J2, K2); (L2, M2)

The maximum combined memory allowed in the 12 DIMM slots controlled by any one CPU is 768 GB. To populate the 12 DIMM slots with more than 768 GB of combined memory, you must use a high-memory CPU that has a PID that ends with an "M", for example, UCS-CPU-6134M.
The NVIDIA Tesla P-Series GPU can support more than 1 TB of memory in the server. All other NVIDIA GPUs can support only 1 TB or less of memory in the server. Therefore, do not install DIMMs totalling more than 1 TB capacity when using an NVIDIA GPU card other than P-Series in this server.

Observe the DIMM mixing rules shown in the following table.

Table 6. DIMM Mixing Rules
DIMM Parameter	DIMMs in the Same Channel	DIMMs in the Same Bank
DIMM Capacity RDIMM = 16GB or 32GB LRDIMM = 64GB TSV-RDIMM = 128GB	You can mix different capacity DIMMs in the same channel (for example, A1, A2).	You cannot mix DIMM capacities in a bank (for example A1, B1). Pairs of DIMMs must be identical (same PID and revision).
DIMM speed For example, 2666 GHz	You can mix speeds, but DIMMs will run at the speed of the slowest DIMMs/CPUs installed in the channel.	You cannot mix DIMM speeds in a bank (for example A1, B1). Pairs of DIMMs must be identical (same PID and revision).
DIMM type RDIMMs or LRDIMMs	You cannot mix DIMM types in a channel.	You cannot mix DIMM types in a bank.

Replacing DIMMs

Identifying a Faulty DIMM

Each DIMM socket has a corresponding DIMM fault LED, directly in front of the DIMM socket. See Internal Diagnostic LEDs for the locations of these LEDs. When the server is in standby power mode, these LEDs light amber to indicate a faulty DIMM.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Remove an existing DIMM:

Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the server from the rack.

Remove the top cover from the server as described in Removing the Node Top Cover.
Remove the air baffle that covers the front ends of the DIMM slots to provide clearance.
Locate the DIMM that you are removing, and then open the ejector levers at each end of its DIMM slot.

Step 6

Install a new DIMM:

Note

Before installing DIMMs, see the memory population rules for this server: DIMM Population Rules and Memory Performance Guidelines.

Align the new DIMM with the empty slot on the motherboard. Use the alignment feature in the DIMM slot to correctly orient the DIMM.
Push down evenly on the top corners of the DIMM until it is fully seated and the ejector levers on both ends lock into place.
Replace the top cover to the server.
Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.

Step 7

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 8

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 9

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing CPUs and Heatsinks

This section contains CPU configuration rules and the procedure for replacing CPUs and heatsinks:

Special Information For Upgrades to Second Generation Intel Xeon Scalable Processors

Caution

You must upgrade your node firmware and software to the required minimum levels before you upgrade to the Second Generation Intel Xeon Scalable Processors that are supported in this node. Older firmware versions cannot recognize the new CPUs and this would result in a non-bootable node.

Note

You can use First Generation and Second Generation Intel Xeon Scalable processors in the same cluster. Do not mix First Generation and Second Generation processors within the same node.

The minimum software and firmware versions required for this node to support Second Generation Intel Xeon Scalable Processors are as follows:

Table 7. Minimum Requirements For Second Generation Intel Xeon Scalable Processors
Software or Firmware	Minimum Version
Node Cisco IMC/BIOS	4.0(4d)
Cisco UCS Manager	4.0(4d)
Cisco HyperFlex Data Platform	4.0(1b)

Do one of the following actions:

If your server's firmware and Cisco UCS Manager software are already at the required minimums shown above (or later), you can replace the CPU hardware by using the procedure in this section.
If your server's firmware and Cisco UCS Manager software are earlier than the required levels, upgrade your software. After you upgrade the software, return to this section as directed to replace the CPU hardware.

CPU Configuration Rules

This node has two CPU sockets on the motherboard. Each CPU supports six DIMM channels (12 DIMM slots).

The minimum configuration is that the node must have two identical CPUs installed.
The maximum combined memory allowed in the 12 DIMM slots controlled by any one CPU is 768 GB. To populate the 12 DIMM slots with more than 768 GB of combined memory, you must use a high-memory CPU that has a PID that ends with an "M", for example, UCS-CPU-6134M.

Tools Required For CPU Replacement

You need the following tools and equipment for this procedure:

T-30 Torx driver—Supplied with replacement CPU.
#1 flat-head screwdriver—Supplied with replacement CPU.
CPU assembly tool—Supplied with replacement CPU. Orderable separately as Cisco PID UCS-CPUAT=.
Heatsink cleaning kit—Supplied with replacement CPU. Orderable separately as Cisco PID UCSX-HSCK=.

One cleaning kit can clean up to four CPUs.
Thermal interface material (TIM)—Syringe supplied with replacement CPU. Use only if you are reusing your existing heatsink (new heatsinks have a pre-applied pad of TIM). Orderable separately as Cisco PID UCS-CPU-TIM=.

New heatsinks have a pre-applied pad of TIM.

Replacing a CPU and Heatsink

Caution

CPUs and their sockets are fragile and must be handled with extreme care to avoid damaging pins. The CPUs must be installed with heatsinks and thermal interface material to ensure cooling. Failure to install a CPU correctly might result in damage to the server.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Remove the existing CPU/heatsink assembly from the node:

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Remove the top cover from the node as described in Removing the Node Top Cover.

Use the T-30 Torx driver that is supplied with the replacement CPU to loosen the four captive nuts that secure the assembly to the motherboard standoffs.

Note

Alternate loosening the heatsink nuts evenly so that the heatsink remains level as it is raised. Loosen the heatsink nuts in the order shown on the heatsink label: 4, 3, 2, 1.

Lift straight up on the CPU/heatsink assembly and set it heatsink-down on an antistatic surface.

Figure 16. Removing the CPU/Heatsink Assembly


1	Heatsink	4	CPU socket on motherboard
2	Heatsink captive nuts (two on each side)	5	T-30 Torx driver
3	CPU carrier (below heatsink in this view)	-

Step 6

Separate the heatsink from the CPU assembly (the CPU assembly includes the CPU and the CPU carrier):

Place the heatsink with CPU assembly so that it is oriented upside-down as shown below.

Note the thermal-interface material (TIM) breaker location. TIM BREAKER is stamped on the CPU carrier next to a small slot.

Figure 17. Separating the CPU Assembly From the Heatsink


1	CPU carrier	4	CPU-carrier inner-latch nearest to the TIM breaker slot
2	CPU	5	#1 flat-head screwdriver inserted into TIM breaker slot
3	TIM BREAKER slot in CPU carrier	-

Pinch inward on the CPU-carrier inner-latch that is nearest the TIM breaker slot and then push up to disengage the clip from its slot in the heatsink corner.

Insert the blade of a #1 flat-head screwdriver into the slot marked TIM BREAKER.

Caution

In the following step, do not pry on the CPU surface. Use gentle rotation to lift on the plastic surface of the CPU carrier at the TIM breaker slot. Use caution to avoid damaging the heatsink surface.

Gently rotate the screwdriver to lift up on the CPU until the TIM on the heatsink separates from the CPU.

Note

Do not allow the screwdriver tip to touch or damage the green CPU substrate.

Pinch the CPU-carrier inner-latch at the corner opposite the TIM breaker and push up to disengage the clip from its slot in the heatsink corner.

On the remaining two corners of the CPU carrier, gently pry outward on the outer-latches and then lift the CPU-assembly from the heatsink.

Note

Handle the CPU-assembly by the plastic carrier only. Do not touch the CPU surface. Do not separate the CPU from the carrier.

Step 7

The new CPU assembly is shipped on a CPU assembly tool. Take the new CPU assembly and CPU assembly tool out of the carton.

If the CPU assembly and CPU assembly tool become separated, note the alignment features shown below for correct orientation. The pin 1 triangle on the CPU carrier must be aligned with the angled corner on the CPU assembly tool.

Caution

CPUs and their sockets are fragile and must be handled with extreme care to avoid damaging pins.

Figure 18. CPU Assembly Tool, CPU Assembly, and Heatsink Alignment Features


1	CPU assembly tool	4	Angled corner on heatsink (pin 1 alignment feature)
2	CPU assembly (CPU in plastic carrier)	5	Triangle cut into carrier (pin 1 alignment feature)
3	Heatsink	6	Angled corner on CPU assembly tool (pin 1 alignment feature)

Step 8

Apply new TIM to the heatsink:

Note

The heatsink must have new TIM on the heatsink-to-CPU surface to ensure proper cooling and performance.

If you are installing a new heatsink, it is shipped with a pre-applied pad of TIM. Go to step 5.
If you are reusing a heatsink, you must remove the old TIM from the heatsink and then apply new TIM to the CPU surface from the supplied syringe. Continue with step a below.

Apply the cleaning solution that is included with the heatsink cleaning kit (UCSX-HSCK=) to the old TIM on the heatsink and let it soak for a least 15 seconds.
Wipe all of the TIM off the heatsink using the soft cloth that is included with the heatsink cleaning kit. Be careful to avoid scratching the heatsink surface.

Using the syringe of TIM provided with the new CPU (UCS-CPU-TIM=), apply 1.5 cubic centimeters (1.5ml) of thermal interface material to the top of the CPU. Use the pattern shown below to ensure even coverage.

Figure 19. Thermal Interface Material Application Pattern

Caution

Use only the correct heatsink for your CPUs to ensure proper cooling. There are two different heatsinks: UCSC-HS-C240M5= for standard-performance CPUs 150 W and less; UCSC-HS2-C240M5= for high-performance CPUs above 150 W. Note the wattage described on the heatsink label.

Step 9

With the CPU assembly on the CPU assembly tool, set the heatsink onto the CPU assembly. Note the pin 1 alignment features for correct orientation. Push down gently until you hear the corner clips of the CPU carrier click onto the heatsink corners.

Caution

In the following step, use extreme care to avoid touching or damaging the CPU contacts or the CPU socket pins.

Step 10

Install the CPU/heatsink assembly to the server:

Lift the heatsink with attached CPU assembly from the CPU assembly tool.

Align the CPU with heatsink over the CPU socket on the motherboard, as shown below.

Note the alignment features. The pin 1 angled corner on the heatsink must align with the pin 1 angled corner on the CPU socket. The CPU-socket posts must align with the guide-holes in the assembly.

Figure 20. Installing the Heatsink/CPU Assembly to the CPU Socket


1	Guide hole in assembly (two)	4	Angled corner on heatsink (pin 1 alignment feature)
2	CPU socket alignment post (two)	5	Angled corner on socket (pin 1 alignment feature)
3	CPU socket leaf spring	-

Set the heatsink with CPU assembly down onto the CPU socket.

Use the T-30 Torx driver that is supplied with the replacement CPU to tighten the four captive nuts that secure the heatsink to the motherboard standoffs.

Caution

Alternate tightening the heatsink nuts evenly so that the heatsink remains level while it is lowered. Tighten the heatsink nuts in the order shown on the heatsink label: 1, 2, 3, 4. The captive nuts must be fully tightened so that the leaf springs on the CPU socket lie flat.

Replace the top cover to the node.
Replace the node in the rack, replace cables, and then fully power on the node by pressing the Power button.

Step 11

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 12

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 13

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Additional CPU-Related Parts to Order with RMA Replacement CPUs

When a return material authorization (RMA) of the CPU is done on a Cisco UCS C-Series server, additional parts might not be included with the CPU spare. The TAC engineer might need to add the additional parts to the RMA to help ensure a successful replacement.

Note

The following items apply to CPU replacement scenarios. If you are replacing a system chassis and moving existing CPUs to the new chassis, you do not have to separate the heatsink from the CPU. See Additional CPU-Related Parts to Order with RMA Replacement System Chassis.

Scenario 1—You are reusing the existing heatsinks:
- Heatsink cleaning kit (UCSX-HSCK=)
  
  One cleaning kit can clean up to four CPUs.
- Thermal interface material (TIM) kit for M5 servers (UCS-CPU-TIM=)
  
  One TIM kit covers one CPU.

Scenario 2—You are replacing the existing heatsinks:

Caution

Use only the correct heatsink for your CPUs to ensure proper cooling. There are two different heatsinks: UCSC-HS-C240M5= for CPUs 150 W and less; UCSC-HS2-C240M5= for CPUs above 150 W.

Heatsink: UCSC-HS-C240M5= for CPUs 150 W and less; UCSC-HS2-C240M5= for CPUs above 150 W

New heatsinks have a pre-applied pad of TIM.
Heatsink cleaning kit (UCSX-HSCK=)

One cleaning kit can clean up to four CPUs.

Scenario 3—You have a damaged CPU carrier (the plastic frame around the CPU):
- CPU carrier (UCS-M5-CPU-CAR=)
- #1 flat-head screwdriver (for separating the CPU from the heatsink)
- Heatsink cleaning kit (UCSX-HSCK=)
  
  One cleaning kit can clean up to four CPUs.
- Thermal interface material (TIM) kit for M5 servers (UCS-CPU-TIM=)
  
  One TIM kit covers one CPU.

A CPU heatsink cleaning kit is good for up to four CPU and heatsink cleanings. The cleaning kit contains two bottles of solution, one to clean the CPU and heatsink of old TIM and the other to prepare the surface of the heatsink.

New heatsink spares come with a pre-applied pad of TIM. It is important to clean any old TIM off of the CPU surface prior to installing the heatsinks. Therefore, even when you are ordering new heatsinks, you must order the heatsink cleaning kit.

Additional CPU-Related Parts to Order with RMA Replacement System Chassis

When a return material authorization (RMA) of the system chassis is done on a Cisco UCS C-Series server, you move existing CPUs to the new chassis.

Note

Unlike previous generation CPUs, the M5 server CPUs do not require you to separate the heatsink from the CPU when you move the CPU-heatsink assembly. Therefore, no additional heatsink cleaning kit or thermal-interface material items are required.

The only tool required for moving a CPU/heatsink assembly is a T-30 Torx driver.

Moving an M5 Generation CPU

Tool required for this procedure: T-30 Torx driver

Caution

When you receive a replacement server for an RMA, it includes dust covers on all CPU sockets. These covers protect the socket pins from damage during shipping. You must transfer these covers to the system that you are returning, as described in this procedure.

Procedure

Step 1

When moving an M5 CPU to a new server, you do not have to separate the heatsink from the CPU. Perform the following steps:

Use a T-30 Torx driver to loosen the four captive nuts that secure the assembly to the board standoffs.

Note

Alternate loosening the heatsink nuts evenly so that the heatsink remains level as it is raised. Loosen the heatsink nuts in the order shown on the heatsink label: 4, 3, 2, 1.

Lift straight up on the CPU/heatsink assembly to remove it from the board.

Set the CPUs with heatsinks aside on an anti-static surface.

Figure 21. Removing the CPU/Heatsink Assembly


1	Heatsink	4	CPU socket on motherboard
2	Heatsink captive nuts (two on each side)	5	T-30 Torx driver
3	CPU carrier (below heatsink in this view)	-

Step 2

Transfer the CPU socket covers from the new system to the system that you are returning:

Remove the socket covers from the replacement system. Grasp the two recessed finger-grip areas marked "REMOVE" and lift straight up.

Note

Keep a firm grasp on the finger-grip areas at both ends of the cover. Do not make contact with the CPU socket pins.

Figure 22. Removing a CPU Socket Dust Cover


1	Finger-grip areas marked "REMOVE"	-

With the wording on the dust cover facing up, set it in place over the CPU socket. Make sure that all alignment posts on the socket plate align with the cutouts on the cover.

Caution

In the next step, do not press down anywhere on the cover except the two points described. Pressing elsewhere might damage the socket pins.

Press down on the two circular markings next to the word "INSTALL" that are closest to the two threaded posts (see the following figure). Press until you feel and hear a click.

Note

You must press until you feel and hear a click to ensure that the dust covers do not come loose during shipping.

Figure 23. Installing a CPU Socket Dust Cover


-	Press down on the two circular marks next to the word INSTALL.	-

Step 3

Install the CPUs to the new system:

On the new board, align the assembly over the CPU socket, as shown below.

Note the alignment features. The pin 1 angled corner on the heatsink must align with the pin 1 angled corner on the CPU socket. The CPU-socket posts must align with the guide-holes in the assembly.

Figure 24. Installing the Heatsink/CPU Assembly to the CPU Socket


1	Guide hole in assembly (two)	4	Angled corner on heatsink (pin 1 alignment feature)
2	CPU socket alignment post (two)	5	Angled corner on socket (pin 1 alignment feature)
3	CPU socket leaf spring	-

On the new board, set the heatsink with CPU assembly down onto the CPU socket.

Use a T-30 Torx driver to tighten the four captive nuts that secure the heatsink to the board standoffs.

Note

Replacing a Mini-Storage Module or M.2 Boot Drive

The mini-storage module plugs into a motherboard socket to provide additional M.2 SSD internal storage. This node includes a SATA M.2 SSD that can be used as a boot drive.

Replacing a Mini-Storage Module Carrier

This topic describes how to remove and replace a mini-storage module carrier.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the server out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the server from the rack.

Step 6

Remove the top cover from the server as described in Removing the Node Top Cover.

Step 7

Remove a carrier from its socket:

Locate the mini-storage module carrier in its socket just in front of power supply 1.
At each end of the carrier, push outward on the clip that secures the carrier.
Lift both ends of the carrier to disengage it from the socket on the motherboard.
Set the carrier on an anti-static surface.

Step 8

Install a carrier to its socket:

Position the carrier over socket, with the carrier's connector facing down and at the same end as the motherboard socket. Two alignment pegs must match with two holes on the carrier.
Gently push down the socket end of the carrier so that the two pegs go through the two holes on the carrier.
Push down on the carrier so that the securing clips click over it at both ends.

Step 9

Replace the top cover to the server.

Step 10

Replace the server in the rack, replace cables, and then fully power on the server by pressing the Power button.


1	Location of socket on motherboard	3	Securing clips
2	Alignment pegs	-

Step 11

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 12

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 13

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing an M.2 SSD in a Mini-Storage Carrier For M.2

This topic describes how to remove and replace an M.2 SSD in a mini-storage carrier for M.2 (UCS-MSTOR-M2).

Procedure

Step 1	Put the node in HX Maintenance Mode, shut down the node, decommission it, and then remove the mini-storage module carrier from the server as described in Replacing a Mini-Storage Module Carrier.
Step 2	Remove an M.2 SSD: Use a #1 Phillips-head screwdriver to remove the single screw that secures the M.2 SSD to the carrier. Remove the M.2 SSD from its socket on the carrier.
Step 3	Install a new M.2 SSD: Angle the M.2 SSD downward and insert the connector-end into the socket on the carrier. The M.2 SSD's label must face up. Press the M.2 SSD flat against the carrier. Install the single screw that secures the end of the M.2 SSD to the carrier.
Step 4	Install the mini-storage module carrier back into the node and then recommission the node, reassociate its profile, and exit HX Maintenance Mode as described in Replacing a Mini-Storage Module Carrier.

Replacing the RTC Battery

Warning

There is danger of explosion if the battery is replaced incorrectly. Replace the battery only with the same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufacturer’s instructions.

[Statement 1015]

The real-time clock (RTC) battery retains system settings when the node is disconnected from power. The battery type is CR2032. Cisco supports the industry-standard CR2032 battery, which can be ordered from Cisco (PID N20-MBLIBATT) or purchased from most electronic stores.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Remove the RTC battery:

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Remove the top cover from the node as described in Removing the Node Top Cover.
Remove PCIe riser 1 from the node to provide clearance to the RTC battery socket that is on the motherboard.
Locate the horizontal RTC battery socket.
Remove the battery from the socket on the motherboard. Gently pry the securing clip to the side to provide clearance, then lift up on the battery.

Step 6

Install a new RTC battery:

Insert the battery into its socket and press down until it clicks in place under the clip.

Note

The positive side of the battery marked “3V+” should face up.

Replace PCIe riser 1 to the node.
Replace the top cover to the node.
Replace the node in the rack, replace cables, and then fully power on the server by pressing the Power button.

Figure 26. RTC Battery Location on Motherboard


1	RTC battery in horizontal socket on motherboard	-

Step 7

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 8

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 9

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing Power Supplies

The node can have one or two power supplies. When two power supplies are installed they are redundant as 1+1.

Replacing AC Power Supplies

Note

If two power supplies are present, you do not have to power off the node to replace one power supply because they are redundant as 1+1.

Note

Do not mix power supply types or wattages in the node. Both power supplies must be identical.

Procedure

Step 1

Remove the power supply that you are replacing:

Perform one of the following actions:
- If your node has two power supplies, you do not have to shut down the server. Continue with step 2.
- If your node has only one power supply:
  1. Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.
  2. Shut down the node as described in Shutting Down and Removing Power From the Node.
  3. Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Step 2

Remove the power supply that you are replacing or a blank panel from an empty bay:

Remove the power cord from the power supply that you are replacing.
Grasp the power supply handle while pinching the release lever toward the handle.
Pull the power supply out of the bay.

Step 3

Install a new power supply:

Grasp the power supply handle and insert the new power supply into the empty bay.
Push the power supply into the bay until the release lever locks.
Connect the power cord to the new power supply.
Only if you shut down the node, press the Power button to boot the node to main power mode.


1	Power supply release lever	2	Power supply handle

Step 4

Only if you shut down the node, perform these steps:

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.
Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.
After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing DC Power Supplies

Warning

A readily accessible two-poled disconnect device must be incorporated in the fixed wiring.

Statement 1022

Warning

This product requires short-circuit (overcurrent) protection, to be provided as part of the building installation. Install only in accordance with national and local wiring regulations.

Statement 1045

Warning

Installation of the equipment must comply with local and national electrical codes.

Statement 1074

Note

If you are replacing DC power supplies in a node with power supply redundancy (two power supplies), you do not have to power off the node to replace a power supply because they are redundant as 1+1.

Note

Do not mix power supply types or wattages in the node. Both power supplies must be identical.

Procedure

Step 1

Remove the DC power supply that you are replacing or a blank panel from an empty bay:

Perform one of the following actions:
- If you are replacing a power supply in a node that has two DC power supplies, you do not have to shut down the node. Continue with step 2.
- If your node has only one power supply:
  1. Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.
  2. Shut down the node as described in Shutting Down and Removing Power From the Node.
  3. Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.
Remove the power cord from the power supply that you are replacing. Lift the connector securing clip slightly and then pull the connector from the socket on the power supply.
Grasp the power supply handle while pinching the release lever toward the handle.
Pull the power supply out of the bay.

Step 2

Install a new DC power supply:

Grasp the power supply handle and insert the new power supply into the empty bay.
Push the power supply into the bay until the release lever locks.
Connect the power cord to the new power supply. Press the connector into the socket until the securing clip clicks into place.
Only if you shut down the node, press the Power button to boot the node to main power mode.


1	Keyed cable connector (CAB-48DC-40A-8AWG)	3	PSU status LED
2	Keyed DC input socket	-

Step 3

Only if you shut down the node, perform these steps:

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.
Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.
After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Grounding for DC Power Supplies

AC power supplies have internal grounding and so no additional grounding is required when the supported AC power cords are used.

When using a DC power supply, additional grounding of the node chassis to the earth ground of the rack is available. Two threaded holes for use with your dual-hole grounding lug and grounding wire are supplied on the chassis rear panel.

Note

The grounding points on the chassis are sized for M5 screws. You must provide your own screws, grounding lug, and grounding wire. The grounding lug must be dual-hole lug that fits M5 screws. The grounding cable that you provide must be 14 AWG (2 mm), minimum 60° C wire, or as permitted by the local code.

Replacing a PCIe Riser

This node has two toolless PCIe risers for horizontal installation of PCIe cards. Each riser is available in multiple versions. See PCIe Slot Specifications for detailed descriptions of the slots and features in each riser version.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Remove the PCIe riser that you are replacing:

Grasp the flip-up handle on the riser and the blue forward edge, and then lift up evenly to disengage its circuit board from the socket on the motherboard. Set the riser on an antistatic surface.
If the riser has a card installed, remove the card from the riser. See Replacing a PCIe Card.

Step 8

Install a new PCIe riser:

Note

The PCIe risers are not interchangeable. If you plug a PCIe riser into the wrong socket, the node will not boot. Riser 1 must plug into the motherboard socket labeled “RISER1.” Riser 2 must plug into the motherboard socket labeled “RISER2.”

If you removed a card from the old PCIe riser, install the card to the new riser. See Replacing a PCIe Card.
Position the PCIe riser over its socket on the motherboard and over its alignment slots in the chassis.
Carefully push down on both ends of the PCIe riser to fully engage its circuit board connector with the socket on the motherboard.

Step 9

Replace the top cover to the node.

Step 10

Replace the node in the rack, replace cables, and then fully power on the node by pressing the Power button.

Figure 29. PCIe Riser Alignment Features


1	Riser handling points (flip-up handle and blue forward edge)	3	Riser 1 alignment features in chassis
2	Riser 2 alignment features in chassis

Step 11

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 12

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 13

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing a PCIe Card

Note

Cisco supports all PCIe cards qualified and sold by Cisco. PCIe cards not qualified or sold by Cisco are the responsibility of the customer. Although Cisco will always stand behind and support the nodes, customers using standard, off-the-shelf, third-party cards must go to the third-party card vendor for support if any issue with that particular card occurs.

PCIe Slot Specifications

The server contains two toolless PCIe risers for horizontal installation of PCIe cards.

Riser 1 contains PCIe slots 1 (x8), 2 (x16), and 3 (x8).
Riser 2B contains PCIe slots 4 (x8), 5 (x16), and 6 (x8). It also includes one PCIe cable connector for rear-loading NVMe SSDs.

Figure 30. Rear Panel, Showing PCIe Slot Numbering

The following tables describe the specifications for the slots.

Table 8. PCIe Riser 1 (UCSC-PCI-1-C240M5) PCIe Expansion Slots
Slot Number	Electrical Lane Width	Connector Length	Maximum Card Length	Card Height (Rear Panel Opening)	NCSI Support	GPU Card Support
1	Gen-3 x8	x24 connector	¾ length	Full height	Yes ¹	No
2	Gen-3 x16	x24 connector	Full length	Full height	Yes	Yes
3	Gen-3 x8	x16 connector	Full length	Full hight	No	No
Micro SD card slot	One socket for Micro SD card on the top of the riser.

¹ NCSI is supported in only one slot at a time. If a GPU card is present in slot 2, NCSI support automatically moves to slot 1.

Table 9. PCIe Riser 2B (UCSC-PCI-2B-C240M5) PCIe Expansion Slots
Slot Number	Electrical Lane Width	Connector Length	Maximum Card Length	Card Height (Rear Panel Opening)	NCSI Support	GPU Card Support
4	Gen-3 x8	x24 connector	¾ length	Full height	Yes	No
5	Gen-3 x16	x24 connector	Full length	Full height	Yes²	Yes
6	Gen-3 x8	x16 connector	Full length	Full hight	No	No
Cable connector for rear NVMe SSD	Gen-3 x8	To rear drive backplane; supports rear-loading NVMe SSDs.

² NCSI is supported in only one slot at a time.

Replacing a PCIe Card

Note

A storage controller card installs into a dedicated motherboard socket. See Replacing a SAS Storage Controller Card (HBA).

Note

For instructions on installing or replacing double-wide GPU cards, see Installing a Double-Wide GPU Card.

Note

If the card you are replacing is a Cisco VIC 1455 (HX-PCIE-C25Q-04), note that this card requires Cisco HX 4.0(1a) or later.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Remove the PCIe card that you are replacing:

Remove any cables from the ports of the PCIe card that you are replacing.
Use two hands to flip up and grasp the blue riser handle and the blue fingergrip area on the front edge of the riser, and then lift straight up.
On the bottom of the riser, push the release latch that holds the securing plate, and then swing the hinged securing plate open.
Open the hinged card-tab retainer that secures the rear-panel tab of the card.
Pull evenly on both ends of the PCIe card to remove it from the socket on the PCIe riser.

If the riser has no card, remove the blanking panel from the rear opening of the riser.

Step 8

Install a new PCIe card:

With the hinged card-tab retainer open, align the new PCIe card with the empty socket on the PCIe riser.
Push down evenly on both ends of the card until it is fully seated in the socket.
Ensure that the card’s rear panel tab sits flat against the riser rear-panel opening and then close the hinged card-tab retainer over the card’s rear-panel tab.
Swing the hinged securing plate closed on the bottom of the riser. Ensure that the clip on the plate clicks into the locked position.
Position the PCIe riser over its socket on the motherboard and over the chassis alignment channels.
Carefully push down on both ends of the PCIe riser to fully engage its connector with the sockets on the motherboard.

Step 9

Replace the top cover to the node.

Step 10

Replace the node in the rack, replace cables, and then fully power on the node by pressing the Power button.

Figure 31. PCIe Riser Card Securing Mechanisms


1	Release latch on hinged securing plate	3	Hinged card-tab retainer
2	Hinged securing plate	-

Step 11

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 12

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 13

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing an mLOM Card

The node supports a modular LOM (mLOM) card to provide additional rear-panel connectivity, such as a Cisco VIC adapter. The mLOM socket is on the motherboard, under the storage controller card.

The mLOM socket provides a Gen-3 x16 PCIe lane. The socket remains powered when the node is in 12 V standby power mode and it supports the network communications services interface (NCSI) protocol.

Note

If the card you are replacing is a Cisco VIC 1457 (HX-MLOM-C25Q-04), note that this card requires Cisco HX 4.0(1a) or later.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Remove any existing mLOM card (or a blanking panel):

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Remove the top cover from the node as described in Removing the Node Top Cover.
Remove any storage controller HBA card to provide clearance to the mLOM socket on the motherboard.
Loosen the single captive thumbscrew that secures the mLOM card to the threaded standoff on the chassis floor.
Slide the mLOM card horizontally to free it from the socket, then lift it out of the node.

Step 6

Install a new mLOM card:

Set the mLOM card on the chassis floor so that its connector is aligned with the motherboard socket.
Push the card horizontally to fully engage the card's edge connector with the socket.
Tighten the captive thumbscrew to secure the card to the chassis floor.
Return the storage controller card to the node.
Replace the top cover to the node.
Replace the node in the rack, replace cables, and then fully power on the node by pressing the Power button.

Figure 32. Location of the mLOM Card Socket Below the Storage Controller Card


1	Position of horizontal mLOM card socket	2	Position of mLOM card thumbscrew

Step 7

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 8

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 9

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing a SAS Storage Controller Card (HBA)

For hardware-based storage control, the server can use a Cisco modular SAS HBA that plugs into a dedicated, vertical socket on the motherboard.

Storage Controller Card Firmware Compatibility

Firmware on the storage controller HBA must be verified for compatibility with the current Cisco IMC and BIOS versions that are installed on the node. If not compatible, upgrade or downgrade the storage controller firmware using the Host Upgrade Utility (HUU) for your firmware release to bring it to a compatible level.

See the HUU guide for your Cisco IMC release for instructions on downloading and using the utility to bring node components to compatible levels: HUU Guides.

Replacing a SAS Storage Controller Card (HBA)

A storage controller card is shipped in a plastic mounting frame. You do not have to remove this frame from an existing card because the frame is preinstalled on a replacement card.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Prepare the node for component installation:

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 6

Remove any existing storage controller card from the node:

Note

A controller card for this node is mounted inside a plastic carrier-frame that helps to secure the card to the inner chassis wall. You do not have to remove this plastic carrier frame from the existing card.

Disconnect cables from the existing card.
Lift up on the card's blue ejector lever to unseat it from the motherboard socket.
Lift straight up on the card's carrier frame to disengage the card from the motherboard socket and to disengage the frame from pegs on the chassis wall.

Step 7

Install a new storage controller card:

Carefully align the card edge with the motherboard socket. At the same time, align the two slots on the back of the carrier frame with the pegs on the chassis inner wall.
Push on both corners of the card to seat its connector in the riser socket. At the same time, ensure that the slots on the carrier frame engage with the pegs on the inner chassis wall.
Fully close the blue ejector lever on the card to lock the card into the socket.
Connect SAS/SATA cables to the new card.

Step 8

Replace the top cover to the node.

Step 9

Replace the node in the rack, replace cables, and then fully power on the node by pressing the Power button.

Figure 33. Replacing a Storage Controller Card


1	Blue ejector lever on card top edge	2	Pegs on inner chassis wall (four)

Step 10

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 11

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 12

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Replacing a Micro SD Card

There is one socket for a Micro SD card on the top of PCIe riser 1.

Caution

To avoid data loss, we do not recommend that you hot-swap the Micro SD card while it is operating, as indicated by its activity LED turning amber. The activity LED turns amber when the Micro SD card is updating or deleting.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Remove an existing Micro SD card:

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Remove the top cover from the node as described in Removing the Node Top Cover.
Locate the Micro SD card. The socket is on the top of PCIe riser 1, under a plastic cover.
Use your fingertip to push the retainer on the plastic socket cover open far enough to provide access to the Micro SD card, then push down and release the Micro SD card to make it spring up.
Grasp the Micro SD card and lift it from the socket.

Step 6

Install a new Micro SD card:

While holding the retainer on the plastic cover open with your fingertip, align the new Micro SD card with the socket.
Gently push down on the card until it clicks and locks in place in the socket.
Replace the top cover to the node.
Replace the node in the rack, replace cables, and then fully power on the node by pressing the Power button.

Figure 34. Location of Internal Micro SD Card Socket


1	Location of Micro SD card socket on the top of PCIe riser 1	3	Plastic retainer (push aside to access socket)
2	Micro SD card socket under plastic retainer	4	Micro SD activity LED

Step 7

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 8

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 9

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Service Headers and Jumpers

This node includes two blocks of headers (J38, J39) that you can jumper for certain service and debug functions.

Figure 35. Location of Service Header Blocks J38 and J39


1	Location of header block J38	6	Location of header block J39
2	J38 pin 1 arrow printed on motherboard	7	J39 pin 1 arrow printed on motherboard
3	Clear CMOS: J38 pins 9 - 10	8	Boot Cisco IMC from alternate image: J39 pins 1 - 2
4	Recover BIOS: J38 pins 11 - 12	9	Reset Cisco IMC password to default: J39 pins 3 - 4
5	Clear password: J38 pins 13 - 14	10	Reset Cisco IMC to defaults: J39 pins 5 - 6

Using the Clear CMOS Header (J38, Pins 9 - 10)

You can use this switch to clear the node’s CMOS settings in the case of a system hang. For example, if the node hangs because of incorrect settings and does not boot, use this jumper to invalidate the settings and reboot with defaults.

Caution

Clearing the CMOS removes any customized settings and might result in data loss. Make a note of any necessary customized settings in the BIOS before you use this clear CMOS procedure.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Install a two-pin jumper across J38 pins 9 and 10.

Step 8

Reinstall the top cover and reconnect AC power cords to the node. The node powers up to standby power mode, indicated when the Power LED on the front panel is amber.

Step 9

Return the node to main power mode by pressing the Power button on the front panel. The node is in main power mode when the Power LED is green.

Note

You must allow the entire node to reboot to main power mode to complete the reset. The state of the jumper cannot be determined without the host CPU running.

Step 10

Press the Power button to shut down the node to standby power mode, and then remove AC power cords from the node to remove all power.

Step 11

Remove the top cover from the node.

Step 12

Remove the jumper that you installed.

Note

If you do not remove the jumper, the CMOS settings are reset to the defaults every time you power-cycle the node.

Step 13

Replace the top cover, replace the node in the rack, replace power cords and any other cables, and then power on the node by pressing the Power button.

Step 14

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 15

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 16

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Using the BIOS Recovery Header (J38, Pins 11 - 12)

Depending on which stage the BIOS becomes corrupted, you might see different behavior.

If the BIOS BootBlock is corrupted, you might see the system get stuck on the following message:
```
Initializing and configuring memory/hardware
```

If it is a non-BootBlock corruption, a message similar to the following is displayed:

****BIOS FLASH IMAGE CORRUPTED****
Flash a valid BIOS capsule file using Cisco IMC WebGUI or CLI interface.
IF Cisco IMC INTERFACE IS NOT AVAILABLE, FOLLOW THE STEPS MENTIONED BELOW.
1. Connect the USB stick with bios.cap file in root folder.
2. Reset the host.
IF THESE STEPS DO NOT RECOVER THE BIOS
1. Power off the system.
2. Mount recovery jumper.
3. Connect the USB stick with bios.cap file in root folder.
4. Power on the system.
Wait for a few seconds if already plugged in the USB stick.
REFER TO SYSTEM MANUAL FOR ANY ISSUES.

Note

As indicated by the message shown above, there are two procedures for recovering the BIOS. Try procedure 1 first. If that procedure does not recover the BIOS, use procedure 2.

Procedure 1: Reboot With bios.cap File

Procedure

Step 1

Download the BIOS update package and extract it to a temporary location.

Step 2

Copy the contents of the extracted recovery folder to the root directory of a USB drive. The recovery folder contains the bios.cap file that is required in this procedure.

Note

The bios.cap file must be in the root directory of the USB drive. Do not rename this file. The USB drive must be formatted with either the FAT16 or FAT32 file system.

Step 3

Insert the USB drive into a USB port on the node.

Step 4

Reboot the node.

Step 5

Return the node to main power mode by pressing the Power button on the front panel.

The node boots with the updated BIOS boot block. When the BIOS detects a valid recovery.cap file on the USB drive, it displays this message:

Found a valid recovery file...Transferring to Cisco IMC
System would flash the BIOS image now...
System would restart with recovered image after a few seconds...

Step 6

Wait for node to complete the BIOS update, and then remove the USB drive from the node.

Note

During the BIOS update, Cisco IMC shuts down the node and the screen goes blank for about 10 minutes. Do not unplug the power cords during this update. Cisco IMC powers on the node after the update is complete.

Procedure 2: Use BIOS Recovery Header and bios.cap File

Procedure

Step 1

Download the BIOS update package and extract it to a temporary location.

Step 2

Copy the contents of the extracted recovery folder to the root directory of a USB drive. The recovery folder contains the bios.cap file that is required in this procedure.

Note

The bios.cap file must be in the root directory of the USB drive. Do not rename this file. The USB drive must be formatted with either the FAT16 or FAT32 file system.

Step 3

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 4

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 5

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 6

Disconnect all power cables from all power supplies.

Step 7

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 8

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 9

Install a two-pin jumper across J38 pins 11 and 12.

Step 10

Reconnect AC power cords to the node. The node powers up to standby power mode.

Step 11

Insert the USB thumb drive that you prepared in Step 2 into a USB port on the node.

Step 12

Return the node to main power mode by pressing the Power button on the front panel.

The node boots with the updated BIOS boot block. When the BIOS detects a valid bios.cap file on the USB drive, it displays this message:

Found a valid recovery file...Transferring to Cisco IMC
System would flash the BIOS image now...
System would restart with recovered image after a few seconds...

Step 13

Wait for node to complete the BIOS update, and then remove the USB drive from the node.

Note

Step 14

After the node has fully booted, power off the node again and disconnect all power cords.

Step 15

Remove the jumper that you installed.

Note

If you do not remove the jumper, after recovery completion you see the prompt, “Please remove the recovery jumper.”

Step 16

Replace the top cover, replace the node in the rack, replace power cords and any other cables, and then power on the node by pressing the Power button.

Step 17

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 18

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 19

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Using the Clear Password Header (J38, Pins 13 - 14)

You can use this switch to clear the administrator password.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Install a two-pin jumper across J38 pins 13 and 14.

Step 8

Reinstall the top cover and reconnect AC power cords to the node. The node powers up to standby power mode, indicated when the Power LED on the front panel is amber.

Step 9

Return the node to main power mode by pressing the Power button on the front panel. The node is in main power mode when the Power LED is green.

Note

You must allow the entire node to reboot to main power mode to complete the reset. The state of the jumper cannot be determined without the host CPU running.

Step 10

Press the Power button to shut down the node to standby power mode, and then remove AC power cords from the node to remove all power.

Step 11

Remove the top cover from the node.

Step 12

Remove the jumper that you installed.

Note

If you do not remove the jumper, the password is cleared every time you power-cycle the node.

Step 13

Replace the top cover, replace the node in the rack, replace power cords and any other cables, and then power on the node by pressing the Power button.

Step 14

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 15

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 16

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Using the Boot Alternate Cisco IMC Image Header (J39, Pins 1 - 2)

You can use this Cisco IMC debug header to force the system to boot from an alternate Cisco IMC image.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Install a two-pin jumper across J39 pins 1 and 2.

Step 8

Reinstall the top cover and reconnect AC power cords to the node. The node powers up to standby power mode, indicated when the Power LED on the front panel is amber.

Step 9

Return the node to main power mode by pressing the Power button on the front panel. The node is in main power mode when the Power LED is green.

Note

When you next log in to Cisco IMC, you see a message similar to the following:

'Boot from alternate image' debug functionality is enabled.  
CIMC will boot from alternate image on next reboot or input power cycle.

Note

If you do not remove the jumper, the node will boot from an alternate Cisco IMC image every time that you power cycle the node or reboot Cisco IMC.

Step 10

To remove the jumper, press the Power button to shut down the node to standby power mode, and then remove AC power cords from the node to remove all power.

Step 11

Remove the top cover from the node.

Step 12

Remove the jumper that you installed.

Step 13

Replace the top cover, replace the node in the rack, replace power cords and any other cables, and then power on the node by pressing the Power button.

Step 14

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 15

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 16

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Using the Reset Cisco IMC Password to Default Header (J39, Pins 3 - 4)

You can use this Cisco IMC debug header to force the Cisco IMC password back to the default.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Install a two-pin jumper across J39 pins 3 and 4.

Step 8

Reinstall the top cover and reconnect AC power cords to the node. The node powers up to standby power mode, indicated when the Power LED on the front panel is amber.

Step 9

Return the node to main power mode by pressing the Power button on the front panel. The node is in main power mode when the Power LED is green.

Note

When you next log in to Cisco IMC, you see a message similar to the following:

'Reset to default CIMC password' debug functionality is enabled.

On input power cycle, CIMC password will be reset to defaults.

Note

If you do not remove the jumper, the node will reset the Cisco IMC password to the default every time that you power cycle the node. The jumper has no effect if you reboot Cisco IMC.

Step 10

To remove the jumper, press the Power button to shut down the node to standby power mode, and then remove AC power cords from the node to remove all power.

Step 11

Remove the top cover from the node.

Step 12

Remove the jumper that you installed.

Step 13

Replace the top cover, replace the node in the rack, replace power cords and any other cables, and then power on the node by pressing the Power button.

Step 14

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 15

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 16

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Using the Reset Cisco IMC to Defaults Header (J39, Pins 5 - 6)

You can use this Cisco IMC debug header to force the Cisco IMC settings back to the defaults.

Procedure

Step 1

Put the node in Cisco HX Maintenance Mode as described in Shutting Down Using vSphere With HX Maintenance Mode.

Step 2

Shut down the node as described in Shutting Down and Removing Power From the Node.

Step 3

Decommission the node from UCS Manager as described in Decommissioning the Node Using Cisco UCS Manager.

Caution

After a node is shut down to standby power, electric current is still present in the node. To completely remove power, you must disconnect all power cords from the power supplies in the node.

Step 4

Disconnect all power cables from all power supplies.

Step 5

Slide the node out the front of the rack far enough so that you can remove the top cover. You might have to detach cables from the rear panel to provide clearance.

Caution

If you cannot safely view and access the component, remove the node from the rack.

Step 6

Remove the top cover from the node as described in Removing the Node Top Cover.

Step 7

Install a two-pin jumper across J39 pins 5 and 6.

Step 8

Reinstall the top cover and reconnect AC power cords to the node. The node powers up to standby power mode, indicated when the Power LED on the front panel is amber.

Step 9

Return the node to main power mode by pressing the Power button on the front panel. The node is in main power mode when the Power LED is green.

Note

When you next log in to Cisco IMC, you see a message similar to the following:

'CIMC reset to factory defaults' debug functionality is enabled.

On input power cycle, CIMC will be reset to factory defaults.

Note

If you do not remove the jumper, the node will reset the Cisco IMC to the default settings every time that you power cycle the node. The jumper has no effect if you reboot Cisco IMC.

Step 10

To remove the jumper, press the Power button to shut down the node to standby power mode, and then remove AC power cords from the node to remove all power.

Step 11

Remove the top cover from the node.

Step 12

Remove the jumper that you installed.

Step 13

Replace the top cover, replace the node in the rack, replace power cords and any other cables, and then power on the node by pressing the Power button.

Step 14

Recommission the node in UCS Manager as described in Recommissioning the Node Using Cisco UCS Manager.

Step 15

Associate the node with its UCS Manager service profile as described in Associating a Service Profile With an HX Node.

Step 16

After ESXi reboot, exit HX Maintenance mode as described in Exiting HX Maintenance Mode.

Setting Up the Node in Standalone Mode

Note

The HX Series node is always managed in UCS Manager-controlled mode. This section is included only for cases in which a node might need to be put into standalone mode for troubleshooting purposes. Do not use this setup for normal operation of the HX Series node.

Initial Node Setup (Standalone)

Note

This section describes how to power on the node, assign an IP address, and connect to node management when using the node in standalone mode.

Node Default Settings

The node is shipped with these default settings:

The NIC mode is Shared LOM EXT.

Shared LOM EXT mode enables the 1-Gb/10-Gb Ethernet ports and the ports on any installed Cisco virtual interface card (VIC) to access the Cisco Integrated Management Interface (Cisco IMC). If you want to use the 10/100/1000 dedicated management ports to access Cisco IMC, you can connect to the node and change the NIC mode as described in Setting Up the Node With the Cisco IMC Configuration Utility.
The NIC redundancy is Active-Active. All Ethernet ports are utilized simultaneously.
DHCP is enabled.
IPv4 is enabled.

Connection Methods

There are two methods for connecting to the system for initial setup:

Local setup—Use this procedure if you want to connect a keyboard and monitor directly to the system for setup. This procedure can use a KVM cable (Cisco PID N20-BKVM) or the ports on the rear of the node.

Remote setup—Use this procedure if you want to perform setup through your dedicated management LAN.

Note

To configure the system remotely, you must have a DHCP server on the same network as the system. Your DHCP server must be preconfigured with the range of MAC addresses for this node. The MAC address is printed on a label that is on the pull-out asset tag on the front panel. This node has a range of six MAC addresses assigned to the Cisco IMC. The MAC address printed on the label is the beginning of the range of six contiguous MAC addresses.

Connecting to the Node Locally For Standalone Setup

This procedure requires the following equipment:

VGA monitor
USB keyboard
Either the supported Cisco KVM cable (Cisco PID N20-BKVM); or a USB cable and VGA DB-15 cable

Procedure

Step 1	Attach a power cord to each power supply in your node, and then attach each power cord to a grounded power outlet. Wait for approximately two minutes to let the node boot to standby power during the first bootup. You can verify system power status by looking at the system Power Status LED on the front panel. The system is in standby power mode when the LED is amber.
Step 2	Connect a USB keyboard and VGA monitor to the node using one of the following methods: Connect an optional KVM cable (Cisco PID N20-BKVM) to the KVM connector on the front panel. Connect your USB keyboard and VGA monitor to the KVM cable. Connect a USB keyboard and VGA monitor to the corresponding connectors on the rear panel.
Step 3	Open the Cisco IMC Configuration Utility: Press and hold the front panel power button for four seconds to boot the node. During bootup, press F8 when prompted to open the Cisco IMC Configuration Utility.
Step 4	Continue with Setting Up the Node With the Cisco IMC Configuration Utility.

Connecting to the Node Remotely For Standalone Setup

This procedure requires the following equipment:

One RJ-45 Ethernet cable that is connected to your management LAN.

Before you begin

Note

To configure the system remotely, you must have a DHCP server on the same network as the system. Your DHCP server must be preconfigured with the range of MAC addresses for this node node. The MAC address is printed on a label that is on the pull-out asset tag on the front panel. This node has a range of six MAC addresses assigned to the Cisco IMC. The MAC address printed on the label is the beginning of the range of six contiguous MAC addresses.

Procedure

Step 1

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

Wait for approximately two minutes to let the node boot to standby power during the first bootup. You can verify system power status by looking at the system Power Status LED on the front panel. The system is in standby power mode when the LED is amber.

Step 2

Plug your management Ethernet cable into the dedicated management port on the rear panel.

Step 3

Allow your preconfigured DHCP server to assign an IP address to the node node.

Step 4

Use the assigned IP address to access and log in to the Cisco IMC for the node node. Consult with your DHCP node administrator to determine the IP address.

Note

The default user name for the node is admin. The default password is password.

Step 5

From the Cisco IMC node Summary page, click Launch KVM Console. A separate KVM console window opens.

Step 6

From the Cisco IMC Summary page, click Power Cycle node. The system reboots.

Step 7

Select the KVM console window.

Note

The KVM console window must be the active window for the following keyboard actions to work.

Step 8

When prompted, press F8 to enter the Cisco IMC Configuration Utility. This utility opens in the KVM console window.

Step 9

Continue with Setting Up the Node With the Cisco IMC Configuration Utility.

Setting Up the Node With the Cisco IMC Configuration Utility

Before you begin

The following procedure is performed after you connect to the node and open the Cisco IMC Configuration Utility.

Procedure

Step 1

Set the NIC mode to choose which ports to use to access Cisco IMC for server management:

Shared LOM EXT (default)—This is the shared LOM extended mode, the factory-default setting. With this mode, the Shared LOM and Cisco Card interfaces are both enabled. You must select the default Active-Active NIC redundancy setting in the following step.

In this NIC mode, DHCP replies are returned to both the shared LOM ports and the Cisco card ports. If the system determines that the Cisco card connection is not getting its IP address from a Cisco UCS Manager system because the server is in standalone mode, further DHCP requests from the Cisco card are disabled. Use the Cisco Card NIC mode if you want to connect to Cisco IMC through a Cisco card in standalone mode.
Shared LOM—The 1-Gb/10-Gb Ethernet ports are used to access Cisco IMC. You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.
Dedicated—The dedicated management port is used to access Cisco IMC. You must select the None NIC redundancy setting in the following step.
Cisco Card—The ports on an installed Cisco UCS Virtual Interface Card (VIC) are used to access the Cisco IMC. You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.

See also the required VIC Slot setting below.
VIC Slot—Only if you use the Cisco Card NIC mode, you must select this setting to match where your VIC is installed. The choices are Riser1, Riser2, or Flex-LOM (the mLOM slot).
- If you select Riser1, you must install the VIC in slot 1.
- If you select Riser2, you must install the VIC in slot 2.
- If you select Flex-LOM, you must install an mLOM-style VIC in the mLOM slot.

Step 2

Set the NIC redundancy to your preference. This server has three possible NIC redundancy settings:

None—The Ethernet ports operate independently and do not fail over if there is a problem. This setting can be used only with the Dedicated NIC mode.
Active-standby—If an active Ethernet port fails, traffic fails over to a standby port. Shared LOM and Cisco Card modes can each use either Active-standby or Active-active settings.
Active-active (default)—All Ethernet ports are utilized simultaneously. The Shared LOM EXT mode must use only this NIC redundancy setting. Shared LOM and Cisco Card modes can each use either Active-standby or Active-active settings.

Step 3

Choose whether to enable DHCP for dynamic network settings, or to enter static network settings.

Note

Before you enable DHCP, you must preconfigure your DHCP server with the range of MAC addresses for this server. The MAC address is printed on a label on the rear of the server. This server has a range of six MAC addresses assigned to Cisco IMC. The MAC address printed on the label is the beginning of the range of six contiguous MAC addresses.

The static IPv4 and IPv6 settings include the following:

The Cisco IMC IP address.

For IPv6, valid values are 1 - 127.
The gateway.

For IPv6, if you do not know the gateway, you can set it as none by entering :: (two colons).
The preferred DNS server address.

For IPv6, you can set this as none by entering :: (two colons).

Step 4

(Optional) Make VLAN settings.

Step 5

Press F1 to go to the second settings window, then continue with the next step.

From the second window, you can press F2 to switch back to the first window.

Step 6

(Optional) Set a hostname for the server.

Step 7

(Optional) Enable dynamic DNS and set a dynamic DNS (DDNS) domain.

Step 8

(Optional) If you check the Factory Default check box, the server reverts to the factory defaults.

Step 9

(Optional) Set a default user password.

Note

The factory default username for the server is admin. The default password is password.

Step 10

(Optional) Enable auto-negotiation of port settings or set the port speed and duplex mode manually.

Note

Auto-negotiation is applicable only when you use the Dedicated NIC mode. Auto-negotiation sets the port speed and duplex mode automatically based on the switch port to which the server is connected. If you disable auto-negotiation, you must set the port speed and duplex mode manually.

Step 11

(Optional) Reset port profiles and the port name.

Step 12

Press F5 to refresh the settings that you made. You might have to wait about 45 seconds until the new settings appear and the message, “Network settings configured” is displayed before you reboot the server in the next step.

Step 13

Press F10 to save your settings and reboot the server.

Note

If you chose to enable DHCP, the dynamically assigned IP and MAC addresses are displayed on the console screen during bootup.

What to do next

Use a browser and the IP address of the Cisco IMC to connect to the Cisco IMC management interface. The IP address is based upon the settings that you made (either a static address or the address assigned by your DHCP server).

Note

The factory default username for the server is admin. The default password is password.

Cisco HX240c M5 HyperFlex Node (Hybrid and All-Flash Models) Installation Guide

Bias-Free Language

Results

Chapter: Maintaining the Node

Maintaining the Node

Status LEDs and Buttons

Front-Panel LEDs

Rear-Panel LEDs

Internal Diagnostic LEDs

Decommissioning the Node Using Cisco UCS Manager

Procedure

Shutting Down and Removing Power From the Node

Shutting Down Using The Cisco UCS Manager Equipment Tab

Procedure

Shutting Down Using The Cisco UCS Manager Service Profile

Procedure

Shutting Down Using vSphere With HX Maintenance Mode

Procedure

Shutting Down Using the Power Button

Procedure

Post-Maintenance Procedures

Recommissioning the Node Using Cisco UCS Manager

Procedure

Associating a Service Profile With an HX Node

Procedure

Exiting HX Maintenance Mode

Procedure

Removing the Node Top Cover

Procedure

Removing and Replacing Components

HX240c SFF Drives Serviceable Component Locations

HX240c LFF Drives Serviceable Component Locations

Considerations For Upgrading Hardware in Multiple Nodes of a Cluster

Procedure

Replacing Drives

Drive Population Rules

SFF Versions Drive Population Rules

LFF Versions Drive Population Rules

HX240c M5 Drive Configuration Comparison

Drive Replacement Overview

Replacing the Housekeeping SSD

Procedure

Replacing Persistent Data Drives

Procedure

Replacing the Caching SSD

Procedure

Replacing Fan Modules

Procedure

Replacing Memory DIMMs

DIMM Population Rules and Memory Performance Guidelines

DIMM Slot Numbering

DIMM Population Rules

Replacing DIMMs

Procedure

Replacing CPUs and Heatsinks

Special Information For Upgrades to Second Generation Intel Xeon Scalable Processors

CPU Configuration Rules

Tools Required For CPU Replacement

Replacing a CPU and Heatsink

Procedure

Additional CPU-Related Parts to Order with RMA Replacement CPUs

Additional CPU-Related Parts to Order with RMA Replacement System Chassis

Moving an M5 Generation CPU

Procedure

Replacing a Mini-Storage Module or M.2 Boot Drive

Replacing a Mini-Storage Module Carrier

Procedure

Replacing an M.2 SSD in a Mini-Storage Carrier For M.2

Procedure

Replacing the RTC Battery

Procedure

Replacing Power Supplies

Replacing AC Power Supplies

Procedure

Replacing DC Power Supplies

Procedure

Grounding for DC Power Supplies

Replacing a PCIe Riser

Procedure

Replacing a PCIe Card