Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Secondary Network Interfaces

You can configure a secondary network interface with a private IP address to connect to an iSCSI storage area network (SAN).

You use secondary network interface to improve performance. If you configure a secondary network interface, you require address information from your SAN network manager. For more information about configuring a network interface, see your Juniper Secure Analytics Administration Guide.

HA Systems in iSCSI Deployments

For dedicated access to the iSCSI storage network, use the following order to set up high availability (HA), iSCSI, and a network interface:

  1. Configure the primary and secondary appliances.

  2. Set up external iSCSI storage on both hosts.

  3. Configure HA on the primary and secondary hosts.

  4. Configure control of the secondary interfaces for your HA appliances.

The HA process for JSA controls the all network interfaces. When an HA appliance is in active mode, the HA process enables the interfaces. When HA is in standby mode, the HA process disables the interfaces. If the dedicated network interface for storage is disabled and the HA system goes into failover, the standby host tries to go into active mode. If the HA system is in standby mode, you cannot access the iSCSI storage system. Access issues are caused during the transition of the HA node from standby to active. The HA process brings the secondary interface online, but when the iSCSI system is mounted, the networking is not available and the failover process fails. The standby HA host cannot change to active mode.

To resolve the issue, you must remove control of the iSCSI network interface from the HA system to ensure that network interface is always active. Remove any dependencies that the network interface has on the status of the HA node. The HA primary and secondary hosts must have unique IP addresses on these secondary network interfaces.