UCS Manager - Revision history

Adj: /* A new step for firmware infrastructure updates */

2026-04-03T05:10:26Z

A new step for firmware infrastructure updates

Adj: /* Applying firmware update to blades */

2026-04-02T23:37:27Z

Applying firmware update to blades

← Older revision		Revision as of 23:37, 2 April 2026
Line 1,364:		Line 1,364:
	ucs-fi-6248up-0-A /firmware #		ucs-fi-6248up-0-A /firmware #
	Note that the UCS Manager SSH client can now talk to a Debian 12 OpenSSH server. Small wins are still wins!		Note that the UCS Manager SSH client can now talk to a Debian 12 OpenSSH server. Small wins are still wins!

			=== A new step for firmware infrastructure updates ===
			It seems that one must accept that a fabric interconnect reboot has happened before applying a new infrastructure firmware pack. Something like this:
			ucs-fi-6248up-0-A# '''scope monitoring'''
			ucs-fi-6248up-0-A /monitoring # '''show new-faults'''
			Severity Code Last Transition Time ID Description
			--------- -------- ------------------------ -------- -----------
			Info F0440 2026-04-02T18:37:14.718 113208 Chassis discovery policy conflict: Link IOM 1/1/2 to peer port A:N/A/1/2 not configured
			ucs-fi-6248up-0-A /monitoring # '''top'''
			ucs-fi-6248up-0-A# '''scope firmware'''
			ucs-fi-6248up-0-A /firmware # '''scope auto-install'''
			ucs-fi-6248up-0-A /firmware/auto-install # '''acknowledge primary fabric-interconnect reboot '''
			ucs-fi-6248up-0-A /firmware/auto-install* # '''commit-buffer'''
			ucs-fi-6248up-0-A /firmware/auto-install # '''install infra infra-vers 3.2(3p)A'''
			This operation upgrades firmware on UCS Infrastructure Components
			(UCS manager, Fabric Interconnects and IOMs).
			Here is the checklist of things that are recommended before starting Auto-Install
			(1) Review current critical/major faults
			(2) Initiate a configuration backup
			(3) Check if Management Interface Monitoring Policy is enabled
			(4) Check if there is a pending Fabric Interconnect Reboot activitiy
			(5) Ensure NTP is configured
			(6) Check if any hardware (fabric interconnects, io-modules, servers or adapters) is unsupported in the target release
			(7) Some fabric-interconnect service-pack install/uninstall will do additional FI reboots in order to complete install/uninstall
			To ensure before triggering auto-install, check manual service-pack activation/remove where warning is given if reboots are required
			Do you want to proceed? (yes/no):'''yes'''

			Triggering Install-Infra with:
			Infrastructure Pack Version: 3.2(3p)A
			Warning: Any Service Pack installed in the system will be removed

			ucs-fi-6248up-0-A /firmware/auto-install # '''acknowledge primary fabric-interconnect reboot'''
			Warning: Check the outstanding faults (scope monitoring <enter> show new-faults) since last FI reboot.
			Please make sure the data paths are recovered before proceeding with this FI reboot to ensure there is no interruption to the data traffic.

			ucs-fi-6248up-0-A /firmware/auto-install* # '''commit-buffer '''
			ucs-fi-6248up-0-A /firmware/auto-install #
			Broadcast message from root (Thu Apr 2 23:36:05 2026):

			The system is going down for reboot NOW!
			Connection to 172.16.10.176 closed by remote host.
			Connection to 172.16.10.176 closed.

Adj: /* Applying firmware update to blades */

2026-04-02T21:48:00Z

Applying firmware update to blades

