Resolving a not_present state for an IP partnership

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. You can use lspartnership command to verify configuration errors.

Error 2020

This error can occur when remote copy link is unavailable. You can configure a maximum of three IP partnership from a system. To identify which partnership is in error state, the system shows 3 node errors 889, 890 and 891 corresponding to these partnerships such that 889 translates to first IP partnership and so on. All three node errors are mapped to the same error code 2020. To determine the remote partnership ID for which error is reported, look at the Node Error Data field in the properties and sense data of the reported event. To fix this event, complete these steps:

1. Verify the connection between to the systems with the svctask ping command. If ping works, there must be something that is blocking a specific port traffic. If ping does not work, there might be no route between the systems. Check the IP gateway configuration on the system nodes and the IP network configuration. If the error 2020 persists, continue to the next step.
2. In the management GUI, select Monitoring > Events.
3. To determine the partnership ID, right-click the error 2020 and select properties to verify the node error and the corresponding partnership. The node errors are displayed in the Event ID field.
4. Click Run Fix. In the fix procedure for the error, details are displayed about the local node that has the error, such as, the local port being used for the partnership. It also includes details about the remote system in the partnership. The following reasons can cause this error:
   • A firewall or switch has not been properly configured to enable communication over port 3265.
   • An external system is blocking access to port 3265.
   • Other LAN issues exist such as faulty switch cabling.

Error 2021

This error indicates that the cluster IP address for the partner system is unreachable. Use the fix procedure for the error in the management GUI. You can also complete the following steps to further troubleshoot this error:

1. Verify the connection between to the system with the svctask ping command. If ping works, there must be something that is blocking a specific port traffic. If ping does not work, there can be no route between the systems. Check the IP gateway configuration on the system nodes and the IP network configuration.
2. Check the configuration of the routers and firewall to ensure that TCP port 3260 used for IP partnership is not blocked.
3. Use the ssh command from another system to attempt to establish a session with the problematic remote system IP address to confirm that the remote system is operational. If the remote system cannot be reached, then log in to the remote system and investigate the cause of the outage.

Error 2022

The error occurs when authentication between the systems is not configured correctly. Use the fix procedure for the error in the management GUI. To ensure that authentication is configured correctly between the systems, complete these checks:

1. On all the systems in the partnership, ensure that the CHAP secret is the same.
2. Run the lssystem command on the primary system and verify the value in the -chapsecret is the same as the -chapsecret value in the results of lspartnership on the auxiliary system in the partnership.
3. If they are not the same, run the chpartnership command on the auxiliary system and change the value.