...
ACL access-group config on MgmtEth interface on standby is lost after device reload: interface MgmtEth0/RP1/CPU0/0 ipv4 access-group lost_acl ingress <-- missing config
Issue has been spotted after 2 device reloads. After 1st reload, following logs are visible in the syslog: RP/0/RP1/CPU0:Sep 24 21:36:31.955 UTC: cfgmgr-rp[177]: %MGBL-CONFIG-4-FAILED : Some 'MgmtEth0_RP1_CPU0_0' Configuration could not be restored by Configuration Manager. To view failed config(s) use the command - 'show configuration failed startup' RP/0/RP1/CPU0:Sep 24 21:36:31.960 UTC: cfgmgr-rp[177]: %MGBL-CONFIG-3-INCONSISTENCY_ALARM : A configuration inconsistency alarm has been raised. Configuration commits will be blocked until 'clear configuration inconsistency' command has been run to synchronize persistent configuration with running configuration. [...] RP/0/RP0/CPU0:Sep 24 21:36:32.973 UTC: cfgmgr-rp[279]: %MGBL-CONFIG-3-STARTUP : Configuration Manager will attempt to retry failed startup configuration in 25 seconds RP/0/RP1/CPU0:Sep 24 21:36:35.818 UTC: ifmgr[366]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RP1/CPU0/0, changed state to Up RP/0/RP0/CPU0:Sep 24 21:36:41.849 UTC: rmf_svr[205]: %PKT_INFRA-FM-3-FAULT_MAJOR : ALARM_MAJOR :RP-RED-LOST-NSRNR :CLEAR :0/RP0/CPU0: RP/0/RP0/CPU0:Sep 24 21:36:44.570 UTC: cfgmgr_cfs_check[67993]: %MGBL-CONFIG-3-INCONSISTENCY_ALARM : A configuration inconsistency alarm has been cleared. Configuration commits within this SDR are no longer blocked. RP/0/RP0/CPU0:Sep 24 21:36:58.383 UTC: cfgmgr-rp[279]: %MGBL-CONFIG-3-STARTUP : Configuration Manager successfully retried failed configuration
NA
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.