Brocade Communications Systems 53-1001778-01 manual Debugging and logging options configuration

Page 53

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:

•	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.

Selecting NO LOG disables logging. Selecting any value other than NO LOG enables logging.

Brocade SMI Agent User’s Guide	37
53-1001778-01

Image 53

Contents Brocade SMI Agent Brocade Communications Systems, Incorporated Title Publication number Summary of changes Date Brocade SMI Agent User’s Guide Contents Chapter Brocade SMI Agent Configuration Chapter Mutual Authentication for Clients and Indications Index How this document is organized This chapterSupported hardware and software Text formatting What’s new in this documentDocument conventions Key terms Identifies command syntax examplesOther industry resources Additional informationBrocade resources FT00X0054E9 Getting technical helpSupport@brocade.com Brocade SMI Agent supportDocument feedback Common Information Model CIM OverviewBrocade SMI Agent Brocade SMI-S InitiativeBrocade SMI Agent Brocade SMI Agent User’s Guide Starting the SMI-A Brocade SMI AgentStopping the SMI-A Starting the SMI-A as a serviceStop the Brocade SMI Agent Stopping the SMI-A as a service Service Location Protocol SLP supportSLP on Linux, Solaris, and AIX Slptool commandsStopping SLP on Linux, Solaris, and AIX Starting SLP on Linux, Solaris, and AIXStarting SLP on Windows Installing SLP on WindowsSLP on Windows Connection monitoring Disable Http for security reasonsFor example Enable multi-homed supportAbout the Brocade SMI Agent Configuration Tool Brocade SMI Agent ConfigurationApply Launching the Brocade SMI Agent Configuration Tool Windows Launch the Brocade SMI-A Configuration ToolAdding proxy connections Proxy connectionsReloading provider.xml on fabric segmentation Removing proxy connections Login failure status informationAccess control Login failure status messages Access controlMapping an SMI-A user to a switch user Setting up default SMI-A user mapping SMI Agent security Limitations of SMI-A user-to-switch user mappingConfiguring mutual authentication for clients Mutual authentication setupConfiguring mutual authentication for indications Mutual authentication for indications Configuring Http accessImporting client certificates Http accessExporting server certificates SMI Agent security Configuring user authentication User authentication Encode proxy details Encoding proxy connection detailsConfiguring or removing the SMI Agent as a service SMI Agent service configuration and removalConfiguring the Http and Https ports Port configurationConfigure Http and Https ports Configuring the ARR and eventing ports Configure ARR and eventing portsConfigure ARR and eventing ports Fabric Manager database server configurationConfiguring software locations for firmware download Firmware download software locations configurationFile Path Debugging options for Cimom Debugging and logging options configurationConfiguring debugging options for Cimom Debugging options for the provider Configure debugging options for CimomDynamic Update Configuring debugging options for the providerLogging options for the provider Configuring logging options for providerLog file examples Configure logging optionsCapturing information from the provider cache Capture provider cache informationCollect support information Support information collectionRunning an XML dump XML dumpCollecting support information Configuring the Cimom server Cimom server configurationUncomment the following lines Configuring log file optionsIntroduction Mutual authentication for clientsClient configuration to use client certificates Mutual authentication for indicationsEnabling mutual authentication for clients Enabling mutual authentication for indicationsClient.ind.truststore Clientind.cer Java -classpath SMIAgent/agent/wbem.jar Xmlerror TroubleshootingXmlerror General questions Frequently Asked QuestionsHow do I collect diagnostic data from the Brocade SMI Agent? Does the SMI Agent have support for Https communication? On Linux Type the following command Appendix Open source software used in SMI-ASource Code License Sun Industry Standards Source LicenseDistribution Obligations Inability to Comply DUE to Statute or Regulation Termination IBM Common Public License Grant of Rights Commercial Distribution OpenSLP License GNU Library General Public License Bouncy CastleSun Binary Code License Agreement Public DomainBrocade SMI Agent User’s Guide Supplemental License Terms Brocade SMI Agent User’s Guide Brocade SMI Agent User’s Guide 53-1001778-01 Sun Binary Code License Agreement Index Brocade SMI Agent User’s Guide