Brocade Communications Systems 53-1001778-01 manual Open source software used in SMI-A, Appendix

Page 73

 

Appendix

Licenses and Attributions

A

 

 

 

In this chapter

•Open source software used in SMI-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

•Sun Industry Standards Source License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

•IBM Common Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

•OpenSLP License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

•Bouncy Castle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

•GNU Library General Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

•Public Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

•Sun Binary Code License Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Open source software used in SMI-A

The CIM MOF files used with the SMI-A are used with the permission of the Distributed Management Task force (DMTF) and are copyrighted by the DMTF.

Some components of the SMI-A are derived from open source software. For your convenience the licenses are included in this document as well as installed as part of the release.

•WBEM Services open source project (Sun Industry Standards Source License)

The JavaTM WBEM API, J WBEM Server and MOF Compiler are derived from the WBEM Services open source project. The license for WBEM Services is the Sun Industry Standards Source License (SISSL) – section 13.1. For more information on WBEM Services see

http://wbemservices.sourceforge.net/

•Standards Based Linux Instrumentation for Manageability (IBM Common Public License)

The Native Provider Interface (NPI) Provider Protocol Adapter is based on work done in SBLIM (pronounced “sublime”). The Standards Based Linux Instrumentation for Manageability is an IBM Open Source project, intended to enhance the manageability of GNU/Linux systems. The license for SBLIM is the IBM Common Public License. For more information on SBLIM, see

http://www-124.ibm.com/sblim/

•SLP (OpenSLP License)

The SLP implementation uses the openSLP implementation and its license is a BSD style license. For more information on openSLP, see

http://www.openslp.org

•Cryptography Security Library, version 1.19 (Bouncy Castle)

The SMI Agent uses only the RSA algorithm. For more information on The Legion Of The Bouncy Castle, see http://www.bouncycastle.org

Brocade SMI Agent User’s Guide

57

53-1001778-01

 

Page 72 Page 74
Image 73
Page 72 Page 74
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 AgentStop the Brocade SMI Agent Starting the SMI-A as a serviceStopping 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
Top Page Image Contents