Cisco Bug: CSCun01514 - Boot Order change via CLI or XML API fails between San & other devices
Last Modified
Jan 24, 2017
Products (1)
- Cisco Unified Computing System
Known Affected Releases
2.2(1b)A
Description (partial)
Symptom: While trying to modify the boot order in boot policy which has san device an error like the following gets displayed. "Boot order numbers must be unique between org-root/boot-policy-<boot policy name>/storage and org-root/boot-policy-<boot policy name>/lan device." Conditions: Case (a) a. User has a San boot device under storage group (Storage ->SanImage) in pre-elcapitan release (ex: 2.1) and the storage boot order is set to 1 b. User has another boot device (ex: Lan, vMedia etc) and the boot order is set to 2 c. Once it is upgraded to elcpaitan (2.2 rel) and then user tried to alter the boot order between these two devices (modify SanMo's order to 2 and LanMo's order to 1), this issue will be observed. Case (b) a. User created a San boot device under storage (Storage ->SanImage) from CLI or XML interface in elcapitan release (2.2) and the storage boot order is set to 1 b. PLEASE NOTE THAT THE ABOVE IS NOT POSSIBLE FROM GUI as GUI ALWAYS USES SANMO HIERARCHY c. User has another boot device (ex: Lan, vMedia etc) and the boot order is set to 2 d. Now when user trying to alter the boot order between these two devices (modify SanMo's order to 2 and LanMo's order to 1), this issue will be observed.
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