Smiagent120.11.0 InstallGuide

53-1001777-01 ®
30 March 2010
Brocade SMI Agent

Installation Guide
Supporting SMI Agent 120.11.0

Copyright © 2006-2010 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol,
DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or
services of their respective owners.
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 Asia-Pacific Headquarters
Brocade Communications Systems, Inc. Brocade Communications Systems China HK, Ltd.
1745 Technology Drive No. 1 Guanghua Road
San Jose, CA 95110 Chao Yang District
Tel: 1-408-333-8000 Units 2718 and 2818
Fax: 1-408-333-8101 Beijing 100020, China
E-mail: info@brocade.com Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
European Headquarters Asia-Pacific Headquarters

Brocade Communications Switzerland Sàrl Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Centre Swissair Citic Plaza
Tour B - 4ème étage No. 233 Tian He Road North
29, Route de l'Aéroport Unit 1308 – 13th Floor
Case Postale 105 Guangzhou, China
CH-1215 Genève 15 Tel: +8620 3891 2000
Switzerland Fax: +8620 3891 2111
Tel: +41 22 799 5640 E-mail: china-info@brocade.com
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Document History
Title Publication number Summary of changes Date
Brocade SMI Agent Installation Guide 53-1000054-01 New document. April 2006
Brocade SMI Agent Installation Guide 53-1000054-02 Removed VM directory from CD May 2006
image path.
Brocade SMI Agent Installation Guide 53-1000198-01 Updated to support the 110.5.0 November 2006
release.
Brocade SMI Agent Installation Guide 53-1000198-02 Rebranded the document using March 2007
the new Brocade templates.
Brocade SMI Agent Installation Guide 53-1000445-01 Updated to support the 120.6.0 June 2007
release
Brocade SMI Agent Installation Guide 53-1000445-02 Updated the supported Kernel July 2007
versions for Linux.
Brocade SMI Agent Installation Guide 53-1000612-01 Updated to support the 120.7.0 November 2007
release.
Title Publication number Summary of changes Date
Brocade SMI Agent Installation Guide 53-1000612-02 Updated to support the 120.7.1 March 2008
release.
Brocade SMI Agent Installation Guide 53-1001145-01 Updated to support the 120.7.2 August 2008
release.
Brocade SMI Agent Installation Guide 53-1001198-01 Updated to support the 120.8.0 December 2008
release.
Brocade SMI Agent Installation Guide 53-1001198-02 Minor corrections to the previous February 2009
version.
release.
Brocade SMI Agent Installation Guide 53-1001262-02 Update description of Proxy April 2009
configuration dialog box.
Brocade SMI Agent Installation Guide 53-1001262-03 Minor corrections to the previous July 2009
version.
Brocade SMI Agent Installation Guide 53-1001534-01 Updated to support the 120.10.0 August 2009
release.
release.
Brocade SMI Agent Installation Guide iii

53-1001777-01
iv Brocade SMI Agent Installation Guide
53-1001777-01
Contents
About This Document

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . vii
What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Brocade SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1 Installation Requirements

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Platform requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
SMI-A (Fabric OS) and SMI (EOS) coexistence requirements. . . . . . . 3
Installing SMI-A (Fabric OS) and SMI (EOS) on the same host . . 3
Chapter 2 Installing the SMI Agent

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Before installing the SMI Agent on Linux, Solaris, and AIX . . . . . . . . 5
Install the Brocade SMI Agent using the wizard . . . . . . . . . . . . . . . . . 6
Installing the SMI-A using the wizard . . . . . . . . . . . . . . . . . . . . . . 6
Install the Brocade SMI Agent in silent mode . . . . . . . . . . . . . . . . . . 26
Creating a properties file for silent installation . . . . . . . . . . . . . 27
Silent mode installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Post-installation considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Brocade SMI Agent Installation Guide v

53-1001777-01
Enable multi-homed support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring IP address for switch-to-SMIAgent communication in
multi-homed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuring IP address for SMI Agent client-to-server communication
in multi-homed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Uninstall the Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Uninstalling the SMI-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3 Silent Installation Status Messages
Chapter 4 Frequently Asked Questions
Index
vi Brocade SMI Agent Installation Guide

53-1001777-01
About This Document
In this chapter
• How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
• Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
• What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
• Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
• Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
• Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
• Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
• Brocade SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
• Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
How this document is organized

This document is an installation guide written for users who need to install 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, “Installation Requirements” lists the memory requirements and supported
platforms for the Brocade SMI Agent.
• Chapter 2, “Installing the SMI Agent” explains how to install and uninstall the Brocade SMI
Agent.
• Chapter 3, “Silent Installation Status Messages” lists the status messages that you might
encounter when performing a silent installation of the Brocade SMI Agent.
• Chapter 4, “Frequently Asked Questions” provides answers to the most frequently asked
questions sent to the SMI Agent Developer Support e-mail address.
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.
Brocade SMI Agent Installation Guide vii

53-1001777-01
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 M5424 switch
• Brocade 7500 Extension Switch
• Brocade 7500E Extension Switch
• Brocade 7600 Application Appliance
• Brocade 7800 Extension Switch
• Brocade 8000 Application Appliance
• Brocade VA-40FC switch
• Brocade 12000 director (only on Fabric OS 5.0.x)
• Brocade 24000 director (single domain only)
viii Brocade SMI Agent Installation Guide

53-1001777-01
• 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).
• Added the section, “Enable multi-homed support,” to the end of Chapter 2.
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
italic text Provides emphasis
Identifies variables
Identifies class properties
Identifies paths and Internet addresses
Identifies document titles
Brocade SMI Agent Installation Guide ix

53-1001777-01
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 all lowercase.
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.
NOTE
A note provides a tip, guidance or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
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 MyBrocade.
See “Brocade resources” on page xi for instructions on accessing MyBrocade.
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
Sun Microsystems, Inc. Sun, Solaris
Red Hat, Inc. Red Hat, Red Hat Network
VMware, Inc. VMware
x Brocade SMI Agent Installation Guide

53-1001777-01
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 User’s 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 MyBrocade 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
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web
site:
http://www.fibrechannel.org
Brocade SMI Agent Installation Guide xi

53-1001777-01
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
• 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.
xii Brocade SMI Agent Installation Guide

53-1001777-01
• Brocade Multiprotocol Router Model AP7420—On the bottom of the chassis and on the
back of the chassis.
3. 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: 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 to collect the required support information to be
sent. Refer to the Brocade SMI Agent User’s Guide for information about this tool.
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.
Brocade SMI Agent Installation Guide xiii

