Switch failover capability is a high availability feature
provided by the configure Link Aggregate Control Protocol (LACP) on
the switch.
Before you begin
This configuration procedure is specific
to switches in environments with AIX systems, and to a remote direct
memory access (RDMA) over converged ethernet (RoCE) network. Switch
failover capability is a high availability feature that is provided
by configuring Link Aggregate Control Protocol (LACP) on the switches.
Before
you begin:
- Ensure
you have created your DB2® pureScale® Feature installation
plan. Your installation plan helps ensure that your system meets the
prerequisites and that you have performed the preinstallation tasks.
- Ensure you have read about supported network topologies for DB2 pureScale environments
in Network topology configuration support for DB2 pureScale environments.
- Power on the
switch and connect a serial cable or Ethernet cable to the switch.
About this task
The
procedure details steps for configuring two switches to support switch
failover. Switch failover capability helps the resiliency, or fault
tolerance, of a network.
To create a DB2 pureScale environment
with multiple switches, you must have multiple cluster interconnects
on CF servers
and configure switch failover on the switches.
Switch failover
configuration on a RoCE network requires the support of Link Aggregate
Control Protocol (LACP) on the switch.
Restrictions
- Administrative access is required on the switches.
Procedure
- Designate two or more ports on each switch to be used as
inter-switch links (ISLs).
- Connect the cables between the two switches.
- For all switches in the cluster, login and configure
the following. Refer to the switch manual for detailed steps:
- Disable the Converged Enhance Ethernet (CEE) feature.
- Ensure Global Pause (IEEE 802.3x) is enabled. For a BNT switch
with firmware level 6.5.2 and higher, port flow control must also
be enabled for Global Pause.
- Disable Spanning Tree Protocol (STP).
- Login to the switch and configure the following
for the ISL ports. Refer to the switch manual for detailed steps:
- Enable Link Aggregate Control Protocol (LACP).
- All ISL ports (on both switches) must be setup as active.
- If the switches are used for a RoCE network with IP support,
you must assign a pingable IP address on the switches.
These
IP addresses, which are assigned to the switch (as IP interfaces)
reside in the same IP subnet as the IP addresses that are used for
the hosts on the RoCE network. If the IP addresses
on the hosts are connected to the same switch but are in different
IP subnets, then each of those IP subnets must have a corresponding
IP address that is assigned to the switch that they are directly connected
to. When the setups of the host IP addresses are complete, you can
then ping the switch IP addresses from the hosts.
For example,
if the IP address 10.1.1.1 (with netmask 255.255.255.0) is assigned
on a host's en1 net interface and the IP address 10.1.2.1 is assigned
to the host's en2 net interface and each is connected to a different
switch, then IP address 10.1.1.24 can be assigned to switch 1 and
IP address 10.1.2.23 can be assigned to switch 2.
As a second
example, if 10.1.1.1 and 10.1.3.1 (with netmask 255.255.255.0) are
assigned on a host's en1 and en3, and they are connected to the same
switch (with 10.1.2.1 and 10.1.4.1 assigned to the host's en2 and en4, connected to a different switch). Then,
both 10.1.1.24 and 10.1.3.24 would be assigned to switch 1, and both
10.1.2.23 and 10.1.4.23 would be assigned to switch 2.
Example
What to do next
Configure the network settings of hosts that you plan
to include in the DB2 pureScale environment.
DB2 10.5 for Linux, UNIX, and Windows