DLSW Custom Queueing

From: Lance (lance@xxxxxxxxxxxxx)
Date: Sat May 18 2002 - 18:01:05 GMT-3

• Next message: cash2001: "Voice lab from All-in-OneCisco CCIE"
• Previous message: Jonathan Hays: "RE: Two Default Routes which path?"
• Next in thread: Sasa Milic: "Re: DLSW Custom Queueing"
• Maybe reply: Sasa Milic: "Re: DLSW Custom Queueing"
• Maybe reply: Bauer, Rick: "RE: DLSW Custom Queueing"
• Maybe reply: Sasa Milic: "Re: DLSW Custom Queueing"
• Maybe reply: Bauer, Rick: "RE: DLSW Custom Queueing"
• Maybe reply: Sasa Milic: "Re: DLSW Custom Queueing"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

   
I have seen many posts regarding the access-list needed to capture DLSW
packets,however there is the option of specifying dlsw as the protocol within
the custom que list defenition. such as:

queue-list 1 protocol dlsw 3

is there a reason that you would want to use an access-list to identify the
dlsw packets instead of using the above mentioned command??

Thanks
  Lance

• Next message: cash2001: "Voice lab from All-in-OneCisco CCIE"
• Previous message: Jonathan Hays: "RE: Two Default Routes which path?"
• Next in thread: Sasa Milic: "Re: DLSW Custom Queueing"
• Maybe reply: Sasa Milic: "Re: DLSW Custom Queueing"
• Maybe reply: Bauer, Rick: "RE: DLSW Custom Queueing"
• Maybe reply: Sasa Milic: "Re: DLSW Custom Queueing"
• Maybe reply: Bauer, Rick: "RE: DLSW Custom Queueing"
• Maybe reply: Sasa Milic: "Re: DLSW Custom Queueing"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:00 GMT-3