Setting up a RoCE network in a GDPC environment (AIX)

On an AIX® operating system, when configuring a geographically dispersed DB2® pureScale® cluster (GDPC) environment on a RoCE network, you must create a relationship from the CF resource to the public network equivalency.

To set up a RoCE network in a GDPC environment:

1. Update the network.
   1. Update the public network equivalency to include the CF hosts. For example:

      $ chequ -u a db2_public_network_${DB2INSTANCE}_0 IBM.NetworkInterface:<ethernet adapter>:<CF 128 host>
      $ chequ -u a db2_public_network_${DB2INSTANCE}_0 IBM.NetworkInterface:<ethernet adapter>:<CF 129 host>

   2. Show the updated public network equivalency with lsequ -e, then verify the CF hosts' <ethernet adapters> are present. For example:

      root@pscalep74007b:/> lsequ -e db2_public_network_jabrum1_0
      Displaying Equivalency information:
      For Equivalency "db2_public_network_jabrum1_0".
      
      Equivalency 1:
              Name                      = db2_public_network_jabrum1_0
              MemberClass               = IBM.NetworkInterface
              Resource:Node[Membership] = {en0:pscalep74007b.torolab.ibm.com,en0:
      pscalep74008b.torolab.ibm.com,en0:pscalep74007c.torolab.ibm.com,en0:
      pscalep74008c.torolab.ibm.com,en0:pscalep74007a.torolab.ibm.com,en0:
      pscalep74008a.torolab.ibm.com}
              SelectString              = ""
              SelectFromPolicy          = ANY
              MinimumNecessary          = 1
              Subscription              = {}
              Color                     = 0
              ActivePeerDomain          = db2domain_20140219133937
              ConfigValidity            =

2. Create relationship.
   1. Create a relationship from the CF resource to the public network equivalency. For example:

      $ rgreq -o lock ca_${DB2INSTANCE}_0-rg
      $ mkrel -p DependsOn -S IBM.Application:ca_${DB2INSTANCE}_0-rs -G IBM.Equivalency:db2_public_network_$
      {DB2INSTANCE}_0 ca_${DB2INSTANCE}_0-rs_DependsOn_db2_public_network_${DB2INSTANCE}_0-rel
      $ rgreq -o unlock ca_${DB2INSTANCE}_0-rg

   2. Show the newly created relationship with lsrel -M <relationship name>. For example:

      $> lsrel -M ca_jabrum1_0-rs_DependsOn_db2_public_network_jabrum1_0-rel
      Displaying Managed Relationship Information:
      For Managed Relationship "ca_jabrum1_0-rs_DependsOn_db2_public_network_jabrum1_0-rel".
      
      Managed Relationship 1:
              Name                        = ca_jabrum1_0-rs_DependsOn_db2_public_network_jabrum1_0-rel
              Class:Resource:Node[Source] = IBM.Application:ca_jabrum1_0-rs
              Class:Resource:Node[Target] = {IBM.Equivalency:db2_public_network_jabrum1_0}
              Relationship                = DependsOn
              Conditional                 = NoCondition
              ConfigValidity              =
              ResourceGroup[Source]       = ca_jabrum1_0-rg

   3. 
      
3. Validate the resource model with the db2cluster command and db2instance command. For example:

   $> db2cluster -verify -resources
   Cluster manager resource states for the DB2 instance are consistent.
   
   $> db2instance -list
   ID   TYPE     STATE    HOME_HOST      CURRENT_HOST   ALERT  PARTITION_NUMBER  LOGICAL_PORT   NETNAME
   --   ----     -----    ---------      ------------   -----  ----------------  ------------   -------
   0    MEMBER   STARTED  pscalep74007b  pscalep74007b     NO                 0             0   pscalep74007b-ro0
   1    MEMBER   STARTED  pscalep74008b  pscalep74008b     NO                 0             0   pscalep74008b-ro0
   2    MEMBER   STARTED  pscalep74007c  pscalep74007c     NO                 0             0   pscalep74007c-ro0
   3    MEMBER   STARTED  pscalep74008c  pscalep74008c     NO                 0             0   pscalep74008c-ro0
   128  CF       PRIMARY  pscalep74007a  pscalep74007a     NO                 -             0   pscalep74007a-ro0
   129  CF       PEER     pscalep74008a  pscalep74008a     NO                 -             0   pscalep74008a-ro0
   
   HOSTNAME                   STATE           INSTANCE_STOPPED        ALERT
   --------                   -----           ----------------        -----
   pscalep74008a             ACTIVE                         NO           NO
   pscalep74007a             ACTIVE                         NO           NO
   pscalep74008c             ACTIVE                         NO           NO
   pscalep74007c             ACTIVE                         NO           NO
   pscalep74008b             ACTIVE                         NO           NO
   pscalep74007b             ACTIVE                         NO           NO

4. Ensure the updated network equivalency is reflected in the lssam command output . For example:

   $>  lssam | grep -i network
   Online IBM.Equivalency:db2_public_network_jabrum1_0
           |- Online IBM.NetworkInterface:en0:pscalep74007b
           |- Online IBM.NetworkInterface:en0:pscalep74008b
           |- Online IBM.NetworkInterface:en0:pscalep74007c
           |- Online IBM.NetworkInterface:en0:pscalep74008c
           |- Online IBM.NetworkInterface:en0:pscalep74007a
           '- Online IBM.NetworkInterface:en0:pscalep74008a