Cannot select an RCIP port to create a link

Symptom

When setting up a Remote Copy configuration or trying to add a link in HPE SSMC, an RCIP port cannot be selected.

In this example, node:slot:port 1:1:1 cannot be selected. Use CLI commands to troubleshoot. See the HPE Primera OS Command Line Interface Reference Guide for more information.

If necessary, obtain IP addresses, netmask, and gateway information from your network administrator.

Action

Source storage system

  1. Log in to the source storage system.
  2. Determine if the port is configured for RCIP.
    cli% showport
    N:S:P      Mode   State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner FailoverState
    0:0:1 initiator   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx disk      SAS  DP-1       -             -
    0:0:2 initiator   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx disk      SAS  DP-2       -             -
    0:1:1      peer   ready                -       xxxxxxxxxxxx rcip       IP      -       -     -
    0:2:1      peer offline                -       xxxxxxxxxxxx free       IP      -       -     -
    0:3:1    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   1:3:1          none
    0:3:2    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   1:3:2          none
    0:3:3    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   1:3:3          none
    0:3:4    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   1:3:4          none  
    0:4:1    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   1:4:1          none
    0:4:2    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   1:4:2          none
    0:4:3    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   1:4:3          none
    0:4:4    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   1:4:4          none
    1:0:1 initiator   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx disk      SAS  DP-1       -             -
    1:0:2 initiator   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx disk      SAS  DP-2       -             -
    1:1:1      peer offline                        xxxxxxxxxxxx rcip       IP     -       -
    1:2:1      peer offline                        xxxxxxxxxxxx free       IP     -       -             -
    1:3:1    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   0:3:1          none
    1:3:2    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   0:3:2          none
    1:3:3    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   0:3:3          none
    1:3:4    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   0:3:4          none
    1:4:1    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   0:4:1          none
    1:4:2    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx host       FC     -   0:4:2          none
    1:4:3    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   0:4:3          none
    1:4:4    target   ready xxxxxxxxxxxxxxxx   xxxxxxxxxxxxxxxx free       FC     -   0:4:4          none
    
    1. If the Type is rcip, go to the next step.
    2. If the Type is not rcip, set the RCIP address and netmask for the port. If the Protocol is not IP, find a free IP port and then set the address and netmask.
      cli% controlport rcip addr -f <IP_address> <netmask> <N:S:P>
  3. Determine if the port is ready.
    cli% showport -rcip
    N:S:P State ---HwAddr---        IPAddr       Netmask Gateway    MTU  Rate Duplex AutoNeg
    0:1:1 ready xxxxxxxxxxxx 10.xxx.10.101 255.255.255.0 10.100.0.1 1500 1Gbps   Full     Yes
    1:1:1 -     xxxxxxxxxxxx 10.xxx.10.102 255.255.255.0          - 1500 1Gbps   Full     Yes
    --------------------------------------------------------------------------------------
    
    1. If the State is ready, go to the next step.
    2. If the State is ready and the Gateway is not blank, verify the netmask and gateway with your network administrator.
    3. If the State is not ready and the Gateway is blank, assign the gateway.
      cli% controlport rcip gw -f <gateway_address> <N:S:P>
  4. Determine if you can connect to the target storage system.
    cli% controlport rcip ping <IP_address> <N:S:P>
    Where:
    • <IP_address>—The IP address of the target system. In this example, 10.xxx.50.110.

    • <N:S:P>—The node, slot, and port. In this example, 1:1:1.

    PING 10.xxx.50.110 (10.xxx.50.110) from 10.xxx.10.102 : 56(84) bytes of data.
    From 10.xxx.50.110 icmp_seq=1 Destination Host Unreachable
    From 10.xxx.50.110 icmp_seq=2 Destination Host Unreachable
    From 10.xxx.50.110 icmp_seq=3 Destination Host Unreachable
    From 10.xxx.50.110 icmp_seq=4 Destination Host Unreachable
    
    1. If the ping fails (destination is unreachable), go to the next step.
    2. If the ping succeeds (packets are transmitted), select the port again. If the problem continues, go to the next step.

Target storage system

  1. Log in to the target storage system.
  2. Repeat the previous steps on the target system.
    1. If the controlport rcip ping command succeeds, select the port again. If the problem continues, contact your network administrator.
    2. If the controlport rcip ping command does not succeed, see "The controlport rcip ping command does not succeed".