19.07.2013 Views

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Site-to-Site V3PN <strong>QoS</strong> Considerations<br />

6-2<br />

<strong>Enterprise</strong> <strong>QoS</strong> <strong>Solution</strong> <strong>Reference</strong> <strong>Network</strong> <strong>Design</strong> <strong>Guide</strong><br />

Chapter 6 IPSec VPN <strong>QoS</strong> <strong>Design</strong><br />

Remote-access clients—Tunnels are established by software to connect mobile users at airports,<br />

hotels, or similar places to a central site using WLAN hotspots, LAN ports, or modems.<br />

Figure 6-1 IPSec VPN <strong>Design</strong> Contexts<br />

IPSec VPN<br />

Tunnels<br />

Site-to-Site<br />

IPSec VPN<br />

Teleworker<br />

IPSec VPN<br />

Service Provider/<br />

Internet<br />

Remote Access<br />

IPSec VPN<br />

(Software Client)<br />

Enabling converged services, such as voice and video, on an IPSec VPN has been dubbed V3PN. V3PN<br />

is essentially the overlaying of <strong>QoS</strong> technologies over IPSec VPNs to provide the required service levels<br />

to voice and video applications. As such, V3PN solutions relate to only two of the three IPSec VPN<br />

design contexts: site-to-site VPNs and telecommuter VPNs. (Little, if any, <strong>QoS</strong> is available in<br />

remote-access client networks.)<br />

This chapter discusses <strong>QoS</strong> design considerations and recommendations for both site-to-site and<br />

telecommuter V3PN solutions.<br />

Note It is beyond the scope of this chapter to detail IPSec encryption operation and configuration; a working<br />

knowledge of IPSec is assumed.<br />

Site-to-Site V3PN <strong>QoS</strong> Considerations<br />

Central Site<br />

WAN<br />

Aggregators<br />

IPSec VPN<br />

Headers<br />

Attractive pricing is usually the driver behind deploying site-to-site IPSec VPNs as an alternative to<br />

private WAN technologies. Many of the same considerations required by private WANs need to be taken<br />

into account for IPSec VPN scenarios because they usually are deployed over the same Layer 2 WAN<br />

access media.<br />

IPSec VPNs also share some similar concerns with MPLS VPNs. For instance, the enterprise’s<br />

end-to-end delay and jitter budgets depend significantly on the service provider’s SLAs. Therefore,<br />

enterprises deploying V3PN solutions are recommended to utilize Cisco Powered <strong>Network</strong> IP<br />

Multiservice service providers, as discussed in Chapter 5, “MPLS VPN <strong>QoS</strong> <strong>Design</strong>.”<br />

Version 3.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!