53-1001777-01
xiv Brocade SMI Agent Installation Guide
53-1001777-01
Chapter
Installation Requirements 1
In this chapter
• Platform requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
• Switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
• System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
• SMI-A (Fabric OS) and SMI (EOS) coexistence requirements . . . . . . . . . . . . . 3
Platform requirements
Your software environment must meet the following requirements before you install the Brocade
SMI Agent (SMI-A):
• Minimum of 512 MB RAM
• One of the following operating systems:
- Microsoft Windows Server 2003 Std SP2 (x86 32-bit)
- Microsoft Windows Server 2008 Std (x86 32-bit)
- Microsoft Windows Vista Business Edition SP1 (x86 32-bit)
- Solaris 9 (SPARC-platform)
- Solaris 10 (SPARC-platform)
- Linux Red Hat AS 3.0 (x86 32-bit)
- Linux Red Hat AS 4.0 (x86 32-bit)
- Linux SUSE Enterprise Desktop 10 (x86 32-bit)
- AIX 5.3 (PowerPC)
• For Linux, Solaris, and AIX, a graphical interface is required for standard installation, but not for
silent installation.
NOTE
In Windows Vista, if you do not have Administrator privileges, you cannot stop and start the server.
To start and stop the server, you must have Administrator privileges and the ConfigurationTool.bat
file must be invoked using the “Run As Administrator” option.
Sun Microsystems JRE version 1.5.0_11 is bundled with the SMI-A and is automatically installed
when the SMI-A is installed.
VMWare ESX Server 3.5 is supported on the following operating systems:
• Microsoft Windows Server 2003 Std SP2 (x86 32-bit)
• Microsoft Windows Server 2008 Std (x86 32-bit)
• Linux Red Hat AS 4.0 (x86 32-bit)
Other virtualization software is not supported.
Brocade SMI Agent Installation Guide 1

53-1001777-01
1 Switch requirements
Switch requirements
When possible, upgrade your switches to Fabric OS v6.4.x.
The SMI-A supports proxy switches running Fabric OS v6.0.x and higher; however, it is
recommended that the proxy switch is running Fabric OS v6.4.x.
It is not necessary to choose the principal switch as the proxy.
Only fabrics in which all user accounts are equivalent on all switches have been tested. For RBAC,
only fabrics containing all Fabric OS 5.2.0, 5.3.0, or 6.0.x and higher switches and in which all user
accounts are equivalent on all switches have been tested.
System requirements
NOTE
The recommendations in this section are applicable for both the physical and the VMware host.
Table 1 lists the memory and CPU recommendations.
TABLE 1 System requirements

Requirements SAN with 1-5,000 switch ports SAN with 5,000-10,000 switch ports
Memory usage by the Agent less than 512 MB less than 1 GB

Memory 2 GB 3 GB
CPU 3 GHz 3 GHz
The memory required for running the SMI-A depends on the following:
• number of switches
• number of ports
• number of devices in a single fabric
• number of fabrics being managed
You should increase the memory as these numbers increase. You should also check the memory
usage of all applications and services running on the host and adjust the memory accordingly. If
the agent is used to manage multiple fabrics, use the total number of switch ports in all fabrics to
determine the memory usage.
Fabric OS v5.2.0 and later support a zoning database size of 1 MB. To support a 1 MB zoning
database, the entire fabric must be upgraded to v5.2.0 or later. If any pre-v5.2.0 switches are part
of the fabric, the maximum zone database size is 256 KB. If the zoning database size exceeds 256
KB, switches not upgraded to Fabric OS v5.2.0 or later are segmented out of the fabric.
You should also increase the memory heap size for the JVM based on the number of switches and
number of switch ports and devices. After you install the SMI Agent, you can increase the heap size
using the following procedure.
NOTE
This document uses <SMIAgent> to refer to the installation folder, although your installation folder
might be different (if you change it from the default).
2 Brocade SMI Agent Installation Guide

53-1001777-01
SMI-A (Fabric OS) and SMI (EOS) coexistence requirements 1
To increase the heap size

1. Open the start_server file for editing. This file is in the following location:
Linux, Solaris, and AIX: <SMIAgent>/agent/server/jserver/bin/start_server
Windows: <SMIAgent>\agent\server\jserver\bin\start_server.bat
Windows only: If you installed the SMI-A as a service, open the jserverd.ini file for editing,
instead of the start_server file. The jserverd.ini file is in the following location:
C:\Windows\system32\jserverd.ini
2. Modify the JVM flag in the file.
The default value of the JVM flag is: -Xmx512m. For example, to increase the memory from 512
MB to 1024 MB, change this value to: -Xmx1024m. For most fabrics, 512 MB is usually
sufficient.
3. Restart the SMI Agent, if it is already started.
SMI-A (Fabric OS) and SMI (EOS) coexistence requirements

The Brocade SMI (Fabric OS) agent can co-exist in the same host with Brocade SMI (EOS) agent
version 2.5 and higher. When the agents co-exist in the same host, they must be configured to run
on different ports.
The system requirements are as follows:
• 4 GB RAM or higher
• 3 GHz CPU
• 1 GB JVM memory size for each agent
By default, during installation both the SMI (EOS) and SMI-A (Fabric OS) are configured to use ports
5988 and 5989. When the agents co-exist in the same host, they must be configured to run on
different ports. SMI (EOS) versions earlier than 2.6 do not provide an option to change ports during
installation. For SMI (EOS) versions earlier than 2.6, you must install the SMI (EOS) before you
install the SMI-A (Fabric OS).
If the SMI-A (Fabric OS) is installed in a host in which and SMI (EOS) agent is already installed, the
SMI-A (Fabric OS) registers to the SLP service that is installed by the SMI (EOS) agent. If a client
queries the SLP service running in the host, the service lists both the SMI-A (Fabric OS) and SMI
(EOS) agents.
Installing SMI-A (Fabric OS) and SMI (EOS) on the same host
The following procedures provide the basic installation order for installing the two SMI agents.
Complete instructions for installing the SMI-A (Fabric OS) are provided in Chapter 2, “Installing the
SMI Agent”. See the Brocade SMI Agent for EOS Products Installation Guide for instructions for
installing the SMI (EOS).
Perform one of the following procedures depending on which SMI is to use the default ports and
which version of SMI (EOS) you are running.

53-1001777-01
1 SMI-A (Fabric OS) and SMI (EOS) coexistence requirements
SMI (EOS) uses the default ports

1. Install the SMI (EOS) agent.
2. Install the SMI-A (Fabric OS) with non-default ports (for example, http: 6000 and https: 6001).
In this scenario, the SMI agent (EOS) would run on the default ports (http: 5988 and https:
5989).
SMI-A (Fabric OS) uses the default ports, and SMI (EOS) version is earlier than 2.6
1. Install the SMI (EOS) agent.
2. Change the http and https port numbers using the Server Configuration tool and restart the
SMI (EOS) agent.
3. Install the SMI-A (Fabric OS) using the default ports (5988 and 5989).
SMI-A (Fabric OS) uses the default ports, and SMI (EOS) version is 2.6 or later
1. Install the SMI-A (Fabric OS) agent using the default ports (5988 and 5989).
2. Install the SMI (EOS) agent with non-default ports (for example, http: 6000 and https: 6001).

53-1001777-01
Chapter
Installing the SMI Agent 2
In this chapter
• Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
• Before installing the SMI Agent on Linux, Solaris, and AIX. . . . . . . . . . . . . . . 5
• Install the Brocade SMI Agent using the wizard . . . . . . . . . . . . . . . . . . . . . . . 6
• Install the Brocade SMI Agent in silent mode . . . . . . . . . . . . . . . . . . . . . . . . 26
• Post-installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
• Enable multi-homed support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
• Uninstall the Brocade SMI Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Introduction
This chapter describes the steps for installing and uninstalling the Brocade SMI Agent (SMI-A) on
Windows, Linux, Solaris, and AIX. You can install the SMI-A either using a wizard or in silent mode,
with no user intervention.
When SMI-A installation is complete, the following shortcuts are automatically added to the Start
menu:
• Brocade SMI Agent Configuration Tool
• Start CIMOM
• Stop CIMOM
• Start SMI Agent Service (Available only if the SMI-A is installed as a service)
• Stop SMI Agent Service (Available only if the SMI-A is installed as a service)
• Uninstall Brocade SMI Agent
NOTE
If you are installing both the SMI-A (Fabric OS) and the SMI (EOS) on the same host, see “SMI-A
(Fabric OS) and SMI (EOS) coexistence requirements” on page 3 for additional requirements and
instructions.
Before installing the SMI Agent on Linux, Solaris, and AIX

The installation wizard allows you to install the SMI-A as a service on Windows, Linux, Solaris, and
AIX. On Linux, Solaris, and AIX, if the SMI-A is already installed and running as a service, then use
the following procedure before starting a new installation for running SMI-A as a service.

53-1001777-01
2 Install the Brocade SMI Agent using the wizard
1. Go to the previously installed <SMIAgent>/agent/server/jserver/bin directory.

2. Edit the stop_agent_service script in that directory according to the instructions given in the
script.
3. Stop the service using the stop_agent_service script.
4. Start the new SMI-A installation, as described in “Install the Brocade SMI Agent using the
wizard,” next, or “Install the Brocade SMI Agent in silent mode” on page 26.
Install the Brocade SMI Agent using the wizard

An installation wizard is provided for installing the SMI-A. The installation wizard does the following:
• Installs Sun Microsystems JRE 1.5.0_11, which is bundled with the installer. The JRE is
installed in the directory local to <SMIAgent>.
• Allows you to configure Fabric Manager database server information (SMIAgentConfig.xml file).
• Provides option for enabling security for the SMI-A.
- During Windows installation, if security is enabled with Windows Domain Authentication,
you must always provide the Windows Domain login credentials to connect to the SMI
Agent; otherwise, all communication to the SMI-A will fail.
- If security is enabled without Windows Domain Authentication, you must always provide
the local account credentials to connect to the SMI Agent; otherwise, all communication to
the SMI-A will fail.
- During Linux, Solaris, and AIX installations, if security is enabled during installation, then
you must always start the SMI-A as root; otherwise, all communication to the SMI-A will fail.
• Provides options for enabling mutual authentication for client and indications.
• Provides options for importing client certificates into the Server truststore and for exporting
Server certificates to a specified directory.
• Allows you to configure http and https port information.
• Allows you to configure eventing and ARR TCP ports (SMIAgentConfig.xml file).
• Allows you to configure secure eventing and ARR TCP ports (SMIAgentConfig.xml file).
• Provides options for enabling console and file logging (jserver.properties file).
• Allows you to configure proxy connections (provider.xml file).
• Provides option for starting the SMI-A as a Windows service or Linux/Solaris/AIX daemon.
• Installs the Brocade SMI Agent Configuration Tool, which allows you to change the SMI-A
configuration settings after the installation. Refer to the Brocade SMI Agent User’s Guide for
information about the Configuration Tool.
Installing the SMI-A using the wizard

1. Locate the installation file for the computer you are installing it on, as follows:
• Windows: CD_Image\Windows\install.exe
• Linux: CD_Image\Linux\install.bin
• Solaris: CD_Image\Solaris\install.bin
• AIX: CD_Image\AIX\install.bin

53-1001777-01
Install the Brocade SMI Agent using the wizard 2
2. Run the installation file.
NOTE
To enable security on Linux, Solaris, and AIX, you must start the installation process by logging
in as root. To enable security on Windows, you must start the installation process by logging in
as a user with administrator privileges.
The installation wizard launches, as shown in Figure 1.
FIGURE 1 Installation wizard
If the installation wizard does not launch, you might be installing in silent mode. Silent mode is
triggered when you run the installation file using the -f option. Check for the presence of the
SilentInstallation.properties file and, if you do not want to install in silent mode, either move
that file to another folder, or rename the file. For information about silent mode installation,
see “Install the Brocade SMI Agent in silent mode” on page 26.
3. Accept the license agreement and click Next.
The System Configuration window appears.

53-1001777-01
FIGURE 2 System configuration
4. Ensure that you have the required disk space for the installation, and click Next.
The Introduction window appears.
FIGURE 3 Introduction
5. Read the introduction and click Next.

The Choose Installation Folder window appears. Figure 4 on page 9 shows the default
installation folder for Windows, C:\SMIAgent.

53-1001777-01
FIGURE 4 Choose installation folder
6. Click Next to accept the default installation location, or enter a different location and click
Next.
If you plan to migrate configuration files from a previous version, each version should be
installed in a different folder.
NOTE
Do not specify spaces in the path or folder name.
7. Windows, Solaris, Linux only: If the installer detects an existing SMI Agent installation, you are
prompted whether you want to import the existing configuration. (The installer cannot detect
an existing installation on the AIX platform.) This prompt does not appear if the previous SMI
Agent installation was terminated.
If you do not want to import the existing configuration files, click Cancel, and go to step 9;
otherwise, click OK to copy the configuration files from the existing installation directory to the
new installation directory.
When you click OK, the Importing Configuration window appears. This window displays the
paths of the configuration files. Select the configuration that you want to import and click Next.
NOTE
SMI-A 120.11.0 supports importing configurations from 120.10.0 and from 120.9.0.

53-1001777-01
FIGURE 5 Importing configuration
The following files from the selected installation are copied:

• provider.xml
• SMIAgentConfig.xml
• cimom.properties
• debug.properties
Windows only: The type of domain authentication is not imported from the previous
installation.
NOTE
If the import fails, you are notified of the failure at the end of this installation procedure.
The HTTP Port Configuration window appears. This window displays the default port number
for non-secured CIMOM communication.

53-1001777-01
FIGURE 6 HTTP port configuration
8. Use the default port number, or enter a new port number.

The range of valid port numbers is from 1 to 65535; however, it is recommended that you use
a value between 1024 and 65535.
9. Click Next to accept the default port number, or enter a new port number and click Next.
If the port is in use, you get an error message and are prompted to enter a new port.
If the port is not in use, the HTTPS Port Configuration window appears. This window displays
the port number that will be used for secured CIMOM communication.
FIGURE 7 HTTPS port configuration

53-1001777-01
10. Use the default HTTPS port number, or enter a new port number.
The range of valid port numbers is from 1 to 65535; however, it is recommended that you use
a value between 1024 and 65535.
11. Click Install.
After the installation finishes, the Fabric Manager Server Configuration window appears.
NOTE
Full installation is not complete at this time. Do not cancel or abort the installation wizard.
For all platforms except AIX: If you imported an existing configuration, this window does not
display. Skip to step 13.
FIGURE 8 Fabric Manager server configuration
This window allows you to specify the connection information for an existing Brocade Fabric
Manager server. Not all users have a Fabric Manager server installed and running in their
environment. The information that you enter here allows the SMI-A to report on historical port
statistics by retrieving the data from the Fabric Manager database server. If your management
application does not make use of historical port statistics, you do not need to enter any
connection information on this screen.
Driver This field is already populated with the default driver that is bundled in the
agent: com.sybase.jdbc2.jdbc.SybDriver. Do not change this driver
information.
URL The database URL should be in the form:
jdbc:subprotocol:subname:host:port/dbname
For example, if the Fabric Manager database server is installed on the same
host as the SMI-A, the URL is: jdbc:sybase:Tds:localhost:2638/fabman
Otherwise, replace localhost with the Fabric Manager database server host IP
address.

