It sounds like it has improved somewhat from when I was using the Allot box
back in '97. It would be nice if there was more automation in the process.

On Wed, Mar 30, 2011 at 2:48 PM, Rick Kunze <[email protected]> wrote:

> It's been a lengthy learning curve, I've been forming this mechanism
> since around 2001 but it all works very well now.  I use 5 levels of
> priority for customers, Level 0 through Level 4.  Level 5 is for
> special use when needed and 6 is infrastructure equipment.  Level 7
> (top level) is reserved so I can reach things in the event of some
> other host or interface causing a packet storm or the like.
>
> Then the balancing act is grouping day-user businesses with
> night-user residentials, or whatever is needed to lump all customers
> into a few smaller groups.  Then the total bandwidth is partitioned
> into the same number of slices as there are groups of
> customers.  This becomes the CIR but is fundamentally based on
> priority.  The burst then comes in from the scattering of priority
> levels within each group.  Basically residentials are sacraficed
> during the week days for any other higher priority packet.  But
> ceilings are also put in place to keep any one customer from sucking
> all the Ether out of the wire.  That's also inherent in the grouping
> strategy.
>
> It's always a moving target though, and needs re-shuffling from time
> to time as the usage patterns of some users change over time.
>
> Some groups are geographical, but mostly it's random based on usage
> patterns.  What I've seen change the most over the last 6-12 months
> especially is that residential is overtaking business.  The night
> time bandwidth demands are equal to and starting to exceed daytime
> business demands.  The former having ramped up considerably lately
> with movies and the like.  A streaming Netflix standard def movie is
> roughly a 1.2 meg stream for a couple hours, but the "duty cycle" as
> I like to call it is only about 50% to 80%.
>
> Rk
>
>
>
> At 08:53 AM 3/30/2011, you wrote:
> >Rick, Thats great! The real trick is can you prioritize AND bill
> accordingly?
> >
> >On Wed, Mar 30, 2011 at 10:53 AM, Rick Kunze
> ><<mailto:[email protected]>[email protected]> wrote:
> >At 10:37 AM 3/29/2011, you wrote:
> > >Wow that would be cool. Now just to find a device which can split
> > >all that out easily and maintain accounting.
> >
> >I have this all automatically controlled with a Packeteer.  Eight
> >levels of priority with "on the fly" per packet control, partitioning
> >of bandwidth, and the ability to control both priority and volume on
> >a per customer basis, right down to the actual type of traffic such
> >as www or smtp, or Citrix, or you name it.  Traffic discovery, makes
> >graphs, runs scripts to change things on weekends for example, all
> >kinds of features.
> >
> >These things are cheap on Ebay.
> >
> >Rk
> >
>
>
>
>
> --------------------------------------------------------------------------------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
>
> --------------------------------------------------------------------------------
>
> WISPA Wireless List: [email protected]
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>



-- 
-RickG

--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: [email protected]

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to