EasyManua.ls Logo

Honeywell Experion C300 - Page 222

Honeywell Experion C300
270 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
C300 Redundancy-related notifications
OPM Status – RDNOPMSTATUS
206 Experion C300 Controller User's Guide R301.1
Honeywell 11/06
Notification Description
RDNOPMSTATUS
Parameter
commence initial-sync. This notification represents
abnormal OPM session termination.
OPM I/O Data
Failure
The primary controller generates this notification that
indicates a loss-of-sync occurrence while transferring I/O
connection data (as part of initial-sync during an OPM
session). Although any loss-of-sync triggers this behavior,
the most probable loss-of-sync cause is the inability of the
secondary controller to interpret the I/O connection data
format. The secondary controller block’s LASTOPMNAME
parameter is blank in this case. This notification represents
abnormal OPM session termination.
Note that this applies to both C200 and C300 Controllers
because they both transfer Series A I/O Connection data
during OPM initial-sync.
IoDataFailure
OPM I/O Conns
Timeout
Indicates a loss-of-sync occurrence while waiting for the
secondary controller to form at least the same number of I/O
connections as the primary controller (as part of initial-sync
during an OPM session). Notification is generated by the
primary controller and sets the RDNOPMSTATUS
parameter to IoConnsTimeout. The secondary controller
block’s LASTOPMNAME parameter is blank. This
notification represents abnormal OPM session termination.
This only applies to C200 controllers because it forms
connections directly with the Series A I/O. As with the C300,
connections are formed between the FTEB and Series A
I/O.
IoConnsTimeout
OPM Peer Refs
Mismatch
Indicates a loss-of-sync occurrence while transferring peer
cross-reference ID data (as part of initial-sync during an
OPM session). The primary controller generates this
notification. Although any loss-of-sync triggers this
behavior, the most probable loss-of-sync cause is the
presence of a ghost peer connection reference. A ghost
peer connection reference exists if the primary controller has
knowledge of a peer connection ID that was not instantiated
in the secondary controller during OPM secondary
checkpoint restore. The secondary controller block’s
LASTOPMNAME parameter is blank. This notification
represents abnormal OPM session termination.
PeerRefsMismatch
OPM Peer Refs
Failure
The one-time OPM initial-sync transfer of dynamic data that
occurs with control frozen contains two components: peer
dynamic data and block dynamic data, with the latter
typically being the larger of the two. A loss-of-sync
occurrence while transferring peer dynamic data causes the
primary controller to generate this notification and to set the
RDNOPMSTATUS parameter to PeerRefsFailure. Although
PeerRefsFailure

Table of Contents

Related product manuals