Cisco Bug: CSCuo31859 - Preconfig lost during nested restore when committed with gl config
Jan 09, 2017
- Cisco Carrier Routing System
Known Affected Releases
Symptom: Preconfig committed under a nV Optical controller can be lost if committed at the same time as transponder or muxponder config. For example, committing the following config in a single commit is unlikely to have the desired effect: nv satellite 100 type ons15454-m6 transponder 100g 3/0/2 ! controller preconfigure Optics100/3/0/1 port-mode ethernet ! The likely behaviour is that the 'port-mode' config is lost from the system. It is possible to see this behaviour in any scenario that causes transponder/muxponder config to be committed along with controller preconfig, for instance during config rollback. Conditions: Seen usually when configuring a transponder or muxponder, and (in the same config commit) preconfiguring a controller that's part of that transponder or muxponder. Only preconfig is impacted; without the 'preconfig' keyword the problem is not seen. There is no impact to preconfig that's already in the system (i.e. listed in 'show running'), when the transponder/muxponder is configured. Can also be seen when configuring a satellite's type (and preconfiguring a controller), if the satellite has existing transponder/muxponder configuration.
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