Cisco Bug: CSCuo35507 - After allconfig import, several veths down/nonpartcipatng on primary FI
Jan 31, 2017
- Cisco Unified Computing System
Known Affected Releases
Symptom: After allconfig import upon erase samDB, several veths down/nonparitcipatng on primary FI; if few chassis were manually discovered before config import Conditions: - Start with Test bed with ?Chassis Discovery Policy? set to NON-DEFAULT values (2,4,8 links or Port-Channel) - All the chassis are fully discovered with all/most of the present links acknowledged, running in IOM uplink port channel mode, - Trigger all config backup - Erase samDB - Before triggering restore from the backup file, manually enable a few server ports to discover some chassis with ?Chassis Discovery Policy? set to DEFAULT values - Upon discovering those chassis, trigger Import operation - After import successful, after all blades gets associated we see several veths on primary FI to be down/non-participating. - ESX Ip on all blades accessible.
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