Hi, I will test this in the lab, thanks Xander!
Do you know in what version this can be fixed and is it affecting 5500 or just 55A1?//Jonas
hi jonas, this is applicable to all ncs55, it was meant to be fixed in 652, but apparently there is a side-effect to it.
hence that tech qos may be useful to see if there is a limitation or a side effect that needs to be addressed.
that also if the workaround is unusable :)
thanks, ill go for the option to use the class-default and set TC/IPPrec until this is fixed
a little bit tricky to create any any for ipv4 and ipv6 plus I need to change it back when the bug is fixed
I will go for the workaround using class-default until the bug is fixed, instead of reconfiguring the ACL's (ipv4 and ipv6)
also when the bug is fixed I don not necessary need to change it back if its class-default