Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are
trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product
names mentioned may be trademarks of others.
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. assume no liability or responsibility to any person or entity with respect
to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the
computer programs that accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other
open source license agreements. To find out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate and Latin American Headquarters
Brocade Communications Systems, Inc.
130 Holger Way
San Jose, CA 95134
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com
European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 – 13th Floor
Guangzhou, China
Tel: +8620 3891 2000
Fax: +8620 3891 2111
E-mail: china-info@brocade.com
Document History
TitlePublication number Summary of changes Date
Brocade Network Advisor Installation and Migration Guide 53-1002570-01New documentAugust 2012
Brocade Network Advisor Installation and Migration Guide 53-1002699-01Update for 12.0December 2012
Brocade Network Advisor Installation and Migration Guide 53-1002950-01Update for 12.1July 2013
Brocade Network Advisor Installation and Migration Guide 53-1003059-01Update for 12.2.0February 2014
Brocade Network Advisor Installation and Migration Guide 53-1003157-01Update for 12.3.0July 2014
This document is organized to help you find the information that you want as quickly and easily as
possible.
The document contains the following components:
• Chapter 1, “Installation,” provides system and pre-installation requirements as well as
step-by-step installation instructions.
• Chapter 2, “Network Advisor Configuration,” provides step-by-step instructions to configure a
fresh Network Advisor installation.
• Chapter 3, “Data Migration,” provides pre-migration requirements as well as step-by-step
instructions for migrating data from a previous release of Network Advisor.
• Chapter 4, “Uninstallation,” provides step-by-step instructions for performing a partial or full
uninstall of Network Advisor.
• Appendix A, “References,” provides the following information for quick lookup:
-Network Advisor packages
-Edition feature support
-Management server and client ports
-Scalability limits
Brocade Network Advisor Installation and Migration Guidevii
53-1003157-01
Supported hardware and software
NOTE
In those instances in which procedures or parts of procedures documented here apply to some
devices but not to others, this guide identifies exactly which devices are supported and which are
not.
Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc. for Network Advisor 12.3.X, documenting all possible
configurations and scenarios is beyond the scope of this document.
Fabric OS hardware and software support
The following firmware platforms are supported by this release of Network Advisor 12.3.X:
• Fabric OS 5.0 or later in a pure Fabric OS fabric
• Fabric OS 6.0 or later in a mixed fabric
Discovery of a Secure Fabric OS fabric in strict mode is not supported.
The hardware platforms in Table 1 are supported by this release of Network Advisor 12.3.X.
TABLE 1Fabric OS-supported hardware
Device nameTerminology used in documentationFirmware level required
Brocade 200E switch16-port, 4 Gbps FC Switch
Brocade 300 switch24-port, 8 Gbps FC SwitchFabric OS v6.1.0 or later
Brocade 4012 switchEmbedded 12-port, 4 Gbps FC Switch
Brocade 4016 switchEmbedded 16-port, 4 Gbps FC Switch
Brocade 4018 switchEmbedded 18-port, 4 Gbps FC Switch
Brocade 4020 switchEmbedded 20-port, 4 Gbps FC Switch
Brocade 4024 switchEmbedded 24-port, 4 Gbps FC SwitchFabric OS v5.3.1 or later
Brocade 4100 switch32-port, 4 Gbps FC Switch
Brocade 4900 switch64-port, 4 Gbps FC SwitchFabric OS v5.2.0 or later
Brocade 5000 switch32-port, 4 Gbps FC Interop SwitchFabric OS v5.2.1 or later
Brocade 5100 switch40-port, 8 Gbps FC SwitchFabric OS v6.1.0 or later
Brocade 5300 switch80-port, 8 Gbps FC SwitchFabric OS v6.1.0 or later
Brocade 5410 embedded switchEmbedded 12-port, 8 Gbps SwitchFabric OS v6.1.0 or later
Brocade 5424 embedded switchEmbedded 24-port, 8 Gbps SwitchFabric OS v6.1.0 or later
Brocade 5431 embedded switchEmbedded 16-port, 8 Gbps Stackable SwitchFabric OS v7.2.0 or later
Brocade 5450 embedded switchEmbedded 16-port, 8 Gbps SwitchFabric OS v6.2.0 or later
Brocade 5460 embedded switchEmbedded 24-port, 8 Gbps SwitchFabric OS v6.1.0_emb or later
Brocade 5470 embedded switchEmbedded 24-port, 8 Gbps SwitchFabric OS v6.1.0 or later
Brocade 5480 embedded switchEmbedded 24-port, 8 Gbps SwitchFabric OS v6.1.0 or later
Brocade 6505 switch24-port, 16 Gbps Edge switchFabric OS v7.0.1 or later
viiiBrocade Network Advisor Installation and Migration Guide
53-1003157-01
TABLE 1Fabric OS-supported hardware (Continued)
Device nameTerminology used in documentationFirmware level required
Brocade M6505 embedded switch24-port, 16 Gbps embedded switchFabric OS v7.2.0 or later
Brocade 6510 switch 48-port, 16 Gbps switchFabric OS v7.0.0 or later
Brocade 6520 switch 96-port, 16 Gbps switchFabric OS v7.1.0 or later
Brocade 6547 embedded switch48-port, 16 Gbps embedded switchFabric OS v7.2.0 or later
Brocade 7500 Extension switch4 Gbps Router, Extension SwitchFabric OS v5.1.0 or later
Brocade 7500E Extension switch4 Gbps Extension SwitchFabric OS v5.1.0 or later
FR4-18i Blade4 Gbps Router, Extension blades
FX8-24 Blade8 Gbps Router, Extension bladesFabric OS v6.4.0 or later
Brocade AP7600 switch4 Gbps 32-port SwitchFabric OS v6.1.0 or later
Brocade 7800 switch8 Gbps Extension SwitchFabric OS v6.3.0 or later
Brocade 7840 switch16 Gbps 24-FC port, 18 GbE port SwitchFabric OS v7.3.0 or later
Brocade 8000 switch8 Gbps 8-FC port, 10 GbE 24-DCB port SwitchFabric OS v6.1.2_CEE
Brocade 8470 FCoE embedded switchFCoE Embedded SwitchFabric OS v6.3.1_CEE
Brocade VA-40FC switch8 Gbps 40-port Switch
Brocade 415 Host Bus Adapter4 Gbps 1-port HBA
Brocade 425 Host Bus Adapter4 Gbps 2-port HBA
Brocade 815 Host Bus Adapter8 Gbps 1-port HBA
Brocade 825 Host Bus Adapter8 Gbps 2-port HBA
Brocade 1860 Fabric Adapter16 Gbps FC HBA mode
10 Gbps CNA mode
10 Gbps NIC mode
Brocade 1867 HBA16 Gbps Mezzanine HBA Adapter Software 3.0.3.0 or later
Brocade 48000 directorDirector Chassis
Brocade 48000 director with FC4-16, FC4-32,
and FC4-48 Blades
Director Chassis with 4 Gbps 16-FC port, 4 Gbps
32-FC port, and 4 Gbps 48-FC port
Brocade 48000 director with FR4-18i BladesDirector Chassis with 4 Gbps router, extension
blades
Adapter Software 3.0.0.0 or later
Fabric OS v5.2.0 or later (FC4-48)
Fabric OS v5.1.0 or later (FR4-18i)
Brocade 48000 director with FC4-16IP BladesDirector Chassis with 4 Gbps 8-FC port and 8
Fabric OS v5.2.0 or later (FC4-16IP)
GbE iSCSI blades
Brocade 48000 director with FC10-6 BladesDirector Chassis with 10 Gbps 6-port ISL blades Fabric OS v5.3.0 or later (FC10-6)
Brocade DCX
Brocade DCX
FC8-48 Blades
1, 2
1, 2
with FC8-16, FC8-32, and
8-slot Backbone ChassisFabric OS v6.0.0 or later
8-slot Backbone Chassis with 8 Gbps 16-FC port,
Fabric OS v6.0.0 or later
8 Gbps 32-FC port, and 8 Gbps 48-FC port
blades
Brocade DCX
1, 2
with FC8-64 Blades8-slot Backbone Chassis with 8 Gbps 64-FC port
Fabric OS v6.4.0
blades
Brocade DCX
1, 2
with FR4-18i Blades8-slot Backbone Chassis with 4 Gbps Router,
Fabric OS v6.0.0 or later
Extension blade
Brocade DCX
Brocade Network Advisor Installation and Migration Guideix
53-1003157-01
1, 2
with FC10-6 Blades8-slot Backbone Chassis with FC 10 - 6 ISL Blade Fabric OS v6.2.0
TABLE 1Fabric OS-supported hardware (Continued)
Device nameTerminology used in documentationFirmware level required
Brocade DCX
Brocade DCX
Brocade DCX-4S with FC16-64 Blades4-slot Backbone Chassis with 16 Gbps 64-FC
Brocade DCX
Brocade DCX-4S
Brocade DCX-4S with FC8-16, FC8-32, and
FC8-48 Blades
Brocade DCX-4S with FC8-64 Blades4-slot Backbone Chassis with 8 Gbps 64-FC port
Brocade DCX-4S with FR4-18i Blades4-slot Backbone Chassis with 4 Gbps Router,
Brocade DCX-4S with FC10-6 Blades4-slot Backbone Chassis with FC 10 - 6 ISL Blade Fabric OS v6.2.0
Brocade DCX-4S with FS8-18 Blades4-slot Backbone Chassis with Encryption BladeFabric OS v6.1.1_enc or later
1, 2
with FS8-18 Blades8-slot Backbone Chassis with Encryption BladeFabric OS v6.1.1_enc or later
1, 2
with FX8-24 Blades8-slot Backbone Chassis with 8 Gbps 12-FC port,
Fabric OS v6.3.1_CEE
10 GbE ports, 2-10 GbE ports blade
Fabric OS v7.3.0 or later
port blades
1, 2
with FCoE10-24 Blades8-slot Backbone Chassis with 10 Gbps 24-port
Fabric OS v6.3.1_CEE
FCoE blade
4-slot Backbone ChassisFabric OS v6.0.0 or later
4-slot Backbone Chassis with 8 Gbps 16-FC port,
Fabric OS v6.2.0
8 Gbps 32-FC port, and 8 Gbps 48-FC port
blades
Fabric OS v6.4.0
blades
Fabric OS v6.2.0
Extension blade
Brocade DCX-4S with FX8-24 Blades4-slot Backbone Chassis with 8 Gbps 12-FC port,
Fabric OS v6.3.1_CEE
10 GbE ports, 2-10 GbE ports blade
Brocade DCX-4S with FCoE10-24 Blades4-slot Backbone Chassis with 10 Gbps 24-port
Fabric OS v6.3.0 or later
FCoE blade
Brocade DCX 8510-416 Gbps 4-slot Backbone ChassisFabric OS v7.0.0 or later
Brocade DCX 8510-8
1, 2
16 Gbps 8-slot Backbone ChassisFabric OS v7.0.0 or later
Brocade Encryption Switch8 Gbps Encryption SwitchFabric OS v6.1.1_enc or later
Brocade VDX 6710 switchVDX 6710 switch2.1 or later
Brocade VDX 6720-24 switchVDX 6720-24 switch2.1 or later
Brocade VDX 6720-60 switchVDX 6720-60 switch2.1 or later
xivBrocade Network Advisor Installation and Migration Guide
Tab le 3.
53-1003157-01
TABLE 3Network OS-supported hardware (Continued)
Device nameTerminology used in documentationFirmware level required
Brocade VDX 6730-32 switchVDX 6730-32 switch2.1 or later
Brocade VDX 6730-76 switchVDX 6730-76 switch2.1 or later
Brocade VDX 6740 switchVDX 6740 switch4.0 or later
Brocade VDX 6740T switchVDX 6740T switch4.0 or later
Brocade VDX 6740T-1G switchVDX 6740T-1G switch4.1 or later
Brocade VDX 8770-4 switchVDX 8770-4 switch3.0 or later
Brocade VDX 8770-8 switchVDX 8770-8 switch3.0 or later
Brocade VDX 8770 with 40G/10G Base-T by line card VDX 8770 switch with 40G/10G Base-T by line card4.1 or later
What’s new in this document
The following changes have been made since this document was last released:
• Information that was added:
-Migration rollback
• Information that was changed:
-Supported hardware and software
-Server and Client operating system requirements
-Client only installation
-Supported migration paths
• Information that was deleted:
-None.
For further information about new features and documentation updates for this release, refer to
the release notes.
Brocade Network Advisor Installation and Migration Guidexv
53-1003157-01
Document conventions
NOTE
This section describes text formatting conventions and important notice formats used in this
document.
Text formatting
The narrative-text formatting conventions that are used are as follows:
bold textIdentifies command names
italic textProvides emphasis
code textIdentifies CLI output
For readability, command names in the narrative portions of this guide are presented in mixed
lettercase: for example, switchShow. In actual examples, command lettercase is all lowercase.
Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
Identifies command syntax examples
Notes
The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.
A note provides a tip, guidance, or advice, emphasizes important information, or provides a
reference to related information.
Key terms
For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade.
See
“Brocade resources” on page xvii for instructions on accessing MyBrocade.
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at:
http://www.snia.org/education/dictionary
xviBrocade Network Advisor Installation and Migration Guide
53-1003157-01
Notice to the reader
This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
CorporationReferenced trademarks and products
Linus TorvaldsLinux
Microsoft CorporationWindows, Windows NT, Internet Explorer
Netscape Communications CorporationNetscape
Red Hat, Inc.Red Hat, Red Hat Network, Maximum RPM, Linux Undercover
OracleSun, Solaris, Sun Fire, Sun Ultra, Java Plug-in
The Open GroupUNIX
VMware, Inc.VMware
Additional information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
Brocade resources
To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user
ID and password.
White papers, online demonstrations, and data sheets are available through the Brocade website
at:
For additional Brocade documentation, visit the Brocade website:
http://www.brocade.com
Release notes are available on the MyBrocade website.
Other industry resources
For additional resource information, visit the Technical Committee T11 website. This website
provides interface standards for high-performance and mass storage applications for Fibre
Channel, storage management, and other applications:
http://www.t11.org
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association
website:
http://www.fibrechannel.org
Brocade Network Advisor Installation and Migration Guidexvii
53-1003157-01
Getting technical help
'"!&'
FT00X0054E9
Contact your switch support supplier for hardware, firmware, and software support, including
product repairs and part ordering. To expedite your call, have the following information available:
1. Management Application Serial Number
To obtain the Management application serial number, select Help > License. The License
dialog box displays.
2. General Information
• Switch model
• Switch operating system version
• Software name and software version, if applicable
• Error numbers and messages received
• supportSave command output
• Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs
• syslog message logs
3. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number label,
as illustrated below:
Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side
on the left
• Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the
switch
• Brocade 7600—On the bottom of the chassis
• Brocade 48000—Inside the chassis next to the power supply bays
• Brocade DCX—On the bottom right on the port side of the chassis
• Brocade DCX-4S—On the bottom right on the port side of the chassis, directly above the
cable management comb
xviiiBrocade Network Advisor Installation and Migration Guide
53-1003157-01
4. World Wide Name (WWN)
Use the licenseIdShow command to display the WWN of the chassis.
If you cannot use the licenseIdShow command because the switch is inoperable, you can get
the WWN from the same place as the serial number, except for the Brocade DCX. For the
Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo plate at
the top of the nonport side of the chassis.
Document feedback
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a
topic needs further development, we want to hear from you. Forward your feedback to:
documentation@brocade.com
Provide the title and version number of the document and as much detail as possible about your
comment, including the topic heading and page number and your suggestions for improvement.
Brocade Network Advisor Installation and Migration Guidexix
53-1003157-01
xxBrocade Network Advisor Installation and Migration Guide
Brocade Network Advisor Installation and Migration Guide1
53-1003157-01
System requirements
NOTE
NOTE
1
Server and client operating system requirements
Tab le 4 summarizes the required operating system (OS) for servers and the packages supported by
each OS version.
Enterprise edition (SAN or IP) and Professional Plus edition (SAN or IP) are not supported on 32-bit
operating systems. You must migrate to a 64-bit operating system.
SAN with SMI Agent + IP edition is not supported on 32-bit operating systems.
TABLE 4Server operating system requirements
Operating
system
Windows
VersionGuest OS versionSupported packages
®
- 2008 Server (x86 32-bit)
- 7 Enterprise (x86 32-bit)
- 2008 Server (x86 64-bit)
SAN with SMI Agent
IP only
SMI Agent only
- 7 Enterprise (x86 64-bit)
- 2008 R2 Data Center Edition (x86 32-bit)
- 2008 R2 Standard Edition (x86 32-bit)
- 2008 R2 Enterprise Edition (x86 32-bit)
- 2012 R2 Data Center Edition (x86 32-bit)
SAN with SMI Agent
IP only
SMI Agent only
SAN with SMI Agent + IP
- 2012 R2 Standard Edition (x86 32-bit)
- 7 Enterprise (x86 32-bit)
- 8 Enterprise (x86 32-bit)
- 8.1 Enterprise (x86 32-bit)
- 2008 R2 Data Center Edition (x86 64-bit)
- 2008 R2 Standard Edition (x86 64-bit)
- 2008 R2 Enterprise Edition (x86 64-bit)
- 2012 R2 Data Center Edition (x86 64-bit)
SAN with SMI Agent
IP only
SMI Agent only
SAN with SMI Agent + IP
- 2012 R2 Standard Edition (x86 64-bit)
- 7 Enterprise (x86 64-bit)
- 8 Enterprise (x86 64-bit)
- 8.1 Enterprise (x86 64-bit)
2Brocade Network Advisor Installation and Migration Guide
53-1003157-01
TABLE 4Server operating system requirements (Continued)
Operating
system
Linux
VersionGuest OS versionSupported packages
®
- RedHat Enterprise 6.1 Advanced (x86 32-bit)
- RedHat Enterprise 6.2 Advanced (x86 32-bit)
- RedHat Enterprise 6.3 Advanced (x86 32-bit)
- RedHat Enterprise 6.4 Advanced (x86 32-bit)
- RedHat Enterprise 6.5 Advanced (x86 32-bit)
- SuSE Enterprise Server 11 (x86 32-bit)
- SuSE Enterprise Server 11.3 (x86 32-bit)
- Oracle Enterprise 6.1 (x86 32-bit)
- Oracle Enterprise 6.2 (x86 32-bit)
- Oracle Enterprise 6.3 (x86 32-bit)
- Oracle Enterprise 6.4 (x86 32-bit)
- Oracle Enterprise 6.5 (x86 32-bit)
- RedHat Enterprise 6.1 Advanced (x86 64-bit)
- RedHat Enterprise 6.2 Advanced (x86 64-bit)
- RedHat Enterprise 6.3 Advanced (x86 64-bit)
- RedHat Enterprise 6.4 Advanced (x86 64-bit)
- RedHat Enterprise 6.5 Advanced (x86 64-bit)
- SuSE Enterprise Server 11.3 (x86 64-bit)
- Oracle Enterprise 6.1 (x86 64-bit)
- Oracle Enterprise 6.2 (x86 64-bit)
- Oracle Enterprise 6.3 (x86 64-bit)
- Oracle Enterprise 6.4 (x86 64-bit)
- Oracle Enterprise 6.5 (x86 64-bit)
Guest VMs - VMware® ESX Server i 5.1
1
- VMware ESX Server i 5.5
- Microsoft Hyper-V (Hyper-V Server 2008 R2 SP1)
- KVM RH 6.5
System requirements
Supports all server
OS versions
available for
Windows and
Linux.
1
SAN with SMI Agent
IP only
SMI Agent only
SAN with SMI Agent
IP only
SMI Agent only
SAN with SMI Agent + IP
Supports all packages
available for Windows
and Linux.
1.It is recommended that you run all Network Advisor virtual CPUs on a single physical CPU.
Brocade Network Advisor Installation and Migration Guide3
53-1003157-01
System requirements
1
Tab le 5 summarizes the required OS for clients.
TABLE 5Client operating system requirements
Operating
system
VersionGuest OS version
Windows
®
®
Linux
Guest
VMs
- 2008 Server (x86 32-bit)
- 7 Enterprise (x86 32-bit)
- 2008 Server (x86 64-bit)
- 7 Enterprise (x86 64-bit)
- 2008 R2 Data Center Edition (x86 32-bit)
- 2008 R2 Standard Edition (x86 32-bit)
- 2008 R2 Enterprise Edition (x86 32-bit)
- 2012 R2 Data Center Edition (x86 32-bit)
- 2012 R2 Standard Edition (x86 32-bit)
- 7 Enterprise (x86 32-bit)
- 8 Enterprise (x86 32-bit)
- 8.1 Enterprise (x86 32-bit)
- 2008 R2 Data Center Edition (x86 64-bit)
- 2008 R2 Standard Edition (x86 64-bit)
- 2008 R2 Enterprise Edition (x86 64-bit)
- 2012 R2 Data Center Edition (x86 64-bit)
- 2012 R2 Standard Edition (x86 64-bit)
- 7 Enterprise (x86 64-bit)
- 8 Enterprise (x86 64-bit)
- 8.1 Enterprise (x86 64-bit)
- RedHat Enterprise 6.1 Advanced (x86 32-bit)
- RedHat Enterprise 6.2 Advanced (x86 32-bit)
- RedHat Enterprise 6.3 Advanced (x86 32-bit)
- RedHat Enterprise 6.4 Advanced (x86 32-bit)
- RedHat Enterprise 6.5 Advanced (x86 32-bit)
- SuSE Enterprise Server 11 (x86 32-bit)
- SuSE Enterprise Server 11.3 (x86 32-bit
- Oracle Enterprise 6.1 (x86 32-bit)
- Oracle Enterprise 6.2 (x86 32-bit)
- Oracle Enterprise 6.3 (x86 32-bit)
- Oracle Enterprise 6.4 (x86 32-bit)
- Oracle Enterprise 6.5 (x86 64-bit)
- RedHat Enterprise 6.1 Advanced (x86 64-bit)
- RedHat Enterprise 6.2 Advanced (x86 64-bit)
- RedHat Enterprise 6.3 Advanced (x86 64-bit)
- RedHat Enterprise 6.4 Advanced (x86 64-bit)
- RedHat Enterprise 6.5 Advanced (x86 64-bit)
- Oracle Enterprise 6.1 (x86 64-bit)
- Oracle Enterprise 6.2 (x86 64-bit)
- Oracle Enterprise 6.3 (x86 64-bit)
- Oracle Enterprise 6.4 (x86 64-bit)
- Oracle Enterprise 6.5 (x86 64-bit)
- VMware
®
ESX Server i 5.1
- VMware ESX Server i 5.5
- Microsoft Hyper-V (Hyper-V Server 2008 R2 SP1)
- KVM RH 6.5
Supports all client OS versions available for
Windows and Linux.
4Brocade Network Advisor Installation and Migration Guide
53-1003157-01
System requirements
NOTE
NOTE
NOTE
NOTE
1
Memory requirements
Memory requirements are only applicable when no other applications are running on the Network
Advisor server. Paging space should be equal to or exceed the physical memory size. Network
Advisor servers for Enterprise and Professional Plus editions are only supported on 64-bit systems.
Network Advisor clients are supported on 32-bit and 64-bit Windows and Linux systems.
Operating system cache requirements
It is recommended that you use the System managed size (the OS allocates the required cache);
however, if you choose to use a custom size, make sure you use the following memory settings for
your operating system.
The virtual memory requirements for Windows system is 1 GB for minimum paging file size and 4
GB for maximum paging file size
TABLE 6Linux swap space requirements
Installed physical memory
(RAM) size
Recommended swap size
4 GB4 GB
Greater than 4 GB and
less than 8 GB
Greater than or equal to
8 GB and less than 64
GB
It is recommended that the memory allocation for ports exceeding 9000 is 6GB.
Equal to the amount of RAM
5 time the amount of RAM
Disk space requirements
The disk space required for your device is a minimum of 10 GB.
A warning message will be displayed if a minimum of 10 GB space is not available.
It is recommended that you add an additional 100 GB of disk space if you use sFlow.
It is recommended that you add an additional 40 GB of disk space for the default temporary
directory.
Brocade Network Advisor Installation and Migration Guide5
53-1003157-01
System requirements
NOTE
NOTE
NOTE
NOTE
1
It is recommended that you add an additional 100 GB of disk space if you use sFlow.
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.
Tab le 7 summarizes the host, memory and disk space requirements for remote client.
TABLE 7Host, Memory, and Disk space requirements for remote client
ResourcesRequired
RAM4 GB
Processor Core
Disk space
2 core CPU
1 GB
Tab le 8 summarizes the minimum system requirements for installation.
TABLE 8Minimum system requirements for installation
ResourcesProfessional EditionEnterprise Edition
RAM4 GB(32-bit) 6GB (64 bit)6 GB
Processor Core (including
physical and logical core)
Disk space10 GB20 GB
2 core2 core
Tab le 9 summarizes the recommended system requirements for installation.
TABLE 9Recommended system requirements for installation
ResourcesSmallMediumLarge
RAM16 GB16 GB16 GB
Processor Core (including
physical and logical core)
Disk space20 GB80 GB100 GB
2 core4 core8 core
You must have 16 core processor when managing 9000 SAN ports or above.
It is recommended to allocate a minimum of 2 GB client memory and 6 GB server memory to
efficiently manage more than 9000 ports.
6Brocade Network Advisor Installation and Migration Guide
53-1003157-01
System requirements
NOTE
NOTE
NOTE
NOTE
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 11
-Firefox 27 on Windows or Linux
-Google Chrome 33
• Java Plug-ins
-Oracle JRE 1.7.0 update 60 for Network Advisor
-Oracle JRE 1.7.0 update 60 for Web Tools
For higher performance, use a 64-bit JRE.
A warning message will be displayed if the required operating system is not available.
1
If the minimum system requirement is not met, you will be blocked from the configuration and
an error message will be displayed.
For the website listing patch information, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Client and server system requirements
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 editions, a single server supports a maximum of 25 clients,
which can be local or remote on 32-bit and 64-bit servers.
• In Professional Plus and Enterprise editions, a single server supports a maximum of 25 clients,
which can be local or remote on 64-bit servers. To suppor t more than 8 clients, you must make
the following changes to your configuration:
-Increase the server memory size. You can configure the server memory size from the
Options dialog box, Memory Allocations pane. For instructions, refer to the Network Advisor User Manual or online help.
-Increase the PostgreSQL database shared buffers memory allocation to 1024 MB by
editing the Install_Home\data\databases\postgresql.conf file.
Brocade Network Advisor Installation and Migration Guide7
53-1003157-01
Downloading the software
1
Downloading the software
You can download the software and documentation from the MyBrocade website.
1. Go to the MyBrocade website.
http://my.brocade.com/
2. Enter your user ID and password.
If you do not already have a MyBrocade account, you can create one.
3. Select MyBrocade from the Take me to list, if necessary.
4. Click LOG IN.
5. Click downloads on the main page.
6. Select Management Software from the Download by list.
7.C l i c k Brocade Network Advisor in the Product Name list.
8. Select the highest version number for the latest GA code.
For example, click Brocade Network Advisor 12.3.x, then click Brocade Network Advisor 12.3.0
Brocade GA.
To download the documentation, click Brocade Network Advisor 12.3.0 Manuals and then
select the manual you want to download.
9. Select one of the following links to download the software:
• Network Advisor 12.3.0 GA for Windows
• Network Advisor 12.3.0 GA for Linux
You can also access the release notes and md5 Checksum from this location.
10. Read the Export Compliance, select the certification check box, and click Submit.
11. Read the Brocade End User License Agreement and click I Accept.
12. Click Save on the File Download dialog box.
13. Browse to the location where you want to save the software and click Save.
Pre-installation requirements
Before you install Network Advisor, make sure you meet the following requirements.
• Make sure all system requirements have been met prior to installation. For specific system
requirements, refer to
If you are running Professional Plus or Enterprise edition on a 32-bit machine, you must
migrate to a 64-bit machine within your current release, then you can migrate to Network
Advisor 12.3.
“System requirements” on page 1.
If you are running SAN with SMI Agent + IP on a 32-bit machine, you must migrate to a 64-bit
machine within your current release, then you can migrate to Network Advisor 12.3.
• To avoid errors, close all instances of the application before beginning the installation or
uninstallation procedures.
8Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Installing the application
NOTE
NOTE
For UNIX system, 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
1
Additional pre-installation requirements for UNIX systems
• 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 “Additional pre-installation requirements for
UNIX systems (headless installation)” on page 12.
• 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.
• For Linux OS with the SELinux security policy enabled, make sure you complete the following
steps.
1. Disable the SELinux security policy using the setenforce 0 command.
2. Install the application (refer to “Installing the application” on page 9).
3. Enable the SELinux security policy using the setenforce 1 command.
Installing the application
Before you install the application, make sure your system meets the minimum pre-installation
requirements (refer to
“Data Migration” on page 39.
SAN with SMI Agent + IP is not supported on 32-bit Windows systems. For more information, refer to
“Pre-migration requirements” on page 44.
“Pre-installation requirements” on page 8). If you are migrating data, refer to
On Windows systems, you must be an Administrator with Read and Write privileges to install Network
Advisor.
Brocade Network Advisor Installation and Migration Guide9
53-1003157-01
Installing the application
NOTE
NOTE
NOTE
1
On UNIX systems, you must be the root user to install Network Advisor.
To install the new application version, complete the following steps.
On Linux systems, if you double-click the install.bin file, select Run. Do not select Run in
Term inal.
The following are the list of folder permission in Linux:
• BNA_HOME - 775
• Conf/schema folder(including sub-folders) - 775
• Conf folder - 775
• Data folder - 775
• Database folder - 700
• DB folder (including sub folder) - 775
• Temp folder -775
• support folder - 777
• Other folders -774
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.
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.
10Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Installing the application
6. Make sure the Launch Configuration check box is selected (default) on the Installation
Complete screen, and click Done.
If the localhost is not mapped to the loopback address, an error message displays. You must
map the loopback address to the localhost (refer to
local host” on page 11) before you configure the application.
If the localhost is mapped to the loopback address, the configuration wizard displays. To
configure the application, refer to one of the following sections:
“Mapping the loopback address to the
• If this is a fresh installation, refer to “Network Advisor Configuration” on page 15.
• If you are upgrading from a previous version and need to migrate data, refer to “Data
Migration” on page 39.
Mapping the loopback address to the local host
To map the loopback address to the local host, complete the following steps.
1. Open the hosts file.
For Windows, the hosts file is located in the WINDOWS\system32\drivers\etc directory.
For Linux, the hosts file is located in the /etc directory
1
2. Add the following entries:
# For IPV4 machine
127.0.0.1 localhost
# For IPV6 enabled machine
127.0.0.1 localhost
::1 localhost
3. Save and close the file.
To configure the application, refer to one of the following sections:
• If this is a fresh installation, refer to “Network Advisor Configuration” on page 15.
• If you are upgrading from a previous version and need to migrate data, refer to “Data
Migration” on page 39.
Brocade Network Advisor Installation and Migration Guide11
53-1003157-01
Headless installation
1
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.
Before you install Network Advisor, make sure you meet the following requirements.
Make sure all system requirements have been met prior to installation. For specific system
requirements, refer to
Additional pre-installation requirements for UNIX systems
(headless installation)
An X Server display is required, even when performing a headless installation, to run the initial
configuration. Before you install Network Advisor, complete the following:
• 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 system console be present and running with a logged-in
user on the X Server-based desktop session, such as KDE, GNOME, and so on).
The DISPLAY can be any host X Server (for example, DISPLAY can be set to display the
configuration to another UNIX system that has an X-based desktop).
“System requirements” on page 1.
• 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).
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, on
a local terminal window of the X-based desktop of the remote system.
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.
• 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.
12Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Headless installation
1
Performing a headless installation on Windows
and UNIX systems
To perform a headless installation through the CLI, download the software (refer to “Downloading
the software” on page 8).
• For Windows systems, open a Command Prompt and execute this command:
• For UNIX systems, open a UNIX shell and execute this command: sh install.bin -i silent
-DUSER_INSTALL_DIR="/opt/Network_Advisor12_3_X"
-DHEADLESS_CONFIG_MODE="false”
The application installs in silent mode using default settings.
To configure the application, refer to one of the following sections:
• If this is a fresh installation, refer to “Network Advisor Configuration” on page 15.
• If you are upgrading from a previous version and need to migrate data, refer to “Data
Migration” on page 39.
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).
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 and Migration Guide13
53-1003157-01
Client-only installation
NOTE
NOTE
NOTE
NOTE
NOTE
NOTE
1
Client-only installation
You can install a client-only application on a machine other than the server (without using a web
browser) by creating a client bundle on the server, and then copying and installing that client on
another machine.
Installing the client-only application
You can download the client bundle only when browser operating system and server operating
system is same. Client Bundle support only 64-bit OS.
Client bundle must be triggered manually if you modify the data in the Option dialog box.
Download client is bundled with BNA server java runtime environment package.
1. Click the client bundle and download the file.
2. Extract the client bundle.
3. Navigate to the extract_location\bin directory (for example,
C:\Users\user_name\desktop\Network Advisor-client\bin) and run
windows and dcmclient for linux or (BNA_HOME\bin) and run
windows and for linux
The Network Advisor Log In dialog box is displayed.
4. Enter the IP address of the Network Advisor server in the Network Address list.
The server must be the exact same version, edition, starting port number, and network size as
the client.
You can remove a server from the Network Address list by selecting the IP address and clicking
Delete.
5. Enter your user name and password.
The defaults are Administrator and password, respectively.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
create-client-bundle.
dcmclient.bat for
create-client-bundle.bat for
6. 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.
7.C l i c k Login.
8. Click OK on the Login Banner dialog box.
The Network Advisor application displays.
14Brocade Network Advisor Installation and Migration Guide
If you have not installed the application, refer to “Installation” on page 1. If you are migrating data,
refer to “Data Migration” on page 39.
To configure Network Advisor, complete the following steps.
1. Click Next on the Welcome screen.
2. Click No, don’t any copy data and settings (default) on the Copy Data and Settings (Migration)
screen and click Next.
You cannot migrate data from an earlier release of Network Advisor to 12.3.x after you
complete the 12.3.x configuration.
To migrate data from a previous management application version, refer to “Data Migration” on
page 39.
Brocade Network Advisor Installation and Migration Guide15
53-1003157-01
Configuring Network Advisor
NOTE
NOTE
NOTE
ATTENTION
NOTE
2
3. Select one of the following options on the Package screen and click Next.
4. Select one of the following options on the Installation Type screen and click Next.
• SAN with SMI Agent
• IP
• SAN with SMI Agent + IP (default)
• SMI Agent Only (Go to step 8.)
SMI Agent is not supported in a Professional edition configuration.
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 downgrade your license and restart all services for the changes to take
affect. For instructions, refer to the user manual or online help.
The DCX and DCX 8510-8 Backbone chassis require the Enterprise edition.
• Network Advisor - Licensed version (default)
Continue with step 5. Requires you to enter a license key during configuration to enable
features and configuration.
• Network Advisor - 120 days Trial
Go to step 6. Enables you to manage IP, SAN, or SAN and IP networks from a single
interface for 120 days.
If you choose to install Trial, once the trial period ends (120 days), you must upgrade to
Licensed software.
• Network Advisor - Professional
Go to step 6. Bundled with Fabric OS and IronWare OS devices to manage small IP, SAN, or
SAN and IP networks from a single interface.
5. (Licensed software only) If you are installing licensed software, browse to the license file (.xml)
and click Next on the Server License screen.
You can also copy (Ctrl+c) and paste (Ctrl+v) the license key in to the License Key field. The
License Key field is not case-sensitive.
If you use the SAN with SMI Agent +IP Enterprise license key, Event-based collection for IP
discovery will be turned off.
If you use 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
16Brocade Network Advisor Installation and Migration Guide
step 6.
53-1003157-01
Configuring Network Advisor
NOTE
6. Complete the following steps on the FTP/SCP/SFTP Server screen.
a. Choose one of the following options:
• Select Built-in FTP/SCP/SFTP Server (default) to configure an internal FTP/SCP/SFTP
server and select one of the following options:
-Select Built-in FTP Server to configure an internal FTP server
This is the default option. 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 Built-in SCP/SFTP Server to configure an internal SCP/SFTP server
The internal SCP/SFTP server uses a default account and port 22. 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/SCP/SFTP Server to configure an external 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.
b. Click Next.
If port 21 or 22 is busy, a message displays. Click OK to close the message and continue. Once
the Management application is configured make sure port 21 or 22 is free and restart the
Server to start the FTP/SCP/SFTP service.
2
If you use an FTP/SCP/SFTP server that is not configured on the same machine as the
Management application, the Firmware Repository feature will not be available.
You can configure the FTP/SCP/SFTP server settings from the Options dialog box. For
instructions, refer to the Network Advisor User Manual or online help.
7. Configure the database password on the Database Administrator Password (dcmadmin)
screen by completing the following steps.
a. Choose one of the following options:
• To use the default password, select Default password.
This is the default option. The default is password.
• To configure a new password, select New password and enter a new password in the
Password and Confirm Password fields.
The password must be between 8 and 15 alphanumeric characters. Special
characters except single quote (‘) are allowed.
b. Click Next.
Brocade Network Advisor Installation and Migration Guide17
53-1003157-01
Configuring Network Advisor
NOTE
NOTE
NOTE
NOTE
2
8. Complete the following steps on the Server IP Configuration screen.
If the Management server or client has multiple Network Interface Cards and if any of these
interfaces are not plugged in, you must disable them; otherwise, the following features do not
work properly:
Server impact
• Configuration wizard (does not display all IP addresses)
• Trap and Syslog auto registration
• Report content (Ipconfiguration element does not display all server IP addresses)
• Network OS configuration backup through FTP
• Tra ce dum p through F TP
Client impact
• Options dialog box (does not display all IP addresses)
• Firmware import and download dialog box
• Firmware import for Fabric OS and Network OS products
• FTP button in Technical Support Repository dialog box
• Technical supportSave of Fabric OS, Network OS, and Host products through FTP
a. Select an address from the Server IP Configuration list.
For Professional software, the Server IP Configuration address is set to “localhost” by
default. You cannot change this address.
For SMI Agent, 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.
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 the 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
after configuration, refer to
“Configuring an explicit server IP address” on page 34.
c.Click Next.
18Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Configuring Network Advisor
NOTE
NOTE
NOTE
NOTE
9. Complete the following steps on the Server Configuration screen (Figure 1).
FIGURE 1Server Configuration screen
a. Enter a port number in the Web Server Port # (HTTPS) field (default is 443).
b. Enable HTTP redirection to HTTPS by selecting the Redirect HTTP Requests to HTTPS
check box.
When you enable HTTP redirection, the server uses port 80 to redirect HTTP requests to
HTTPS. You can configure the server port settings from the Options dialog box (Server Port
pane). For instructions, refer to the Network Advisor User Manual or online help.
2
c.Enter a port number in the Database Port # field (default is 5432).
Do not use a port number below 1024.
d. Enter a port number in the Starting Port Number field (default is 24600).
For Professional software, the server requires 15 consecutive free ports beginning with
the starting port number.
For Trial and Licensed software, the server requires 18 consecutive free ports beginning
with the starting port number.
e. Enter a port number in the Syslog Port Number field (default is 514).
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 25.
Brocade Network Advisor Installation and Migration Guide19
53-1003157-01
Configuring Network Advisor
NOTE
NOTE
NOTE
2
10. (SAN with SMI Agent + IP or SAN with SMI Agent) Complete the following steps on the SMI
f.Enter a port number in the SNMP Port Number field (default is 162).
g. Enter a port number in the TFTP Port Number field (default is 69).
h. Click Next.
If you enter a syslog port number already in use, a 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.
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.
If you are configuring Professional software, go to step 13.
If you are configuring IP Enterprise, go to step 12.
Agent Configuration screen.
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.
11. (SAN Enterprise or SMI Agent) Select one of the following options on the SAN Network Size
screen and click Next:
Port count is equal to the total number of switch ports across all fabrics.
SAN with SMI Agent + IP edition is not supported on a 32-bit Windows system.
• Small (managing up to 2000 switch ports, 1-20 domains)
• Medium (managing up to 5000 switch ports, 21-60 domains)
• Large (managing up to 15000 switch ports, 61-120 domains)
For full performance and dashboard functionality, the Large option of the SAN Enterprise
edition only supports 5000 switch ports on a 32-bit system.
If you are configuring IP Enterprise, continue with step 12; otherwise, go to step 13.
20Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Configuring Network Advisor
NOTE
NOTE
NOTE
12. (IP Enterprise) Select one of the following options on the IP Network Size screen and click Next:
Port count is equal to the total number of all managed product ports.
SAN with SMI Agent + IP edition is not supported on a 32-bit Windows system.
2
• Small (managing up to 1-20 products)
• Medium (managing up to 21-200 products)
• Large (managing up to 201-5050 products)
13. Enable feature usage data transfer from the application by selecting the Yes, I want to
participate option.
If you do not want to participate in feature usage data transfer, make sure the No, Thank You
option is selected. You can stop participating at any time. To view an example of the usage
data, click View Example Data.
To stop participating in feature usage data transfer after configuration, refer to “Product
improvement” on page 35.
14. Verify your configuration information on the Server Configuration Summary screen and click
Next.
15. Complete the following steps on the Start Server screen.
a. (Trial and Licensed only) Select the Start SMI Agent check box, if necessary.
Only enabled if you enabled SMI Agent on the SMI Agent Configuration screen.
b. (Trial and Licensed only) 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.
Only displays if you selected SAN with SMI Agent + IP or SAN with SMI Agent on the
Package screen.
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 (refer to
“Configuring an explicit server IP address” on page 34).
16. Enter your user name and password.
The defaults are Administrator and password, respectively.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
17. Cli ck Login.
18. Click OK on the Network Advisor Login Banner.
Brocade Network Advisor Installation and Migration Guide21
53-1003157-01
Accessing the Network Advisor interfaces
NOTE
NOTE
NOTE
NOTE
2
Accessing the Network Advisor interfaces
Use the following procedures to access Network Advisor from the server and client as well as to
access the Server Management Console and the SMI Agent Configuration Tool.
Logging into a server
You must log into a server to monitor your network.
You must have an established user account on the server to log in.
1. Double-click the desktop icon or open the application from the Start menu.
The Log In dialog box displays.
2. Log into another server by entering the IP address to the other server in the Network Address
field.
The server must be the exact same version, edition, starting port number, and network size as
the client.
You can remove a server from the Network Address list by selecting the IP address and clicking
Delete.
3. Enter your user name and password.
The defaults are Administrator and password, respectively.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
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 Login Banner dialog box.
The Network Advisor application displays.
22Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Accessing the Network Advisor interfaces
NOTE
NOTE
NOTE
NOTE
2
Launching a remote client
The remote client requires Oracle JRE 1.7.0_60. For the website listing patch information, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
For higher performance, use a 64-bit JRE.
1. Open a web browser and enter the IP address of the Network Advisor server in the Address bar.
If the web server port number does not use the default, you must enter the web server port
number in addition to the IP address; for example, IP_Address:Port_Number.
The default port number for the Network Advisor web server is 443 if SSL is enabled;
otherwise, the default is 80.
The Network Advisor web start screen displays.
2. Click the Network Advisor web start link.
The Log In dialog box displays.
3. Log into another server by entering the IP address to the other server in the Network Address
field.
The server must be the exact same version, edition, starting port number, and network size as
the client.
You can r emove a s erver from the Network Address list by selected the IP address and clicking
Delete.
4. Enter your user name and password.
The defaults are Administrator and password, respectively.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
5. 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.
6. Click Login.
7.C l i c k OK on the Login Banner dialog box.
The Network Advisor application displays.
Brocade Network Advisor Installation and Migration Guide23
53-1003157-01
Accessing the Network Advisor interfaces
NOTE
2
Launching the SMC on Windows
Open the Server Management Console from the Start menu on the Network Advisor server.
You can also drag the SMC icon onto your desktop as a short cut.
Launching the SMC on Linux
The Server Management Console is a graphical user interface and should be launched from the
XConsole on Linux systems.
Double-click the SMC icon on your desktop.
OR
1. On the Network Advisor server, go to the following directory:
Install_Directory/bin
2. Type the following at the command line:
./smc
OR
sh smc
Launching the SMIA Configuration Tool
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.
The defaults are Administrator and password, respectively.
4. Click Login.
Launching the SMIA Configuration Tool remote client
The remote client requires Oracle JRE 1.7.0_60. For the website listing patch information, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
1. Open a web browser and enter the IP address of the Network Advisor server in the Address bar.
If the web server port number does not use the default, you must enter the web server port
number in addition to the IP address; for example, IP_Address:Port_Number.
The default port number for the Network Advisor web server is 443 if SSL is enabled;
otherwise, the default is 80.
The Network Advisor web start screen displays.
2. Click the SMIA Configuration Tool web start link.
The SMIA Configuration Tool Log In dialog box displays.
24Brocade Network Advisor Installation and Migration Guide
53-1003157-01
3. Enter your user name and password.
The defaults are Administrator and password, respectively.
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.
The SMIA Configuration Tool displays.
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.
Finding the process
1. Open a command window.
Syslog troubleshooting
2
2. Choose one of the following options:
• On Linux systems, 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.
• On Windows systems, 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
Choose one of the following options:
• On Linux systems, type kill -9 “ProcessID”, where ProcessID is the ID of the process you
want to stop, and press Enter.
For example, kill -9 “27397”.
• On Windows systems, type taskkill /F /PID “ProcessID”, where ProcessID is the ID of
the process you want to stop, 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.
Brocade Network Advisor Installation and Migration Guide25
53-1003157-01
Installing the ODBC driver
NOTE
2
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.
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.
Adding the data source on Windows systems
1. To add the data source, complete the following steps. Choose one of the following options:
• (32-bit OS) Select Start > Settings > Control Panel > Administrative Tools > Data Sources
The ODBC Data Source Administrator dialog box displays.
2. Click the System DSN tab.
3. Click Add.
The Create a New Data Source dialog box displays.
4. Select PostgreSQL Unicode.
5. Click Finish.
The PostgreSQL Unicode ODBC Driver (psqlODBC) Setup dialog box displays.
6. Enter a name for the data source in the Datasource field.
7. Enter the description of the Network Advisor database in the Description field.
8. Enter the name of the Network Advisor database in the Database field.
9. Select enable or disable from the SSL Mode list to specify whether or not to use SSL when
connecting to the database.
26Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Installing the ODBC driver
NOTE
NOTE
10. Enter the IP address or host name of the Network Advisor server in the Server field.
11. Enter the database server port number in the Port Number field.
12. Enter the database user name in the User Name field.
13. Enter the password in the Password field.
14. Click Test to test the connection.
You can also use the Windows ODBC Driver Manager to add the DSN for the Linux database
server.
15. Click OK on the Connection Test dialog box.
16. Click Save.
17. Cli ck OK on the ODBC Data Source Administrator dialog box.
2
Installing the ODBC driver on 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
For 32-bit Linux systems, the installer file is located in DVD/BROCADE/Network
Advisor/odbc/Linux/ edb_psqlodbc.bin.
For 64-bit Linux systems, the installer file is located in DVD/BROCADE/Network
Advisor/odbc/Linux_64/ 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.
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.
Brocade Network Advisor Installation and Migration Guide27
53-1003157-01
Installing the ODBC driver
NOTE
2
Adding the datasource on Linux systems
Before you edit the INI files, install Network Advisor (refer to “Installation” on page 1) and make
sure the PostgreSQL database is up and running.
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:
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 driver path is not updated, add the following:
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.
28Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Installing the ODBC driver
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.
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.
For 32-bit Linux systems, 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.
For 64-bit Linux systems, if an error message (cannot open library) displays, complete the
following steps:
2. Navigate to the Postgres ODBC library (default location is
opt/PostgreSQL/psqlODBC/lib/).
3. Create a list of missing libraries by executing the following command:
ldd psqlodbcw.so
Missing files display as: libodbc.so.1=> not found
4. Find shared libraries with the same name as the missing library by executing the
following command:
find –name libodbc.so*
5. Create a soft link for libodbc.so.1 pointing to libodbc.so.2.0.0 by executing the
following command:
ln -s libodbc.so.1 libodbc.so.2.0.0
f.Click Next.
6. On the Save and proceed screen, click Finish.
Brocade Network Advisor Installation and Migration Guide29
53-1003157-01
Smart Card driver installation
2
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.
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
> cd <new_dir>
> vi pcscctl
Search for “/opt” and change it to the name of the new directory.
step 1.
30Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Smart Card driver installation
NOTE
NOTE
2
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.
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.
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 32.
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 and Migration Guide31
53-1003157-01
Smart Card driver installation
NOTE
2
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 30.
2. Run the following commands to support remote clients (Web Start).
> cd /usr/lib
> ln –s /opt/pcsc/lib/libpcsclite.so .
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.
-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:
32Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Smart Card driver installation
2
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.
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.
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 and Migration Guide33
53-1003157-01
Configuring an explicit server IP address
NOTE
NOTE
2
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 12.3.0 > 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.
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 Server Name 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.
11. Enter your user name and password and click Login.
The defaults are Administrator and password, respectively.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
12. Click OK on the Login Banner.
34Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Product improvement
To improve its products, Brocade is collecting usage statistics from the field. If you agree to
participate in the program, the Network Advisor server will transmit data back to the secure
Brocade web server (HTTPS). The Brocade web server is hosted in a Brocade network.
Brocade collects the following usage data:
• Installation details
-The version information (such as Major, M ino r, Revision, and Patch)
-The Edition (such as Enterprise, Professional Plus, or Professional)
-The Package (such as SAN, IP, or SAN + IP)
-Whether SSL is enabled or not
-Generates a unique identifier based on the MAC address
-The operating system (such as Windows or Linux)
• User actions
-Top l eve l menu a ction s
-Tool bar actions
-Right-click menu actions
• Feature details
-Feature name
-Button identifier (such as OK, Help, or Cancel, and so on)
Product improvement
2
Enabling product improvement data transfer
You can enable feature usage data transfer during installation or migration. For more information,
refer to
once your system is up and running.
To enable feature usage data transfer from the application, complete the following steps.
1. Select Server > Options.
2. Select Product Improvement in the Category list.
3. Select the Yes, I want to participate option.
4. Click OK to save your selection and close the Options dialog box.
“Installation” on page 1. You can also enable data transfer from the Options dialog box
The Options dialog box displays.
To view an example of the usage data, click View Example Data.
Brocade Network Advisor Installation and Migration Guide35
53-1003157-01
Product improvement
NOTE
2
Disabling product improvement data transfer
You can disable feature usage data transfer from the Options dialog box once your system is up
and running.
To disable feature usage data transfer from the application, complete the following steps.
1. Select Server > Options.
The Options dialog box displays.
2. Select Product Improvement in the Category list.
3. Select the No, thank you option.
4. Click OK to save your selection and close the Options dialog box.
Data transfer
If you agree to participate in the program, these are the actions that occur on the client and server.
1. You log in to the Network Advisor client.
The main window displays.
2. The application automatically schedules a timer.
The timer is configured with an initial delay of 5 minutes and an interval of 24 hours.
3. Once scheduled, the client triggers the scheduled data transfer.
4. The client checks the reachability of the Brocade web server for the data transfer to make sure
that the client workstation has HTTP connectivity.
If the Brocade web server is reachable, the client schedules the timer.
5. The client triggers the schedule to run in 5 minutes and then every 24 hours thereafter.
6. When the scheduled timer runs, the client requests the server to transfer the usage data.
7. The server determines the availability of the data based on the following details:
• Last transfer timestamp must be greater than 24 hours to avoid frequent data uploads.
• Data must be available for transfer. Data availability is determined by the difference
between the last data transfer and the current data.
8. The client requests a data transfer.
If data is available, the server nominates the client to transfer data. Once nominated, any
further upload requests are denied.
If the nominated client’s session is ended or stuck, the session is invalidated and the state is
cleared.
9. The nominated client requests the server to prepare the data.
10. The server compiles the usage data text file into a .zip file using the following naming
convention: UUID_usagedata_file_creataion_timestamp, where UUID is the unique
identification of the server based on the MAC address.
36Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Configuring remote client access to the database
11. When the file is successfully created, the client changes the state of the data transfer to
“Uploading” and transmits the data.
The client transmits the data securely to the Brocade web server using the Apache HTTP
Components third-party library. The client communicates with the Brocade web server using an
authorization token.
12. When the transfer is complete, the client updates the Brocade web server database with the
transfer status (success or failure). The client also triggers an application event with the
following details: success or failure, source client IP address, and source user name.
Configuring remote client access to the database
1. Open the pg_hba.conf file (in the Install_Home\data\databases\ directory).
2. To allow all IPv4 remote connections for all users, search for the following text and uncomment
the second line:
# IPv4 remote connections (Uncomment below line to allow all IPv4 remote
users):
#host all all 0.0.0.0/0 md5
2
3. To allow all IPv6 remote connections for all users, search for the following text and uncomment
the second line:
# IPv6 remote connections (Uncomment below line to allow all IPv6 remote
users):
#host all all ::0/0 md5
4. To allow access to a specific IPv4 address, search for the following text and uncomment the
second line:
# Uncomment below line and provide IPV4 address to allow specific IPv4 remote
user
#host all all <IPV4 address>/32 md5
5. To allow access to a specific IPv6 address, search for the following text and uncomment the
second line:
# Uncomment below line and provide IPV6 address to allow specific IPv6 remote
user
#host all all <IPV6 address>/128 md5
6. Save and close the file.
Brocade Network Advisor Installation and Migration Guide37
53-1003157-01
Configuring remote client access to the database
2
38Brocade Network Advisor Installation and Migration Guide
The quickest and simplest method of moving from one package to another is to enter the new
license information on the Network Advisor License dialog box. The following tables list the
available upgrade paths:
TABLE 10SAN upgrade paths
Current software releaseTo software release
3
SAN Professional SAN Professional Plus Trial or Licensed version
SAN Enterprise Trial or Licensed version
SAN Professional Plus Licensed versionSAN Enterprise Licensed version
SAN + IP Enterprise Licensed version
SAN Enterprise TrialSAN Enterprise Licensed version
SAN EnterpriseSAN + IP Enterprise Licensed version
TABLE 11IP upgrade paths
Current software releaseTo software release
IP Professional IP Base Trial or Licensed version
IP Base TrialIP Base Licensed version
SAN + IP Enterprise Licensed version
IP Base Licensed version (lower count)IP Base Licensed version (higher count)
SAN + IP Enterprise Licensed version
Brocade Network Advisor Installation and Migration Guide39
53-1003157-01
Upgrading the license
NOTE
3
TABLE 12SAN + IP upgrade paths
Current software releaseTo software release
SAN + IP Professional SAN Professional Plus + IP Trial or Enterprise
Licensed version
SAN + IP Enterprise Trial or Licensed version
SAN Professional Plus + IP Enterprise Trial SAN Professional Plus + IP Enterprise Licensed
version
SAN + IP Enterprise Trial or Licensed version
SAN Professional Plus + IP Enterprise Licensed
version
SAN + IP Enterprise Trial
SAN + IP Enterprise Licensed Version
1. Select Help > License.
The Network Advisor License dialog box displays.
2. Browse to the license file (.xml) and click Update.
3. Click OK on the Network Advisor License dialog box.
4. Click OK on the message.
The Client closes after updating the license successfully. Restart the Server from the Server
Management Console for the changes to take effect.
5. Open the application (double-click the desktop icon or open from the Start menu).
The Log In dialog box displays.
6. Enter your user name and password.
The defaults are Administrator and password, respectively. If you migrated from a previous
release, your user name and password do not change.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
SAN + IP Enterprise Licensed version
IP Enterprise Licensed version
7. 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.
8. Click Login.
9. Click OK on the Network Advisor Login Banner.
40Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Supported migration paths
NOTE
NOTE
NOTE
Enterprise and Professional Plus editions are not supported on 32-bit servers. To migrate Enterprise
and Professional Plus editions to a 64-bit server, refer to
migrating from one server to another” on page 44.
Direct migration is not supported on pre-12.0.X releases. Table 13 shows the migration paths from
DCFM, INM, and Network Advisor 12.3.X or earlier releases.
Network Advisor 11.1.X includes 11.1.0, 11.1.1, 11.1.2, 11.1.3, 11.1.4, and 11.1.5.
Network Advisor 11.2.X includes 11.2.0, 11.2.1, and 11.2.2.
1.Migration from pre-12. 0.0 releases does not support partial data migration and network path migration.
2.Local path migration is only supported when you partially uninstall the current version. Network path migration (whether the
current version is fully installed or partially uninstalled) is always supported.
Enterprise
2
Yes
2
2
2
Tab le 15 shows the migration paths from SMI Agent only. For the step-by-step migration
procedures, refer to “Migrating data” on page 48.
TABLE 15SMI Agent only migration paths
Current versionProfessional version Trial versionLicensed VersionSMI Agent only
Network Advisor 12.0.X/12.1.X SMI Agent
only
Professional
Plus
NoNoNoNoNoYe s
EnterpriseProfessional
Plus
Enterprise
DCFM migration paths
Before you migrate from DCFM to Network Advisor 11.0.X, 11.1.0, 11.1.1, or 11.1.2, you must reset
your DCFM password back to the default (password).
You cannot migrate directly from DCFM 10.0.X, DCFM 10.1.X or DCFM 10.3.X to Network Advisor
12.3.0. You must first migrate to DCFM 10.4.X, then migrate to Network Advisor 11.1.X, then
migrate to Network Advisor 12.0.X, then migrate to Network Advisor 12.3.0.
To migrate from DCFM 10.0.X, DCFM 10.1.X or DCFM 10.3.X to DCFM 10.4.X, contact your
customer representative. To migrate from DCFM 10.4.X to Network Advisor 11.1.X, refer to Network Advisor Migration Guide for Network
Advisor 11.1.X.
INM migration paths
You cannot migrate directly from INM to Network Advisor 12.3.0. You must first migrate to Network
Advisor 11.0.X, then migrate to Network Advisor 11.1.X, then migrate to Network Advisor 12.0.X,
then migrate to Network Advisor 12.3.0. To migrate from INM to Network Advisor 11.1.X, contact
your customer representative.
Brocade Network Advisor Installation and Migration Guide43
53-1003157-01
Pre-migration requirements
3
EFCM and Fabric Manager migration paths
You cannot migrate directly from EFCM or Fabric Manager to Network Advisor 12.3.0. To migrate
from EFCM or Fabric
Advisor 11.1.X, then migrate to Network Advisor 12.0.X, then migrate to Network Advisor 12.3.0.
For more information about migrating from EFCM or Fabric Manager to DCFM 10.3.X, contact your
customer representative.
Manager, you must first migrate to DCFM 10.3.X, then migrate to Network
Pre-migration requirements
Before you install Network Advisor, make sure you meet the following pre-migration requirements.
• Make sure all system requirements have been met prior to installation. For specific system
requirements, refer to
• Check for and install the latest Java patches for your operating system. Network Advisor
• Make sure that you fully back up your current Management application data on your
management server.
• Make sure you close all instances of the application before migrating.
• Make sure to install Network Advisor on the same system as your current Management
application.
• If you are migrating within the same release or you are migrating from Professional to Licensed
software, make sure to partially uninstall (refer to
• Partial data migration is not supported from pre-12.0.0 releases. If you are migrating data from
a partially uninstalled source, complete the following steps:
1.7.0_60. For the web site listing patch information, go to
“System requirements” on page 1.
“Uninstallation” on page 57) the application.
1. Re-install your current Network Advisor version on the same machine and migrate the
partially uninstalled data.
If your current release is pre-11.3.X, you must migrate to Network Advisor 11.3.0 or later.
Refer to
2. Install Network Advisor 12.1 (refer to “Installation” on page 1) on the same machine and
migrate your data (refer to “Migrating data” on page 48).
Tab le 13 on page 41 for the release migration path.
Pre-migration requirements when migrating from
one server to another
If you are migrating from Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor
12.2.X on a 32-bit Windows server to Network Advisor 12.3.0 on a 64-bit Windows server, complete
the following steps.
1. Take server backup for 12.0.X, 12.1.X, or 12.2.X using Options > Server Backup on the 32-bit
Windows server.
2. Install Network Advisor 12.0.X, 12.1.X or Network Advisor 12.2.X on the 64-bit Windows server.
3. Select SMC > Restore tab to restore the backup taken on the 32-bit Windows server.
4. Install Network Advisor 12.3.0 on the 64-bit Windows server.
44Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Pre-migration requirements
Perform seamless migration to Network Advisor 12.3.0.
If you are migrating from a pre-12.0.X release on a 32-bit Windows server to Network Advisor
12.3.0 on a 64-bit Windows server, complete the following steps.
1. Install and migrate to Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor
12.2.X in the same machine (refer to
2. Take server backup using Options > Server Backup on the 32-bit Windows server.
3. Install Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor 12.2.X on the
64-bit Windows server.
4. Select SMC > Restore tab to restore the backup taken on the 32-bit Windows server.
5. Install Network Advisor 12.3.0 on the 64-bit Windows server.
Perform seamless migration to Network Advisor 12.3.0.
If you are migrating from Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor
12.2.X on a 32-bit Linux server to Network Advisor 12.3.0 on a 64-bit pure Linux server, complete
the following steps.
1. Take server backup for 12.0.X, 12.1.X, or 12.2.X using Options > Server Backup on the 32-bit
Linux server.
“Supported migration paths” on page 41).
3
2. Install Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor 12.2.X on the
64-bit pure Linux server.
3. Select SMC > Restore tab to restore the backup taken on the 32-bit Linux server.
4. Install Network Advisor 12.3.0 on the 64-bit pure Linux server.
Perform seamless migration to Network Advisor 12.3.0.
If you are migrating from a pre-12.0.X release on a 32-bit Linux server to Network Advisor 12.3.0 on
a 64-bit pure Linux server, complete the following steps.
1. Install and migrate to Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor
12.2.X in the 32-bit Linux server (refer to
2. Take server backup using Options > Server Backup on the 32-bit Linux server.
3. Install Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor 12.2.X on the
64-bit pure Linux server.
4. Select SMC > Restore tab to restore the backup taken on the 32-bit Linux server.
5. Install Network Advisor 12.3.0 on the 64-bit pure Linux server.
Perform seamless migration to Network Advisor 12.3.0.
If you are migrating from Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor
12.2.X on a 32-bit Linux server to Network Advisor 12.3.0 on a 64-bit Linux server (32-bit
compatible), complete the following steps.
1. Take server backup for 12.0.X, 12.1.X, or 12.2.X using Options > Server Backup on the 32-bit
Linux server.
“Supported migration paths” on page 41).
2. Install Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor 12.2.X on the
64-bit Linux server (32-bit compatible).
3. Select SMC > Restore tab to restore the backup taken on the 32-bit Linux server.
4. Install Network Advisor 12.3.0 on the 64-bit Linux server (32-bit compatible).
Brocade Network Advisor Installation and Migration Guide45
53-1003157-01
Pre-migration requirements
NOTE
NOTE
3
Perform seamless migration to Network Advisor 12.3.0.
If you are migrating from a pre-12.0.X release on a 32-bit Linux server to Network Advisor 12.3.0 on
a 64-bit Linux server (32-bit compatible), complete the following steps.
1. Install and migrate to Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor
12.2.X in the 32-bit Linux server (refer to
2. Take server backup using Options > Server Backup on the 32-bit Linux server.
3. Install Network Advisor 12.0.X, Network Advisor 12.1.X, or Network Advisor 12.2.X on the
64-bit Linux server (32-bit compatible).
4. Select SMC > Restore tab to restore the backup taken on the 32-bit Linux server.
5. Install Network Advisor 12.3.0 on the 64-bit Linux server (32-bit compatible).
Perform seamless migration to Network Advisor 12.3.0.
“Supported migration paths” on page 41).
• If you are migrating from a pre-12.0.0 release on one server to another server, complete the
following steps. Migrating using this procedure requires that the server versions are the same
(32-bit to 32-bit OR 64--bit to 64-bit).
If you are migrating from a pre-11.3.0 release, you must first migrate to Network Advisor 12.0.X
on the current server (refer to Table 13 on page 41 for the release migration path).
1. Install Network Advisor 12.0.X on your new machine (refer to “Installation” on page 1) and
migrate your data (“Migrating data” on page 48) using the network path.
2. Install Network Advisor 12.3.0 on your new machine (refer to “Data Migration” on page 39)
and migrate your data (“Migrating data” on page 48).
• If you are migrating from a Network Advisor 12.0.X release on a 32-bit server to Network
Advisor 12.3.0 on a 64-bit server, complete the following steps.
1. Back up the Network Advisor 12.0.X server data on your current 32-bit machine. For
instructions, refer to “Configuring backup” in the Brocade Network Advisor User Manual or
online help.
2. Install Network Advisor 12.0.X on your new 64-bit machine (refer to “Installation” on
page 1).
3. Restore the server back up from your original 32-bit machine. For instructions, refer to
“Restoring data” in the Brocade Network Advisor User Manual or online help.
4. Install Network Advisor 12.3.0 on the 64-bit Windows server (refer to “Data Migration” on
page 39) and migrate your data (“Migrating data” on page 48).
• If you are migrating from Windows server that is no longer supported to a supported Windows
server, complete the following steps. For a list of supported operating system servers, refer to
Tab le 4 on page 2.
If you are migrating from a pre-11.3.0 release, you must first migrate to Network Advisor
11.3.0 on your current server (refer to Tabl e 13 on page 41 for the release migration path).
46Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Pre-migration requirements
NOTE
NOTE
1. Install Network Advisor 12.0.X on your current machine (refer to “Installation” on page 1)
and migrate your data (“Migrating data” on page 48).
2. Install Network Advisor 12.3.0 on your new machine (refer to “Data Migration” on page 39)
and migrate your data (“Migrating data” on page 48).
3
• If you are migrating from Linux server that is no longer supported to a supported Linux server,
complete the following steps. For a list of supported operating system servers, refer to
on page 2.
If you are migrating from a pre-11.3.0 release, you must first migrate to Network Advisor
11.3.0 on your current server (refer to Tabl e 13 on page 41 for the release migration path).
1. Install Network Advisor 12.0.X on your current machine (refer to “Installation” on page 1)
and migrate your data (“Migrating data” on page 48).
2. Back up the server data on your current machine. For instructions, refer to “Configuring
backup” in the Brocade Network Advisor User Manual or online help.
3. Install Network Advisor 12.0.X on the supported server (refer to “Data Migration” on
page 39).
4. Restore the server back up from your original server. For instructions, refer to “Restoring
data” in the Brocade Network Advisor User Manual or online help.
Tab le 4
5. Install Network Advisor 12.3.0 on your new machine (refer to “Data Migration” on page 39)
and migrate your data (“Migrating data” on page 48).
• Cross OS migration is not supported; however, you can restore a Windows OS backup to a
Linux
OS and vice versa. If you are migrating from one OS to another, complete the following
steps.
If you are migrating from a pre-11.3.0 release, you must first migrate to Network Advisor 12.0.X
on your current server (refer to Tabl e 13 on page 41 for the release migration path).
1. Install Network Advisor 12.3.0 (refer to “Installation” on page 1) on the current machine
and migrate your data (refer to “Migrating data” on page 48).
2. Back up the server data on your current machine. For instructions, refer to “Configuring
backup” in the Brocade Network Advisor User Manual or online help.
3. Install Network Advisor 12.3.0 (refer to “Installation” on page 1) on the new machine.
4. Restore the server back up from your original machine. For instructions, refer to “Restoring
data” in the Brocade Network Advisor User Manual or online help.
Additional pre-migration requirements on UNIX systems
• Make sure that the current application services are running.
1. Go to Install_Home/bin.
2. Execute ./smc or sh smc.
3. Click the Services tab.
The tab lists the DCFM services.
Brocade Network Advisor Installation and Migration Guide47
53-1003157-01
3
NOTE
NOTE
NOTE
NOTE
NOTE
Migrating data
4. Click Start, if necessary.
• 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).
• 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
command xhost +IP, 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 command xterm from the same shell
from which you run
should open.
install.bin. A new X terminal window to the destination X Server display
Additional trial requirements
• Two versions of the Management application (DCFM, INM, or Network Advisor) cannot reside
• Data collected during the Trial cannot be migrated back to the Professional software.
• Once the Enterprise trial period expires, you must upgrade to Licensed software.
Migrating data
The quickest and simplest method of moving from one package to another is to enter the new
license information on the Network Advisor License dialog box. To upgrade from a previous release,
refer to
“Installation” on page 1.
If an error occurs while migrating from pre 12.3.0 to version 12.3.0, it rolls back to the earlier
version.
Trial to Professional software migration is not supported.
Licensed software to Trial software migration is not supported.
on the same host unless there are two
“Upgrading the license” on page 39. If you have not installed the application, refer to
guest operating systems on the same host.
Enterprise software to Professional Plus software migration is not supported.
SAN with SMI Agent + IP is not supported on 32-bit systems.
48Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Migrating data
NOTE
NOTE
NOTE
NOTE
To migrate data from a previous version, complete the following steps.
1. Click Next on the Welcome screen.
2. Choose one of the following options:
• If data is detected on your system, the Copy Data and Settings from previous releases
screen displays. To migrate data from the previous version installed (automatically
detected), select Yes, from the following location. Continue with
step 3.
• If data is not detected, the Copy Data and Settings from previous releases screen displays.
Complete the following steps:
a. Select Yes, from this machine or on network and click Browse to browse to the
installation directory.
b. Click Next on the Copy Data and Settings from previous releases screen. Continue
with
step 3.
If you are migrating from a 32-bit server, you will need to browse to the shared directory of
the 32-bit server on the Copy Data and Settings from previous releases screen.
3
If you are migrating to the same install location (as the previous version), you will need to
browse to the renamed directory on the Copy Data and Settings from previous releases
screen.
3. To migrate historical performance data, select the SAN and IP check boxes, if necessary.
4. Click Start on the Data Migration screen.
Data migration may take several minutes. When data migration is complete, the previous
version is partially uninstalled.
5. Click Next on the Data Migration screen.
If you have products associated with the Brocade North America or Brocade International Call
Home centers, a message displays. To map these Call Home centers to the Brocade E-mail Call
Home center after migration, click Yes. To not map these Call Home centers, click No.
Make sure you configure the Brocade E-mail Call Home center (refer to the Brocade Network Advisor User Manual or online help).
If you are migrating from Professional or Trial software, continue with step 6.
If you are migrating from Licensed software, go to step 7.
6. Select one of the following options on the Installation Type screen and click Next.
The DCX and DCX 8510-8 Backbone chassis require Enterprise edition.
• Network Advisor - Licensed version
Continue with step 7. Requires you to enter a license key during configuration to enable
features and configuration.
Brocade Network Advisor Installation and Migration Guide49
53-1003157-01
3
ATTENTION
NOTE
NOTE
Migrating data
• Network Advisor - 120 days Trial
Go to step 8. Enables you to manage IP, SAN, or SAN and IP networks from a single
interface for 120 days.
If you choose to install Trial, once the trial period ends (120 days), you must upgrade to
Licensed software.
• Network Advisor - Professional
Go to step 8. Bundled with Fabric OS and IronWare OS devices to manage small IP, SAN, or
SAN and IP networks from a single interface.
7. Choose one of the following options on the Server License screen:
• If you are migrating from a licensed source, the source license information displays. Click
Next. Continue with
step 8.
• If you are migrating from Professional or Trial software to Licensed software, browse to the
license file (.xml) and click Next. Continue with
The License Key field is not case-sensitive.
step 8.
Downgrading the license from the current configuration during migration is not supported.
8. Complete the following steps on the FTP/SCP/SFTP Server screen.
The default selection reflects the previous edition configuration.
a. Choose one of the following options:
• Select Built-in FTP/SCP/SFTP Server to configure an internal FTP/SCP/SFTP server
and select one of the following options:
-Select Built-in 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 Built-in SCP/SFTP Server to configure an internal SCP/SFTP server
The internal SCP/SFTP server uses a default account and port 22. 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/SCP/SFTP Server to configure an external 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.
b. Click Next.
If port 21 or 22 is busy, a message displays. Click OK to close the message and continue. Once
the Management application is configured make sure port 21 or 22 is free and restart the
Server to start the FTP/SCP/SFTP service.
If you use an FTP/SCP/SFTP Server which is not configured on the same machine as the
Management application, the Firmware Repository feature will not be available.
50Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Migrating data
NOTE
NOTE
NOTE
NOTE
You can configure the FTP/SCP/SFTP server settings from the Options dialog box. For
instructions, refer to the Network Advisor User Manual or online help.
9. Complete the following steps on the Server IP Configuration screen.
If the Management server or client has multiple Network Interface Cards and if any of these
interfaces are not plugged in, you must disable them; otherwise, the following features do not
work properly:
Server impact
• Configuration wizard (does not display all IP addresses)
• Trap and Syslog auto registration
• Report content (Ipconfiguration element does not display all server IP addresses)
• Network OS configuration backup through FTP
• Tra ce dum p through F TP
Client impact
• Options dialog box (does not display all IP addresses)
• Firmware import and download dialog box
• Firmware import for Fabric OS and Network OS products
• FTP button in Technical Support Repository dialog box
• Technical supportSave of Fabric OS, Network OS, and Host products through FTP
3
a. Select an address from the Server IP Configuration list.
For Professional software, the Server IP Configuration address is set to “localhost” by
default. You cannot change this address.
For SMI Agent, 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.
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 the an IPv6 address is selected, server start up 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 34.
c.Click Next.
Brocade Network Advisor Installation and Migration Guide51
53-1003157-01
3
NOTE
NOTE
NOTE
NOTE
Migrating data
10. Complete the following steps on the Server Configuration screen.
FIGURE 2Server Configuration screen
a. Enter a port number in the Web Server Port # (HTTPS) field (default is 443).
b. Enable HTTP redirection to HTTPS by selecting the Redirect HTTP Requests to HTTPS
check box.
When you enable HTTP redirection, the server uses port 80 to redirect HTTP requests to
HTTPS. You can configure the server port settings from the Options dialog box (Server Port
pane). For instructions, refer to the Network Advisor User Manual or online help.
c.Enter a port number in the Database Port # field (default is 5432).
Do not use a port number below 1024.
d. Enter a port number in the Starting Port # field (default is 24600).
For Professional software, the server requires 15 consecutive free ports beginning with
the starting port number.
For Trial and Licensed software, the server requires 18 consecutive free ports beginning
with the starting port number.
e. Enter a port number in the Syslog Port # field (default is 514).
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 25.
52Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Migrating data
NOTE
NOTE
f.Enter a port number in the SNMP Port # field (default is 162).
g. Enter a port number in the TFTP Port # field (default is 69).
h. Click Next.
If you enter a syslog port number already in use, a 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
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.
If you are configuring Professional software, go to step 14.
If you are configuring IP Enterprise, go to step 13.
11. (SAN with SMI Agent + IP or SAN with SMI Agent) Complete the following steps on the SMI
Agent Configuration screen.
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.
step 11.
3
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.
12. (SAN Enterprise or SMI Agent) Select one of the following options on the SAN Network Size
screen and click Next:
Port count is equal to the total number of switch ports across all fabrics.
• Small (managing up to 2000 switch ports, 1-20 domains)
• Medium (managing up to 5000 switch ports, 21-60 domains)
• Large (managing up to 15000 switch ports, 61-120 domains)
If you are configuring IP Enterprise, continue with step 13; otherwise, go to step 14.
13. (IP Enterprise) Select one of the following options on the IP Network Size screen and click Next:
Port count is equal to the total number of all managed product ports.
• Small (managing up to 1-20 products)
• Medium (managing up to 21-200 products)
• Large (managing up to 201-5050 products)
14. Enable feature usage data transfer from the application by selecting the Yes, I want to
participate option.
You can stop participating at any time. To view an example of the usage data, click View
Example Data.
Brocade Network Advisor Installation and Migration Guide53
53-1003157-01
3
NOTE
NOTE
Migrating data
To stop participating in feature usage data transfer after configuration, refer to “Product
improvement” on page 35.
15. Verify your configuration information on the Server Configuration Summary screen and click
Next.
16. Complete the following steps on the Start Server screen.
a. (Trial and Licensed only) Select the Start SMI Agent check box, if necessary.
b. (Trial and Licensed only) Select the Start SLP check box, if necessary.
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 (refer to
“Configuring an explicit server IP address” on page 34).
17. Enter your user name and password.
The defaults are Administrator and password, respectively. If you migrated from a previous
release, your user name and password do not change.
Do not enter Domain\User_Name in the User ID field for LDAP server authentication.
18. Click Login.
19. Click OK on the Network Advisor Login Banner.
Cross flavor migration
To migrate from Brocade Network Advisor 12.0.X to a non-Brocade Network Advisor 12.3.X,
complete the following steps.
1. Install Brocade Network Advisor 12.0.X (refer to “Installing the application” on page 9).
2. Install non-Brocade Network Advisor 12.3.X (refer to “Installing the application” on page 9).
3. Migrate the supported (partial or full) data from Brocade Network Advisor 12.0.X (refer to
“Migrating data” on page 48) to the Non-Brocade Network Advisor 12.3.X by browsing to the
Brocade Network Advisor 12.3.X location on the Copy Data and Setting screen.
If the Non-Brocade Network Advisor is not supporting SAN + IP, it is recommended to install SAN only
Brocade Network Advisor and then migrate to Non-Brocade Network Advisor.
Migration rollback
Migration rollback is triggered when a failure occurs while migrating to a different version of
Brocade Network Advisor. After successful rollback, the previous version will be running and the
destination version will be uninstalled. The destination version failure logs and the source version
supportsave will be zipped and stored at the source BNA_HOME\support folder in the following
format.
Zip file format, Migration_Failure_SupportSave_<Time stamp>.zip
54Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Migrating data
3
Migration rollback due to insufficient space
When migration rollback fails due to insufficient space, you can either increase the disk space and
try rollback or cancel the migration rollback. The destination version is uninstalled manually if you
cancel the migration rollback. Use the following commands, to retrieve the source version.
BNA_HOME>bin>sh dbsvc start
BNA_HOME>bin>sh service dcmsvc start
For Linux, if SLP is enabled
BNA_HOME>bin>sh slpsvc start
For Linux, if CIMOM is enabled
BNA_HOME>bin>sh service cimomsvc start
Brocade Network Advisor Installation and Migration Guide55
53-1003157-01
3
Migrating data
56Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Chapter
NOTE
Uninstallation
In this chapter
This section provides step-by-step instructions to uninstall Network Advisor and SMI Agent from
both Windows and UNIX systems.
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.
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. This is the default option.
• Full Uninstall — All data is removed.
3. Click Uninstall.
4. Click Done on the Uninstall Complete screen.
Brocade Network Advisor Installation and Migration Guide57
53-1003157-01
Uninstalling from Windows systems (headless uninstall)
NOTE
4
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
• To fully uninstall Network Advisor (all data is removed), execute
Install_Home\Uninstall_Network Advisor 12.3.0\Uninstall_Network Advisor 12.3.0.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.
Uninstalling from UNIX systems
Follow these instructions to uninstall the Network Advisor and SMI Agent from your UNIX system.
The Uninstall folder is retained.
1. Go to Install_Home/Uninstall_Network_Advisor12_1_0.
2. Execute ./Uninstall_Network_Advisor12_1_0.
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. This is the default option.
• Full Uninstall — All data is removed.
4. Click Uninstall.
5. Click Done on the Uninstall Complete screen.
58Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Uninstalling from UNIX systems (headless uninstall)
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_Advisor12_1_0.
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 12_1_0 –f
<absolute path of partial uninstall property file>.
• To fully uninstall Network Advisor (all data is removed), execute
.\Uninstall_Network_Advisor 12_1_0 –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.
4
Brocade Network Advisor Installation and Migration Guide59
53-1003157-01
Uninstalling from UNIX systems (headless uninstall)
4
60Brocade Network Advisor Installation and Migration Guide
Tab le 16 summarizes the packages and available versions for each package.
TABLE 16Packages and versions
PackageVersions
SAN with SMI Agent +IP Licensed Version — Enterprise
• SAN — Support for 36 fabrics, 10,000 devices, and 15,000 switch ports
• IP — Support for 5,050 products and 100 MPLS products
NOTE: Virtual Fabrics are counted as Fabrics when calculating the managed count limits.
Professional
• SAN — Support for 2 fabric, 1000 devices, and 300 switch ports
• IP — Support for 20 products
NOTE: Virtual Fabrics are counted as Fabrics when calculating the managed count limits.
NOTE: SMI Agent is not supported on Professional.
SAN with SMI AgentLicensed Version — Enterprise
• SAN — Support for 36 fabrics, 10,000 devices, and 15,000 switch ports
NOTE: Virtual Fabrics are counted as Fabrics when calculating the managed count limits.
Licensed Version — Professional Plus
• SAN — Support for 36 fabrics, 4,096 devices, and,2560 switch ports
NOTE: Virtual Fabrics are counted as Fabrics when calculating the managed count limits.
Professional
• SAN — Support for 2 fabric, 1,000 devices, and 300 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
A
Brocade Network Advisor Installation and Migration Guide61
53-1003157-01
Edition feature support
A
Edition feature support
Tab le 17 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 17SAN features supported
FeatureProfessional Professional PlusEnterprise
AAA (Authentication, Authorization, and Auditing)
Authentication and authorization configuration
Access Gateway (AG) management
AG display
Support for firmware download, supportSave, performance statistics, and
configuration file management
Active session managementYesYesYes
Bottleneck detection
ConfigurationNoYesYes
StatisticsNoYesYes
Badge on topology and product treeYesYesYes
Show affected hostNoYesYes
Call Home support
Support for all call home centersNoYesYes
SupportSave for Fabric OS switchesNoYesYes
Support for appending the last 30 events in a call home event for e-mail-based
call home centers
Certificate managementYesYes
Configuration management
Configuration repository managementNoYesYes
Firmware downloadYesYesYes
Manual backup
NOTE: Professional only supports one switch at a time.
Save configuration
NOTE: Professional only supports one switch at a time.
Periodic configuration backup and persistenceNoYesYes
Replicate switch configurationNoYesYes
DashboardYesYesYes
DCB configuration managementYesYesYes
DCX backbone chassis discovery and managementNoNoYes
Deployment Manager
Diagnostic port testNoYesYes
Digital diagnostic YesYesYes
NoYesYes
YesYesYes
NoYesYes
YesYesYes
YesYesYes
62Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Edition feature support
TABLE 17SAN features supported (Continued)
FeatureProfessional Professional Plus Enterprise
Encryption
Layer 2 FC support Ye sYesYes
Encryption configuration and monitoring YesYesYes
Access Gateway – Cisco interop supportYesYesYes
Device decommissioningYesYesYes
End device connectivity
Collection
Views
Fabric bindingNoYesYes
Fabric Watch
HardwareElement
PortsElement
AdminElement
Router AdminElement
Name ServerElement
Fault managementElement
Show switch eventsYesYesYes
Show fabric eventsYesYesYes
Syslog registration and forwardingYesYesYes
SNMP trap registration and forwardingYesYesYes
Trap configuration, credentials, and customizationYesYesYes
Event forwardingNoYesYes
Event custom reportNoYesYes
Event processing (event policies and pseudo events)NoYesYes
Common SNMP/Trap registrationYesYesYes
FCIP management
FCIP configuration wizardYesYesYes
Iperf and IP trace routeYesYesYes
FCoE management
FCoE configuration YesYesYes
Migration from DCFMYesYesYes
FICON/CUP
YesYesYes
Element
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
Element
Manager
A
Brocade Network Advisor Installation and Migration Guide63
53-1003157-01
Edition feature support
A
TABLE 17SAN features supported (Continued)
FeatureProfessional Professional Plus Enterprise
Cascaded FICON configuration wizardNoNoYe s
Cascaded FICON Fabric merge wizardNoNoYes
PDCM MatrixElement
Manager
Firmware management and supportSave
Firmware downloadYesYesYes
Capture SupportSaveYesYesYes
Flow VisionNoYesYes
Frame monitorNoYesYes
HBA management
HBA managementYesYesYes
VM managementYesYesYes
Driver/DIOS managementNoYesYes
Fabric assigned WWNNoYesYes
HBA Server and Storage port mappingNoYesYes
High Integrity FabricNoYesYes
IPv6 — Server - Switch supportYesYe sYes
iSCSI discoveryYesYesYe s
Layer 2 trace routeNoYesYes
License NoYesYes
MAPS managementNoYesYes
Meta-SAN
Routing configuration
Domain ID configuration
Name ServerYesYesYes
Open Trunking Support
Display trunks on the topologyYesYe sYes
Display trunks propertiesYesYe sYes
Display marching antsYesYesYes
Display connections propertiesYesYesYes
NoYesYes
Element
Manager
Yes
64Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Edition feature support
TABLE 17SAN features supported (Continued)
FeatureProfessional Professional Plus Enterprise
Performance management - SNMP monitoring
Real Time Performance collection, display, and reports YesYesYe s
Historical Performance collection, display, and reports NoYesYes
ThresholdsNoYesYes
Top talkers - Supported on SAN switches and Access GatewayNoYesYes
Marching antsNoYesYes
Data agingNoYe sYes
End-to-End monitorsNoYesYes
Policy MonitorYe sYesYes
Port Administration Element
Manager
Port Fencing NoYesYes
Port group configurationNoNoYes
ReportsYe sYesYes
Generate reportsYesYe sYes
View reportsYesYesYes
Performance reportsYesYesYes
FCR reportsYesYesYes
SCOM plug-in supportNoYesYes
Security management
Replicate switch policy configurationNoYesYes
SNMP configurationYesYesYes
L2 ACL configuration
NOTE: Only supported on DCB devices.
YesYesYes
Element
Manager
Element
Manager
A
Brocade Network Advisor Installation and Migration Guide65
53-1003157-01
Edition feature support
A
TABLE 17SAN features supported (Continued)
FeatureProfessional Professional Plus Enterprise
SMI Agent
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
Tru nki ng
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
Basic configurations through the Element Manager
Switch port enable/disable through right-click menuYesYesYes
Technical SupportSaveYesYesYes
Tel net
NOTE: Telnet through the server is only supported on Windows systems.
70Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Edition feature support
TABLE 18IP features supported (Continued)
FeatureProfessionalBase
Licensed
version
Web Element ManagerYesYesYesYe s
Web Tools/Fabric WatchYesYesYesYe s
Zoning
Member selectionYesYe sYesYes
Zone editingYesYesYesYes
Live fabric library scopeYesYe sYesYes
Zone alias supportYesYe sYesYes
Delete Zone databaseNoYe sYesYes
Impact analysisYesYesYesYes
Remove offline devices NoYe sYesYes
Device to Zone / zoneset participation analysisYesYesYe sYe s
LSAN ZonesNoYe sYesYes
Rolling back to an activated zone databaseNoYe sYesYes
Import or export a zone databaseNoYesYesYes
Base with
Licensed
Ethernet
Fabrics
Base with
Unlicensed
Ethernet
Fabrics
A
Brocade Network Advisor Installation and Migration Guide71
53-1003157-01
Management server and client ports
NOTE
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 Products and the Servers or Clients. In other words, a Server or
Client can find a Product, appear to log in, but is immediately logged out because the Product
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.
Professional edition does not support remote clients.
Tab le 19 lists the default port numbers and whether or not it needs to be opened up in the firewall
and includes the following information:
• Port Number — The port at the destination end of the communication path.
• Ports — The name of the port.
• Transport — The transport type (TCP or UDP).
• Description — A brief description of the port.
• Communication Path — The “source” to “destination” values. Client and Server refer to the
Management application client and server unless stated otherwise. Product refers to the
Fabric OS, Network OS, or IronWare OS devices.
• Open in Firewall — Whether the port needs to be open in the firewall.
TABLE 19Port usage and firewall requirements
Port Number PortsTransportDescriptionCommunication Path Open in Firewall
1
20
1
21
2
22
23Teln etTCPTelnet port from server/client
2
25
2
49
69TFTPUDPFile upload/download to
FTP Port (Control)TCPFTP Control port for internal
FTP
server
FTP Port (Data)TCPFTP Data port for internal
FTP
server
SSH or SCP or SFTPTCPSecure telnet and secure
upload and download to
product
to product
SMTP Server portTCPSMTP Server port for e-mail
communication if you use
e-mail notifications without SSL
TACACS+ Authentication portTCPTACACS+ server port for
authentication if you use
TACACS+ as an external
authentication
product
Client–Server
Product–Server
Client–Server
Product–Server
Server–Product
Client –Product
Product – Server
Server–Product
Client–Product
Server–SMTP
Server
Server–TACACS+
Server
Product-ServerYes
Yes
Yes
Yes
Yes
Yes
Yes
72Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Management server and client ports
TABLE 19Port usage and firewall requirements (Continued)
Port Number PortsTransportDescriptionCommunication Path Open in Firewall
Client–ServerYes
port if you use secure
client-server communication.
You need this port for HTTP
redirection
Product HTTP serverTCPProduct non-SSL http port for
Server–Product Yes
http and CAL communication if
you do not use secure
communication to the product
Product non-SSL http port for
Client–Product Yes
http and CAL communication if
you do not use secure
communication to the product
and you do not use the
Management application
server proxy
SNMP port UDPDefault SNMP portServer–ProductYes
SNMP Trap port UDPDefault SNMP trap portProduct-ServerYe s
LDAP Authentication Server PortUDP
TCP
LDAP server port for
authentication if you use LDAP
Server–LDAP
Server
Yes
as an external authentication
HTTPS serverTCPHTTPS (HTTP over SSL) server
Client-Server Yes
port if you use secure client server communication
HTTPS (HTTP over SSL) server
Server–Product Yes
port if you use secure
communication to the product
Client–Product Yes
port if you use secure
communication to the product
and you do not use the
Management application
server proxy
HTTPS (HTTP over SSL) server
port if you use vCenter
Server-vCenter
Server
Yes
discovery
SMTP Server port for SSLTCPSMTP Server port for e-mail
communication if you use
Server-SMTP
Server
Yes
e-mail notifications with SSL
Syslog PortUDPDefault Syslog PortProduct–Server
Yes
Managed Host -
Server
LDAP Authentication SSL portTCPLDAP server port for
authentication if you use LDAP
Server–LDAP
Server
Yes
as an external authentication
and SSL is enabled
A
Brocade Network Advisor Installation and Migration Guide73
53-1003157-01
Management server and client ports
A
TABLE 19Port usage and firewall requirements (Continued)
Port Number PortsTransportDescriptionCommunication Path Open in Firewall
2
1812
2
1813
5432Database port TCPPort used by database if you
5988SMI Server port TCPSMI server port on the
1,2
5989
2
6343
24600
24601
24602
24603
24604
24605
24606
24607
24608
24609
24610
RADIUS Authentication Server PortUDPRADIUS server port for
authentication if you use
Server–RADIUS
Server
RADIUS as an external
authentication
RADIUS Accounting Server PortUDPRADIUS server port for
accounting if you use RADIUS
Server–RADIUS
Server
as an external authentication
Remote ODBC–
access the database remotely
Database
from a third-party application
SMI Client- ServerYes
Management application and
the CIM/SMI port on HBAs if
you use SMI Agent without SSL
Server-Managed
Host
SMI Server port with SSL enabledTCPSMI Agent port on the
Management application and
SMI Agent Server–
Client
the CIM/SMI port on HBAs if
you use SMI Agent with SSL
Server-Managed
Host
sFlowUDPReceives sFlow data from
Product-ServerYes
products if you are monitoring
with sFlow
1,2
JBoss remoting connector port TCPUse for service location. Uses
Client–ServerYes
SSL for privacy.
1,2
JBoss Transaction Services Recovery
TCPNot used remotely.Server Yes
Manager port
2
JBoss Transaction Status Manager portTCPNot used remotelyServerYes
1,2
HornetQ Netty portTCPUse for JMS (Java Message
Client–ServerYes
Service), async messages from
server to client.
Uses SSL for privacy.
1,2
JMX remoting connector portTCPManagement console port for
Client–ServerYes
native connector (JMX)
1,2
JBoss https management portTCPManagement console port for
Reserved for future useTCPNot usedClient - Server No
2
Reserved for future useTCPNot usedClient - Server No
2
Reserved for future useTCPNot usedClient - Server No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
74Brocade Network Advisor Installation and Migration Guide
53-1003157-01
Scalability limits
TABLE 19Port usage and firewall requirements (Continued)
Port Number PortsTransportDescriptionCommunication Path Open in Firewall
A
34568HCM Agent discovery portTCPUsed for HBA management via
JSON
1
55556
1.Port does not need to be open in the firewall for Professional edtion.
2.The default port number. You must use the same port number for all products or hosts managed by the Management server. This port is
configurable in the Management server; however, some products and firmware versions do not allow you to configure a port.
Launch in Context (LIC) client hand
shaking port
TCPClient port used to check if a
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.
Server - Managed
Host
Client No
Yes
Scalability limits
The following tables summarize the scalability limits for support with Network Advisor.
Tab le 20 summarizes the SAN scalability limits for support with Network Advisor Enterprise edition.