How it Works
Brocade Communications Systems
Loading...
53-1001778-01
User Manual
90 pgs1.13 Mb0
Table of contents
Loading...

Brocade Communications Systems 53-1001778-01 User Manual

53-1001778-01
®
30 March 2010
Brocade SMI Agent
User’s Guide
Supporting SMI Agent 120.11.0
Copyright © 2006-2010 Brocade Communications Systems, Inc. All Rights Reserved.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other open source license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 1745 Technology Drive San Jose, CA 95110 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: info@brocade.com
European Headquarters Brocade Communications Switzerland Sàrl Centre Swissair Tour B - 4ème étage 29, Route de l'Aéroport Case Postale 105 CH-1215 Genève 15 Switzerland Tel: +41 22 799 5640 Fax: +41 22 799 5641 E-mail: emea-info@brocade.com
Asia-Pacific Headquarters Brocade Communications Systems China HK, Ltd. No. 1 Guanghua Road Chao Yang District Units 2718 and 2818 Beijing 100020, China Tel: +8610 6588 8888 Fax: +8610 6588 9999 E-mail: china-info@brocade.com
Asia-Pacific Headquarters Brocade Communications Systems Co., Ltd. (Shenzhen WFOE) Citic Plaza No. 233 Tian He Road North Unit 1308 – 13th Floor Guangzhou, China Tel: +8620 3891 2000 Fax: +8620 3891 2111 E-mail: china-info@brocade.com
Document History
Title Publication number Summary of changes Date
Brocade SMI Agent User’s Guide 53-1000109-01 New document. April 2006
Brocade SMI Agent User’s Guide 53-1000199-01 Updated to support Fabric OS 5.2.0
and SMI-A 110.5.0.
Brocade SMI Agent User’s Guide 53-1000199-02 Rebranded the document using the
new Brocade templates.
Brocade SMI Agent User’s Guide 53-1000446-01 Updated to support Fabric OS 5.3.0
and SMI-A 120.6.0
Brocade SMI Agent User’s Guide 53-1000613-01 Updated to support Fabric OS 6.0.0
and SMI-A 120.7.0.
Brocade SMI Agent User’s Guide 53-1000613-02 Updated to support Fabric OS 6.1.0
and SMI-A 120.7.1.
Brocade SMI Agent User’s Guide 53-1001146-01 Updated to support Fabric OS 6.1.1
and SMI-A 120.7.2
November 2006
March 2007
June 2007
November 2007
March 2008
August 2008
Title Publication number Summary of changes Date
Brocade SMI Agent User’s Guide 53-1001199-01 Updated to support Fabric OS 6.2.0
December 2008
and SMI-A 120.8.0
Brocade SMI Agent User’s Guide 53-1001199-02 Minor corrections to the previous
February 2009
version.
Brocade SMI Agent User’s Guide 53-1001263-01 Updated to support Fabric OS
March 2009
6.1.2_cee and SMI-A 120.9.0
Brocade SMI Agent User’s Guide 53-1001263-02 Updated the procedure for adding
April 2009
proxy connections.
Brocade SMI Agent User’s Guide 53-1001263-03 Updated the Brocade logo. July 2009
Brocade SMI Agent User’s Guide 53-1001535-01 Updated to support Fabric OS 6.3.0
August 2009
and SMI-A 120.10.0.
Brocade SMI Agent User’s Guide 53-1001778-01 Updated to support Fabric OS 6.4.0
March 2010
and SMI-A 120.11.0.
Brocade SMI Agent User’s Guide iii 53-1001778-01
iv Brocade SMI Agent User’s Guide
53-1001778-01

Contents

About This Document
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . x
What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Other industry resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Brocade SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Chapter 1 Overview
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Common Information Model (CIM). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Brocade SMI-S Initiative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2 Brocade SMI Agent
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Start the Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Starting the SMI-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Starting the SMI-A as a service. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Stop the Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Stopping the SMI-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Stopping the SMI-A when mutual authentication for clients is
enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Stopping the SMI-A as a service . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Brocade SMI Agent User’s Guide v 53-1001778-01
Service Location Protocol (SLP) support . . . . . . . . . . . . . . . . . . . . . . . 7
slptool commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SLP on Linux, Solaris, and AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SLP on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Disable HTTP for security reasons . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Connection monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Enable multi-homed support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Configuring IP address for switch-to-SMIAgent communication in
multi-homed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Configuring IP address for SMI Agent client to server communication
in multi-homed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 3 Brocade SMI Agent Configuration
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
About the Brocade SMI Agent Configuration Tool. . . . . . . . . . . . . . .13
Launch the Brocade SMI-A Configuration Tool . . . . . . . . . . . . . . . . .15
Launching the Brocade SMI Agent Configuration Tool (Linux, Solaris,
and AIX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Launching the Brocade SMI Agent Configuration Tool (Windows)15
Proxy connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Reloading provider.xml on fabric segmentation . . . . . . . . . . . .16
Including multiple switch connection entries from the same fabric in
the provider.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Adding proxy connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Removing proxy connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Login failure status information . . . . . . . . . . . . . . . . . . . . . . . . . 17
Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Mapping an SMI-A user to a switch user . . . . . . . . . . . . . . . . . .19
Setting up default SMI-A user mapping . . . . . . . . . . . . . . . . . . . 20
Limitations of SMI-A user-to-switch user mapping . . . . . . . . . . 21
SMI Agent security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Mutual authentication setup. . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Configuring mutual authentication for clients . . . . . . . . . . . . . .22
Configuring mutual authentication for indications . . . . . . . . . .23
Configuring HTTP access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Importing client certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Exporting server certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Viewing or deleting client certificates from SMI-A server truststore27
Configuring user authentication . . . . . . . . . . . . . . . . . . . . . . . . .28
Encoding proxy connection details . . . . . . . . . . . . . . . . . . . . . . . 30
SMI Agent service configuration and removal . . . . . . . . . . . . . . . . . 31
Configuring or removing the SMI Agent as a service. . . . . . . . . 31
Port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Configure HTTP and HTTPS ports . . . . . . . . . . . . . . . . . . . . . . . . 32
Configure ARR and eventing ports . . . . . . . . . . . . . . . . . . . . . . .33
vi Brocade SMI Agent User’s Guide
53-1001778-01
Fabric Manager database server configuration . . . . . . . . . . . . . . . .34
Configuring the Fabric Manager database server connection
parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Firmware download software locations configuration . . . . . . . . . . .35
Configuring software locations for firmware download. . . . . . . 35
Debugging and logging options configuration. . . . . . . . . . . . . . . . . . 37
Debugging options for CIMOM . . . . . . . . . . . . . . . . . . . . . . . . . .37
Debugging options for the provider . . . . . . . . . . . . . . . . . . . . . .38
Logging options for the provider . . . . . . . . . . . . . . . . . . . . . . . . .40
Capture provider cache information . . . . . . . . . . . . . . . . . . . . . . 42
Support information collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Collect support information. . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
XML dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
CIMOM server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Configuring the CIMOM server . . . . . . . . . . . . . . . . . . . . . . . . . .45
Configuring log file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 4 Mutual Authentication for Clients and Indications
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Mutual authentication for clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Enabling mutual authentication for clients . . . . . . . . . . . . . . . .48
Mutual authentication for indications . . . . . . . . . . . . . . . . . . . . . . . .48
Enabling mutual authentication for indications. . . . . . . . . . . . .48
Client configuration to use client certificates . . . . . . . . . . . . . . . . . .48
Configuring a client to use client certificates using a property file49 Configuring a client to use client certificates using system property
values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Configuring a client to use client certificates using client listener
program (mutual authentication for indications only). . . . . . . . 50
Client configuration to use client certificates for default SSL indications 50
Configuring a client for default SSL indications using a property file 50 Configuring a client for default SSL indications using system property
values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Configuring a client for default SSL indications using client listener
program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 5 Frequently Asked Questions
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
General questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Brocade SMI Agent User’s Guide vii 53-1001778-01
Appendix A Licenses and Attributions
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
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
Index
viii Brocade SMI Agent User’s Guide
53-1001778-01

About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
•Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
•Brocade SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

How this document is organized

This document is a user’s guide written for end users to help you learn about starting, stopping, and configuring the Brocade SMI Agent.
This document is organized to help you find the particular information that you want as quickly and easily as possible.
The document contains the following components:
• Chapter 1, “Overview,” provides an overview of the CIM, the Brocade SMI-S initiative, and the
Brocade SMI Agent.
• Chapter 2, “Brocade SMI Agent,” explains how to start and stop the Brocade SMI Agent.
• Chapter 3, “Brocade SMI Agent Configuration,” describes how to use the Brocade SMI Agent
Configuration Tool for configuring SMI-A settings, such as fabric proxy connections, agent security, port settings, and logging options.
• Chapter 4, “Mutual Authentication for Clients and Indications,” explains how to enable mutual
authentication for clients and indications manually, after installation.
• Chapter 5, “Frequently Asked Questions,” provides answers to the most frequently asked
questions sent to the SMI Agent Developer Support e-mail address.
• Appendix A, “Licenses and Attributions,” includes the licenses for open source software.
Brocade SMI Agent User’s Guide ix 53-1001778-01

Supported hardware and software

In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies exactly which switches are supported and which are not.
Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for SMI-A 120.11.0, documenting all possible configurations and scenarios is beyond the scope of this document.
The following hardware platforms are supported by this release of Brocade SMI Agent 120.11.0:
• Brocade 200E switch
• Brocade 300 switch
• Brocade 3000 switch
• Brocade 3014 switch
• Brocade 3016 switch
• Brocade 3200 switch
• Brocade 3250 switch
• Brocade 3600 switch
• Brocade 3800 switch
• Brocade 3850 switch
• Brocade 3900 switch
• Brocade 4012 switch
• Brocade 4016 switch
• Brocade 4018 switch
• Brocade 4020 switch
• Brocade 4024 switch
• Brocade 4100 switch
• Brocade 4424 switch
• Brocade 4900 switch
• Brocade 5000 switch
• Brocade 5100 switch
• Brocade 5300 switch
• Brocade 5410 switch
• Brocade M5424 switch
• Brocade 5460 switch
• Brocade 5470 switch
• Brocade 5480 switch
• Brocade 7500 Extension Switch
• Brocade 7500E Extension Switch
• Brocade 7600 Application Appliance
• Brocade 7800 Extension Switch
x Brocade SMI Agent User’s Guide
53-1001778-01
• Brocade 8000 Application Appliance
• Brocade 8470 switch
• Brocade VA-40FC switch
• Brocade 12000 director (only on Fabric OS 5.0.x)
• Brocade 24000 director (single domain only)
• Brocade 48000 director
• Brocade Encryption Switch
• Brocade Multiprotocol Router Model AP7420 (only as a non-proxy switch)
• Brocade DCX Data Center Backbone
• Brocade DCX-4S Data Center Backbone
• The following blades are supported on the Brocade DCX and DCX-4S:
- Port blades: FC8-16, FC8-32, FC8-48, FC8-64
- FC4 port blades
- FC10-6
- FC4-16IP
- FC4-48C
- FCoE10-24
- FA4-18
- FR4-18i
- FS8-18
- FX8-24

What’s new in this document

• New hardware platform supported (Brocade 8470)
• New blade supported (FC8-64)

Document conventions

This section describes text formatting conventions and important notice formats used in this document.

Text formatting

The narrative-text formatting conventions that are used are as follows:
bold text Identifies command and method names
Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI
Brocade SMI Agent User’s Guide xi 53-1001778-01
italic text Provides emphasis
NOTE
ATTENTION
Identifies variables Identifies class properties Identifies paths and Internet addresses Identifies document titles
code text Identifies CLI output
Identifies command syntax examples
For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive.

Notes, cautions, and warnings

The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.
A note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information.
An Attention statement indicates potential damage to hardware or data.

Key terms

For definitions specific to Brocade and Fibre Channel, see the technical glossaries on Brocade Connect. See “Brocade resources” on page xiii for instructions on accessing Brocade Connect.
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at:
http://www.snia.org/education/dictionary

Notice to the reader

This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
Corporation Referenced Trademarks and Products
IBM Corporation AIX
Linus Torvalds Linux
Microsoft Corporation Windows, Windows NT, Internet Explorer
Novell, Inc. SUSE
xii Brocade SMI Agent User’s Guide
53-1001778-01
Corporation Referenced Trademarks and Products
Sun Microsystems, Inc. Sun, Solaris
Red Hat, Inc. Red Hat, Red Hat Network
VMware, Inc. VMware

Additional information

This section lists additional Brocade and industry-specific documentation that you might find helpful.

Brocade resources

The following SMI-A documentation can be obtained from developer support at Brocade:
• Brocade SMI Agent Installation Guide
• Brocade SMI Agent Developer’s Guide
To get up-to-the-minute information, go to http://my.brocade.com and register at no cost for a user ID and password.
For practical discussions about SAN design, implementation, and maintenance, you can obtain
Building SANs with Brocade Fabric Switches through:
http://www.amazon.com
For additional Brocade documentation, visit the Brocade Web site:
http://www.brocade.com
Release notes are available on the My Brocade web site and are also bundled with the Fabric OS firmware.

Other industry resources

For information about the Distributed Management Task Force (DMTF), including information about CIM standards and educational materials:
http://www.dmtf.org
For information about the Storage Management Initiative (SMI) of the Storage Networking Industry Association (SNIA), including the Storage Management Initiative Specification (SMI-S):
http://www.snia.org/smi/home
For information about Web Based Enterprise Management (WBEM):
http://wbemservices.sourceforge.net/
For additional resource information, visit the Technical Committee T11 Web site. This Web site provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications:
http://www.t11.org
Brocade SMI Agent User’s Guide xiii 53-1001778-01
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web site:
http://www.fibrechannel.org

Getting technical help

Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available:
1. General Information
• Switch model
• Switch operating system version
• Software name and software version, if applicable
• Error numbers and messages received
• supportSave command output
• Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs
• syslog message logs
2. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number label, as illustrated below.:
*FT00X0054E9*
FT00X0054E9
The serial number label is located as follows:
• Brocade 200E—On the nonport side of the chassis
• Brocade 300, 4100, 4900, 5100, 5300, 7500, 7500E, 7800, 8000, VA-40FC, and
Brocade Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side on the left
• Brocade 3014—On the top of the chassis, under the insertion arm
• Brocade 3016 and 4012—On the bottom of the switch module
• Brocade 3250, 3850, and 7600—On the bottom of the chassis
• Brocade 3900— Nonport side of the chassis
• Brocade 4016—On the top of the switch module
• Brocade 4018—On the top of the blade
• Brocade 4020 and 4024—On the bottom of the switch module
• Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the
switch
xiv Brocade SMI Agent User’s Guide
53-1001778-01
• Brocade 8470—On the top of the chassis
• Brocade 12000, 24000, and 48000—Inside the chassis next to the power supply bays
• Brocade DCX—On the bottom right on the port side of the chassis
• Brocade DCX-4S—On the bottom right on the port side of the chassis, directly above the
cable management comb.
• Brocade Multiprotocol Router Model AP7420—On the bottom of the chassis and on the
back of the chassis.
1. World Wide Name (WWN)
Use the licenseIdShow command to display the WWN of the chassis.
If you cannot use the licenseIdShow command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX. For the Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo plate at the top of the nonport side of the chassis.
For the Brocade Multiprotocol Router Model AP7420: Provide the switch WWN. Use the switchShow command to display the switch WWN.

Brocade SMI Agent support

Report any problems or issues in using the Brocade SMI Agent to the following e-mail address:
support@brocade.com
When contacting support at Brocade, provide the following:
• Operating system version and patch level
• Sample code exhibiting problem (if possible)
• Switch models and operating system versions, including the proxy switch
• Compiler version
• Error messages received
• XML received from the Brocade SMI Agent
• XML sent to the Brocade SMI Agent
• Steps followed to produce the problem
• Server-side console output and log files
• Thread dump, if the SMI Agent is hanging or if memory consumption goes up
You can use the SMI Agent Configuration Tool, which is described in this document, to collect the required support information to be sent.
Brocade SMI Agent User’s Guide xv 53-1001778-01

Document feedback

Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to:
documentation@brocade.com
Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
xvi Brocade SMI Agent User’s Guide
53-1001778-01
Chapter

Overview

In this chapter

•Common Information Model (CIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
•Brocade SMI-S Initiative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
•Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Common Information Model (CIM)

The Common Information Model (CIM) is a conceptual, object-based information model defined by the Distributed Management Task Force (DMTF) for describing management, which is not bound to a particular implementation. This allows for the interchange of management information between management systems and applications.
CIM consists of two parts:
• CIM Specification
• CIM Schema
The CIM Specification describes the language, naming, metaschema, and mapping techniques to other management models, such as SNMP MIBs and FC-GS. The metaschema is a formal definition of the model that defines the terms used to express the model and their usage and semantics. The elements of the metaschema are classes, properties, and methods. The metaschema also supports indications and associations as types of classes and references as types of properties.
1
The CIM Schema provides the actual model descriptions. The CIM Schema supplies a set of classes with properties and associations that provide a well-understood conceptual framework within which it is possible to organize the available information about the managed environment. The CIM Schema itself is structured into three distinct layers:
• Core Schema
• Common Schema
• Extension Schema
The Core Schema defines basic classes, such as a managed element or an association. The Common Schema provides a set of foundation classes that can be used as the super-class to describe other devices, such as a system, a device, or a network. The Extension Schema allows users to expand the definitions in the Common Schema to describe specific device types, such as a Brocade FC switch.
The formal definition of the CIM Schema is expressed in a managed object format (MOF) file, which is an ASCII file that can be used as input into a MOF editor, parser, or compiler to generate code for use in a provider or client application.
Web-Based Enterprise Management (WBEM) is a set of management and internet standard technologies to unify management of an enterprise. It includes CIM, CIM Schemas, CIM operations over HTTP, and CIM-XML encoding.
Brocade SMI Agent User’s Guide 1 53-1001778-01

Brocade SMI-S Initiative

Storage
Applications
Mainframes
SMI
Events
Databases
1
Brocade SMI-S Initiative
Storage Management Initiative (SMI) is a broad-based initiative sponsored by the Storage Networking Industry Association (SNIA) that is standardizing all aspects of storage management for multivendor storage networking products. SMI encompasses the storage aspects of CIM, as shown in Figure 1.

Brocade SMI Agent

FIGURE 1 Storage Management Initiative
The Storage Management Initiative Specification (SMI-S) defines the interface that allows storage management systems to manage and monitor storage area network (SAN) resources.
SMI-S is the only standard that addresses manageability from the perspective of a logical unit number (LUN) in a storage array, all the way through the data path, to an application running on a host. The standard promises to remove much of the vendor-specific issues associated with managing storage, storage networks, hosts, and applications by providing a common interface and management paradigm across the full scope of application and storage management. This in turn will improve the interoperability of various management products and allow more products to be managed by most management environments. Customers will benefit from a much wider choice of broad-based management applications.
The Brocade SMI Agent (SMI-A) is a “proxy” agent to multiple fabrics; it resides on a separate host. The SMI-A does not require any modification or upgrade to deployed fabrics when it is deployed. All the support required in Brocade switches is already in place. Figure 2 on page 3 shows the high-level architecture of the SMI-A.
2 Brocade SMI Agent User’s Guide
53-1001778-01
Brocade SMI Agent
Brocade
CIM Object Manager
(CIMOM)
Management
Provider
CIM Client CIM Client CIM Client
Provider
Provider
Provider
Brocade SMI Agent
Application
1
FIGURE 2 Brocade SMI Agent high-level architecture
The Brocade SMI Agent supports the evolving SMI-S standard and the Brocade functionality not available through the standard.
The Brocade SMI Agent provides the following features:
• CIM agent compliant with SMI-S, with support for the following profiles:
• Server profile (supported by the SMI-A with CIMOM vendor-supplied providers)
• Fabric profile
• Switch profile
• Extender profile (discovery only)
• FC HBA profile
The Brocade SMI Agent Developer’s Guide has additional information about the supported profiles and subprofiles.
• Additional support for physical objects such as chassis, blades, fans, power supplies,
temperature sensors, and transceivers
• Support for the following:
• Connection and account management
• Port performance and error statistics
• HBA and device information via FDMI
• Configuration download to switches
• Firmware download to switches
Brocade SMI Agent User’s Guide 3 53-1001778-01
Brocade SMI Agent
1
• SLP (Service Location Protocol) to discover SMI-S profiles
• CIM agent management using CIM
• Indications: life-cycle indications for fabrics, SANs, nodes, switches, and switch ports; and
alert indications for many fabric events.
• Basic support for non-Brocade switches (switches, ports, topology information, and so on)
• HTTP and HTTPS protocols
• HTTP and HTTPS port configuration
• Mutual authentication for clients and indications
• Security authorization using native OS access control mechanisms
• Provider logging of exceptions, operations, and performance metrics for diagnostic
purposes
• Secure SAN fabrics
• Secure RPC communication
• CIM queries, using WBEM Query Language (WQL)
• DMTF CIM Schema v2.19 (final)
4 Brocade SMI Agent User’s Guide
53-1001778-01
Chapter
NOTE

Brocade SMI Agent

In this chapter

•Start the Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
•Stop the Brocade SMI Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
•Service Location Protocol (SLP) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
•Disable HTTP for security reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
•Connection monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
•Enable multi-homed support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Start the Brocade SMI Agent

There are two ways you can start the SMI-A:
• from the command line
• as a service or daemon
You can start the SMI-A as a service only if the option to start as a service was selected during installation or if you configure the SMI-A as a service using the Brocade SMI-A Configuration Tool, as described in “SMI Agent service configuration and removal” on page 31.
2
The following procedures describe how to start the SMI-A without security and with security enabled.
By default, security is disabled on all platforms. In this case, security is the authentication of the client username and password (and domain name, if security is enabled on Windows by selecting domain authentication) when connecting to the server. The procedure for enabling security varies, depending on the platform.
On Solaris, Linux, or AIX, if security is enabled for the SMI-A, start the SMI-A as a root using the start_server script.
This document uses <SMIAgent> to refer to the installation folder, although your installation folder might be different (if you changed it from the default).

Starting the SMI-A

1. Type the following at the command line:
On Linux, Solaris, and AIX:
sh <SMIAgent>/agent/server/jserver/bin/start_server.sh
Brocade SMI Agent User’s Guide 5 53-1001778-01

Stop the Brocade SMI Agent

NOTE
2
On Windows:
<SMIAgent>\agent\server\jserver\bin\start_server.bat
On Windows, you can also click Start > Programs > SMIAgent > Start CIMOM.
The SMI-A is now ready to use.

Starting 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/start_agent_service.sh
On Windows:
<SMIAgent>\agent\server\jserver\bin\start_agent_service.bat
On Windows, you can also click Start > Programs > SMIAgent > Start SMI Agent Service.
Stop the Brocade SMI Agent
To stop the SMI-A, refer to the following procedures. If mutual authentication for clients is enabled and the HTTP service is disabled, use the procedure “Stopping the SMI-A when mutual
authentication for clients is enabled”.
If the SLP daemon was started, stop the daemon using the procedures described in “Service
Location Protocol (SLP) support” on page 7.
On Linux, Solaris, or AIX, if security is enabled for the agent, then the stop_server or stop_agent_service command should be provided with a username and password. For example:
sh <SMIAgent>/agent/server/jserver/bin/stop_server.sh -s
http://localhost:<portnum>/interop -u <username> -p <password>

Stopping the SMI-A

1. Select one of the following options depending on your operating system:
a. On Windows, select Start > Programs > SMIAgent > Stop CIMOM.
1. Alternatively, you can open a command prompt that is different from the window in which the start_server.bat file is running.
2. Run the following:
<SMIAgent>/agent/server/jserver/bin/stop_server.bat
a. On Linux, Solaris, or AIX, become the root user: for example, % su root.
Run the following:
sh <SMIAgent>/agent/server/jserver/bin/stop_server.sh
-s http://localhost:portnum/interop
The protocol, host, and port information are required only when the defaults are changed.
6 Brocade SMI Agent User’s Guide
53-1001778-01

Service Location Protocol (SLP) support

NOTE
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.
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
Service Location Protocol (SLP) support
NOTE
2
• slptool script that starts up the slptool platform-specific program
• slptool program that can be used to verify that SLP is operating properly. A different slptool
exists for Solaris, Linux, AIX, and Windows.
By default, the SMI-A is configured to advertise itself as a Service Agent (SA). The advertised SLP template shows its location (IP address) and the WBEM Services it supports. The default advertised WBEM services show that the SMI-A:
• accepts WBEM requests over HTTP without SSL on TCP port 5988
• accepts WBEM requests over HTTPS using SSL on TCP port 5989

slptool commands

Although the IP address shown below might vary, the following slptool commands can be used to verify that the SLP is operating properly:
• slptool findsrvs service:service-agent
This command verifies that the SMI-A SLP service is properly running as a Service Agent (SA). Although the IP address might be different, it should produce output similar to the following:
service:service-agent://127.0.0.1,65535
• slptool findsrvs service:wbem
This command verifies that the SMI-A SLP service is properly advertising its WBEM services. Although the IP address might be different, it should produce output similar to the following:
service:wbem:https://10.0.1.3:5989,65535 service:wbem:http://10.0.1.3:5988,65535
This output shows that the SMI-A:
• accepts WBEM requests over HTTP using SSL on TCP port 5989
• accepts WBEM requests over HTTP without SSL on TCP port 5988
• slptool findattrs service:wbem:http://10.0.1.2:5988
This command verifies that the SMI-A SLP service is properly advertising its WBEM SLP template over the HTTP protocol. Note: Change the IP Address:Port to those displayed by slptool findsrvs service:wbem.
• slptool findattrs service:wbem:https://10.0.1.2:5989
This command verifies that the SMI-A SLP service is properly advertising its WBEM SLP template over the HTTPS protocol.
Change the IP Address:Port to those displayed by slptool findsrvs service:wbem.

SLP on Linux, Solaris, and AIX

On Linux, Solaris, and AIX, you do not need to install the SLP service.
8 Brocade SMI Agent User’s Guide
53-1001778-01
Service Location Protocol (SLP) support
NOTE
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:
2
# 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.
Change the IP Address:Port to those displayed by slptool findsrvs service:wbem:
Brocade SMI Agent User’s Guide 9 53-1001778-01
Service Location Protocol (SLP) support
2
# <SMIAgent>/agent/bin/slptool findattrs service:wbem:http://192.168.0.100:5988
# <SMIAgent>/agent/bin/slptool findattrs service:wbem:https://192.168.0.100:5989

SLP on Windows

This section describes how to install, start, and verify the SLP daemon on Windows.
On Windows, the SLP service must be installed from a command prompt. It need only be installed once, but must be installed before starting the SMI-A.
Installing SLP on Windows
1. Open a command prompt via Start > Programs > Accessories > Command Prompt.
2. Change to the directory where slpd.bat is located:
cd C:\<SMIAgent>\agent\bin
3. Run slpd -install to install the SLP service into Windows. If SLP is already installed, the following message displays:
CreateService failed - The specified service already exists. (0x431)
Starting SLP on Windows
1. Install the SLP service, as described in “Installing SLP on Windows”.
2. Open a command prompt via Start > Programs > Accessories > Command Prompt.
3. Change to the directory where slpd.bat is located:
cd C:\<SMIAgent>\agent\bin
4. Run slpd -start to start the SLP service.
You can also start the SLP service from the Windows Service Console. If the SLP is installed as a Windows service, you should access the Services Console and ensure that the startup is set to Automatic.
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 be statically registered 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
10 Brocade SMI Agent User’s Guide
53-1001778-01

Disable HTTP for security reasons

NOTE
2
Verifying that the SLP service is correctly installed and operating
1. Start the SLP service and SMI-A.
2. Open a command prompt via Start > Programs > Accessories > Command Prompt.
3. Change to the directory where slpd.bat is located:
cd C:\<SMIAgent>\agent\bin
4. Verify that the SLP service is properly running as a Service Agent.
> slptool findsrvs service:service-agent
5. Verify that the SLP service is properly advertising its WBEM services:
> slptool findsrvs service:wbem
6. Verify that the SLP service is properly advertising its WBEM SLP template over its configured Client Protocol Adapters. Note: Change the IP Address:Port to those displayed by slptool findsrvs service:wbem
> slptool findattrs service:wbem:http://192.168.0.100:5988 > slptool findattrs service:wbem:https://192.168.0.100:5989
Disable HTTP for security reasons
If security or mutual authentication is enabled, you might want to disable the unsecure HTTP protocol, leaving only the secure HTTPS enabled. There are two ways to enable and disable the HTTP protocol:
• Use the SMI-A Configuration Tool (see “Configuring HTTP access” on page 24).
• Use the command-line scripts packaged by the SMI-A installer.
The SMI-A installer packages the scripts DeleteXMLProtocolAdapter to permanently disable the HTTP port used by the SMI-A and CreateXMLProtocolAdapter to enable the HTTP port again. These scripts can be found in the following directory:
<SMIAgent>/agent/bin

Connection monitoring

The SMI-A handles connection monitoring for the connection to the proxy switch. Whenever there is a connection failure to the proxy switch, by default the SMI-A automatically tries to reconnect to the proxy switch 5 times with a wait time of 90 seconds between each retry. This process is repeated every 30 minutes until the connection is reestablished to the proxy switch.
The actual time between each retry is the 90-second wait time plus the retry time (the time spent on reestablishing the connection to the proxy switch). The retry time is beyond the SMI Agent’s control.
These default values of 5 retries, 90-second sleep interval between retries, and 30 minutes between each retry process are all configurable through the Brocade_ConnectionMonitoringService and through instances of Brocade_ConnectionMonitor. These values are not configurable through the SMI-A installer or configuration tool.
Brocade SMI Agent User’s Guide 11 53-1001778-01
Loading...
+ 63 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use