← Older revision		Revision as of 21:48, 2 April 2026
Line 1,321:		Line 1,321:
	ucs-fi-6248up-0-A#		ucs-fi-6248up-0-A#
	Still only does RSA host keys. But it does support more recent symmetric encryption schemes than the SSH server in 2.5(2a). But major excitement! The web UI now just needs HTML rendering. And ECMAscript. And CSS. But no more need for Java just to see what is going on with the UCS infrastructure. It does seem to still be needed for the KVM. But this is a major step forward. I very strongly recommend getting to the 3.1 UCS Manager releases.		Still only does RSA host keys. But it does support more recent symmetric encryption schemes than the SSH server in 2.5(2a). But major excitement! The web UI now just needs HTML rendering. And ECMAscript. And CSS. But no more need for Java just to see what is going on with the UCS infrastructure. It does seem to still be needed for the KVM. But this is a major step forward. I very strongly recommend getting to the 3.1 UCS Manager releases.

			And now for some server (blade) firmware. Available at the same place as the UCS Manager download, a section called "Related Software" has the server firmware images. Download and copy those to the UCS Manager running on the fabric interconnects, too:
			ucs-fi-6248up-0-A# '''scope firmware'''
			ucs-fi-6248up-0-A /firmware # '''download image scp://adj@172.17.0.18/home/adj/Downloads/ucs-k9-bundle-b-series.3.1.3l.B.bin'''
			ucs-fi-6248up-0-A /firmware # '''show download-task'''

			Download task:
			File Name Protocol Server Userid State
			--------- -------- ------------------------------------- --------------- -----
			ucs-k9-bundle-b-series.3.1.3l.B.bin
			Scp 172.17.0.18 adj Downloading
			ucs-k9-bundle-infra.2.2.8m.A.bin
			Tftp 172.17.0.18 Downloaded
			ucs-k9-bundle-infra.2.5.2a.A.bin
			Scp 172.17.0.18 adj Downloaded
			ucs-k9-bundle-infra.3.1.3l.A.bin
			Tftp 172.17.0.18 Downloaded
			ucs-mini-k9-bundle-infra.3.0.2f.A.bin
			Tftp 172.17.0.18 Downloaded
			ucs-fi-6248up-0-A /firmware # '''show download-task ucs-k9-bundle-b-series.3.1.3l.B.bin detail'''

			Download task:
			File Name: ucs-k9-bundle-b-series.3.1.3l.B.bin
			Protocol: Scp
			Server: 172.17.0.18
			Userid: adj
			Path: /home/adj/Downloads
			Downloaded Image Size (KB): 517633
			State: Downloading
			Current Task: unpacking image ucs-k9-bundle-b-series.3.1.3l.B.bin on primary(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:UnpackLocal)
			ucs-fi-6248up-0-A /firmware # '''show download-task ucs-k9-bundle-b-series.3.1.3l.B.bin detail'''

			Download task:
			File Name: ucs-k9-bundle-b-series.3.1.3l.B.bin
			Protocol: Scp
			Server: 172.17.0.18
			Userid: adj
			Path: /home/adj/Downloads
			Downloaded Image Size (KB): 517633
			State: Downloaded
			Current Task:
			ucs-fi-6248up-0-A /firmware #
			Note that the UCS Manager SSH client can now talk to a Debian 12 OpenSSH server. Small wins are still wins!

Adj: /* Applying firmware update to blades */

2026-04-02T19:37:49Z

Applying firmware update to blades

@@ Line 1,293: / Line 1,293: @@
 -04-02T17:53:33.561802+00:00 zarathud sudo:      adj : TTY=pts/22 ; PWD=/home/adj ; USER=root ; COMMAND=/usr/bin/grep ssh.*172.16.10.176 /var/log/auth.log
  adj@zarathud:~$
-So, for expediency's sake, we will just do it over TFTP this time.  Maybe the SSH client in the 3.0(2f) release will be better able to talk to my SSH servers?
+So, for expediency's sake, we will just do it over TFTP this time.  Maybe the SSH client in the 3.1(3l) release will be better able to talk to my SSH servers?  That last remains to be seen.  But the SSH server is a bit nearer to 2026 standards:

Adj: /* Applying firmware update to blades */

2026-04-02T18:00:39Z

Applying firmware update to blades

@@ Line 1,285: / Line 1,285: @@
  Package-Vers: 2.5(2a)A
  ucs-fi-6248up-0-A#
