•
email.
Uses TCP ports 25, 110 and 443.
•
telnet.
Uses TCP port 23.
•
ssh.
Uses TCP port 22.
•
ftp.
Uses TCP ports 20 and 21.
•
smb.
Uses TCP port 139.
•
fileshare.
Uses TCP ports 20, 21 and 139.
Joining a VPN Gateway to an Existing Cluster
After having installed the first VPN Gateway in a cluster, additional AVGs may be added to the
same cluster by specifying the Management IP address (MIP) that identifies the cluster. When
you are installing the VPN Gateway to join an existing cluster, less information is needed
because the new VPN Gateway will fetch most of the configuration from the other AVG(s) in
the cluster.
The following applies when joining a new VPN Gateway to an existing cluster:
• If the VPN Gateway you are about to join is installed on a different subnet than existing
AVGs, this new device must be configured as a slave. Master AVGs cannot exist on
different subnets.
• If the Access list consists of entries (for example, IP addresses for control of Telnet and
SSH access), also add the cluster's MIP, the existing VPN Gateway's host IP address on
Interface 1, and the host IP address you have in mind for the new AVG to the Access list.
This must be done before joining the new VPN Gateway, otherwise the devices will not
be able to communicate. Use the
/cfg/sys/accesslist
command. If the Access list
is empty, this step is not required.
• If the VPN Gateway you are about to join has a different software version than existing
AVGs, install the preferred software version on the new VPN Gateway before joining it
(see
Reinstalling the Software
on page 66) or upgrade the whole cluster to the same
software version as the new VPN Gateway (see
Performing Minor/Major Release
Upgrades
on page 69). Use the
/boot/software/cur
command to check the
currently installed software version.
Setting up a One-Armed Configuration
If the currently installed VPN Gateway(s) in the cluster are set up for a one-armed configuration
you probably want the new VPN Gateway to be set up similarly.
When you log in after having started the VPN Gateway the first time, you will enter the Setup
menu.
1. Choose
join
from the Setup menu to add a VPN Gateway to an existing cluster.
Joining a VPN Gateway to an Existing Cluster
User Guide
April 2013 51
Summary of Contents for 3050-VM
Page 1: ...User Guide Avaya VPN Gateway Release 9 0 NN46120 104 Issue 04 04 April 2013 ...
Page 4: ...4 User Guide April 2013 Comments infodev avaya com ...
Page 12: ...12 User Guide April 2013 ...
Page 20: ...New in this release 20 User Guide April 2013 Comments infodev avaya com ...
Page 30: ...Introducing the VPN Gateway 30 User Guide April 2013 Comments infodev avaya com ...
Page 36: ...Introducing the ASA 310 FIPS 36 User Guide April 2013 Comments infodev avaya com ...
Page 74: ...Upgrading the AVG Software 74 User Guide April 2013 Comments infodev avaya com ...
Page 86: ...Managing Users and Groups 86 User Guide April 2013 Comments infodev avaya com ...
Page 130: ...The Command Line Interface 130 User Guide April 2013 Comments infodev avaya com ...
Page 162: ...Supported Ciphers 162 User Guide April 2013 Comments infodev avaya com ...
Page 212: ...Syslog Messages 212 User Guide April 2013 Comments infodev avaya com ...
Page 242: ...Definition of Key Codes 242 User Guide April 2013 Comments infodev avaya com ...
Page 259: ...Creating a Port Forwarder Authenticator User Guide April 2013 259 ...
Page 266: ...Using the Port Forwarder API 266 User Guide April 2013 Comments infodev avaya com ...
Page 274: ...X 509 274 User Guide April 2013 Comments infodev avaya com ...