Cisco UCS Rack servers - Revision history

Adj: /* Serial over LAN */

2026-03-26T18:26:05Z

Serial over LAN

← Older revision		Revision as of 18:26, 26 March 2026
Line 90:		Line 90:
	Connection to 172.16.10.160 closed.		Connection to 172.16.10.160 closed.
	$		$
			The Ctrl+x thing is annoying. My habit with GRUB is to kick off edited menu entries with Ctrl+x. On this one, I must hit the F10 key instead. No major complaints aside from that, though. Pasting in 200+ character disk passphrases works without issue.

	== Mass storage devices, RAID, JBOD, and such ==		== Mass storage devices, RAID, JBOD, and such ==

2026-03-26T15:53:36Z

Server Power Control

@@ Line 50: / Line 50: @@
  Do you want to continue?[y|N]'''y'''
  C220-WZP22040X50 /chassis # '''exit'''
  C220-WZP22040X50#
 === Serial over LAN ===

2026-03-26T15:30:33Z

Doing things with the CIMC

2026-03-24T21:13:51Z

JBOD operations

← Older revision		Revision as of 21:13, 24 March 2026
Line 110:		Line 110:

	== JBOD operations ==		== JBOD operations ==
	JBOD mode, right? Plug in a disk, maybe scan the bus, watch it go, right? Well, no. That would be too easy. Instead, one can SSH to the CIMC and do this:		JBOD mode, right? Plug in a disk, maybe scan the bus, watch it go, right? Well, no. That would be too easy. Instead, one can SSH to the CIMC and do something like this:
	C220-WZP22040X50# '''scope chassis'''		C220-WZP22040X50# '''scope chassis'''
	C220-WZP22040X50 /chassis # '''scope storageadapter MRAID'''		C220-WZP22040X50 /chassis # '''scope storageadapter MRAID'''

2026-03-24T21:07:17Z

Storage media with SCSI Protection Information need not apply

← Older revision		Revision as of 21:07, 24 March 2026
Line 105:		Line 105:

	== Storage media with SCSI Protection Information need not apply ==		== Storage media with SCSI Protection Information need not apply ==
	Yeah, so the <code>AVAGO <Cisco 12G Modular Raid Controller with 2GB cache (max 16 drives)> Configuration</code> does not like these at all. Drop into a Dell machine with perhaps a LSI SAS2008 instead and do something like		Yeah, so the <code>AVAGO <Cisco 12G Modular Raid Controller with 2GB cache (max 16 drives)> Configuration</code> does not like these at all. These would be drives that do not have 512-byte or 4096-byte sectors. Often such drives are NetApp or EMC or 3PAR pulls. Drop into a Dell machine with perhaps a LSI SAS2008 instead and do something like
	$ '''sudo sg_format --verbose --verbose --format --quick --size=512 --fmtpinfo=0 --pfu=0 /dev/sg3'''		$ '''sudo sg_format --verbose --verbose --format --quick --size=512 --fmtpinfo=0 --pfu=0 /dev/sg3'''
	to such a drive before trying anything in the UCS server. Ugh...		to such a drive before trying anything in the UCS server. Ugh...

2026-03-24T21:04:06Z

Mass storage devices, RAID, JBOD, and such

@@ Line 103: / Line 103: @@
 * Save changes and reset the system one more time
 From here, operating system installation can commence.  Or storage device firmware updates.  Or whatever...
 == Hardware Fault Resolution ==

2026-03-21T18:22:44Z

Mass storage devices, RAID, JBOD, and such

← Older revision		Revision as of 18:22, 21 March 2026
Line 103:		Line 103:
	* Save changes and reset the system one more time		* Save changes and reset the system one more time
	From here, operating system installation can commence. Or storage device firmware updates. Or whatever...		From here, operating system installation can commence. Or storage device firmware updates. Or whatever...

			== Hardware Fault Resolution ==
			Before arriving in the data center and being put into service, my first UCS C series server had a memory DIMM removed to count how much RAM was installed. It was won at auction and no hardware specs were supplied. The DIMM was not correctly re-seated before the server was powered on. The POST code correctly flagged the issue, deactivated the DIMM, and made entries in the System Event Log (SEL) '''and''' a Cisco specific Fault History Log. The SEL is easy enough to clear with <code>ipmitool</code> from the running OS, or from the CIMC. However, the Fault History Log is separate. <strike>Google</strike> Duck Duck Go search results have indicated the server's Fault History Log may be clearable with the Cisco UCS Manager software. [[UCS Manager]] is a whole separate thing and has its own page.

2026-03-18T00:52:43Z

Mass storage devices, RAID, JBOD, and such

← Older revision		Revision as of 00:52, 18 March 2026
Line 102:		Line 102:
	* Arrow down to <code>JBOD Mode</code> and set to <code>Enabled</code> if it is not already so.		* Arrow down to <code>JBOD Mode</code> and set to <code>Enabled</code> if it is not already so.
	* Save changes and reset the system one more time		* Save changes and reset the system one more time
	From here, operating system installation can commence.		From here, operating system installation can commence. Or storage device firmware updates. Or whatever...

2026-03-16T00:44:40Z

Mass storage devices, RAID, JBOD, and such

@@ Line 94: / Line 94: @@
 * Select <code>Yes</code> from the menu.
 * Return to the top level of the <code>AVAGO &lt;Cisco 12G Modular Raid Controller with 2GB cache (max 16 drives)&gt; Configuration</code> menu.
-* Save configuration and reboot server.
+* Save configuration, reboot server, and enter the BIOS setup screen one more time (press <code>F2</code>).

2026-03-16T00:34:59Z

Mass storage devices, RAID, and such

@@ Line 70: / Line 70: @@
+ $
-== Mass storage devices, RAID, and such ==
+== Mass storage devices, RAID, JBOD, and such ==
 The ECS C220 M5 has a Broadcom/LSI MegaRAID Tri-Mode SAS3516 attached to the disk backplane in the front of the chassis.