Brocade Communications Systems 53-1001778-01 manual Configuring log file options

Page 62

3 CIMOM server configuration

FIGURE 29 Configure the CIMOM server

Configuring log file options

You cannot configure log file options with the SMI Agent Configuration Tool. The following procedure describes how to change the log file options by modifying the jserver.properties file.

1.Open the jserver.properties file found at …server/jserver/bin.

2.Uncomment the following lines:

#com.wbemsolutions.jserver.logdirectory=/mylogfiledir

#com.wbemsolutions.jserver.log.maxfilesize=5000000

#com.wbemsolutions.jserver.log.numfiles=3

Replace mylogfiledir with the complete path of the log file directory. Replace 5000000 with the maximum size of the log file (in KB). Replace 3 with the number of rotating log files.

When the specified size is exceeded on the first log file, logs are written to the next log file. When approximately the specified number of KB have been written to one log file, another log file is opened.

NOTE

Sometimes log file will exceed the size specified because of a limitation in Java logging. After the server is stopped, the size of the log file will be reduced to the size specified.

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

Image 62

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 This chapter How this document is organizedSupported hardware and software Text formatting What’s new in this documentDocument conventions Identifies command syntax examples Key termsOther industry resources Additional informationBrocade resources Getting technical help FT00X0054E9Brocade SMI Agent support Support@brocade.comDocument feedback Overview Common Information Model CIMBrocade SMI-S Initiative Brocade SMI AgentBrocade SMI Agent Brocade SMI Agent User’s Guide Brocade SMI Agent Starting the SMI-AStopping the SMI-A Starting the SMI-A as a serviceStop the Brocade SMI Agent Service Location Protocol SLP support Stopping the SMI-A as a serviceSlptool commands SLP on Linux, Solaris, and AIXStarting SLP on Linux, Solaris, and AIX Stopping SLP on Linux, Solaris, and AIXStarting SLP on Windows Installing SLP on WindowsSLP on Windows Disable Http for security reasons Connection monitoringEnable multi-homed support For exampleBrocade SMI Agent Configuration About the Brocade SMI Agent Configuration ToolApply Launch the Brocade SMI-A Configuration Tool Launching the Brocade SMI Agent Configuration Tool WindowsAdding proxy connections Proxy connectionsReloading provider.xml on fabric segmentation Login failure status information Removing proxy connectionsAccess control Access control Login failure status messagesMapping an SMI-A user to a switch user Setting up default SMI-A user mapping Limitations of SMI-A user-to-switch user mapping SMI Agent securityMutual authentication setup Configuring mutual authentication for clientsConfiguring mutual authentication for indications Configuring Http access Mutual authentication for indicationsHttp access Importing client certificatesExporting server certificates SMI Agent security Configuring user authentication User authentication Encoding proxy connection details Encode proxy detailsSMI Agent service configuration and removal Configuring or removing the SMI Agent as a serviceConfiguring the Http and Https ports Port configurationConfigure Http and Https ports Configure ARR and eventing ports Configuring the ARR and eventing portsFabric Manager database server configuration Configure ARR and eventing portsFirmware download software locations configuration Configuring software locations for firmware downloadFile Path Debugging options for Cimom Debugging and logging options configurationConfiguring debugging options for Cimom Configure debugging options for Cimom Debugging options for the providerConfiguring debugging options for the provider Dynamic UpdateConfiguring logging options for provider Logging options for the providerConfigure logging options Log file examplesCapture provider cache information Capturing information from the provider cache Support information collection Collect support informationRunning an XML dump XML dumpCollecting support information Cimom server configuration Configuring the Cimom serverConfiguring log file options Uncomment the following linesMutual authentication for clients IntroductionEnabling mutual authentication for clients Mutual authentication for indicationsClient configuration to use client certificates Enabling mutual authentication for indicationsClient.ind.truststore Clientind.cer Java -classpath SMIAgent/agent/wbem.jar Troubleshooting XmlerrorXmlerror Frequently Asked Questions General 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 Open source software used in SMI-A AppendixSun Industry Standards Source License Source Code LicenseDistribution Obligations Inability to Comply DUE to Statute or Regulation Termination IBM Common Public License Grant of Rights Commercial Distribution OpenSLP License Bouncy Castle GNU Library General Public LicensePublic Domain Sun Binary Code License AgreementBrocade 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