Brocade Communications Systems 53-1001778-01 manual XML dump, Collecting support information

Page 60

3 Support information collection

Collecting support information

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click Collect Information in the menu tree (see Figure 27). The content pane displays the current path for the zip file.

3.To change the path of the zip file, type a new path or click Select Folder to browse for the location.

4.Click Apply.

FIGURE 27 Collect support information

XML dump

An XML dump is a file that enumerates all instances of the leaf classes that have a provider support within all the namespaces in the SMI-A. Classes that represent indications (that have the “Indication” qualifier) are not included. The output is in CIM-XML format.

This procedure generates an XML dump for use in case of any product-related issues. To generate an XML dump, the SMI Agent server should be running.

Running an XML dump

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click Run XML Dump in the menu tree (see Figure 28 on page 45). The content pane displays the current path for the XML file.

3.To change the XML file path, type a new path or click Select Folder to browse for the location.

4.Click Start Server to ensure that the SMI Agent server is running.

5.Click Apply.

44

Brocade SMI Agent User’s Guide

 

53-1001778-01

Image 60
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 What’s new in this document Document conventionsText formatting Identifies command syntax examples Key termsAdditional information Brocade resourcesOther industry 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-AStarting the SMI-A as a service Stop the Brocade SMI AgentStopping the SMI-A 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 AIXInstalling SLP on Windows SLP on WindowsStarting SLP 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 WindowsProxy connections Reloading provider.xml on fabric segmentationAdding proxy connections 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 servicePort configuration Configure Http and Https portsConfiguring the 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 and logging options configuration Configuring debugging options for CimomDebugging 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 provider Configure logging options Log file examplesCapture provider cache information Capturing information from the provider cacheSupport information collection Collect support informationXML dump Collecting support informationRunning an XML dump Cimom server configuration Configuring the Cimom serverConfiguring log file options Uncomment the following linesMutual authentication for clients IntroductionMutual authentication for indications Client configuration to use client certificatesEnabling mutual authentication for clients 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