text: Two Fibre Channel port masks are on a system. The local port mask controls connectivity to 
  other nodes in the same system; the partner port mask controls connectivity to nodes in 
  remote, partnered systems. By default, all ports are enabled for both local and partner 
  connectivity. 
  
  The port masks apply to all nodes on a system; a different port mask cannot be set on nodes 
  in the same system. You do not have to have the same port mask on partnered systems. 
  
  A mixed traffic of host, back-end, intracluster, and replication might cause congestion and 
  buffer to buffer credit exhaustion. This type of traffic can result in heavy degradation of 
  performance in your storage environment. 
  
  Fibre Channel I/O ports are logical ports, which can be on Fibre Channel platform ports or 
  FCoE platform ports. 
  
  The port mask is a 64-bit field that applies to all nodes in the cluster. In the local FC port 
  masking, you can set a port to be dedicated to node-to-node/intracluster traffic by setting a 1 
  to that port. Remote FC port masking allows you to set which ports can be used for replication 
  traffic by setting 1 to that port. 
  
  If a port has a 0 in the specific mask, it means no traffic of that type is allowed. Therefore, in a 
  local FC port map, a 0 means no node-to-node traffic occurs. A 0 on the remote FC port 
  masking means that no replication traffic occurs on that port. Therefore, if a port has a 0 on 
  local and remote FC port masking, only host and back-end storage traffic is allowed on it. 