Configuring Control Of Secondary Interfaces in HA Deployments
If you use iSCSI and a dedicated network interface in a high-availability (HA) deployment, you must ensure that the secondary interface is not managed by the HA process. Configure the management of the secondary interface to ensure that in the event of a failover to the secondary HA host, the interface always remains active.
Ensure that the following conditions are met:
Separate IP addresses for the dedicated iSCSI network interface on each of the HA servers.
Separate IP addresses prevent IP address conflicts when the network interfaces are active on both HA hosts at the same time. The iSCSI software and drivers can access the external storage at startup and during the HA failover. Also, the external volume can be successfully mounted when the HA node switches from standby to active.
The primary and secondary appliances are configured.
For more information, see the Juniper Secure Analytics High Availability Guide.
iSCSI storage is configured.
NetworkManager is disabled by typing the command systemctl status NetworkManager
- On the primary host, use SSH to log in to the JSA console as the root user.
- Disable the JSA HA service
control of network interface.
Go to the
The directory contains a list of files that are named
ifcfg-ethN. One file exists for each interface that is controlled by JSA HA processes.
Delete the file that is used to access your ISCSI storage network.
Deleting the file removes control of the interface from the HA processes.
- Re-enable operating system-level control of the network
Go to the
ifcfg-ethNfile for the interface that connects to your ISCSI network.
To ensure that the network interface is always active, change the value for the
- To restart the iSCSI services, type the following command:
systemctl restart iscsi
- Repeat these steps for the HA secondary appliance.
- Optional: To test access to your ISCSI storage from your
secondary appliance, use the ping command: