From: Chris Lewis (chrlewiscsco@yahoo.com)
Date: Wed Nov 30 2005 - 14:44:31 GMT-3
Good point, with a voice vlan on an access port it would also make sense.
I agree, to get per port per vlan working you need hierarchy of some kind, the following is an example.
class-map match-any dscp_class
match ip dscp 9
exit
class-map match-all vlan_class
match vlan 10 20-30 40
match class-map dscp_class
exit
"HIERS, DAVID (AIT)" <dh4578@sbc.com> wrote:
Per-port/per-vlan is required on the trunk-like-access-ish port that is connected to the typical ip-phone/pc combo.
According to one book, a nested class structure is required to make Per-port/per-vlan work on a 3550.
David Hiers
CCIE 10734, CISSP
-###-
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Chris Lewis
Sent: Tuesday, November 29, 2005 1:05 PM
To: Venkataramanaiah.R; Cisco certification
Subject: Re: Per Port Per Vlan..
It is perfectly reasonable to configure parent/child class maps for an access port, something like shaping the output to an overall rate, then providing differentiated guarantees for different traffic types within that shaped rate.
Per port per vlan configurations are applied on trunk ports, not access ports.
"Venkataramanaiah.R" wrote:
Hi,
i would like to know whether it makes any sense to configure the
parent/child class maps for an access port, if we want to just
classify some traffic on the given access port.
My understanding is that per port/per vlan applies only to the trunk
ports.. Correct me if i am wrong.
Regards
-Venkat
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:08 GMT-3