0% found this document useful (0 votes)
13 views53 pages

Installation Guide

The Brocade Network Advisor Installation Guide provides essential information for installing and configuring the Network Advisor 11.2.1 software. It includes system requirements, pre-installation steps, and detailed instructions for various configurations and troubleshooting. The document also outlines the minimum host requirements for different network setups and provides contact information for Brocade Communications Systems, Inc.

Uploaded by

gerrymrichards
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views53 pages

Installation Guide

The Brocade Network Advisor Installation Guide provides essential information for installing and configuring the Network Advisor 11.2.1 software. It includes system requirements, pre-installation steps, and detailed instructions for various configurations and troubleshooting. The document also outlines the minimum host requirements for different network setups and provides contact information for Brocade Communications Systems, Inc.

Uploaded by

gerrymrichards
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 53

53-1002532-01 ®

16 March 2011

Brocade Network Advisor


Installation Guide

Supporting Network Advisor 11.2.1


Copyright © 2010-2011 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, MLX, SAN Health, VCS, and VDX are registered trademarks, and AnyIO, Brocade
One, CloudPlex, Effortless Networking, ICX, NET Health, OpenScript, and The Effortless Network are trademarks of Brocade Communications
Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks 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.
130 Holger Way No. 1 Guanghua Road
San Jose, CA 95134 Chao Yang District
Tel: 1-408-333-8000 Units 2718 and 2818
Fax: 1-408-333-8101 Beijing 100020, China
E-mail: [email protected] Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: [email protected]
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: [email protected]
Fax: +41 22 799 5641
E-mail: [email protected]

Document History

Title Publication number Summary of changes Date

Brocade Network Advisor Installation Guide 53-1002046-01 New document. October 2010
Brocade Network Advisor Installation Guide 53-1002170-01 Updated for the Network May 2011
Advisor 11.1.X release.
Brocade Network Advisor Installation Guide 53-1002357-01 Updated for the Network September 2011
Advisor 11.2.X release.
Brocade Network Advisor Installation Guide 53-1002532-01 Updated for the Network March 2011
Advisor 11.2.1 release.

2 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
In this guide

In this guide
• System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
• Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
• Installing the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
• Headless installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
• Professional edition configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
• Trial version configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
• License version configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
• SMI Agent only configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
• Syslog troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
• Installing the ODBC driver on Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
• Configuring an explicit server IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
• Smart Card driver installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
• Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
• Edition feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
• Network Advisor packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
• Management server and client ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
• Scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Brocade Network Advisor Installation Guide 3 of 53


53-1002532-01
System requirements

System requirements
Use the following sections to determine if you have met the requirements for this application.
• “Operating system requirements” on page 4
• “Host requirements” on page 6
• “Memory requirements” on page 7
• “Disk space requirements” on page 9
• “Browser requirements” on page 10
• “Client and server system requirements” on page 11

Operating system requirements


Table 1 summarizes the required Operating Systems (OS) for servers and the packages supported by each OS
version.

TABLE 1 Server operating system requirements


Operating system Version Guest OS version (VMWare only) Supported packages

Windows® • 2003 Server SP2 (x86 32-bit) SAN with SMI Agent
• 2008 Server (x86 32-bit) IP only
• XP Professional SP3 (x86 SMI Agent only
32-bit) SAN with SMI Agent + IP
• 7 Professional (x86 32-bit) (Professional, Professional Plus
(Medium), and Enterprise (Medium)
only)
• 2008 R2 Data Center Edition SAN with SMI Agent
(x86 64-bit) IP only
• 2008 R2 Standard Edition (x86 SMI Agent only
64-bit) SAN with SMI Agent + IP
• 2008 R2 Enterprise Edition
(x86 64-bit)
Linux® • RedHat 5.5 Advanced SAN with SMI Agent
Platform (x86 32-bit) IP only
• RedHat 5.6 Advanced SMI Agent only
Platform (x86 32-bit, x86 64-bit SAN with SMI Agent + IP
— Network Advisor will run in
32-bit compatability mode)
• RedHat 6.1 Advanced
Platform (x86 32-bit)
• SuSE Enterprise Server 11 (x86
32-bit)
• Oracle Enterprise 5.6 (x86
32-bit)

4 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
System requirements

TABLE 1 Server operating system requirements (Continued)


Operating system Version Guest OS version (VMWare only) Supported packages

VMware® • ESX Server 4.1 Windows 2003 Server SP2 (x86 SAN with SMI Agent
• ESX Server 5.0 32-bit) IP only
• ESX Server i 5.0 SMI Agent only
• vCenter 4.1 SAN with SMI Agent + IP
(Professional, Professional Plus
(Medium), and Enterprise (Medium)
only)
• ESX Server 4.1 • Windows 2008 R2 Data Center SAN with SMI Agent
• ESX Server 5.0 Edition (x86 64-bit) IP only
• ESX Server i 5.0 • Windows 2008 R2 Standard SMI Agent only
• vCenter 4.1 Edition (x86 64-bit) SAN with SMI Agent + IP
• Windows 2008 R2 Enterprise
Edition (x86 64-bit)
• Linux RedHat 5.5 Advanced
Platform (x86 32-bit)
• Linux RedHat 5.6 Advanced
Platform (x86 32-bit, x86
64-bit)
• Linux SuSE Enterprise Server
11 (x86 32-bit)
• Linux Oracle Enterprise 5.6
(x86 32-bit)

Table 2 summarizes the required OS for clients.

TABLE 2 Client operating system requirements


Operating system Version Guest OS version

Windows • 2003 Server SP2 (x86 32-bit)


• 2008 Server R2 (x86 32-bit)
• 2008 Server R2 (x86 64-bit)
• XP Professional SP3 (x86 32-bit)
• 7 Professional (x86 32-bit)
Linux • RedHat 5.5 Advanced Platform (x86 32-bit)
• RedHat 5.6 Advanced Platform (x86 32-bit, 64-bit)
• RedHat 6.1 Advanced Platform (x86 32-bit)
• SuSE Enterprise Server 11 (x86 32-bit)
• Oracle Enterprise 5.6 (x86 32-bit)
VMware • ESX Server 4.1 • Windows 2003 Server SP2 (x86 32-bit)
• ESX Server 5.0 • Windows 2008 R2 (x86 32-bit)
• ESX Server i 5.0 • Windows 2008 R2 (x86 64-bit)
• vCenter 4.1
• ESX Server 4.1 • Linux RedHat 5.5 Advanced Platform (x86 32-bit)
• ESX Server 5.0 • Linux RedHat 5.6 Advanced Platform (x86 32-bit,
• ESX Server i 5.0 x86 64-bit)
• vCenter 4.1 • Linux RedHat 6.1 Advanced Platform (x86 32-bit)
• Linux SuSE Enterprise Server 11 (x86 32-bit)
• Linux Oracle Enterprise 5.6 (x86 32-bit)

Brocade Network Advisor Installation Guide 5 of 53


53-1002532-01
System requirements

Host requirements
Table 3 through Table 5 summarizes the minimum host requirements for running Network Advisor SAN with SMI
Agent + IP on Windows and Linux systems.

TABLE 3 SAN with SMI Agent + IP host requirements


Server/Client Professional Professional Plus

Server plus 1 local Intel Core2 duo 2 GHz or Intel Core2 duo 2 GHz or
client equivalent equivalent
Remote client only N/A Intel Core2 duo 2 GHz or
equivalent

TABLE 4 SAN with SMI Agent + IP host requirements for server plus 1 local client
Small LAN Medium LAN Large LAN

Small SAN Enterprise Intel Core2 duo 2GHz or Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo
equivalent 2.4 GHz or equivalent 2.4 GHz or equivalent
Medium SAN Enterprise Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo Intel quad dual core or dual
2.4 GHz or equivalent 2.4 GHz or equivalent quad core, 2.4 GHz or
equivalent
Large SAN Enterprise Intel Dual CPU Core2 duo Intel quad dual core or dual Intel quad dual core or dual
2.4 GHz or equivalent quad core, 2.4 GHz or quad core, 2.4 GHz or
equivalent equivalent

TABLE 5 SAN with SMI Agent + IP host requirements for remote client
Small LAN Medium LAN Large LAN

Small SAN Enterprise Intel Core2 duo 2 GHz or Intel Core2 duo 2 GHz or Intel Dual CPU Core2 duo
equivalent equivalent 2.4 GHz or equivalent
Medium SAN Enterprise Intel Core2 duo 2 GHz or Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo
equivalent 2.4 GHz or equivalent 2.4 GHz or equivalent
Large SAN Enterprise Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo Intel Dual CPU Core2 duo
2.4 GHz or equivalent 2.4 GHz or equivalent 2.4 GHz or equivalent,

Table 6 summarizes the minimum host requirements for running Network Advisor SAN with SMI Agent on Windows
and Linux systems.

TABLE 6 SAN with SMI Agent host requirements


Professional Professional Plus Enterprise

Small Medium Large LAN

Server plus one local Intel Core2 duo Intel Core2 duo Intel Core2 duo Intel Dual CPU Intel Dual CPU
client 2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent Core2 duo 2.4 GHz Core2 duo 2.4 GHz
or equivalent or equivalent
Remote client only N/A Intel Core2 duo Intel Core2 duo Intel Core2 duo Intel Core2 duo
2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent

6 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
System requirements

Table 7 summarizes the minimum host requirements for running Network Advisor IP on Windows and Linux systems.

TABLE 7 IP only host requirements


Professional Enterprise

Small Medium Large

Server plus one local Intel Core2 duo Intel Core2 duo Intel Dual CPU Intel Dual CPU
client 2 GHz or equivalent 2 GHz or equivalent, Core2 duo 2.4 GHz Core2 duo 2.4 GHz
or equivalent or equivalent
Remote client only N/A Intel Core2 duo Intel Core2 duo Intel Core2 duo
2 GHz or equivalent 2 GHz or equivalent 2 GHz or equivalent

Table 8 summarizes the minimum host requirements for running SMI Agent only on Windows and Linux systems.

TABLE 8 SMI Agent only host requirements


Enterprise

Small Medium Large

Server plus one local Intel Core2 duo Intel Dual CPU Intel Dual CPU
client 2GHz or equivalent Core2 duo 2.4 GHz Core2 duo 2.4 GHz
or equivalent or equivalent
Remote client only Intel Core2 duo Intel Core2 duo Intel Core2 duo
2GHz or equivalent 2GHz or equivalent 2GHz or equivalent

Memory requirements
Table 9 through Table 11 summarizes the minimum system memory requirements for running Network Advisor SAN
with SMI Agent + IP on Windows and Linux systems.

NOTE
These requirements are only applicable when no other applications are running on Network Advisor.

NOTE
Paging space should be equal to or exceed the physical memory size.

TABLE 9 SAN with SMI Agent + IP memory requirements


Server/Client Professional Professional Plus

Server plus 1 local client 2 GB (32-bit) 4 GB (32-bit)


3 GB (64-bit) 6 GB (64-bit)
Remote client only N/A 1 GB

Brocade Network Advisor Installation Guide 7 of 53


53-1002532-01
System requirements

