1 1.1. Abstract Traditionally organizations have designed their VPN networks using layer 2 WANs that provide emulated leased lines. In the last years a great variety of VPN technologies has appeared, making more difficult to match the best technology for each organization. In the actual scene service providers are trying that costumers outsource their VPN in order to efficiently manage their networks. In this paper there is a simulation-based analysis of the four main VPN technologies used nowadays: Frame Relay, ATM, IP-Tunneling (GRE, IPSec) across public Internet, and private IP-MPLS network. In this analysis a general scenario has been defined. In this scenario an organization has to interconnect four remote offices with the central building and its servers. The organization has also four remote workers that need access to the corporative intranet. The user profile includes all kind of applications: Web, FTP, and Database access. A scenario has been created for each technology; then, the network performance has been evaluated from the point of view of efficiency, scalability, QoS and economic cost. The simulations analysis will show the best option for each scenario VPN Overview The meaning of the VPN term is used in several ways and there are different definitions depending on the technology or the applications used in the VPN. IETF gives the next definition: VPN is defined as the emulation of a private WAN through public networks.  We can mainly differentiate between two kinds of VPN models: the Overlay model and the Peer-to-Peer model. In the Overlay model the service provider network provides the costumer a set of emulated leased lines, called virtual circuits, to interconnect the sites. On the other hand, in the Peer-to-Peer model the provider s edge-routers directly exchange routing information with costumer routers. That fact simplifies costumer routing and bandwidth provisioning links, it is more scalable, and service provider can route packets more efficiently. In the past, almost all organizations used to design Overlay VPN using layer 2 technologies as Frame Relay or ATM. Later the layer 3 Overlay VPN with GRE and IPSec became more popular, because it has the great advantage of the economical fares of internet connections. With the use of MPLS inside the IP backbones of service providers, the last generation of VPN technologies arrives.
2 MPLS networks have the advantages of VPN Peer-to-Peer model and also implement QoS for priority traffic. From the service provider s point of view, MPLS allow several services over a single network, so traffic engineering can be applied to distribute traffic flows efficiently. Many costumers decide to outsource their intra or extranet communications due to the great advantages of this service. Figura 1: Figure 1: VPN technologies 1.3. Network Topology The design of the network model is composed of a central service LAN where we can find all the Intranet servers. There are four remote offices connected to the corporative intranet trough the service provider network, and there are also four remote workers that will connect to the intranet using ISDN or xdsl links, depending on the technology of the service provider backbone. Figura 2: Figure 2: Network topology
3 The LAN model design simplifies the reality because the focus of this study is to analyze the WAN that interconnect all corporative LANs. For that reason, all LAN links and hardware are over provisioned to prevent any influence on the study. The central LAN is composed of four servers supporting standard applications (FTP, Web, and database) and several LANs that group 100 users. Everything is interconnected by a single switch. Figura 3: Figure 3: Central LAN topology Remote offices are simpler that the central LAN and we can only find a pair of LANs of 50 users. Figura 4: Figure 4: Remote LANs topology For each technology the next scenarios have been defined: - Frame Relay network - ATM network - Public IP network - Private IP network
4 1- Frame Relay Network. a. Hub-and-Spoke topology. b. Hub-and-Spoke topology with double number of remote offices. Figura 5: Figure 5: Frame Relay basic topology The Frame Relay WAN network has been modeled with a frame delay represented by an exponential curve centered on 35 ms; that is the typical delay measured on these networks. Also, the 5% of EIR frames will be discarded. After configuring the WAN node, the PVCs between remote office and central services have been defined with a committed CIR of 512 Kb and an EIR of 2 Mbps. Figura 6: Figure 6: PVC configuration The remote workers connectivity is achieved through ISDN links that connect to a RAS device. Frame Relay doesn t permit integrating VPDN connections.
5 2- ATM Network. a. Hub-and-Spoke topology. b. Hub-and-Spoke topology with double number of remote offices. Figura 7: Figure 7: ATM topology The ATM WAN network has been modeled with a uniform cell delay from 30 to 40 ms; that is the typical delay measured on these networks. Also, the of cells will be discarded. After configuring the WAN node, the SPVCs between remote office and central services have been defined. UBR is the defined contract traffic and AAL5 is used as an adaptation layer. Figura 8: Figure 8: SPVC configuration As in the Frame Relay scenario, the remote workers connectivity is achieved through ISDN links that are connected to a RAS device. ATM doesn t permit integrating VPDN connections.
6 3- Public IP Network: INTERNET. a. Hub-and-Spoke topology. b. Hub-and-Spoke topology with double number of remote offices. Figura 9: Figure 9: Public IP network topology The Internet node has been modeled with a packet delay represented by an exponential curve centered on 250 ms; that is the typical delay measured on these networks. Also, the 5% of packets will be discarded. As in the other Overlay model technologies, the virtual circuits between remote office and central services have been defined. In this case the virtual circuits are configured by the costumer using tunneling techniques as IPSEC. The encryption and decryption procedures will add 100 ms to network delay. The tunnels operation mode is compulsory, so security is centralized on the Central LAN. Figura 10: Figure 10: VPN configuration
7 In this case, remote users can connect to the corporative network through Internet. In this scenario they will use ADSL links to access to Internet. 4- Private IP Network: MPLS a. Hub-and-Spoke Topology. b. Hub-and-Spoke Topology with double number of remote offices. Figura 11: Figure 11: Private IP network topology One of the advantages of this technology is its ability to integrate all kind of access links. In this model we use Frame Relay, ATM, ADSL, ISDN, and point-to-point leased links. OPNET does not provide a WAN node with IP-MPLS features, and for that reason we had to model it manually. In the next figure we can observe the backbone design. It is composed of LERs (acting as edge routers), LSRs (in the core of the WAN), and gateways to other networks.
8 Figura 12: Figure 12: MPLS backbone design Another limitation of OPNET 8.0 is that it is not possible to configure VPN as it is specified in the standard. It is necessary the implementation of VRF tables on the LER edge routers. We have used an alternative method to implement the VPN, using traffic engineering techniques. It consists on defining some conditions (FECs), that determine which VPN belongs to each packet and its destination. In all LERs that belong to the VPN, each FEC is assigned to a LSP that has been previously defined. Figura 13: Figure 13: VPN configuration
9 1.4. Traffic Modeling The traffic has been modeled in two different ways, with explicit traffic and with background traffic. The reason of this hybrid traffic model is that the explicit traffic makes the simulation very slow; so, in order to get a better simulation performance it is good to combine explicit traffic with conversation pair background traffic. In the modeled scenarios background traffic represents the 90% percent of the total traffic. This traffic is increased during the simulation, to test the links and devices response to congestion. On the next figure, the background traffic between one remote office and the Central router is shown. Figura 14: Figure 14: Background traffic The explicit traffic is generated by users using standard applications, as HTTP, FTP, e- mail, and database access.
10 1.5. Simulation Results / Analysis Here are the different results obtained in the simulation of the different scenarios. Also, an analysis of these results is given in order to compare the technologies and scenarios. 1- Frame Relay Network. a. Hub-and-Spoke topology. Frame Relay Delay Frame Relay Residual Error Rate DB Query Response Time Figura 15: Figure 15: FR delay, residual error rate, and query response time in basic scenario With a Frame Relay basic scenario the simulation results show a network that provides low frame latency and a low jitter, between 50 and 60 ms. There isn t any discarded frame until traffic exceeds the committed CIR. The query response time is low at the fist moment of simulation, around 150 ms, but discarded frames cause great delays on application in the last part of the simulation.
11 b. Hub-and-Spoke topology with double number of remote offices. Frame Relay Delay Frame Relay Residual Error Rate DB Query Response Time Central Router CPU Utilization Figura 16: Figure 16: FR delay, residual error rate, query response time and central router CPU utilization in the double scenario In the double scenario the delay and the frame error rate are very similar to the basic scenario. Query response time has increased to the maximum values due to the bigger flow of traffic and the discarded frames. The last figure is a comparison between the CPU utilization of the central router of each scenario. In the second scenario this parameter is 20 times bigger. In a real system we would probably have to change the actual router to a more powerful one. That fact gives us an idea that it is not a very scalable technology.
12 2- ATM Network. a. Hub-and-Spoke topology. ATM Delay ATM UBR Cell Loss Ratio DB Query Response Time Figura 17: Figure 17: ATM delay, UBR CLR and query response time in the basic scenario With an ATM VPN the simulation results reflect a very good network performance. The ATM cell delay is very low (around 40 ms) and constant during all the simulation. During the simulation it has not been registered any loss of cell. The query response time is low and considerably constant, between 200 and 400 ms.
13 b. Hub-and-Spoke topology with double number of remote offices. ATM Delay ATM UBR Cell Loss Ratio DB Query Response Time Central Router CPU Utilization Remote Office IP Processing Delay Remote Office Router CPU Utilization Figura 18: Figure 18: ATM delay, UBR CLR, query response time and router utilizations in the double scenario In this scenario delay and error rate doesn t change compared to the ATM basic scenario, but we can see that the response time has an important increase at the third part of simulation. To explain this fact, we can look at the CPU utilization of the
14 routers. In the central router comparison, the values are on the same order, around 50% (in the double scenario, central router has been modeled with a x5 speed factor) The problem is localized, then on the remote office routers. The CPU utilization is around 80%, causing additional delays of 1.5 s. So like Frame Relay, we also have problems when the network grows in the ATM double scenario. 3- Public IP Network: INTERNET. a. Hub-and-Spoke Topology. IP Delay Dropped Traffic DB Query Response Time Figura 19: Figure 19: IP delay, dropped traffic and query response time in the basic scenario With the Internet scenario we have collected the worst network performance results. In this case the delay is 10 times bigger (between 500 and 700 ms) and the jitter increases too. The error rate is also higher, with a mean of 2 dropped packets per second. The response time has been increased in the same proportion as the network delay. The
15 query application has a latency between 1.5 and 2 seconds, that is a poor performance compared with the 250 ms mean latency of the previous scenarios b. Hub-and-Spoke topology with double number of remote offices. IP Delay Dropped Traffic DB Query Response Time Network Server CPU Utilization Figura 20: Figure 20: IP delay, dropped traffic, query response time and utilization in the double scenario In the double scenario we can see that performance is degraded when the network grows. Network delay grows 100 ms and dropped IP packets are 4 times bigger. The response time is similar to the previous graphic of the basic Internet scenario. The network server comparison shows that in the second scenario the CPU utilization is two times the basic scenario, as it was supposed to be when it had to manage double volume of traffic.
16 Private IP Network: MPLS a. Hub-and-Spoke Topology. TCP Delay IP Traffic Dropped DB Query Response Time Figura 21: Figure 21: TCP delay, dropped traffic and query response time in the basic scenario In MPLS scenario we achieve a medium performance, between ATM (or FR) and Internet scenario. In this case the simulation results show a variable low delay that goes between 30 and 70 ms. The mean dropped IP packet is around 0.5 packet per second, 4 times less than the Internet scenario with the same traffic. Response time of the query application is low and has a high jitter too, which goes from 50 ms to 150 ms.
17 b. Hub-and-Spoke topology with double number of remote offices TCP Delay IP Traffic Dropped Figura 22: DB Query Response Time Central Router CPU Utilization Figura 23: Figure 22: TCP delay, dropped traffic, query response time and utilization in the double scenario In the double scenario the results have not changed much respecting the basic scenario. The mean latency and response time has increased in some milliseconds. The dropped IP packets and Central Router CPU utilization has increased a 100%, as it was supposed when the network grows a 100% too. We can see that kind of networks can grow without problems.
18 1.6. Conclusions Choosing a VPN technology depends in a high percentage on the applications that run over the network, the geographic situation of LANs and the economic cost. Depending on the organization requirement, we will have to decide which the best technology is. On the one hand, traditional technologies as Frame Relay have the advantages of being mature, reliable and secure technologies. On the other hand, the link cost is expensive, and usually it is only appropriated for hub-and-spoke topologies, due to Overlay model limitations. For that reason these networks can have problems of scalability. The banks usually implement their networks with this technology, because they need this security and reliability to transport critical traffic. ATM has similar features to Frame Relay. It is a mature and reliable technology but it has the Overlay model problems too. It can be used to transport big volumes of critical traffic, that need special QoS, or to transport multimedia communications. New techniques of tunneling and encryption through Internet as GRE or IPSec are the cheapest option, but not very appropriated when a guaranteed SLA is needed. It is usually a good option to interconnect remote workers or SOHOs to corporative Intranet using ISDN, xdsl, or cable links. However, it is not recommendable to use this technology between the important sites of an organization. Nowadays VPN services over service provider MPLS-IP backbones are the most flexible option. On the one hand, we can implement all kind of topologies without any restriction, it allows the integration of remote users on the same network and it can guarantee a level of service and apply QoS to priority traffic flows. The disadvantages of this service are that: it is not as cheaper as Internet VPN and also, you loose control of VPN network, because it is managed by the service provider. In the last figure we can see the position of each technology in a cost / quality diagram. As simulation results show, IP-MPLS is the technology that takes more area and is more
19 flexible with costumer needs, but not always matches all organizations needs References   Frame Relay  Frame Relay  ATM  IPSEC White Paper, IPSEC  Implementing a Cisco Virtual Private Network, IPSec  MPLS and VPN Architectures, Jim Guichard, Ciscopress.com 2002 
MPLS and MPLS VPNs: Basics for Beginners Christopher Brandon Johnson Abstract Multi Protocol Label Switching (MPLS) is a core networking technology that operates essentially in between Layers 2 and 3 of
Volume 3, Issue 9, September 2013 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Layer Based
ICTTEN6172A Design and configure an IP- MPLS network with virtual private network tunnelling Release: 1 ICTTEN6172A Design and configure an IP-MPLS network with virtual private network tunnelling Modification
Exam : 642-889 Title : Implementing Cisco Service Provider Next-Generation Egde Network Services Version : DEMO 1 / 6 1.Which type of VPN requires a full mesh of virtual circuits to provide optimal site-to-site
1 ISTANBUL 1.1 MPLS overview 1 1.1.1 Principle Use of a ATM core network 2 Overlay Network One Virtual Circuit per communication No routing protocol Scalability problem 2 1.1.1 Principle Weakness of overlay
Chair for Network Architectures and Services Prof. Carle Department for Computer Science TU München Master Course Computer Networks IN2097 Prof. Dr.-Ing. Georg Carle Christian Grothoff, Ph.D. Chair for
Table of Contents Which VPN Solution is Right for You?...1 Introduction...1 Before You Begin...1 Conventions...1 Prerequisites...1 Components Used...1 NAT...2 Generic Routing Encapsulation Tunneling...2
MPLS L2VPN (VLL) Technology White Paper Issue 1.0 Date 2012-10-30 HUAWEI TECHNOLOGIES CO., LTD. 2012. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any
Page 1 of 8 Computer Networking Networks 9.1 Local area network A local area network (LAN) is a network that connects computers and devices in a limited geographical area such as a home, school, office
International Journal of Computer Science and Telecommunications [Volume 5, Issue 6, June 2014] 9 ISSN 2047-3338 Implementation of Traffic Engineering and Addressing QoS in MPLS VPN Based IP Backbone Mushtaq
Case Study 2 Configure ISDN Backup and VPN Connection Cisco Networking Academy Program CCNP 2: Remote Access v3.1 Objectives In this case study, the following concepts are covered: AAA authentication Multipoint
Abstract Virtual Private Networks (VPNs) are today becoming the most universal method for remote access. They enable Service Provider to take advantage of the power of the Internet by providing a private
Introducción n a MPLS y MPLS VPN firstname.lastname@example.org Nelson Muñoz Presentation_ID 200, Cisco Systems, Inc. Agenda Introducción Que es una VPN? IP+ATM Conceptos básicos de MPLS MPLS VPN QoS en MPLS Ventajas
VPN1 6/9/03 6:00 PM Page 1 Part 1 The VPN Overview VPN1 6/9/03 6:00 PM Page 2 VPN1 6/9/03 6:00 PM Page 3 Chapter 1 VPN-in-Brief 1.1 VPN Overview This is the information age. We no longer have to commute
MPLS@NLBd.d. Janko Jager * MPLS Multi Protocol Label Switching ** NLBd.d. Nova Ljubljanska banka d.d. Telecommunications, Portorož, 04.10.2008 NLB d.d. 1 Foreword This presentation is about NLB d.d. experience
# 129 TECHNOLOGY WHITE PAPER Page: 1 of 5 MPLS and IPSec A Misunderstood Relationship Jon Ranger, Riverstone Networks ABSTRACT A large quantity of misinformation and misunderstanding exists about the place
Module 1-1 Introducing Basic MPLS Concepts 2004 Cisco Systems, Inc. All rights reserved. 1-1 Drawbacks of Traditional IP Routing Routing protocols are used to distribute Layer 3 routing information. Forwarding
Sprint Global MPLS VPN IP Whitepaper Sprint Product Marketing and Product Development January 2006 Revision 7.0 1.0 MPLS VPN Marketplace Demand for MPLS (Multiprotocol Label Switching) VPNs (standardized
Managed Services: Taking Advantage of Managed Services in the High-End Enterprise What You Will Learn This document explores the challenges and solutions for high-end enterprises using managed services.
Top-Down Network Design Chapter Five Designing a Network Topology Copyright 2010 Cisco Press & Priscilla Oppenheimer Topology A map of an internetwork that indicates network segments, interconnection points,
WHITE PAPER EVALUATING NETWORKING TECHNOLOGIES CONTENTS EXECUTIVE SUMMARY 01 NETWORKS HAVE CHANGED 02 Origin of VPNS Next-generation VPNS TODAY S CHOICES 04 Layer 3 VPNS Layer 2 VPNS MAKING YOUR DECISION
Addressing Inter Provider Connections With MPLS-ICI Introduction Why migrate to packet switched MPLS? The migration away from traditional multiple packet overlay networks towards a converged packet-switched
E-Guide In this eguide discover the differences between MPLS VPNs and traditional virtual private networks, as well as the advantages and disadvantages of the latest in service provider offerings. While
Virtual Private Networks Solutions for Secure Remote Access White Paper Copyright Decipher Information Systems, 2005. All rights reserved. The information in this publication is furnished for information
Multiservice Core Lucent Technologies Bell Labs Innovations Jan Damborský Network Sales Consultant Central Estern Europe InterNetworking Systems Na Příkopě 21 117 19 Ptaha 1 Czech Republic email@example.com
MPLS-TP Future Ready. Today Introduction As data traffic started dominating telecom networks, there was a need for transport data networks, as opposed to transport TDM networks. Traditional transport technologies
MPLS Concepts Overview This module explains the features of Multi-protocol Label Switching (MPLS) compared to traditional ATM and hop-by-hop IP routing. MPLS concepts and terminology as well as MPLS label
NETWORKS NetIron XMR 16000 NETWORKS NetIron XMR 16000 NETWORKS NetIron XMR 16000 Introduction MPLS in the Enterprise Multi-Protocol Label Switching (MPLS) as a technology has been around for over a decade
IVCi s IntelliNet SM Network Technical White Paper Introduction...2 Overview...2 A True ATM Solution End to End...2 The Power of a Switched Network...2 Data Throughput:...3 Improved Security:...3 Class
INTRODUCTION TO L2VPNS 4 Introduction to Layer 2 and Layer 3 VPN Services CE Layer 3 VPN Link Comprised of IP Traffic Passed Over IP Backbone LEGEND Layer 3 VPN Layer 2 VPN CE CE PE IP Backbone PE CE Layer
1 QoS Performance Evaluation in BGP/MPLS VPN M. C. Castro, N. A. Nassif and W. C. Borelli 1 Abstract-- The recent exponential growth of the Internet has encouraged more applications, users and services
MPLS in Private Networks Is It a Good Idea? Jim Metzler Vice President Ashton, Metzler & Associates March 2005 Introduction The wide area network (WAN) brings indisputable value to organizations of all
Quidway MPLS VPN Solution for Financial Networks Using a uniform computer network to provide various value-added services is a new trend of the application systems of large banks. Transplanting traditional
A Silicon Valley Insider MPLS VPN Services PW, VPLS and BGP MPLS/IP VPNs Technology White Paper Serge-Paul Carrasco Abstract Organizations have been demanding virtual private networks (VPNs) instead of
A Performance Analysis of Gateway-to-Gateway VPN on the Linux Platform Peter Dulany, Chang Soo Kim, and James T. Yu PeteDulany@yahoo.com, ChangSooKim@yahoo.com, firstname.lastname@example.org School of Computer Science,
Solution Overview Managed 4G LTE WAN: Provide Cost-Effective Wireless Broadband Service What You Will Learn With the arrival of the fourth-generation (4G) or Long Term Evolution (LTE) cellular wireless
Virtual Private LAN Service (VPLS) A WAN that thinks it s a LAN. VPLS is a high security, low latency means to connect sites or services either point-to-point or as a mesh. We use Virtual Private LAN Service
School of Electronic Engineering - DCU Broadband Switching and Systems Laboratory 1/17 Bandwidth Management in MPLS Networks Sanda Dragos & Radu Dragos Supervised by Dr. Martin Collier email: email@example.com
MPLS/BGP Network Simulation Techniques for Business Enterprise Networks Nagaselvam M Computer Science and Engineering, Nehru Institute of Technology, Coimbatore, Abstract Business Enterprises used VSAT
Multiprotocol Label Switching Layer 3 Virtual Private Networks with Open ShortestPath First protocol PRASAD ATHUKURI Sreekavitha engineering info technology,kammam Abstract This paper aims at implementing
Contents: The Case for Frame Relay The Case for IP VPNs Conclusion Frame Relay vs. IP VPNs 2002 Contents: Table of Contents Introduction 2 Definition of Terms 2 Virtual Privacy and 3 the Value of Shared
Sales & Engineering 3500 Virginia Beach Blvd Virginia Beach, VA 23452 800.853.0434 Ground Operations 1520 S. Arlington Road Akron, OH 44306 800.268.8653 VPN over Satellite A comparison of approaches by
VPN Date: 4/15/2004 By: Heena Patel Email:firstname.lastname@example.org What is VPN? A VPN (virtual private network) is a private data network that uses public telecommunicating infrastructure (Internet), maintaining
Tunnel Routing Preface As the pace of economic globalization picks up, more and more enterprises have set up branch offices beyond the geographical boundaries. Traditionally, private leased lines are used
Link Layer 5.1 Introduction and services 5.2 Error detection and correction 5.3Multiple access protocols 5.4 Link-Layer Addressing 5.5 Ethernet 5.6 Hubs and switches 5.7 PPP 5.8 Link Virtualization: and
Investigation and Comparison of MPLS QoS Solution and Differentiated Services QoS Solutions Steve Gennaoui, Jianhua Yin, Samuel Swinton, and * Vasil Hnatyshin Department of Computer Science Rowan University
Virtual Private LAN Service (VPLS) Walking through Wan history, from the early days Leased lines Customers subscribe to dedicated point-to-point links Cost prohibitive for customers Started in the 1980
Intranet Security Solution 1. Introduction With the increase in information and economic exchange, there are more and more enterprises need to communicate with their partners, suppliers, customers or their
Network Management for Common Topologies How best to use LiveAction for managing WAN and campus networks April 2014 www.liveaction.com Contents 1. Introduction... 1 2. WAN Networks... 2 3. Using LiveAction
2007 Cisco Systems, Inc. All rights reserved. DESGN v2.0 3-11 Enterprise Campus and Data Center Design Review Analyze organizational requirements: Type of applications, traffic volume, and traffic pattern
WHY CHOOSE COX BUSINESS FOR YOUR COMPANY S NETWORK SERVICE NEEDS? This document provides an overview of the Cox Business portfolio of business networking services and explains why customers should consider
UNDERSTANDING BUSINESS ETHERNET SERVICES EMPOWER YOUR BUSINESS TO MEET 21ST CENTURY DEMANDS INTRODUCTION The network is your business has been a mantra for many years indicating how businesses rely more
MPLS: Key Factors to Consider When Selecting Your MPLS Provider Whitepaper 2006-20011 EarthLink Business Page 1 EXECUTIVE SUMMARY Multiprotocol Label Switching (MPLS), once the sole domain of major corporations
EMPOWER YOUR BUSINESS TO MEET 21ST CENTURY DEMANDS INTRODUCTION The network is your business has been a mantra for many years indicating how businesses rely more heavily on being networked between their
Building integrated services intranets A White Paper from Inalp Networks Inc Meriedweg 7 CH-3172 Niederwangen Switzerland http://www.inalp.com CONTENTS CONTENTS...2 1 EXECUTIVE SUMMARY...3 2 INTRODUCTION...4
WAN and VPN Solutions: Choosing the Best Type for Your Organization xo.com WAN and VPN Solutions: Choosing the Best Type for Your Organization WAN and VPN Solutions: Choosing the Best Type for Your Organization
Quality of Service Analysis of site to site for IPSec VPNs for realtime multimedia traffic. A Network and Data Link Layer infrastructure Design to Improve QoS in Voice and video Traffic Jesús Arturo Pérez,
Basic Networking Concepts 1. Introduction 2. Protocols 3. Protocol Layers 4. Network Interconnection/Internet 1 1. Introduction -A network can be defined as a group of computers and other devices connected
White Paper Virtual Private LAN Service on Cisco Catalyst 6500/6800 Supervisor Engine 2T Introduction to Virtual Private LAN Service The Cisco Catalyst 6500/6800 Series Supervisor Engine 2T supports virtual
WHITEPAPER MPLS: Key Factors to Consider When Selecting Your MPLS Provider INTRODUCTION Multiprotocol Label Switching (MPLS), once the sole domain of major corporations and telecom carriers, has gone mainstream
COMP9333 Advance Computer Networks Mini Conference QoS issues in Voice over IP Student ID: 3058224 Student ID: 3043237 Student ID: 3036281 Student ID: 3025715 QoS issues in Voice over IP Abstract: This
Private IP Overview Private IP is a network-based virtual private network (VPN) enabling customers to effectively communicate over a secure network. It also provides the foundation for automating business
Res. Lett. Inf. Math. Sci., 2005, Vol. 7, pp 19-27 19 Available online at http://iims.massey.ac.nz/research/letters/ Performance of voice and video conferencing over ATM and Gigabit Ethernet backbone networks
Bandwidth Aggregation Redundant WAN Link and VPN Fail-Over Solutions Find your network example: 1. Basic network with and 2 WAN lines - click here 2. Add a web server to the LAN - click here 3. Add a web,
Taking a Peek Into Virtual Private Networks Backbone POP Internet Copyright 2001-2002 Global TechPro. All rights reserved. Joseph Alvarez Global TechPro, LLC 5659 Columbia Pike #200 Falls Church, Virginia
Blue 102 IP Service Architecture Futures Geoff Huston May 2000 Next Wave IP Services Service Requirements Connectivity service for customer-operated routers Service payload is IP packet High peak carriage
Kingston University London Thesis Title Implementation and performance evaluation of WAN services over MPLS Layer-3 VPN Dissertation submitted for the Degree of Master of Science in Networking and Data
WHITE PAPER ANALYZING MPLS FROM AN ROI PERSPECTIVE Analyzing MPLS from an ROI Perspective Site Interconnection In most cases, a Virtual Private Network (VPN) is considered a means of connecting various
WAN Data Link Protocols In addition to Physical layer devices, WANs require Data Link layer protocols to establish the link across the communication line from the sending to the receiving device. 1 Data
Hitachi Review Vol. 48 (1999), No. 4 203 GR2000: a Gigabit Router for a Guaranteed Network Kazuo Sugai Yoshihito Sako Takeshi Aimoto OVERVIEW: Driven by the progress of the information society, corporate
How Virtual Private Networks Work by Jeff Tyson This article has been reprinted from http://computer.howstuffworks.com/ Please note that the web site includes two animated diagrams which explain in greater
World of Computer Science and Information Technology Journal (WCSIT) ISSN: 2221-0741 Vol. 2, No. 3, 110-114, 2012 Performance Evaluation for VOIP over IP and MPLS Dr. Reyadh Shaker Naoum Computer Information
Transport for Enterprise VoIP Services Introduction Many carriers are looking to advanced packet services as an opportunity to generate new revenue or lower costs. These services, which include VoIP, IP
Network Working Group Request for Comments: 2547 Category: Informational E. Rosen Y. Rekhter Cisco Systems, Inc. March 1999 BGP/MPLS VPNs Status of this Memo This memo provides information for the Internet
White Paper The Essential Guide to Deploying MPLS for Enterprise Networks Daniel Backman Systems Engineer Troy Herrera Sr. Field Solutions Manager Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale,
Whitepaper WAN Traffic Management with PowerLink Pro100 Overview In today s Internet marketplace, optimizing online presence is crucial for business success. Wan/ISP link failover and traffic management
Scientific Bulletin of the Electrical Engineering Faculty Year 11 No. 2 (16) ISSN 1843-6188 EXPERIMENTAL STUDY FOR QUALITY OF SERVICE IN VOICE OVER IP Emil DIACONU 1, Gabriel PREDUŞCĂ 2, Denisa CÎRCIUMĂRESCU