From: Geert Nijs (geert.nijs@simac.be)
Date: Wed Jul 28 2004 - 08:51:59 GMT-3
Simple,
What if you would like to SET ip precedence or something else in a WHOLE VLAN ???
You will have to set it on ALL access ports of that VLAN, and also on the trunk ports (where you would be
need to filter on VLAN ID).
An access port is also an entry port for VLAN traffic, just as is a trunk port....
The problem I am having with this is, that you can`t apply it on a vlan interface.
So what about marking packets that are entering my vlan via the VLAN interface (routed packets) ???????
Any ideas ?
Regards,
Geert
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Pierre-Alex Guanel
Sent: woensdag 28 juli 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:04 GMT-3