Preview Tool

Cisco Bug: CSCut61527 - B200 M4 reboot due to blank MRAID12G Serial number

Last Modified

Nov 20, 2019

Products (1)

  • Cisco Unified Computing System

Known Affected Releases

2.2(3) 2.2(3a)A

Description (partial)

B200 M4 rebooted unexpectedly

A deep discovery is observed from the UCSM tech-support, rather than the intended shallow discovery

Any operation that triggers a shallow discovery could transition to a deep discovery if the Serial number of the blade's MRAID12G RAID controller is blank.

Even after the unexpected reboot and deep discovery, UCSM "show server inventory expand" output will show a blank SN for the MRAID12G RAID controller:
        RAID Controller 1:
            Type: SAS
            Vendor: Cisco Systems Inc
            Model: UCSB-MRAID12G
            HW Revision: C0
            PCI Addr: 01:00.0
            Raid Support: RAID0, RAID1
            OOB Interface Supported: Yes
            Rebuild Rate: 30
            Controller Status: Optimal

Example operations that will trigger a shallow discovery:
	CIMC Reset
	UCS Manager Upgrade
	UCS Manager Cluster lead operation
	IOM Reboot/Reset
	IOM Offline Event due to cable disconnect/reconnect
	Fabric Interconnect Reboot

Note: The UCSB-MRAID12G RAID controller is an optional/removable component on the B200-M4. If no attributes are populated in the show server inventory expand command output for Raid Controller 1, then it is not installed and you are not impacted.
RAID Controller 1:  
            Type: SAS  
            HW Revision:  
            PCI Addr:  
            Raid Support:  
            OOB Interface Supported: No

Related Community Discussions

Change boot policy
Hi, I'm planning to change the boot policy from SAN boot to local disk while decommissioning our old SAN storage. Can I change this in the Service Profile Template and reboot one server at a time to reinstall OS on it? I want to be sure that the change of boot policy does not trigger a reboot of all servers at the same time (Maint policy is User Ack).
Latest activity: Mar 06, 2017
Bug details contain sensitive information and therefore require a 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.