text: <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>−</td></tr></thead><tbody><tr><td>A single remote copy port group 1 is configured on two Ethemer ports, one each on Node A1 and Node A2 on System A. Similarly, a single remote copy port group is configured on two Ethemet ports on Node B1 and Node B2 on System B.</td></tr><tr><td>Alhough two ports on each system are configured for remote capy port group 1, only one Ethemed port in each system activity participates in the iff partnership process. This selection is determined by a path configuration algorithm thath</td></tr><tr><td>The other port on the partner note in the ITI - Group behaves as a standty port that is used if there is a note tailure. If sole A 1 fastle A 1 fast in System A, IF partnership confinues servicing replication I ’ O from Ethemet Port 2 because a failor</td></tr><tr><td>However, it might take some time for discovery and path configuration logic to reseablish paths post failorer. This delay can cause patherohips to change to : Present for that time. The details of the particular iP port that is actively par</td></tr><tr><td>This configuration has the following characteristics :</td></tr><tr><td>- Each node in the I / O proup has the same remote copy port group that is configured. However, only one port in that remote copy port group is active at any time at each system.</td></tr><tr><td>-- II the Node A1 in System A or the Node B2 in System B fals in the respective systems, iP partnerships rediscovery is triggeed and continues servicing the IIO hom the failover port.</td></tr><tr><td>-- The discovery mechanism that is triggered because of fallower might introduce a delay where the patherships momentantly change to the firt. J - resent state and recover.</td></tr><tr><td>Two 4 - node systems in IP partnership over a single inter - site link ( with failover ports configured ), as shown in Figure 11 - 100 on page 559 ( configuration 3 ).</td></tr></tbody>
          </table> </body> </html>