Synchronization Tab Overview
The Synchronization Tab allows you to change the synchronization state of the system and provides information about the last four synchronization attempts.
Option | Description |
|---|---|
Synchronize Secondary | Click on this button to force the primary redundancy module to attempt synchronization with its partner. This button is enabled only when the chassis redundancy state is either primary with disqualified secondary or disqualified secondary. In all other cases, the button is disabled. Note : Synchronization is asynchronous with the execution of this command. Successful execution of this command begins synchronization, which may not finish for several seconds. Be sure to visually monitor the chassis status displayed on the bottom of the property sheet to determine when synchronization has been completed. |
Disqualify Secondary | Click on this button to force the primary redundancy module to disqualify its partner. This button is enabled only when the chassis redundancy state is either primary with synchronized secondary or synchronized secondary. In all other cases, the button is disabled. Note : If the user click Disqualify Secondary button and simultaneously Always is set for Auto-Synchronization , then an auto-synchronization attempt occurs immediately (and disqualification isn’t achieved).To ensure that the secondary remains disqualified, first set Auto-Synchronization to Conditional.
WARNING:
Disqualifying the secondary chassis makes it unable to assume control functions. |
Initiate Switchover | Click on this button to force the system to initiate an immediate switchover from the primary chassis to the secondary chassis. This function enables you to perform a realistic test of your redundant control chassis behavior should a detected failure occur in the primary control chassis. This button is enabled only when the chassis redundancy state is either primary with synchronized secondary or synchronized secondary. In all other cases, the button is disabled |
Become Primary | Click on this button to force a disqualified secondary system to become a primary system. This button is enabled only when the chassis redundancy state is disqualified secondary with no partner. In all other cases, the button is disabled. |
Recent Synchronization Attempts | Displays the last four synchronization attempts. These attempts are labeled as follows:
|
Description | Select an entry in the Recent Synchronization Attempts list to see the details under Description . |
Refresh | Click on this button to refresh the Recent Synchronization Attempts list to display the four most recent synchronization attempts. |
For each attempt, a result and a cause are given. The Result and Cause columns indicate the reason for the attempted synchronization and its final status.
Possible Result | Description |
Undefined | The result of the synchronization is unknown. |
Synchronization not attempted | Synchronization has not been attempted since power was applied to the module. |
Success | Full synchronization was successfully completed. |
Cancel | The synchronization attempt failed. |
Possible causes for the results above
Possible Cause | Description |
|---|---|
Undefined | The cause of synchronization failure is unknown. |
Module Pair Incompatible | One or more modules in the primary chassis has an incompatible partner. Look at the synchronization status tab to identify which slots are reporting an incompatible partner. Check to make sure that the primary & secondary partners are occupying the same slot & have the same Vendor ID, Product Type & compatible Product Codes. Also ensure that the firmware revision of the secondary module is the same or greater than its primary partner. Additionally, for ControlNet communication modules, the partners should have the same MAC ID & keeper signatures, & identical media configuration (both single or both redundant media). |
Module Configuration Error | A module in the chassis returned an invalid response to a Synchronization request 1. See Event Log for Slot Number of Module which rejected qualification. 2. Check module configuration and retry. |
Edit Session In Progress | An edit or configuration change occurred during synchronization that canceled the synchronization attempt. Synchronization can be attempted via the Synchronize Secondary button once the edit operation has been completed. |
Crossloading Failure | The Redundancy Module failed when attempting to crossload data between one or more module pairs. This can occur if: 1. There is a problem with the Redundancy Cable. Check the cable and cable installation. 2. A problem exists with one of the modules that refuse to crossload. Reseat each module and retry. If still unsuccessful, the module may need to be replaced. 3. A problem exists with one of the Redundancy Module modules. Reseat each Redundancy Module and retry. If still unsuccessful the module may need to be replaced. 4. A problem with the chassis may exist. |
Communication Disconnected | The Redundancy Module was unable to maintain the required communication links during synchronization. This can occur if: 1. There is a problem with the Redundancy Cable. Check the cable and cable installation. 2. A problem exists with one of the modules that refuses to crossload. Reset each module and retry. If still unsuccessful the module may need to be replaced. 3. A problem exists with one of the Redundancy modules. Reset each Redundancy Module and retry. If still unsuccessful, the module may need to be replaced. 4. A problem with the chassis may exist. |
Module Insertion | A module was inserted under power while attempting synchronization. Remedy: 1. Check for correct module pairing and retry Synchronization. 2. See Event Log for slot number of the inserted module. |
Module Removal | A module was removed under power while attempting synchronization. 1. Check for correct module pairing and retry Synchronization. 2. See Event Log for slot number of the removed module. |
Secondary Module Failed | One or more modules in the secondary chassis had failed when synchronization was in progress. Use the Synchronization Tab to determine the failed module and repair or replace the module. |
Incorrect Chassis Redundancy State | The chassis redundancy state must be Primary with a Disqualified Secondary in order to Synchronize. Synchronization can be attempted via the Synchronize Secondary button when the chassis state is Primary with Disqualified Secondary. |
Loss of Communication | The Redundancy Module was unable to establish the required communication links prior to synchronization. This can occur if: 1. There is a problem with the Redundancy Cable. Check the cable and cable installation. 2. A problem exists with one of the modules that refuses to crossload. Reset each module and retry. If still unsuccessful, the module may need to be replaced. 3. A problem exists with one of the Redundancy Modules. Reset each Redundancy Module and retry. If still unsuccessful, the module may need to be replaced. 4. A problem with the chassis may exist. |
Non-Redundant Compliant Module Exists | One or more modules in the chassis was not supported in a redundant configuration. 1. The Synchronization Tab can be used to determine which module pair is not supported. 2. Check module versions, make necessary corrections, and retry. |
Secondary Module Failed Module prior to Synchronization attempt | One or more modules in the secondary chassis failed before attempting synchronization. Use the Synchronization Tab to determine the failed module and repair or replace the module. |
Local Redundancy Module in Major Unrecoverable Fault state | A major unrecoverable fault has been detected in the local Redundancy Module when synchronization was in progress. Reset or Repair/Replace failed module and retry. |
Partner Redundancy Module has Major Fault | A Major Fault occurred in the Partner Redundancy Module when synchronization was in progress. Clear Fault, Reset or Repair/Replace the partner Redundancy Module & retry synchronization. |
Sec SYS_FAIL_L Subsystem Failed | Module Failure Checking Mechanism in partner Redundancy Module failed. 1. Reset or Replace the partner Redundancy Module. 2. A problem with the secondary chassis may exist. Retry after replacing the secondary chassis. |
Secondary Redundancy Module Device Status Communication Error | Information about the partner's Redundancy Module Device Status was Invalid. Retry after each of the following steps: 1. Check Redundancy Cable installation and retry. 2. Reseat each Redundancy Module, retrying after each. 3. Replace each Redundancy Module, retrying after each. 4. Reseat each module, retrying after each. 5. Replace each module, retrying after each. 6. Replace each chassis, retrying after each. |
Secondary Redundancy Module Device Status in Major Recoverable Fault state | Major Recoverable Fault detected in partner Redundancy Module before attempting synchronization. Reset, Repair/Replace failed partner Redundancy Module and retry. |
Secondary Redundancy Module Device Status in Major Unrecoverable Fault state | Major Unrecoverable Fault detected in partner Redundancy Module before attempting synchronization. Reset, Repair/Replace failed partner Redundancy Module and retry. |
Incorrect local Redundancy Module Device State | The local Redundancy Module device was found to be in a Major Unrecoverable Fault State before attempting synchronization. Reset, Repair/Replace failed Redundancy Module and retry. |
Primary Module Failed | Synchronization was canceled because of a failure in the primary module. |
Primary Failed Module Exists | A module in the primary chassis has asserted the SYS_FAIL line, indicating that it has faulted or failed. |
Change in Auto-Sync Option | Auto-Synchronization option changed from Never to Always when synchronization was in progress. Do not attempt to change the Auto-Synchronization option when synchronization is in progress. Re-Send the Synchronize Secondary command. |
Module Qualification Request | Module requested for Synchronization when Chassis Synchronization was in progress. See Event Log to locate the module requesting synchronization. Change Auto-Synchronization option to Never & Re-Send the Synchronize Secondary command. |
SYS_FAIL_L Deasserted | One of the modules recovered from failure in partner chassis. Reset\Re-Seat each module in partner chassis & retry. |
Disqualify Command | A Disqualify command was issued from either Config Tool or a controller user program. |
Disqualify Request | A Secondary Disqualification request was posted by one of the modules in the primary chassis when synchronization was in progress.See Event Log to locate an entry related to disqualification. Check module settings/configuration & eliminate the cause for module disqualification request & retry. |
Partner Module not Found | One or more modules in the primary chassis does not have a partner in the secondary chassis. Check to make sure that all the primary modules have a compatible partner resident in the same slot as the secondary chassis. If compatible partners already exist, look at the synchronization status tab of the primary redundancy module to verify that the compatibility column shows FULL for all slots, before attempting synchronization. |
Platform Configuration Identity Mismatch Detected | There are modules in the primary or secondary chassis that do not belong to the same hardware platform or the Redundancy Module in the primary or secondary chassis is not compatible with the other redundancy compliant modules in its chassis due to platform differences. See the Event Log to locate the most recent "Qualification Canceled" record & read its extended information to understand the nature of the discrepancy & identify the slots occupied by the standard & enhanced modules. To resolve this mismatch, ensure that all modules in the primary & secondary chassis belong to the same platform & the Redundancy Module operational in the chassis belongs to the same platform as the remaining redundancy compliant modules. |
A module rejected qualification but did not report a reason | The extended error status in the module's qualification response is unavailable. See the Event log to locate a "Qualification Canceled" Event. The extended information associated with this event will identify the slot number of the module that rejected qualification. Reset or Re-configure the module before retrying synchronization. |
A module rejected qualification but reported an invalid cause | The extended error status in the module's qualification response is invalid. See the Event log to locate a "Qualification Canceled" Event. The extended information associated with this event will identify (a) the slot number of the module that rejected qualification, & (b) the extended error status. Reset or Re-configure the module before retrying synchronization. |
A module rejected qualification but reported an invalid status | The general error status in the module's qualification response is invalid. See the Event log to locate a "Qualification Canceled" Event. The extended information associated with this event will identify (a) the slot number of the module that rejected qualification, & (b) the general error status. Reset or Re-configure the module before retrying synchronization. |
The ICP test line on the primary backplane is in the asserted state | A faulty backplane or module may have asserted the ICP test line. Qualification cannot proceed until this line is de-asserted. Remove the non-RM modules from the primary chassis one at a time & each time re-attempt qualification, until this cause disappears. Then replace the module that allowed qualification to succeed when it was removed from the chassis. Re-insert all the remaining modules in the primary chassis & attempt to synchronize again. If qualification still cancels after removing all the primary non-RM modules, replace the primary RM. If qualification still cancels with a new RM, replace the primary chassis. |
Application requires Enhanced Platform | A module rejected qualification. See the Event log to locate a "Qualification Canceled" Event. The extended information associated with this event will identify:
|
The ICP test line on the secondary backplane is in the asserted state | A faulty backplane or module may have asserted the ICP test line. Qualification cannot proceed until this line is de-asserted. Remove the non-RM modules from the secondary chassis & its corresponding partner module from the primary chassis, one at a time & each time re-attempt qualification, until this cause disappears. Then replace the module in the secondary that allowed qualification to succeed when it was removed from the chassis. Re-insert all the remaining modules in the primary & secondary chassis & attempt to synchronize again. If qualification still cancels after removing all the primary & secondary non-RM modules, replace the secondary RM. If qualification still cancels with a new RM, replace the secondary chassis. |
Unicast Connection Not Supported | Qualification is rejected when a unicast connection(s) exist in the redundant controller. |
Time Sync Configuration Error | A redundant controller has Time Sync enabled but it is not the grandmaster or synchronized to a grandmaster, or a redundant controller pair is synchronized to different grandmasters. Check your Time Sync network configuration and retry. |
Partner Mismatch | Unrecoverable partner mismatch. Replace the secondary module or contact RA support. |
Node Address Mismatch | Set partners to identical node addresses to resolve the mismatch. |
Version Mismatch | Severe partner versions incompatibility. See documentation for compatible module version information. |
Secondary Offline | The secondary partner module is not active on its network. The secondary module must be online for synchronization to be successful |
No Partner Ping | The primary is unable to communicate with its partner across the network. Verify that both partners are active on the same network. |
Primary Not Time Synchronized | Primary is configured for CIP Synch but must first become time synched to allow redundancy synchronization. Retry synchronization after primary becomes time synched. |
Keeper Mismatch | The partners do not have identical keepers. Update the keepers to match. |
Keeper Invalid | One or both of the partner's keepers are invalid. Update the keepers to valid and matching keeper values. |
Keeper Update In Progress | A keeper update has been requested and is in progress. The system requires more time to complete the request. |
TTL Not Default | The Time_To_Live Ethernet configuration value must be defaulted in both modules when configured for IP address switching. Powering the module up with node switches set to 888 will return attributes to default. |
MAC Address Not Default | The Ethernet Multicast addressing scheme must be defaulted in both modules when configured for IP address switching. Powering the module up with node switches set to 888 will return attributes to default. |
Incompatible Partner Revision | Partner revisions are incompatible. See documentation for compatible module version information. |
Node Address Zero | One or both of the partner's node addresses are set to zero. Set node address to a valid value. |
Class 1 I/O Present with No IP-Swap | Class 1 connections detected in partners not configured for IP address switching. The partners must be configured for IP swapping to support class 1 connections. |
Not Enough Information | Severe incompatibility. Refer to the help documentation for compatible module information. |
Port Count Max | Severe incompatibility. Refer to the help documentation for compatible module information. |
Port Info Size Too Big | Severe incompatibility. Refer to the help documentation for compatible module information. |
Port Info Out of Range | Severe incompatibility. Refer to the help documentation for compatible module information. |
Partner Vendor Mismatch | The partners are not made by the same vendor. Only partners made by the same vendor are allowed to synchronize. |
Partner Product Type Mismatch | The partners do not have the same device type. Only partners of the same device type are allowed to synchronize. |
Partner Product Code Mismatch | The partners do not have the same product code. Only partners of the same product code are allowed to synchronize. |
Port Not Redundancy Capable | One of the modules has a port which is not redundancy capable. Refer to the help documentation for compatible module information. |
Primary Revision Out of Range | The primary's revision is not within the acceptable range for synchronization. The secondary may need to be updated to a later revision before attempting synchronization. |
Partner Firmware Revision Not Compatible | The partner firmware revisions are not compatible. The secondary's revision must be equal to or greater than the primary's for synchronization to occur. |
Partner Not on Same Link | The primary and secondary partners are not on the same network. The partners must be communicating on the same network to synchronize. |
Duplicate Node Exists | One or both of the partners are in a duplicate node state. Resolve duplicate nodes before attempting synchronization. |
Secondary Not Time Synchronized | The primary partner is Time Sync enabled and is time synched, but the secondary partner is not time synched. Ensure the secondary partner can become time synched and retry redundancy synchronization. |
Ability to Control Unknown | The partners were not able to determine their ability to control. Manually retry synchronization. |
No Transition to Qualifying State | The secondary was not able to transition to the qualifying state. Manually retry synchronization. |
No Response to Qualifying Notification | The primary never received a response to its request to the secondary to enter the qualifying state. Manually retry synchronization. |
No Response to Qualified notification | The primary never received a response to its request to the secondary to enter the qualified state. Manually retry synchronization. |
Time Sync - Get Status Failed | The primary was unable to send a connection information query to a backplane module. Possibly a hardware problem (for example, module, backplane, slot, etc.). |
Failed to Send Qualifying Notification | The primary was unable to send a qualifying notification to the secondary. Manually retry synchronization. |
Failed to Send Qualified Notification | The primary was unable to send a qualified notification to the secondary. Manually retry synchronization. |
Failed to Send Secondary Status Query | The primary was unable to send a query to the secondary requesting its status. Manually retry synchronization. |
Rack Connection in RCP Exists | Rack connections were detected and are not supported in an RCP. Change all rack connections to direct connections to allow synchronization. |
No Connection via RM | The primary is unable to communicate with its secondary partner through its redundancy module connection. Cycle power to the secondary chassis and retry synchronization. |
Phase 1 Out of Sequence | Synchronization requires a specific set of events to occur. A request to proceed to phase 1 was received out of sequence. Manually attempt to synchronize. |
Phase 2 Out of Sequence | Synchronization requires a specific set of events to occur. A request to proceed to phase 2 was received out of sequence. Manually attempt to synchronize. |
Phase 3 Out of Sequence | Synchronization requires a specific set of events to occur. A request to proceed to phase 3 was received out of sequence. Manually attempt to synchronize. |
Phase 4 Out of Sequence | Synchronization requires a specific set of events to occur. A request to proceed to phase 4 was received out of sequence. Manually attempt to synchronize. |
Qualification failed to complete - Secured Module Mismatch | The serial number of the secondary Secure Communication module does not match the serial number that has been previously locked in. Perform one of the following: 1. Replace the secondary Secure Communication module with a module that has previously had its serial number "locked in". 2. Clear the memory in the secondary controller by removing the battery or energy storage module. |
Multicast or TTL change pending | There is a pending Multicast address setting or Time_To_Live Ethernet configuration value change. Manually retry synchronization. |
Primary Controller Faulted | Primary Controller is in a Faulted State. Clear the Fault and attempt to synchronize again. |
Secondary Controller Faulted | Secondary Controller is in a Faulted State. Clear the Fault and attempt to synchronize again. |
Primary Controller: Project Download In Progress | A download is in progress to the Primary Controller. Complete the download and attempt to synchronize again. |
Primary Controller: Project Download Canceling | A download is still canceling to the Primary Controller. Let the download finish canceling and attempt to synchronize again. |
Primary Controller: Edits In Progress | The Primary Controller is online with Software that is performing online edits. Go offline and attempt to synchronize again. |
Secondary Controller: Edits In Progress | The Secondary Controller is online with Software that is performing online edits. Go offline and attempt to synchronize again. |
Secondary Controller: Project Download In Progress | A download is in progress to the Secondary Controller. Complete the download and attempt to synchronize again. |
Secondary Controller: Project Download Canceling | A download is still canceling to the Secondary Controller. Let the download finish canceling and attempt to synchronize again. |
Controller Project Not Configured For Redundancy | The Primary Controller contains a project that is not configured for Redundancy. Re-download the project with Redundancy Enabled and attempt to synchronize again. |
Controller Project Crossload Failed | Primary Controller failed to crossload the User Project to the Secondary Controller. Try one of these recovery steps and attempt to synchronize again: 1. Reset the Secondary Controller or 2. Cycle power to the Secondary Chassis or 3. Re-download the User Project to the Primary Controller. For more detailed troubleshooting, look in the event logs for a Qualification Canceled event. |
Provide Feedback