Print Download PDF Send Feedback

Previous

Next

Connectivity Upgrade Error Messages

If any of these error messages are displayed in the connectivity upgrade script, contact Check Point support and do not continue the CU.

Error

Description

Failed to get kernel parameter ###

CU could not retrieve the kernel parameter, which can happen if CU is on the old Cluster Member.

You must specify the Sync IP and the member Id of the old member

The user did not pass the sync IP and Cluster Member ID to the CU script.

Invalid IP address

The IP address passed to the CU script is not in valid format.

The member Id must be between 1-4

An invalid Cluster Member ID was passed to the CU script.

Only a single instance of connectivity upgrade can run at a time

The CU script is already running, and the user is trying to run CU again.

Run the ps auxw | cphacu command to make sure that the CU script is running and wait until CU finishes running.

Failed to get member state

CU could not get the cluster state of the local Cluster Member.

Run cphaprob state command on the local Cluster Member and make sure that the output shows the state of the local Cluster Member.

Connectivity upgrade failed since the local member is not in Ready state

CU only runs, if the state of the new Cluster Member is in the Ready state.

CU examines many times, if the Cluster Member is in the Ready state.

If the Cluster Member is still not in the Ready state, then the CU script exits.

Connectivity upgrade failed since Synchronization PNote is set to problem

For Security Gateways only: CU only runs, if the Critical Device Synchronization reports its state as OK.

CU examines many times, if the Critical Device Synchronization reports its state as OK.

If the Critical Device Synchronization reports its state as PROBLEM, then the CU script exits.

If you get this error, install policy on this cluster and run the cphacu script again.

Connectivity upgrade failed because CPHAPROB cannot see the old member's state.

When CU starts, the two Cluster Members begin to communicate, and the new Cluster Member sees the old Cluster Member as Active.

Check communication on the Sync interface, and make sure that the MAC Magic Configuration is correct.

Failed to enable Connectivity Upgrade

CU could not update the kernel about the status of this kernel parameter.

Failed to get fwha_version

 

Failed to get fwha_cu_override_last_heard_ccp_version of the other member

This can happen, if you run CU on a version that does not support CU.

Failed to get fwha_cu_last_heard_ccp_version of the other member

 

Failed to initialize full sync for VS ###; Connectivity Upgrade failed

CU failed to start a Full Sync for this Virtual System, which synchronizes the connections from the old Cluster Member to the new Cluster Member.

Failed to run fullsync for VS ###; Connectivity Upgrade failed

The Full Sync started, but did not finish for this Virtual System.

This means that some of the connections were not synchronized.

Failed to run cphacu state for VS ###

The script cphacu state failed to show the current CU state for this Virtual System.

Error printing connections table per vs

CU failed to print the connection table summary for each Virtual System.