-It would seem that 3.0(2f) is the latest in the next-newer release train.  So acquire that from Cisco's download site and install on the FI and apply following the process documented above.
+It would seem that 3.0(2f) is the latest in the next-newer release train.  So acquire that from Cisco's download site and install on the FI and apply following the process documented above.  And there is a hiccup with the SSH in 2.5(2a) not being able to get a host key from the SSH servers running on Debian 12 or Debian 13.  Here's an example Debian server log of that:

Adj: /* Serial console for blades? */

2026-04-02T17:21:09Z

Serial console for blades?

← Older revision		Revision as of 17:21, 2 April 2026
Line 1,237:		Line 1,237:
	ucs-fi-6248up-0-A /chassis/server/cimc # '''top'''		ucs-fi-6248up-0-A /chassis/server/cimc # '''top'''
	ucs-fi-6248up-0-A#		ucs-fi-6248up-0-A#
			So there is still no working serial console on the blade at this point. https://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-b-series-blade-servers/200105-Utilizing-SoL-logging-for-Serial-Redirec.html says to SSH to the CIMC IP address. Just getting a TCP RST back ("connection refused") when trying that. And the IPMI over LAN serial just does not seem to be supported at all. Maybe the blade needs a firmware update, too?
			=== Applying firmware update to blades ===
			So far (I think) I have only done firmware updates to the fabric interconnect and the blade chassis FEXes. First up, let's see what is available for our B200 M3 blades:
			ucs-fi-6248up-0-A# '''scope firmware'''
			ucs-fi-6248up-0-A /firmware # '''show image \| i b200-m3'''
			ucs-b200-m3-bios.B200M3.2.0.4a.0.080920121557.bin
			ucs-b200-m3-bios.B200M3.2.2.1a.0.111220131105.bin
			ucs-b200-m3-brdprog.11.0.bin Board Controller 11.0
			ucs-b200-m3-k9-cimc.2.0.4b.bin CIMC 2.0(4b)
			ucs-b200-m3-k9-cimc.2.2.1c.bin CIMC 2.2(1c)
			ucs-b200-m3-mrsasctlr.20.10.1-0100_4.30.00_NA.bin
			ucs-b200-m3-mrsasctlr.20.12.1-0160_4.37.00_NA.bin
			ucs-fi-6248up-0-A /firmware #
			Those might be kinda old? Let's see what is installed on the B200 M3 that is in the chassis:
			ucs-fi-6248up-0-A /firmware # '''top'''
			ucs-fi-6248up-0-A# '''scope server 1/1'''
			ucs-fi-6248up-0-A /chassis/server # '''show firmware'''
			Server 1/1:
			Adapter 1:
			Running-Vers: 4.1(3a)
			Package-Vers:
			Update-Status: Ready
			Activate-Status: Ready
			Adapter 2:
			Running-Vers: 4.1(3a)
			Package-Vers:
			Update-Status: Ready
			Activate-Status: Ready
			BIOS:
			Running-Vers: B200M3.2.2.6d.0.062220160055
			Package-Vers:
			Update-Status: Ready
			Activate-Status: Ready

			RAID Controller 1:
			Running-Vers: 20.13.1-0255
			Package-Vers:
			Activate-Status: Ready

			BoardController:
			Running-Vers: 15.0
			ucs-fi-6248up-0-A /chassis/server #
			From this, it would seem that the blade in the chassis is already running a newer firmware bundle than the one running on the fabric interconnect. So, let's find out what we are running on the FI, and see about some more updates to it:
			ucs-fi-6248up-0-A /chassis/server # '''top'''
			ucs-fi-6248up-0-A# '''show version brief'''
			System version: 2.5(2a)
			Package-Vers: 2.5(2a)A
			ucs-fi-6248up-0-A#
			It would seem that 3.0(2f) is the latest in the next-newer release train. So acquire that from Cisco's download site and install on the FI and apply following the process documented above.

Adj: /* Serial console for blades? */

2026-03-31T22:04:43Z

Serial console for blades?

← Older revision		Revision as of 22:04, 31 March 2026
Line 1,188:		Line 1,188:
	ucs-fi-6248up-0-A /chassis/server/cimc* # '''commit-buffer'''		ucs-fi-6248up-0-A /chassis/server/cimc* # '''commit-buffer'''
	ucs-fi-6248up-0-A /chassis/server/cimc #		ucs-fi-6248up-0-A /chassis/server/cimc #

			And trying again from a machine on the same subnet:
			router$ '''ipmitool -I lanplus -H 172.16.10.169 -U admin sol activate'''
			Password:
			Error activating SOL payload: Invalid data field in request
			router$

			So still no. Grrrr. Maybe it needs to be powered on first?
			router$ '''ipmitool -I lanplus -H 172.16.10.169 -U admin chassis power status'''
			Password:
			Chassis Power is off
			router$ '''ipmitool -I lanplus -H 172.16.10.169 -U admin chassis power on'''
			Password:
			Chassis Power Control: Up/On
			router$ '''sleep 30'''
			router$ '''ipmitool -I lanplus -H 172.16.10.169 -U admin sol activate'''
			Password:
			Error activating SOL payload: Invalid data field in request
			router$

			More grrrr. Manuals suggest I might need a BIOS policy that enables the serial port, too?
			ucs-fi-6248up-0-A# '''scope org /'''
			ucs-fi-6248up-0-A /org # '''create bios-policy serial_is_good'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set quiet-boot-config quiet-boot disabled'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set serial-port-a-config serial-port-a enabled'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set console-redir-config baud-rate 115200'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set console-redir-config console-redir serial-port-a'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set console-redir-config flow-control none'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set console-redir-config legacy-os-redir disabled'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''set console-redir-config terminal-type vt100-plus'''
			ucs-fi-6248up-0-A /org/bios-policy* # '''commit-buffer'''
			ucs-fi-6248up-0-A /org/bios-policy # '''up'''
			ucs-fi-6248up-0-A /org # '''show service-profile'''

			Service Profile:
			Service Profile Name Type Server Assignment Association
			-------------------- ----------------- ------- ---------- -----------
			UCS_B200_M3_FCH162871NA
			Instance 1/1 Assigned Associating
			ucs-fi-6248up-0-A /org # '''scope service-profile UCS_B200_M3_FCH162871NA'''
			ucs-fi-6248up-0-A /org/service-profile # '''set bios-policy serial_is_good'''
			ucs-fi-6248up-0-A /org/service-profile* # '''commit-buffer'''
			ucs-fi-6248up-0-A /org/service-profile # '''top'''
			ucs-fi-6248up-0-A# '''scope server 1/1'''
			ucs-fi-6248up-0-A /chassis/server # '''scope cimc'''
			ucs-fi-6248up-0-A /chassis/server/cimc # '''reset'''
			ucs-fi-6248up-0-A /chassis/server/cimc* # '''commit-buffer'''
			ucs-fi-6248up-0-A /chassis/server/cimc # '''top'''
			ucs-fi-6248up-0-A#

Adj: /* Create VLAN and VLAN group to connect the CIMC IP pool to */

2026-03-31T18:19:56Z

Create VLAN and VLAN group to connect the CIMC IP pool to

Show changes

Adj: /* Another UCS Manager (and Fabric Interconnect) update */

2026-03-30T22:05:08Z

Another UCS Manager (and Fabric Interconnect) update

Show changes

Adj: /* Telling the FI to discover the blade chassis */

2026-03-27T17:12:21Z

Telling the FI to discover the blade chassis

← Older revision		Revision as of 17:12, 27 March 2026
Line 193:		Line 193:

	=== Telling the FI to discover the blade chassis ===		=== Telling the FI to discover the blade chassis ===
	This is way more complicated that it needs to be. I'm sure it's totally amazing if you have racks full of Cisco UCS hardware. But I have just the one blade chassis and the one C series server and the 2 fabric interconnects. And the FI management software is all lovely out of date Java stuff. So fumbling around the CLI, hoping to find my way out of the darkness here.		This is way more complicated that it needs to be. I'm sure it's totally amazing if you have racks full of Cisco UCS hardware. But I have just the one blade chassis and the one C series server and the 2 fabric interconnects. And the friendly FI management software is all lovely out of date (completely unrunnable in 2026!) Java stuff. So fumbling around the CLI, hoping to find my way out of the darkness here.

	The process for this seems to be something like:		The process for this seems to be something like: