BNA 14.2.0 GA Release Notes v1.6

Brocade Network Advisor 14.2.
0
GA Release Notes v1.6
August 3, 2017
Document History
Version of Document Summary of Changes Publication Date
v1.0 Initial Draft 12/21/16
v.1.1 Updated the date in Defects Closed with Code Change in 12/22/16
Network Advisor 14.2.0 chapter from “December 21, 2015” to
“December 21, 2016”.
Added PostgreSQL version 9.5.4.
v1.2 In Supported SAN Devices section the Footnote21 is updated 01/03/17

with the minimum recommended and minimum supported
versions of AMP OS.
v1.3 Updated the defect 628481 with the workaround. 01/10/17

Added an important note about the non-default output
directory path when saving CLI reports on Windows OS.
v1.4 Added support for JRE 1.8_u121. Added support for Brocade 03/28/17
G610 switch. Added RHEL 7.3 support.
v1.5 Updated the Important Notes for managing Brocade Analytics 06/07/17
Platform section with the patch related information for AMP
monitoring.
v1.6 Added a list of fixed CVEs in Security Vulnerability Fixes section 08/03/17
© 2016 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, Brocade Assurance, AnyIO, ClearLink, DCX, Fabric OS, FastIron, HyperEdge, ICX,
MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and Fabric Vision is a
trademark 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. shall have no liability or responsibility to any person
or entity with respect to any loss, cost, liability, or damages arising from the information contained in this
book or the computer programs that accompany it.
Notice: 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 .
Export of technical data contained in this document may require an export license from the United States
Government.
Brocade Network Advisor 14.2.0 GA Release Notes v1.6 2

Contents
Overview ...........................................................................................................................................5
Brocade Network Advisor Version 14.2.0 ............................................................................................5
New Enhancements .................................................................................................................................. 5
Important considerations for web client users ....................................................................................7
Fabric Insight Portal (new) ........................................................................................................................ 7
Deprecated and retired features .............................................................................................................. 9
Supported OS, Browsers, JRE ..............................................................................................................9
Supported Operating Systems .................................................................................................................. 9
Supported Browsers................................................................................................................................ 10
Security Vulnerability Fixes .............................................................................................................. 11
Supported Hardware........................................................................................................................ 12
Supported SAN Devices........................................................................................................................... 12
Supported NOS Devices .......................................................................................................................... 15
Supported Wireless Devices ................................................................................................................... 16
Supported Adapters ................................................................................................................................ 16
Supported vCenter versions ................................................................................................................... 18
Installing Network Advisor ............................................................................................................... 18
To install Network Advisor on Windows (Server) ................................................................................... 18
To install Network Advisor on Linux (Server) .......................................................................................... 18
To launch the Network Advisor Client .................................................................................................... 18
Before Upgrading or Installing the Software ..................................................................................... 20
System Requirements ...................................................................................................................... 20
Memory, host, and disk space requirements ......................................................................................... 20
System Requirements for Network Advisor without AMP ..................................................................... 20
System Requirements for Network Advisor with Brocade Analytics Monitoring Platform.................... 22
Operating system cache requirements ................................................................................................... 23
Client and server system requirements .................................................................................................. 23
Upgrade and Migration considerations ............................................................................................. 24
Migration Impact ............................................................................................................................. 25
Configuration Considerations ................................................................................................................. 25
Limitations and Restrictions.................................................................................................................... 26

Important Notes for managing Brocade Analytics Platform (Only for AMP users) .............................. 26
Upgrading the License ...................................................................................................................... 28
Downgrading the License ................................................................................................................. 29
User Guides ..................................................................................................................................... 31
List of Documents ................................................................................................................................... 31
Reporting Errors in the Guides................................................................................................................ 31
Known Documentation Errors ................................................................................................................ 32
Contacting Brocade Support ............................................................................................................. 33
Defects ............................................................................................................................................ 34
Open defects in Network Advisor 14.2.0 ................................................................................................ 34
Defects Closed with Code Change in Network Advisor 14.2.0 ............................................................... 46
Defects Closed without Code Change in Network Advisor 14.0.0 .......................................................... 59
Known Issues ................................................................................................................................... 66
Important SAN Notes ....................................................................................................................... 66
Display of Logical Switches ..................................................................................................................... 69
SSL connections using certificates with MD5 signatures ........................................................................ 69
Reset Ports operation in Logical Switches dialog ................................................................................... 69
Important IP Notes .......................................................................................................................... 70
Miscellaneous Important Notes that Apply to IP Installations ............................................................... 70
Boot, Monitor, Firmware Image Updates ............................................................................................... 71
Important Notes common for SAN and IP ......................................................................................... 71
Support Saves and server backup may take a long time with large databases ...................................... 75
Installation on Network Mounted Drives is not supported .................................................................... 75
Client disconnects ................................................................................................................................... 75
Cross-flavor Migration ............................................................................................................................ 75
Migrating same version of BNA (14.2.0) from OEM1 version to OEM2 version ................................ 75
Migrating BNA (pre-14.2.0) OEM1 version to BNA 14.2.0 OEM2 version .......................................... 75
Virtual Connect Enterprise Manager (VCEM) Support ........................................................................... 76
Performance Statistics Counters - Calculation Formulae ....................................................................... 76
SMI Agent ........................................................................................................................................ 77
Indications delivery depends on SAN Size and SNMP registration ......................................................... 78
CIMOM Heap Size ................................................................................................................................... 78

Logging for CIMOM ................................................................................................................................. 79
Service Location Protocol (SLP) support ................................................................................................. 79
Management SMI Agent SLP application support .................................................................................. 79
Management SMI Agent SLP application support includes the following components: ....................... 79
SLP on UNIX systems ............................................................................................................................... 81
SLP on Windows systems ........................................................................................................................ 81
Overview
Brocade Network Advisor Version 14.2.0

Brocade Network Advisor 14.2.0 is a major release supporting Fabric OS 8.1.0, NOS 7.1.0, FI 8.0.50, NI
6.1, VM insight, various enhancements to MAPS, Flow Monitoring, FCIP, Usability and troubleshooting
areas.
This release inherited the Fabric Insight Portal web client (designed in Network Advisor 14.1.x release for
AMP users only) for general SAN users to provide the user with an easy to use and intuitive interface for
monitoring IO level and fabric behavior in a Brocade Fibre Channel SAN fabric. The Network Advisor
Fabric Insight Portal also introduces Flow Collections and Flow Filtering for Analytics Monitoring
Platform flow management, and custom Rules Sets for use with MAPS for more flexible and granular
flow monitoring.
New Enhancements
 Fabric OS platform support
o Fabric OS 8.1.0x
o Brocade G610 switch with Gen 6 Fibre Channel technology
 VM Insight support
o Identify and track VMs within a fabric
o Provide VM visibility in Fabric Vision technology for monitoring and diagnostics
o Flow Monitoring
 Flow Vision enhancements
o Top N Flows/Bottom N Flows – Dashboard widget - Entity ID, VM Name and Application
name added to the Top N /Bottom N Flows widgets
o Flow Vision IOS Measures support in Historical Graph and Dashboard
 MAPS Enhancements
o VM Insight based flows
o Alert Severity Support for MAPS Rule
o Enhancement in MAPS Policy Creation

o New default Rules to Monitor Rx, TX & UTIL Measures
o New default Rules to Monitor ERR_PORTS measures
o Fabric Performance Impact (FPI) Monitoring Feature Enhancements
o MAPS Rule Name Limitations
o Monitor Front end Encryption port
o Support for uninstalling vTAPs when threshold of 250K IOPS is exceeded
o User defined policies and rules limits
o Quiet time support for SNMP
o Restriction of Orphan rules creation
 Web UI Enhancements
 AMP Enhancements
 CLI Reports
o Various reports for AMP users and general FC
 Zoning
o Alias Support in Peer Zoning
o Enhanced Zone Name Support
o Zone DB size restriction based on per chassis limit
o Alias/Zone creation by Port WWN instead of Node WWN
 D-Port Test
o Electrical and Optical Loop Back Test support for 32G QSFPs
o Support D-Port Test “Stop” Option
 Virtual Fabric
o Offline LISL state at Logical Switch creation
o FICON LS support
o 16 LS support for Gen-6 chassis
 FCIP
o 10 circuits/tunnel support
o Circuit measures in performance graphs and dashboard
o WAN Vision Dashboard
 COMPASS Enhancements
o Track Switch User Accounts
o Track Switch User Account Credential
 Web Client
o Unified Inventory
o PM support for NOS and IP
 Campus Enhancements
o Campus Dashboard
o New Syslog Formatting
o sFlow support for Campus Fabric
o Stack ISSU Support
 REST API

o Port enable/disable, Port name settings
o Peer zoning and zone alias support (Read-only)
 TRILL trunk alerting for trunk members
 Infrastructure upgrade
o JRE upgraded to 1.8.0u112
o PostgreSQL updated to v9.5.4
 Brocade Analytics Monitoring Platform support
o ampos2.0.0a
 Monitor DB data migration from 14.1.x to 14.2.0
 Support for JRE 1.8.0u121
Important considerations for web client users

This release introduces a new improved web client design - Fabric Insight Portal - replacing the web
client supported in releases BNA versions 14.0.x and earlier. The Fabric Insight Portal uses new design
paradigms for ease of use and will be enhanced going forwards. In this release the web client
functionality fully replaces the earlier web client with the following caveats:
 SAN Report Builder – this functionality is deprecated and replaced with a command line driven
set up reports for SAN FC environments.
 Global search - In this release is restricted to searches within a single instance of BNA and not
across BNA instances.
 Supportsave for NOS is not included in the new web client.
Deprecated Web Client (14.0.x)

In Network Advisor releases 14.0.x and earlier, when pointed the browser at the Network Advisor server
hostname or IP address, you were directed to a Web Page where you could access some functionality of
the Java based client through a browser. The functions, such as Dashboards, Inventory, Events, Reports,
were provided mainly in read-only mode. This client was based on software technology that is
deprecated and no longer supported. It is replaced with the Fabric Insight Portal, a browser accessible
User Interface based on cutting edge User Interface technology and modern web-based applications
workflows and paradigms.
Fabric Insight Portal (new)

The new Fabric Insight Portal provides the user with an optimized interface for monitoring and accessing
the detailed IO-level flow information provided by the Analytics Monitoring Platform. This interface was
designed to match common workflow processes users will follow when investigating application
performance, understanding workload behaviors, troubleshooting performance issues, or tuning and
optimizing a SAN environment.

Now, when the user specifies the IP address or hostname of a Network Advisor server from a standard
web browser, they will be directed to the new Network Advisor Fabric Insight Portal UI. The same
credentials used in the traditional Network Advisor client are used to login to the server.
In addition to the new interface design of the Fabric Insight Portal, the database and back-end
architecture has been redesigned in Network Advisor to provide better performance when managing a
SAN with AMP. This new architecture enables highly responsive updates in the Fabric Insight Portal,
whether for bringing up a dashboard view, drilling down into detailed information in the new
Investigation Mode, or examining lists of flows from one or multiple AMP appliances in the
environment. The new architecture and UI design also allow Network Advisor to scale and support even
more AMP flows than in previous releases.
With the introduction of the Fabric Insight Portal, some functionality that was available in the legacy
web client has been changed or removed. The following sections summarize key new features
introduced in the Fabric Insight Portal and also note functionality that has changed or is not supported
in this new interface. For details of the supported features and functions, please refer to the 14.2 User
Documentation.
Fabric Insight Portal Filters (new)

In Network Advisor 14.2, Fabric Insight Portal introduces support for Filters, a new capability that allows
user to zero in on specific AMP flows of interest. Filters allow users to quickly and easily investigate
behaviors related to a specific application, host device, or storage array and retain their filter
configuration for future use. Filters can be applied to templates, dashboards, and detailed Network
Flows information and support zones and zone aliases for easy identification of devices in a SAN.
Fabric Insight Portal Collections (new)

The Fabric Insight Portal in Network Advisor 14.2 also introduces support for collections, logical
groupings of flows identified and tracked by the Analytics Monitoring Platform. Users can define Flow
Collections to fit their needs for monitoring, performance optimization, investigation, troubleshooting,
reporting, and a variety of other purposes.
Flow Collections also support the ability to establish custom Rule Sets for the flows in a collection,
allowing users to specify IO performance and latency thresholds at unique levels for different
applications or types of storage devices. The Flow Collection Rule Sets are managed in the Fabric Insight
Portal and sent to AMP appliances to monitor the unique rules in real time and for every IO operation.
Users can also choose to create aggregate Flow Collection metrics, providing a look at IO level
performance and behaviors for the Flow Collection as a whole. This allows the SAN Administrator to
understand performance behaviors and investigate an entire storage array, application, business group,
department, or other logical grouping as a complete entity, instead of the individual flow components of
the group.
SAN Dashboards and AMP Dashboards (new)

The Network Advisor Fabric Insight Portal provides the SAN Dashboards that are most useful in
managing the SAN. In addition it provides two new Dashboards and widgets to manage, investigate, and
troubleshoot environments using AMP.
Note. Dashboards for IP Port Health are not available in the Fabric Insight Portal in Network Advisor
14.2. If your deployment contains Brocade’s IP switches and Routers, please use the standard Java
client to access the IP Dashboards or use Network Advisor versions other than 14.2.
SAN Inventory
The SAN Inventory web pages are replaced with a new and redesigned look in the Fabric Insight Portal in
14.2.
IP Inventory
IP Inventory web pages are replaced with a new and redesigned look in the Fabric Insight Portal in 14.2.
Events
The Events page is supported in the Fabric Insight Portal in Network Advisor 14.2.
Reports
The Reports capability available in the web client in previous versions of Network Advisor is not
supported in Network Advisor 14.2. Using the Fabric Insight Portal, users are able to easily export any
widget available in any dashboard or template in seconds.
Deprecated and retired features

 Bottleneck detection
For switches running FOS v8.0.0 and above Bottleneck configuration through the legacy
Bottleneck Detection dialog is not allowed. For these switches Bottleneck conditions/thresholds
configuration as well as bottleneck widgets and ports’ bottleneck status will be supported through
MAPS FPI. Bottleneck configuration and detection dialogs will still be supported for switches
running FOS version prior to v8.0.0.
Supported OS, Browsers, JRE

Supported Operating Systems
 Windows Server 2008 R2 SP1 Datacenter, Standard and Enterprise
 Windows Server 2012 R2 Standard, Datacenter
 Windows 7 Enterprise (Client only)
 Windows 8.1 Enterprise (Client only)
 MAC OS 10.12 (Sierra) (Fabric Insight Portal only)
 Windows 10 Enterprise

 Red Hat Enterprise Linux 6.8

 SUSE Linux Enterprise Server 11.3
 SUSE Linux Enterprise Server 12.0
 Oracle Enterprise Linux 7.1
Supported Browsers
Recommended browser versions:
 Internet Explorer 11 and later (Windows only, except Windows 8 and Windows 2012)
 Edge 13 (Windows 10 only)
 Firefox 41 and later (Linux only)
 Chrome 46 and later (Windows, MAC OS)
Supported JRE versions
Network Advisor version JRE version supported
14.2.0 JRE 1.8u112, JRE 1.8u121
Note 1: Web Tools launch from Network Advisor is also supported for the above combination.
Note 2: Applicable only to WebTools from Fabric OS releases done before 2/13/2015. Due to
java signing certificate expiration, the Web Tools launch from Network Advisor will not work
with JRE 8. An attempt to launch the Web Tools will be blocked and “Failed to validate
certificate. The application will not be executed” message will be shown. To work around this
issue, please uninstall JRE 8, install JRE 7 updates 79/80 and set the security level to Medium.
If you have JRE 7 installation, an attempt to launch the Web Tools will be blocked and
“Application Blocked by Security Settings” message will be shown. To work around this issue,
reduce the security level from High to Medium and continue using JRE 7 update 79/80.
Note 3: Oracle enforces the latest JRE update to be used to web start the applications. The
recommended JRE versions for this release are listed in JRE Support table. Beyond JRE expiration
date you will see the message “Your Java version is out of date” on attempt to launch the web
client.

You can either ignore the message “Your Java version is out of date” by selecting a later option
and proceed with the web start client, or install the latest released JRE patch and then web start
the client. The following warning will be shown and can be ignored: “The client system has java
version <Latest Installed JRE> but the recommended java version is <as noted in JRE Support
table>. Do you want to continue?”
Note 4. JRE 1.8.0 update 66 and later support begins with the following Fabric OS versions:
 Fabric OS v6.4.3f
 Fabric OS v7.0.2e
 Fabric OS v7.1.1c
 Fabric OS v7.1.2
 Fabric OS v8.1.0x
 Apply the following workaround on a computer when launching WebTools using a browser or
the Network Advisor Remote client for all Fabric OS versions earlier than the above listed:
a. Navigate to the jre installation directory.
On Windows, navigate to C:\Program Files\Java\jre8\lib\security
On Linux, navigate to <jre install directory>/lib/security
b. Open the java.security file and change the jdk.certpath.disabledAlgorithms=MD2,

