Brocade Communications Systems 53-1001778-01 manual

Page 70

5 General questions

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

Restarting of the SMIAgent is required when:

configuration parameters, such as the debug level or log file name, are changed.

host IP, HTTP, or HTTPS port is changed.

firmware download configuration entry in SMIAgentConfig.xml is changed.

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

These are ports that are used by the agent to receive events and ARP responses from the fabric. The client is not required to fill in these ports; the operating system selects the ports dynamically. One probable use case for specifying these ports is if there is a firewall between the fabric and the host. In this case, you can specify a fixed port to be opened by the administrator for eventing or ARR.

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

At login the Brocade SMI Agent first contacts the switch through RPC on portmapper port 111. All other calls to the switch are through RPC on ports 897 (non-secure) and 898 (secure).

The ARR and Eventing ports that you select are those on the Brocade SMI Agent host.

If there is a firewall between the Brocade SMI Agent and the Brocade fabric, the following ports must be opened:

SMIAgent to Switch:

111

897

898

Switch to SMIAgent:

Your ARR and Eventing port selections

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

The SMI Agent comes with a utility to encrypt the password. This utility is present in the following directory:

Linux, Solaris, and AIX:<SMIAgent>/agent/bin/PasswordEncryptor

Windows: <SMIAgent>\agent\bin\PasswordEncryptor.bat

Use this utility to encrypt the password.

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

Please fill in the “Submit Problem Report” form at the partner web site. See “Document feedback” on page xvi for additional information.

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

The Brocade SMI Agent Configuration Tool (described in this document) can be used to collect required data.

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?

Just one switch per fabric.

54

Brocade SMI Agent User’s Guide

 

53-1001778-01

Image 70
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 Document conventions What’s new in this documentText formatting Identifies command syntax examples Key termsBrocade resources Additional informationOther 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-AStop the Brocade SMI Agent Starting the SMI-A as a serviceStopping 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 AIXSLP on Windows Installing 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 WindowsReloading provider.xml on fabric segmentation Proxy connectionsAdding 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 serviceConfigure Http and Https ports Port configurationConfiguring 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 Configuring debugging options for Cimom Debugging and logging options configurationDebugging 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 cacheSupport information collection Collect support informationCollecting support information XML dumpRunning an XML dump 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