NOTE
The Network Advisor Server for SAN with SMI Agent + IP (Enterprise) with both a large SAN and a large IP is only
supported on 64-bit Windows systems and 32-bit Linux systems.

TABLE 10 SAN with SMI Agent + IP (Enterprise) memory requirements for server plus 1 local client
Small LAN Medium LAN Large LAN

Small SAN 4 GB 4 GB (32-bit) 6 GB (64-bit)


6 GB (64-bit)
Medium SAN 4 GB (32-bit) 4 GB (32-bit) 6 GB (64-bit)
6 GB (64-bit) 6 GB (64-bit)
Large SAN 6 GB (64-bit) 6 GB (64-bit) 6 GB (64-bit)

NOTE
The Network Advisor Client for SAN with SMI Agent + IP (Enterprise) is also supported on 32-bit Windows and Linux
systems.

TABLE 11 SAN with SMI Agent + IP (Enterprise) memory requirements for remote client
Small LAN Medium LAN Large LAN

Small SAN Enterprise 2 GB 3 GB 4 GB

Medium SAN Enterprise 3 GB 4 GB 4 GB

Large SAN Enterprise 4 GB 4 GB 4 GB

Table 12 summarizes the minimum system memory requirements for running Network Advisor SAN with SMI Agent
on Windows and Linux systems.

TABLE 12 SAN with SMI Agent memory requirements


Server/Client Professional Professional Enterprise
Plus Small Medium Large

Server plus 1 local client 2 GB (32-bit) 3 GB (32-bit) 3 GB (32-bit) 4 GB (32-bit) 4 GB (32-bit)


3 GB (64-bit) 4 GB (64-bit) 4 GB (64-bit) 6 GB (64-bit) 6 GB (64-bit)
Remote client only N/A 1 GB 1 GB 2 GB 2 GB

Table 13 summarizes the minimum system memory requirements for running Network Advisor IP on Windows and
Linux systems.

TABLE 13 IP only memory requirements


Server/Client Professional Enterprise
Small Medium Large

Server plus 1 local client 2 GB (32-bit) 3 GB (32-bit) 4 GB (32-bit) 4 GB (32-bit)


3 GB (64-bit) 4 GB (64-bit) 6 GB (64-bit) 6 GB (64-bit)
Remote client only N/A 1 GB 2 GB 2 GB

8 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
System requirements

Table 14 summarizes the minimum system memory requirements for running SMI Agent only on Windows and Linux
systems.

TABLE 14 SMI Agent only memory requirements


Server/Client Enterprise
Small Medium Large

Server plus 1 local client 3 GB 4 GB 4 GB


Remote client only 1 GB 2 GB 2 GB

Disk space requirements


Table 15 through Table 17 summarizes the minimum disk space requirements for running Network Advisor SAN with
SMI Agent + IP on Windows and Linux systems.

TABLE 15 SAN with SMI Agent + IP disk space requirements


Server/Client Professional Professional Plus

Server plus 1 local client 10 GB 20 GB


Remote client only N/A 1 GB

TABLE 16 SAN with SMI Agent + IP (Enterprise) disk space requirements for server plus 1 local client
Small LAN Medium LAN Large LAN

Small SAN Enterprise 20 GB 60 GB 60 GB

Medium SAN Enterprise 60 GB 60 GB 80 GB

Large SAN Enterprise 60 GB 80 GB 80 GB

TABLE 17 SAN with SMI Agent + IP (Enterprise) disk space requirements for remote client
Small LAN Medium LAN Large LAN

Small SAN Enterprise 1 GB 1 GB 1 GB

Medium SAN Enterprise 1 GB 1 GB 1 GB

Large SAN Enterprise 1 GB 1 GB 1 GB

Table 18 summarizes the minimum disk space requirements for running Network Advisor SAN with SMI Agent on
Windows and Linux systems.

TABLE 18 SAN with SMI Agent disk space requirements


Server/Client Professional Professional Enterprise
Plus Small Medium Large

Server plus 1 local client 10 GB 10 GB 20 GB 40 GB 60 GB


Remote client only N/A 1 GB 1 GB 1 GB 1 GB

Brocade Network Advisor Installation Guide 9 of 53


53-1002532-01
System requirements

Table 19 summarizes the minimum required disk space requirements for running Network Advisor IP on Windows
and Linux systems.

TABLE 19 IP only disk space requirements


Server/Client Professional Plus Enterprise
Small Medium Large

Server plus 1 local client 10 GB 20 GB 40 GB 60 GB


Remote client only 1 GB 1 GB 1 GB 1 GB

Table 20 summarizes the minimum disk space requirements for running SMI Agent only on Windows and Linux
systems.

TABLE 20 SMI Agent only disk space requirements


Server/Client Enterprise
Small Medium Large

Server plus 1 local client 20 GB 40 GB 60 GB


Remote client only 1 GB 1 GB 1 GB

NOTE
If you enable periodic supportSave or configure the Network Advisor server as the Upload Failure Data Capture
location for monitored switches, then additional disk space will be required. Each switch supportSave file is
approximately 5 MB and each Upload Failure Data Capture file is approximately 500 KB. To determine the disk space
requirements, multiply the frequency of scheduled supportSave files by 5 MB and the expected Upload Failure Data
Capture files by 500 KB before the planned periodic purge activity.

Browser requirements
The launch of Network Advisor and the launch of Element Manager (Web Tools) from the application are supported
from the following browsers with a Java plug-in:
• Browsers
- Windows Internet Explorer under Windows
- Firefox under Windows or Linux
• Java Plug-ins
- Oracle JRE 1.6.0 update 26 for Network Advisor
- Oracle JRE 1.6.0 update 26 for Web Tools
For the website listing patch information, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html.

10 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Pre-installation requirements

Client and server system requirements

NOTE
Network Advisor is not supported in a Network Address Translation (NAT) environment where the server and client are
on different sides of the NAT Server.

Network Advisor has the following client and server system requirements:
• In the Professional edition, a single server supports a single client, which must be a local client only.
• In Professional Plus and Enterprise edtions, a single server supports a maximum of 8 clients, which can be local
or remote.

Pre-installation requirements
Before you install Network Advisor, make sure you meet the following requirements for each platform.
• Make sure all system requirements have been met prior to installation. For specific system requirements, refer
to “System requirements” on page 4.
• To avoid errors, close all instances of the application before beginning the installation or uninstallation
procedures.
For UNIX systems, if you still receive error messages after closing the application, enter the following commands:
#ps -ef | grep -i “” to list the process IDs
#kill -9 “Process_ID” where Process_ID is any Management application process

Additional UNIX pre-installation requirements


• Make sure that an X Server is available for display and is configured to permit X Client applications to display
from the host on which they are installing the Network Advisor server (typically, this simply requires that the
systems console be present and running with a logged-in user on the X Server-based desktop session, such as
KDE, GNOME, and so on).
If this is a headless unit with no console, refer to “Pre-installation requirements” on page 11.
• Make sure that the DISPLAY environment variable is correctly defined in the shell with a valid value (for example,
to display to the local console, export DISPLAY=:0.0, or to display to a remote system that has an X Server
running, export DISPLAY=Remote_IP_address:0.0).
You may also need to consider a firewall that might block the display to the X Server, which listens by default on
TCP port 6000 on the remote host.
To display to a remote system, you need to permit the remote display of the X Server by running the xhost +IP
command, where IP is the IP address of the Network Advisor server host from the X-based desktop of the remote
system.
• Make sure you test the DISPLAY definition by running the xterm command, from the same shell from which you
run install.bin. A new X terminal window to the destination X Server display should open.

Brocade Network Advisor Installation Guide 11 of 53


53-1002532-01
Installing the application

Installing the application


Use the following procdure to install Network Advisor. If you are migrating data, refer to the Network Advisor
Migration Guide.

NOTE
SMI Agent is only available with the SAN with SMI Agent or SAN with SMI Agent + IP packages, it is not available with
the IP only package.

NOTE
On Windows systems, you must be an Administrator with Read and Write privileges to install Network Advisor.

NOTE
On UNIX systems, you must be the root user to install Network Advisor.

To install the new application version, complete the following steps.


1. Insert the installation DVD into the DVD-ROM drive.
• For Windows systems, if autorun is enabled, the DVD Index page launches automatically. Click the Install
link.
If autorun is not enabled, open this file: DVD_Drive\Application_Name\windows\install.exe.
• For UNIX systems, open this file: DVD_Drive\Application_Name\UNIX_Platform\install.bin.
2. Click Next on the Introduction screen.
3. Read the agreement on the License Agreement screen, select I accept the terms of the License Agreement, and
click Next.
4. Select the usual location for your system application files (for example, D:\Program Files\Application_Name or
opt/Application_Name) on the Select Install Folder screen and click Next.

NOTE
Do not install to the root directory C:\ (Windows) or / (UNIX).

5. Review the displayed installation summary on the Pre-Installation Summary screen and click Install.
6. Make sure the Launch Configuration check box is selected (default) on the Installation Complete screen, and
click Done.

To configure the application, refer to one of the following sections:


• “Professional edition configuration” on page 14
• “Trial version configuration” on page 16
• “License version configuration” on page 21
• “SMI Agent only configuration” on page 25

12 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Headless installation

Headless installation
Headless installation, also known as silent mode installation, is fully supported on all platforms. Once initiated, the
headless installation requires minimal user interaction and runs based on the default values provided. Headless
installation performs the actual installation; however, you must use the Configuration wizard in graphical user
interface mode to copy data and settings, configure the FTP or SCP server, configure IP, and configure server ports.

Performing a headless installation on Windows and UNIX systems


To perform a headless installation through the CLI, insert the installation DVD into the DVD-ROM drive.
• For Windows systems, open a Command Prompt and execute this command:
install.exe -i silent -DUSER_INSTALL_DIR="C:\Program Files\Network Advisor11.X.X"
• For UNIX systems, open a UNIX shell and execute this command: install.bin -i silent
-DUSER_INSTALL_DIR="/opt/Network_Advisor11_X_X"
The application installs in silent mode using default settings.
To configure the application, refer to one of the following sections:
• “Professional edition configuration” on page 14
• “Trial version configuration” on page 16
• “License version configuration” on page 21
• “SMI Agent only configuration” on page 25

Troubleshooting the Linux headless installation


If you have completed all of the pre-Installation requirements and you are still unable to install the application, run
the following commands on the host.
1. Go to Install_Home/ (the directory containing install.bin).
2. Execute strace -f -F -v -s 1024 -o NetworkAdvisorinstall.txt ./install.bin.
3. Execute rpm -qa >> system.txt.
4. Execute ps -elf >> system.txt.
5. Execute md5sum install.bin >> system.txt.
6. Execute df -k >> system.txt.
7. Execute sh -c "xterm -e echo nothing >> system.txt 2>&1".
8. Execute env >> system.txt.
9. Execute sh -c "DISPLAY=:0.0 xterm -e echo nothing >> system.txt 2>&1".
10. Execute zip support1.zip NetworkAdvisorinstall.txt system.txt.
Send the support1.zip file output from the above (containing install.txt and system.txt) to Technical Support.
This file will help Technical Support isolate the issue.

Brocade Network Advisor Installation Guide 13 of 53


53-1002532-01
Professional edition configuration

Professional edition configuration


To configure Professional edition, complete the following procedures, as necessary:
• “Configuring Professional edition” on page 14
• “Installing the ODBC driver on Windows systems” on page 29
• “Configuring an explicit server IP address” on page 32
• “Smart Card driver installation” on page 34 (UNIX Only)
If you have not installed the application, refer to “Installing the application” on page 12. If you are migrating data,
refer to the Network Advisor Migration Guide.

Configuring Professional edition


1. Click Next on the Welcome screen.
2. Click No on the Copy Data and Settings screen, and click Next.
To migrate data from a previous management application version, refer to the Network Advisor Migration Guide.
3. Select one of the following options on the Package screen and click Next.
• SAN with SMI Agent
• IP
• SAN with SMI Agent + IP
4. Select Network Advisor - Professional on the Installation Type screen and click Next.
5. Choose one of the following options on the FTP Server screen and click Next.
• Select Internal FTP Server to configure an internal FTP server.
The internal FTP server uses a default account and port 21. You can configure your own account from the
Options dialog box. For instructions, refer to the Network Advisor User Manual or online help.
• Select External FTP Server to configure an exnternal FTP server.
You can configure the external FTP server settings from the Options dialog box. For instructions, refer to the
Network Advisor User Manual or online help.
If port 21 is busy, a “port not free” message displays. Click OK to close the message and continue. Once the
Management application is configured make sure port 21 is free and restart the Server to start the FTP service.

NOTE
If you use an FTP Server which is not configured on the same machine as the Management application, the
Firmware Repository feature will not be available.

6. Select an address from the Switch - Server IP Configuration Preferred Address list on the Server IP Configuration
screen and click Next.
The Server IP Configuration address is set to “localhost” by default. You cannot change this address.

14 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Professional edition configuration

7. Complete the following steps on the Server Configuration screen (Figure 1).

NOTE
Do not use port 1527 for any of these port numbers. Port 1527 is used internally by the server.

FIGURE 1 Server Configuration screen

a. Enter a port number in the Web Server Port # (HTTP) field (default is 80).
b. Enter a port number in the Database Port # field (default is 5432).

ATTENTION
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.

c. Enter a port number in the Starting Port # field (default is 24600).

NOTE
The server requires 13 consecutive free ports beginning with the starting port number.

d. Enter a port number in the Syslog Port # field (default is 514).

NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default syslog port number, refer to “Syslog
troubleshooting” on page 28.

e. Enter a port number in the SNMP Port # field (default is 162).


f. Click Next.
If you enter a syslog port number already in use, a “syslog port not free” message displays. Click No on the
message to remain on the Server Configuration screen and edit the syslog port number (return to step 7d).
Click Yes to close the message and continue with step 6.
If you enter a port number already in use, a warning displays next to the associated port number field. Edit
that port number and click Next.
8. Verify your configuration information on the Server Configuration Summary screen and click Next.

Brocade Network Advisor Installation Guide 15 of 53


53-1002532-01
Trial version configuration

9. Select the Start Client check box, if necessary, on the Start Server screen and click Finish.
After all of the Network Advisor services are started, the Log In dialog box displays.
To make changes to the configuration, you can re-launch the configuration wizard. On Windows systems, select
Start > Programs > Network Advisor 11.X.X > Configuration Wizard. On UNIX systems, execute sh
Install_Home/bin/configwizard.

NOTE
To launch the configuration wizard, you must be the Administrator on Windows systems and the root user on
UNIX systems.

10. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
11. Click OK on the Network Advisor Login Banner.

Trial version configuration


To configure trial version, complete the following procedures, as necessary:
• “Configuring trial version” on page 16
• “Installing the ODBC driver on Windows systems” on page 29
• “Configuring an explicit server IP address” on page 32
• “Smart Card driver installation” on page 34 (UNIX only)
If you have not installed the application, refer to “Installing the application” on page 12. If you are migrating data,
refer to the Network Advisor Migration Guide.

Configuring trial version


1. Click Next on the Welcome screen.
2. Select No on the Copy Data and Settings screen and then click Next.
To migrate data from a previous version, refer to the Network Advisor Migration Guide.
3. Select one of the following options on the Package screen and click Next.
• SAN with SMI Agent
• IP
• SAN with SMI Agent + IP
• SMI Agent only
If you selected SMI Agent only, refer to “SMI Agent only configuration” on page 25.
4. Select Network Advisor - 75 days Trial on the Installation Type screen and click Next.

ATTENTION
If you choose to install Trial, once the trial period ends (75 days), you must upgrade to Licensed version.

16 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Trial version configuration

5. Complete the following steps on the Trial Configuration screen.


a. (SAN with SMI Agent + IP or SAN with SMI Agent) Select one of the following from the SAN with SMI Agent
options:
- Enterprise (9000 switch ports, 24 fabrics and 10,000 devices)
Required for evaluation of DCX Backbone and FICON management.
- Professional Plus (2560 switch ports, 4 fabrics and 4096 devices)
b. (SAN with SMI Agent + IP or IP) Select one of the following from the IP options:
- Support for 50 products
- Support for 150 products
c. (SAN with SMI Agent + IP or IP) Select the Support for 10 MPLS products check box to manage MPLS
products.
This option is required for evaluation of MPLS.
d. (IP) Select the Support for advanced capabilities check box to discover VM Managers.
(SAN with SMI Agent + IP) The Support for advanced capabilities check box is automatically selected and
cannot be cleared.
e. Click Next.
A “downgrading not supported” message displays. Click OK on the message. Make sure your configuration
is correct and click Next.
6. (SAN with SMI Agent + IP or SAN with SMI Agent) Select Internal FTP Server or External FTP Server on the FTP
Server screen and click Next.
The internal FTP server uses a default account and port 21. If port 21 is busy, a message displays. Click OK to
close the message and continue. Once Network Advisor is configured, make sure port 21 is free and restart the
server to start the FTP service.
You can configure your own account from the Options dialog box. For instructions, refer to Configuring an
internal FTP server and Configuring an external FTP or SCP server in the user manual.

NOTE
If you use an FTP Server which is not configured on the same machine as Network Advisor, the Firmware
Repository feature will not be available.

Brocade Network Advisor Installation Guide 17 of 53


53-1002532-01
Trial version configuration

7. Complete the following steps on the Server IP Configuration screen.


a. Select an address from the Server IP Configuration list.
b. Select an address from the Switch - Server IP Configuration Preferred Address list.

NOTE
If the “hostname” contains invalid characters, the host name does not display in the list. Valid characters
include alphanumeric and dash (-) characters. The IP address is selected by default. If an IPv6 address is
selected, server start up will fail.

If Domain Name System (DNS) is not configured for your network, do not select the “hostname” option from
either the Server IP Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the
“hostname” option prevents clients and devices from communicating with the server.
If you select a specific IP address from the Server IP Configuration screen and the selected IP address
changes, you will not be able to connect to the server. To change the IP address, refer to “Configuring an
explicit server IP address” on page 32.
c. Click Next.
8. Complete the following steps on the Server Configuration screen (Figure 2).

NOTE
Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server.

FIGURE 2 Server Configuration screen

a. Enable SSL by selecting the SSL Enabled check box.


b. Enter a port number in the Web Server Port # (HTTP) field (default is 80).
c. If you enabled SSL, enter a port number in the Web Server Port # (HTTPS) field (default is 443).
d. Enter a port number in the Database Port # field (default is 5432).

ATTENTION
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.

18 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Trial version configuration

e. Enter a port number in the Starting Port Number field (default is 24600).

NOTE
The server requires 16 consecutive free ports beginning with the starting port number.

f. Enter a port number in the Syslog Port Number field (default is 514).

NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default Syslog port number, refer to “Syslog
troubleshooting” on page 28.

g. Enter a port number in the SNMP Port Number field (default is 162).
h. Click Next.
If you enter a syslog port number already in use, a “syslog port not free” message displays. Click No on the
message to remain on the Server Configuration screen and edit the syslog port number. Click Yes to close
the message and continue with step 9.
If you enter a port number already in use, a Warning displays next to the associated port number field. Edit
that port number and click Next.
9. (SAN with SMI Agent + IP or SAN with SMI Agent) Complete the following steps on the SMI Agent Configuration
screen.

NOTE
If you selected IP only, this screen does not display. Continue with step 10.

a. Enable the SMI Agent by selecting the Enable SMI Agent check box.
b. Enable the SLP by selecting the Enable SLP check box, if necessary.
Only enabled after you select the Enable SMI Agent check box.
c. Enable the SSL by selecting the Enable SSL check box, if necessary.
Only enabled after you select the Enable SMI Agent check box.
d. Enter the SMI Agent port number in the SMI Agent Port # field (default is 5989 if SSL Enabled is selected;
otherwise, the default is 5988).
e. Click Next.

Brocade Network Advisor Installation Guide 19 of 53


53-1002532-01
Trial version configuration

10. (SAN with SMI Agent + IP or SAN with SMI Agent Enterprise) Select one of the following options on the SAN
Network Size screen and click Next:
• Small (managing up to 2000 switch ports, 1-20 domains)
• Medium (managing up to 5000 switch ports, 21-60 domains)
• Large (managing up to 9000 switch ports, 61-120 domains)
NOTE
If you selected the 75 day trial with the Professional Plus (2560 switch ports, 4 fabrics and 4096 devices)
option, the SAN Network Size screen does not display. The SAN size defaults to Small.

NOTE
If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled.

NOTE
Port count is equal to the total number of switch ports across all fabrics.

11. Verify your configuration information on the Server Configuration Summary screen and click Next.
12. Complete the following steps on the Start Server screen.
a. (SAN with SMI Agent + IP or SAN with SMI Agent) Select the Start SMI Agent check box, if necessary.
b. (SAN with SMI Agent + IP or SAN with SMI Agent) Select the Start SLP check box, if necessary.
c. Select the Start Client check box, if necessary.
d. Click Finish.
After all of the selected services are started, the Log In dialog box displays.
To make changes to the configuration, you can re-launch the configuration wizard. On Windows systems,
select Start > Programs > Network Advisor 11.X.X > Configuration Wizard. On UNIX systems, execute sh
Install_Home/bin/configwizard.

NOTE
To launch the configuration wizard, you must be the Administrator on Windows systems and the root user on
UNIX systems.

13. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
14. Click OK on the Network Advisor Login Banner.

20 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
License version configuration

License version configuration


To configure a licensed edition, complete the following procedures, as necessary:
• “Configuring Licensed version” on page 21
• “Installing the ODBC driver on Windows systems” on page 29
• “Configuring an explicit server IP address” on page 32
• “Smart Card driver installation” on page 34 (UNIX only)
If you have not installed the application, refer to “Installing the application” on page 12. If you are migrating data,
refer to the Network Advisor Migration Guide.

Configuring Licensed version


1. Click Next on the Welcome screen.
2. Select No on the Copy Data and Settings screen and then click Next.
To migrate data from a previous version, refer to the Network Advisor Migration Guide.
3. Select one of the following options on the Package screen and click Next.
• SAN with SMI Agent
• IP
• SAN with SMI Agent + IP
• SMI Agent only
If you selected SMI Agent only, refer to “SMI Agent only configuration” on page 25.
4. Select Network Advisor - Licensed Version on the Installation Type screen and click Next.
5. (Licensed Version only) If you are installing a licensed edition, browse to the license file (.xml) on the Server
License screen and click Next.
The License Key field is not case-sensitive.

NOTE
If you use the SAN with SMI Agent +IP Enterprise license key and the IP product managed count is more than
550, Event-based collection for IP discovery will be turned off.

If you have the SAN with SMI Agent +IP Enterprise license key, a message displays. Click No on the message to
remain on the Server License screen and edit the license key. Click Yes to close the message and continue with
step 6.
6. Select Internal FTP Server or External FTP Server on the FTP Server screen and click Next.
The internal FTP server uses a default account and port 21. If port 21 is busy, a message displays. Click OK to
close the message and continue. Once Network Advisor is configured, make sure port 21 is free and restart the
server to start the FTP service.
You can configure your own account from the Options dialog box. For instructions, refer to Configuring an
internal FTP server and Configuring an external FTP or SCP server in the user manual.

NOTE
If you use an FTP Server which is not configured on the same machine as Network Advisor, the Firmware
Repository feature will not be available.

Brocade Network Advisor Installation Guide 21 of 53


53-1002532-01
License version configuration

7. Complete the following steps on the Server IP Configuration screen.


a. Select an address from the Server IP Configuration list.
b. Select an address from the Switch - Server IP Configuration Preferred Address list.

NOTE
The host name does not display in the list if it contains invalid characters. Valid characters include
alphanumeric and dash (-) characters. The IP address is selected by default. If the an IPv6 address is
selected, server startup will fail.

If DNS is not configured for your network, do not select the “hostname” option from either the Server IP
Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the “hostname” option
prevents clients and devices from communicating with the server.
If you select a specific IP address from the Server IP Configuration screen and the selected IP address
changes, you will not be able to connect to the server. To change the IP address, refer to “Configuring an
explicit server IP address” on page 32.
c. Click Next.
8. Complete the following steps on the Server Configuration screen (Figure 3).

NOTE
Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server.

FIGURE 3 Server Configuration screen

a. Enable SSL by selecting the SSL Enabled check box.


b. Enter a port number in the Web Server Port # (HTTP) field (default is 80).
c. If you enabled SSL, enter a port number in the Web Server Port # (HTTPS) field (default is 443).
d. Enter a port number in the Database Port # field (default is 5432).

NOTE
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.

22 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
License version configuration

e. Enter a port number in the Starting Port Number field (default is 24600).

NOTE
The server requires 16 consecutive free ports beginning with the starting port number.

f. Enter a port number in the Syslog Port # field (default is 514).

NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default syslog port number, refer to “Syslog
troubleshooting” on page 28.

g. Enter a port number in the SNMP Port # field (default is 162).


h. Click Next.
If you enter a syslog port number already in use, a “syslog port not free” message displays. Click No on the
message to remain on the Server Configuration screen and edit the syslog port number. Click Yes to close
the message and continue with step 9.
If you enter a port number already in use, a warning displays next to the associated port number field. Edit
that port number and click Next.
9. (SAN with SMI Agent + IP or SAN with SMI Agent) Complete the following steps on the SMI Agent Configuration
screen.

NOTE
If you selected IP only, this screen does not display. Continue with step 10.

a. Enable the SMI Agent by selecting the Enable SMI Agent check box.
b. Enable the SLP by selecting the Enable SLP check box, if necessary.
Only enabled after you select the Enable SMI Agent check box.
c. Enable the SSL by selecting the Enable SSL check box, if necessary.
Only enabled after you select the Enable SMI Agent check box.
d. Enter the SMI Agent port number in the SMI Agent Port # field (default is 5989 if SSL Enabled is selected;
otherwise, the default is 5988).
e. Click Next.
10. (SAN with SMI Agent + IP or SAN with SMI Agent Enterprise) Select one of the following options on the SAN
Network Size screen and click Next:
• Small (managing up to 2000 switch ports, 1-20 domains)
• Medium (managing up to 5000 switch ports, 21-60 domains)
• Large (managing up to 9000 switch ports, 61-120 domains)
NOTE
Port count is equal to the total number of switch ports across all fabrics.

NOTE
If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled
for SAN Network Size (Enterprise).

Brocade Network Advisor Installation Guide 23 of 53


53-1002532-01
License version configuration

11. (SAN with SMI Agent + IP or IP Enterprise) Select one of the following options on the IP Network Size screen and
click Next:
• Small (managing up to 1000 device ports, 1-20 products)
• Medium (managing up to 10000 device ports, 21-200 products)
• Large (managing up to 25000 device ports, 201-5050 products)
NOTE
Port count is equal to the total number of all managed product ports.

NOTE
If you installed the SAN with SMI Agent + IP package on a 32-bit Windows system, the Large option is disabled
for IP Network Size (Enterprise and Professional Plus).

12. Verify your configuration information on the Server Configuration Summary screen and click Next.
13. Complete the following steps on the Start Server screen.
a. Select the Start SMI Agent check box, if necessary.
Only enabled if you enabled SMI Agent on the SMI Agent Configuration screen.
b. Select the Start SLP check box, if necessary.
Only enabled if you enabled SLP on the SMI Agent Configuration screen.
c. Select the Start Client check box, if necessary.
d. Click Finish.
After all of the services are started, the Log In dialog box displays.
To make changes to the configuration, you can re-launch the configuration wizard. On Windows systems,
select Start > Programs > Network Advisor 11.X.X > Configuration Wizard. On UNIX systems, execute sh
Install_Home/bin/configwizard.

NOTE
To launch the configuration wizard, you must be the Administrator on Windows systems and the root user on
UNIX systems.

14. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
15. Click OK on the Network Advisor Login Banner.

24 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
SMI Agent only configuration

SMI Agent only configuration


To configure the SMI Agent only, complete the following sections:
• “Installing the application” on page 12
• “Configuring SMI Agent only” on page 25

Configuring SMI Agent only


NOTE
If you choose to install only the SMI Agent, the configuration defaults to the SAN Enterprise package. When you open
the Network Advisor client, a License dialog displays, where you must enter a SAN Enterprise license key to use the
client. If you enter a SAN Professional Plus license key, you must re-install the application.

1. Click Next on the Welcome screen.


2. Select No on the Copy Data and Settings screen and then click Next.
3. Select SMI Agent only on the Package screen and click Next.
4. Complete the following steps on the Server IP Configuration screen.
a. Select an address from the Server IP Configuration list.

NOTE
If the Server IP Configuration list contains a duplicate IP address or is empty, an error message displays and
the configuration wizard closes.

b. Select an address from the Switch - Server IP Configuration Preferred Address list.

NOTE
The host name does not display in the list if it contains invalid characters. Valid characters include
alphanumeric and dash (-) characters. The IP address is selected by default. If the an IPv6 address is
selected, server startup will fail.

If DNS is not configured for your network, do not select the “hostname” option from either the Server IP
Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the “hostname” option
prevents clients and devices from communicating with the server.
If you select a specific IP address from the Server IP Configuration screen and the selected IP address
changes, you will not be able to connect to the server. To change the IP address, refer to “Configuring an
explicit server IP address” on page 32.
c. Click Next.

Brocade Network Advisor Installation Guide 25 of 53


53-1002532-01
SMI Agent only configuration

5. Complete the following steps on the Server Configuration screen.

NOTE
Do not use port 2638 for any of these port numbers. Port 2638 is used internally by the server.

FIGURE 4 Server Configuration screen

a. Enable SSL by selecting the SSL Enabled check box.


b. Enter a port number in the Web Server Port # (HTTP) field (default is 80).
c. If you enabled SSL, enter a port number in the Web Server Port # (HTTPS) field (default is 443).
d. Enter a port number in the Database Port # field (default is 5432).

ATTENTION
Do not use a port number less than 1024. Using a port number less than 1024 causes the installation to
stop responding (hang or freeze) on “Initialize Database”.

e. Enter a port number in the Starting Port # field (default is 24600).

NOTE
The server requires 16 consecutive free ports beginning with the starting port number.

f. Enter a port number in the Syslog Port # field (default is 514).

NOTE
If the default syslog port number is already in use, you will not receive any syslog messages from the device.
To find and stop the process currently running on the default syslog port number, refer to “Syslog
troubleshooting” on page 28.

g. Enter a port number in the SNMP Port # field (default is 162).


h. Click Next.
If you enter a syslog port number already in use, a “syslog port not free” message displays. Click No on the
message to remain on the Server Configuration screen and edit the syslog port number (return to step 5e).
Click Yes to close the message and continue with step 8.
If you enter a port number already in use, a warning displays next to the associated port number field. Edit
that port number and click Next.

26 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
SMI Agent only configuration

6. Complete the following steps on the SMI Agent Configuration screen.


The Enable SMI Agent and Enable SLP check boxes are selected by default and cannot be cleared.
a. Enable the SSL by selecting the Enable SSL check box, if necessary.
b. Enter the SMI Agent port number in the SMI Agent Port # field (default is 5989 if SSL Enabled is selected;
otherwise, the default is 5988).
c. Click Next.
7. Select one of the following options on the SAN Size screen and click Next:

NOTE
Port count is equal to the total number of switch ports across all fabrics.

• Small (managing up to 2000 ports, 1-20 domains)


• Medium (managing up to 5000 ports, 21-60 domains)
• Large (managing up to 9000 ports, 61-120 domains)
8. Verify your configuration information on the Server Configuration Summary screen and click Next.
9. Complete the following steps on the Start Server screen.
a. Select the Start SMI Agent check box, if necessary.
b. Select the Start SLP check box, if necessary.
c. Click Finish.
After all of the services (SLP and SMI Agent) are started, the configuration wizards closes. You can access
the SMIA Configuration Tool from the Server Management Console (Start > Programs > Network Advisor
11.2.1 > Server Management Console).

NOTE
To launch the Server Management Console, you must be the Administrator on Windows systems and the
root user on UNIX systems.

Launching the SMIA Configuration Tool


NOTE
To launch the Server Management Console, you must be the Administrator on Windows systems and the root user on
UNIX systems.

1. Launch the Server Management Console from the Start menu.


2. Click Configure SMI Agent.
The SMIA Configuration Tool Log In dialog box displays.
3. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.

Brocade Network Advisor Installation Guide 27 of 53


53-1002532-01
Launching a remote client

Launching a remote client


To launch a remote client, complete the following steps.
1. Open a web browser and type the IP address of the Network Advisor server in the Address bar and press Enter.
If the web server port number does not use the default (443 if is SSL Enabled; otherwise, the default is 80), you
must enter the web server port number in addition to the IP address. For example, IP_Address:Port_Number.
The Network Advisor web start screen displays.
2. Click the Web Start the Network Advisor Client link.
The Log In dialog box displays.
3. Enter your user name and password.
The defaults are Administrator and password, respectively. If you migrated from a previous release, your
username and password do not change.
4. Select or clear the Save password check box to choose whether you want the application to remember your
password the next time you log in.
5. Click Login.
6. Click OK on the Network Advisor Login Banner.

