Symptom

Cat9K stack - We may see standby reloads due to config-sync failure while adding/removing ingress QOS service-policy at certain conditions. The issue is seen on 16.11.1C but it might be seen on other main releases as well. As long as manual configuration of service-policy is done on a port where same policy was once pushed by a dynamic template/ISE, the config-sync failure is seen consistently and the reload triggers while removing that ingress QOS policy from the port. *Dec 10 19:51:11.684: Config Sync: Line-by-Line sync verifying failure on command: no service-policy input MARKING_IN due to parser return error *Dec 10 19:51:11.823: %RF-5-RF_RELOAD: Peer reload. Reason: Configuration mismatch *Dec 10 19:51:12.480: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT) *Dec 10 19:51:12.481: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN) *Dec 10 19:51:12.481: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE) *Dec 10 19:51:12.564: %SMART_LIC-5-EVAL_START: Entering evaluation period *Dec 10 19:51:12.565: %SMART_LIC-5-EVAL_START: Entering evaluation period *Dec 10 19:51:12.569: %HMANRP-5-CHASSIS_DOWN_EVENT: Chassis 1 gone DOWN! *Dec 10 19:51:12.701: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down

Conditions

As long as manual configuration of service-policy is done on a port where same policy was once pushed by a dynamic template/ISE, I see the config-sync issue consistently while removing that ingress QOS policy.

Workaround

Further Problem Description