Guest

Preview Tool

Cisco Bug: CSCut63966 - FI boot variables not set after a successful upgrade

Last Modified

Aug 21, 2017

Products (1)

  • Cisco Unified Computing System

Known Affected Releases

2.2(1b)A 2.2(3) 2.2(3c)A 2.2(3d)A 2.2(3e)A 2.2(3f)A 2.2(4b)A

Description (partial)

Symptom:
During upgrade, or after a reboot or power cycle of the Fabric Interconnect, it could fail to reload properly due to boot variables not being set, or due to one of the partitions on the SSD (i.e. /bootflash, /opt) getting corrupted.

The SSD corruption symptoms can be different, from simple file system corruption to the file system becoming read-only.

Conditions:
Performing Fabric Interconnect reload or power cycle during manual and auto firmware installs.

Related Community Discussions

Recover FI
We took a extended power failure, and one of our FI's didn't come back. We reset the power on it, hoping it would come back, but it didn't. Connecting a console on it, and booting it again has exposed the problem as a corrupt image.  The question I have is which one?  Am I past the 3 special firmwares I have to create a TAC case on. I can tell that it successfully boots the kickstart image: Booting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5 .2.3.N2.2.23f.bin.... ............................................................................... ...
Latest activity: Dec 01, 2015
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.