Avaya BCM 4.0 Networking Guide de configuration télécharger pdf (Page 649)

100

101

649

BCM 4.0 Networking Configuration Guide

Chapter 68

Virtual Private Networks (VPN)

BCM uses the Internet and tunneling protocols to create secure extranets. These secure extranets

require a protocol for safe transport from the BCM to another device through the Public Data

Network (PDN). BCM uses the IPSec (“IPSec” on page 651) tunneling protocol.

Extranets can connect:

• mobile users to a fixed private network at their office over the PDN

• private networks in the two branch offices of the same corporation over PDN

• two divisions of the same corporation over the corporate intranet

When connecting two branch offices, the use of a VPN over the public data network is very

efficient if the connection is required only intermittently or a dedicated point-to-point link is

considered too expensive. Also, with the advent of business-to-business solutions, VPNs can be

deployed to provide secure connections between corporations.

IPSec tunnel modes

In the IPSec Specification, there are two tunnel modes defined: tunnel mode and transport mode.

BCM supports only tunnel mode. Tunnel mode describes a method of packetizing TCP/IP traffic

to create a virtual tunnel.

Tunnels are created between servers, which are also known as gateways. This is called a Branch

Office Connection. The end nodes connect to each other through gateways. These gateways set up

the tunnel over the PDN on behalf of the end nodes. The establishment of the tunnel, and the PDN

in between, is transparent to the end nodes which behave as if they are interacting through a router.

Typically, the edge devices connecting the branches of a corporation to the ISP use VPN in this

mode.

BCM is compatible with the Extranet Switch and the Nortel Services Edge Router (formerly

known as Shasta 5000).

Refer to the following topics to configure the tunnel portion of BCM using IPSec.

IP Addresses and DHCP Server

Ensure that the IP addresses for the LAN interfaces, WAN interfaces, and dial up links are unique

across all sites. This simplifies configuration, eliminates conflicts due to NAT, and prevents the

addresses assigned by the DHCP server from conflicting with the IP addresses of subnets in

remote sites.

For information about how to change the DHCP Server settings, refer to the “Configuring DHCP”

on page 589.

1 2 ... 644 645 646 647 648 649 650 651 652 653 654 ... 757 758

Commentaires sur ces manuels

Pas de commentaire

Avaya BCM 4.0 Networking Guide de configuration Page 649

Commentaires sur ces manuels

Produits connexes et manuels pour Mise en réseau Avaya BCM 4.0 Networking