From: Sean C. (Upp_and_Upp@xxxxxxxxxxx)
Date: Tue Mar 12 2002 - 22:32:08 GMT-3
Hi Nic,
Hmmm..., I see how you're trying to grab dlsw first and put it into queue 3.
I've never tried it that way.
I 've used this config from a commercial lab for dlsw and queueing and it
has worked:
queue-list 1 protocol ip 1 list 101
queue-list 1 protocol ip 2
queue-list 1 protocol ipx 3
queue-list 1 queue 1 byte-count 2048
queue-list 1 queue 2 byte-count 1024
queue-list 1 queue 3 byte-count 1024
acl 101 permit tcp any eq 2062 any
acl 101 permit tcp any any eq 2065
acl 101 permit tcp any any eq 2067
acl 101 permit tcp any any eq 1981
acl 101 permit tcp any any eq 1982
acl 101 permit tcp any any eq 1983
HTH,
Sean
----- Original Message -----
From: "Nicolai Gersbo Solling" <nicolai@cisco.com>
To: "CCIE Lab" <ccielab@groupstudy.com>
Sent: Tuesday, March 12, 2002 9:51 AM
Subject: Custom Q list
Hi there!
I have the followingf queue list configured:
queue-list 1 protocol dlsw 3
queue-list 1 protocol ip 1
queue-list 1 protocol ipx 2
queue-list 1 queue 1 byte-count 1150
queue-list 1 queue 2 byte-count 2300
queue-list 1 queue 3 byte-count 2296
this is apllied to my serial 0:1 interface - I see the IP and IPX packets
beeing put in the right queue, but the DLSW queue never get's used!
My DLSW configuration is working fine , henci I have some windows 95
machines broadcasting their netbios names on the network, which is beeing
seen under DLSW reachability on the remote DLSW peer!
Any ideas?
Nic
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:02 GMT-3