53-1001777-01
User Name The database user on whose behalf the connection is being made. The
default DSN user name is: dba
Password The user’s password. The default DSN password is: sql
This information is stored in the configuration file SMIAgentConfig.xml located at
<SMIAgent>\agent\server\jserver\bin. You can use the SMI Agent Configuration tool to
change these settings after installation.
12. Enter database schema information, and click Next.
The Enabling Mutual Authentication for Client window appears.
FIGURE 9 Enabling mutual authentication for client
13. Choose whether to enable mutual authentication (trust by certificate) between client
management applications and the Brocade SMI Agent by selecting one of the following
options, and then click Next:
• Yes: Enables mutual authentication.
Only allow management applications that have the Brocade-provided security certificate to
connect to the SMI Agent. Requires that the Brocade-provided security certificate
(server.cer) is imported into the truststore of the management application before a
connection is established. The management application must have a mechanism that
provides the client certificate (client.cer) during the initial handshake.
• No: (Default) No mutual authentication by certificate.
Trust by certificate is not used; however, basic encryption and local or domain
authentication can still be established by enabling security in step 19.
The Enabling Mutual Authentication for Indications window appears.

53-1001777-01
FIGURE 10 Enabling mutual authentication for indications
14. Choose whether to enable mutual authentication (trust by certificate) between client
management application event system and the Brocade SMI Agent by selecting one of the
following options, and then click Next:
• Yes: Enables mutual authentication.
Allow only management applications that have the Brocade-provided security certificate to
register their event system with the SMI Agent. Requires that the Brocade-provided
security certificate (serverind.cer) is imported into the truststore of the management
application before a connection is established. The management application must have a
mechanism that provides the client certificate (clientind.cer) during the initial
handshake.
• No: (Default) No mutual authentication by certificate.
The SMI-A uses SSL to send CIM-XML indications to a WBEM client listener, but does not
attempt to verify the identity of the WBEM client listener.
NOTE
The SMI Agent uses this connection to send asynchronous event notifications, similar to SNMP,
to the management application event system.
The Importing client certificate for Mutual Authentication for Clients window appears.

53-1001777-01
FIGURE 11 Importing client certificate for mutual authentication for clients
This window allows you to import a security certificate into the SMI Agent server truststore.
If mutual authentication for clients is enabled, this certificate will be used. If mutual
authentication for clients is not enabled, you can provide a security certificate now, which will
be used if you enable mutual authentication for clients later.
NOTE
You can import only certificates generated using Java Keytool or OpenSSL.
If mutual authentication for clients is enabled and if you do not provide a security certificate,
then the Brocade-provided client certificate (client.cer) will be used to authenticate clients.
15. Enter the path of the client certificate and the alias name of the certificate, and click Next.
The Importing client certificate for Mutual Authentication for Indication window appears.

53-1001777-01
FIGURE 12 Importing client certificate for mutual authentication for indications
This window allows you to import a security certificate into the SMI Agent server truststore.
If mutual authentication for indications is enabled, this certificate will be used. If mutual
authentication for indications is not enabled, you can provide a security certificate now, which
will be used if you enable mutual authentication for indications later.
NOTE
You can import only certificates generated using Java Keytool or OpenSSL.
If mutual authentication for indications is enabled and if you do not provide a security
certificate, then the Brocade-provided security certificate (clientind.cer) will be used for
authentication.
16. Enter the path of the client certificate and the alias name of the certificate, and click Next.
The Exporting Server certificate for Mutual Authentication for Clients window appears.

53-1001777-01
FIGURE 13 Exporting server certificate for mutual authentication for clients
This window allows you specify a file name and directory in which to export the SMI Agent
server certificate (server.cer) used for mutual authentication for clients.
If mutual authentication for clients is enabled and if you do not export the SMI Agent server
certificate, then the client keystore, truststore, and server certificates will be used for
authentication.
If mutual authentication for clients is not enabled, you can provide the server certificate
information now, which will be used if you enable mutual authentication for clients later.
17. Enter the directory and the file name, and click Next.
The Exporting Server certificate for Mutual Authentication for Indication window appears.

53-1001777-01
FIGURE 14 Exporting server certificate for mutual authentication for indications
This window allows you specify a file name and directory in which to export the SMI Agent
server certificate (serverind.cer) used for mutual authentication for indications.
If mutual authentication for indications is enabled and if you do not export the SMI Agent
server certificate, then the client keystore, truststore, and server certificates will be used for
authentication.
If mutual authentication for indications is not enabled, you can provide the server certificate
information now, which will be used if you enable mutual authentication for indications later.
18. Enter the directory and the file name, and click Next.
The Enabling Security window appears.

53-1001777-01
FIGURE 15 Enabling security
19. Enable or disable authentication for the SMI Agent by selecting one of the following options,
and then click Next:
• Yes: Enables authentication.
SMI Agent validates the user name and password. Note that for Linux or Solaris systems,
the SMI Agent can only validate the user’s credentials against the local database.
NOTE
To enable security on an AIX platform, add the following lines to the /etc/pam.conf file, if
not already added:
wsi-wbem-server auth required /usr/lib/security/pam_aix
wsi-wbem-server session required /usr/lib/security/pam_aix
wsi-wbem-server password required /usr/lib/security/pam_aix
wsi-wbem-server account required /usr/lib/security/pam_aix
• No: (Default) Disables authentication.

SMI Agent accepts any user name and password.
One of following windows appears depending on your operating systems and the security
setting you have selected:
• If you selected No, the Eventing and ARR TCP Port Configuration window appears
(Figure 18 on page 21); skip to step 22.
• If you selected Yes for Linux or Solaris systems, the Eventing and ARR TCP Port
Configuration window appears (Figure 18); skip to step 22.
• If you selected Yes for Windows systems, the Enter Type of Domain Authentication window
appears (Figure 16). Continue with the instructions in step 20 to set up user
authentication for Windows.

53-1001777-01
FIGURE 16 Enter type of domain authentication
20. (Windows with security enabled only) Select whether to validate users against the domain user
database, and then click Next:
• Yes: Enables domain authentication.
SMI Agent validates the user name and password against the domain user database.
• No: (Default) Disables domain authentication.
SMI Agent validates the user against the Windows local user accounts on the SMI-A
system.
One of following windows appears depending on your operating system and the setting you
have selected:
• If you selected No, the Eventing and ARR TCP Port Configuration window appears
(Figure 18); skip to step 22.
• If you selected Yes, the Enter Valid Domain Name window appears (Figure 17). Continue
with step 21.
Domain authentication is not available on Linux, AIX, and Solaris platforms.

53-1001777-01
FIGURE 17 Enter valid domain name
21. (Windows with domain security enabled only) Enter name of the domain that the SMI Agent will
use to authenticate user credentials, and click Next.
The Eventing and ARR TCP Port Configuration window appears.
FIGURE 18 Eventing and ARR TCP port configuration
The ARR port is the port through which the switches in the fabric send data (large payload
responses) back to the SMI-A.

