2.
Enter a name for the connection.
3.
Use the drop-down menus to select
IKEv2
for the IKE version and either
Start
,
Add
or
Ignore
for the Boot Action.
a. Start - loads a connection and brings it up immediately (boot up, or after saving the configuration).
b. Add - loads a connection without starting it. For example, the VPN can be conditionally started with a
script.
c. Ignore - ignores the connection
4. For the Remote (Right) Side, enter the following parameters:
a. Leave the ID field blank.
b. Enter the IP address of the remote VPN in the IP Address field.
c. Enter the subnet the console server will use to connect through in the SubNet field.
5.
For the Local (Left) Side, enter the following parameters:
a. Leave the ID field blank.
b. Enter the IP address of the primary interface in the IP Address field.
NOTE: The primary interface is the interface (etho or eth1) used to connect to the remote firewall. By default, the
setting is eth0 and Bootp Configuration Retrieval is enabled. If your primary interface is eth1, make sure the Bootp
Configuration Retrieval on the Security Profile page is disabled.
6. Click the RSA Certificate radio button, click the Local PKCS12 Files drop-down arrow and select the PKCS12
file.
To enable IPSec on the console server:
1.
From the sidebar of the
Expert
tab, click
System - Security - Security Profile
.
2.
Click the Custom radio button under Security Profile.
3.
Check the Enable IPSec box, then click
Save
.
NOTE: After the Save button is clicked, the VPN connection starts automatically if the Boot Action is Start. The
information is saved and the VPN starts (or restarts).
Verification
Verification tests can be performed to ensure the IPSec configuration was successful. The ping command is used to test
communication.
To verify the IPSec status and test communication:
1.
Log in to the console server as root.
2.
Check the status of the IPSec by entering the command
ipsec status
at the Shell prompt. Note the VPN
DHCP IP address.
3.
Enter ping at the command prompt, press the Space bar, enter the address you’d like to ping and then press
the Enter key on your keyboard and wait for the ping results..Test the communication from the console server to
the remote subnet's target client.
4. Test the communication from the remote subnet's target client to the VPN DHCP IP address of the console
server.
NOTE: To test communication, enter ping from the target client to the VPN DHCP IP address the console server and
from the console server to the subnet's target client.
Vertiv™ | Avocent® ACS800/8000 Advanced Console Server Installer/User Guide
32
