Avaya 3.7 User Manual

Page of 326
Device management
284 Avaya VPNmanager Configuration Guide Release 3.7
IPSec Engine Status - The IPSec Engine Status section shows the current state of the 
VSU-1200’s two packet processor engines (PPE). If either PPE fails, a FAILED status is 
displayed indicating which PPE failed. Both PPEs must be functional for the VSU-1200 to 
operate correcting. The PPEs and Ethernet cards are enclosed in a tamper-evident case and 
can only be serviced by an authorized technician. Contact your customer service representative 
for instructions on getting the VSU-1200 repaired.
Switching
To individually switch the active public or private ports, select which active ports to switch from 
and which passive ports to switch to, then click the Switch Ports button. Note that the active 
public and private ports can only be switched to passive ports of the same type. A public port 
cannot be switched to a private port or vice versa.
Importing and exporting VPN configurations to a device
A secure, inter-company extranet can be created by exporting a VPN configuration to a file that 
is then imported by other VPNmanager installations. Select Import VPN when you receive your 
exported VPN file and have it copied to a local directory. You will need the password from the 
exporting administrator.
Export VPN
Creating an extranet is a cooperative effort between system administrators running independent 
copies of VPNmanager and involves the same steps as creating any other VPN: create the 
VSUs, then the Groups and Clients, and finally the VPN.
The names chosen for VPN components must be synchronized within each corporation’s 
VPNmanager. This requires close coordination between the system administrators during the 
VPN component creation process and can be achieved by performing the following procedure:
The administrators at each corporation agree that all VPN components will be created by 
one of the administrators (the “exporting” administrator) and that the exporting 
administrator will create and deliver an export VPN configuration file to the other 
administrators (the “importing” administrators). 
The exporting administrator then creates security gateways, groups, users, and VPNs 
required, with the exception of the security gateways under management control of 
importing administrators. 
The VPN name must be unique to both the exporting and importing administrators’ 
VPNmanager databases.