RSA keySize < 1024 value from 1024 to 256.
For example, jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 256
 Apply the following workaround on the Network Advisor server when launching Element
Manager from Network Advisor client for all Fabric OS versions earlier than the above listed:
a. Navigate to the Network Advisor installation directory.
On Windows, navigate to <Network Advisor install directory>\jre64\lib\security
On Linux, navigate to <Network Advisor install directory>/jre/lib/security
b. Open the java.security file and change the jdk.certpath.disabledAlgorithms=MD2,
RSA keySize < 1024 value from 1024 to 256.
For example, jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 256
Security Vulnerability Fixes

This section lists the Common Vulnerabilities and Exposures (CVEs) fixes that are added in Network
Advisor 14.2.0.

 CVE-2016-3508: Unspecified vulnerability in Oracle Java SE 6u115, 7u101, and 8u92; Java SE
Embedded 8u91; and JRockit R28.3.10 allows remote attackers to affect availability via vectors
related to JAXP, a different vulnerability than CVE-2016-3500.
 CVE-2016-3485: Unspecified vulnerability in Oracle Java SE 6u115, 7u101, and 8u92; Java SE
Embedded 8u91; and JRockit R28.3.10 allows local users to affect integrity via vectors related to
Networking.
Supported Hardware
Supported SAN Devices

The following table lists the versions of Brocade firmware supported in this release. Brocade
recommends using the latest firmware versions in order to get the greatest benefit from the
network and network management.
Fabric OS version Switch or Director Type SAN Devices

FOS v8.0.1, v8.0.1a, 8.1.0x Brocade X6-4 Director20
Brocade X6-8 Director20
Brocade G620 switch17
Brocade G610 switch22
FOS v8.0.0 Brocade G62017
FOS v5.0.x, v5.1.x, v5.2.x, v5.3.x, Brocade 3250
v6.0.x. v6.1.x, v6.2.x, v6.3.x, Brocade 4100
v6.4.x, Brocade 75001
v7.0.x, v7.1.x, v7.2.x, v7.3.x, Brocade 200E
v7.4.x
Brocade 49002
v8.0.1, v8.0.1a, v8.1.0
Brocade 50003
Brocade AP76004
Brocade 3005
Brocade 51005
Brocade 53005
Brocade 650513
Brocade 651012
Brocade 652014
Brocade 784015
Brocade 80009
Brocade 12000
Brocade 780010
Brocade VA40-FC

Fabric OS version Switch or Director Type SAN Devices
Brocade Encryption Switch7
Brocade 48000 with FC4-16, FC4-32 and FC4-482 blades
Brocade 48000 with FR4-181
Brocade 48000 with FC4-162
Brocade 48000 with FC10-64
Brocade 48000 with FA4-18
Brocade DCX6 with FC8-16, FC8-32,FA4-18, and FC8-48 blades
Brocade DCX6 with FR4-18i blades
Brocade DCX with FC10-6 blades
Brocade DCX7 with FS8-18 blades
Brocade DCX10 with FCoE10-24 blades
Brocade DCX10 with FX8-24 blades
Brocade DCX-4S8 with FC8-16, FC8-32,FA4-18, FC8-48 and FC8-64
blades
Brocade DCX11 with FC8-64 blades
Brocade DCX-4S8 with FR4-18i blades
Brocade DCX-4S8 with FC10-6 blades
Brocade DCX-4S8 with FS8-18 blades
Brocade DCX-4S with FA4-18
Brocade DCX-4S10 with FCoE10-24 blades
Brocade DCX-4S10 with FX8-24 blades
Brocade DCX-4S11 with FC8-64 blades
Brocade DCX 8510-412 and DCX 8510-812
Brocade DCX 8510-412 and DCX 8510-812 with FC16-32 , FC16-48
blades and FC8-64
Brocade DCX 8510-413 and DCX 8510-813 with FC8-32e and FC8-48e
blades
Brocade DCX 8510-415 and DCX 8510-815 with FC16-64 blade
P
Brocade Analytics Monitoring Platform21
Fabric OS version Blade Type SAN Devices

FOS v5.2.x, v5.3.x, Brocade 3014
v6.0.x, v6.1.x, v6.2.x v6.3.x, Brocade 3016
v6.4.0, Brocade 4020
v7.0.x, v7.1.x, v7.2.x, v7.3.x Brocade 4016
Brocade 40241
Brocade 4018

Brocade 4012
Brocade 4424
Brocade 54102
Brocade 54502
Brocade 54602
Brocade 54242
Brocade 54702
Brocade 54802
Brocade M6505
Brocade 6547
Brocade 5430
Brocade 5431
Brocade 5432
Brocade 6546
Brocade 6548
Brocade 655816
Brocade 654319
Brocade 654218
Footnotes:
1
P Requires FOS v5.1.0 or later
2
P
3
4
5
6
7
P Requires FOS v6.1.1_enc or later
P
8
P
9
P Requires FOS v6.1.2_CEE or later
P
10
P Requires FOS v6.3.x or later
P
11
P
12
P
13
P Requires FOS v7.0.1
P
14
P
15
P
16
P Requires FOS v7.3.0_cng or later
P
17
Requires FOS v8.0.0
P
18
Requires FOS v7.4.0_ins
P
19
Requires FOS v7.3.0_hur or later
20
Requires FOS v8.0.1
21
The minimum recommended compatible version of AMP OS for sustained use is v2.0.0a. AMP OS
v2.0.0 is the minimum supported version for compatibility with BNA 14.2.0. AMP OS v1.5.0 is only
supported for temporary use to facilitate AMP migration to AMP OS v2.0.0 or later. Please refer to AMP
OS Release Notes for additional migration and compatibility information.
22
Requires FOS v8.1.0.a or later

Supported NOS Devices
Network OS version NOS Device Type
Network OS v7.0.0, v7.0.1, 7.1.0x VDX 6940-144S, VDX 6740, 6740T, 8770, 6740T-1G,
6940-36Q, 2746, 2741
Network OS v6.0.1, v6.0.1x, v6.0.2, v6.0.2x VDX 6940-144S, VDX 6740, 6740T, 8770, 6740T-1G,
2740, 6940-36Q
Network OS v6.0.0 VDX 6740, 6740T, 8770, 6740T-1G, 2740, 6940-36Q
Network OS v5.0.0, v5.0.1x VDX 6740, 6740T, 8770, 6740T-1G, 2740
Network OS v5.0.1_tcn VDX 2741

Network OS v4.0.1_hit1, v6.0.1 , v6.0.1x VDX 2746
Network OS v3.0.0_dcb3, v3.0.0_dcb4, v4.1.2, VDX 6746
v4.1.2a, v4.1.3, v4.1.3a, v4.1.3b
Network OS v4.1.0, v4.1.1, v4.1.2, v4.1.3 VDX 6740, 6740T, 8770, 6710, 6720, 6730, 6740T-1G,
2740
Network OS v4.0.0 &v4.0.1 VDX 6740, 6740T, 8770, 6710, 6720, 6730
Network OS v3.0.0, v3.0.0a, v3.0.0b, v3.0.1, v3.0.1a VDX 8770, 6710, 6720, 6730
1
Network OS v2.1P P , v2.1.1, v2.1.1a, v2.1.1b, VDX 6710, 6720, 6730
v2.1.2a
Network OS v2.1.1_fuj, v3.0.0dcb5 VDX 2730
P Supported IP Devices
FI/NI Versions IP Device Type
8.0.40, 8.0.40a, 8.0.50 FastIron ICX 7450-32ZP, 7450, 7250, and 7750
8.0.x FastIron ICX 7450, 7250, 7750
2.7.02x, 2.7.03x, 2.8.x, 2.9.x BigIron RX
7.1.x, 7.2.x FastIron FGS, FGS-STK, FLS, FLS-STK, SuperX
7.1.x, 7.2.x, 7.3.x, 7.4.x FESX, FWS
7.1.x, 7.2.x, 7.3.x, 7.4.x, 8.0.x FastIron CX, FCX-STK
7.1.x, 7.2.x, 7.3.x, 7.4.x, 8.0.x FastIron SX
8.0.x FastIron ICX 6610, 6450, 6430,
7.4.x, 8.0.x FastIron ICX 6430, 6450
7.5x, 8.0.01x, 8.0.1x, 8.0.2x, 8.0.3x Brocade 6650
5.0.x , 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5x, 5.6.x, 5.7.x, NetIron CES, CER, MLX, XMR, MLXe
5.8.x, 5.9.x, 6.0.0, 6.1.0
2.0.x, 2.1.x, 2.2.x Brocade 6910

FI/NI Versions IP Device Type
12.1. x2, 12.2. x2, 12.3.x, 12.4.x, 12.5.0x ServerIron ADX

10.2.01x , 11.0.x ServerIron
4.1.x, 4.2.x, 7.3.x, 7.4.x, 8.0.x, 8.0.01x TurboIron 24X
4.1.x , 4.1.01x FastIron FES
Footnotes:
2
P 12.1.0f and 12.2.1 are not supported
Supported Wireless Devices
Wireless Controllers Access Points FW version

ZoneFlex ZF7372
ZoneFlex ZF7982
ZoneFlex R300
SmartZone 100
ZoneFlex R310
Virtual SmartZone - Essentials (vSZ-E) 3.1.1.0.442
Ruckus ZoneFlex R700
Virtual SmartZone – High Scale (vSZ-H) 3.1.2.0.520
ZoneFlex R710
SmartCell Gateway 200 (SCG200)
ZoneFlex R500
ZoneFlex R600
ZoneFlex H500
7010 6.4.1.0
AP124
7210
7220 AP125
Aruba* 7240 AP224 6.3.1.3,
3200XM AP135 6.4.2.2_46307
3400XM AP225
3600XM AP124
RFS 4000 AP7131
4.3.1.0, WiNG 5.1,
Motorola RFS 6000 AP 7131N 5.2, 5.3, 5.4, 5.5
RFS 7000 AP 5181
* Aruba Instant Access Points are supported in Network Advisor.
Supported Adapters
For Windows, the Emulex and QLogic adapter discovery is based on Windows Management
Instrumentation (WMI).
For ESXi host, the Emulex adapter discovery is based on CIM provider.
For Brocade adapters, HCM 3.2.4 version is integrated with BNA.

Adapter Types Driver/Firmware versions
Brocade 415,425,815,825
Brocade 8041
Brocade 1010,1020,10072 Driver/Firmware Versions:
Brocade 1741 3 1.1, 2.0, 2.1, 2.2, 3.0, 3.1, 3.2, 3.2.4
Brocade
Brocade 18604 CIM Provider version:
Brocade 18675 cpba3.2.3
Brocade 18696
Driver Versions:
ESXi: 10.0.727.44
Windows: 10.0.720.0
LPe12002-M8 8Gb 2-port PCIe Fibre Channel
Adapter Firmware Versions:
ESXi: 1.1.43.3
Emulex LPe16000 16Gb PCIe Fibre Channel Adapter Windows: 1.1.43.3
LPe32002-M2 32Gb 2-port PCIe Fibre Channel CIM Provider Version:

Adapter ESXi 5.1 and 5.5: 10.0.774.0
Boot Code and Firmware Version:

11.0.243.19 (LPe32002 only)
QLE2562-CK 8Gb, Dual Port, FC HBA, x4 PCIe

Boot Code Version:
QLE2672-CK - Host bus adapter - PCI Express 3.0 01.01.38 (multi-bot image with
x4 / PCI Express 2.0 x8 low profile - 16Gb Fibre FCode for QLE269x/27xx Series
Channel x 2 Adapters)
Corp ISP2532-based 8Gb Fibre Channel to PCI Driver Versions:

Qlogic Express HBA Windows: 9.1.13.20
QLE2742 PCIe 3.0 ×8 (dual-port) 32G FC HBA Firmware Versions:

QLE2740 Single-port PCIe 3.0 x8 to 32Gb Fibre Windows: 8.00.00
Channel Adapter – SFP+
CIM Provider Version:
QLE2764 Quad-port PCIe 3.0 x8 to 32Gb Fibre ESX-5.5.0-qlogic-cna-provider-1.5.7
Channel Adapter
Footnotes:
1
P Requires v2.1.1.0 or later
2
P P Requires v2.0 or later
3
----P Requires v2.2 or later
4
P Requires v3.0 or later
5
P Requires v3.0.3 or later
6
P Requires v3.2.3 or later

Supported vCenter versions
Virtual Machine Management: vCenter and ESXi Supported Versions
ESXi 5.5, 6.0

VCenter 5.5, 6.0
Installing Network Advisor

Installation instructions are provided for the following operating systems:
1. Microsoft Windows
2. Linux
Note: The 32 Bit installer is no longer supported for any edition of the Network Advisor.
The Network Advisor Server runs as multiple services on Windows and multiple processes on Linux. They
all start automatically after the installation.
To install Network Advisor on Windows (Server)

1. Download and extract the zip archive.
2. Navigate to the Windows folder.
3. Execute install.exe.
4. Follow the instructions to complete the installation. For details refer to the Installation
and Migration Guide.
To install Network Advisor on Linux (Server)

1. Download and extract the tar.gz archive
2. Navigate to the Linux_64 folder.
3. Execute Install.bin from the File Manager window.
4. Follow the instructions to complete the installation. For details refer to the Installation
and Migration Guide.
To launch the Network Advisor Client

To launch the Network Advisor Client on the same local machine as the Network Advisor Server,
launch the client as follows:
On Windows:
 Select Start > Programs > Network Advisor 14.2.x > Network Advisor 14.2.x.
 Click the Desktop icon.
 Launch command prompt, navigate to <Install Home>/bin, type dcmclient and press
Enter.
On Linux:
 Click the Desktop icon.

 Launch terminal, navigate to “<Install Home>/bin, type sh dcmclient and press Enter.
To launch the Network Advisor Client from a remote host, complete the following steps.
Windows and Linux: Follow the below steps on launching the client from a web browser.
Note 1: The web start remote client is supported with JRE versions listed in JRE Support section
in this document. The supported JRE version needs to be installed on the remote client system
prior to establishing a server connection.
Note 2: The Remote client can be launched in the following ways

 Open a browser window and enter the Network Advisor server hostname or IP address in
the Address field.
For example:
https://NetworkAdvisorServerhost1.companyname.com/
https://192.x.y.z/
If the Network Advisor web server port number does not use the default (443 if is SSL
Enabled; otherwise, the default is 80), you must enter the web server port number in
addition to the IP address. For example, IP_Address:Port_Number. In the following
examples, 8080 is the web server port number:
https:// NetworkAdvisorServerhost1.companyname.com:8080/
https://192.x.y.z:8080/
The web client login page displays.
 Click Desktop Client.

The Network Address web start page displays.
 Choose one of the following options:

 Click the Web Start the Client link.
The Log In dialog box displays.
 Click the Download client bundle (64-bit OS only) link.
To launch the Network Advisor Client from a web browser, complete the following steps.
5. Open a browser window and enter the Network Advisor IP address in the Address bar.
For example:
https://192.x.y.z/
If the Network Advisor web server port number does not use the default (443 if is SSL
Enabled; otherwise, the default is 80), you must enter the web server port number in
addition to the IP address. For example, IP_Address:Port_Number. In the following
examples, 8080 is the web server port number:
https://192.x.y.z:8080/

The web client login page displays with the server name and IP address in the upper left.
6. Click Desktop Client to launch the Java client from any page of the web client.
Note 3: Launching element manager applications within Network Advisor Client is done using
Java Web Start technology. This requires the local system’s web browser to be able to run Java
web start applications. This setting may have been turned off in the wake of recent Java zero-
day vulnerabilities.
To turn on Java content in the browser, please follow the below steps:
1. Launch “Java Control Panel” (refer to

http://java.com/en/download/help/win_controlpanel.xml to locate Java Control Panel
application on Windows)
2. In the Java Control Panel, click on the Security tab.
3. Select the Enable Java content check box in the browser. This will enable the Java plug-in in
the browser.
4. Click Apply. When the Windows User Account Control (UAC) dialog appears, allow
permissions to make the changes. Click OK in the Java Plug-in confirmation window.
5. Now launch Element Manager from Network Advisor Client.
Before Upgrading or Installing the Software

Before you install the application, make sure your system meets the minimum pre-installation
requirements. Refer to “Pre-installation requirements” in Installation and Migration Guide. If you are
migrating data, refer to “Data Migration” chapter.
System Requirements
Memory, host, and disk space requirements
Memory requirements are only applicable when there are no other applications running on the Network
Advisor server. Paging space should be equal to or exceed the physical memory size.
Note.
When Network Advisor is installed on VM the system resources have to be dedicated to the VM.
System Requirements for Network Advisor without AMP
Below table summarizes the memory, host, and disk space requirements for a remote client.

Memory, Host, and Disk space requirements for remote client
Resources Small Medium Large
Installed Memory 4 GB 4 GB 4 GB
Processor Core Count 4

