The most important thing is to know your traffic pattern by using some kind of Netflow. Once you know your traffic, you must classify it and decide which traffic can be dropped in case of congestion. QOS of service can be used to achieve that. For example you can classify the traffic of your top $$$ customer as gold (VOIP-VPN) and the traffic from XDSL home user as Bronze (KAZAA) etc. Off course you must have enough bandwidth to serve you top $$$ customer. Advantages and disadvantages will depend on the way how you want to implement the QOS solution.
-----Original Message----- From: ISP-CACHING Discussion List digest [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 09, 2003 09:00 AM To: isp-caching digest recipients Subject: isp-caching digest: February 08, 2003 ISP-CACHING Digest for Saturday, February 08, 2003. 1. Bandwidth Management / Traffic Shaping ... ---------------------------------------------------------------------- Subject: Bandwidth Management / Traffic Shaping ... From: "Netman" <[EMAIL PROTECTED]> Date: Sat, 8 Feb 2003 04:20:39 -0500 (EST) X-Message-Number: 1 Hi there. We are a service provider looking for a product to help us manage our bandwidth consumption, i.e: traffic shaping. We looked into Packeteer's, SysMaster's, and a couple other solutions. But i wanted to hear from you guys, someone who is actually using any of these or others, how well the solution is working for them, any advantages/disadvantages ...etc Thanks ! _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! --- END OF DIGEST --- You are currently subscribed to isp-caching as: [EMAIL PROTECTED] To unsubscribe send a blank email to %%email.unsub%% ____________ The ISP-CACHING Discussion List ___________ To Join: mailto:[EMAIL PROTECTED] To Remove: mailto:[EMAIL PROTECTED] Archives: http://isp-lists.isp-planet.com/isp-caching/archives/
