如果您回顾一下我在3年前开始在写这篇博客时，我写了一系列关于我们如何建立当前广域网的博客：使BGP我们的核心企业路由协议使用BGP使我们的互联网接入动态使用BGP构建单独的实验室网络绝大多数这些路由协议设计，全部基于网络设计模板，仍然存在。然而，我们在去年遇到了一个有趣的问题。我们出了带宽。尽管网络设计稳固，但用户仍然互相踩到带宽，即使是QoS.。当我们建立新的WAN 4年前，我们为美国提供了两个3 MBPS MPLS电路的每个典型站点，该电路是负载平衡（国际网站的大小）。因此，由于每次会话负载平衡，6 Mbps总带宽，但个人用户会话限制为3 Mbps。当时，这是合适的。我们的应用程序较少，没有VoIP，每个申请使用每个会话的带宽较少，而YouTube和Facebook刚刚入门。不幸的是，几个事件发生在过去4年中，让我们在今天的带宽泡菜中。首先，尽管经济衰退，我们尽可能地做得很好。更多人等于更多的WAN带宽。其次，互联网内容正在爆炸，用户期望访问。第三，我们添加了许多应用程序，视频会议和VoIP。 Finally, and more importantly, about every 2 years you should go to your carriers and require a price leveling (this should be part of your contract). This keeps your pricing in line with industry competitive standards. Normally, this price reduction is turned into bandwidth upgrades. So, your total spend doesn't change, but you end up with an across-the-board bandwidth upgrade. Too bad our 2-year mark was the fall of 2008. Anyone remember what happened in the fall of 2008? The cost savings from that price leveling was delivered to the bottom line to reduce costs during the recession and the bandwidth upgrade was skipped. This leaves us today with a WAN that hasn't had a bandwidth upgrade in 4 years. We started to notice the cracks about a year ago. Sites started complaining about slow response times or individual users filling the circuits doing large downloads (QoS would protect critical applications, but bulk transfers would step on each other). Then, we started testing WAN acceleration thinking it would be the elixir for the bandwidth problem, only to be因结果而失望。WAN加速测试是我们了解到的地方WAN加速是好的，但需要与更多的带宽合并。鉴于此信息，我们旨在为完整的WAN制定业务案例转型。这不仅仅是一个带宽升级，而且包括许多服务 - 带宽，WAN加速，升级的Internet访问，SIP中断等。该商业案例现已批准，我们即将开始。下周我将深入研究业务案例我们为它创造了ROI。之后，我将覆盖构成WAN转型的新技术和服务。这将是一个有趣的12个月。
更多>来自Field Blog条目：
去思科子网对于更多思科新闻，博客，讨论论坛，安全警报，书籍赠品等等。