Cisco Bug: CSCuo34760 - Veth's/VIF's down on several servers after rebooting Primary-FI
Nov 27, 2018
- Cisco Unified Computing System
Known Affected Releases
2.1(2d)A 2.2(1.200)A 2.2(1d)A 2.2(2.107)A 2.2(2.116)A
Symptom: Some of the Veths/VIFs may be in down state on the Fabric Interconnect which is currently primary and becomes subordinate after it is rebooted. Corresponding Veths/VIFS are up state on Primary Fabric Interconnect. The VIF's are down from both UCSM and Switch perspective. Conditions: i)UCS is in cluster HA configuration. ii)This issue is seen intermittently only if Primary Fabric Interconnect gets rebooted and come back up as subordinate Fabric Interconnect and some Veths/VIFs state remain down on this new subordinate FI (while previous subordinate Fabric Interconnect becomes Primary). Reboot of FI when working as Primary Fabric Interconnect is not a normal/expected operation. If primary FI needs to be rebooted, user should force a switchover so that other FI becomes primary FI. Once it becomes subordinate FI after switchover, it can be rebooted without this issue impact.
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