Thread View: aus.acsnet
3 messages
3 total messages
Started by Piers Lauder
Mon, 13 Jul 1992 06:56
costs vs. delays explained
Author: Piers Lauder
Date: Mon, 13 Jul 1992 06:56
Date: Mon, 13 Jul 1992 06:56
53 lines
2668 bytes
2668 bytes
ggm@brolga.cc.uq.oz.au (George Michaelson) writes: > Dear Piers. please save myself and other sysops a lot of trouble by > explaining by example how we do this. The values shown by your automatically > generated table do not equate to values present in my commandsfile and I > am unwilling to stir the entrails without a better understanding of whats > required. > > Take > bunyip<->qdpii as an instance. > > you state: > > unequal link costs: > bunyip.cc.uq.oz.au to qdpii.comp.qdpi.oz.au => 0 > qdpii.comp.qdpi.oz.au to bunyip.cc.uq.oz.au => 1 > > I have this in commandsfile: > > delay bunyip.D=cc.O=uq.oz.au, > N=stallion.D=sw.O=stallion.oz.au 86400 > delay N=stallion.D=sw.O=stallion.oz.au, > bunyip.D=cc.O=uq.oz.au 86400 > > > Now tell me what I should have. First thing to do is read the relevant section of "netstate(8)" :-) You will notice that "delay" and "cost" are different commands. You should only set costs on links _from_ your site to a link, (that is, your site only `owns' the cost parameter in the outbound directions), conversely, you should only set delays from a link _to_ your site. Of course you _can_ set both directions, but that will only affect your local routing, will not be believed by other sites, and netstate will warn you the first time you try it. (Because it may cause routing loops between you and another site who believes what your link tells it about the parameters that it `owns'.) So, to change the "cost" inequality above, should you feel it to be incorrect, "bunyip" can use the command: cost N=bunyip.D=cc.O=uq.P=oz.C=au, N=qdpii.D=comp.O=qdpi.P=oz.C=au 1 OR, "qdpii" can use: cost N=qdpii.D=comp.O=qdpi.P=oz.C=au, N=bunyip.D=cc.O=uq.P=oz.C=au 0 -- Computer Science, Sydney University, Madsen Bldg F09, Sydney NSW 2006 Phone: +61 2 692 3423 Fax: +61 2 692 3838
Re: costs vs. delays explained
Author: George Michaelson
Date: Mon, 13 Jul 1992 11:26
Date: Mon, 13 Jul 1992 11:26
23 lines
1651 bytes
1651 bytes
(1) I have no instances of the word "cost" in my commandsfile and
much though I admire my downstream feeds, I doubt if they read
the manuals, and will have added them either. Thus, I have to beg
some guidance on how instances of cost-values can creep into my
link state.
(2) netmap -Y does reveal information in [] appended after link details
as per manual. It doesnt append in the form [<number>(C|D)] as shown
in the manual. If you'd asked me 30 seconds ago what the difference
between delay and cost was based on what netmap -Y tells you, I'd have
been marginally less able to say.
As it stands, the best I can say is...
huh?
-George
--
George Michaelson
G.Michaelson@cc.uq.oz.au The Prentice Centre | There's no market for
University of Queensland | hippos in Philadelphia
Phone: +61 7 365 4079 QLD Australia 4072 | -Bertold Brecht
Re: costs vs. delays explained
Author: David J. Hughes
Date: Tue, 14 Jul 1992 01:52
Date: Tue, 14 Jul 1992 01:52
24 lines
1599 bytes
1599 bytes
piers@basser.cs.su.oz.au (Piers Lauder) writes: >You will notice that "delay" and "cost" are different commands. You >should only set costs on links _from_ your site to a link, (that is, >your site only `owns' the cost parameter in the outbound directions), >conversely, you should only set delays from a link _to_ your site. Ah yes, now it's as clear as mud.... Is there some subliminal relation between cost and delay parameters? You quote "cost" figures between lance and ptcburp and also lance and bunyip yet they have no costs set on the links. The figures do, though, closely resemble the delay settings. One more time with feeling, please Piers. ___ David J. Hughes bambi@bu.oz.au / \ / / / / __/ __ __ ____/ / / __ Senior Network Programmer / \ / \ / \ / / / / / \ / Comms Development & Operation \____/ \__// / \__/ \___/ / / / AUSTRALIA (+61 75 951450)
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads