Envoy Configuration and Management Manual

Envoy Event Messages
Envoy Configuration and Management Manual—429861-001
B-2
ZENV Subsystem ID
Table B-2 lists the Envoy-generated event messages defined by other subsystems.
ZENV Subsystem ID
To determine which subsystem generated a particular event message, you must know the
event number and the three-character abbreviation of the subsystem that generated the
event. The symbolic name of event numbers has the form ZENV-EVT-event, where
ENV is a three-character abbreviation for the subsystem and event identifies the event.
Event Numbers
An event number is part of the header of an event message. The header token named
ZEMS-TKN-EVENTNUMBER contains the event number. The value of the event
number is subsystem-specific and is represented by its symbolic name. Because event
numbers are not unique across subsystems, you must know both the event number and
the three-character abbreviation of the subsystem which created the event.
Tokens in All Event Messages
Event-message buffers, like any other SPI buffers, contain header tokens and data-
portion tokens. The header tokens that appear in all Envoy event messages are listed in
Table B-3. The tokens that appear only in certain event messages are listed and
described in the individual message descriptions in the remainder of this section.
Table B-2. Envoy Event Messages Defined by Other Subsystems
Event Number and Symbolic Name Description
-00003: ZCOM-EVT-SUMSTATE-CHANGE A line state transition has occurred.
-00001: ZCOM-EVT-CPU-SWITCH The backup I/O PROCESS has become the
primary I/O PROCESS.
-10003: ZCDG-EVT-PON-INTRPT A power-on interrupt was detected.
Table B-3. Header Tokens That Appear in All Envoy Event Messages (page 1 of 2)
Header Tokens Token Type
ZSPI-TKN-SSID SSID
ZEMS-TKN-EVENTNUMBER ENUM
ZEMS-TKN-CPU UINT
ZEMS-TKN-CRTPID CRTPID
ZEMS-TKN-GENTIME TIMESTAMP
ZEMS-TKN-LOGTIME TIMESTAMP