(including physical and 2 4 (2 physical, 4
logical cores) (1 physical, 2 virtual) (2 physical, 4 virtual) virtual)
Disk Space 1 GB 1 GB 1 GB
Below table summarizes the minimum system requirements for server (plus 1 client) installation.
Minimum system requirements for server (plus 1 client) installation
Resources Professional Edition Professional Plus or

Enterprise Edition
Installed Memory 6 GB 6 GB
Processor Core Count (including 2 2
physical and logical cores)
Disk Space 10GB 20GB
Below table summarizes the recommended system requirements for server (plus 1 client) installation.
Recommended system requirements for server (plus 1 client) installation

Installed Memory 16GB 16GB 16GB
Processor Core Count 2 4 8
(including physical and (1 physical, 2 (2 physical, 4 virtual) (4 physical, 8
logical cores) virtual) virtual)
Disk Space 20GB 80GB 100GB
NOTE
1. To efficiently manage more than 9000 SAN ports or 200 IP devices, the recommended memory
allocation is 16 GB. The minimum memory allocation is 2GB for the client and 6GB for the
server.
2. If you use sFlow, it is recommended that you add an additional 100 GB of disk space.
3. It is recommended that you add an additional 40 GB of disk space for the default temporary
directory.
4. If you enable periodic supportSave or configure the Network Advisor server as the Upload
Failure Data Capture location for monitored switches, you must add additional disk space. 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.

System Requirements for Network Advisor with Brocade Analytics Monitoring
Platform
Here is the minimum system requirements for BNA to manage AMP devices.
Minimum System Requirements

 RAM Memory: 16 GB
 Processor: 6
 Disk Space: 40 GB
Note: Minimum system requirements is to validate the functionality with 1 or 2 AMP devices and 100 to 200
flows. Performance issues (slowness) and longevity issues shouldn’t be reported with this system
configuration.
Recommended System Requirements
Installation resources 20K Flows 40K Flows 60K Flows 80K Flows 100K Flows
Installed Memory 32 GB 32 GB 32 GB 64 GB 64 GB
Processor Core Count 24 (12 physical, 24 (12 physical, 24 (12 48 (24 48 (24
(physical + logical) 24 logical) 24 logical) physical, 24 physical, 48 physical, 48
logical) logical) logical)
Disk Space (including 4 TB 8 TB 12 TB 16 TB 20 TB
future migration)
Server Heap 6 GB 6 GB 6 GB 6 GB 6 GB
Client Heap 2 GB 2 GB 2 GB 2 GB 2 GB
Recommended system configuration for remote java client with AMP
This is applicable for both – desktop client and browser based web client.

Installed Memory 4 GB 6 GB 6 GB
Processor Core Count 2 (1 physical, 2 4 (2 physical, 4 8 (4 physical, 8 virtual)
(including physical and virtual) virtual)
logical cores)
Disk Space 10 GB 10 GB 10 GB
When BNA monitors 10 AMPs or 100000 flows, the system requirements for server (plus 1 desktop/web
client) installation are:
 Processor: 48 core processor (24 physical and 24 virtual)
 Disk Space: 20 TB (Recommended: SSD)
When BNA monitors 10 AMPs or 100000 flows, the system requirements for the remote client (desktop
or web client) are:

 Processor: 8 core processor (4 physical and 4 virtual)
 Disk Space: 1 GB
NOTE
1. It is recommended to use only the remote client for the Brocade Network Advisor server
when managing Brocade Analytics Monitoring Platform with more than 20K flows
2. SSD storage is strongly recommended for better performance when managing Brocade
Analytics Monitoring Platform. Future releases of Brocade Network Advisor when supporting
Brocade Analytics Monitoring Platform will require the use of SSD and the storage space
requirements may increase due to additional capabilities.
3. When managing Brocade Analytics Monitoring Platform, it is recommended to use a server
with a minimum of two Processors/CPUs, with each Processor/CPU having a minimum of six
Physical cores with two or more threads (logical cores) per core, resulting in a minimum total of
24 logical cores.
4. When managing Brocade Analytics Monitoring Platform, the Brocade Network Advisor
supports a maximum of 8K switch ports in a fabric.
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.
Linux swap space requirements
Installed physical memory (RAM) size Recommended swap size

Greater than 6 GB and less than 8 GB Equal to the amount of RAM
Greater than or equal to 8 GB and less than 64 GB 5 times the amount of RAM
Client and server system requirements
Note. Network Advisor is not supported in a Network Address Translation (NAT) environment where the
server and client are on different sides of the NAT Server.
Network Advisor has the following client and server system requirements:
1. In the Professional edition, a single server supports a single client, which must be a local client
only.
2. 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 support more than 8 clients, you must make
the following changes to your configuration:

a. 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.
b. Increase the PostgreSQL database shared buffers memory allocation to 1024 MB by editing
the Install_Home\data\databases\postgresql.conf file.
Upgrade and Migration considerations

Migration is supported from the following previous releases.
Pre-14.2 release Versions
Network Advisor 14.0.x 14.0.0, 14.0.1, 14.0.2, 14.0.3
Network Advisor 14.1.x 14.1.0, 14.1.1
Note 1: Network Advisor 14.0.x (14.0.0, 14.0.1, 14.0.2, 14.0.3) and 14.1.x (14.0.0, 14.1.1) running on the Linux and
Windows operating systems can be upgraded to Network Advisor 14.2.0.
Note 2: All Network Advisor editions are supported only on 64-bit servers. To migrate Enterprise and Professional
editions to a 64-bit server, refer to ‘Pre-migration requirements when migrating from one server to another’
section of the Installation and Migration Guide.
Note 3: Direct migration from pre-14.0.0 releases to 14.2.0 is not supported. Refer to Supported migration paths in
the Installation and Migration Guide for migration paths from pre-14.0.0 releases.
Note 4: Refer to Supported migration paths in the Installation and Migration Guide for SMI Agent only migration
paths.
Note 5: SAN users may add IP management to Network Advisor 14.2.0 for SAN+IP network management with the
procurement of the IP functionality. Also, IP users may add SAN management to Network Advisor 14.2.0 for
SAN+IP network management with the procurement of the SAN functionality.
Note 6: Make sure minimum of free space is 1.5 times the size of the Network Advisor data folder
(<Install_Home>\data) available for performing migration for the servers with large amount of Performance,
Events, and Flow Vision data in the database.
Note 7: Network migration is not supported from 14.0.x releases to the 14.2 release.
Note 8: Network migration is supported from 14.1.x to 14.2.0 release.
Note 9: Cleanup the monitor entries in BNA Database during the Migration case (pre-14.1.x)
 When customer migrates from pre-14.1.x release to 14.2.0, following AMP related data would be removed in
14.2.0 after migration:
o Flows retrieved from AMP in pre 14.1.x release
o Dropping all statistics retrieved from AMP in pre 14.1.x release
o Out of the box dashboards, added in 12.4.2 and 12.4.3 release for AMP

 SAN Analytics Monitoring: Top Flows
 SAN Analytics Monitoring: Summary
 There are no changes made to the source (pre 14.1.x release) database. Customer can install respective pre
14.1 release and consume this data.
Note 10: Monitor entries migration from 14.1.x releases to 14.2.0 release is supported.
Migration Impact
If the OEM name for any of the switch models has changed from one release to another, then you will
need to change the properties file after migration. To see these new names, edit the existing Model
name with that of the new name in the “oem-switch-model-mapping.properties” file located in the
‘conf’ folder of BNA home location and restart the server for changes to take effect.
Brocade Network Advisor downgrade to previous versions is not supported.
Configuration Considerations
Supported scalability limits by Network Advisor edition
Enterprise Edition Professional Plus

Professional
Edition + IP Base
Small Medium Large Edition
Edition
SAN Switch Ports 2000 5000 15000 2560 300
SAN Switches and
40 100 400 40 15
Access Gateways
SAN Devices 5000 15000 40000 5000 1000
SAN Fabrics 25 50 100 36 2
1550 (Supported)
1200 (recommended)
IP Switches* 50 200 (with performance 50 50
monitoring on up to
20000 ports)
MPLS switches 1 10 100 1 Not Supported

VDX switches 50 100 400 50 50
Managed Hosts 20 100 400 100 20
vCenters 1 5 10 5 1
VMs
(includes powered 1000 5000 10000 5000 1000
down VMs)
ESX Hosts 200 1000 2000 1000 200
*The IP switch count includes MPLS and VDX switches.

Note 1. Virtual Fabrics are counted as fabrics when calculating the managed count limits.
Note 2. SMI Agent is not supported on Professional edition.
Note 3. Professional Plus is not supported for the IP package.
Note 4. Supported network latency between Network Advisor server and client or server and devices is
100ms.
Limitations and Restrictions

Qlogic branded Brocade adapters are not supported for discovery.
Important Notes for managing Brocade Analytics Platform (Only for AMP users)
1. To monitor Analytics Monitoring Platform with Brocade Network Advisor 14.2.0, additional patches need to be
applied to the application. Please contact support for more information.
2. Backup and restore recommendations
a) With AMP discovered in Network Advisor, for Back up, it is recommended to use with External device
with since backing up to CD is not the recommended method. The usable capacity of a CD is
i. Approximately 700 MB and needs to be replaced when full. It is recommended that you
configure the backup system to target a hard drive or a network drive.
ii. Note that: The amount of space required for each backup is 1/10th of the size of BNA
installation directory and the backup process takes about 1.5 hours for 100GB of data.
b) By default, the Network Advisor server backup is scheduled for every day - a backup every 24hrs.
With AMP discovered in the Network Advisor, since the data size will be huge,
i. If user needs better BNA performance, it is recommended to disable the default scheduled
back by disabling the “Enable Backup” option (also shown in the figure below) and trigger a
manual backup on a weekly basis or based on the need, by enabling the “Enable Backup”
check box and selecting “Backup Now” button.
ii. If user needs the data back up every day, then the performance of the BNA will be impacted
due to the backup process. Based on the need, the backup can be planned.

3. Support save recommendations
a) With AMP discovered in Network Advisor, for capturing the Server and Client support save data,
it is recommended to select the Partial option, this would exclude historical performance data
and events from the database capture.
4. Disk space recommendation in case of Migration

a) It is recommended to have free disk space of 3 times the size of “BNA installation folder/data”. Note
that it would take approximately 2 hours to complete the migration for 100G of data folder size.
Example:
Size of the “BNA installation folder/data” is – 500 GB
Additional free disk space required is - 1000 GB (1.5 TB)
Time that will take for completing migration would be – 10 hours approximately.
4. Performance considerations for Dashboard

a) When there are more than 30k flows monitored in BNA
i. It is recommended to select the 30 minutes or 1 hour time scope for better performance of
the drill down graphs/dialogs
ii. The drill down graph/dialog launch will take around 5 minutes when user selects 6 hours/12
hours/1 day time scope.
5. An AMP device should be discovered by only one BNA server
Upgrading the License
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.
SAN Upgrade Paths
Current software release To software release

SAN Professional Plus or Licensed version
SAN Enterprise Trial or Licensed version
SAN + IP Professional Plus Licensed version
SAN Professional SAN + IP Enterprise Licensed version
SAN Enterprise Licensed version
SAN Professional Plus Licensed Version SAN + IP Enterprise Licensed version
SAN Enterprise Licensed version
SAN Enterprise Trial SAN + IP Enterprise Trial or Licensed version
SAN Enterprise Licensed version SAN + IP Enterprise Licensed version
IP Upgrade Paths

IP Base Trial or Licensed version
IP Professional SAN + IP Enterprise Licensed version
IP Base Licensed version
IP Base Trial SAN + IP Enterprise Licensed version
IP Base Licensed version (higher count)
IP Base Licensed version (lower count) SAN + IP Enterprise Licensed version

SAN+IP Upgrade Paths

SAN + IP Professional SAN + IP Enterprise Trial or Licensed version
SAN + IP Professional Plus Licensed version SAN + IP Enterprise Trial or Licensed version
SAN + IP Enterprise Trial SAN + IP Enterprise Licensed version
License Upgrade procedure in Network Advisor
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).
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.
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.
Downgrading the License

User can downgrade from a higher Trial configuration to a licensed version with a lower
Configuration. User can perform the following types of downgrade:
• Edition
• Package
• MPLS
• IP Product Count
NOTE:
1. Downgrade to Professional Edition is not supported.

2. Downgrading to a Trial version is not supported.
3. Downgrade during migration (Configuration Wizard) is not supported.

4. License downgrade operation will not run when IP Profile discovery and Server Backup are in
progress.
5. If you combine more than one downgrade option, you must meet the requirements for all downgrade
options.
Edition Downgrade Paths

Professional Plus SAN + IP
Enterprise SAN + IP Professional Plus SAN
Professional Plus SAN + IP
Enterprise SAN Professional Plus SAN
Package downgrade paths

Enterprise SAN
Enterprise IP
Enterprise SAN + IP Professional Plus SAN
Enterprise SAN
Enterprise IP
Professional Plus SAN + IP Professional Plus SAN
Enterprise SAN
Enterprise IP
Professional SAN + IP Professional Plus SAN
MPLS Downgrade Paths

Enterprise SAN + IP with fewer MPLS
Enterprise SAN + IP without MPLS
Enterprise IP with MPLS
Enterprise IP without MPLS
Professional Plus SAN + IP without MPLS
Enterprise SAN + IP with MPLS Professional Plus SAN + IP with fewer MPLS

Enterprise IP with fewer MPLS
Enterprise IP with MPLS Professional Plus SAN + IP with fewer MPLS

Enterprise IP with MPLS
Professional Plus SAN + IP with MPLS Professional Plus SAN + IP with fewer MPLS
IP Product count downgrade paths
Enterprise SAN + IP with fewer products

Professional Plus SAN + IP with fewer products
Enterprise SAN with SMI Agent + IP Enterprise IP with fewer products
Enterprise IP Enterprise IP with fewer products
Professional Plus SAN + IP with fewer products
Professional Plus SAN with SMI Agent + IP Enterprise IP with fewer products
User Guides
List of Documents
You can download the software and documentation from the MyBrocade website.
 Brocade Network Advisor Installation and Migration Guide
 Brocade Network Advisor SAN User Manual
 Brocade Network Advisor SAN User Manual (AMP)
 Brocade Network Advisor SAN + IP User Manual
 Brocade Network Advisor SAN + IP User Manual (AMP)
 Brocade Network Advisor IP User Manual
 Brocade Network Advisor Software Licensing Guide
 Brocade Network Advisor Port Commissioning Quick Start Guide
 Brocade Network Advisor REST API Guide
 Brocade Network Advisor SMI Agent Developer’s Guide
 Virtual Connect Enterprise Manager Server Guide
 Brocade Analytics Monitoring Platform User Guide
Refer to www.brocade.com or http://my.brocade.com for latest versions of the documents.
Reporting Errors in the Guides

Send an email to documentation@brocade.com to report errors in the user guides.

Known Documentation Errors
 In the Network Advisor SAN + IP User Manual (Part Number: 53-1004879-01), SAN User Manual
(Part Number: 53-1004880-01), IP User Manual (Part Number: 53-1004881-01), SAN+IP_AMP User
Manual (Part Number: 53-1004879-01), SAN_AMP User Manual (Part Number: 53-1004935-01),
replace 14.0.1 references to 14.2.0.
o Launching Configuration Wizard section of the Getting Started Chapter should replace
14.0.1 to 14.2.0 as follows:
“NOTE
You can only restart the server using the Server Management Console (Start > Programs >
Management_Application_Name 14.0.1 > Server Management Console).”
“ On Windows systems, select Start > Programs > Management_Application_Name 14.0.1>

Management_Application_Name Configuration.”
 In the Network Advisor SAN_AMP_IP User Manual 14.2.0 (Part Number: 53-1004934-01), SAN_AMP
User Manual (Part Number: 53-1004935-01):
o Firmware requirements section should read:
“After migration from 14.0.x, you must enable the Monitor service for monitoring
the Brocade Analytics Monitoring Platform”.
o Upgrade and Migration considerations section should show the following table:
Release Version
Network Advisor 14.0.x 14.0.1, 14.0.2,14.0.3
Network Advisor 14.1.x 14.1.0, 14.1.1
o Following NOTEs should read:
“Direct migration from pre-14.0.x releases to 14.2.0 is not supported. Refer to

Supported migration paths in the Installation Guide for migration paths from DCFM,
INM and pre-14.0.x releases.”
“SAN users may add IP management to Network Advisor 14.2.0 for SAN+IP network
management with the procurement of the IP functionality. Also, IP users may add
SAN management to version 14.2.0 for SAN+IP network management with the
procurement of the SAN functionality”
“Network migration is not supported from 14.0.x releases to the 14.2.0 release.”
o Following NOTE should be removed from SAN_AMP_Manual and in SAN_IP_AMP_Manual:

“If pre 14.1 version having AMP firmware 1.4 / 1.5, upgrade the AMP to 2.0 after
migrated to 14.1 and before enabling the AMP services. Historic data for AMP flows
from pre-14.1 will not be migrated to 14.1.x after migration.”
 In the Network Advisor Installation and Migration Guide, 14.0.1 (Part Number: 53-1004149-02), add
the following details.
1. In the section “Linux swap space requirements”, change “Greater than 4 GB and less than 8 GB”
to “Greater than 6 GB and less than 8 GB”.
 In the Network Advisor SAN Installation and Migration Guide, 14.0.1 (Part Number: 53-1004150-02),
add the following details.
1. In the section “Linux swap space requirements”, change “Greater than 4 GB and less than 8 GB”
to “Greater than 6 GB and less than 8 GB”.
Contacting Brocade Support

Contact your Network Advisor provider for software support. To expedite your call, have the following
information immediately available:
 Technical Support contract number, if applicable

 Network Advisor edition
 Network Advisor version
 Detailed description of the problem, including the supportsave data, screen shots of
the problem if applicable
 Description of any troubleshooting steps already performed and the results
To contact Brocade, go to http://www.brocade.com/services-support/index.page for the latest e-mail

and telephone contact information.

Defects
Open defects in Network Advisor 14.2.0

This section lists the open defects with Critical, High and Medium Technical Severity as of December 21,
2016 in Network Advisor 14.2.0
.Defect ID: DEFECT000450299

Technical Severity: Low Probability: Medium
Product: Brocade Network Advisor Technology Group: Device Management
Reported In Release: Network Advisor12.0.2 Technology: Device configuration (SAN)
Symptom: Operation never completes and user unable to proceed with any more decommission request
Condition: Performing decommission operation on discovered CIMOM.
Defect ID: DEFECT000541621

Technical Severity: Medium Probability: Medium
Symptom: FCIP circuit trace route verification fails when attempted from BNA on DCX and DCX8510-4XT
Condition: Run FCIP trace route tests on DCX and DCX8510-4XT
Workaround: Use CLI to run the tests

Technical Severity: High Probability: Medium
Product: Brocade Network Advisor Technology Group: Client
Reported In Release: Network Advisor12.4.0 Technology: Active Sessions
Symptom: Trace route on Ethernet fabrics failed with the reason "Timed out waiting for response"
Condition: Launch Trace route on a VDX 2741 running firmware 5.0.1

Reported In Release: Network Advisor12.4.0 Technology: Device configuration (General)
Symptom: Sync/Sync All operation on BNA's COMPASS feature which involve templates that have only a
subset of the three AAA settings (RADIUS, LDAP, TACACS+) causes the other subset to be
removed (if configured) on the synced switches & AGs.
Condition: Issue may be observed under the following condition,
When the monitored switches and AGs have been configured with a subset of the three AAA
settings, RADIUS, LDAP, TACACS+ (For Example: Only RADIUS servers are configured) and the
COMPASS template with which they are being synced via the Sync/Sync All operation has been
configured with a different subset of the three AAA settings (For Example: LDAP and TACACS+).
Workaround: The COMPASS template can be created by first importing the current AAA settings from the
switch/AG and then configuring it further as needed for monitoring before performing the link
and subsequent sync/sync all operations.
As per the Fabric OS design, all three AAA servers (RADIUS. ADLDAP, TACACS+) have to be
configured together. All three AAA server settings should be present in the configuration file
(from COMPASS), when we want to add any one server additionally (RADIUS, ADLDAP,
TACACS+). This can be achieved in COMPASS using “Import from Switch” and “Edit” options.
For example, let’s say all the three AAA servers are configured on switch. From COMPASS, if
we try to push only ADLDAP configuration during sync operation then already configured
RADIUS and TACACS+ configurations on switch will get removed. The template configuration
present in the configuration file will get downloaded to switch replacing the existing
configuration.

Recovery: The removed AAA settings can be restored by performing a previous switch configuration restore
via BNA's Configuration File Manager feature.

Product: Brocade Network Advisor Technology Group: Management
Reported In Release: Network Advisor12.4.1 Technology: Configuration Fundamentals
Symptom: Although the firmware download was successful, the error message "Active and Standby CPs
failed to gain HA synchronization within 10 minutes” was shown in Network Advisor.
Condition: Intermittently observed only on director class switches.

Symptom: Customer is not able to discover or get the recent details from switch.
Condition: The Ethernet interface of the Windows machine where the application is installed behaves
wrongly.
Recovery: Once the server is restarted . user can see the recent data from switch and he is able to discover
new FOS switch.

Product: Brocade Network Advisor Technology Group: Device Monitoring
Reported In Release: Network Advisor12.4.2 Technology: Reports
Symptom: User is unable to view the device properties connected to the stack other than unit 1.
Unable to remove the port from custom port group.
Link is shown between VDX and ICX in L2 topology.
Unable to get syslog/events from vdx.
Condition: Multiple issues related to VDX and ICX stack switch.

Product: Brocade Network Advisor Technology Group: Fault Management
Reported In Release: Network Advisor12.3.2 Technology: SNMP Setup
Symptom: BNA sends a "Cold Start" trap after password changes made to FOS switch
Condition: Password changes on switches that are managed by BNA, cause an SNMP trap to be
forwarded through BNA CIMOM

Reported In Release: Network Advisor14.0.0 Technology: Firmware Management
Symptom: The traffic disruption message is shown while performing Hot Code Load on switches when
16G and 32G are connected
Condition: When different models of 16G and 32G capable switches with or without ISL is selected for Hot
code load from Network Advisor

Symptom: Incorrect source and destination information is displayed for the sub flows

Condition: Learning flow is created with ingress / egress port as F port

Reported In Release: Network Advisor12.4.2 Technology: CLI Configuration (IP)
Symptom: User will not able to configure NTPv4 from Network Advisor
Condition: This issue is specific to ICX7450
Workaround: User can use CLI to configure the NTP

Reported In Release: Network Advisor14.0.1 Technology: Flow Vision (SAN)
Symptom: 6 sec values are shown for the IOS measures in real time graph dialog instead of 20 secs data
Condition: Launching real time graph for the flows from the Gen 6 platform switches sometimes shows
incorrect values (6 secs instead of 20 secs data).

Symptom: Mirrored frame count is not populated for vTap flows
Condition: Move the sys_analytics_vtap flow to the right hand side panel in flow vision dialog for an AMP
switch. The flow measure on both historical and real time counters were shown blank.
Workaround: Use CLI output to view the correct values.

Reported In Release: Network Advisor14.0.1 Technology: Events
Symptom: In the Network Advisor Master Log the " Link up on port unknown " message is shown for
Brocade X6-8 Director.
Condition: Brocade X6-8 Director is being managed by the Network Advisor; IO is running. Issue is
observed after enabling VF and creating new FID on Brocade X6-8 Director.

Symptom: Values are not getting populated for the flows which was created through defined flow from
subflow,
Condition: Create a flow with * in source and destination and make sure traffic values are getting
collected in subflow for a EX port. Create a static flow from the subflow for 2 edges and the
values are not getting populated.

Symptom: Unable to select luns from flow vision dialog as it is throwing error message

Condition: Discover the host connected to a Gen 6 platform, with LUNs configured and detected in
properties dialog. An error "There are no LUNs in fabric" error message pops up on launching
the picker dialog in flow add dialog.

Symptom: Unable to see the sub flows for a selected flow definition
Condition: Create a flow which has source / destination as * and specify the LUN ID.Select the flows from
the left hand panel in flow vision dialog to right hand panel.

Reported In Release: Network Advisor14.0.1 Technology: Topology Views
Symptom: Additional port info displays shows status of E-Ports for F-Ports
Condition: This happens intermittently when we do blade level decommission or recommission operation

Symptom: Master log event description is blank for one of the Management Server Events.
Condition: In Network Advisor, the Master log shows a blank Description for one of the Management
Server Events for v8.0.1a fabrics with running traffic.

Reported In Release: Network Advisor14.0.2 Technology: Device configuration (IP)
Symptom: Client Count attribute is always shown as 0 in the properties of the Access Point managed by
the Ruckus controller.
Condition: Issue observed when Ruckus controller is discovered and managed by the Network Advisor.

Symptom: The correct gateway value is not being displayed when viewing the FCIP Tunnel Circuit
information for the remote side gateway.
Condition: Issue observed in a 10G FCIP tunnel setup when using IPv6 instead of IPv4 for the network.

Technical Severity: Medium Probability: Low
Reported In Release: Network Advisor14.1.0 Technology: Dashboards
Symptom: Colors change for the existing measure when a new measure is selected in the widgets in
Dashboard.
Condition: Add or remove measures to the widgets and the line chart color will change for each new
measure added.

Reported In Release: Network Advisor14.1.0 Technology: User Accounts
Symptom: Help dialog is not launching in Add User dialog
Condition: Launch Add User dialog and click 'Help' button.

Symptom: MAPS violation lookup dialog from summary widget shows all violations (both IT & ITL
violations).
Condition: The ITL violations are not rolled up to to parent IT. As a result, the violations might be double
counted in below cases if time-based rules are configured:
1. Collections
2. Initiator/Target port violation widgets

Technical Severity: Medium Probability: High
Symptom: The Close button on the FCIP Tunnel/Circuit Configuration Report window will be disabled.
Condition: When Network Advisor tries to roll back the failed tunnel configuration, the rollback also fails
and it is not able to complete the tunnel creation operation
Workaround: Use the close window "X" in the upper right corner to close the window.

Technical Severity: High Probability: High
Symptom: The Fabric Initiator Target Latency metric does not match the value shown in CLI.
Condition: In Flow list and investigation mode, for the metric Fabric I-T latency.

Reported In Release: Network Advisor14.2.0 Technology: Call Home
Symptom: Call Home is not getting triggered for Embedded switch platforms.
Condition: Issues is observed when the embedded platform switches Brocade 6546 and Brocade 6545
are assigned to any call home center.

Product: Brocade Network Advisor Technology Group: Monitoring
Reported In Release: Network Advisor14.0.1 Technology: Hardware Monitoring
Symptom: Real time graph do not plot the values for the discovered switches
Condition: Real time Graph does not plot after un-managing the Host that was used as initiator/target
during flow creation.
Recovery: Rediscover the fabric and try again.


Symptom: Deployment of sFlow with a custom sample rate fails with "Wrong value occurred" error.
Condition: Seen when attempting to deploy sFLow with the custom sample rate on selected available
products.

Symptom: Firmware download fails when using SCP option.
Condition: Issue is seen when attempting the firmware download using SCP option.

Reported In Release: Network Advisor14.2.0 Technology: Policy Monitor
Symptom: "Not Found" error is being shown when trying to email Configuration Policy Manager Report
from the browser.
Condition: In Network Advisor discover some NOS FOS and IP devices, from Monitor -> Configuration
Policy Manager, run the policy and launch the report by giving the information. Click the Send
button and observe that “Not Found” error is being displayed, although the report is emailed
out.

Symptom: After successfully configuring sFlow via Network Advisor, sFlow reports cannot be viewed in
Monitor sFlow dialog.
Condition: Issue is observed when the switch is not able to transfer the UDP packets due to network
problem.

Symptom: Network Advisor FCIP Tunnel dialog will popup error stating that Default Switch not Managed
Condition: When a pair of SW7840 is locked in a IPEX tunnel and resides in the logical fabric and has
GiGE ports in the respective SW7840 Default Partitions.

Symptom: The partition dialog in Network Advisor will be unresponsive
Condition: When user tries to move ports from one partition to another, the ports are not enabled after
the port movement and the dialog is unresponsive


Symptom: Will not see violations for the flows having same initiator, target, lun and vtap from different
fabrics
Condition: if the same initiator, target, lun and vtap from different fabrics are configured to collections and
deployed

Symptom: Zoning Compare dialog wil be non-responsive
Condition: When user tries to compare the zoning configuration whose size is 1 MB

Symptom: The topology will show the device as not managed for few minutes even though it is managed.
Condition: User tries to create more than 8 partitions using Network Advisor partition management dialog
for a chassis at a given time
Workaround: User can create the partitions in the batches of four at a time for a given chassis

Symptom: Firmware download to NetIron XMR-MLX switch from a Network Advisor fails.
Condition: Issue is observed in Network Advisor running on Linux platform.

Symptom: Network Advisor presents a warning that VE Ports address-assignments are not supported
Condition: When user tries to move an entire FX8-24 (Extension) blade into a FICON-created Logical
Switch and enabled for Addressing.

Symptom: Violations are not displayed correctly in the Top N widget for flows.
Condition: Issue is observed in the user defined traffic flows widget with the active VM flow. .

Reported In Release: Network Advisor14.2.0 Technology: MAPS - Monitoring and Alerting Policy
Suite
Symptom: F-Port will only get fenced instead of port decommission
Condition: When the MAPS threshold is exceeded for the MAPS rule which is configured for the port
decommission and fenced action and the password is not configured for CIMOM server

Symptom: The tunnel configuration dialog will indicate the rollback is failed.
Condition: When user tries to modify the tunnel configuration for two switches - Switch A and Switch B, if
the Switch B configuration failed then the configuration made on the Switch A will not be rolled
back
Workaround: Use CLI to change the switch configuration

Symptom: Firmware downgrade for NetIron LP Boot image will be getting failed with "First Token Within
the File Name is invalid" when using SCP
Condition: Issue observed when:
1. Product communication is set as SSH
2. Configuration file transfers as SCP
Workaround: With the below configurations Firmware download can be performed successfully for NetIron
LP Boot image
1. Product communication is set as TELNET

2. Configuration file transfers as TFTP

Suite
Symptom: User will get maximum 500 rules reached message even though the maximum limit of rules is
not reached
Condition: When user try to create 500 rules each for two different user defined policies

Symptom: The trap which is sent after the MAPS quite time expiry will not have the correct violation count.
Condition: This issue will be seen for all the MAPS rules configured with SNMP trap action and quite time.

Symptom: Historical graph data not being collected for FC ports on the fx8-24 blade installed in a Brocade
8510 switch and 'No Data Points' found error shown.
Condition: When attempting to collect FC data for fx8-24 blade in Brocade 8510.

Symptom: Occasionally a huge spike is seen in real time graph for IOS measures where graph plots to
zero and then to some non-zero value.

Condition: Observed on launching the real time graph for IOS measures.

Symptom: Network Advisor will allow user to enable/disable HIF mode for FICON LS.
Condition: User will see this issue while configuring FICON LS in the partition dialog.

Symptom: While generating fabric Summary report, the switch and connected switch port details will be
empty.
Condition: This issue will be seen for Fibre Channel Routing fabric

Suite
Symptom: FICON host is not notified when a port statistics threshold is exceeded on a F-Port, but no
subsequent notification is sent for the fenced port by Network Advisor
Condition: When FMS enabled and MAPS is running with the FENCE action enabled and port is fenced by
Network Advisor

Symptom: The topology will incorrectly show that there is a link between GE port and VE port for the FCIP
tunnel.
Condition: User will see this issue when a fabric with switch A has shared GiGE port and Switch B has a
physical GiGE port present in it.
Workaround: Relaunch the client

Symptom: Occasionally the Network Advisor exceeds the number of HTTP sessions to the switch while
trying to do a firmware download on a DCX 8510.
Condition: Issue observed during firmware download on a DCX 8510 with 16 LS.

Symptom: For pizza box devices the addressing mode will be displayed as disabled
Condition: When user tries to create FICON LS for the pizza box devices

Symptom: When creating FICON enabled logical switches via Logical Switch management dialog, creation
may fail with "No response from switch (read timeout)" error.
Condition: Issue is observed when multiple LS are created simultaneously using Network Advisor.
Workaround: For FICON environments, it is highly recommended to limit the Creation, Modification, or
Deletion of Logical Switches from Network Advisor’s Logical Switches dialog to less than 4 LS
at a time to avoid timeout issues.

Symptom: While create a new FICON logical switch the user is not given the pop-up to bind the ports while
being moved to the newly create logical switch on Gen5 (DCX+). When doing this same
operation on Gen6 (Venator) the user is presented with a pop-up that allows the binding to take
place.
Condition: 1. Gen5(DCX+) switch with FOS 8.1
2. Switch is monitored by BNA.
3. Try to create new FICON logical switch.

Symptom: Intermittently the topology shows the ISL with the broken line, bearing the missing icon, after
the E-port connection is being restored.
Condition: Issue observed after pulling out and then restoring the physical connection between director
switches.

Symptom: CLI "Collection Aggregated Time Series Report" report generation fails with “Database
Connection Failed!" error, even though the Mater log shows and entry for successful
authentication.
Condition: If Network Advisor server bound to specific IP Address, the report generation would fail.
Workaround: The workaround is to bind BNA server to “All” (Host name). The server Bind address can be
configured through Options dialog or by re launching configuration wizard.

Symptom: Although Zone names cannot begin with a numeric character or a special character. the
Network Advisor documentation incorrectly reads this:
Please include the below sentence :

(Zone names, Zone configuration names, and Alias name can begin with an alpha numeric
character and can have one or more special characters “ _” , "-", "$", "^".)
Condition: Issue exists in the SAN AMP and SAN+IP AMP user guides.

Reported In Release: Network Advisor14.0.2 Technology: Discovery
Symptom: On some switches the real time performance graph stays empty.
Condition: The issue observed in migrated Network Advisor.

Symptom: In the partition management status dialog - delete logical switch failed Reason: No response
from switch(Found) will be shown as status
Condition: When user tries to delete LS in the partition management dialog from Network Advisor
Workaround: Workaround would be to delete individual Logical Partitions.
Recovery: No recovery was needed because the deletion operation was actually successful.

Symptom: In the partition management status dialog - create logical switch failed Reason: VF is not
manageable even server sleeps for 20 seconds on core switch
Condition: When user tries to create eight LS and without moving the ports in the partition management
dialog from Network Advisor

Reported In Release: Network Advisor14.1.0 Technology: Installation & Migration
Symptom: In one instance the Network Advisor migration failed and rolled back to the previous version.
Condition: Issue observed while migration from Network Advisor version 14.0.1 to 14.1.0.

Symptom: Unable to proceed with the Network Advisor installation with a selected preferred IP Address.
The “port 22 is occupied” error message is shown in port configuration page.
Condition: Issue observed in a dual NIC server with both NICs configured with IP addresses, when scp/ftp
server is running with Ethernet address 1 as a preferred IP address. In this case, even though
the ports associated with other Ethernet IP address are free, the error message is shown.

Symptom: Report generation failed message will be displayed when user tries to generate report through
report CLI.
Condition: When the BNA host's preferred IP address is IPv6
Workaround: Change the preferred IP address to host name

Symptom: Network Advisor displays the unsupported IOS measures for a flow on a Brocade G620 switch
Condition: Launch historical or real time graph for a flow with “Target” device as source and “HBA” port as
destination on a Brocade G620.

Symptom: CLI command portstatsshow reports a non-zero value for
er_rx_c3_timeout attribute.
Condition: The issue is seen when querying the CIM class Brocade_SwitchFCPortStats.

Product: Brocade Network Advisor Technology Group: Partner Integration
Reported In Release: Network Advisor14.2.0 Technology: SMI Agent
Symptom: Indications are not received when server is configured with raw IPv6.
Condition: Observed in raw IPv6 server.

Symptom: Indications are not received when server is configured with pure IPv6 and a
"java.lang.NoClassDefFoundError" exception is thrown.
Condition: Issue observed in pure IPv6 server with SMI Agent enabled.

Symptom: Occasionally the switch manageability is being lost and topology shows the switch as not
managed.
Condition: Issue observed on Brocade X6-4 and Brocade X6-8 devices during creation of a new Logical
Switch with FICON enabled via Network Advisor.

Symptom: Collection Aggregated Time Series Report and Collection Aggregation Report generation failure
observed.
Condition: The report generation fails when the measure for the report is specified as wr_pend_io,
othother_cmd_latency, other_cmd_latency_io the report.


Symptom: Intermittently a "java.lang.NoClassDefFoundError" is shown and indications are not received
with neither http nor https.
Condition: Issue seen when attempting to create indication subscription in SMIA client bundled within the
Network Advisor.

Symptom: NullPointerException is thrown when attempting to run CLI report "Collection Violations Report"
with a ctag.
Condition: Issue is observed when ctag parameter is specified.

Symptom: Fabric Latency Average value, displayed in Network Advisor, is greater than Max value due to
rounding off the millisecond values.
Condition: Issue is observed in Collection Dashboard widget for Fabric Latency Average value on Analytics
Monitoring Platforms.
Defects Closed with Code Change in Network Advisor 14.2.0

This section lists the defects with Critical, High and Medium Technical Severity closed with a code
change as of December 21, 2016 in Network Advisor 14.2.0.

Symptom: Gateway and MTU size fields are not updated while IPv6 circuit is edited in Network Advisor.
Condition: Perform IPv6 circuit create or edit operation from Network Advisor. The subsequent editing of
IPv6 circuit is not successful.
Workaround: Close and launching the FCIP Tunnel dialog.

Reported In Release: Network Advisor12.4.0 Technology: Third-party tools
Symptom: SLP service fails to start during installation. User cannot start the service from Server console
either.
Condition: When installing Network Advisor server on a 64-bit Linux OS.


Symptom: For a valid and functional flow mirror, the 'Destination Device' column does not show the
destination device’s WWN.
Condition: When the switch is part of both monitored and un-monitored fabrics.

Reported In Release: Network Advisor14.0.1 Technology: Troubleshooting
Symptom: D-port test hangs
Condition: When user selects more than one port to run the D-port test, D-port test is running for ever.
Workaround: Run the D-port for each port individually

Symptom: AG fabric N-Ports connections are not displayed in Topology.
Condition: Issue observed on G620 after changing the switch mode to AG.

Symptom: SNMPv1 TRAP “ospfNbrStateChange“and “ospfIfStateChange“generated by MLXe or ICX shown
as “Unsupported Trap".
Condition: Perform CLI “disable” over interface eth1/1, it makes eth1/1 link down state and OPSF neighbor
down MLX generates SNMP traps including “ospfNbrStateChange“and “ospfIfStateChange“.

Reported In Release: Network Advisor14.0.0 Technology: RESTful API
Symptom: "500 internal error" is shown when incorrect login credentials provided for login call.
Condition: Issue is observed when incorrect login credentials are provided for rest login call.

Symptom: Need to update status code or error message code for "404 not found" and need to show the
error message instead of "500 internal server" in control zone transaction request API.
Condition: if the user makes a rest request for control Zone transaction with wrong uri then user can't able
to see the proper error message as a response for the request failure.
Instead user will get response as 500 Internal server error.
Recovery: Needs to make a rest call with correct URI for the Control Zone transaction request.

Symptom: Support save collection with external SCP is failing for all platforms
Condition: When user chose external SCP protocol for collecting Switch Support its getting failed to collect
the Support Save

Workaround: User can chose internal FTP or SCP to collect Switch Support Save

Suite
Symptom: Intermittently policies keep loading indefinitely in the MAPS configuration dialog
Condition: Observed on NOS 7.0.0 switches

Reported In Release: Network Advisor14.0.1 Technology: Performance
Symptom: Customer will not get the values for historical and realtime graph values.
Condition: When user discover the Network OS device with 100g,40g and 10g ports and apply historical
graph for list of the ports. User will not see the values for some of the ports in performance
graph.

Suite
Symptom: MAPS config dialog is loading for a long time and unable to close the progress dialog.
Condition: Happens in rare scenario when the devices are responding slowly to get the MAPS configuration
details by the time the application request is timed out

Symptom: Network Advisor indicates failure to deploy previously saved configuration due to timeout,
although it was successful.
Condition: Issue is observed when device configuration is large and it takes longer time for device to
respond to Network Advisor.
Workaround: User can go back to configuration repository dialog, get the latest configuration and compare
the time stamps and ensure the correct status.

Symptom: "Token in header is null or empty" error message not showing in BNA REST Response when run a
request without WStoken property.
Condition: If the user makes a Rest call without WStoken other than login request the Response is showing
as 500 Internal server error instead of "Token in header is null or empty" error message.
Recovery: 1> user needs to enter WStoken for all of the Rest request URI's other than login


Symptom: User cannot create custom group for break-out ports. From Manage Group dialog user cannot
select Break-out ports to create custom groups.
Condition: Creating customer groups with break-out ports for the Network OS 6.0.1 device.

Symptom: New connection added to ISL Trunk group is not shown with [+] sign.
Condition: 1) Discover a switch with ISL Trunks. Physically remove the master connection and accept the
changes.
2) Connect the removed trunk port again. Network Advisor shows the newly added connection,
but [+] is not shown.

Reported In Release: Network Advisor14.0.1 Technology: Menus & Toolbars
Symptom: Port Tab of Property sheet is not shown the 100Gige port details when 40G port is converted as
100G port through CLI.
Condition: Discover the 'VDX6940-144S' device. Convert 40Gige port to 100Gige through CLI and launch
the property sheet.

Symptom: Installation fails in SuSe 11.3 server due to missing Lib issues.
Condition: 1.Installation fails in SuSe 11.3 server during database initialization.
2.verify migration scripts log contains error that : error while loading shared libraries:
libreadline.so.6: cannot open shared object file: No such file or directory .

Symptom: HA status is shown as offline in FCIP dialog when a Tunnel without HA is edited and provided the
HA details
Condition: Configure FCIP Tunnel between two 7840 switches without HA configured and then edit the
configuration to add HA details

Symptom: BNA search will fail in Zoning Dialog
Condition: When attached port is empty or null, then search in zoning dialog will not highlight any value
Recovery: Zoning dialog relaunch or client relaunch may resolve this issue


Symptom: IOS measures were not displayed in real time graph for flow created on egress port for wedge
switch
Condition: Launch flow vision dialog and move flow created on egress port with source and destination
defined in wedge switch to view the Real time graph.

Symptom: Not all EX-Port is getting filtered from brocade_switchfcport
Condition: Brocade_switchfcport class does not show all the the EX ports which is trunked. Only trunk
master is visible in the Brocade_switchfcport class.

Symptom: Network Advisor performance collectors threshold configuration values are lost
Condition: When Deutschland locale setting is used

Symptom: An attempt to move GE port (e.g. ge10) to another FID failed with the error that said it is because
of existing configurations, although no configuration existed on the port. Also the port was
incorrectly represented as XGE0.
Condition: Issue is observed when attempted to move GE port (e.g. ge10) to another FID via Logical
Switches dialog.

Symptom: if the response is taking more than 10 minutes for any rest request. connection gets closed.
Condition: The response is exceeding more than 10 minutes because of having too many zone members.
So the WStoken gets expired after 10 minutes

Product: Brocade Network Advisor Technology Group: Security
Reported In Release: Network Advisor12.4.1 Technology: Security Vulnerability
Symptom: SSH Insecure HMAC Algorithms Enabled.
Condition: BNA is contacting the below websites for updates.
• terracotta.org
• async-io.org
When we checked this we found that these are third party APIs which we are using in BNA server.
Customer is pointing to below server log snippets and also concerned about their security.
2016-04-10 18:54:23,255 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService

Thread Pool -- 161)

For Atmosphere Framework Commercial Support, visit
http://www.async-io.org/ or send an email to mailto:support@async-io.org
2016-04-10 18:54:23,255 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService

Thread Pool -- 161) Installed AtmosphereInterceptor @PushEndpoint Interceptor with priority
AFTER_DEFAULT
2016-04-10 18:54:23,736 INFO [org.atmosphere.cpr.AtmosphereFramework] (Thread-237)
Latest version of Atmosphere's JavaScript Client 2.2.13
2016-04-10 18:54:23,738 INFO [org.atmosphere.cpr.AtmosphereFramework] (Thread-237)

Symptom: Troubleshooting dialog shows a popup error stating that the port is not connected to the switch
when the port is actually connected
Condition: A pair of G6 logical switches locked in a FICON secured logical fabric and traffic was running.

Reported In Release: Network Advisor14.0.1 Technology: Online Help
Symptom: Table 1 in SAN and SAN+IP User Guides does not provide following information for Brocade X6-8
Director chassis:
Footnote 1. Professional can discover, but not manage, this device. This device cannot be used
as a Seed switch.
Footnote 2. Professional Plus Trial and Licensed version can discover, but not manage this
device. This device cannot be used as a Seed switch.
.
Condition: Missing information in the User manuals.

Technical Severity: Low Probability: Low
Symptom: BNA-MIB is not available in Event Action Wizard under Traps.
Condition: Issue exists in SAN only installation of Network Advisor.

Symptom: Device tree in In Network Advisor shows duplicate entry for an ISL truck group.
Condition: Observed when attempting to recreate the same trunk group after it's been deleted.


Symptom: CLI configured IPSec Policy and pre-shared key are not displayed in the Tunnel tab parameters of
“FCIP Tunnels” Dialog
Condition: This issue will be seen when the pre-shared key for the Brocade 7840 switch is empty.

Symptom: When attempted a full uninstallation of Network Advisor, received an error "Failed to Stop
Database Service".
Condition: Observed rarely during Network Advisor uninstallation or migration, when database shutdown
takes longer time.
Recovery: Launch Server Management Console, stop all the services, and then continue with the
uninstallation/migration.

Symptom: When user tries to rediscover a SCG200 controller, it throws an exception as
BatchUpdateException.
Condition: If the IP address of the connected Access Point is being acquired by different Access Point, which
means the MAC address of the connected device is now changed, the controller rediscovery in
Network Advisor will fail.
Workaround: Delete the controller from the Network Advisor and discover it again.

Symptom: LSAN Zoning (Device Sharing) performance is slow and the dialog shows "Loading Zone DB of the
selected zoning scope. Please wait".
Condition: When LSAN has more than 2500 Zones and 5000 zone members.

Symptom: Licensed features attribute in VCS properties sheet will be blank
Condition: VDX 6740 running Network OS 7.0.0

Symptom: MAPS Rules for Curcuit_IP Utilization (UTIL) for High, Medium, and Low QOS not listed in the
Network Advisor MAPS policy dialog.
Condition: Issue observed when View Policy dialog is being launched and user immediately clicks on FCIP
tab, as it takes around 10 seconds to update the circuit IP rules in the dialog.


Symptom: Event actions do not work sporadically for "Drop" rule.
Condition: Setup an event action to drop the event sec-1203 from showing up in the master log.

Symptom: Even though, product communication is set as "SSH only", Network Advisor tries with telnet
protocol to check the telnet reachability
Condition: Any operation to reach the product ends up with using telnet protocol

Reported In Release: Network Advisor12.4.3 Technology: Configuration File Management
Symptom: Network Advisor reports "Save Running Configuration" failure on MLXe routers running 5.6.0g
and 5.8.0c firmware versions
Condition: Discover MLXe device running frimware versions 5.6.0g or 5.8.0c with a login service account
and SNMP v2c only
Workaround: Discover the device through super user password from Network Advisor or add the "no snmp-
server pw-check" command on the device through CLI.

Symptom: Serial Number for Ruckus Virtual SmartZone - HighScale (vSZ-H) controller is blank in Properties
dialog.
Condition: Issue observed when vSZ-H controller discovered and monitored in Network Advisor.

Symptom: Firmware upgrade on ICX7450-PoE switch using CLI Manager is failing
Condition: Upgrading the PoE on ICX7450 - POE using cli template, the status shows “failed” but the
console shows image is downloaded successfully.

Symptom: User loses changes made by editing a filter, if he navigates to a different view without saving the
changes as there is no warning dialog.
Condition: When user movies away from edit filter dialog without committing the changes,
Workaround: Always commit the changes before exiting the edit view.


Symptom: In Java client, Fabric summary and Ports report displays the model name incorrectly as Brocade
7840 instead of Analytics Monitoring platform.
Condition: In the Fabric summary and ports report of Java client.

Symptom: When user launches the sFlow report by giving the fully qualified domain name as Network
Address in login dialog, the report launch fails
Condition: Launch the sFlow report by giving the fully qualified domain name as Network Address in login
dialog.

Symptom: All the events are captured in improper host and ip address
Condition: Forwarded syslogs are not using proper FQDN.
Workaround: Issue is seen on the server with multiple NICs.

Symptom: User cannot differentiate between RX and TX performance values using REST performance URIs
Condition: The REST performance URIs do not include attribute to differentiate between RX and TX
performance values.

Technical Severity: High Probability: Low
Symptom: User will not able to view the IO latency and Performance widgets
Condition: Create a template with MAPS violation widgets. In for Traffic performance, IO latency and
Performance widgets the value shows zero.
Workaround: Violations are displayed in MAPS widget in java client

Symptom: User with read-only privilege will be able to add Performance widgets to the Template.
Condition: User with read-only privilege will be seeing the Performance widgets in the Select Widgets dialog
and can add them to the template.

Suite

Symptom: User will not able to see Port related MAPS Violations that might have occurred that between
server stop and restart after server restart in the Initiator/Target/ISL port violations widgets in
Web client.
Condition: After stopping and restarting Network Advisor server.
Workaround: The Out of Range Violations Widget on the Thick client Dashboard will display these violations.

Symptom: Flow from summary performance does not show data in investigation mode.
Flow from summary performance is not showing the data in investigation when it is selected after
a flow from latency summary
Condition: When a flow is selected for investigation from latency summary.

Symptom: Configuration restore on Brocade 6546 and 6520 fails with an error message 'Time Zone invalid'.
Condition: When trying to restore configuration on Brocade 6546 and 6520.
Workaround: Use CLI to restore the saved configuration.

Symptom: When a graph has both very high and very low values, the low values appear as zero.
Condition: Mouse over near zero to see the actual data value.

Symptom: All the flows added manually by providing LUN numbers are not shown in 'Add Flow' tables
Condition: Add flows by providing LUN number in the "Enter Manually" option of the Add Flow dialog. Only
few of those flows are displayed in the add flow table.
Workaround: After actual deployment, the details are correctly populated.

Symptom: Customer is seeing high CPU usage on the VDX devices.
Condition: If customer is managing the VCS fabric (which has MAC table entries) using BNA, then they will
notice the high CPU usage on VDX device as BNA is indefinitely querying the MAC address table.
Workaround: The workaround is to disable the IP Storage Collector which will query the MAC address
entries. We had provided a script for the same. Please contact Brocade support for the script.
Recovery: Customer has to run the script to disable the IP Storage Collector.


Symptom: Look up dialog is blank even though the violation count is displayed for the FRU health in ISL Port
Violations widget
Condition: Launch the Analytics summary template in the web client dashboard. Make sure data is available
for FRU health in ISL Port Violations. The lookup dialog opens up blank.

Symptom: "Connected To" and "Attached Port #" fields are blank in F-Port properties dialog in the Java
client.
Condition: Launch port properties dialog for F-port in the java client.

Symptom: Fabric Performance Impact violations are not displayed in Initiator/ target port violations widget.
Condition: When a measure has a very high value and another measure is has a low value, data points in
the bar graph will not be visible.
Workaround: User will need to mouse over the measures to see the values.

Symptom: Zero value is shown for Read / Write Data Rate in flow expanded view even though CLI has no
value for it.
Condition: Apply a filter in the Network Flows page, expand the table row on a flow. .

Symptom: Violations are not shown for BE-port Health Category in Dashboard
Condition: Launch the violation lookup dialog for BE-Port Health category in Dashboard.
Workaround: Look at the Java client violation widget.

Symptom: Network Advisor documentation does not mention Local Flow mirroring or the bidirectional
specific restriction.
Condition: The issue is with the Network Advisor SAN Admin User guide.

Symptom: Intermittently, widgets do not display data if filters created on the fly are applied to the widgets.

Condition: When you create a filter and save it by launching the 'Add Filter' dialog from Dashboard.
Recovery: Do a manual page refresh or open the filter dialog to apply the changes again.

Symptom: Tool tip shows the value 'NaN' for Max in the Flow Summary Performance widget
Condition: Launch Analytics Summary template in the dashboard and hover the mouse on any data point.

Symptom: Asset collection is triggered for few switches, even though they are of Virtual connect type
switches.
Condition: For few SNMP traps, VF id is not available, which triggered the asset collection of those Virtual
connect switches.

Symptom: FileReceiveServlet in Network Advisor is vulnerable to remote access.
Condition: FileReceiveServlet in Network Advisor is vulnerable to remote access. Network Advisor versions
prior to 14.0.3 are susceptible to this vulnerability.

Symptom: DashboardFileReceiveServlet in Network Advisor is vulnerable to remote access.
Condition: DashboardFileReceiveServlet in Network Advisor is vulnerable to remote access. Network Advisor
versions prior to 14.0.3 are susceptible to this vulnerability.

Symptom: SoftwareImageUpload servlet in Network Advisor is vulnerable to remote access.
Condition: SoftwareImageUpload servlet in Network Advisor is vulnerable to remote access. Network Advisor

Symptom: CliMonitorReportServlet in Network Advisor is vulnerable to remote access.
Condition: CliMonitorReportServlet in Network Advisor is vulnerable to remote access. Network Advisor


Symptom: HPE no longer supports Call Home in Brocade Network Advisor, however the call home center 'HP
LAN' is still visible in the application and listed in the documentation.
Condition: The 'HP LAN’ call home center is visible under Monitor > Event Notification > Call Home in the HP
flavor of Network Advisor application.
Workaround: Manually hide the call home center from the dialog.

Symptom: Cannot view the active flows in the large network when Network Advisor is monitoring around
100k flows.
Condition: Issue observed in large scale environment.
Recovery: We have fixed this issue ,By adding new Temp table to get latest record & process it.

Symptom: Network Advisor response will be slow.
Condition: This issue is seen when there are more than 10 million MAPS events in Network Advisor

Symptom: Internal server error will be displayed to the user when requesting zoning information through
REST API
Condition: Retrieving zoning data from Network Advisor using REST API for Large Fabric

Symptom: Network Advisor documentation did not state that I18N internationalization and localization is
not supported in Network Advisor.
Condition: The issue has been reported with the Network Advisor documentation.

Reported In Release: Network Advisor14.0.1 Technology: Call Home
Symptom: Network Advisor triggers a call home for an unmonitored Brocade Analytics Monitoring Platform
(AMP).
Condition: Issue observed when the AMP switch becomes unmonitored (for instance, due to user initiated
reboot) in the Discovery dialog window.


Symptom: Network Advisor failed to trigger the startup configuration backup.
Condition: Issue observed when both - DoBackupOnRunningConfigChangeTrap and
DoBackupOnStartupConfigChangeTrap options are enabled in the IP preferences dialog.

Symptom: Two emails are being received for a switch port state change event.
Condition: Issue observed when a port state changes from offline to online and port type changes
respective (e.g. from G-port to E-port or F-port).

Symptom: User will not be prompted with spinner when creating/updating collection.
Condition: When creating/updating the collection, spinner to show the progress is not seen.
Recovery: Wait up to 10 seconds to see the proper status.

Symptom: Unable to save the dashboard template when changing the measures / IO size in the widgets.
While trying to change the measure / IO size on widget, the web page displays the progress
spinner which is never ending.
Condition: Issue is observed when editing the template multiple times by adding or removing widgets.
Recovery: Refresh the page and try again

Symptom: Unable to discover and manage MLX6.0.0a
Condition: Latest versions of MLX (greater than 5.8) with Rbridge ID greater than 32767 cannot be
discovered in Network Advisor.
Defects Closed without Code Change in Network Advisor 14.0.0

This section lists the defects with Critical, High and Medium Technical Severity closed without a code
change as of December 21, 2016 in Network Advisor 14.2.0.
Defect ID: DEFECT000549536 Technical Severity: High

Reason Code: Not Reproducible Probability: Medium
Symptom: Address Finder search fails with an error for Brocade ICX devices.
Condition: When the ICX device is running firmware version FI 8.0.10

Reason Code: Will Not Fix Probability: Medium
Symptom: The Monitor tab on the COMPASS dialog displays which template is linked to the switch groups.
This tree representation updates multiple times when linking a template to multiple
fabrics/switch groups.
Condition: On Performing the link/unlink operation the Tree table showing the Drift status updates multiple
times causing the UI to be slow and sluggish
Workaround: The workaround is to wait after the link/unlink operation to complete the operation before
performing other operations.

Symptom: Real time and Historical Graph data collection is not happening for both Default flow and User
Defined Flow
Condition: After 15 mins the real time and historical measures for the flows (sys_gen_all_simports) stops
updating.
Workaround: Use CLI "flow --show sys_gen_all_simports"

Symptom: ‘No VLAN configurations are available at this time. Try again later’ error message will be
displayed in VLAN Management dialog.
Condition: This is applicable for Aruba wireless controllers

Suite
Symptom: Master logs shows that both port decommissioning and port fencing were successful for port
Condition: When a rule with both port decommissioning and fence action is violated, though port fencing is
successful, master log shows both actions are successful. This occurs once in 10 times.

Symptom: User not able to perform any operations due to client got hung
Condition: Launch the client and perform some operations daily. client got hung after 10 days. This is an
inconsistent issue.
Workaround: Restart the server and launch the new client
Recovery: Restart the server and launch the new client

Reported In Release: Network Advisor12.4.3 Technology: Fabric Tracking (SAN)

Symptom: Creates ambiguity as the template sync actually resulted in a failure. User has to lookup Status
details field in the dialog that contains the reasons for failure.
Condition: The user will see the Overall Deployment status as Success instead of Failed when the Maps
policies are deployed on a Maps Disabled switch.
Workaround: User has to read the Status details field that details about the Maps policy deployment failure
on a Maps disabled switch.

Reason Code: Will Not Fix Probability: Low
Symptom: User cannot download firmware using SCP protocol
Condition: Firmware download fails with status showing as ‘Downloading’ when used Built-in SCP/SFTP
server with preferred protocol set to SCP..

Symptom: MAPS violations are not displayed in the Out of Range widgets, whereas they are seen in violation
dialog
Condition: Seen in VDX switches.

Reported In Release: Network Advisor14.0.1 Technology: vCenter Integration
Symptom: VM Alarms Widget is not updated when an alarm is triggered on VM level
Condition: Create a Custom Dashboard with VM Alarms widget. Select any virtual machine of the ESXi server
managed in the vCenter Server and create an Alarm. vCenter dispalys the alarm in the triggered
alarms tab but the VM Alarms widget in custom dashboard of BNA do not populate the alarm nor
any event in the master log.
Workaround: Restart the VM to get the updates

Symptom: BNA Performance | Real-Time Graph failed to get started when monitoring Tx % Utilization and
specifying an active FCIP Tunnel. (Actual tunnel was IPEX with FC traffic flowing).The Real-Time
Graph appeared and Measure Tx & Utilization was selected but no plotting ever began. Waited
72 hrs and the graph was still empty.Verified that the correct VE Ports associated with the tunnel
were correct.
Condition: Topology: Pair of GEN 6 Logical Switches connected into a stable Logical Fabric held together
with a single IPEX tunnel. The Logical Fabric was 100% stable and consisted of a X6-4 and a X6-
8 chassis.Traffic: Significant FC traffic and FCP traffic and FC FICON traffic was traversing the
IPEX tunnel. In addition, there was also IP traffic flowing over the same tunnel.
Workaround: Use the "portshow fciptunnel --ch" command on each side of the tunnel to obtain the Tx
Utilization.
Defect ID: DEFECT000592092 Technical Severity: Medium

Reason Code: Design Limitation Probability: Medium

Symptom: Unable to apply imported ADX MIBs to historical collector in Network Advisor
Condition: Upload a new MIB file (ASR12502f.mib) for an ADX device and attempt to apply selected MIB
object as historical collector by moving to the right pane

Reason Code: Design Limitation Probability: Medium
Symptom: Real-time graph TXmb/sec values fluctuation observed when granularity is set to 20 seconds,
even though the traffic is stable.
Condition: Issue is observed after one hour of plotting the data.

Reason Code: Feature/Function Not Supported Probability: Medium
Symptom: User is unable to perform Diagnostic Port Test on ICL and QSFP ports. Observe that electrical &
optical loop-back test is skipped with reason as "No SFP or Chip support".
Condition: Launch Diagnostic Port dialog and select 16G ICL/32 ICL/32 QSFP ports and start the test.

Symptom: There are duplicate flow definitions shown to the user
Condition: Discover a fabric with flows. Delete the tunnels make sure that fabric is segmented. Again
configure the tunnel in the fabrics and make sure that fabrics are merged after tunnel comes
online. Now launch flow vision dialog.

Symptom: Unsupported measures are displayed for VE Port and E Port flows in real time graph
Condition: Launch real time graph for the subflows in VE port and E port where IO measures which is not
supported for the above said ports are listed.

Symptom: User not able to run D-port test as the dialog appeared blank.
Condition: Happens very intermittently when the G620 is part of the fabric

Symptom: Measures are not moving in Real time graph
Condition: Select the measure (IO Insight/Frames/SCSI etc ) in the flow vision dialog and launch real time
performance graph.

Symptom: Unable to deploy AAA configuration on the switches with error: 'null'; Details: 'download_failed
Process function of configdownload failed for filter "aaaconf"
Condition: Issue observed during AAA configuration deployment via COMPASS configuration dialog.

Symptom: BNA hung when trying to disable SIM mode on multiple ports
Condition: Disable SIM mode on multiple ports on a switch. Occasionally BNA freezes and no changes were
made on the switch.

Symptom: End devices are not shown in the Product Tree or Topology immediately when the SIM mode is
enabled. Product Tree or Topology taking few minutes to update the same.
Condition: Select unoccupied port from product tree and enable SIM mode.
Recovery: Rediscover the device

Symptom: Subflows for sys_gen_all_sim_ports turns inactive and lose measures
Condition: Launch Flow Vision and move the active default flow, sys_gen_all_sim_ports from left hand panel
into right hand panel. After 15-20 mins, the subflows turn inactive (yellow color) and the
measures Runs completed & Percentage completed loses the count.

Symptom: Users will get a wrong error message in Network Advisor while trying to configure STP in
transparent VLAN for VCS enabled Network OS devices
Condition: When user try to configure STP on the VLAN we are getting wrong error message. Instead of
showing ''STP configuration not allowed on transparent VLAN".

Symptom: Failed to create Port groups for the wireless controllers vSZ-E and vSZ-H.
Condition: Issue observed when creating the port groups for the virtual wireless controllers vSZ-E and vSZ-H.


Symptom: Network Advisor client will not update the port movement after Tunnel deletion operation
Condition: Intermittently moving the ports to other context immediately after deleting the tunnel.
Workaround: Close and relaunch the Network Advisor client

Reason Code: Not Reproducible Probability: Low
Symptom: When the custom time range is set to less than 30 minutes, User will see the data for last 30
minutes in Non-AMP Performance widgets in Dashboard of the Web Client.
Condition: When user selects the custom time scope less than 30 minutes in Web Client.

Symptom: Web client on an Edge browser logs out.
Condition: When moving Back or forward using the buttons to select dates in Calendar date picker.
Recovery: Log back into the client.

Symptom: Apply button does not get enabled when the Date or Time is entered manually on Internet
Explorer 11 browser.
Condition: In the PM graph on IE 11, when trying to edit Date/Time field.
Workaround: Use mouse to select the dates from the calendar instead of manually typing.

Symptom: Duplicate configuration backup is seen for Fabric OS/AMP devices.
Condition: When the credentials of the switch/AMP is updated while Fabric/switch discovery or config
backup is in progress.

Reason Code: Feature/Function Not Supported Probability: Low
Symptom: If customer launches the BNA thin client with host name, it 's referring back to IP address in URL.
Condition: When user installs the BNA with IP address as client side communication, and tried to launch the
BNA thin client with Host name in URL.

Symptom: Flow summary latency widget may show data up to 15 minutes behind the system time.
Condition: If Network Advisor services are partially restarted.
Recovery: Refresh the web page.

Symptom: When viewing flow details for a particular violation (by mousing over the content in the object
column to see the tool tip, the VTAP FC address may get displayed with only 5 digits ignoring the
leading zero (For e.g. 050600 may get displayed as 50600).
Condition: When zone alias or port name is not configured and the FC address begins with a zero.
Workaround: Configure zone alias or port name so that they will be shown instead of the FC address.

Reason Code: Will Not Fix Probability: High
Symptom: Active zone configuration icon Is not shown for active config in Zone DB tab
Condition: Modify the active zone configuration by adding or removing zones. Activate the same modified
zone configuration. Observe that Active zone configuration icon Is not shown for active config in
Zone DB tab.

Symptom: When an F-port is disabled and changes are accepted, connection persists in topology as U port
to N port.
Condition: Discover a SAN Fabric with F-N Port connections. Disable a F port and Accept changes in Network
Advisor.

Reason Code: Not Reproducible Probability: High
Symptom: Intermittently, AMP widgets remain in the loading state on Dashboard.
Condition: Seen intermittently on Network Advisor servers running for a few days.
Recovery: Refreshing the browser or re-logging into the application solves this issue.

Suite
Symptom: Initiator and Target fields accepts invalid FC Address in the Collections page.
Condition: Launch Network Advisor and create a collection. Add about 80 flows by choosing "Enter
manually" option.

Symptom: Total flow and Active flow count went to zero after un-monitoring & monitoring the fabric.
Condition: Un-monitor the fabric after deploying a collection successfully. Now reboot the AMP device and
when it comes up and Network Advisor displays all the fabric and ports, monitor the fabric that

was currently un-monitored. Launch Collection Management page where the Total flow and
Active flow count is displayed as zero.

Symptom: In the Initiator/ Target Port Violations widgets, violations are reported twice, resulting in duplicate
data.
Condition: When a flow is tapped at both ends, the violations are reported twice.

Reason Code: Not Reproducible Probability: High
Symptom: Average value for 'Other command latency' measure is not displayed in Dashboard and
Investigate mode pages.
Condition: In the Analytics Summary widget, in both Dashboard and investigation views, for 'Other
Command Latency'.
Known Issues
Important SAN Notes
 While pushing larger zone configurations, make sure to reserve enough space in zonedb to
accommodate hdr size of all the LS and actual committed configuration within the zoneDB max
size. It is recommended to add zones gradually. Pushing Zone DB of size more than max zone DB
size, will set availalle zone DB size to negative value which in turn causes a deadlock where any
zone operation will not work.
 FOS 8.1 and BNA 14.2 support a total of 16 LS on each X6 Director. For Creation, Modification, or
Deletion of Logical Switches in FICON environments, it is highly recommended to limit these
operations from Network Advisor’s Logical Switches dialog to less than 4 LS at-a-time to avoid
timeout issues. For non-FICON environments, a limit of 8 LS at-a-time is enforced.
 Firmware Download fails if built-in SCP is used as preferred protocol. The workaround is to use
the FTP/SFTP option in BNA
 SNMPv3 using AES256 algorithm may not work with certain passwords as there could be some
mismatch for encryption/decryption of passwords. For example: “pass1”, “xyz12mo” fails
whereas “xyz12” works. This is because AES256 algorithm is not a standard implementation
 Trying to move 200+ ports to a Logical Switch with ‘Reset to Default’ option selected, results in
operation time-out.

 During installation, if Network Advisor database initialization fails on Windows Operating
System, user needs to verify access to the drive on which the installation is performed. If the
user “Administrator” alone has access to the drive, then required permissions should also be
provided to “Authenticated Users” and then continue with the installation.
 The FCIP links will not be shown in the topology for tunnels with degraded circuits
 IP Ping, IP Route and Trace route is not supported for Brocade 7840/SX6
 Network Advisor uses SNMPv3 by default to discover SAN products. If required, user can select
the ‘Manual’ option in Discovery dialog and choose SNMPv1 for discovery, as in case of AG
discovery which requires use of SNMPv1 by default.
 A delay of 5 to 7 minutes is seen when Web Tools is launched on a system (through Network
Advisor or directly in a web browser) where internet access is not available and the network
does not return a ‘destination unreachable’ message. This issue occurs as Java tries to validate
the SSL certificates with external CAs. This problem can be avoided on such systems by
modifying the below Java properties:
On Windows:
C:\Users\<logged in
username>\AppData\LocalLow\Sun\Java\Deployment\deployment.properties
On Linux:
home/< logged in user name>/.java/deployment/deployment.properties
In the ‘deployment.properties’ file, edit the below parameters and set them to ‘false’. If these
parameters are not present, add them and save the file. Then re-launch Web tools.
deployment.security.validation.ocsp = false
deployment.security.validation.crl = false
 Real time graph will not display proper data for FCIP tunnels when the polling interval is 10 sec.
User need to keep 20 sec polling interval in graph to see the correct data for Brocade 7840/SX6
 Emulex: HTTPS discovery for ESXi host will work only with certificate import
Workaround
Perform the following two steps to work around this issue.
Step 1) Add following line in <User Home>/.java/deployment/deployment.properties file
deployment.expiration.check.enabled=false
For example, if the user is root then the absolute path of this file would be as below:
/root/.java/deployment/deployment.properties
Step 2) Launch the java control panel using below command and click
on Ok button <Network Advisor Home>\jre\bin\jcontrol
 If Network Advisor is installed on Linux Operating System, the Fabric OS Element Manager and
