From: Alvaro Motta <alvarolmmotta@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Use of qcdisc+htb
Date: Thu, 14 Jul 2005 13:14:37 +0000 [thread overview]
Message-ID: <3941d81c05071406147a1107e6@mail.gmail.com> (raw)
Hi folks.
This message may be a bit verbose and not as techie as the ones I've
seen in this list, but describing the scenario will save a lot of
messages.
Scenario:
A building with 17 floors, each floor with 24 offices (totals 408
offices) connected to the backbone through a border switch (1 vlan for
each office). The offices can lease bandwidth of 64k, 128k, 256k,
512k, 1M and 2Mbps, according to their needs. We have 3 links to the
internet, 2Mbps each. Currently, we use cisco's bbsm to handle the
task of allocating the leased bandwidth for the vlans.
Problem: bbsm never performed as expected. It freezes, disconnect
users, reboots for itself leaving us in an awkward situation. After
wasting precious time with cisco and it's product, we decided to move
to another solution and since the boss is an enthusiast of open source
software, we decided to go for a linux based solution.
We found that queueing discipline may be the solution.
The question: are we correct, I mean is qdisc+htb the right thing to
be used in such a scenario? Has anyone out there seen a linux box
handling so many networks?
As I go deeper in this subject, I will come to share my thoughts and
doubts with you guys.
Hope to hear from you. Have a good one.
AL
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-07-14 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 13:14 Alvaro Motta [this message]
2005-07-14 14:27 ` [LARTC] Use of qcdisc+htb rsenykoff
2005-07-14 15:24 ` Peter Surda
2005-07-14 17:02 ` Peter Surda
2005-07-15 9:55 ` Paweł Staszewski
2005-07-15 12:16 ` Peter Surda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3941d81c05071406147a1107e6@mail.gmail.com \
--to=alvarolmmotta@gmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.