From: Rob Webber (rwebber@xxxxxxxxxxxx)
Date: Thu Feb 01 2001 - 14:35:39 GMT-3
I believe cost on the local peer statement (cost keyword) is the cost you
advertise out to your peers. The remote peer statement (cost keyword) is the
cost of reaching that remote peer. This basically let's you override the
cost they are advertising to you.
I'm not sure if the "peer cost" in the show dlsw cap is the cost that peer
is advertising to you, or the cost you manually set with the remote peer
statement. My guess would be the former...?
Rob.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
omoruyi usuanlele
Sent: Thursday, February 01, 2001 3:03 AM
To: Devender Singh; Ccielab@Groupstudy. Com (E-mail)
Subject: Re: more DLSW question
The cost keyword on the remote-peer command is the
cost the local router is advertising to the remote
peer, hence it is possible to advertise different cost
to different peers.
To confirm that the cost actually changed, you have to
check the remote router. sh dlsw capa on the remote
router will show the cost that it is recieving from
R4.
Cheers//
Omoruyi
--- Devender Singh <devender.singh@cmc.cwo.net.au>
wrote:
> Question 1: Ring list. My book shows ring included
> in ring list command as
> directly attached rings to the router. But can we
> include rings that are not
> directly connected.
>
> Question 2: In "dlsw icanreach" command if we define
> a mac-address without
> the mask, it defaults to ffff.ffff.ffff, which in
> common sense I would say
> will point to only one host. But documentation says
> that f means don't care,
> which would mean every possible host. This doen't
> make much sense to me. Can
> someone enlighten me on this one.
>
> Question 3: When I change cost to a remote peer, how
> do I confirm the cost.
> because " sh dlsw capa " keeps on showing default
> cost. Or m I missing
> something here
>
> !
> source-bridge ring-group 10
> dlsw local-peer peer-id 4.4.4.4 passive
> dlsw ring-list 1 rings 100
> dlsw remote-peer 1 tcp 1.1.1.1 cost 2
> dlsw remote-peer 1 tcp 3.3.3.3 cost 4
> !
> ****************
> r4#sh dlsw capa
> DLSw: Capabilities for peer 1.1.1.1(2065)
> vendor id (OUI) : '00C' (cisco)
> version number : 2
> release number : 0
> border peer capable : no
> peer cost : 3 <------- Cost shows
> up as
> default value
> UDP Unicast support : yes
> Fast-switched HPR supp. : no
> local-ack configured : yes
> priority configured : no
> cisco RSVP support : no
> configured ip address : 1.1.1.1
> peer type : conf
> version string :
> Cisco Inte
>
> DLSw: Capabilities for peer 3.3.3.3(2065)
> vendor id (OUI) : '00C' (cisco)
> V2 multicast capable : yes
> peer cost : 3 <------- Cost shows
> up as
> default value
> biu-segment configured : no
> UDP Unicast support : yes
> Fast-switched HPR supp. : no
> local-ack configured : yes
> priority configured : no
> cisco RSVP support : no
> configured ip address : 3.3.3.3
> peer type : conf
> version string :
>
******************************************************
>
> Devender Singh
> BE(Hons), CCNP
> IP Solution Specialist
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:33 GMT-3