Brocade Communications Systems 53-1001778-01 manual Service Location Protocol SLP support

Page 23

Service Location Protocol (SLP) support

2

Stopping the SMI-A when mutual authentication for clients is enabled

1.Modify the stop_server script to specify the CLASSPATH for the WbemClient.properties file. (See “Client configuration to use client certificates” on page 48 if the WbemClient.properties file is not used.)

The CLASSPATH should contain only the path to the directory where the file is present and not the path to the file itself. For example, if the WbemClient.properties file is located at C:\SMIAgent\agent, then the CLASSPATH should be:

C:\SMIAgent\agent

2. Run the following command to stop the SMI-A:

<SMIAgent>/agent/server/jserver/bin/stop_server -s https://localhost:<HTTPSPort>/interop

This command is the same on all platforms. The protocol, host, and port information are required only when the defaults are changed.

Stopping the SMI-A as a service

1. Type the following at the command line: On Linux, Solaris, and AIX:

sh <SMIAgent>/agent/server/jserver/bin/stop_agent_service.sh -s http://localhost:<portnum>/interop

On Windows:

<SMIAgent>\agent\server\jserver\bin\stop_agent_service.bat

On Windows, you can also click Start > Programs > SMIAgent > Stop SMI Agent Service.

Service Location Protocol (SLP) support

The Brocade SMI Agent supports SLP to allow applications to discover the existence, location, and configuration of WBEM services in enterprise networks.

A WBEM client is not required to use SLP discovery to find a WBEM Server; that is, it might already know about the location and capabilities of the WBEM Server to which it wants to send its requests. In such environments, starting the SLP component of the SMI-A is not needed.

However, in a dynamically changing enterprise network environment, many WBEM clients might choose to use SLP discovery to find the location and capabilities of other WBEM Servers. In such environments, the SLP component of the SMI-A should be started to allow advertisement of its existence, location, and capabilities.

NOTE

If you want SLP support, you must install and start the SLP daemon prior to starting the SMI-A.

Brocade SMI Agent SLP support consists of the following components:

•slpd script that starts up the slpd platform-specific program

•slpd program that acts as a Service Agent (SA). A different slpd binary executable exists for Solaris, Linux, AIX, and Windows.

Brocade SMI Agent User’s Guide

7

53-1001778-01

 

Page 22 Page 24
Image 23
Page 22 Page 24
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
Top Page Image Contents