Brocade Communications Systems 53-1001778-01 manual Fabric Manager database server configuration

Page 50

3 Fabric Manager database server configuration

4. Click Apply.

The changes take effect when you restart the server. Click Start Server to restart the server.

FIGURE 19 Configure ARR and eventing ports

Fabric Manager database server configuration

Configuring a Fabric Manager database server connection allows the Brocade SMI Agent to report on historical port statistics by retrieving the data from the Fabric Manager database server. Not all users have a Fabric Manager server installed and running in their environment. Here you can specify the connection information for an existing Brocade Fabric Manager server. If your management application does not make use of historical port statistics, you do not need to configure a connection to the Fabric Manager database.

The Fabric Manager Database server TCP/IP listener is always started on port 2638, which is registered with Internet Assigned Numbers Authority (IANA). Database connection credentials are not user-customizable and are fixed at the factory.

Configuring the Fabric Manager database server connection parameters

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click Connection Parameters in the menu tree (see Figure 20). The content pane displays the current connection parameters.

The Driver field is already populated with the default driver that is bundled in the agent: com.sybase.jdbc2.jdbc.SybDriver.

Do not change this driver information.

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

Image 50

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 cacheSupport 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