Brocade Communications Systems 53-1001778-01 manual Log file examples, Configure logging options

Page 57

Debugging and logging options configuration

3

4.To enable file logging:

a.Check the Enable File logging check box.

b.Type the full path to the log file, or click Select File to browse for the file location.

c.Type the size of the log file (in kilobytes). The log file size can be between 1 and 51200 kilobytes (between 1024 and 52428800 bytes).

d.Type the number of log files.

To disable file logging, clear the Enable File logging check box.

5. Click Apply.

The changes take effect when you restart the server. Click Start Server to restart the server.

FIGURE 25 Configure logging options

Log file examples

The SMI-A trace information is appended to the log file each time the SMI-A is started. The following example shows the sample contents of the log file the first time the SMI-A is started:

<?xml version="1.0" encoding="windows=1252" standalone="no"?> <!DOCTYPE log SYSTEM "logger.dtd">

<log>

<record>

.

.

.

</record>

</log>

The next example shows the contents of the log file on the subsequent startup. The text in bold is the contents from the second time the SMI-A was started.

Brocade SMI Agent User’s Guide

41

53-1001778-01

 

Image 57
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 What’s new in this document Document conventionsText formatting Key terms Identifies command syntax examplesAdditional information Brocade resourcesOther industry 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 AgentStarting the SMI-A as a service Stop the Brocade SMI AgentStopping the SMI-A 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 AIXInstalling SLP on Windows SLP on WindowsStarting SLP 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 ToolProxy connections Reloading provider.xml on fabric segmentationAdding proxy connections 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 removalPort configuration Configure Http and Https portsConfiguring the 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 and logging options configuration Configuring debugging options for CimomDebugging 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 collectionXML dump Collecting support informationRunning an XML dump 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