Dell PowerStore 5200T EMC PowerStore Host Configuration Guide - Page 59

Policy-Based Routing, Bonding/Teaming, Steps, Description, IP Address

Page 59 highlights

In light of this limitation, use one of the following solutions to make both network interfaces accessible with hosts that are connected to PowerStore storage with PowerStore operating system 1.x: ● Policy-Based Routing ● Bonding/Teaming ● Disable Reverse Path Filtering Steps 1. Dell recommends creating four target iSCSI IP addresses (two per node) on the same subnet/VLAN. 2. Configure two iSCSI interfaces on the same subnet as the storage cluster iSCSI portals. Example: Description Host (NIC-0) Host (NIC-1) Node-A-Port0 Node-A-Port1 Node-B-Port0 Node-B-Port1 IP Address 1.1.1.10/24 1.1.1.11/24 1.1.1.1/24 1.1.1.2/24 1.1.1.3/24 1.1.1.4/24 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, see RedHat Knowledge Article 30564 (How to connect...). Bonding/Teaming Use bonding/teaming as a solution to the single network subnet limitation. NOTE: This 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 technical information about configuring network bond on Red Hat Enterprise Linux version 7, see Networking Guide: Configure Network Bonding. Host Configuration for Linux 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93

In light of this limitation, use one of the following solutions to make both network interfaces accessible with hosts that are
connected to PowerStore storage with PowerStore operating system 1.x:
Policy-Based Routing
Bonding/Teaming
Disable Reverse Path Filtering
Steps
1.
Dell recommends creating four target iSCSI IP addresses (two per node) on the same subnet/VLAN.
2.
Configure two iSCSI interfaces on the same subnet as the storage cluster iSCSI portals.
Example:
Description
IP Address
Host (NIC-0)
1.1.1.10/24
Host (NIC-1)
1.1.1.11/24
Node-A-Port0
1.1.1.1/24
Node-A-Port1
1.1.1.2/24
Node-B-Port0
1.1.1.3/24
Node-B-Port1
1.1.1.4/24
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, see
RedHat Knowledge Article 30564 (How to connect...)
.
Bonding/Teaming
Use bonding/teaming as a solution to the single network subnet limitation.
NOTE:
This 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 technical information about
configuring network bond on Red Hat Enterprise Linux version 7, see
Networking Guide: Configure Network Bonding
.
Host Configuration for Linux
59