Powered by Zoomin Software. For more details please contactZoomin

WAF Administration Guide

Source Type
Application Security
Data Security
Network Security
Application Performance
Product Versions
Hypervisor Installation
Document Type
Access
Product Area
This guide
Table of Contents

Creating SSH Trust

 Creating SSH Trust

To load the configuration of the primary server onto the secondary server without having to enter a password each time, you need to create a trusted SSH connection between the two servers. This section provides the procedure for the AWS environment and for other environments.

AWS environment

To create a trusted SSH connection between the primary and secondary MX servers (on an AWS environment):

  1. Open an SSH connection to the secondary MX server.
  2. Login using root credentials.
  3. Manually configure a trusted SSH root connection between the MXs.
  4. Open an SSH connection to the primary MX server.
  5. Login using root credentials.
  6. Run the following command to set up the folder structure and allow the mxserver user to connect to the MX-DR:

    impctl server dr create --ip=<secondary server IP address>

    A confirmation message stating the connection was successfully set is displayed.

  7. Perform the procedure described in Loading Licenses.

Other environments

To create a trusted SSH connection between the primary and secondary MX servers (on a non-AWS environment):

  1. Open an SSH connection to the secondary MX server.
  2. Login using root credentials.
  3. Run the following command to enable the primary MX server to connect as root to the secondary MX server:

    impctl hardening config --root-source-ip-exception=<primary server IP address>

  4. Open an SSH connection to the primary MX server.
  5. Login using root credentials.
  6. Run the following command to set up the folder structure and allow the mxserver user to connect to the MX-DR:

    impctl server dr create --ip=<secondary server IP address>

  7. Type the password of the secondary MX server and hit Enter.
  8. A confirmation message stating the connection was successfully set is displayed.
  9. Perform the procedure described in Loading Licenses.
Was this topic helpful?