CISCO'S ANSWER: --------------- >peer-on-demand defaults does not change what we learn from the peer during CapEx. We have learned the default cost >value from the remote, which is 3 - and that is what we show in 'sh dls cap'. However, the value configured on peer-on- >demand defaults (5) overrides this operationally. So even though the capabilities reported a value of 3, the value >that is actually being used is 5. > >Unfortunately, other than the config there is no show command that shows the operational cost value of the peer. > > - Scott
PROBLEM/ISSUE: -------------- i have the following config...r5 is the border peer & r8 & r4 are clients...i configure a default cost of 5 on r5 but when i issue a "show dlsw cap" on either client, the peer cost stays @ 3...is this a bug or misconfig? r5 (the border peer) dlsw local-peer peer-id 100.100.5.5 group 100 border promiscuous dlsw peer-on-demand-defaults cost 5 #also tried configuring "dlsw prom-peer-defaults cost 5" here but it did not work as well - the only thing that works is when i explictly configure the cost on the dlsw local-peer statement (then it shows up on r8 & r4 w/ a cost of 2) -------------------------------------------------------------------------- r8 (a border peer client) dlsw local-peer peer-id 100.100.8.8 group 100 dlsw remote-peer 0 tcp 100.100.5.5 -------------------------------------------------------------------------- r4 (a border peer client) dlsw local-peer peer-id 100.100.4.4 group 100 dlsw remote-peer 0 tcp 100.100.5.5 Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=47333&t=47333 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
