These branches typically have one branch router with a WAE (either internal or external) for optimizing traffic. 9.5 Common Branch TopologiesĪlthough in many cases a branch might have overlapping features from the following profiles, a typical branch with WAN optimization can be categorized into one of the most widely deployed topologies. These methods can improve both availability and scaling. In addition, branch routers can have multiple exit interfaces connected to the WAN for load sharing. In a branch network, load sharing can be implemented by having multiple WAN exit routers to share the load. Load sharing can provide both improved availability and scalability to the network. 9.4 Load SharingĪ good branch design also provides resources for scaling and growth. Network performance is a key consideration for such applications, which need fast connectivity and bandwidth. 9.3 Network and Application PerformanceĪs global businesses evolve, some deploy more and more business critical applications that can provide split-second decisions. Additionally, many government regulations, such as Health Insurance Portability and Accountability Act (HIPAA) and Sarbanes-Oxley (SOX) mandate securing traffic. To protect against snooping and provide business confidentiality, some form of data encryption should be deployed. Data that traverses the Internet is highly susceptible to snooping. Typically, data transfer between branches and corporate headquarters happens over a service provider (SP) network or over the Internet. Security is a critical factor in any network design. In very small branch offices, the cost of providing resiliency may not provide adequate cost benefits. Designers should consider the cost-benefit ratio of resiliency and plan for appropriate resiliency. The cost of business interruption caused by network failure, the probability of component or network device failure, and other factors must be carefully analyzed. It is essential to avoid single points of failure. Providing uninterrupted network connectivity between branches and headquarters, and among branches, is critical to any network design. This chapter considers different technologies that can address these requirements, and introduces sample branch designs. For any branch network, the designer must consider the following key requirements: Their branch offices must have effective and reliable network connectivity to their corporate HQs (and between branch offices) in support of business applications. In today's global economy, companies are rapidly expanding their presence throughout the world. ![]() 9.23.2 Data Center Deployment Scenario 2.9.23.1 Data Center Deployment Scenario 1.9.23 NAM-2 Data Collection for WAN and Application Optimization.9.21 NAM 3.6 Metrics for WAN and Application Optimization.9.20.1 NAM-2 Support for WAN and Application Optimization.9.20 Cisco NAM Use Cases for WAN and Application Optimization. ![]() 9.19 Use Case 2: Validating WAAS Effectiveness.9.18 Use Case 1: Predeployment Baselining.9.17.6 Device Performance Analysis using NetQoS NetVoyant.9.17.5 Link Traffic Analysis using NetQoS ReporterAnalyzer.9.17.4 Application Response Time Analysis with NetQoS SuperAgent.9.17.3 NetQoS Deployment Considerations.9.17.2 NetQoS Metrics for WAN and Application Optimization.9.17.1 NetQoS Support for WAN and Application Optimization.9.17 Performance Monitoring for WAN and Application Optimization.9.15.2 WAAS Catalyst 6500 Load Balancing.9.13.4 Large Branch Offices with Dual-Homed, Dual-Tiered Branch Routers.9.13.3 Medium Branch Office with Dual-Homed, Dual-Tiered Branch Routers.9.13.2 Small Branch Office with Dual-Homed, Single-Tier Branch Router.9.13.1 Small Branch Office with Single-Homed SOHO Branch Router.9.12.11 NBAR Cannot Perform DPI if WAE TCP Optimization Occurs before NBAR Discovery.9.12.10 WAAS Might Not Intercept IP SLA Probes Configured on the Branch Router.9.12.7 CIFS tunneling on WAE and Network visibility.9.12.6 PFR Interface Mapping and NetFlow Sampling.9.12.5 PfR Cannot Recognize MQC Marking Done by the Same Router.9.12.3 PfR Might Break WAAS TCP Optimization if the WAAS Network Path Changes.9.12.2 PfR Supports only BGP or Static Routes for Path Optimization. ![]() 9.12.1 PfR Supports Only One Next Hop Per Interface.9.11.2 QoS, NBAR, NetFlow, and Path Optimization with PfR.9.9.2 Internet-Based VPNs Secured using DMVPN.9.6.1 Application Visibility Using NBAR.9.5.5 Branch WAN-Side High Availability.9.5.4 Branch LAN-Side High Availability.9.3 Network and Application Performance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |