Match-any or Match All For Class-map On Nexus?

Answered Question
Oct 16th, 2014
User Badges:

  I have an access-list MANAGEMENT

        permit udp any eq snmp any
        permit udp any any eq snmp
        permit tcp any any eq telnet
        permit tcp any eq telnet any
       permit tcp any any eq 22
       permit tcp any eq 22 any
 

 

My question does it matter if I use a match-any or match-all. I want to match anything in the access-list to classify the traffic correctly

 class-map type qos match-any MANAGEMENT
            match access-group name MANAGEMENT

Or

class-map type qos match-all MANAGEMENT
            match access-group name MANAGEMENT

 

I understand a match-any is an or and a match-all is an and function. Does this apply to an access-list for  a class-map?

Thanks
 

Correct Answer by Jody Lemoine about 2 years 10 months ago

It applies to match statements within the class map. In your case, you're only using one match statement, so there will be no difference between match-all and match-any, no matter how many entries are in the ACL. If your class map had two different ACLs in two different match statements , then the and/or logic of match-all and match-any would come into play.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Jody Lemoine Thu, 10/16/2014 - 21:54
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Member's Choice, April 2016

It applies to match statements within the class map. In your case, you're only using one match statement, so there will be no difference between match-all and match-any, no matter how many entries are in the ACL. If your class map had two different ACLs in two different match statements , then the and/or logic of match-all and match-any would come into play.

 

Actions

This Discussion