8. C300 Redundancy operation
8.8. C300 Redundancy-related notifications
Series 8 C300 Controller User's Guide
Honeywell
8.8
C300 Redundancy-related notifications
This section provides listings of redundancy-related notifications implemented for the
C300 Controller. Table 13 lists notifications along with their descriptions that may occur
during controller synchronization and switchover operations.
Table 13 Redundancy-Related Notifications
The secondary generates the Backup State Change Event
as part of event regeneration. A transition to the Backup
State only occurs as part of startup or a redundancy role
change. In both of these cases, any previously existing
notification connection is broken, a new notification
connection is reformed, and event regeneration is
commanded.
The primary and secondary are configured for redundancy
but the redundant pair is not synchronized or not in standby.
The primary is configured for redundancy through C300
block load of the MODISREDUN parameter. A secondary
can only be in the secondary role if, retention startup
remembered that it was previously configured redundant,
and the C300 is configured with the even Device Index.
The "Not Synchronized" alarm returns to normal upon
configuring the primary at the odd Device Index as non-
redundant or upon entering the Synchronized or Standby
state.
Redun Incompatible
Partner
Both the primary and secondary controllers generate this
notification upon determining that their partner module is not
compatible for attempting initial-sync.
Both the primary and secondary controllers generate this
notification when the partner is not present.
Note that the primary controller only generates this
notification when it is either explicitly or implicitly configured
for redundant behavior. Explicit redundancy configuration
occurs when the C300 block is loaded with MODISREDUN
set ON, and implicit redundancy configuration occurs in the
absence of any configuration, (C300 in the NODB state).
Only the controller explicitly configured non-redundant
generates this notification when the partner is not present.
Both the primary and secondary controllers generate this
notification upon detecting a compatible partner visible
To Next Page
Loading...
