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 |
---|---|
|
CU could not retrieve the kernel parameter, which can happen if CU is on the old Cluster Member. |
|
The user did not pass the sync IP and Cluster Member ID to the CU script. |
|
The IP address passed to the CU script is not in valid format. |
|
An invalid Cluster Member ID was passed to the CU script. |
|
The CU script is already running, and the user is trying to run CU again. Run the |
|
CU could not get the cluster state of the local Cluster Member. Run |
|
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. |
|
For Security Gateways only: CU only runs, if the Critical Device Synchronization reports its state as CU examines many times, if the Critical Device Synchronization reports its state as If the Critical Device Synchronization reports its state as If you get this error, install policy on this cluster and run the |
|
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. |
|
CU could not update the kernel about the status of this kernel parameter. |
|
|
|
This can happen, if you run CU on a version that does not support CU. |
|
|
|
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. |
|
The Full Sync started, but did not finish for this Virtual System. This means that some of the connections were not synchronized. |
|
The script |
|
CU failed to print the connection table summary for each Virtual System. |