throwing money is the obvious and easy thing to do. OTOH, lots of businesses seem to have extra money, recession of no. Besides, what do you expect as a solution from the telcos? ;->
A comment of two below -- coming soon: www.chuckslongroad.info ""Chris Charlebois"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Is look at the traffic and figure out what it is and if it's necessary. 3 > mbs is some serious bandwidth for one spoke site. Is it database lookups on > some apps? Perhaps it makes sense to put a database in the remote site and > synchronize. Voice/video traffic? make sure your QoS infrastructure is up > to date. Is it internet traffic? Perhaps some policies would help, or > perhaps the third T1 should go from the remote site directly to an ISP. Is > it garbage (i.e. SAP, DHCP, DNS, routing protocols, proxied arp, etc)? Then > cut that B (as in b) S (as in s) out. CL: In the book "Advanced IP Routing in Cisco Networks" Slattery and Burton discuss a bandwidth analysis in the TCP/IP Overview chapter. This gets back to the original studies regarding TCP windowing done by Van Jacobson and reported in RFC 1323 CL: it has been a while since I have done it, but Optsys has an application that allows one to simulate a data netowrk and do some what-if's with bandwidth. I can recall looking at a test network with a 128K link, and the simulation showing that traffic was chiking the link. doubling that link to a simulated 256K ended the congestion ( according to the simulation ) Of course, the folks running the study - a telco - were pushing the T1 solution because "more is better" CL: which gets me to ask - ever wonder why telcos offer Fractional T's, and Frame and ATM CIR's in the increments they do? most of them do not offer increments of 64K ( one channel ) they have increments of 56K, 128K, 384K, 768K and full T1, as an example. Why? One answer might be to maximize their revenues ;-> > > Anyone can throw more money at a problem. As professionals, we need to > throw brains first. CL: using brains takes time. throwing hardware / bandwidth at the problem is faster and easier. and for us overworked net engineers and sales engineers may not have the luxury of doing so. ;-> Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=51385&t=51304 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
