text: 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. 
  
  However, it might take some time for discovery and path configuration logic to reestablish 
  paths post-failover, and this delay might cause partnerships to change to the Not_Present 
  state. 
  
  This process can lead to remote copy relationships stopping, and 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). 
  
  This configuration has the following characteristics: 
  
  (cid:2) 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. 
  
  (cid:2) 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. 
  
  (cid:2) The discovery mechanism that is triggered because of failover might introduce a delay 
  wherein the partnerships momentarily change to the Not_Present state and then recover. 
  
  (cid:2) The bandwidth of the single link is used completely. 