HCM cannot be launched when the client is launched using the dcmclient script available in
Network Advisor installation folder. The Launch in Context (LIC) dialogs from SMIA configuration

tool (launched from Server Management Console) also cannot be launched (e.g. Discovery
Dialog, Options Dialog etc.). To use the above features on Linux machines, launch the Network
Advisor client from a browser (after installing supported JRE 7 version), pointing to the Network
Advisor server installed on that machine.
Workaround
Perform the following steps to work around this issue.
Step 1) Add following line in <User Home>/.java/deployment/deployment.properties file
deployment.expiration.check.enabled=false
For example, if the user is root then the absolute path of this file would be as below:
/root/.java/deployment/deployment.properties
Step 2) Launch the java control panel using below command and click OK.
<Network Advisor Home>\jre\bin\jcontrol
 Secure Syslog is not supported from Network Advisor
 SAN Configuration Purge Backup is being enabled automatically when “Enable Scheduled
Backup” is set and remains enabled after disabling the Scheduled Backup.
 User is not recommended to perform write operations such as delete or enable/disable on FCIP
tunnels which have circuits with different IDs.
 When CIMOM server is bound to host name, SLP service fails to get registered. Workaround: To
overcome this issue user can bind the CIMOM server to IP Address instead of host name.
 Firmware upgrade will happen serially for B7840's with HA configured tunnels between them.
For parallel download on B7840's use CLI.
 FCIP circuit trace route verification fails when attempted from Network Advisor
 Web tools launch is not supported for Brocade Analytics Monitoring Platform
 HTTP TRACK/TRACE methods are not blocked in BNA 14.2.0 JBoss (v 8.2) Webserver. If a web
application server has TRACE enabled, attacker (Cross-Site Tracing attack) can just send Http
request to the target server and in turn attackers will be able to hijack the session.
 SAN Inventory widget in default dashboard shows ‘Error loading the data’ on creating and
deleting custom dashboards inconsistently when managing more than 9000 ports. User has to
re-launch the client to see the data again.
 Do not enable “Use SSL 2.0 compatible ClientHello format” setting in Java Control Panel on the
Network Advisor Client machine as it will interfere with the remote client launch.
 For AMP users with scaled number of AMP flows, it is recommended that you disable daily
database backups for better Network Advisor performance with the AMP case.
If local server has JRE version 1.8u112, the links in Configure SMIA Agent dialog in Server
Management Console, will not launch.
Workaround for this issue: Uninstall the JRE version 1.8u112 or install JRE version 1.8u111.
 While generating reports from Microsoft Windows command prompt and saving the report in
non-default location, the report output directory path should not end with the backslash (“\”),
or the backslash character should be prefixed with forward slash (“/”). For example: –o “c:\/”.
 Make sure that the Management application server and the Fabric Insight Portal system clocks
are synchronized even if they are in different time zone.

Display of Logical Switches
If you create Logical switches through the Logical Switch dialog box, the Logical switch displays
under undiscovered Logical Switch in the existing Logical Switches Panel. You have to rediscover
the newly created logical switch fabric by going to the discovery dialog and add the IP address of
the chassis using the Add dialog.
SSL connections using certificates with MD5 signatures

SSL-based product communication will fail if the devices have ‘weak’ authentication certificates.
The user will see “Fabric Discovery failed because SSL certificate of the seed switch uses a weak
algorithm. Install SSL Certificate with strong authentication algorithm on the switch and try
again” for devices with weak certificates. Java 1.8 used by BNA 12.x disables the use of
certificates with ‘weak’ authentication. The certificates on such devices need to be updated to
be compliant with JRE v1.8. Please refer to the ‘Secure Sockets Layer protocol’ section of Fabric
OS Admin guide for details on updating certificates
The recommended solution is to replace the certificate on the network device with a certificate
using the more secure SHA signature. If that is not practical, the Network Advisor server
configuration can be changed to accept MD5 signatures. Note that accepting MD5 signatures
may result in warnings from network security scanning tools.
To accept MD5 signatures, edit the following text file:
On 64-bit Windows or Linux: <install-dir>/jre64/lib/security/java.security
Remove “MD5” from the following line near the end of the file:
jdk.tls.disabledAlgorithms=MD5, DES, 3DES, RC2
The modified line should appear as:
jdk.tls.disabledAlgorithms=DES, 3DES, RC2
The change will take effect the next time the Network Advisor server is restarted.
Reset Ports operation in Logical Switches dialog

Note 1: Reset ports to default operation is applicable only when the ports are moved from one
Logical Switch to another Logical Switch through the Right Arrow button i.e., from (Chassis ports
Tree/Tree Table) LHS to (Logical Switches Device Tree) RHS device tree.
It is not applicable when:
a. Ports from a Logical Switch are moved to default Logical Switch through Left Arrow
button, i.e., from (Logical Switches Device Tree) RHS to (Chassis ports Tree/Tree
Table) LHS.
b. When a Logical Switch is deleted - its ports will not be reset to default before
moving to Default Logical Switch before its deletion

Ports which are moved to the default logical switch can be reset to default, if they are moved
from Chassis ports Tree/Tree Table LHS to Logical Switches Device Tree RHS device tree.
Note 2: Reset ports to default operation will not clear FCIP configurations in the following
scenarios:
a. In 7800, 7840 and FX8-24, GE ports cannot be reset to default unless their
corresponding VE ports are cleared of their FCIP configurations
b. Switch reset to default operation on Brocade 7840 may fail due to GE port sharing
or if the associated VE port exists in another LS
Important IP Notes
Miscellaneous Important Notes that Apply to IP Installations

1. For large networks the Adaptive polling turned off by default for all IP devices (even for
migrated servers).
2. SNMP write credentials will not be populated by default for NI/FI/NOS devices.
3. Each IP product has a System max value that can be configured for various parameters, such as
“ip-filter-sys” for ACLs. Network Advisor deployments do not check whether the payload being
sent to the device has a number greater than the system-max value. In such deployment
scenarios, the deployment may report success even though the number was limited to the
system-max value. To ensure successful deployments, make sure the payload being sent is no
greater than System max value.
4. Syslog messages will not be received for the VDX 8770 that is configured with different IP
addresses for CPs.
5. Pizza Box switches running Network OS 4.0 are displayed with ‘Product Type’ as ‘Router’ in
Network Advisor, even when they do not have Layer 3 license.
6. When two ports of the same storage are connected to two VDX devices, only one of the
attached ports is displayed in the Zoning dialog.
7. On VDX devices managed through in band IP address in Network Advisor, firmware download,
product support save and configuration backup operations fail.
8. Fabric Watch violation can be viewed under following path Fabric Vision-->MAPS-->Violations.
9. Firmware upgrade in NetIron devices using simplified image doesn’t update the boot image
from NI 5.6 and above. Boot image need to deploy separately.
10. Discovery of a cluster running Network OS 6.0 and above requires addition of SNMP user
settings from CLI as default user support is not available.
11. Configuration backup on MLX running 5.8.00a code using SCP fails with 'Bad client version string
[Unknown cause]'. Work around is to use the TFTP, SCP then TFTP and TFTP then SCP. The issue
is not seen in NI 6.0 and later.

12. In IP Address and Detailed Reports IP Management Ports will not be consistent with the CLI port
naming conventions. This is caused by SNMP index and port name inconsistencies. In some
cases, Management ports will not be displayed in the reports.
13. L2 topology does not show link between Ruckus Wireless Controllers and connected L2 switches
as Ruckus Wireless Controllers don't support LLDP.
14. BNA would not rediscover the controller managing Access Points if there is a change detected in
the MAC Address of one or more Access Points. The controller has to be deleted first, and then
discovered to see the Access Points with the new MAC Address.
15. To use SSL Certificates for ServerIron products, contact your customer support representative
16. The Identifier column in the Ethernet Ports table of a detailed report shows incorrect identifier
details for Control Bridge's second slot ports.
17. The Control Bridge ports of a Campus Fabric do not show role as 'SPX PORT' in device properties
port tab if Campus Fabric has more than 2 Port Extenders.
Boot, Monitor, Firmware Image Updates

1. Network Advisor does not support boot and firmware upgrade and downgrade for ADX devices
running 12.1 or above.
2. Firmware Download to NetIron CES devices fails via SCP with the error message “There is not
enough space on MP flash”. Below are the considerations before downloading the image to NI
CES device.
1) If device flash size is 32 MB, it will support either primary or secondary flash. If image is
T
already present in primary flash and needs to download for secondary flash and vice-versa, then
we should manually delete the primary and secondary flash respectively by using the command
“delete primary or delete secondary” and download will be happen as expected. 39T
2) If it is 64 MB, it will support for both primary and secondary flash and the download will be
T
happen successfully.
Important Notes common for SAN and IP

1. In rare cases, due to some interactions with virus scan software, Network Advisor Server Start
process might go on 10 to 12 minutes, or may fail to start the server. If this happens, then configure
the virus scans to skip scanning Network Advisor files.
2. 64 bit OS is required to run any edition of Network Advisor - Professional, Professional-Plus and
Enterprise.
3. Network Advisor server startup and restart may take up to 10+ minutes to complete.
4. To avoid excessive telnet/ssh login messages in the Network Advisor master log and event report,
and the device CLI console, disable lazy polling by un-checking the “Enable lazy polling” checkbox in
IP Discovery Global Settings > Preferences Dialog.

5. Starting 12.0, the supported number of client connections has increased to 25. Please refer to the
installation guide for the details. In addition to those details, the following database memory setting
is required:
 The PostgreSQL’s parameter “shared_buffers” memory allocation should be increased to
1024MB. [This setting can be done by editing
<installation_directory>\data\databases\postgresql.conf file.]
Change following line: shared_buffers = 512MB
To: shared_buffers = 1024MB
 Server needs to be restarted.
6. In Linux 64 bit machines, connecting to the database through Open office using ODBC will not work.
Solution is to connect from Windows ODBC Client to the 64 bit Linux machine where Network
Advisor is running to view the Database tables.
7. Technical Support data collection for discovered Products fails through an external Linux FTP server
on a Windows installation of Network advisor. To successfully collect support save data for Network
OS and Fabric OS devices the below configuration needs to be done in the VSFTPD FTP server before
triggering the support save by setting external VSFTPD FTP Linux server (other than BNA FTP server):
/etc/vsftpd.conf file and set "chroot_local_user=YES"
8. Client only application can be installed on a machine other than the server (without using a web
browser) by creating a client bundle on the server, then copying and installing that client on another
machine. Refer to ‘Client only installation’ section of the Installation and Migration guide for details.
9. Intermittently HTTP 500 error message is displayed when launching the Web Client. Server restart
will fix the issue.
10. User needs to run the “sanperformancestatenable” script from BNA home utilities folder to
enable/disable performance statistics collection for SMIA only package installation. Below are the
steps to execute the script,
 Windows: Open cmd prompt and move to <BNA_HOME>\utilities and
run sanperformancestatsenable.bat dbusername dbpassword enable|disable
 Linux: Open terminal and move to <BNA_HOME>\utilities and
run sanperformancestatsenable dbusername dbpassword enable|disable
11. REST API does not provide FCIP circuit measures for the GigE port.
12. BNA is now enforcing minimum disk space requirements during migration. When the disk space
requirements are not met, BNA display a message prompting the user to use the script to delete
performance data and retry migration.
13. SNMP Trap auto-registration does not happen for a discovered VCS which is configured with ‘Read-
Only’ community string alone. Registration can be done manually post discovery through “Product
Trap Recipients” dialog.
14. When Network Advisor is managing more than 1500 IP products, user might experience some
performance degradations such as delays while launching some dialogs.
15. Due to Microsoft Windows operating system restriction which does not allow services logged in as
Local System user to interact with the desktop, the GUI application cannot be launched using
“Launch a Script” option of Add Event Action.
Please refer the following link for more information:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms683502%28v=vs.85%29.aspx
16. During migration, if insufficient space is detected, then a warning message will be displayed with an
option to rollback. If user chooses "No", then migration will be aborted. As a result, the source
version services will remain uninstalled. Please refer to the Installation Guide for the instructions to
install the source version services manually.
17. The ports listed in Network Advisor Installation and Migration guide need to be open bi-directionally
for all the bi-directional protocols in the firewall where the server is installed.
18. If source Network Advisor has more products discovered then it is recommended to stop all the
services manually from Network Advisor Server Management Console of the older version before
initiating migration from the Configuration Wizard.
19. Service start up failure can be seen in Windows 2008 R2 OS and the recommendation is to apply this
hot fix from http://support.microsoft.com/kb/2577795
20. If you see the following error message “Signature could not be validated” during firmware download
or technical support data collection (Fabric OS and Network OS devices only) or configuration
backup/restore (Network OS devices only) using SCP/SFTP, then it could be due to a mismatch in the
signature key used in the ssh handshake between the switch and SCP/SFTP server. Try the following
cli command work-around to address the issue:
 For Fabric OS devices
sw0:FID128:admin> sshutil delknownhost
IP Address/Hostname to be deleted: <IP Address of SSH server to be deleted>
 For Network OS devices

Firmware version 3.0 and later
sw0# clear ssh-key <IP Address of SSH server to be deleted>
 Firmware version 2.1.1b

sw0#execute-script sshdeleteknownhost
IP Address/Hostname to be deleted: <IP Address of SSH server to be deleted>
If the above does not work, go to Server > Options > Software Configuration > FTP/SFTP/SCP,
and uncheck the SCP/SFTP option.
21. You need to use a different (non-default) name for the widget when attempting to add “Top Product
Response Time” widget to avoid this error “Monitor could not be added. Duplicate monitor name”.
22. Patch Installer troubleshooting – The Patch installer may not launch if UAC is enabled on a Windows
7/8/2008/2008 R2/2012 Editions. You must first disable the UAC using the procedure provided in
the “Chapter G: Troubleshooting - Patch troubleshooting” Section of the User Manual and then
launch the patch installer.
23. During migration, BNA uninstallation process requires 1 GB of physical RAM. Sometimes Windows
OS do not clear the released memory and keeping it in standby Memory. Use Microsoft tool like
“RAM MAP” to clean up the unused RAM from standby list

 Download RAMMap.zip file from URL - https://technet.microsoft.com/en-
us/sysinternals/rammap.aspx
 Extract the zip file and run the runmap.exe
 Click empty menu > Empty Standby List
