North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Xedia vs Packeteer Comparsion
> > I was told that the xedia boxes only shape outgoing bandwidth, not > incoming. I haven't had the chance to ask xedia about this yet, and > haven't gotten their box in yet, so I'm not positive if this is true, but > you may want to check it out before buying. We have several of the Xedia boxes, and they shape only on the outgoing port; of course, this simply means that you can configure two different CBQ's for a given IP or port range, one on the "outgoing" port to the server, and one on the "outgoing" port to the rest of the net. :) It's an issue of technical correctness versus real utility. So the real answer is that the Xedia can rate shape in both directions, it simply does the rate shaping on the corresponding "out" interface for the particular direction of traffic. Hope this helps! Matt > On Fri, 30 Oct 1998, bcurnow > wrote: > > > > > I got some followups/corrections on key points which I feel I should > > distribute: > > > > The person from Xedia who told me 600 was the class limit, emailed me > > again and realized that I might really mean how many end points under > > control of those classes. The answer I came away with is that the Xedia > > can support a lot more end points (users) than 600. Hope I got that > > right. :) > > > > An engineer at UU.net also said 600 was too low, and that it is more an > > issue of how much RAM is in the box. He said thousands, which sounds > > promising. > > > > So, if I had to buy today, it looks like Xedia is the one to have if > > you're doing things on a large scale. > > > > ----------------- Brian Curnow ---------------- > > > > > > > > Thank you, > > Jonathan A. Zdziarski > Sr. Systems Administrator > Netrail, inc. > 888.NET.RAIL x240 > >
|