Time Range and QOS

From: Angelo De Guzman (a.deguzman@wesolv.ph.fujitsu.com)
Date: Fri Sep 15 2006 - 05:48:00 ART


Hi All,
   The link between R2 and R5 (Serial) must place all WEB traffic into a
priority queue allowing FULL BW between 6PM and 8AM on weekdays. Outside of
this time all web traffic must be treated as best effort.

My Answers
1.
!---> covers 12:OO midnight to 7:59 AM and 6PM to 12Midnight
time-range HIGH_WWW
 periodic weekdays 18:00 to 23:59
 periodic weekdays 0:00 to 7:59
!---> covers time from 8:00 AM to 6PM where WWW and probably others would be
treated as best effort
time-range LOW_WWW_ANY
 periodic weekdays 8:00 to 17:59
 periodic weekend 0:00 to 23:59
!
access-list 101 permit tcp any any eq www time-range HIGH_WWW
access-list 102 permit ip any any time-range LOW_WWW_ANY
priority-list 1 protocol ip high list 101
priority-list 2 protocol ip normal list 102 <--- i dont know if this is Best
Effort in priority-queue

2.
access-list 101 permit tcp any any eq www time-range HIGH_WWW
!
class-map match-all HIGH_WWW
 match access-group 101
class-map match-all BestEffort
 match not access-group 101
!
!
policy-map LOW_BW
 class BestEffort
   police 8000 < ---- some action that I just made up for the "best Effort" but
I dont know if correct.
policy-map R2_R5
 class HIGH_WWW
  priority percent 100 <---- if it is www and okays time range then it is
prioritized
 class class-default
  service-policy LOW_BW

int s0/0/1
 service-policy output R2_R5

1. Which is better solution?
2. Is # 2 a valid logic?
2. Is there a default queueing or action for the default class?
 Your thoughts please and corrections.

TIA

***********************
No virus was detected in the attachment no filename

Your mail has been scanned by InterScan MSS.
***********-***********



This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART