I noticed something odd after upgrading to 7.19.2 - in winbox switch port for rules using redirect-to-cpu action all showed up as unknown, via ssh, printing the rule shows *FFFFFFFF for the port. - This is on a CCR2216
I tried testing the same rule using every other action than redirect-to-cpu and port shows up correctly.
Testing on a CSR317 and CSR305 - all ports wired to switch chip no longer respond, the only way I can recover is to use console port and remove the rule on CSR317, and CSR305 only netinstall was possible.
On devices using 7.19 - this issue isnt observed, so its either 7.19.1 or 7.19.2 change that breaks this. I already opened a support case, but figured I’d start a thread as well to hopefully help someone avoid an unnecessary netinstall
Also if you have 7.19 and upgrade to 7.19.2 - the switch will be in the same broken state as mentioned above. Only RDS2216, CCR2116 and CCR2216 seem to stay responsive, though the rule most of the time is ignored when matching traffic passes the device.
Example of a rule:
on 7.19:
/interface/ethernet/switch/rule/add switch=switch1 ports=sfp-sfpplus1 vlan-id=6 redirect-to-cpu=yes
/interface/ethernet/switch/rule/print
Flags: X - disabled, I - invalid; D - dynamic
0 switch=switch1 ports=sfp-sfpplus1 vlan-id=6 copy-to-cpu=no
redirect-to-cpu=yes mirror=no
/interface/ethernet/switch/rule/export
/interface ethernet switch rule
add ports=sfp-sfpplus1 redirect-to-cpu=yes switch=switch1 vlan-id=6