Cisco Bug: CSCuq78915 - port-mode config applied after controller deletion
Jan 07, 2017
- Cisco Carrier Routing System
Known Affected Releases
Symptom: 'port-mode' config applied to a nV Optical Optics controller is rejected if committed at the same time as the controller being deleted. For instance, the 'no transponder' config below causes the Optics100/3/0/1 controller to be deleted, and the port-mode config to be rejected. The expected behaviour is that the 'port-mode' config is moved to preconfiguration under the deleted controller. RP/0/0/CPU0:ios(config)#show conf Wed Sep 10 15:01:29.158 BST Building configuration... !! IOS XR Configuration 0.0.0 nv satellite 100 no transponder 100g 3/0/2 ! ! controller Optics100/3/0/1 port-mode Otn ! end RP/0/0/CPU0:ios(config)#commit Wed Sep 10 15:01:36.086 BST % Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors RP/0/0/CPU0:ios(config)#show conf fail ... controller Optics100/3/0/1 port-mode Otn !!% Invalid argument specified in satellite configuration: Controller Optics100/3/0/1 not found ! end Conditions: Seen in any scenario that causes 'port-mode' config to be added or changed on an Optics controller that is being deleted. In particular, it's possible to see this behaviour during config rollbacks.
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