53-1001777-01
The eventing port is the port through which the switch connects to the SMI-A to deliver events.
If a firewall exists between the SMI-A and the fabric, these ports must be open in the firewall.
The ARR and eventing port ranges are from 0 to 65535.
When you choose values for the ARR and eventing ports, make sure they are not one of the
assigned TCP ports. The Installation wizard does not check for this. You can see a list of
assigned TCP ports at:
http://www.iana.org/assignments/port-numbers
ARR and eventing ports are optional. If you do not configure them, or if you configure them with
a value of 0, the SMI Agent dynamically allocates a port during server startup.
22. To allow the SMI Agent to allocate ports dynamically when started, enter 0 for each port
number or leave this form blank, and click Next; to assign a specific port or range of ports,
enter port numbers or range, and click Next.
NOTE
Ports cannot be the same or in use. The SMI Agent does not verify whether the ports are
available.
The Enabling Console And/Or File Logging window appears.
FIGURE 19 Enabling console and file logging
23. Set up logging as follows, and then click Next.

a. To display detailed messages in the console, select Yes.
NOTE
To view console messages the SMI Agent must be running from a console session, not as a
service. Selecting yes to enable console messages when SMI Agent is running as a service
does not affect the system.
b. To disable file logging, select No.

53-1001777-01
Figure 20 on page 23 shows the Windows default log file name and location.
FIGURE 20 Configure log file
c. Enter the complete path to the log file.

d. Enter the number of log files and the maximum size of the log files.
The minimum log file size is 1 KB. The file count is a value between 1 and 999. The default
is 20 log files of 10240 kilobytes (10 MB) each.
When the specified size is exceeded on the first log file, logs will be written to the next log
file. When approximately the specified number of KB have been written to one log file,
another log file is opened.
NOTE
Sometimes log file will exceed the size specified because of a limitation in Java logging.
After the server is stopped, the size of the log file will be reduced to the size specified.
e. Click Next.
The Proxy Connections Configuration window appears.

53-1001777-01
FIGURE 21 Proxy connections configuration
24. Configure the fabrics that you want the SMI Agent to proxy. For each fabric, click Add and fill
out the values in the Proxy Configuration window.
FIGURE 22 Proxy configuration
Proxy switch IP IP address of the proxy switch in IPv6 or IPv4 format (for example:
100.200.100.200)
User name Username to be used to log in to the switch (for example: admin)
Password Password to be used to log into the switch (for example: password)
Protocol Protocol: RPC, Secure RPC, or Any. RPC is used for a non-secure connection
and Secure RPC is used for a secure connection. Any means that first a
secure channel is tried and if it fails, then a non-secure channel is tried.
No. of RPC Handles Number of RPC connections to be used to connect to the switch. The
possible range of values is 1 to 20. The default value is 1.
NOTE
Fabric OS limits the number of RPC handles allowed per switch; therefore increasing the RPC
handles decreases the number of connections per switch.

53-1001777-01
25. After all the fabrics are configured in the Proxy Connections Configuration window, click Next.
The Important Information window appears.
FIGURE 23 Important information
26. Click Next.

The Configuring and Starting as a Service window or Start Agent as a Daemon window
appears.
FIGURE 24 Configuring and starting as a service
27. Select Yes to start the SMI Agent as a service, and click Next.

53-1001777-01
2 Install the Brocade SMI Agent in silent mode
NOTE
If you choose not to run the SMI Agent as a service, the agent does not stop or restart
automatically. You must manually start and stop the SMI Agent using the start_server script.
Only one agent at a time can be installed as a service on a host.
The Installation Completed window appears. This window displays a message if any errors
occurred during installation; check the log file for details.
FIGURE 25 Installation completed

28. Click Done.
Install the Brocade SMI Agent in silent mode

You can install the SMI-A in silent mode, with no user intervention. In silent mode you are not
prompted to enter input; instead, the installer reads input from a properties file. You are not
notified of invalid inputs; however, error messages are written to a log file (the location of which is
specified in the properties file).
For Windows, silent mode installation displays a splash screen while the installer is loading. This is
a limitation of the InstallAnywhere installer.
ATTENTION
In silent mode, the terms of the end user license agreement cannot be displayed for acceptance.
Silent installation means that, by default, you accept the same license agreement displayed during
normal installation.

53-1001777-01
Install the Brocade SMI Agent in silent mode 2
Creating a properties file for silent installation

Prior to installation in silent mode, you must create a properties file that includes all of the
properties required for agent startup. The installer will use this file to get the installation parameter
values.
Brocade provides a sample properties file that you can modify:
CD_image\SilentInstallation.properties
This file contains the installation parameters listed in Table 2 and also contains instructions for
modifying these parameters. You are required to specify values for the installation directory and the
installer log file. The remaining parameters are either optional or have default values.
During silent installation, you cannot add fabric proxy information to the properties file.
Configuration of proxies must be explicitly done via the provider.xml file or through the LoginAsUser
extrinsic method. Refer to the Brocade SMI Agent Developer’s Guide for more information.
TABLE 2 Installation parameters in the SilentInstallation.properties file

Parameters Description
INSTALLER_UI = silent The default is silent.

USER_INSTALL_DIR = Required. Specify the installation directory. Spaces are not
allowed in the pathname. Replace all backslashes (\) in the
pathname with double backslashes (\\). For example:
USER_INSTALL_DIR = C:\\SMIAgent
INSTALLER_LOG_FILE = Required. Specify the log file to which all installation messages
will be written. Spaces are not allowed in the pathname. Replace
all backslashes (\) in the pathname with double backslashes (\\).
For example:
INSTALLER_LOG_FILE = C:\\SMIAgent\\Install.log
CHOSEN_DIALOG_BUTTON = Windows, Solaris, Linux only. Import the existing configuration, if
one exists. To import the existing configuration, change this
parameter to:
CHOSEN_DIALOG_BUTTON = 0
To not import the existing configuration, leave this parameter as is
(not import is the default), or change this parameter to:
CHOSEN_DIALOG_BUTTON = 1
REG_COMPONENT_LOCATION The path from which to import configuration information. Spaces
are not allowed in the pathname. Replace all backslashes (\) in
the pathname with double backslashes (\\). For example:
\\root\\SmiA01\\agent\\server\\jserver\\bin
CIMOM_HTTP_PORT = 5988 CIMOM ports (HTTP and HTTPS). Defaults are 5988 and 5989,
CIMOM_HTTPS_PORT = 5989 respectively.
FM_SERVER_DRIVER_INFO = Fabric Manager Server configuration information. If Fabric
FM_SERVER_URL_INFO = Manager server configuration is not required, then you do not
FM_SERVER_USER_NAME = need to specify these parameters. There are no defaults.
FM_SERVER_PASSWORD = See page 12 for more information.
CLIENT_AUTH_DISABLED = 1 Mutual authentication for clients. Default is disabled
(CLIENT_AUTH_DISABLED = 1). To enable mutual
authentication for clients, change this parameter to:
CLIENT_AUTH_ENABLED = 1
See page 13 for more information.

53-1001777-01
2 Install the Brocade SMI Agent in silent mode
TABLE 2 Installation parameters in the SilentInstallation.properties file (Continued)

IND_AUTH_DISABLED = 1 Mutual authentication for indications. Default is disabled

