From: Bill Dicks (wdicks@xxxxxxxxxxxxxxxxxx)
Date: Tue Jul 25 2000 - 12:10:27 GMT-3
What's probably happening is that R2 is returning the explorer packets
significantly earlier than R1, so even though the costs are different, it
uses the first response. Set the "dlsw timer explorer-wait-time" to several
seconds, maybe even as high as 5 secs and this should solve your problem.
This will cause the router to wait X number of seconds before it chooses a
peer for the resource. This command is available starting in 11.3
Bill
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jansen
Sent: Tuesday, July 25, 2000 1:29 AM
To: ccielab
Subject: dlsw question,pls.
Hi,
For r4, I have two dlsw peers r1 and r2, the reachability to a
ethernet of r1 and r2 is the same,such like:
PC-SERVER FOUND REMOTE 1.1.1.1(2065)---------->r1
2.2.2.2(2065)------------>r2
but peer cost to r1 is 1,and peer cost to r2 is 5.
In my opinion, circuit should be
established between r4 and r1,when i use netbios to test the reachability
from r4,but
the circuit is established between r4 and r2,why?
r4#show dlsw circuit detail
Index local addr(lsap) remote addr(dsap) state uptime
1610612771 0003.3001.18cf(F0) 0005.93c1.44b4(F0) CONNECTED
00:00:48
PCEP: 9DC644 UCEP: 9EE730
Port:TB1 peer 2.2.2.2(2065)
Flow-Control-Tx CW:20, Permitted:34; Rx CW:20, Granted:21; Op:
Repeat
Congestion: Low(02), Flow Op: Half: 0/0 Reset 0/0
RIF = --no rif--
Total number of circuits connected: 1
Jansen
jysh@teamsun.com.cn
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:58 GMT-3