From: Jon Carmichael (jonc@xxxxxxxxxxx)
Date: Sun Oct 07 2001 - 19:27:38 GMT-3
The typical scenario where DLSW "cost" would come into play, is in the old
hub and spoke analogy, --where the two spokes happen to be sitting on the
same segment. Which one is the hub going to use?
You are correct that the lower cost is the preferred like a routing
protocol, however the difference is that a routing protocol metric for each
link is what a router will add to the metric for each route at each hop
along the way. In the case of DLSW, there is only one "hop." The default
cost is 3, --so when I set this, -I set one of the spokes to 4, and the
other to 2. In the case of DLSW, the spoke is telling the hub how much the
one hop is going to cost, --then the hub, when given a choice of two spokes
can make a choice of the least cost.
At the hub, --you should be able to do a "show dlsw capabilities" to see
what the spoke has set the cost to.
JCLab1-R3#sho dlsw capa
DLSw: Capabilities for peer 192.168.17.1(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
border peer capable : no
peer cost : 4
biu-segment configured : no
UDP Unicast support : yes
NetBIOS Namecache length : 15
local-ack configured : yes
priority configured : no
configured ip address : 192.168.17.1
peer type : prom
version string :
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS56I-L), Version 12.0(17), RELEASE SOFTWARE
(fc1)
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 16-Apr-01 19:05 by nmasa
DLSw: Capabilities for peer 192.168.17.2(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
border peer capable : no
peer cost : 2
biu-segment configured : no
UDP Unicast support : yes
NetBIOS Namecache length : 15
local-ack configured : yes
priority configured : no
configured ip address : 192.168.17.2
peer type : prom
version string :
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS56I-L), Version 12.0(17), RELEASE SOFTWARE
(fc1)
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 16-Apr-01 19:05 by nmasa
JCLab1-R3#
JONC
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Nicholas Jaksec
Sent: Friday, October 05, 2001 12:28 PM
To: CCIE
Subject: DLSW cost
I believe you can apply a cost parameter on a local peer and remote peer
statement. What does each one do:
1)If its applied to the local peer statement, is this value advertised to
all your remote peers ??
2)If its applied to the remote peer statements, is it only those specific
peers that get the advertised cost ??
3)Is the DLSW cost value work the same as routing protocols, the lower the
better (preferred) ??
Any reply would be appreciated !!
********************************************
Nicholas R. Jaksec, CCNP, CCDP, MCSE+I, CNA
Network Systems Engineer
Lucent Worldwide Services
One North Shore Center
12 Federal St. Suite 420
Pittsburgh, Pa 15212
Office: 412-330-6336 Fax: 412-323-7665
Pager: 1-800-467-1467
Email: jaksec@lucent.com
********************************************
Having trouble posting? Read:
http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:14 GMT-3