match traffic of vlan 10

Unanswered Question
Feb 19th, 2008
User Badges:
  • Silver, 250 points or more

i want to match the traffic of vlan 10 and set its ip precedence to 3.

I am doing this way but switch is not accepting it.

class-map abc

match vlan 12

policy-map pabc

class abc

set ip prec 3

It is not accepting by the 3560 switch. If i make a access-list and bind it with the class and then that class is bind again in the policy-map with the existing class then it works. Please send your comments



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
lamav Tue, 02/19/2008 - 13:33
User Badges:
  • Blue, 1500 points or more

Are you trying to match vlan 10 or vlan 12?

Is this a typo? If so, is it a typo you made just on this forum or is it on the switch also?

Also, use these guidelines when matching vlan traffic:

Classifying Traffic on a Per-Port Per-VLAN Basis by Using Class Maps You use the class-map global configuration command to name and to isolate a specific traffic flow (or class) from all other traffic. To further classify the traffic flow, the class map defines the matching criteria to use.

To define packet classification on a per-port per-VLAN basis, follow these guidelines:

• You must use the match-all keyword with the class-map global configuration command.

• Per-port per-VLAN classification is a per-port feature and does not work on redundant links. It is supported only on an ingress port configured as a trunk or as a static-access port.

• The class map must have two match commands in this order: one match vlan vlan-list class-map configuration command and one match class-map class-map-name class-map configuration command. The class map specified in the match class-map class-map-name command must be predefined and cannot contain the match vlan vlan-list and the match class-map class-map-name commands.

• You cannot configure both port-based classification and VLAN-based classification at the same time. When you configure the match vlan vlan-list command, the class map becomes per-port per-VLAN based. If you configure a policy map that contains both port-based and VLAN-based class maps, the switch rejects the policy map when you attach it to an interface.

• With per-port per-VLAN classification, unmatched VLANs are treated similarly to the default class, which means that the unmatched VLANs share the remaining bandwidth from those used by the matched VLAN classes. You cannot modify this default-class behavior. If necessary, you can use

VLAN map filters to block these VLANs.

• Within a policy map, when you use the match vlan vlan-list command, all other class maps must use the match vlan vlan-list command.

• If you want to modify the VLAN list, first remove the previous configuration in the class map by using the no match vlan vlan-list command and the no match class-map class-map-name command. Then reconfigure the class map, and specify the new VLAN list. If the policy map is attached to an interface and you modify the class map by using any other method, the policy map detaches from the interface.




This Discussion