From: Lekan Magbagbeola (lekkyl@xxxxxxxxxxx)
Date: Wed Jul 17 2002 - 03:14:05 GMT-3
Ping,
Here is my thought on dlsw cost...
In a situation where you have two links going from say router R1 to
routers R2 and R3 and you are faced with two tasks:
1. Prefer link to R2 to access say, resource A and use link via R3 when
link via R2 goes down. Both links must stay connecetd while this
requirement is met.
2. Equally Load balance traffic between links via R2 and R3 from R1 to
acess the same resource.
In the first scenario, you can set the cost from both R2 and and R3 in
their local peer statement with R2 having a lower cost. Thess will be
exchanged during capability exchange with R1. In the alternative, you can
set the cost in the remote statement on R1 to both R2 and R3 with R2
having a lower cost. The second option allows the network administrator
of R1 to have more control over the choice of path. Nevertheless, your
choice depends on what other requirements you must meet in your dlsw
peering.
I would say the first scenario is the converse of dlsw backup scenario.
In the second scenario, you set equal cost to go through links R2 and R3.
Nonetheless, you may also achieve second scenario with dlsw load balance
circuit-count statement on R1 and set equal circuit-weight in the remote
statements to R2 and R3 on R1.
My thought on dlsw priority...
DLSw+ places all SNA and NetBIOS traffic into TCP packets, making it
difficult or impossible to identify the traffic by TCP port #s, LLC SAP,
protocol, etc. So in other to distinguish between DLSw traffic, you
use dlsw priority in the remote statement and this creates four
different TCP ports (2065, 1981, 1982, and 1983) for all DLSW traffic.
This allows you to classify the dlsw traffic and place them in different
TCP connection. Then ultimately, you assign each TCP onto different queue
on the output interface.
I would suggest you read more from the DLSW design guide on CCO.
I hope this helps!
Lekan
>From: Ping Pong >Reply-To: Ping Pong >To: ccielab@groupstudy.com
>Subject: dlsw cost and priority >Date: Tue, 16 Jul 2002 13:37:37 -0700
(PDT) > >Hi.. > >I am struggling to find a proper usage for dlsw cost
>and dlsw priority commands.Can someone explain me?. > >Thanks. > >Ping >
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:33 GMT-3