OmniMessaging EMS Operator's Manual 1.8
OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 69
EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process
Recovery \NSK.$Z4QZ: Server Warning <error> Could not initialize sendmsg library
Pathmon: NSK.$IMAP7
Cause: The sendmsg library could not be initialized
Corrective Action: Contact OmniMessaging support
8 DUD EMS Messages
These messages are generated by the OmniMessaging DUD server.
8.1 EMS Message 200
This EMS event is displayed in the primary collector.
EMS Message: 02-11-16 12:00:40 \OMNI.$M011 TANDEM.NSIM.G06 000200 OMNI
DUD STOPPED \OMNI.$M011 Pathmon: \OMNI.$PNIM0
Cause: DUD Server stopped.
Corrective Action: Check EMS messages preceding this EMS message for details.
8.2 EMS Message 201
This EMS event is displayed in the primary collector.
EMS Message: 02-11-16 12:06:32 \OMNI.$Z3XC TANDEM.NSIM.G06 000201 OMNI Process DUD
STARTED \OMNI.$Z3XC Pathmon: \OMNI.$OMNI2
Cause: DUD Server has started.
Corrective Action: No corrective action.
8.3 EMS Message 202
This EMS event is displayed in the primary collector.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSSQ TANDEM.NSIM.G06 000202 OMNI Process
DUD \OMNI.$OSSQ I/O Error: File System Error <error> File Name <filename>, MTP_Reply failed.
Pathmon: \OMNI.$OMNIQ
Cause: Interprocess communcation failed.
Corrective Action: Check system configuration and if it persists contact Opsol support.
EMS Message: 02-04-05 13:13:21 \NITRO.$YI51 TANDEM.NSIM.G06
000202 OMNI Process MTA \NITRO.$Y0NH I/O Error: File System Error <error> File Name <filename>,
REV LOOKUP TIMEOUT Pathmon: \NITRO.$Z28CE
Cause: MTA-DUD communication timedout during reverse lookup.
Corrective Action: Check the filesystem error and take action accordingly.
EMS Message: 02-04-05 13:13:21 \NITRO.$YI51 TANDEM.NSIM.G06
000202 OMNI Process MTA \NITRO.$Y0NH I/O Error: File System Error <error> File Name <filename>,
DOM LOOKUP TIMEOUT Pathmon: \NITRO.$Z28CE
Cause: MTA-DUD communication timedout during domain lookup.
Corrective Action: Check the filesystem error and take action accordingly.