Syslog troubleshooting
If the default syslog port number is already in use, you will not receive any syslog messages from the device. Use one
of the following procedures (depending on your operating system), to determine which process is running on the
syslog port and to stop the process.

Windows operating system


Finding the process
1. Open a command window.
2. Type netstat –anb | find /i “514” and press Enter.
The process running on port 514 displays.
Example output: UDP 127:0:0:1:514 *:* 3328.

Stopping the process


Type taskkill /F /PID “<PID>” and press Enter.
For example, taskkill /F /PID "<3328>".
OR
1. Select Ctrl + Shift + Esc to open Windows Task Manager.
2. Click the Processes tab.
3. Click the PID column header to sort the processes by PID.
4. Select the process you want to stop and click End Process.

28 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Installing the ODBC driver

Linux operating system


Finding the process
1. Open a command window.
2. Type netstat –nap | grep 514 and press Enter.
The process running on port 514 displays.
Example output: UDP 0 0 ::ffff:127:0:0:1:514 :::* 27397.

Stopping the process


Type kill -9 “<PID>” and press Enter.
For example, kill -9 “<27397>”.

Installing the ODBC driver


You must have the Open Database Connectivity (ODBC) driver to allow remote clients to export data and generate
reports. The ODBC driver enables you to configure the data source name (DSN) for the Network Advisor database.

Installing the ODBC driver on Windows systems


You must have the Open Database Connectivity (ODBC) driver to allow remote clients to export data and generate
reports. The ODBC driver enables you to configure the data source name (DSN) for the Network Advisor database.
To install the ODBC driver, complete the following steps.
1. Double-click edb_psqlodbc.exe located on the DVD (DVD_Drive/Network Advisor/odbc/Windows).
2. Install the file to the usual location for your system’s application files (for example, C:\Program Files\Network
Advisor ODBC Driver) on the Select Install Folder screen and click Next.

NOTE
If you select an invalid location, the ODBC driver is installed in a different location than where the ODBC
executable drivers are located.

3. On the Ready to Install screen click Next.


4. Click Finish to complete the installation.
5. Choose one of the following opitions:
• (32-bit OS) Select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
• (62-bit OS) (Windows only) Select Start > Run, type %windir%\SysWOW64\odbcad32.exe and press Enter.
The ODBC Data Source Administrator dialog box displays.
6. Click the System DSN tab.
7. Click Add.
The Create a New Data Source dialog box displays.
8. Select PostgreSQL Unicode.

Brocade Network Advisor Installation Guide 29 of 53


53-1002532-01
Installing the ODBC driver

9. Click Finish.
The PostgreSQL Unicode ODBC Driver (psqlODBC) Setup dialog box displays.
10. Enter a name for the data source in the Datasource field.
11. Enter the description of the Network advisor database in the Description field.
12. Enter the name of the Network Advisor database in the Database field.
13. Select enable or disable from the SSL Mode list to specify whether or not to use SSL when connecting to the
database.
14. Enter the IP address or host name of the Network Advisor server in the Server field.
15. Enter the database server port number in the Port Number field.
16. Enter the database user name in the User Name field.
17. Enter the password in the Password field.
18. Click Test to test the connection.

NOTE
You can also use the Windows ODBC Driver Manager to add the DSN for the LINUX database server.

19. Click OK on the Connection Test dialog box.


20. Click Save.
21. Click OK on the ODBC Data Source Administrator dialog box.

Installing the ODBC driver on Linux systems


NOTE
The ODBC driver is not supported on 64-bit Linux systems.

You must have the Open Database Connectivity (ODBC) driver to allow remote clients to export data and generate
reports. The ODBC driver enables you to configure the data source name (DSN) for the Network Advisor database.
To install the ODBC driver, complete the following steps.
1. Execute the following command in the terminal:
> su
>chmod 777 edb_psqlodbc.bin
> ./edb_psqlodbc.bin

2. On the Setup psqlODBC screen click Next.


3. Install the file to the usual location for your system’s application files (for example, /opt/PostgreSQL/psqlODBC)
on the Installation Directory screen and click Next.

NOTE
If you select an invalid location, the ODBC driver is installed in a different location than where the ODBC
executable drivers are located.

4. On the Ready to Install screen click Next.


5. On the Completing the psqlODBC Setup Wizard screen click Finish to complete the installation.

30 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Installing the ODBC driver

Adding the Datasourse on Linux systems


Before you edit the INI files, install Network Advisor (refer to “Installing the application” on page 12) and make sure
the PostgreSQL database is up and running.

NOTE
For RedHat and Oracle Enterprise systems, the odbc.ini and odbcinst.ini files are located in /etc. For SUSE systems,
the odbc.ini and odbcinst.ini files are located in /etc/unixODBC.

1. Open the odbc.ini file in an editor and enter the datasource information as follows:
[TestDB]
Description = PostgreSQL 8.3
Driver = /opt/PostgreSQL/psqlODBC/lib/psqlodbcw.so
Database = dcmdb
Servername = 172.26.1.54
UserName = dcmadmin
Password = passw0rd
Port = 5432

2. Save and close the odbc.ini file.


3. Open the odbcinst.ini file in a text editor and make sure that the driver path information is correct.
After you install the PostgreSQL ODBC driver, the odbcinst.ini should automatically update the driver path. If the
direver path is not updated, add the following:
[psqlODBC]
Description=PostgreSQL ODBC driver
Driver=/opt/PostgreSQL/psqlODBC/lib/psqlodbcw.so

4. Save and close the odbcinst.ini file.

Testing the connection on Linux systems


To test the connection, complete the following steps.
1. Download and install Open Office.
2. Select File > New > Database.
The Database Wizard displays.
3. On the Select database screen, complete the following steps.
a. Select the Connect to an existing database option.
b. Select ODBC from the list.
c. Click Next.
4. On the Set up ODBC connection screen, complete the following steps.
a. Click Browse.
The datasource saved in the odbc.ini file is populated in the Datasource dialog box.
b. Select the datasource and click OK on the Datasource dialog box.
c. Click Next.
5. On the Set up user authentication screen, complete the following steps.
a. Enter the database user name in the User name field.
b. Select the Password required check box.

Brocade Network Advisor Installation Guide 31 of 53


53-1002532-01
Configuring an explicit server IP address

c. Click Test Connection to test the connection.


