From: Nick Shah (nshah@xxxxxxxxxxxxxx)
Date: Tue Jul 02 2002 - 01:03:20 GMT-3
ok. lets go over this (I am not a ccie yet, but I will make a best effort in
explaining it)
* Step one is to specify "priority" keyword with the remote-peer statement.
This opens up 4 TCP connections (instead of 1, port 2065). It also
prioritizes basic traffic into 4 Queues. By basic traffic, I mean, DLSW
traffic like SSP frames, name queries etc. All of these are assigned
different Q's (check the url document as to which traffic is assigned what
priority)
* Step two is to specify your "own traffic" to be prioritized and assign to
appropriate TCP connection (out of the 4). This is done by SAP addr list,
mac addr. list or locaddr's. Now if you do just step 1, you are not Queuing
any of "your traffic" , but only dlsw traffic (explained above)
* Step 3 is to assign the different types of dlsw traffic (your traffic
which you have assigned to 4 different pipes) to the Queueing mechanism to
be handled. Now, over here you can use various types of Queuing (WFQ,
CUSTOMQ, PRIORITYQ).
However note that if you dont do step 1 & 2, you can just apply queueing
mechanism to SNA traffic (which is only port 2065 traffic) and other traffic
(which could be anything). But once you do step 1 & step 3, you now have the
power to control 4 "variants" of SNA traffic (SNA traffic divided into 4
queues) and you can specify priority to all the 4 "variants" of SNA traffic
by their port numbers.
If you choose to do step 1 &2 & 3(remember step 1 is important if you want
to do step 2). Then with step 2 you get even more control, because now you
can have "user traffic" based on SAP lists, mac lists etc. prioritized and
assigned to different priority Queues (these are DLSW Q's) and you end up
getting much finer control (total control over all type of SNA, netbios etc.
traffic)
Coming back to your questions ...
* priority keyword is needed to open up 4 TCP connections (or call them
Queues, but promise me that you wont get confused :)
* sap - priority lists are somewhat similar to extended access lists wherein
you specify source/destination address/port pairs to identify traffic flows.
These traffic flows are just identified here.
* once these traffic flows are identified, you have to assign them to
different Queues
* and sap priority lists are indeed applied on interfaces for "seperating
traffic" so in reality they have nothing to do with remote-peer (meaning,
traffic is not actually denied or permitted)
hth
Nick
----- Original Message -----
From: "elping" <elpingu@acedsl.com>
To: "Nick Shah" <nshah@connect.com.au>
Cc: <ccielab@groupstudy.com>
Sent: Tuesday, July 02, 2002 1:37 PM
Subject: Re: dlsw priority
> no nick....i read the document ...
> see I am not a ccie yet ....so I do know nothing >: 0
> that is whay i am asking if the stament I made are true....those were my
> conclusions .
>
> just asking for some clarification.......
>
>
>
>
>
> Nick Shah wrote:
>
> > Mate,
> >
> > This url explains what you are lookign for best... I dont think I will
be
> > able to explain it better than this doc :)
> >
> >
http://www.cisco.com/warp/customer/cc/pd/ibsw/ibdlsw/prodlit/dlsw5_rg.htm
> >
> > rgds
> > Nick
> > ----- Original Message -----
> > From: "elping" <elpingu@acedsl.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Monday, July 01, 2002 4:06 PM
> > Subject: dlsw priority
> >
> > > just some clarification:
> > > are the statement below true
> > >
> > > dlsw priority on the remote peer command works in conjuntion with
custom
> > > queing.?
> > >
> > >
> > > ssap priority list must be aplied to nterfaces and do not work with
the
> > > dlsw remote peer command?
> > >
> > > any help apreciated......
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:17 GMT-3