From: Richard Dumoulin (richard.dumoulin@vanco.es)
Date: Wed Jul 28 2004 - 18:58:44 GMT-3
Well, it makes sense if you create only one policy-map and apply the same
policy-map to access ports and trunks !!
The alternative would be to create one policy-map for the access ports and
one per port per vlan policy-map for the trunks but then you would have
doubled the effort :)
--Richard
-----Original Message-----
From: Pierre-Alex Guanel [mailto:pierreg@planetkc.com]
Sent: miircoles, 28 de julio de 2004 13:25
To: Ccielab@Groupstudy.Com
Subject: Qo 3550: Per-port per-VLAN classification
FROM CISCO DOCUMENTATION:
" 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. "
This will match traffic from vlan 10, 20-30- and 40 with a DSCP of 9
Switch(config)# class-map match-any dscp_class
Switch(config-cmap)# match ip dscp 9
Switch(config-cmap)# exit
Switch(config)# class-map match-all vlan_class
Switch(config-cmap)# match vlan 10 20-30 40
Switch(config-cmap)# match class-map dscp_class
Switch(config-cmap)# exit
QUESTION: how could you possibly receive traffic from VLAN 10, 20 etc.. on
an access-port !!!!!!????
Per-port per-VLAN classification only make sense on a TRUNK, but Cisco
says that it works also on an access-port.
Can someone please shed some light with an exemple where doing this on an
access-port would make sense?
Thanks,
Pierre
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:12:05 GMT-3