DB2 Version 10.1 for Linux, UNIX, and Windows

Adding communication adapter ports to a CF or member

Cluster caching facilities (CFs) and members support multiple communication adapter ports. Using multiple communication adapter ports provide greater scalability and availability. This task describes how to add a communication adapter port.

Before you begin

Read the Network topology configuration considerations for DB2 pureScale environments.
Log in as a user with root authority on a host in the DB2 pureScale instance.

About this task

Adding communication adapter ports helps achieve the following goals:

Increase bandwidth to handle more requests by using more than one communication adapter port.
Enable the adoption of network topologies with multiple switches.

Restrictions

A maximum of four communication adapter ports can be used on each CF or member. Communication adapter ports with one or two ports are supported.
On supported AIX® operating systems, a CF or member with more than one communication adapter port must be on its own physical host (or LPAR on AIX).

Procedure

To enable additional communication adapter ports:

Attach an extra interconnect cable from the switch to an open communication adapter port on the CF or member.
Configure the IP address and the associated cluster interconnect netname.
Repeat steps 1 - 2 for any additional ports you plan to use.
To update the CF or member with the additional cluster interconnect netname configured in the preceding step, run the db2iupdt -update command on each CF or member with the additional port.
For example, to update the CF:
```
db2iupdt -update -cf <cfHostname> -cfnet <cfnet0,cfnet1> <instanceName>
```
To update a member:
```
db2iupdt -update -m <memberHostname> -mnet <membernet0,membernet1> <instanceName>
```

Results

The cluster caching facility or member now communicates through each communication adapter port by using the registered cluster interconnect netnames.

Example

Updating a CF and member to use an additional communication adapter port on an InfiniBand network.

Before updating the CF or member, db2nodes.cfg contains:
```
0   memberhost0    0   membernet0
128 cfhost0        0   cfnet0
```
Note: Do not modify db2nodes.cfg directly.

Update the CF and member by running these commands:

db2iupdt -update -cf cfhost0 -cfnet cfnet0,cfnet1 <instanceName>
db2iupdt -update -m memberhost0 -mnet membernet0,membernet1 <instanceName>

After the updates, the db2nodes.cfg contains:

0   memberhost0    0   membernet0,membernet1
128 cfhost0        0   cfnet0,cfnet1

What to do next

Repeat the same procedure on the secondary CF or other members.