|
Problem IC68697
|
Status: Closed |
FCM SENDER IS NOT SELECTING DESIGNATED NETWORK INTERFACE TO SEND DATA |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If multiple network interfaces are available on a machine with
multiple logical partitions (MLNs), and each logical partition
is specified to use a designated network interface for
inter-partition communication (ie, via the netname column in
db2nodes.cfg), DB2 may not choose the designated network
interface to send data across partitions; it would instead let
the operating system (OS) choose interfaces that are deemed
appropriate to use. Depending on the actual workloads, this
behavior can potentially be suboptimal for send traffic if the
OS chose a single interface (or only a small subset) for all
logical partitions rather than fully utilizing all available
ones. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All of these criteria must be present for the problem to *
* occur: *
* - DPF *
* - MLNs *
* - multiple network interfaces on a machine *
* - user configured each logical partition to use a different *
* network interface (ie, via the netname column in *
* db2nodes.cfg). *
****************************************************************
* PROBLEM DESCRIPTION: *
* If multiple network interfaces are available on a machine *
* with *
* multiple logical partitions (MLNs), and each logical *
* partition *
* is specified to use a designated network interface for *
* *
* inter-partition communication (ie, via the netname column in *
* *
* db2nodes.cfg), DB2 may not choose the designated network *
* *
* interface to send data across partitions; it would instead *
* let *
* the operating system (OS) choose interfaces that are deemed *
* *
* appropriate to use. Depending on the actual workloads, this *
* *
* behavior can potentially be suboptimal for send traffic if *
* the *
* OS chose a single interface (or only a small subset) for all *
* *
* logical partitions rather than fully utilizing all available *
* *
* ones. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97fp3 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in v97fp3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68775
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.05.2010
16.09.2010
16.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
