Brocade Communications Systems 53-1001778-01 manual

Page 71

General questions

5

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

Yes.

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

You can have only one connection at a time into the fabric. The only advantage in designating multiple proxies is that if the first proxy fails to connect, the SMI-A tries the next proxy until it finds one that works.

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?

If the agent is set to run as a daemon on Linux, Solaris, and AIX, or as a service on Windows. use the start_agent_service and stop_agent_service scripts instead. On Windows, you can also use the Services window.

On Linux, Solaris, and AIX, you must have root permissions to stop the service. The best way to start and stop the server is to use the Configuration Tool.

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

No. You should provide only the username, as shown:

UserPrincipal up = new UserPrincipal("username");

PasswordCredential pc = new PasswordCredential("password");

Does the SMI Agent have support for HTTPS communication?

Yes, the SMI Agent supports HTTPS (the combination of a normal HTTP interaction over an encrypted secure socket layer (SSL) or transport layer security (TLS) transport mechanism) between the CIMClient and SMI Agent. The Brocade SMI Agent also supports secure communication between the SMI Agent and the fabric via secure RPC.

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?

Starting with 120.6.0 the Brocade SMI Agent supports multi-homed hosts. Some systems have multiple network interfaces that are connected to different IP subnets. Each connection uses a different IP address. By default, the CIMOM uses all IP addresses used by the system. To configure the CIMOM to use only a specific IP address, modify the jserver.properties file found at

.../server/jserver/bin with the following entry:

HostIPAddress=<specific ip address>

This forces the CIMOM to only use the network interface with <specific IP address> even though the system uses other network interfaces with different IP addresses.

To configure the IP address for Switch-to-SMIAgent communication in multi-homed systems, see “Enable multi-homed support” on page 12.

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

The title bar in the Brocade SMI Agent Configuration Tool displays the version of the SMI-A, for versions 120.7.0 and later. See Figure 3 on page 14 for an example.

Brocade SMI Agent User’s Guide

55

53-1001778-01

 

Image 71
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 clientsEnabling mutual authentication for indications Mutual authentication for indicationsClient configuration to use client certificates Enabling mutual authentication for clientsClient.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