Difference between revisions of "VPN Site-to-Site networking"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
(→Important informations) |
(→Important informations) |
||
| Line 39: | Line 39: | ||
=== Important informations === | === Important informations === | ||
| − | VPN | + | * Normal Internet traffic completely separated from Voice traffic by means of second Internet connection to ISP: |
| + | ** Voice quality over VPN is preserved from normal Internet traffic side effects (No Voice/Date traffic congestion, no burstly data traffic or high downstream can jam Voice connections) | ||
| + | ** HiPath 2000 can manage VPN Bandwidth entirely (No Bandwith share with normal Internet traffic) | ||
| + | ** Better HiPath 2000 performance usage: it must only handle and route VPN traffic | ||
| + | * Routing/Security policies demanded at additional Proxy/Firewall devices for normal Internet traffic handling | ||
== VPN with normal Internet traffic and QoS support == | == VPN with normal Internet traffic and QoS support == | ||
Revision as of 13:50, 18 November 2006
Contents
VPN Site-to-Site networking
VPN without normal Internet traffic
This Site-to-Site networking scenario lets an enterprises to use:
- HiPath 2000 as VPN Site-to-Site gateway both for Voice and Data traffic.
- HiPath 2000 as a cost-effective gateway to route VoIP traffic by means of use CorNet-IP trunking between sites over VPN trunk.
- HiPath 2000 as gateway to access enterprise resources and applications available on the company’s VPN networked sites.
Overview
VPN Site-to-Site networking without normal Internet traffic Overview here
Important informations
- Basic bandwidth reservation for Voice can be implemented on HiPath 2000 setting:
- Outgoing Bandwidth Control
- B-Channels limitation
- No external Firewall is required at site (HiPath 2000 features firewalling service)
- If, at some point, normal Internet traffic (like Web navigation, Mail server access, etc.) is required by the Customer, then Hipath 2000 VPN Site-to-Site networking implementation must be designed according to VPN with normal Internet traffic scenario. In that case:
- Customer need to ensure itself with additional ISP connection to Internet
- Customer need to ensure additional devices/services like:
- Router, necessary to route LAN hosts normal data traffic to Internet
- Firewall, necessary to protect LAN hosts and implement DMZ at site
- Proxy, necessary to implement Internet traffic policies
VPN with normal Internet traffic
Overview
VPN Site-to-Site networking with normal Internet traffic Overview here
Important informations
- Normal Internet traffic completely separated from Voice traffic by means of second Internet connection to ISP:
- Voice quality over VPN is preserved from normal Internet traffic side effects (No Voice/Date traffic congestion, no burstly data traffic or high downstream can jam Voice connections)
- HiPath 2000 can manage VPN Bandwidth entirely (No Bandwith share with normal Internet traffic)
- Better HiPath 2000 performance usage: it must only handle and route VPN traffic
- Routing/Security policies demanded at additional Proxy/Firewall devices for normal Internet traffic handling
VPN with normal Internet traffic and QoS support
Overview
VPN Site-to-Site networking with normal Internet traffic and QoS support Overview here
Important informations
VPN Site-to-Site networking with normal Internet traffic and QoS support Important informations here
