From: Chris McCoy (mccoy-cm@pacbell.net)
Date: Sun Jun 15 2003 - 16:55:14 GMT-3
Oliver,
From my experience, any DLSW protocols listed in priority-lists or
queue-lists are for "direct" encapsulations only. These are where you
specify a serial interface and/or frame-relay DLCIs in your remote-peer
statements. So use the TCP ports if that's what you're using for your
peers. I definitely know the "match protocol dlsw" in the Modular QoS
CLI (MQC - class-maps) is for direct encapsulations and won't pick up
TCP port 2065. I don't think DLSW+ lite even matches either, since it
is llc2, although I could be wrong. Try turning off CEF/fast-switching
and issue a "debug priority" or a "debug custom" to watch how a packet
is queued. If you need to pick up DLSW+ with NBAR, use a custom
protocol with TCP port 2065, just remember that NBAR
_never_ works on any packets sourced by the router, since they are
process switched, and not CEF switched.
Hope this helps you! Best of luck!
Chris McCoy, #11801
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Oliver Ziltener
Sent: Sunday, June 15, 2003 10:59 AM
To: Oliver Ziltener; ccielab@groupstudy.com
Subject: AW: dlsw and priority-list (still waiting....)
Hope somebody help me in this....
-----Urspr|ngliche Nachricht-----
Von: Oliver Ziltener
Gesendet: Samstag, 14. Juni 2003 17:39
An: ccielab@groupstudy.com
Cc: Oliver Ziltener
Betreff: dlsw and priority-list
When I use PQ and I should give DLSW+ the highest level
should I do this
priority-list 1 protocol ip high tcp 2065
or
priority-list 1 protocol dlsw high
Or does both the same?
Is the first statement only for TCP encapsultation and the second for
dlsw+ lite (llc2)
thanks for the feedback
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:58 GMT-3