(IND_AUTH_DISABLED = 1). To enable mutual authentication
for indications, change this parameter to:
IND_AUTH_ENABLED = 1
IMPORT_CLIENT_CERTIFICATE_MUTUAL Path of the client certificate to be imported for mutual
_AUTH_CLIENT_FILEPATH = authentication for client. Spaces are not allowed in the pathname.
Replace all backslashes (\) in the pathname with double
backslashes (\\). For example:
D:\\certfolder\\mycertClient.cert
IMPORT_CLIENT_CERTIFICATE_MUTUAL Alias name for the client certificate used for mutual
_AUTH_CLIENT_ALIAS = authentication for client.
IMPORT_CLIENT_CERTIFICATE_MUTUAL Path of the client certificate to be imported for mutual
_AUTH_INDICATION_FILEPATH = authentication for indications. Spaces are not allowed in the
pathname. Replace all backslashes (\) in the pathname with
double backslashes (\\). For example:
D:\\certfolder\\mycertInd.cert
IMPORT_CLIENT_CERTIFICATE_MUTUAL Alias name for the client certificate used for mutual
_AUTH_INDICATION_ALIAS = authentication for indications.
EXPORT_SERVER_CERTIFICATE_MUTUAL Location for exporting the SMI Agent server certificate used for
_AUTH_CLIENT_DIR = mutual authentication for client. Spaces are not allowed in the
D:\\certOutfolderClient\\
EXPORT_SERVER_CERTIFICATE_MUTUAL Output file name of the exported server certificate used for
_AUTH_CLIENT_FILENAME = mutual authentication for client.
EXPORT_SERVER_CERTIFICATE_MUTUAL Location for exporting the SMI Agent server certificate used for
_AUTH_INDICATION_DIR = mutual authentication for indications. Spaces are not allowed in
the pathname. Replace all backslashes (\) in the pathname with
D:\\certOutfolderIndication\\
EXPORT_SERVER_CERTIFICATE_MUTUAL Output file name of the exported server certificate used for
_AUTH_INDICATION_FILENAME = mutual authentication for indications.
SECURITY_DISABLED = 1 SMI-A security. Default is disabled (SECURITY_DISABLED =
1). To enable security, change this parameter to:
SECURITY_ENABLED = 1
WINDOWS_DOMAIN_AUTH_DISABLED = 1 Windows only. Windows domain authentication. This parameter is
used only if security is enabled. Default is disabled
(WINDOWS_DOMAIN_AUTH_DISABLED = 1). To enable
Windows domain authentication, change this parameter to:
WINDOWS_DOMAIN_AUTH_ENABLED = 1

53-1001777-01
Install the Brocade SMI Agent in silent mode 2
TABLE 2 Installation parameters in the SilentInstallation.properties file (Continued)

WINDOWS_DOMAIN_NAME = Windows only. Windows domain name. This parameter is required

if Windows domain authentication is enabled.
EVENTING_PORT = Eventing port. If not specified, or if the specified port is in use,
then the port is dynamically selected at startup.
ARR_PORT = ARR port. If not specified, or if the specified port is in use, then
the port is dynamically selected at startup.
SECURE_EVENTING_PORT = Secure eventing port. If not specified, or if the specified port is in
use, then the port is dynamically selected at startup.
SECURE_ARR_PORT = Secure ARR port. If not specified, or if the specified port is in use,
then the port is dynamically selected at startup.
CONSOLE_LOGGING_DISABLED = 1 Console logging. Default is disabled
(CONSOLE_LOGGING_DISABLED = 1). To enable console
logging, change this parameter to:
CONSOLE_LOGGING_ENABLED = 1
FILE_LOGGING_DISABLED = 1 File logging. Default is disabled (FILE_LOGGING_DISABLED =
1). To enable file logging, change this parameter to:
FILE_LOGGING_ENABLED = 1
LOG_FILE_NAME = This parameter is required only if file logging is enabled. Specify
the location of the log file. Spaces are not allowed in the
LOG_FILE_NAME = C:\\SMIAgent\\SMIAgent.log
LOG_FILE_COUNT = 20 These parameters are used only if file logging is enabled. Specify
LOG_FILE_SIZE = 10240 the number of log files and the size of the log files. Default is 20
log files of 10240 kilobytes (10 MB) each.
SERVICE_DISABLED = 1 Start the SMI-A as a service. Default is no (SERVICE_DISABLED
= 1). To start the SMI-A as a service, change this parameter to:
SERVICE_ENABLED = 1
Silent mode installation

Silent mode installation is triggered when you run the installation file using the -f option, where
filename is the absolute path of the properties file.
Installing the SMI-A in silent mode

1. Edit the SilentInstallation.properties file as described in “Creating a properties file for silent
installation” on page 27.
2. Save the properties file in the same folder as the installer executable:
On Windows: CD_Image\Windows
On Linux: CD_Image/Linux

53-1001777-01
2 Post-installation considerations
On Solaris: CD_Image/Solaris
On AIX: CD_Image/AIX
3. Run the installation file:
On Windows: CD_Image\Windows\install.exe -f "filename"
On Linux: CD_Image/Linux/sh install.bin -f "filename"
On Solaris: CD_Image/Solaris/sh install.bin -f "filename"
On AIX: CD_Image/AIX/sh install.bin -f "filename"
where filename is the absolute path of the properties file.
If the properties file name is the default name, SilentInstallation.properties, then you can run
the installation file without the -f option, as follows:
On Windows: CD_Image\Windows\install.exe
On Linux: CD_Image/Linux/install.bin
On Solaris: CD_Image/Solaris/install.bin
On AIX: CD_Image/AIX/install.bin
The SMI-A is installed to the location specified in the USER_INSTALL_DIR parameter of the
properties file.
The status of the installation, along with any error messages, is reported in the installation log file,
which is in the location specified in the INSTALLER_LOG_FILE parameter of the properties file. The
status of the installation is SUCCESS only if all of the installation operations succeeded; otherwise,
the overall installation status is FAILED. Refer to Chapter 3, “Silent Installation Status Messages,”
for details about the status messages.
Post-installation considerations
The Brocade SMI Agent supports SLP to allow applications to discover the existence, location, and
configuration of WBEM services in enterprise networks. If you want Service Location Protocol (SLP)
support, you must install and start the SLP daemon prior to starting the SMI-A. See the Brocade
SMI Agent User’s Guide for instructions on installing and starting the SLP daemon.
After you install the SMI-A, you can change many of the configuration settings using the Brocade
SMI Agent Configuration Tool. For example, you can:
• reconfigure the ports used by the SMI-A
• enable and disable logging and configure different levels of logging
• add and remove fabrics
See the Brocade SMI Agent User’s Guide for instructions on using this tool.
Enable multi-homed support

The Brocade SMI Agent supports multi-homed hosts; that is, hosts configured with multiple IPs.
This means that you can configure which IP address the SMI Agent should use for Event and ARR
registration on the switch.

53-1001777-01
Uninstall the Brocade SMI Agent 2
Configuring IP address for switch-to-SMIAgent communication in

