Invalid RCFC link due to bad zoning

Symptom

An RCFC link cannot be created. Performing the steps in Unable to create RCFC link due to incorrect connection or zoning did not resolve the issue.

Cause

The ports of the connecting storage systems are not physically zoned together.

Action

Source storage system

Determine if the ports are ready.

showrctransport -rcfc

N:S:P Peer_Node_WWN    Peer_Port_WWN    State
0:3:1 2FF7xxxxxx07E990 2231xxxxxx07E990 ready
1:3:1 2FF7xxxxxx07E990 2231xxxxxx07E990 new
2:3:1 2FF7xxxxxx07E990 2231xxxxxx07E990 incomplete

If the State is ready, go to the next port.
If the State is not ready, go to the next step.

Verify that the fabric zoning is one-to-one.

Check each port. For example, 0:3:1.

cli% showportdev all 0:3:1

    PtId LpID  Hadr ----Node_WWN---- -Port_WWN/HW_Addr- ftrs   svpm   bbct   flen   -----vp_WWN----- Name
0xae0080 0x00  0x00 2FF7xxxxxx07E990 2031xxxxxx07E990   0x8800 0x0032 n/a    0x0800 2031xxxxxx07E990 0:3:1
0xce0400 0x02  n/a  2FF7xxxxxx07E991 2031xxxxxx07E991   0x0000 0x0032 0x0000 n/a    2031xxxxxx07E990 -
----------------------------------------------------------------------------------------------------------
       2 total

In this example, the zoning is correct. Zoning is one-to-one: the only ports in the zone are one port from the primary site and one port from the secondary site.

Check the next port. For example, 2:3:1.

cli% showportdev all 2:3:1

   PtId LpID  Hadr ----Node_WWN---- -Port_WWN/HW_Addr- ftrs   svpm   bbct   flen   -----vp_WWN----- Name
0x10a00 0x00  0x00 2FF7xxxxxx07E897 2033xxxxxx07E897   0x8800 0x0032 n/a    0x0800 2033xxxxxx07E897 2:3:1
0x20a00 0x02  n/a  2FF7xxxxxx07E896 2033xxxxxx07E896   0x0800 0x0032 0x0014 n/a    2033xxxxxx07E897 -
0x20e00 0x05  n/a  2FF7xxxxxx07E896 2034xxxxxx07E896   0x0000 0x0032 0x0000 n/a    2033xxxxxx07E897 -
0x20b00 0x06  n/a  2FF7xxxxxx07E896 2133xxxxxx07E896   0x0000 0x0032 0x0000 n/a    2033xxxxxx07E897 -
0x20f00 0x07  n/a  2FF7xxxxxx07E896 2134xxxxxx07E896   0x0000 0x0032 0x0000 n/a    2033xxxxxx07E897 -
---------------------------------------------------------------------------------------------------------
      5 total

In this example, multiple ports have been incorrectly zoned together.

Note each port that is incorrectly zoned.

Target storage system

Repeat steps 1-3 for each port on the target system.
Rezone the ports in a one-to-one configuration on the SAN switch.

Source storage system

For each port that was incorrectly zoned, dismiss the links.
1. Remove the Remote Copy link.
```
cli% dismissrcopylink <target_name> <N:S:P> <remote wwn>
```
  Where:
  - <target_name>—the name of the target created from this system.
  - <N:S:P>—the node:slot:port for this port.
  - <remote wwn>—the World Wide Name for the peer port on the other system.
2. Verify that the zoning is one-to-one.
```
cli% showportdev all N:S:P
```
  - If the zoning is not correct, repeat this procedure.
  - If the zoning is correct, continue to the next step.
For each port that was incorrectly zoned, reconfigure the ports.
1. Take the port on each node offline.
```
cli% controlport offline -f <N:S:P>
```
  Where:
  
  <N:S:P>—Location of the source system FC adapter port
2. Set the port connection mode and type on each node.
```
cli% controlport config rcfc -ct point -f <N:S:P> 
```
3. Initialize the port on each node.
```
cli% controlport rcfc init -f <N:S:P>
```

Target storage system

Repeat steps 6 and 7 for the target system.

Both systems

On both systems, verify that the ports are ready.

showrctransport -rcfc

N:S:P Peer_Node_WWN    Peer_Port_WWN    State
0:3:1 2FF70002AC07E990 22310002AC07E990 ready
1:3:1 2FF70002AC07E990 22310002AC07E990 ready
2:3:1 2FF70002AC07E990 22310002AC07E990 ready

Return to HPE SSMC and create the RCFC links.