Brocade Communications Systems 53-1001778-01 manual Frequently Asked Questions, General questions

Page 69

 

Chapter

Frequently Asked Questions

5

 

 

 

 

In this chapter

General questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

General questions

Besides Windows Domain authentication, does the SMI Agent support local user authentication?

What are some situations that might require restarting the SMI Agent?

What are the Eventing and ARR TCP Ports? Do they relate to indications?

If I have a firewall between the SMIAgent and the Brocade switch, what are the ports that must be opened and in which direction?

What encryption method is used to encrypt the password field in provider.xml?

How do I report a problem and what information should I provide?

How do I collect diagnostic data from the Brocade SMI Agent?

Does the Brocade SMI Agent need to point to every switch in a fabric or just one switch in each fabric to collect the data?

Can the SMI Agent proxy for two fabrics that are in different subnets?

Should I designate multiple proxies into a fabric? What are the best practices concerning this?

Do the start_server and stop_server scripts work if the agent is set to run as a daemon on Linux and Solaris? Do these scripts work if the agent running as a service on Windows or do you have to use the Services window?

In using Windows domain authentication, do I need to include the domain name along with the username for authentication?

Does the SMI Agent have support for HTTPS communication?

Does the SMI Agent work on hosts with multiple IP addresses? If so is there a way to configure the CIMOM to choose a specific NIC/IP? Is there anything special I need to do for the SMI Agent to see proxy switches connected to the second NIC, or will it just work by default?

How do I tell what version of SMI-A I am running?

Besides Windows Domain authentication, does the SMI Agent support local user authentication?

The SMI Agent also supports authenticating the user against the system on which it is installed. By default when you configure security, the user’s credentials (username and password) are validated against the ones present on the local system. To ensure this happens, follow these steps:

1.During SMI-A installation, enable security and select “No” for Windows domain authentication.

2.Create a local user on the Windows system where the agent is installed.

Brocade SMI Agent User’s Guide

53

53-1001778-01

 

Image 69
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