multi-homed systems
1. Edit the SMIAgentConfig.xml file found at .../server/jserver/bin with the following entry:
<host address="xxx.xxx.xxx.xxx"/>
For example,
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE agent_config SYSTEM "SMIAgentConfig.dtd">
<agent_config>
<dbserver driver="" is_password_encrypted="" password="" url=""
username=""/>
<port_config arr="5400" eventing="123"/>
<secureport_config arr="876" eventing="1"/>
<host address="10.201.64.173"/>
</agent_config>
2. Restart the Brocade SMI Agent.
Configuring IP address for SMI Agent client-to-server communication in

multi-homed systems
1. Edit the jserver.properties file found at …server/jserver/bin with the following entry:
HostIPAddress=xxx.xxx.xxx.xxx
2. Restart the Brocade SMI Agent.
Uninstall the Brocade SMI Agent

The uninstaller automatically uninstalls the SMI-A in the same way you installed it: either using the
wizard or in silent mode.
The JRE that was installed when you installed the SMI-A is removed as part of the uninstallation.
Uninstalling the SMI-A

1. Click the “Uninstall Brocade SMI Agent” shortcut on the Start menu.
or
Type the following at the command line:
Windows: <SMIAgent>\UninstallerData\"Uninstall Brocade SMI Agent.exe"
Linux, Solaris, or AIX: ./<SMIAgent>/UninstallerData/Uninstall_Brocade_SMI_Agent

If you installed the SMI-A using the wizard, the Uninstall wizard launches and directs you through
the uninstallation process (see Figure 26 on page 32).
If you installed the SMI-A in silent mode, the SMI-A is automatically uninstalled in silent mode.

53-1001777-01
2 Uninstall the Brocade SMI Agent
FIGURE 26 Uninstalling the Brocade SMI Agent

53-1001777-01
Chapter
Silent Installation Status Messages 3
When you install the SMI-A in silent mode, status messages are written to the installation log file,
the name and location of which is specified in the properties file.
The format of each status message is:
SMIAgent;120.11.0;Operation=opname;Status=status;StatusCode=code;StatusMessage=msg
;
where opname is the name of the operation, status is either Passed or Failed, code is the numeric
status code, and msg is the status message.
Table 3 lists the possible operation names and, for each operation, the possible status, status
codes, and status messages.
TABLE 3 Silent installation error codes

Operation name Status Status code Status message
Choose Installer Folder Passed 0 Successful

Name
Failed -1 Your system drive does not have disk space required for the
installation
Failed -2 Invalid Folder
Failed -3 Installation Folder Name contains a space
CIMOM Ports Passed 0 CIMOM Ports Configured
Configuration
Failed -5 Configured HTTP port in use
Failed -5 Configured HTTPS port in use
Failed -6 Invalid Port Range
Failed -7 Non Numeric or Negative CIMOM Ports
Failed -16 HTTP and HTTPS cannot be the same
FM Server Configuration Passed 0 Successful
Mutual Authentication Passed 0 Disabled Mutual Authentication for SMI Agent
for Client
Passed 0 Enabled Mutual Authentication for SMI Agent
Failed -5 Configured HTTP port in use
Failed -22 Invalid Parameter for Mutual Authentication for Client
Mutual Authentication Passed 0 Disabled Mutual Authentication for Indication
for Indication
Passed 0 Enabled Mutual Authentication for Indication
Failed -5 Configured HTTP port is in use
Failed -22 Invalid Parameter for Mutual Authentication for Indication

53-1001777-01
3 Silent Installation Status Messages
TABLE 3 Silent installation error codes (Continued)

Import client certificate Passed 0 Successful

for mutual
Failed -31 Invalid file path.
authentication for client
Failed -32 Alias name must not contain special characters
Failed -33 Empty file location
Failed -34 Empty alias name
Failed -35 Failed to import
Failed -40 Duplicate alias name
Import client certificate Passed 0 Successful
for mutual
authentication for
indications Failed -32 Alias name must not contain special characters
Failed -34 Empty alias name
Failed -35 Failed to import
Failed -40 Duplicate alias name
Export server certificate Passed 0 Successful
for mutual
authentication for client
Failed -36 Output file must not contain special characters
Failed -38 Empty output file name
Failed -39 Failed to export
Failed -41 Duplicate output file name
Export server certificate Passed 0 Successful
for mutual
authentication for
indications Failed -33 Empty file location
Failed -36 Output file must not contain special characters
Failed -38 Empty output file name
Failed -39 Failed to export
Failed -41 Duplicate output file name

53-1001777-01
Silent Installation Status Messages 3

Eventing and ARR Passed 0 Eventing and ARR ports configured

Configuration
Failed -6 Invalid Port Range
Failed -10 Ports used for Eventing and ARR cannot be the same
Failed -11 Eventing Port value should not be negative
Failed -12 ARR Port value should not be negative
Failed -17 Invalid or Non-numeric port
Failed -18 Port used for Eventing is already configured as HTTP or HTTPS
port
Failed -19 Port used for ARR is already configured as HTTP or HTTPS port;
Secure Eventing and Passed 0 Secure Eventing and ARR ports configured
ARR Configuration
Failed -23 Port used for Secure ARR is already configured as HTTP or
HTTPS port, or is negative
Failed -24 Ports used for Secure Eventing and Secure ARR cannot be the
same
Failed -25 Ports used for Secure Eventing and Eventing cannot be the
same
Failed -26 Ports used for Secure Eventing and ARR cannot be the same
Failed -27 Ports used for Secure ARR and Eventing cannot be the same
Failed -28 Ports used for Secure ARR and ARR cannot be the same
Failed -29 Invalid port number provided for Secure ARR or Eventing port.
The valid port range is 0–65535.
Failed -30 Port used for Secure Eventing is already configured as HTTP or
HTTPS port, or is negative.
Security Passed 0 Disabled Security for SMI Agent.
Passed 0 Enabled Security for SMI Agent.
Passed 0 Enabled Security for SMI Agent without Windows domain
authentication
Failed -5 Configured HTTP port is in use
Failed -8 You should be a root user to enable security
Failed -9 Windows domain name should not be empty for enabling
security on Windows
Failed -20 Windows domain authentication failed
Failed -21 Windows domain authentication failed. Failed to stop the
server.
Failed -22 Invalid Parameter for Security
Console Logging Passed 0 Enabled Console Logging
Passed 0 Disabled Console Logging
Failed -22 Invalid Parameter for Console Logging

53-1001777-01
3 Silent Installation Status Messages

File Logging Passed 0 Disabled File Logging

Passed 0 Enabled File Logging
Failed -13 Invalid Log File Size
Failed -14 Invalid file size count
Failed -15 Empty File location
Failed -22 Invalid Parameter for File Logging
SMI Agent as Service Passed 0 Disabled SMI Agent as Service
Passed 0 Enabled SMI Agent as Service
Passed 0 Installer has detected that already one SMI Agent is installed
as a service. This operation will remove the old one and install
the new one
Failed -8 You must be a root user to install SMI Agent as a service
Failed -22 Invalid parameter for SMI Agent as Service
Installation Passed 0 SMI Agent was successfully installed on your machine.
Failed -100 SMI Agent overall installation failed.

