Filter
Top Products
Brocade SMI Agent User’s Guide 37
53-1001778-01
Debugging and logging options configuration
3
Debugging and logging options configuration
This section explains how to use the Brocade SMI Agent Configuration Tool to configure debugging
and logging options for the CIMOM and Provider. This information can be useful in diagnosing
problems during development of client applications, providers, and other components.
• “Debugging options for CIMOM” on page 37
• “Debugging options for the provider” on page 38
• “Logging options for the provider” on page 40
• “Capture provider cache information” on page 42
Debugging options for CIMOM
The SMI-A can write detailed debugging output to a file. By default, the SMI-A is configured with
debugging disabled.
You can enable or disable debugging for CIMOM using the Brocade SMI Agent Configuration Tool. If
you enable debugging, trace statements are logged to a trace file with the following name format:
jserverlog_<month & date>_<Hour & Mins>.trace
For example, jserverlog_1017_1655.trace is the trace file for 4:55 p.m. on October 17.
Whenever the CIMOM server is restarted, a new trace file is generated with the timestamp of when
the server starts.
The location of this log file is the folder from which the SMIA server is started. It is usually the folder
that contains the start_server script:
On Linux, Solaris, and AIX:<SMIAgent>/agent/server/jserver/bin
On Windows: <SMIAgent>\agent\server\jserver\bin
Configuring debugging options for CIMOM
1. Launch the Brocade SMI Agent Configuration Tool.
2. Click CIMOM in the menu tree (see Figure 23 on page 38).
The content pane displays the current debugging configuration for CIMOM. By default,
debugging is disabled (log level = NO LOG).
3. Select a log level value from the list. Possible values are:
Selecting NO LOG disables logging. Selecting any value other than NO LOG enables logging.
• NO LOG 10000 Do not log (default).
• SEVERE 1000 Log severe error messages.
• WARNING 900 Log warning messages.
• INFO 800 Log informational messages.
• CONFIG 700
• FINE WITH XML TRACE 500 Log detailed trace information, including Server XML
Trace output.
• FINER 400
• FINEST 300
• ALL 0 Log all messages.