From: Marvin Greenlee (mgreenlee@ipexpert.com)
Date: Sun Jul 13 2008 - 11:09:56 ART
Match traffic
Class ftp
Match prot ftp
Class telnet
Match prot telnet
Etc...
A few potential snags:
Can't directly use match prot dns, as it would match both tcp and udp for
port 53, recommend creating a custom, or using an ACL.
From what I recall, 'protocol dlsw' was used for direct encapsulation, not
for the (tcp session on port 2065 ) type of DLSW traffic, so not something
that is easily matched in an ACL. Someone correct me if I'm wrong on that
point, I have purged most of my DLSW memory, due to lack of need for it.
I'm pretty sure the last time I "decoded a RIF" was on a written test 5
years ago.
Also on a similar note, there is mention in the cisco docs that "For some
protocols, such as TFTP and FTP, only the initial request uses port 69.
Subsequent packets use a randomly chosen port number. For these types of
protocols, the use of port numbers fails to be an effective method to manage
queued traffic." Therefore, the use of an ACL matching tcp port 21 may more
closely correspond to the behavior seen with the custom queue list.
Assigning bandwidth - total up the queues.
FTP 1000/(3000+1000+800+5000+100) = 1000/9900 or ~10.1 %
telnet 3000/9900 or ~30.3%
DNS 800/9900 or ~8.08%
Etc.
For the scope of the lab, if you get asked a question and the numbers don't
come out to nice, whole number values, you are usually missing a queue
somewhere or did some math wrong.
You could also configure the queue limits for each class or confirm that
leaving at the default is OK. CQ defaults to 20, CBWFQ defaults to 64.
Marvin Greenlee, CCIE #12237 (R&S, SP, Sec)
Senior Technical Instructor - IPexpert, Inc.
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
Mailto: mgreenlee@ipexpert.com
Progress or excuses, which one are you making?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of ccie
Sent: Sunday, July 13, 2008 9:35 AM
To: ccielab@groupstudy.com
Subject: converting custom queuing to MQC
Hi Experts,
Could someone help my in converging this custom queuing to MQC with
clarification for that
Queue-list 1 protocol ip 1 tcp telnet
Queue-list 1 protocol ip 2 tcp ftp
Queue-list 1 protocol ip 3 udp dns
Queue-list 1 protocol ip 4 dlsw
Queue-list 1 protocol ip 5 default
Queue-list 1 protocol ip 1 byte-count 3000
Queue-list 1 protocol ip 2 byte-count 1000
Queue-list 1 protocol ip 3 byte-count 800
Queue-list 1 protocol ip 4 byte-count 5000
Queue-list 1 protocol ip 5 byte-count 100
Regards,
Amin
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:54 ART