Cisco Bug: CSCur49297 - Unexpected blades reboot by changes from UCS Central
Apr 27, 2015
- Cisco UCS Central Software
Known Affected Releases
Symptom: In some rare conditions, some UCS blades rebooted unexpectedly in UCS Central managed environment. Service Profile disassociate and re-associate are evident in UCSM logs to cause the blade to reboot. blade obfl logs evident UUID changes from dynamic/logical UUID to hardware default UUID, and then from hardware UUID back to logical UUID Not necessary all blades rebooted and typical will be some blades in the same UCS domain. Conditions: The condition is: 1. UCS Central pnDn property was empty when we send over the Service Profile changes to UCSM 2. blade discovery attribute is not compute::CONST_DISCOVERY_COMPLETE or presence is NOT equipment::CONST_PRESENCE_EQUIPPED A known scenario to meet this condition is: 1. UCS Central and UCS Manager connection is down by potential management network issue (lost visibility) 2. Some changes to service profile were made in UCS Central during the connection is down 3. UCSM cluster lead switchover occurred at the same time the connection between UCS Central and UCSM comes up, as a result, pending service profile changes are applied to blades which are undergoing shallow discovery.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases