Setup Guide

NOTE: The example below is based on RedHat. For details on configuring PowerStore disk device with iSCSI, refer to the

specific instructions of your operating system.

Parameter Description Value

node.session.timeo.replacement_timeout Specifies the number of seconds the iSCSI layer waits for a

timed-out path/session to re-establish before failing any

commands on that path/session. The default value is 120.

Using these settings prevents commands from being split by the iSCSI initiator and enables instantaneous mapping from the

host to the volume.

To apply the adjusted iscsid.conf settings, run the following command on the Linux host:

service iscsi restart

NOTE: If a previous iSCSI target is discovered on the Linux host, delete the iSCSI DB and rerun the iSCSI target discovery

procedure with the iscsid.conf setting described above.

Configuring the PowerStore Cluster Disk Device with iSCSI -

Single Network Subnet Support

This topic describes the issue of single subnet support for iSCSI target portals.

In PowerStore, only single network subnet is supported for the iSCSI target portals.

By design, on various Linux distributions, only two network interfaces can be configured on the same network subnet. For

details, refer to RedHat KB 30564 (https://access.redhat.com/solutions/30564) and RedHat KB 53031 (https://

access.redhat.com/solutions/53031).

In light of this limitation, use one of the following solutions to make both network interfaces accessible with hosts connected to

PowerStore storage:

● Policy-Based Routing (recommended)

● Bonding/Teaming

● Disable Reverse Path Filtering

Policy-Based Routing

This topic outlines policy-based routing as a solution to the single network subnet limitation (recommended solution).

This solution is based on adding routing tables and rules, binding source IP address for each route, and adding those as default

gateways for each network interface.

Using this solution, a routing table is defined for each interface, thus the default routing table is redundant for those interfaces.

For additional technical information on Policy-Based Routing, refer to https://access.redhat.com/solutions/30564.

Bonding/Teaming

This topic outlines bonding/teaming as a solution to the single network subnet limitation.

NOTE: The following section does not apply to hosts directly attached to the PowerStore appliances.

This solution is based on the Bond and Network teaming configuration.

● Bond - Binding multiple network interfaces into a single bonded channel enables them to act as one virtual interface. That

way, only a single network address is defined and the said limitation does not apply.

For additional technical information on configuring network bond on Red Hat Enterprise Linux 7, refer to https://

access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/ch-

configure_network_bonding.

● Network Teaming - With Red Hat Enterprise Linux 7, Network Teaming is offered as a new implementation of the bonding

concept. The existing bonding driver is unaffected.

Host Configuration for Linux