class-map match-any vs match-all

[Martin Kyrc]

Hello,

is there any performance difference between match-all and match-any criteria inside class-map definition?

http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA5_1_0/command/reference/classmap.html#wp1281832

I have this question, because when I use L4 criteria only is better to use 'match-any' match criteria regards future changes. The reason is: when I need change 'match virtual-address' criteria inside class-map I can add new VIP and remove old VIP address (ther can exists more virtual-address match criteria). But when is used match-all, it is not possible add new VIP (ther can exists only one virtual-address criteria) and it is not possible remove old VIP criteria without removing class-map from service-policy definition. That means, there is more work whan I need change VIP address for existing class-map.

--

martin

[Jorge Bejarano · Accepted solution]

Hello Martin,

Basically, there´s no a technically performance difference between match-all and match-any criteria inside class-map definition.

As you said, if you plan to apply changes eventually in the future, then it is better to configure  match-any since it is easier and faster to be edited. On the other hand, as you also mentioned, for match-all, this might be a "pain" sometimes, since you might have to follow a path just to apply just some  little changes which might take more time that match-any.

Now, if you are trying to have a method to match in an "AND" way then you need to use a match-all to make sure, all the criteria will be matched but if you just want to match anything (kind of "OR") , then you can configure match-any.

Match-all is like a checklist, where you need to "mark" everything to work playing.

Match-any is more relaxed, "just match something and I let you go".

Again, in relation to your original, there´s no improvement to use one or the other, just depends on what you need them for.

Jorge