Figure 6-31 shows an eight-node system (System A in Site A) and a four-node system  (System B in Site B). A single remote copy port group 1 is configured on nodes A1, A2, A5,  and A6 on System A at Site A. Similarly, a single remote copy port group 1 is configured on  nodes B1, B2, B3, and B4 on System B. Although there are four I/O groups (eight nodes) in System A, any two I/O groups at maximum  are supported to be configured for IP partnerships. If Node A1 fails in System A, IP  partnership continues using one of the ports that is configured in remote copy port group from  any of the nodes from either of the two I/O groups in System A.  This process can lead to remote copy relationships stopping. The administrator must  manually start them if the relationships do not auto-recover. The details of which particular  IP port is actively participating in IP partnership process is provided in  lsportip  output  (reported as  used ).  However, it might take some time for discovery and path configuration logic to reestablish  paths post-failover. This delay might cause partnerships to change to the  Not_Present  state.  This configuration has the following characteristics:  GLYPH<SM590000> Each node has the remote copy port group that is configured in both the I/O groups that  are identified for participating in IP Replication. However, only one port in that remote copy  port group remains active on each system and participates in IP Replication.  GLYPH<SM590000> If the Node A1 in System A or the Node B2 in System B fails in the system, the  IP partnerships trigger discovery and continue servicing the I/O from the failover ports. GLYPH<SM590000> The discovery mechanism that is triggered because of failover might introduce a delay  where the partnerships momentarily change to the  Not_Present  state and then recover. GLYPH<SM590000> The bandwidth of the single link is used completely.  Chapter 6. Copy services  225