Validating Ethernet partnerships configuration

You can validate the Ethernet partnerships configuration (short-distance and long-distance).

Validating IP (short-distance and long-distance) partnerships configuration

For configuring IP (short-distance and long-distance) partnership, you need to create a portset, add IP address to that portset, and then, assign this portset to new IP partnership. Hence, to validate this new IP partnership (short-distance and long-distance) configuration is running accurately, certain attribute needs to be checked.

To ensure that new IP (short-distance and long-distance) partnership is functioning correctly, run lspartnership command on each system in the configuration and complete the following checks:
Note: IP replication support is disabled on 100g ports.
  • Ensure that the partnership is in a Fully Configured state.
  • Ensure that backup IP addresses if available, are configured correctly for all the portsets that are used for the partnership.

Resolving a not_present state for an IP (long-distance and short-distance) partnership

The not_present state indicates that the remote system is not visible. This state can be caused by a problem with the connectivity between the local and remote system, the remote system is unavailable, or if the partnership was not configured correctly. You can use lspartnership command to check the status of partnerships.

Possible configuration mistakes of IP partnerships and several error codes can result in a not_present state. The system supports up to 3 IP partnerships and it is important to determine which system in the configuration that has faced connectivity issues. You can use the Events page in the management GUI to run dedicated fix procedures for these errors provide specific details on troubleshooting steps. You can also use the lseventlog command.
Configuration error that causes the not_present state
The IP addresses of the corresponding portsets from both the system are not mutually reachable. All the configured IP addresses for the portsets used while creating an IP partnership on one system should be reachable to the corresponding IP address on other system.
Error 2020 (long-distance partnerships only)
Error 2021 (short-distance and long-distance partnerships)
Error 2022 (short-distance and long-distance partnerships)
Error 2023 (short-distance and long-distance partnerships)

Complete the following steps to troubleshoot short-distance partnerships using RDMA configuration:

  1. Ensuring connectivity between links
    Ensure that all IP addresses associated with the link1 and link2 portsets on the primary IBM FlashSystem are connected with all IP addresses associated with the link1 and link2 portsets on the secondary IBM FlashSystem. The same can be validated as follows:
    • By using the GUI: Go to Settings > Network > >Ethernet Connectivity. Select the node and click Show Results.
    or
    • By using the CLI: Run the CLI command sainfo lsnodeipconnectivity on all the nodes of the system.
  2. Ensuring resilient configuration and maximum redundancy
    For a more resilient configuration and to have maximum redundancy, ensure that IP addresses configured on the ports for both the links are from different nodes.
  3. Further troubleshooting if partnership status is not fully_configured
    In case the partnership status, is anything but fully_configured, further troubleshooting is required to understand why there is change in partnership. Here are some of the partnerships states and ways to troubleshoot:
    Partnership is not_present state
    An IP partnership can transition to not_present state due to multiple reasons and it means that the replication services have come to a halt. Check for alerts, warnings, or errors that are associated with partnership by using the lseventlog CLI command or select Monitoring > Events tab in the GUI to view the list of events pertaining to the changes that have occurred in the system.
    Check whether there are issues with sessions established
    Run the command sainfo lsnodeipconnectivity on all the nodes of the system to understand if there are any issues with the sessions established. The session status should ideally be Connected but apart from this state, other possible states include Protocol mismatch, Degraded, or Unreachable. The output is as follows:
    CabaroN1:~ # sainfo lsnodeipconnectivity 01-1
status     local_port_id local_vlan local_rdma_type local_ip_addr remote_port_id remote_vlan remote_rdma_type remote_ip_addr remote_wwnn   remote_panel_name cluster_id    error_data
Connected:iWARP 3            iWARP      xx.xx.xx.xx  6             iWARP      xx.xx.xx.xx  500507681000110C 01-1       0000020435202218
CabaroN1:~ # sainfo lsnodeipconnectivity 01-2
status     local_port_id local_vlan local_rdma_type local_ip_addr remote_port_id remote_vlan remote_rdma_type remote_ip_addr remote_wwnn   remote_panel_name cluster_id    error_data
Connected:iWARP 3            iWARP      xx.xx.xx.xx  6             iWARP      xx.xx.xx.xx  5005076810001143 01-2       0000020435202218
    For more information on errors, see: Error 2024 (short-distance partnerships only)
  4. Check reachability to system
    While reference of event logs and DMPs from the GUI are the recommended way to resolve any issue pertaining to the IBM FlashSystem, an alternate way is to verify connectivity to the remote system by checking reachability to the system.
    • Check the connectivity to the remote cluster by using the svctask ping command:

      For IPv4: svctask ping -srcip4 <source_ip> <destination_ip>

      For IPv6: svctask ping6 -srcip6 <source_ip> <destination_ip>

Resolving a mkippartnership command failure

The mkippartnership command defines a new partnership (short-distance and long-distance) that is created over intersite WAN links. The mkippartnership might fail because of empty portsets and correct IP address not selected.

To fix failure of mkippartnership command complete these checks:
  • Empty portsets leads to failure of mkippartnership command, hence associated IP addresses must be configured and mapped to the corresponding portsets before using them with mkippartnership command.
  • A system that is running on version 8.4.2.x or later can partner with only one of three systems from version less than 8.4.2.x. The mkippartnership command fails if any attempt is made to establish IP partnership with more than one system that is running on version less than 8.4.2.x. Hence, try to restrict the IP partnership with only one system running on version lesser than 8.4.2.x if multiple IP partnerships are intended.
  • The mkippartnership command fails while creating an IP partnership (short-distance and long-distance), in case either of the systems participating in the partnership fail to specify link1 or link2 on both the sides. Both systems must specify either link1 or link2 on both sides to establish a partnership.)
  • The mkippartnership command fails while creation of IP partnership with a dual portsets. This happens when each portset ID or portset name is specified twice while executing mkippartnership command on each system. Hence, use different available portset ID or portset name while executing the mkippartnership command on each system.

Even after following the troubleshooting procedure, if the issue still is not resolved, raise a support ticket with IBM for further assistance.