Custom Queuing for DLSW -- Turing on DSLW priority

From: Jeongwoo Park (jpark@wams.com)
Date: Tue Apr 15 2003 - 04:22:03 GMT-3

• Next message: bobby: "Reg: RSVP & CBWFQ"
• Previous message: Joe Chang: "Re: STOP ASKING LAB QUESTIONS"
• Next in thread: Joe Chang: "Re: Custom Queuing for DLSW -- Turing on DSLW priority"
• Maybe reply: Joe Chang: "Re: Custom Queuing for DLSW -- Turing on DSLW priority"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi, all.
I know there were a discussion on C.Q for DLSW in the past.
Quote from the past thread;
access-list 101 permit tcp any eq 2065 any

access-list 101 permit tcp any any eq 2065

access-list 101 permit tcp any any eq 2067

access-list 101 permit tcp any any eq 1981

access-list 101 permit tcp any any eq 1982

access-list 101 permit tcp any any eq 1983

queue-list 1 protocol ip 1 list 101

Now in order to use the below ACL..

access-list 101 permit tcp any any eq 1981

access-list 101 permit tcp any any eq 1982

access-list 101 permit tcp any any eq 1983..

I was told that DLSW priority should be turned on.

So, I tried to turn on DLSW priority by doing;

r4(config)#dlsw remote-peer 1 tcp 120.20.35.3 priority
%port-list 1 does not exist.

As you can see I got this error.

What am I missing here? Should I have Priority Queue configured before I
turn on DLSW priority?

Thanks,

JP

• Next message: bobby: "Reg: RSVP & CBWFQ"
• Previous message: Joe Chang: "Re: STOP ASKING LAB QUESTIONS"
• Next in thread: Joe Chang: "Re: Custom Queuing for DLSW -- Turing on DSLW priority"
• Maybe reply: Joe Chang: "Re: Custom Queuing for DLSW -- Turing on DSLW priority"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:52 GMT-3