Cisco Bug: CSCvv37367 - DCNM incorrectly modifies Nexus logfile configuration with Enable Strict Config Compliance enabled
Sep 01, 2020
- Cisco Data Center Network Manager
Known Affected Releases
Symptom: A Nexus 9000 switch managed by DCNM (Data Center Network) with the "Enable Strict Config Compliance" option configured will incorrectly disable the default syslog of the Nexus 9000 switch if the default syslog configuration is modified (such as to increase or decrease the logging level). For example, consider a scenario where a network administrator manually configures the following through the CLI of the Nexus 9000 switch while troubleshooting an unrelated issue: N9K# configure terminal N9K(config)# logging logfile messages 7 N9K(config)# end N9K# If this configuration is not manually reverted to the default value (logging level messages 5), then DCNM will incorrectly push the following configuration to the Nexus 9000 switch: no logging logfile messages 7 This disables the default syslog of the Nexus 9000 switch, which can be detrimental when troubleshooting future issues. Conditions: This issue is observed with Nexus 9000 switches managed by an instance of DCNM with the "Enable Strict Config Compliance" option configured on the fabric.
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