53-1001777-01
Chapter
Frequently Asked Questions 4
This chapter contains questions most frequently sent to the SMI Agent Developer Support email
address.
• Besides Windows Domain authentication, does the SMI Agent support local user
authentication?
• What are the Eventing and ARR TCP Ports? Do they relate to indications?
• What encryption method is used to encrypt the password field in provider.xml?
• How do I report a problem and what information should I provide?
• Does the Brocade SMI Agent need to point to every switch in a fabric or just one switch in each
fabric to collect the data?
• Can the SMI Agent proxy for two fabrics that are in different subnets?
• Should I designate multiple proxies into a fabric? What are the best practices concerning this?
• In using Windows domain authentication, do I need to include the domain name along with the
username for authentication?
• What are some situations that might require restarting the SMI Agent?
• How do I start and stop the SMI Agent?
• How do I tell what version of SMI-A I am running?
See the “Frequently Asked Questions” chapter in the Brocade SMI Agent User’s Guide for
additional questions and answers.
Besides Windows Domain authentication, does the SMI Agent support local user authentication?
SMIAgent 110.4.0 and higher support authenticating the user against the system on which it is
installed. By default when you configure security, the user’s credentials (username and password)
are validated against the ones present on the local system. To ensure this happens, follow these
steps:
1. During SMI-A installation, enable security and Select “No” for Windows domain authentication.
2. Create a local user on the Windows system where the agent is installed.
What are the Eventing and ARR TCP Ports? Do they relate to indications?
These ports are used by the agent to receive events and ARP responses from the fabric. The client
is not required to fill in these ports; the operating system selects the ports dynamically. One
probable use case for specifying these ports is if there is a firewall between the fabric and the host.
In this case, you can specify a fixed port to be opened by the administrator for eventing or ARR.
What encryption method is used to encrypt the password field in provider.xml?

The SMI Agent comes with a utility to encrypt the password. This utility is in the following directory:
Linux, Solaris, and AIX: <SMIAgent>/agent/bin/PasswordEncryptor
Windows: <SMIAgent>\agent\bin\PasswordEncryptor.bat
Use this utility to encrypt the password.

53-1001777-01
4 Frequently Asked Questions
How do I report a problem and what information should I provide?

Fill in the “Submit Problem Report” form at the partner web site.
Does the Brocade SMI Agent need to point to every switch in a fabric or just one switch in each
fabric to collect the data?
Just one switch per fabric. If the switches in the fabric do not all have the same Fabric OS version,
then you should designate the switch with the highest supported Fabric OS version as the proxy. It
is not necessary to choose the principal switch as the proxy.
Can the SMI Agent proxy for two fabrics that are in different subnets?
Yes.
Should I designate multiple proxies into a fabric? What are the best practices concerning this?
You can have only one connection at a time into the fabric. The only advantage in designating
multiple proxies is that if the first proxy fails to connect, the SMI-A tries the next proxy until it finds
one that works.
In using Windows domain authentication, do I need to include the domain name along with the
username for authentication?
No. You should provide only the username, as shown:
UserPrincipal up = new UserPrincipal("username");
PasswordCredential pc = new PasswordCredential("password");
What are some situations that might require restarting the SMI Agent?
Restarting of the SMIAgent is required when:
• configuration parameters, such as the debug level or log file name, are changed.
• host IP, HTTP, or HTTPS port is changed.
• firmware download configuration entry in SMIAgentConfig.xml is changed.
How do I start and stop the SMI Agent?
See the Brocade SMI Agent User’s Guide for instructions on starting and stopping the SMI Agent.
How do I tell what version of SMI-A I am running?

The title bar in the Brocade SMI Agent Configuration Tool displays the version of the SMI-A, for
versions 120.7.0 and later. See the Brocade SMI Agent User’s Guide for information on the
Configuration Tool. You can also check the file version.txt in the agent/server/jserver/bin directory.

53-1001777-01
Index
D P
Distributed Management Task Force (DMTF), xi platform support, 1
E R
enabling requirements for installation, 1
multi-homed support, 30 return codes for silent installation, 33
error codes for silent installation, 33
S
F
silent installation
Fibre Channel Association, xi error codes, 33
frequently asked questions (FAQs), 37 on Windows, 26
SMI (EOS) installation requirements, 3
SMI-A
H installing as a service, 5
installing on Windows, 6
heap size, increasing, 3 uninstalling, 31
help, SMI agent support, xiii Storage Management Initiative (SMI), xi
Storage Management Initiative Specification (SMI-S), xi
Storage Networking Industry Association (SNIA), xi
supported platforms, 1
I
increasing heap size, 3
installation requirements, 1 U
installing SMI-A as a service, 5
installing SMI-A on Windows, 6 uninstalling SMI-A, 31
installing SMI-A with SMI (EOS), 3
W
M Web Based Enterprise Management (WBEM), xi
memory requirements, 2
multi-homed support, enabling, 30

53-1001777-01
53-1001777-01

Smiagent120.11.0 InstallGuide

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Smiagent120.11.0 InstallGuide

Încărcat de

Drepturi de autor:

Formate disponibile

53-1001777-01 ®

Brocade SMI Agent

Supporting SMI Agent 120.11.0

Brocade Communications Systems, Incorporated

European Headquarters Asia-Pacific Headquarters

Title Publication number Summary of changes Date

Brocade SMI Agent Installation Guide iii

About This Document

Chapter 1 Installation Requirements

Chapter 2 Installing the SMI Agent

Brocade SMI Agent Installation Guide v

Chapter 3 Silent Installation Status Messages

Chapter 4 Frequently Asked Questions

vi Brocade SMI Agent Installation Guide

How this document is organized

Supported hardware and software

Brocade SMI Agent Installation Guide vii

viii Brocade SMI Agent Installation Guide

What’s new in this document

Brocade SMI Agent Installation Guide ix

Notes, cautions, and warnings

Notice to the reader

Corporation Referenced Trademarks and Products

IBM Corporation AIX

x Brocade SMI Agent Installation Guide

Other industry resources

Brocade SMI Agent Installation Guide xi

The serial number label is located as follows:

xii Brocade SMI Agent Installation Guide

Brocade SMI Agent support

Brocade SMI Agent Installation Guide xiii

Brocade SMI Agent Installation Guide 1

Table 1 lists the memory and CPU recommendations.

TABLE 1 System requirements

Memory usage by the Agent less than 512 MB less than 1 GB

2 Brocade SMI Agent Installation Guide

To increase the heap size

SMI-A (Fabric OS) and SMI (EOS) coexistence requirements

Brocade SMI Agent Installation Guide 3

SMI (EOS) uses the default ports

4 Brocade SMI Agent Installation Guide

Installing the SMI Agent 2

Before installing the SMI Agent on Linux, Solaris, and AIX

Brocade SMI Agent Installation Guide 5

1. Go to the previously installed <SMIAgent>/agent/server/jserver/bin directory.

Install the Brocade SMI Agent using the wizard

Installing the SMI-A using the wizard

6 Brocade SMI Agent Installation Guide

2. Run the installation file.

The installation wizard launches, as shown in Figure 1.

FIGURE 1 Installation wizard

Brocade SMI Agent Installation Guide 7

FIGURE 2 System configuration

5. Read the introduction and click Next.

8 Brocade SMI Agent Installation Guide

FIGURE 4 Choose installation folder

Brocade SMI Agent Installation Guide 9

FIGURE 5 Importing configuration

The following files from the selected installation are copied:

10 Brocade SMI Agent Installation Guide

FIGURE 6 HTTP port configuration

8. Use the default port number, or enter a new port number.