Technical data

Configuring SNMP
13.5 SNMP Log Files
13.5 SNMP Log Files
Unless the SNMP_TRACE option is set, output from the SNMP master agent and
subagent processes to SYS$OUTPUT is redirected to the following files:
TCPIP$SNMP_RUN.LOG
TCPIP$OS_MIBS.LOG
TCPIP$HR_MIB.LOG
The output is written to these files continuously while SNMP processes are
running. Buffering may cause a delay in writing to disk; therefore, if a process is
terminated abnormally, some data may be lost.
While processes are running, output for SYS$ERROR can be redirected to other
files. See Section 13.4.3 for information about controlling this. In addition, the
master agent and subagents may write to SYS$ERROR. This output is redirected
to the following files:
TCPIP$SNMP_RUN.LOG
TCPIP$OS_MIBS.ERR
TCPIP$HR_MIB.ERR
Unlike a regular log or a trace log, this output is written when the corresponding
SNMP process terminates. Therefore, abnormal termination can cause data to be
lost.
All of the listed log files are located in the SYS$SYSDEVICE:[TCPIP$SNMP]
directory. The configuration-related files described in Section 13.4.3 are also
stored there. TCP/IP Services does not allow you write to log files in other
directories.
The log level and specific events during processing determine how much
information is recorded in the log files; log files can be empty or nonexistent.
The log files contain startup and event information and additional messages,
depending on the logging level specified for an agent. The SNMP logging facility
uses three logging levels:
Trace (logs trace, warning, and error messages)
Warning (logs warning and error messages)
Error
The default logging level for the master agent and standard subagents is
Warning. Because the Chess example subagent does not use a default, messages
are captured only if you specify tracing, as described in Section 13.6.4.
Many logging options are configurable using the text configuration file
SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$VMS_SNMP_CONF.DAT; see
Table 13–3 for more details.
The following log files exist under normal production conditions if special
configuration options are not used. In most cases, a new version of each file is
created each time SNMP is started:
13–20 Configuring SNMP