We hit today the same bug #CSCvn18256, but different "command":
RBK-SW-CO-DC#sh redundancy config-sync failures mcl
Mismatched Command List
-----------------------
-monitor session 1 source Po40 , Po41 , Po42 , Po43 , Po44 , Po45 , Po46 , Po47 , Po48 , Po53 , Po54 , Po100 rx
our configuration connected to this "mismatched command" is:
monitor session 1 source interface Po13 , Po21 , Po22 , Po23 , Po24 , Po25 , Po26 , Po27 , Po28 , Po29 , Po30 , Po31 , Po32 , Po33 , Po34 , Po35 , Po36 , Po37 , Po38 , Po39 rx
monitor session 1 source Po40 , Po41 , Po42 , Po43 , Po44 , Po45 , Po46 , Po47 , Po48 , Po53 , Po54 , Po100 rx
monitor session 1 destination interface Te1/1/2
monitor session 1 filter packet-type good rx
As you can see, keyword "interface" is missing and this is the trigger point that hits the bug.
Workaround (in our case):
- remove monitor session 1 completely (from active VSS member)
- it is not removed from standby member, because stb device was not able to boot after power outage (it is rebooting in loop)
How to solve this situation? We had two possibilities:
1. boot stb box with no connection (pull out all data/vsl/dad cables). Remove misconfiguration, save and reboot with connected ethernet cables. Too much work, because lot of connected cables in chassis.
2. 'redundancy config-sync ignore mismatched-commands' command is your friend :). but! this command is possible to use only if both VSS members are in "VSS connection". In other words, during stb booting you must check situation if VSS members are connected ('show redundancy') and paste command. time slot for this is around 1 sec! After this, stbd member can join VSS ane everything is working!
Maybe helps somebody.
Martin
