System information

89 of 114Release 7.0VNX™ System Operations
Read log messages
Each type of log has a slightly different format. This section explains the formats by
displaying a line of the log with an explanation of the component parts. Table 4 on
page 89 provides a complete list of Server log components.
Server log
Example:
2005-06-21 04:38:04: ADMIN: 4: Command succeeded: logsys add output>
disk=root_log_2 bufsz=256
EMC
Symmetrix™
API
$ /nas/log/symapi.log
Lists events from the SYMAPI layer
generated as the VNX for file interacts with an
attached Symmetrix system. The Symmetrix
documentation provides more information
about these messages.
Installation
and upgrade
$ /nas/log/instcli.log
$ /nas/log/install.
<NAS_Code_Version>.log
$ /nas/log/upgrade.
<NAS_Code_Version>.log
Stores log SYMCLI installation.
NAS code installations and upgrades.
Table 4 Server log components (page 1 of 2)
Log component Description Example
Date Displays the date.
2005-03-15
Time Displays the time.
04:38:04
Category Lists the part of the VNX for file where the error
originates.
Table 6 on page 90 provides a complete list of
categories.
ADMIN
Severity level Indicates the importance of the event. Values
can be 0 through 7, with 0 indicating the highest
level of importance.
Table 5 on page 90 describes these levels.
The default severity for each module is set to 4.
Whenever the Data Mover or blade tries to
generate a log message, it provides the log
severity level and the module name. If the given
severity is less than or equal to the current
severity level for the given module, the message
goes to server log; otherwise, it is ignored.
4
Table 3 VNX for file logs (page 2 of 2)
Log
Command line or
log location
Description