The Authentication Password dialog box displays.
d. Enter the database password in the Password field and click OK.
e. Click OK on the Connection Test dialog box.
If an error message (file not found while testing the connection) displays, copy the lib files from the
<postgresSQL path>/lib/* directory to the /usr/lib/ directory.
f. Click Next.
6. On the Save and proceed screen, click Finish.

Configuring an explicit server IP address


If you selected a specific IP address from the Server IP Configuration screen during installation and the selected IP
address changes, you will not be able to connect to the server. To connect to the new IP address, you must manually
update the IP address information.
To change the IP address, complete the following steps.
1. Choose one of the following options:
• On Windows systems, select Start > Programs > Network Advisor 11.2.1 > Network Advisor Configuration.
• On UNIX systems, execute sh Install_Home/bin/configwizard in terminal.
2. Click Next on the Welcome screen.
3. Click Yes on the confirmation message.
4. Click Next on the FTP Server screen.
5. Complete the following steps on the Server IP Configuration screen.
a. Select an address from the Server IP Configuration list.
b. Select an address from the Switch - Server IP Configuration Preferred Address list.

NOTE
The host name does not display in the list if it contains invalid characters. Valid characters include
alphanumeric and dash (-) characters. The IP address is selected by default. If the an IPv6 address is
selected, server startup will fail.

If DNS is not configured for your network, do not select the “hostname” option from either the Server IP
Configuration or Switch - Server IP Configuration Preferred Address list. Selecting the “hostname” option
prevents clients and devices from communicating with the server.
c. Click Next.
6. Click Next on the Server Configuration screen.
7. (SAN with SMI Agent or SAN with SMI Agent + IP packages) Click Next on the SMI Agent Configuration screen.
8. Verify your configuration information on the Server Configuration Summary screen and click Next.
9. Click Finish on the Start Server screen.
10. Click Yes on the restart server confirmation message.

32 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Configuring an explicit server IP address

Brocade Network Advisor Installation Guide 33 of 53


53-1002532-01
Smart Card driver installation

11. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
12. Click OK on the Login Banner.

Smart Card driver installation


Windows operating systems do not require smart card drivers to be installed separately; the driver is bundled with
the operating system. However, you must install a smart card driver for the Linux operating systems. You must install
both the special USB Chip/Smart Card Interface Device (USB CCID) and the PC/SC IFD driver. You can download the
source code and compile it from one of the following websites:
• USB CCID (ccid-1.3.7.tar.bz2)
Open Source URL: http://pcsclite.alioth.debian.org/ccid.html.
• Muscle PC/SC IFD Driver (pcsc-lite-1.4.101.tar.gz)
Open Source URL: https://alioth.debian.org/frs/?group id=30105.
The Encryption Manager Client within Network Advisor provides the binary code on both platforms for installation.
You must uncompress or untar the file depending on the platform. The procedures for the local client and the remote
client configurations follow. The thirdparty/pscs-lite-1.4.101-linux-x86.tar.gz file can be found on the Network Advisor
DVD.

Installing the Smart Card driver on the local client


1. Verify that the /opt directory exists.
If the /opt directory does not exist, create an /opt directory. If you want to install the driver in a different
directory, create that directory. Otherwise, skip this step.
> su
> mkdir /opt

2. Copy the appropriate pscs file for your platform (Linux) from the DVD and rename the file as
pcsc-lite-1.4.101-linux-x86.tar.gz file.
3. Log in as the superuser to untar the pcsc-lite-1.4.101-linux-x86.tar.gz file.
> su
> cd /opt
> gunzip pcsc-lite-1.4.101-linux-x86.tar.gz
> tar -xvf pcsc-lite-1.4.101-linux-x86.tar
After the pcsc_lite_1.4.101.tar file is extracted, the necessary binary, library, and smart card drivers are stored
in the /opt/pcsc directory.
4. If you installed a pcsc directory into a location other than /opt, modify the pcscctl script to change “/opt” to the
directory you specified in step 1.
> cd <new_dir>
> vi pcscctl

Search for “/opt” and change it to the name of the new directory.

34 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Smart Card driver installation

5. Create a soft link into the system directory. This is to support the automatic restart of the pcscd daemon upon
system restart.
If you installed the pcsc directory into the /opt directory, just create the soft link. Otherwise, use the name of the
new directory in place of /opt.
S.u.s.e> ln –s /opt/pcsc/pcscctl /etc/init.d/pcscd
S.u.s.e> chkconfig --add pcscd

or
redhat> ln –s /opt/pcsc/pcscctl /etc/init.d/pcscd
redhat> chkconfig --add pcscd

NOTE
Before you enter chkconfig --add pcscd, you can enter chkconfig –list | grep pcscd to verify that the pcscd
file is already on the list. If it already exists, you do not need to enter chkconfig –add pcscd. After you reboot
the system, you should expect the following links under /etc/rc2.d, /etc/rc3.d, /etc/rc3.d, /etc/rc4.d, and
/etc/rc5.d.

lrwxrwxrwx 1 root root 15 Jul 28 01:50 S94pcscd -> ../init.d/pcscd

NOTE
For some Linux vendors, the Smart Card driver may come with the operating system. In this case, extra
system configuration may be needed. For more information, refer to “Detecting and correcting a default
Linux Smart Card driver” on page 36.

6. Start the pcscd daemon or stop the pcscd daemon.


To start pcscd, type:
> /opt/pcsc/pcscctl start
To stop pcscd, type:
> /opt/pcsc/pcscctl stop

Brocade Network Advisor Installation Guide 35 of 53


53-1002532-01
Smart Card driver installation

Installing the Smart Card driver on the remote client


1. Complete steps 1 through 4 in “Installing the Smart Card driver on the local client” on page 34.
2. Run the following commands to support remote clients (Web Start).
> cd /usr/lib
> ln –s /opt/pcsc/lib/libpcsclite.so .

NOTE
If a soft link exists on libpcsclite.so, make sure that the final file is linked to /opt/pcsc/lib/libpcsclite.so.xxx.
It is recommended that you back up the original.

Example
> ls –l libpcsc*
lrwxrwxrwx 1 root root 20 Aug 4 16:16 libpcsclite.so ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 20 Jun 4 12:30 libpcsclite.so.1 ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 34 Aug 5 14:36 libpcsclite.so.1.0.0

> mv libpcsclite.so.1.0.0 libpcsclite.so.1.0.0.org


> ln -s /opt/pcsc/lib/libpcsclite.so.1.0.0 libpcsclite.so.1.0.0

> ls –l libpcsc*
lrwxrwxrwx 1 root root 20 Aug 4 16:16 libpcsclite.so ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 20 Jun 4 12:30 libpcsclite.so.1 ->
libpcsclite.so.1.0.0
lrwxrwxrwx 1 root root 34 Aug 5 14:36 libpcsclite.so.1.0.0 ->
/opt/pcsc/lib/libpcsclite.so.1.0.0
-rwxr-xr-x 1 root root 35428 Aug 4 16:17 libpcsclite.so.1.0.0.org

Detecting and correcting a default Linux Smart Card driver


This section applies to the Linux system only. Some Linux systems may provide a default Smart Card driver and have
their own setup to activate it. In this case, you must use the driver provided with Network Advisor. Otherwise, there
could be an incompatibility issue between the driver and the native library that could cause a driver detection failure.
Complete the following steps to discover whether a default driver already exists and how to reconfigure the driver
environment.
1. Detect a different Smart Card driver by running the following commands:
> cd /
> find . –name pcscd –print

If the results contain “pcscd”, and it is not located under /opt/pcsc or /etc/init.d/pcscd, a different driver exists
on the system.
2. Make sure the pcscd file on the /etc/init.d directory is linked to /opt/pcsc/pcscctl by running the following
commands:
> cd /etc/init.d
> ls –l pcscd
lrwxrwxrwx 1 root root 17 Jul 28 01:29 pcscd -> /opt/pcsc/pcscctl

36 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Smart Card driver installation

3. If there is an existing pcscd script in this directory, you can move and rename this file before you overwrite it.
> mv /etc/init.d/pcscd /etc/init.d/pcscd.org

4. Create a soft link using the following command.


> ln –s /opt/pcsc/pcscctl /etc/init.d/pcscd

The existing pcscd.org script in this directory implies that a different driver version exists. You can compare the
existing one with the one under /opt/pcsc/pcscd/sbin. If the size is different and the existing pcscd script
contains the following information, you must clean up the driver configuration. The example below shows a
different pscsd.org script and how to do the configuration cleanup. The configuration level is 2345, the start
priority is 25, and the stop priority is 88.
> more /etc/init.d/pcscd

#!/bin/sh
#
# pcscd Starts the pcscd Daemon
#
# chkconfig: 2345 25 88

5. Remove the existing pcscd start priority file by deleting the file as SNNpcscd, where NN is the start priority. For
example, from the preceding step, the file name is S25pcscd.
> find /etc/. –name “S25pcscd” –exec rm {} \; -print
> sync;sync;sync
> reboot

After the reboot, the new configuration from the /opt/pcsc/pcscctl file should be under the /etc/rc2.d,
/etc/rc3.d, /etc/rc4.d, and /etc/rc5.d directories.
lrwxrwxrwx 1 root root 15 Jul 28 01:50 S94pcscd -> ../init.d/pcscd

6. For the remote client, ensure that the Smart Card native library is linked to the one under /opt/pcsc/lib.
> cd /
> find . –name libpcsclite.so* -print

If the library libpcsclite.so* exists in multiple locations, you must ensure that there is only one library under /lib
or /usr/lib, and that it is linked to the library on /opt/pcsc/lib correctly. For example, to find a copy of the library
on /lib, use the following commands.
> cd /lib
> ls –al libpcsclite.so

If a copy of the library exists, either remove it or save it as a backup.


To find a copy of the library on /usr/lib, use the following commands.
> cd /usr/lib
> ls –al libpcsclite.so

Use this copy for the soft link.


> ln –s /opt/pcsc/lib/libpcsclite.so /usr/lib/.

Brocade Network Advisor Installation Guide 37 of 53


53-1002532-01
Uninstallation

Uninstallation
This section provides step-by-step instructions to uninstall Network Advisor and SMI Agent from both Windows and
UNIX systems.

NOTE
Network Advisor is installed on a separate directory from your previous version; therefore, you do not need to uninstall
the previous version immediately. However, you cannot run both versions simultaneously.

Uninstalling from Windows systems


Follow these instructions to uninstall the Network Advisor and SMI Agent from your Windows system.
1. Select Start > Programs > Network Advisor 11.2.1 > Uninstall Network Advisor.
2. Select one of the following options on the Uninstall Option screen:
• Partial Uninstall—Configuration and performance data is retained to be re-used by the new installation.
• Full Uninstall—All data is removed.
3. Click Uninstall.
4. Click Done on the Uninstall Complete screen.

Uninstalling from Windows systems (headless uninstall)


If the application was installed using the headless installation, complete the following steps to uninstall Network
Advisor and SMI Agent from your Windows server.
1. Open a command prompt.
2. Choose one of the following options:
• To partially uninstall Network Advisor (configuration and performance data is retained to be re-used by the
new installation), execute Install_Home\Uninstall_Network Advisor 11.2.1\Uninstall_Network Advisor
11.2.1.exe –f <absolute path of partial uninstall property file>.
• To fully uninstall Network Advisor (all data is removed), execute Install_Home\Uninstall_Network Advisor
11.2.1\Uninstall_Network Advisor 11.2.1.exe –f <absolute path of full uninstall property file>.
When uninstallation is complete, an “Uninstallation complete” message displays. You must manually delete the
Install_Home/silent folder.

38 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Uninstallation

Uninstalling from UNIX systems


Follow these instructions to uninstall the Network Advisor and SMI Agent from your UNIX system.

NOTE
The Uninstall folder is retained.

1. Go to Install_Home/Uninstall_Network_Advisor11_2_1.
2. Execute ./Uninstall_Network_Advisor11_2_1.
3. Select one of the following options on the Uninstall Option screen:
• Partial Uninstall—Configuration and performance data is retained to be re-used by the new installation.
• Full Uninstall—All data is removed.
4. Click Uninstall.
5. Click Done on the Uninstall Complete screen.

Uninstalling from UNIX systems (headless uninstall)


If the application was installed using the headless installation, complete the following steps to uninstall Network
Advisor and SMI Agent from your UNIX server.
1. Go to Install_Home/Uninstall_Network_Advisor11_2_1.
2. Choose one of the following options:
• To partially uninstall Network Advisor (configuration and performance data is retained to be re-used by the
new installation), execute Uninstall_Network_Advisor 11_2_1 –f <absolute path of partial uninstall property
file>.
• To fully uninstall Network Advisor (all data is removed), execute \Uninstall_Network_Advisor 11_2_1 –f
<absolute path of full uninstall property file>.
When uninstallation is complete, an “Uninstallation complete” message displays. You must manually delete the
Install_Home/silent folder.

Brocade Network Advisor Installation Guide 39 of 53


53-1002532-01
Edition feature support

Edition feature support


Table 21 details whether the SAN features are supported in the Professional, Professional Plus, or Enterprise
versions, or only through the Element Manager of the device.

TABLE 21 SAN features supported


Feature Professional Professional Plus Enterprise

Access Gateway Management Yes Yes Yes


Active Sessions Yes Yes Yes
Call Home No Yes Yes
Configuration Management
Configuration file management Yes Yes Yes
Configuration repository management No Yes Yes
Firmware download Yes Yes Yes
Manual backup Yes Yes Yes
Periodic configuration backup and persistence No Yes Yes
Replicate switch configuration No Yes Yes
Save configuration Yes Yes Yes
Network Advisor Client No Yes Yes
Authentication
Authorization
Auditing
Deployment Manager
Encryption Yes Yes Yes
Layer 2 FC support Yes Yes Yes
Encryption configuration and monitoring No Yes Yes
Access Gateway – Cisco interop support No Yes Yes
Device decommissioning No Yes Yes
Fabric Binding No Yes Yes
Fabric Watch Element Element Element
Manager Manager Manager
Fault Management Yes Yes Yes
Show switch events
Show fabric events
Event actions
Pseudo events
Syslog registration and forwarding
SNMP trap registration and forwarding
NOTE: Professional edition does not support Event actions, Pseudo events, Syslog
forwarding, and SNMP trap forwarding.
FCIP Management Yes Yes Yes
FCIP configuration wizard
IP Troubleshooting

40 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Edition feature support

TABLE 21 SAN features supported (Continued)


Feature Professional Professional Plus Enterprise

FICON/CUP
Cascaded FICON configuration wizard No No Yes
Cascaded FICON Fabric merge wizard No No Yes
PDCM Matrix Element Element Yes
Manager Manager

Firmware Management and SupportSave Yes Yes Yes


Firmware download
Capture SupportSave
HBA Management Yes Yes Yes
Discovery
Configuration
HBA Port/Storage port mapping Yes Yes Yes
High Integrity Fabric No Yes Yes
IPv6
Server - Client support Yes Yes Yes
Server - Server support
Server - Switch support
iSCSI Discovery Yes Yes Yes
License No Yes Yes
Limited M-EOS fabric support No Yes Yes
Features that support M-EOS switches
Mixed fabric support
Pure fabric support
Meta-SAN No Yes Yes
Routing configuration
Domain ID configuration
M-EOS Element Manager No Yes Yes
Switch configuration for M-EOS switches through Element Manager
Name Server Yes Yes Yes
Open Trunking Support Yes Yes Yes
Display trunks on the topology
Display trunks properties
Display marching ants
Display connections properties
Performance management
Real Time Performance collection , display, and reports (5-second intervals on Yes Yes Yes
selected ports)
Historical Performance collection , display, and reports (5-second intervals on No Yes Yes
selected ports)
Thresholds No Yes Yes

Brocade Network Advisor Installation Guide 41 of 53


53-1002532-01
Edition feature support

TABLE 21 SAN features supported (Continued)


Feature Professional Professional Plus Enterprise

Top talkers No Yes Yes


Marching ants No Yes Yes
Performance aging No Yes Yes
Performance statistics Yes Yes Yes
End-to-End monitors No Yes Yes
Bottleneck Detection No Yes Yes
Policy Monitor Yes Yes Yes
Port Administration Element Element Element
Manager Manager Manager
Port Fencing (for M-EOS switches) No Yes Yes
User Management No Yes Yes
Reports Yes Yes Yes
Generate
View
Scalability
Up to 1000 port support Yes Yes Yes
Up to 2560 port support No Yes Yes
Up to 9000 port support No No Yes
Security management
Replicate switch policy configuration No Yes Yes
SNMP configuration Yes Yes Yes
L2 ACL configuration

42 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Edition feature support

TABLE 21 SAN features supported (Continued)


Feature Professional Professional Plus Enterprise

SMI Agent No Yes Yes


Server Profile
Fabric Profile
Indication Sub Profile
Zone Control Sub Profile
Enhanced Zoning and Enhanced Zoning Control Sub Profile
FDMI (Fabric Device Management Interface) Sub Profile
Fabrics Virtual Fabrics Sub Profile
Topology View Sub Profile
FC HBA (Fibre Channel Host Bus Adapter) Profile
Fan, Power Supply, and Sensor Profiles
Inter Fabric Routing (FCR) Profile
Trunking
CP Blade Sub Profile
CEE (Converged Enhanced Ethernet)
Launch In Context Profile
Switch Profile
Role Based Authorization (CEE ACL) Profile
N port Virtualizer (AG NPIV) Profile
Profile Registration Sub Profile
Object Manager Adapter Sub Profile
Fabric Views Sub Profile
Physical Package Sub Profile
Software Sub Profile
Access Points Sub Profile
Location Sub Profile
Fabric Switch Partitioning Sub Profile
FC Initiator Ports Sub Profile
Fabric and Host discovery
SAN Zoning
Switch configuration management Element Yes Yes
Manager
Switch port enable/disable through right-click menu Yes Yes Yes
Technical SupportSave Yes Yes Yes
Telnet Yes Yes Yes
NOTE: Telnet through the server is only supported on Windows systems.
Tool launcher (Setup tools)
Troubleshooting and Diagnostics No Yes Yes
Device connectivity troubleshooting wizard Yes Yes Yes
Trace Route Yes Yes Yes
Ping
Fabric device sharing No Yes Yes
Diagnostic Port Test
Virtual Fabrics
Discovery Yes Yes Yes

Brocade Network Advisor Installation Guide 43 of 53


53-1002532-01
Edition feature support

TABLE 21 SAN features supported (Continued)


Feature Professional Professional Plus Enterprise

Configuration No Yes Yes


VM Plugin Support No Yes Yes
Zoning
Member selection Yes Yes Yes
Zone editing Yes Yes Yes
Live fabric library scope Yes Yes Yes
QoS support Yes Yes Yes
Zone alias support Yes Yes Yes
Delete Zone database No Yes Yes
Impact analysis Yes Yes Yes
Remove offline devices No Yes Yes
TI Zones Yes Yes Yes
Device to Zone / zoneset participation analysis Yes Yes Yes
LSAN Zones No Yes Yes
Rolling back to an activated zone database No Yes Yes
Import or export a zone database No Yes Yes

Table 22 details whether the IP features are fully or partially supported in the Professional or Licensed Version.

TABLE 22 IP features supported


Feature Professional Licensed version

Address Finder No Yes


ADP management No Yes
Call Home support No Yes
CLI Configuration management No Yes
GSLB management No Yes
MLX/XMR management No Yes
MPLS management No Yes
SSL Certificate management No Yes
Third Party Device support No Yes
Tools launcher (Setup Tools) No Yes
Traffic Analyzer No Yes
User Account management (RBAC) No Yes
VIP Server management No Yes
HBA management No Partial support
Change management Partial support Yes
Configuration management Partial support Yes

44 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Network Advisor packages

TABLE 22 IP features supported (Continued)


Feature Professional Licensed version

Fault management Partial support Yes


Performance management Partial support Yes
Reports Partial support Yes
CLI Element Manager Yes Yes
Configuration wizard Yes Yes
Dashboard Yes Yes
DCB Configuration management Yes Yes
Deployment management Yes Yes
Discovery Yes Yes
FCoE Configuration management Yes Yes
Firmware management Yes Yes
IPv6 Server - Switch support Yes Yes
Power Center Yes Yes
Security configuration Yes Yes
Telnet Yes Yes
Topology management Yes Yes
VLAN management Yes Yes
Web Element Manager Yes Yes
Web Tools/Fabric Watch Yes Yes

Network Advisor packages


Table 23 summarizes the packages and available versions for each package.

TABLE 23 Packages and versions


Package Versions

SAN with SMI Agent +IP Licensed Version — Enterprise


• SAN — Support for 24 fabrics, 10,000 devices, and 9,000 switch ports
• IP — Support for 5,050 products and 100 MPLS products
Professional
• SAN — Support for 1 fabric, 1000 devices, and 1,000 switch ports
• IP — Support for 20 products
NOTE: SMI Agent is not supported on Professional.
SAN with SMI Agent Licensed Version — Enterprise
• SAN — Support for 24 fabrics, 10,000 devices, and 9,000 switch ports
Licensed Version — Professional Plus
• SAN — Support for 4 fabrics, 4,096 devices, and,2560 switch ports

Brocade Network Advisor Installation Guide 45 of 53


53-1002532-01
Management server and client ports

TABLE 23 Packages and versions (Continued)


Package Versions

Professional
• SAN — Support for 1 fabric, 1,000 devices, and 1,000 ports
NOTE: SMI Agent is not supported on Professional.
IP Licensed Version — Enterprise
• IP — Support for 5,050 products and 100 MPLS products
Professional
• IP — Support for 20 products
SMI Agent only N/A

Management server and client ports


The Management application has two parts: the Server and the Client. The Server is installed on one machine and
stores device-related information; it does not have a user interface. To view information through a user interface, you
must log in to the Server through a Client. The Server and Clients may reside on the same machine, or on separate
machines. If you are running Professional, the server and the client must be on the same machine.
In some cases, a network may utilize virtual private network (VPN) or firewall technology, which can prohibit
communication between Switches and the Servers or Clients. In other words, a Server or Client can find a Switch,
appear to log in, but is immediately logged out because the Switch cannot reach the Server or Client. To resolve this
issue, check to determine if the ports in the table below need to be opened up in the firewall.

NOTE
Professional edition does not support remote clients.

Table 24 lists the ports that need to be opened up in the firewall for Professional.

TABLE 24 Professional ports


Port Number Ports Transport Description Communication Path Open in Firewall

201 FTP Port (Control) TCP FTP Control port for internal Client–Server No
FTP server Switch–Server Yes
211, 2 FTP Port (Data) TCP FTP Data port for internal Client–Server No
FTP server Switch–Server Yes
221 SSH or Secure Telnet TCP Sectelnet port from server to Server–Switch Yes
switch/client to switch Client–Switch
231 Telnet TCP Telnet port from server/client Server–Switch Yes
to switch Client–Switch
25 SMTP Server port TCP SMTP Server port for E-mail Server–SMTP Yes
communication Server
49 TACACS+ Authentication port TCP TACACS+ server port for Server–TACACS+ Yes
authentication if TACACS+ is Server
chosen as an external
authentication

46 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Management server and client ports

TABLE 24 Professional ports (Continued)


Port Number Ports Transport Description Communication Path Open in Firewall

80 jboss.web.http.port TCP Non-SSL HTTP/1.1 connector Client–Server No


port
803, 4, 5 Switch http TCP Switch non-SSL http port for Server–Switch Yes
http and CAL communication Client–Switch
1611 SNMP Port UDP Default SNMP port Server–Switch Yes
3
162 snmp.trap.port UDP Default SNMP trap port Switch–Server Yes
6
514 Syslog Port UDP Default Syslog Port Switch–Server Yes
636 LDAP Authentication SSL port TCP LDAP server port for Server–LDAP Yes
authentication if LDAP is Server
chosen as an external
authentication and SSL is
enabled
5432 Database port (Enforced during install) TCP Port used by database Server–Database No
Remote ODBC–
Database
24600 jboss.naming.jnp.port - port 0 TCP Bootstrap JNP service port Client–Server No
24601 jboss.connector.ejb3.port - port 1 TCP EJB3 connector port Client–Server No
24602 jboss.connector.bisocket.port - port 2 TCP Bisocket connector port Client–Server No
24603 jboss.connector.bisocket.secondary.port TCP Bisocket connector secondary Client–Server No
- port 3 port
24604 jboss.naming.rmi.port - port 4 TCP RMI naming service port Client–Server No
24605 jboss.jrmp.invoker.port - port 5 TCP RMI/JRMP invoker port Client–Server No
24606 jboss.pooled.invoker.port - port 6 TCP Pooled invoker port Client–Server No
24607 jboss.connector.socket.port - port 7 TCP Socket invoker port Server No
24608 jboss.web.ajp.port - port 8 TCP AJP 1.3 connector port Server No
24609 jboss.web.service.port – port 9 TCP Web service port Server No
24610 connector.bind.port – port 10 TCP Port to listen for requests on Server No
24611 jboss.pooled.invoker.port - port 11 TCP Pooled invoker port Client–Server Yes
24612 jboss.connector.socket.port - port 12 TCP Socket invoker port Server No

Brocade Network Advisor Installation Guide 47 of 53


53-1002532-01
Management server and client ports

TABLE 24 Professional ports (Continued)


Port Number Ports Transport Description Communication Path Open in Firewall

32768 - Ephemeral ports UDP Ephemeral transport protocol Switch - Server Yes
65535 ports.

1 Port is not configurable (either in the switch or the Management server).


2 Every FTP session requires an additional port which is randomly picked. If the firewall is enabled then FTP operation (used for firmware
download, technical support, firmware import (from client-server) and so on.) will fail.
3 Ports configurable in the switch and the Management server. Port must be the same for all switches managed by the Management
server.
4 Ports used to launch the Web Tools application for Fabric OS switches from the Management client. This is applicable only when the
Fabric OS version is earlier than 6.1.1.
5 Port 80 is the default web server port number. If you set the web server port number to a port other than the default, you must open that
port in the firewall.
6 The Syslog listening port is configurable in the Management server. The switch always sends syslog messages to port 514. If you have
any other syslog daemon on the Management server machine already listening to 514, then the Management Server can be configured
to listen to a different port. You must manually configure relay in existing syslogd to forward the syslog messages to the Management
Server listening on the configured port.
7 The Management server tries to find a contiguous block of 13 ports from the starting port configured (for example, 24600); if any port in
this range is not available for the Management application, then you must provide a new starting port. Note that Port 1 to Port 12 in
“Ports” column of the table above are not separately configurable and those ports vary based on the starting port number configuration
(specified as Port 0 in the above table). The port numbers mentioned in the table above are the default ports (for example, when 24600
is selected as the starting port number).

Table 25 lists the ports that need to be opened up in the firewall for Trial and Licensed Version.

TABLE 25 Trial and Licensed Version ports


Port Number Ports Transport Description Communication Path Open in Firewall

201 FTP Port (Control) TCP FTP Control port for internal Client–Server Yes
FTP server Switch–Server Yes
211, 2 FTP Port (Data) TCP FTP Data port for internal Client–Server Yes
FTP server Switch–Server Yes
221 SSH or Secure Telnet TCP Sectelnet port from server to Server–Switch Yes
switch/client to switch Client–Switch
231 Telnet TCP Telnet port from server/client Server–Switch Yes
to switch Client–Switch
25 SMTP Server port TCP SMTP Server port for E-mail Server–SMTP Yes
communication Server
49 TACACS+ Authentication port TCP TACACS+ server port for Server–TACACS+ Yes
authentication if TACACS+ is Server
chosen as an external
authentication
80 jboss.web.http.port TCP Non-SSL HTTP/1.1 connector Client–Server Yes
port
803, 4 Switch http TCP Switch non-SSL http port for Server–Switch Yes
http and CAL communication Client–Switch
1611 SNMP Port UDP Default SNMP port Server–Switch Yes
1623 snmp.trap.port UDP Default SNMP trap port Switch–Server Yes

48 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Management server and client ports

TABLE 25 Trial and Licensed Version ports (Continued)


Port Number Ports Transport Description Communication Path Open in Firewall

389 LDAP Authentication Server Port TCP LDAP server port for Server–LDAP Yes
authentication if LDAP is Server
chosen as an external
authentication
4433, 4, 5 Switch https TCP Switch SSL http port for https Server–Switch Yes
and CAL communication Client–Switch
5146 Syslog Port UDP Default Syslog Port Switch–Server Yes
636 LDAP Authentication SSL port TCP LDAP server port for Server–LDAP Yes
authentication if LDAP is Server
chosen as an external
authentication and SSL is
enabled
10241, 7 MPI TCP MPI trap recipient port Switch–Server Yes
1812 RADIUS Authentication Server Port TCP RADIUS server port for Server–RADIUS Yes
authentication if RADIUS is Server
chosen as an external
authentication
20481, 9 MPI TCP MPI discovery NMRU port Server–Switch Yes
1,5,7,9
2049 MPI TCP MPI discovery NMRU port for Server–Switch Yes
SSL
26388 Database port (Enforced during install) TCP Port used by database Server–Database Yes
Remote ODBC–
Database
44301, 5, 7 MPI TCP XML-RCP port for SSL Server–Switch Yes
5988 SMI Agent port TCP SMI Agent port SMI Agent Server– Yes
Client
5989 SMI Agent port with SSL enabled TCP SMI Agent port with SSL SMI Agent Server– Yes
enabled Client
80801, 7 MPI TCP XML-RCP port/HTTP port Server–Switch Yes
10
24600 jboss.naming.jnp.port - port 0 TCP Bootstrap JNP service port Client–Server Yes
24601 jboss.connector.ejb3.port - port 1 TCP EJB3 connector port Client–Server Yes
24602 jboss.connector.bisocket.port - port 2 TCP Bisocket connector port Client–Server Yes
24603 jboss.connector.bisocket.secondary.port TCP Bisocket connector secondary Client–Server Yes
- port 3 port
246045 jboss.connector.sslbisocket.port - port 4 TCP SSL Bisocket connector port Client–Server Yes
246055 jboss.connector.sslbisocket.secondary.p TCP SSL Bisocket connector Client–Server Yes
ort - port 5 secondary port
24606 smp.registry.port - port 6 TCP RMI registry port Client–Server Yes
24607 smp.server.export.port - port 7 TCP RMI export port Client–Server Yes
24608 smp.server.cliProxyListening port - port TCP CLI proxy telnet port Client–Server Yes
8
24609 jboss.naming.rmi.port - port 9 TCP RMI naming service port Client–Server Yes

Brocade Network Advisor Installation Guide 49 of 53


53-1002532-01
Management server and client ports

TABLE 25 Trial and Licensed Version ports (Continued)


Port Number Ports Transport Description Communication Path Open in Firewall

24610 jboss.jrmp.invoker.port - port 10 TCP RMI/JRMP invoker port Client–Server Yes


24611 jboss.pooled.invoker.port - port 11 TCP Pooled invoker port Client–Server Yes
24612 jboss.connector.socket.port - port 12 TCP Socket invoker port Server No
24613 jboss.web.ajp.port - port 13 TCP AJP 1.3 connector port Server No
24614 jboss.web.service.port – port 14 TCP Web service port Server No
24615 connector.bind.port – port 15 TCP Port to listen for requests on Server No
32768 - Ephemeral ports UDP Ephemeral transport protocol Switch - Server Yes
65535 ports.
5555510 Client Export Port TCP Client port to which server Server–Client Yes
pushes the M-EOS device
Element Manager updates
55556 Launch in Context (LIC) client hand TCP Client port used to check if a Client No
shaking port Management application client
opened using LIC is running on
the same host
NOTE: If this port is in use, the
application uses the
next available port.

1 Port is not configurable (either in the switch or the Management server).


2 Every FTP session requires an additional port which is randomly picked. If the firewall is enabled then FTP operation (used for firmware
download, technical support, firmware import (from client-server) and so on.) will fail.
3 Ports configurable in the switch and the Management server. Port must be the same for all switches managed by the Management
server.
4 Ports used to launch the Web Tools application for Fabric OS switches from the Management client. This is applicable only when the
Fabric OS version is earlier than 6.1.1.
5 Port used for SSL communication. If SSL is enabled, you must open 443*, 24604, and 24605 in the firewall. If SSL is not enabled, port
80* must be open in the firewall and 443*, 24604, and 24605 can be closed. An asterisk (*) denotes the default web server port number.
If you set the web server port number to a port other than the default, you must open that port in the firewall.
6 The Syslog listening port is configurable in the Management server. The switch always sends syslog messages to port 514. If you have
any other syslog daemon on the Management server machine already listening to 514, then the Management Server can be configured
to listen to a different port. You must manually configure relay in existing syslogd to forward the syslog messages to the Management
Server listening on the configured port.
7 Ports used for communicating with M-EOSn (M-i10K) directors. M-i10K always uses NMRU over SSL (2049). M-i10K always uses 8080
for http requests (firmware download, configuration backup/ restore, data collection). If M-EOSn firmware version is less than 9.1 the
Management application uses 8080 for XML-RPC requests (discovery and asset collection). If the M-EOSn firmware version is more
than 9.1 then it always uses SSL port (4430) for XML-RPC.
8 Port must be opened in firewall for the server when the remote ODBC client needs to talk to the Management database server (Only for
EE). The same port is used by the Management server to database server (local). This is not used by the Management client.
9 Ports used for communicating with M-EOS (excluding M-i10K) switches (only required when the Management server manages M-EOS
switches).
10 Port should be opened in firewall in the Management client to allow communication between server and client (only applicable for
M-EOS switches). If this port is not opened in the firewall, then the M-EOS element manager does not receive updates. Also if multiple
clients are opened, it will try to use the next available port (55556). So if there are n clients opened in the same machine then you must
open 55555 (configurable) to 55555 + n ports in the firewall.
11 The Management server tries to find a contiguous block of 16 ports from the starting port configured (for example, 24600); if any port in
this range is not available for the Management application, then you must provide a new starting port. Note that Port 1 to Port 15 in
“Ports” column of the table above are not separately configurable and those ports vary based on the starting port number configuration
(specified as Port 0 in the above table). The port numbers mentioned in the table above are the default ports (for example, when 24600
is selected as the starting port number).

50 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Scalability limits

Scalability limits
The following tables summarize the scalability limits for support with Network Advisor.
Table 26 summarizes the SAN scalability limits for support with Network Advisor Enterprise edition.

TABLE 26 Enterprise-supported limits by SAN size


Small Medium Large

Number of Fabrics 8 16 24
Number of Domains 20 60 120
Number of Switch Ports 2000 5000 9000
Number of Device Ports 5000 10000 20000
Number of Access Gateways 20 30 40
Performance Monitoring Polling 5 minutes 5 minutes 5 minutes

Table 27 summarizes the SAN scalability limits for support with Network Advisor Professional Plus edition.

TABLE 27 Professional Plus-supported limits by SAN size


Values Limits

Number of Fabrics 4
Number of Domains 20
Number of Switch Ports 2560
Number of Device Ports 4096
Number of Access Gateways 20
Performance Monitoring Polling 5 minutes

Table 28 summarizes the SAN scalability limits for support with Network Advisor Professional edition.

TABLE 28 Professional-supported limits by SAN size


Values Limits

Number of Fabrics 1
Number of Domains 10
Number of Switch Ports 1000
Number of Device Ports 1000
Number of Access Gateways 5
Performance Monitoring Polling N/A

Brocade Network Advisor Installation Guide 51 of 53


53-1002532-01
Scalability limits

Table 29 summarizes the IP scalability limits for support with Network Advisor Enterprise edition.

TABLE 29 Enterprise-supported limits by IP size


Small Medium Large

Number of Products 1 - 20 21 - 200 201 - 5050


Number of MPLS Products 1 1 100

Table 30 summarizes the IP scalability limits for support with Network Advisor Professional edition.

TABLE 30 Professional-supported limits by IP size


Values Limits

Number of Products 20
Number of MPLS Products 0

Table 31 summarizes the SAN scalability limits for mixed fabrics (Fabric OS and M-EOS fabrics) with Network Advisor.

TABLE 31 Supported limits by SAN size for mixed fabrics (Fabric OS and M-EOS fabrics)
Values Small Medium Large

Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40
Performance Monitoring Polling 5 minutes 5 minutes 5 minutes

Table 32 summarizes the SAN scalability limits for pure M-EOS fabrics with Network Advisor.

TABLE 32 Supported limits by SAN size for pure M-EOS fabrics


Small Medium Large

Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40
Performance Monitoring Polling 5 minutes 5 minutes 5 minutes

52 of 53 Brocade Network Advisor Installation Guide


53-1002532-01
Scalability limits

Table 33 summarizes the SAN scalability limits for pure Fabric OS fabrics with Network Advisor Enterprise edition.

TABLE 33 Enterprise-supported limits by SAN size for SMI Agent only on pure Fabric OS fabrics
Small Medium Large

Number of Fabrics 8 16 24
Number of Domains 20 60 120
Number of Switch Ports 2000 5000 9000
Number of Device Ports 5000 10000 20000
Number of Access Gateways 20 30 40

Table 34 summarizes the SAN scalability limits for SMI Agent only on mixed fabrics (Fabric OS and M-EOS fabrics)
with Network Advisor.

TABLE 34 Supported limits by SAN size for SMI Agent only on mixed fabrics (Fabric OS and M-EOS fabrics)
Values Small Medium Large

Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40

Table 32 summarizes the SAN scalability limits for for SMI Agent only on pure M-EOS fabrics with Network Advisor.

TABLE 35 Supported limits by SAN size for SMI Agent only on pure M-EOS fabrics
Small Medium Large

Number of Fabrics 8 16 24
Number of Domains 10 30 60
Number of Switch Ports 1000 2500 5000
Number of Device Ports 2500 5000 10000
Number of Access Gateways 20 30 40

Brocade Network Advisor Installation Guide 53 of 53


53-1002532-01

You might also like