SNMP Configuration and Management Manual

Trap Multiplexer Subagent/Manager
SNMP Configuration and Management Manual—424777-006
12-44
103: ZTMX-EVT-TMX-IO-ERR
ZTMX-EVT-TMX-IO-ERR
is the event number (103). The DDL AS clause of this value (“Process-I/O-error”) is
inserted in the message text following “event number:”
ZTMX-VAL-TF-IO
identifies the type of transient fault that occurred. For this event, the DDL heading
of the value (“IO-error”) is inserted in the message text following “fault type:”
ZTMX-TKN-FS-ERR
contains the file-system error code and subcode, documented in the Guardian
Procedure Errors and Messages Manual. The token is based on this structure:
DEFINITION ZTMX-DDL-FS-ERR.
02 ERR-CODE TYPE ZSPI-DDL-INT
HEADING 'error code'
02 ERR-SUBCODE TYPE ZSPI-DDL-INT
HEADING 'error subcode'
END.
ZTMX-TKN-FILE-NAME
contains the name of the file with which the subagent experienced an I/O error.
This token is of type ZSPI-TYP-STRING.
ZTMX-TKN-ERR-TEXT
contains text describing the error. This token is of type ZSPI-TYP-STRING.
Cause. The Trap Multiplexer process encountered an I/O error. The cause is most
likely the assignment of an incorrect agent process name at Trap Multiplexer startup or
a stopped SNMP agent process.
Effect. The Trap Multiplexer cannot function.
Recovery. Investigate the reported error code and subcode and then correct the
condition they describe. If the error code is 14 (file does not exist), the Trap Multiplexer
could not open the SNMP agent process, and you should ensure that the SNMP agent
is running or that you specified the correct agent process name when starting the Trap
Multiplexer. If the error code is in the 4000 range, ensure that the Trap Multiplexer
process is started by a member of the super user group and that no other process is
controlling the port you want to monitor for traps.
If the Trap Multiplexer was running as a process pair when the I/O error occurred, the
backup process takes over. This new primary process tries to establish communication
with the SNMP agent. If the process cannot establish communication, it retries every
10 minutes for a period of 1 hour and then stops.
For more detailed information, including recovery actions, refer to the information about
file-system errors in the Guardian Procedure Errors and Messages Manual.