From: Jonathan V Hays (jhays@jtan.com)
Date: Fri Jul 25 2003 - 20:55:57 GMT-3
Yes, I agree that's what it does. And from my experiments it appears
that the default cost is 3.
But it is cost configured on the "dlsw local-peer" statement that is
advertised to the remote peer. The "dlsw remote-peer" cost doesn't show
up in the capabilities exchange.
R3:
dlsw local-peer peer-id 140.4.3.3 cost 2 promiscuous
R5:
r5#sh dlsw capabilities ip-address 140.4.3.3
DLSw: Capabilities for peer 140.4.3.3(2065)
vendor id (OUI) : '00C' (cisco)
version number : 2
release number : 0
init pacing window : 20
unsupported saps : none
num of tcp sessions : 1
loop prevent support : no
icanreach mac-exclusive : no
icanreach netbios-excl. : no
reachable mac addresses : 0cc0.0cc0.0000 <mask ffff.ffff.0000>
reachable netbios names : none
V2 multicast capable : yes
DLSw multicast address : none
cisco version number : 1
peer group number : 0
peer cluster support : no
border peer capable : no
peer cost : 2 <===========
biu-segment configured : no
UDP Unicast support : yes
Fast-switched HPR supp. : no
NetBIOS Namecache length : 15
local-ack configured : yes
priority configured : no
cisco RSVP support : no
configured ip address : 140.4.3.3
peer type : prom
version string :
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JOS56I-L), Version 12.1(19), RELEASE
SOFTWARE (fc1)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Tue 04-Mar-03 14:46 by kellythw
r5#
If I configure R5's "dlsw remote-peer" statement, it doesn't seem to
have any affect.
R5:
dlsw local-peer peer-id 140.4.5.5
dlsw remote-peer 0 tcp 140.4.3.3 cost 2
[I then do "dlsw disable" followed by "no dlsw disable" to restart the
process.]
R3:
r3#sh dlsw capabilities ip-address 140.4.5.5
DLSw: Capabilities for peer 140.4.5.5(2065)
vendor id (OUI) : '00C' (cisco)
version number : 2
release number : 0
init pacing window : 20
unsupported saps : none
num of tcp sessions : 1
loop prevent support : no
icanreach mac-exclusive : no
icanreach netbios-excl. : no
reachable mac addresses : none
reachable netbios names : none
V2 multicast capable : yes
DLSw multicast address : none
cisco version number : 1
peer group number : 0
peer cluster support : no
border peer capable : no
peer cost : 3 <========= no effect: default of 3
biu-segment configured : no
UDP Unicast support : yes
Fast-switched HPR supp. : no
NetBIOS Namecache length : 15
local-ack configured : yes
priority configured : no
cisco RSVP support : no
configured ip address : 140.4.5.5
peer type : conf
version string :
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JOS56I-L), Version 12.1(19), RELEASE
SOFTWARE (fc1)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Tue 04-Mar-03 14:46 by kellythw
r3#
I don't understand how to apply the "cost" parameter on the "dlsw
remote-peer" statement, but it seems that on the local-peer statement
the default is 3, and you can use it to influence the remote peer via
dlsw capabilities exchange. Perhaps you can set different costs on
remote-peer statements to prefer one over the other - if so, how do you
verify it?
I probably raised more questions than I answered here. ;-)
HTH,
Jonathan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Joe Martin
Sent: Friday, July 25, 2003 7:09 PM
To: CCIE GroupStudy
Subject: Default Cost for DLSW remote-peer?
Can anyone confirm that the default cost for a DLSW remote peer is 3?
Also, As I understand it, the cost is used to choose a DLSW peer to
forward
traffic to if more than one has reachability to the destination. Can
anyone
confirm or correct?
TIA,
Joe Martin
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:53 GMT-3