Brocade Communications Systems 53-1001778-01 manual Starting SLP on Linux, Solaris, and AIX

Page 25

Service Location Protocol (SLP) support

2

Starting SLP on Linux, Solaris, and AIX

1.Become the root user:

% su root

2.Check that the SLP daemon is not already started:

#ps -eaf grep slpd

3.Start the SLP daemon, if one is not already started:

#<SMIAgent>/agent/bin/slpd

Stopping SLP on Linux, Solaris, and AIX

1.Become the root user:

% su root

2.Find the process ID for the SLP daemon:

#ps -eaf grep slpd

3.Stop the SLP daemon process, if found:

#kill -9<slp_process_id>

An SLP log file can be found at:

<SMIAgent>/agent/cfg/slp.log

The SLP daemon can be reconfigured by modifying the following file:

<SMIAgent>/agent/cfg/slp.conf

Applications that do not dynamically register themselves with SLP using SLPAPIs can instead register statically by modifying the following file:

<SMIAgent>/agent/cfg/slp.reg

For more information about these files, read the comments contained in them, or read:

http://www.openslp.org/doc/html/UsersGuide/index.html

Verifying that the SLP service is correctly installed and operating

1.Become the root user:

% su root

2.Verify that the SLP service is properly running as a Service Agent (SA):

#<SMIAgent>/agent/bin/slptool findsrvs service:service-agent

3.Verify that the SLP service is properly advertising its WBEM services:

#<SMIAgent>/agent/bin/slptool findsrvs service:wbem

4.Verify that the SLP service is properly advertising the WBEM SLP template over its configured client protocol adapters.

NOTE

Change the IP Address:Port to those displayed by slptool findsrvs service:wbem:

Brocade SMI Agent User’s Guide

9

53-1001778-01

 

Image 25
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 Document conventions What’s new in this documentText formatting Key terms Identifies command syntax examplesBrocade resources Additional informationOther industry 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 Agent Stop the Brocade SMI Agent Starting the SMI-A as a service Stopping the SMI-A 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 AIXSLP on Windows Installing SLP on WindowsStarting SLP 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 ToolReloading provider.xml on fabric segmentation Proxy connectionsAdding proxy connections 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 removalConfigure Http and Https ports Port configurationConfiguring the 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 Configuring debugging options for Cimom Debugging and logging options configurationDebugging 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 collectionCollecting support information XML dumpRunning an XML dump Configuring the Cimom server Cimom server configurationUncomment the following lines Configuring log file optionsIntroduction Mutual authentication for clientsClient configuration to use client certificates Mutual authentication for indicationsEnabling mutual authentication for clients Enabling mutual authentication for indicationsClient.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