Domestic and International Modem based Call Home is no longer supported for Brocade Call
Home Centers in 12.x and above
Alternatively, customers using Domestic or International Call Home Modem feature can reconfigure
their Call Home to utilize the Brocade Email option for continued Call Home notifications in the
event of a system problem. Please refer to the Call Home section of the Brocade Network Advisor
User Manual for more configuration details. Note that EFCM and DCFM customers will also be
affected by this change and need to reconfigure their call home to utilize the Brocade Email option
for continued Call Home notifications in the event of a system problem.

During migration, an option will be given to migrate the switches which are configured assigned to
the Brocade Domestic and Brocade International call centers. Please select “No” in the config wizard
when the message is displayed.
Note: EMC Call Home Center will continue to support Modem Call Home functionality.
Support Saves and server backup may take a long time with large databases
As databases grow larger from Event, sFlow, and Performance Collector data, support save and
server backup operation may take a long time to run. Larger databases will promote longer support
save/ server backup operations.
For server backup, make sure you have free disk space equivalent to “total of twice the
<Install_Home>\data folder (except databases folder) and 30% of <Install_Home>\data\databases
folder”.
For support save collection, make sure you have free disk space equivalent to a “total of
<Install_Home>\logs folder and 30% of <Install_Home>\data\databases folder”
Note:
For networks with large amounts of data to backup, the Management application’s performance is
degraded during the daily scheduled backup. To avoid performance degradation, configure backup
to an external hard drive or use Backup Now on demand.
Installation on Network Mounted Drives is not supported

Installation onto a windows network mounted drive is not supported but install is allowed and DB
fails to start.
Client disconnects
Under heavy server load or degraded network links, there is a potential for Network Advisor
client to get disconnected from the server. Work around is to restart the client.
Cross-flavor Migration
Migrating same version of BNA (14.2.0) from OEM1 version to OEM2 version
a. Partially uninstall the source BNA 14.2.0 OEM1 version
b. Now install BNA 14.2.0 OEM2 version
c. In the ‘copy data and settings’ page, browse to the BNA 14.2.0 OEM1 version and
continue with the migration.
Migrating BNA (pre-14.2.0) OEM1 version to BNA 14.2.0 OEM2 version

d. Install the source BNA pre-14.2.0 OEM1 version
e. Now install BNA 14.2.0 OEM2 version
f. In the ‘copy data and settings’ page, browse to the BNA pre-14.2.0 OEM1 version
and continue with the migration.

Virtual Connect Enterprise Manager (VCEM) Support
The supported and tested versions are listed below:
HP SIM Version v7.4.0

HP VCEM version v7.4.1
OA firmware Onboard Administrator (OA) v2.41 or later
VC E-net module firmware(HP VC 8Gb 20-Port v3.15
FC Module &
HP VC 8Gb 24-Port FC Module)
Hardware HP BladeSystem c3000 or c7000
Servers Proliant BL465c G7, Proliant BL460c G6
HBA Brocade 804 8Gb FC HBA, Emulex LPe1205-
HP 8Gb FC HBA, QLogic QLE2562 8Gb FC
HBA, QLogic QLE2672-CK 16Gb FC HBA
Performance Statistics Counters - Calculation Formulae

For calculating the statistics for FC, GE, FCIP and TE port we use SNMP to query the respective OIDs,
mentioned below in the table.
For calculating the HBA and CNA statistics, we use the APIs provided by HCM. And for EE monitors we
use HTTP to get the TX, RX and CRC error values.
Polling interval for historical graph is 5 min and for real-time, it changes based on the granularity value
selected in the Real Time graph dialog.
Name y Sourced value Formula
TX FC SP .1.3.6.1.3.94.4.5.1.6 TX = (Delta valueP1P / (1000 *

1000)) / (Polling intervalP2P)
RX FC MP .1.3.6.1.3.94.4.5.1.7 RX = (Delta valueP1P / (1000 *
TX G SP .1.3.6.1.2.1.31.1.1.1.10 TX = (Delta valueP1P / (1000 *
RX GE SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta valueP1P / (1000 *
TX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.10 TX = (Delta valueP1P / (1000 *
RX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta valueP1P / (1000 *
Uncompre FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.6 (Delta valueP1P / (1000 * 1000))
ssed Tx/Rx / (Polling intervalP2P)
MB/sec
TX EE HTTP PortRX (variable from the TX = (Delta valueP1P / (1000 *
Monitors return html file) 1000)) / (Polling intervalP2P)
RX EE HTTP PortTX (variable from the RX = (Delta valueP1P / (1000 *
Monitors return html file) 1000)) / (Polling intervalP2P)
TX HBA, CNA HCM API NA TX = (Delta valueP1P / (1000 *
RX HBA, CNA HCM API NA RX = (Delta valueP1P / (1000 *

TX TE SNMP 1.3.6.1.2.1.31.1.1.1.10 TX = (Delta valueP1P / (1000 *
RX TE SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta valueP1P / (1000 *
TX% / RX% FC NA TX = .1.3.6.1.3.94.4.5.1.6 TX% or RX% for FC = ((delta value1
RX = .1.3.6.1.3.94.4.5.1.7 of TX or RX) / ((Bytes
transmitted * port speed)*(polling
interval2))) * 100 where
Bytes transmitted for 1G,2G,4G,8G
and 16G port speed is
106250000 and Bytes transmitted
for 10G port speed is
127500000. If utilization is less
than 1, the value is 0.0.
TX% / RX% GE SNMP TX = .1.3.6.1.2.1.31.1.1.1.10 TX% or RX% for FC = ((delta value1
RX =.1.3.6.1.2.1.31.1.1.1.6 of TX or RX)
/((125000000* port
speed)*(polling interval2))) * 100.
If the utilization is less than 1 the
value is 0.0.
TX% / RX% FCIP SNMP TX = .1.3.6.1.2.1.31.1.1.1.10 TX% or RX% for FCIP = ((delta
RX = .1.3.6.1.2.1.31.1.1.1.6 value1 of TX or RX) /(maximum
bytes transmitted))*polling
interval2))) * 100, where maximum
bytes transmitted = tunnel speed
TX% / RX% TE SNMP TX = .1.3.6.1.2.1.31.1.1.1.10 TX% or RX% for TE = ((delta value1
(Pre 6.4.1 RX = .1.3.6.1.2.1.31.1.1.1.6 of TX or RX) /((125000000*
Edison 10)*(polling interval2)))* 100. If
release) utilization
is less than 1, the value is 0.0.
Cumulativ FCIP .1.3.6.1.4.1.1588.4.1.1.4 Compression Ratio = current
e value/ 1000
Compressi Since for compression ratio we will
on Ratio take the current compression ratio
value
Receive TE .1.3.6.1.2.1.16.1.1.1.5 Receive EOF = Delta valueP1P /
EOF (1000 * 1000)
Other Other counters = Delta valueP1P
Counters
Current FCIP NA NA (ifHCInOctets + ifHCOutOctets) /
Compressi fcipExtendedLinkCompressedBytes
on Ratio .
1. Delta valueP1P: is the difference of value retrieved between the two consecutive poling cycles.
2. Polling intervalP2 P: duration between the two polling cycle in seconds
SMI Agent
 For Network Advisor that has more than 30K instances, the CIMOM takes more memory to
generate CIM instances.

 If user performs Enumerate Instances and total number of size is more than 2 MB for all
managed fabrics, it may result in out of memory issue. In this case, user has to increase the
CIMOM heap size to fetch zone database size of 2 MB. Note: For 1.6 MB of zone database
(144600 zone members), with 9 GB of heap size the Brocade_zonemembershipsettingdata
instances are retrieved.
Indications delivery depends on SAN Size and SNMP registration

The time to deliver the indication will vary based on Network Advisor SAN size selected during
installation. If large SAN size is selected, indication delivery time will be longer.
Provider classes may take more time to update the fabric changes if the switches managed in
Network Advisor are not SNMP registered. As this would cause a delay in indication delivery, all the
switches managed in Network Advisor should be SNMP registered
CIMOM Heap Size

The CIMOM heap size has been increase for small, medium and Large SAN Network Sizes:
Od heap size:
l
small
platform.32.cimom.conf.set.MAX_HEAP_SIZE = 768m
medium
Large
Curent Heap Size:

r
small
medium

Large
Logging for CIMOM
The default logging level is "INFO" in integrated Agent. To change the logging level to DEBUG,
update the "com.brocade" category value in cimom-log4j.xml file present in <Installation Dir>\conf
folder.
The log file size and number of log files also can be changed by modifying the file rolling appender
parameters in this cimom-log4j.xml file.
Logging Level, File size and Number of Log files can be changed by modifying the following fields:
"Log Level", "File Size" and "Number of Files" from Configuration Tool through CIMOM tab.
Service Location Protocol (SLP) support

The Management application SMI Agent uses Service Location Protocol (SLP) to allow applications to
discover the existence, location, and configuration of WBEM services in enterprise networks.
You do not need a WBEM client to use SLP discovery to find a WBEM Server; that is, SLP discovery
might already know about the location and capabilities of the WBEM Server to which it wants to
send its requests. In such environments, you do not need to start the SLP component of the
Management application SMI Agent.
However, in a dynamically changing enterprise network environment, many WBEM clients might
choose to use SLP discovery to find the location and capabilities of other WBEM Servers. In such
environments, start the SLP component of the Management application SMI Agent to allow
advertisement of its existence, location, and capabilities.
SLP installation is optional and you can configure it during Management application configuration.
Once installed, SLP starts whenever the Management application SMI Agent starts.
Management SMI Agent SLP application support
Management SMI Agent SLP application support includes the following components:
• slpd script starts the slpd platform
• slpd program acts as a Service Agent (SA). A different slpd binary executable file exists for
UNIX and Windows systems.

• slptool script starts the slptool platform-specific program
• slptool program can be used to verify whether SLP is operating properly or not. A different
slptool exists for UNIX and Windows.
By default, the Management application SMI Agent is configured to advertise itself as a
Service Agent (SA). The advertised SLP template shows its location (IP address) and the
WBEM Services it supports. The default advertised WBEM services show the
Management application SMI Agent:
• accepts WBEM requests over HTTP without SSL on TCP port 5988
• accepts WBEM requests over HTTPS using SSL on TCP port 5989
slptool commands
Use the following slptool commands to verify whether the SLP is operating properly.
• slptool findsrvs service:service-agent

Use this command to verify that the Management application SMI Agent SLP service is properly
running as a Service Agent (SA).
Example output: service:service-agent://127.0.0.1,65535

• slptool findsrvs service:wbem
Use this command to verify that the Management application SMI Agent SLP service is
properly advertising its WBEM services.
Example outputs:
service:wbem:https://10.0.1.3:5989,65535
service:wbem:http://10.0.1.3:5988,65535
This output shows the functionalities of Management application SMI Agent:
1. accepts WBEM requests over HTTP using SSL on TCP port 5989
2. accepts WBEM requests over HTTP without SSL on TCP port 5988
3. slptool findattrs service:wbem:http://IP_Address:Port
a. Use this command to verify that Management application SMI Agent SLP service is
properly advertising its WBEM SLP template over the HTTP protocol.
b. Example input: slptool findattrs service:wbem:http://10.0.1.2:5988
c. Note: Where IP_Address:Port is the IP address and port number that display when you
use the slptool findsrvs service:wbem command.
4. slptool findattrs service:wbem:https://IP_Address:Port
a. Use this command to verify that the Management application SMI Agent SLP service
is properly advertising its WBEM SLP template over the HTTPS protocol.
b. Example input: slptool findattrs service:wbem:https://10.0.1.2:5989

c. Note: Where IP_Address:Port is the IP address and port number that display when you
SLP on UNIX systems

This section describes how to verify the SLP daemon on UNIX systems.
SLP file locations on UNIX systems:
 SLP log—Management_Application/cimom /cfg/slp.log

 SLP daemon—Management_Application/cimom /cfg/slp.conf
 The SLP daemon can be reconfigured by modifying,
SLP register—Management_Application/cimom /cfg/slp.reg
You can statically register an application that does not dynamically register with SLP using SLPAPIs
by modifying this file. For more information about these files, read the comments contained in
them, or refer to http://www.openslp.org/doc/html/UsersGuide/index.html
Verifying SLP service installation and operation on UNIX systems:
1. Open a command window.

2. Type % su root and press Enter to become the root user.
3. Type # Management_Application/cimom/bin/slptool findsrvs service:service-agent and press
Enter to verify the SLP service is running as a Service Agent (SA).
4. Type # < Management_Application >/cimom/bin/slptool findsrvs service:wbem and press Enter
to verify the SLP service is advertising its WBEM services.
5. Choose one of the following options to verify the SLP service is advertising the WBEM SLP
template over its configured client protocol adapters.
• Type # Management_Application/cimom /bin/slptool findattrs
service:wbem:http://IP_Address:Port and press Enter.
• Type # Management_Application/cimom /bin/slptool findattrs
service:wbem:https://IP_Address:Port and press Enter.
Note: Where IP_Address:Port is the IP address and port number that display when you use the
slptool findsrvs service:wbem command.
SLP on Windows systems

This section describes how to verify the SLP daemon on Windows systems.
SLP file locations:

1. SLP log—Management_Application\cimom \cfg\slp.log

2. SLP daemon—Management_Application\cimom\cfg\slp.conf
The SLP daemon can be reconfigure the by modifying this file.
3. SLP register—Management_Application\cimom\cfg\slp.reg
statically register an application that does not dynamically register with SLP using SLPAPIs by
modifying this file. For more information about these files, read the comments contained in
them, or refer to http://www.openslp.org/doc/html/UsersGuide/index.html
Verifying SLP service installation and operation on Windows systems:
2. Launch the Server Management Console from the Start menu.
3. Click Start to start the SLP service.
4. Open a command window.
5. Type cd c:\Management_Application\cimom \bin and press Enter to change to the
directory where slpd.bat is located.
6. Type > slptool findsrvs service:service-agent and press Enter to verify the SLP service is
running as a Service Agent.
7. Type > slptool findsrvs service:wbem and press Enter to verify the SLP service is
advertising its WBEM services.
8. Choose one of the following options to verify the SLP service is advertising the WBEM
SLP template over its configured client protocol adapters.
1. Type > slptool findattrs service:wbem:http://IP_Address:Port and press Enter.
2. Type > slptool findattrs service:wbem:https://IP_Address:Port and press Enter.
Note: Where IP_Address:Port is the IP address and port number that display when you

BNA 14.2.0 GA Release Notes v1.6

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BNA 14.2.0 GA Release Notes v1.6

Hochgeladen von

Copyright:

Verfügbare Formate

Brocade Network Advisor 14.2.

Version of Document Summary of Changes Publication Date

v1.0 Initial Draft 12/21/16

v1.2 In Supported SAN Devices section the Footnote21 is updated 01/03/17

v1.3 Updated the defect 628481 with the workaround. 01/10/17

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 2

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 3

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 4

Brocade Network Advisor Version 14.2.0

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 5

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 6

Important considerations for web client users

Deprecated Web Client (14.0.x)

Fabric Insight Portal (new)

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 7

Fabric Insight Portal Filters (new)

Fabric Insight Portal Collections (new)

SAN Dashboards and AMP Dashboards (new)

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 8

Deprecated and retired features

Supported OS, Browsers, JRE

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 9

Recommended browser versions:

Supported JRE versions

Network Advisor version JRE version supported

14.2.0 JRE 1.8u112, JRE 1.8u121

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 10

b. Open the java.security file and change the jdk.certpath.disabledAlgorithms=MD2,

Security Vulnerability Fixes

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 11

Supported SAN Devices

Fabric OS version Switch or Director Type SAN Devices

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 12

Brocade Analytics Monitoring Platform21

Fabric OS version Blade Type SAN Devices

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 13

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 14

Network OS version NOS Device Type

Network OS v5.0.1_tcn VDX 2741

FI/NI Versions IP Device Type

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 15

12.1. x2, 12.2. x2, 12.3.x, 12.4.x, 12.5.0x ServerIron ADX

Supported Wireless Devices

Wireless Controllers Access Points FW version

* Aruba Instant Access Points are supported in Network Advisor.

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 16

LPe32002-M2 32Gb 2-port PCIe Fibre Channel CIM Provider Version:

Boot Code and Firmware Version:

QLE2562-CK 8Gb, Dual Port, FC HBA, x4 PCIe

Corp ISP2532-based 8Gb Fibre Channel to PCI Driver Versions:

QLE2742 PCIe 3.0 ×8 (dual-port) 32G FC HBA Firmware Versions:

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 17

ESXi 5.5, 6.0

Installing Network Advisor

To install Network Advisor on Windows (Server)

To install Network Advisor on Linux (Server)

To launch the Network Advisor Client

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 18

Note 2: The Remote client can be launched in the following ways

The web client login page displays.

 Click Desktop Client.

 Choose one of the following options:

 Click the Download client bundle (64-bit OS only) link.

Brocade Network Advisor 14.2.0 GA Release Notes v1.6 19