|
Problem IC67845
|
Status: Closed |
DB2HAICU WON'T ALLOW 2 NETWORK EQUIVALENCIES TO HAVE THE SAME NETWORK INTERFACE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
If a network interface is a member of an exising network
equivalency, db2haicu won't allow that network interface to be
added to another network equivalency.
ie:
The network adapter bond0 on node etestadm01 is already defined
in network SA-nfsserver-nieq-1 and cannot be added to another
network until it is removed from its current network.
HA NFS creates its own network equivalency using the FCM
network. If db2haicu is run after ha nfs is setup, it won't be
able to create an FCM network equivalency and therefore won't be
able to create dependencies between the db2 partitons and the
FCM network.
From a TSA perspective, there is no reason why we can't have 2
or more network equivalencies using the same network interface. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2haicu users with existing TSA network equivalency *
* containing a NIC that is to be added to other network *
* equivalencies. *
****************************************************************
* PROBLEM DESCRIPTION: *
* db2haicu users with existing TSA network equivalency *
* containing a NIC that is to be added to other network *
* equivalencies. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.5.0.6, or use TSA commands to *
* create the network equivalency. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
If a network interface is a member of an exising network
equivalency, db2haicu won't allow that network interface to be
added to another network equivalency.
ie:
The network adapter bond0 on node etestadm01 is already defined
in network SA-nfsserver-nieq-1 and cannot be added to another
network until it is removed from its current network.
HA NFS creates its own network equivalency using the FCM
network. If db2haicu is run after ha nfs is setup, it won't be
able to create an FCM network equivalency and therefore won't be
able to create dependencies between the db2 partitons and the
FCM network.
From a TSA perspective, there is no reason why we can't have 2
or more network equivalencies using the same network interface. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67939 IC67962 IC67974
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.04.2010
14.05.2010
14.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.0.6
|
| Problem solved according to the fixlist(s) of the following version(s) |
