From: Edmund Roche-Kelly (edr9007@xxxxxxx)
Date: Sun Jun 23 2002 - 16:38:06 GMT-3
The cost in the local peer statement is the cost you advertise to
remote peers. The cost on a remote peer statement sets that peers
cost, and overrides the cost you receive from a remote peer. So
if peer 172.14.7.7 below was sending you a cost of 4, you'd ignore
it and assign 5 to the peer.
Note that if you do show dlsw capabilities for that peer, you'll
see the cost the peer advertised, not the cost you set.
Ed
elping <elpingu@acedsl.com> wrote:
>to the dlsw gurus:
>
>I have noticed that i can influence the cost via the cost via the local
>peer command and the cost to this peer will be relayed to the remote
>peer ..and i will see the cost reflected in the sho capabilities .
>
>example:
>dlsw local-peer peer-id 172.14.8.8 cost 1 promiscuous
>
>but in a configuration as the one below
>
>dlsw local-peer peer-id 172.14.2.2 promiscuous
>dlsw remote-peer 0 tcp 172.14.8.8 cost 1
>dlsw remote-peer 0 tcp 172.14.7.7 cost 5
>
>does this state anything from this router will prefer the dlsw
>coonection to 172.14.1.1...
>in the remote peers I do not see the cost in the sho dlsw
>capabilities....
>
>is the below statement true
>influencing paths in dlsw can be made though local peer and remote peer
>statments .. ?
>
>now I will say it is true but due to i connot see it in the capabilities
>when i use it on a remote peer statement . I am questioning It...
>
>El ping
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:40 GMT-3