Brocade Communications Systems 53-1001778-01 Port configuration, Configure Http and Https ports

Page 48

3 Port configuration

Port configuration

This section describes how to configure the HTTP, HTTPS, ARR, and Eventing ports.

“Configure HTTP and HTTPS ports” on page 32

“Configure ARR and eventing ports” on page 33

Configure HTTP and HTTPS ports

The SMI-A includes the CIM-XML and CIM-XMLS Client Protocol Adapters (CPA). By default, all are installed and enabled for use. Each CPA uses a different TCP port to exchange WBEM requests and responses. By default, the SMI-A has configured its supported CPAs to use the following ports:

CIM-XMLS (HTTPS) on TCP port 5989

CIM-XML (HTTP) on TCP port 5988

If multiple CIM agents are running at the same time on a system, they cannot use the same ports. For example, some operating systems (such as Solaris 8 and Solaris 9) have a CIM agent preinstalled and already running on standard CIM TCP ports. This can cause conflicts with the SMI-A if both agents are listening on the same ports. In this case, you must configure each SMI-A to use different ports. Refer to your operating system documentation for more information on whether a CIM agent is running.

When you choose values for the HTTP and HTTPS ports, make sure they are not one of the assigned TCP ports. The Configuration Tool does not check for this. You can see a list of assigned TCP ports at:

http://www.iana.org/assignments/port-numbers

Configuring the HTTP and HTTPS ports

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click Server in the menu tree (see Figure 18 on page 33).

The content pane displays the current and configured HTTP and HTTPS ports.

Current means the SMI Agent is currently using these ports, provided the server is running. Configured means the configuration is not in effect currently, but will be used when the server is restarted.

3.To change the settings, type new values in the Configured HTTP Port and Configured HTTPS Port fields.

The value must be between 1 and 65535, inclusive.

Make sure the ports are not in use before you assign them; otherwise, the results will be unpredictable.

4.Click Apply.

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

32

Brocade SMI Agent User’s Guide

 

53-1001778-01

Image 48
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 providerConfigure 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