4245 Partition IP configuration failed.

Explanation

When the active management system is switched from failover or to failback being the preferred management system in a policy-based high availability configuration, the configuration node of the newly assigned active management system takes on the partition IP address of the partition and assigns it to the first Ethernet port configured in the SystemManagement portset. This event is logged by the newly assigned active management system when the following problem is detected during that process:
  • The partition IP address could not be assigned to the port on the configuration node. This might indicate a problem with the Ethernet adapter or port. In this case there will be other events in the log indicating Ethernet port failure.

User response

If bringing the partition IP address online is a priority, you can try switching the configuration node to the other node in the system.
Note: If you switch the configuration node you must still troubleshoot the cause of the configuration failure. The partition management address will fail again if the fault remains and the configuration node switches back.
To switch the configuration node to the other node, do the following:
  1. Log into the CLI of the configuration node.
  2. Run the svctask stopsystem -reset -node <id/name> -force command to perform a warm start of the configuration node.
  3. Wait for the other node in the system to become the configuration node.
  4. Make sure you can connect to the system CLI or management GUI using the system partition IP address.
  5. Make sure you can connect to the partition using the partition management address.
To troubleshoot the cause of the configuration failure, carry out the following actions:
  1. Log into the management GUI or CLI of the partition's active management system using its system partition IP address.
  2. Use the management GUI to view the details of the event. Take note of the node ID, IP ID and IP address shown in the sense data.
  3. View the IP configuration and check which port ID the address is bound to. You can run the lsip command to find the IP by its id and check the port_id value.
  4. Identify affected Ethernet port by its node ID and port ID, and check its hardware location. You can run the lsportethernet command and match node_id and port_id, taking note of adapter_location and adapter_port_id). If the port is not listed, there might be a hardware failure.
    Note: Location 0 means the port is built into the node or node canister
  5. Check the event log for hardware failures relating to the affected port. Resolve any you find by following fix procedures in the management GUI or the service action for the error codes in documentation.

To test whether the problem is resolved, log into the management GUI or CLI of the partition's active management system using the partition IP address. If the problem is resolved, find the event in the management GUI (Monitoring > Events) and mark the event as fixed.