> I've got some weird behavior here, maybe somebody can explain: Customer has a VSX cluster that we upgraded to R80.20 JHF 118 recently. After we upgraded, we noticed that fwaccel stat doesn't show the rule which disables templating any more.
Good, that means that the relaxing of the templating rules in R80.10+ via constructs such as NMR/NMT templates is allowing your entire rulebase to use Accept templates.
> I noticed that one vs has about 19% F2F traffic but no clue which rule is causing that.
Separate issue, status of SecureXL rule templating has no impact on SecureXL Throughput Acceleration (i.e. which path the traffic is processed in). Would need to see which blades are enabled in the VS with 19% F2F (command enabled_blades) to hazard a guess about that. Less than 10% F2F is generally OK though, so 19% F2F is not the end of the world and reducing it probably won't make a huge difference.
> Oh, I forgot: There is one vs where fwaccel stat states that templating is disabled by rule 650 but there are only 630 rules in that ruleset. This is the only vs in which fwaccel stat displays anything at all.
Is the VS being managed by an MDS? Are you using Global Rules and objects? That may account for the "extra" rules at the end. It sounds like templating is being stopped well past the end of your local rulebase, so resolving that once again probably won't make much difference. Also this SK is old but may be relevant to your situation: sk62323: Output of 'fwaccel stat' shows that SecureXL Accept Templates are disabled from rule, whose...