brocade network advisor 12.2 - · pdf fileswitch type san devices – b-series brocade...

Brocade Network Advisor 12.2.0 GA Release Notes v1.0

February 14, 2014

Document History

Document Title Summary of Changes Publication Date

Brocade Network Advisor 12.2.0 GA Release Notes v1.0 Initial version Feb 14, 2014

Brocade Network Advisor 12.2.0 GA Release Notes v1.0 2

© 2014 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health,

ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET

Health, Brocade One, Extraordinary Networks, MyBrocade, VCS, and VDX are trademarks of Brocade

Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or

service names mentioned are or may be trademarks or service marks of their respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or

implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade.

Brocade reserves the right to make changes to this document at any time, without notice, and assumes no

responsibility for its use. This informational document describes features that may not be currently

available. Contact a Brocade sales office for information on feature and product availability. Export of

technical data contained in this document may require an export license from the United States

government.

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any

person or entity with respect to any loss, cost, liability, or damages arising from the information contained

in this book or the computer programs that accompany it.

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.

http://www.brocade.com/support/oscd


Contents

Product Overview................................................................................................................................................... 4

Brocade Network Advisor Version 12.2.0 .............................................................................................................. 4

Key Feature Enhancements .................................................................................................................................... 4

Incremental Hardware/Firmware Support ............................................................................................................. 4

Migrations & Upgrades ............................................................................................................................................ 4

Operating Systems Supported ................................................................................................................................ 5

JRE Support .............................................................................................................................................................. 6

Device Platform & Hardware Support Requirements ............................................................................................ 6

Installing Network Advisor ..................................................................................................................................... 9

To install Network Advisor on Windows (Server) .................................................................................................. 10

To install Network Advisor on Linux (Server) ........................................................................................................ 10

To launch the Network Advisor Client ................................................................................................................... 10

Important SAN Notes ........................................................................................................................................... 11

Important IP Notes .............................................................................................................................................. 14

Common Issues for SAN and IP ........................................................................................................................... 15

Patch Installer troubleshooting ............................................................................................................................. 16

Performance Statistics Counters - Calculation Formulae ................................................................................... 17

SMI Agent ............................................................................................................................................................ 19

Logging for CIMOM ................................................................................................................................................ 19

Service Location Protocol (SLP) support .............................................................................................................. 20

Documentation Updates ..................................................................................................................................... 22

Enhancements (RFEs) in Network Advisor 12.2.0 ............................................................................................... 23

Defects ................................................................................................................................................................ 23

Open Defects in Brocade Network Advisor 12.2.0 .............................................................................................. 23

Closed with Code Change in Brocade Network Advisor 12.2.0 .......................................................................... 32

Closed without Code Change in Brocade Network Advisor 12.2.0 ..................................................................... 40


Product Overview

Brocade® Network Advisor greatly simplifies daily operations while improving the performance and reliability of

the overall Storage Area Network (SAN) and IP networking environment. Brocade Network Advisor unifies under

a single platform, full lifecycle network management for SAN, LAN and converged networks. Brocade Network

Advisor provides a consistent user experience, across the entire Brocade portfolio of switches, routers and

adapters. This network management tool offers flexible and proactive SAN/IP network performance analysis in

addition to IP network configuration change deployment and monitoring for compliance. Brocade Network

Advisor supports Fibre Channel SANs, including 16 Gbps platforms, Layer 2/3 IP networks (including those

running Brocade VCS® Fabric technology), wireless networks, application delivery networks, and Multiprotocol

Label Switching (MPLS) networks for service providers.

Brocade® Network Advisor can reduce operation expenditures and help organizations focus on strategic IT

initiatives by providing a common network management tool for provisioning, monitoring, reporting and

troubleshooting. Brocade Network Advisor provides customizable health and performance dashboards, with an

easy-to-use graphical user interface and comprehensive features that automate repetitive tasks. With Brocade

Network Advisor, storage and network administrators can proactively manage their SAN/IP network

environments to support non-stop networking. BNA also provides network administrators the ability to quickly

access network topology, health and performance data required to troubleshoot and remediate network

issues.

Brocade Network Advisor Version 12.2.0

Revision 12.2.0 of Brocade Network Advisor supports Network OS v4.1.0. Additionally, there is support for new

VDX hardware as listed below.

Key Feature Enhancements Support for VCS Virtual Fabrics

Support for Virtual Routers

Support for NOS Access Gateway (AG)

NOS Trace route enhancements

NOS Fabric Watch events integration in Dashboard

Incremental Hardware/Firmware Support Network OS v4.1.0

VDX6740T-1G

VDX 8770 Modules: 6X100G, 27X40G, 48X10G Base-T

2X10G Management Module for SX800 and SX1600 Chassis

vRouter 5400 v6.6

ICX6680, ICX7750-48C, ICX7750-29Q

Fast Iron firmware v8.0.1

Migrations & Upgrades

Network Advisor 12.0.X (12.0.0 – 12.0.4) and 12.1.X (12.1.0 – 12.1.5) running on the Linux and Windows

operating systems can be upgraded to Network Advisor 12.2.0.


Note 1: Enterprise and Professional Plus editions are not supported on 32-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 2: Direction migration from pre-12.0.x releases to 12.2.0 is not supported. Refer to Table 29 from

Installation and Migration Guide for migration paths from DCFM, INM and Network Advisor 12.2.X or earlier

releases.

Note 3: Refer to Table 31 from Installation and Migration Guide for SMI Agent only migration paths

Note 4: SAN users may add IP management to Network Advisor 12.2.0 for SAN+IP network management with

the procurement of the IP functionality. Also, IP users may add SAN management to Network Advisor 12.2.0 for

SAN+IP network management with the procurement of the SAN functionality.

Operating Systems Supported

Note: Below is the minimum required system physical memory for running Network Advisor 12.2.0 (server plus

one local client):

Professional Edition: 4GB (32-bit OS), 8GB (64-bit OS)

Pro-plus and Enterprise Editions (supported on 64-bit OS only):

o Small SAN fabric and/or small IP network: 8GB

o Any combination that includes a medium/large SAN fabric or a medium/large IP

network: 16GB

Operating Systems (64-bit) / Architecture (Supported for SAN, IP, and SAN+IP)

Windows Server 2008 R2 Standard, Enterprise, Datacenter

Windows Server 2012 and 2012 R2 Standard, Datacenter

Windows 7 Enterprise

Windows 8 and 8.1 Enterprise

Red Hat Enterprise Linux Adv 6.1, 6.2, 6.3, 6.4, 6.5

Oracle Enterprise Linux 6.1, 6.2, 6.3, 6.4

SUSE Linux Enterprise Server 11 (x86)

Operating System (32-bit) / Architecture

Note: Only Network Advisor Professional Edition (SAN or IP) is supported on a 32-bit Operating System. Pro-Plus

and Enterprise Editions require a 64-bit Operating System for installation.

Windows 2008 Standard (x86)

Windows 7 Enterprise (x86)

Red Hat Enterprise Linux Adv (x86) 6.1, 6.2, 6.3

Oracle Enterprise Linux (x86) 6.1, 6.2, 6.3

SUSE Linux Enterprise Server 11 (x86)

Note: All the above Operating Systems are supported as Guest VMs on VMware ESXi 5.5, KVM (RedHat

Enterprise Linux 6.3/6.4 Adv) and Microsoft Hyper-V (Hyper-V Server 2008 R2 SP1, Windows Server 2012)

Browser Support

Internet Explorer 10

Firefox 23


JRE Support

Network Advisor version JRE version supported

11.2.0 JRE 1.6u24

11.2.1 JRE 1.6u26

11.3.0, 12.0.0 JRE 1.6u33

12.0.1 JRE 1.7u11

12.0.2 JRE 1.7u17

11.2.2, 12.0.3, 12.1.0, 12.1.2, 12.1.3 JRE 1.7u25

12.0.4, 12.1.4, 12.1.5 JRE 1.7u45

12.2.0 JRE 1.7u51

Note: Web Tools launch from Network Advisor is also supported for the above combinations.

Device Platform & Hardware Support Requirements

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.

Operating System Device Type

Network OS v4.1.0 VDX 6740-T-1G, 6740, 6740T, 8770, 6710, 6720, 6730,

6746

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, 2730

Network OS v2.11 , v2.1.1, v2.1.1a,

v2.1.1b, v2.1.2a

VDX 6710, 6720, 6730, 2730

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,

7.3.x, 7.4.x, 8.0.x FastIron ICX 6610

7.4.x, 8.0.x FastIron ICX 6430, 6450, 7750-48C, 7750-29Q

7.5a Brocade 6650

5.0.x , 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x,

5.6.x

NetIron CES, CER, MLX, XMR, MLXe

2.0.x, 2.1.x, 2.2.x Brocade 6910


Operating System Device Type

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

10.2.01x , 11.0.x ServerIron

4.1.x, 4.2.x, 7.3.x, 7.4.x, 8.0.x TurboIron 24X

4.3.1.0, WiNG 5.1, 5.2, 5.3, 5.4 Wireless Controllers - RFS 4000, RFS 6000, RFS 7000

4.1.x , 4.1.01x FastIron FES

Vyatta vRouter 5400 v6.6

Footnotes:

1 Network OS 2.0 is not supported.

212.1.0f and 12.2.1 are not supported.

Switch Type SAN Devices – B-Series

FOS v5.0.x, v5.1.x, v5.2.x, v5.3.x,

v6.0.x. v6.1.x, v6.2.x, v6.3.x,

v6.4.x, v7.0.x, v7.1.x, v7.2.x

Brocade 3250

Brocade 4100

Brocade 75001

Brocade 200E

Brocade 49002

Brocade 50003

Brocade AP76004

Brocade 3005

Brocade 51005

Brocade 53005

Brocade 650513

Brocade 651012

Brocade 652014

Brocade 80009

Brocade 12000

Brocade 780010

Brocade VA40-FC

Brocade Encryption Switch7

Brocade 48000 with FC4-16, FC4-32 and FC4-482 blades

Brocade 48000 with FR4-18i1

Brocade 48000 with FC4-16IP2

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


Switch Type SAN Devices – B-Series

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 and FC16-

48 blades

Brocade DCX 8510-413 and DCX 8510-813 with FC8-32e and FC8-

48e blades

Blade Type SAN Devices – B-Series

FOS v5.2.x, v5.3.x, v6.0.x,

v6.1.x, v6.2.x v6.3.x,

v6.4.0,v7.0.x, v7.1.x, v7.2.x

Brocade 3014

Brocade 3016

Brocade 4020

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

Footnotes:

1 Requires FOS v5.1.0 or higher


2 Requires FOS v5.2.0 or higher 3 Requires FOS v5.2.1 or higher 4 Requires FOS v5.3.0 or higher 5 Requires FOS v6.1.0 or higher 6 Requires FOS v6.0.0 or higher 7 Requires FOS v6.1.1_enc or higher 8 Requires FOS v6.2.0 or higher 9 Requires FOS v6.1.2_CEE or higher 10 Requires FOS v6.3.x or higher 11 Requires FOS v6.4.0 or higher 12 Requires FOS v7.0.0 or higher 13 Requires FOS v7.0.1 14 Requires FOS v7.1.0 or higher

Adapters Types

1.1, 2.1.1.0, 2.0, 2.2, 3.0, 3.1,

3.2

Brocade 415,425,815,825

Brocade 8041

Brocade 1010,1020,10072

Brocade 17413

Brocade 18604

Brocade 18675

Footnotes:

1 Requires v2.1.1.0 or higher 2 Requires v2.0 or higher 3 Requires v2.2 or higher 4 Requires v3.0 or higher 5 Requires v3.0.3 or higher

Virtual Machine Management:

vCenter and ESXi Supported Versions

ESX 4.0, 4.1

ESXi 4.0, 5.0, 5.1

VCenter 4.0, 4.1, 5.0, 5.1

Installing Network Advisor

Installation instructions are provided for the following operating systems:

Microsoft Windows

Linux

The Network Advisor Server runs as multiple services on Windows and multiple processes on Linux; and they

start automatically after 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.

To install Network Advisor on Linux (Server)

1. Download and extract the tar.gz archive

2. Navigate to the Linux folder.

3. Execute Install.bin from the File Manager window.

4. Follow the instructions to complete the installation.

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:

Windows: Select Start > Programs > Network Advisor 12.2.0 > Network Advisor 12.2.0

Windows:

Client can be launched via Desktop icon.

Launch command prompt and go to the location “<Install location>/bin” and type “dcmclient”

Linux:

Client can be launched via Desktop icon.

Launch terminal and go to the location “<Install location>/bin” and type “sh dcmclient”

Windows and Linux: Follow the below steps on launching the client from a web browser.

- To launch the Network Advisor Client from a remote host, launch the client as follows:

Open a browser window and type the Network Advisor server hostname or IP address in the Address

field; for example:

https://NetworkAdvisorServerhost1.companyname.com/

https://192.x.y.z/

- If when the Network Advisor server was installed, a Network Advisor web server HTTPS port number

was specified (instead of the default443); you must specify the port number after the hostname or IP

address. In the following examples, 8080 is the web server port number:

https:// NetworkAdvisorServerhost1.companyname.com:8080/

https://192.x.y.z:8080/

Please note that the required Client Oracle JRE version has now changed to 1.7.0_51. For remote clients, this

JRE needs to be installed prior to establishing a server connection.

Note 1 :

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.

https://networkadvisorserverhost1.companyname.com/

https://192.x.y.z/

https://192.x.y.z:8080/


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 check box for Enable Java content 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 BNA client.

Note 2 :

On a Windows server, if only ‘Administrators’ have access to a drive, windows does not allow Postgres to

create some required directories and a result, migration from a previous version of Network Advisor to a

newer supported version fails. The following steps need to be followed to resolve the issue:

1. Make sure that the previous version of Network Advisor is up and running.

2. Right click on the drive where the new version of Network Advisor is intended to be installed (E.g. :D)

3. Navigate to the Security tab -> Edit -> Add

4. Add “Authenticated Users” and give full permission, click “Ok”

5. Now install the new version of Network Advisor and start the migration progress.

Important SAN Notes

1. Host based stand-alone SMI agents cannot manage products with Fabric OS v7.0 and above. It

requires use of the integrated SMI Agent with Brocade Network Advisor 12.1.0 and above.

2. Supported AG limits are the following: 64 bit OS - max of 200 AGs

3. Network Advisor cannot manage an ESXi 5.0 host due to a VMware issue (KB 2012672: SFCB CIMOM

on ESXi 5.0 is incompatible with JRE 1.6 U29 and later). The user is hence required to update to ESXi

5.0 update 1 or later to be able to manage the host in Network Advisor through the host adapter

discovery.

4. 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>

http://java.com/en/download/help/win_controlpanel.xml


If the above does not work, go to Server > Options > Software Configuration > FTP/SFTP/SCP, and

uncheck the SCP/SFTP option.

5. The Encryption Smart Card Driver is only supported for 32 bit Linux. It is not supported on 64 bit

Linux.

6. Firmware Download operation on Fabric OS switches fails via SCP/SFTP when trying to upgrade from

FOS v6.3.2b to v6.4.2b4. The workaround is to use the FTP option in BNA to perform the firmware

download operation.

7. Firmware Download operation on Fabric OS switches fails when trying to upgrade from FOS v6.4.2a to

v7.0.2c. The workaround is to use CLI for this operation.

8. Trying to move 200+ ports to a Logical Switch with ‘Reset to Default’ option selected, results in

operation time-out.

9. 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.

10. There will be a delay in populating the Gige port details in the Network Advisor client if the server IP is

not registered on the switch to receive SNMP traps from the switch.

11. When the active and defined zone sets have identical zones which differ only by the case of their

names, user will get alerted that the active zone set is different from the defined configuration in the

zone database. The workaround is to edit the identical zone names (for such zones) in defined set, so

that after modification, both zone names are identical in active and defined zone sets.

12. After upgrading to Network Advisor 12.x from 11.x, SSL-based product communication will fail if the

devices have ‘weak’ authentication certificates. The user will see a ‘4002’ error on attempting to

discover such devices. Devices discovered prior to migration will not be manageable in Network

Advisor after migration. Java 1.7 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.7.

Please refer to the ‘Secure Sockets Layer protocol’ section of FOS Admin guide for details on updating

certificates.

13. Receive Throughput measure is not updated in Flow Vision dialog.

14. D-port test fails for F-ports with the result as “null” in the report.

15. In Real Time performance graphs, percentage utilization will fluctuate between 0 – 100 if a single port

is selected. The workaround is to select more than one port while generating Real Time performance

graphs.

16. 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.

17. 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.

18. On FOS switches running firmware versions v7.2.0 and v7.2.1, if LSAN tags are added or removed

from CLI, the corresponding events are not received by Network Advisor in Master Log. As a result,

adaptive polling is not initiated and the changed tags are updated in Network Advisor after the next

polling cycle.

19. 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

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 adding the IP address of the chassis using the add

dialog.

Destination columns are blank for Brocade Encryption Switch in top talkers dialog

When the Top Talkers dialog box is launched for the Brocade Encryption Switch, the columns ‘Destination,

Destination port and Destination switch port are sometimes empty.

SSL connections using certificates with MD5 signatures

To avoid potential security vulnerabilities, Network Advisor versions 12.0 and later do not support SSL

connections using certificates with MD5 signatures. If Network Advisor is configured to use HTTPS instead of

HTTP when communicating with SAN switches, and the SAN switch has a certificate installed that is signed with

an MD5 algorithm, discovery of the switch fails with the following pop-up message: “Authentication failure

during discovery operation: 4002.”

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 32-bit Windows or Linux: <install-dir>/jre/lib/security/java.security

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:


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.

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:

In 7500 and FR4-18i, VE ports cannot be reset to default unless their corresponding GE ports

are cleared of their FCIP configurations.

In 7800 and FX8-24, GE ports cannot be reset to default unless their corresponding VE ports

are cleared of their FCIP configurations.

Important IP Notes

Miscellaneous Important Notes that Apply to IP Installations

1. Prior to v12.2.0 release, Network Advisor would attempt to discover IP products with default

community strings (‘public’ as read community and ‘private’ as write community) without requiring

this to be configured in Global Settings tab of IP Discovery dialog. However, this could trigger login

attempts failure and could send alarms to Network Administrators if the write community string

configured on the device did not match Network Advisor’s default write community string (private).

To avoid this issue, starting Network Advisor v12.2.0 release, discovery process will not use

default write community string if it is not configured in Global Settings. User has to explicitly

configure Read-Write community strings in ‘Add Device’ dialog or Global Settings dialog.

2. Adaptive polling turned off by default for all IP devices (even for migrated servers).

3. SNMP write credentials will not be populated by default for IOS devices.

4. 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.

5. NOS device configuration backup will only be collected for the following cases:

In case of VCS cluster, Manual Discovery/Rediscovery of the cluster members

CLI manager configuration deployments

6. Syslog messages will not be received for the VDX 8770 that is configured with different IP

addresses for CPs

7. Simplified image upgrade is recommended for NI devices running 5.3 and above.

8. Fixed Form Factor 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.

9. When two ports of the same storage are connected to two VDX devices, only of the attached ports

is displayed in the Zoning dialog.

10. On NOS switches, Technical support data collection will fail, if System Time is not set on the

switch. The operation will be in progress for 10 to 20 minutes and eventually fail. Setting System

Time resolves this issue.

11. On VDX devices managed through in band IP address in Network Advisor, firmware download and

configuration backup operations fail.


12. Cluster IP address does not fall back to the Physical IP address of the Principal node, when the

Virtual IP Address of the cluster is not reachable from Network Advisor.

13. In VLAN Topology view, RSPAN and TLS information associated with Virtual Fabrics is not

displayed. The VLAN Manager dialog displays this information.

IP Address and Detailed Reports

14. IP Management Ports will not be consistent with the CLI port naming conventions. These are

caused by SNMP index and port name inconsistencies. In some cases, Management ports will not

be displayed in the reports.

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 Image Update on FastIron devices using Configuration Wizard using "SCP only" or "SCP

then TFTP" results in the corruption of the flash to which image is pushed. Use CLI as

workaround.

3. Firmware Download to NetIron CES devices fails via SCP with the error message ‘there is not

enough space on MP flash’.

Common Issues for SAN and IP

Miscellaneous Important Notes that Apply to both SAN and IP Installations

1. 64 bit OS is required to run Network Advisor Professional-Plus and Enterprise Editions.

2. M Model switches are unsupported as Seed switch or member switch from Network Advisor 12.0.0.

3. Privileges related to SAN and IP features are prefixed with ‘SAN –‘and ‘IP –‘strings. After migration

from an older version, new privilege names will be displayed in the Role Management dialog with

these prefixes.

4. Network Advisor server startup and restart can take up to 10+ minutes to complete.

5. When configuring Brocade Network Advisor in SSL enable mode in application configuration wizard,

please ensure that both HTTP and HTTPS ports are free and available for Network Advisor. Currently

the application checks only if the HTTPS configured port is available and not the HTTP port.

6. 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.

7. Starting 12.0, the number of client connections supported 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:

1. 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 = 256MB

To: shared_buffers = 1024MB

2. Server needs to be restarted.


8. 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.

9. If you are using the ODBC connection from a remote host to the database, after migrating to 12.0.X,

you will no longer be able to connect from the remote host. If you want to connect from the remote

host, please refer to the “Configuring remote client access to the database” section in the “Installation

and Migration” guide.

10. When attempting to install Network Advisor on a Linux Server, if the message ‘Insert New Media’ is

displayed, the below command needs to be executed from a terminal:

ulimit –n 2000

11. Technical Support data collection for discovered Products fails through an external Linux FTP server on

a Windows installation of Network advisor.

12. 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.

13. During installation on a Linux server, if user sets the password for Network Advisor database starting

with a ‘$’, installation of the application will fail.

Patch Installer troubleshooting

Patch installer may not launch if UAC is enabled on a Windows 7/8/2008/2008 R2/2012 Editions. User has

to 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.

Domestic and International Modem based Call Home is no longer supported for

Brocade Call Home Centers in 12.0 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 with these Call

Home centers to Brocade email call home. If you do not have any switches assigned to the Brocade

Domestic and Brocade International call centers, please select “No” in the config wizard when the

message is displayed.

Note: EMC and IBM Call Home Centers will continue to support Modem Call Home functionality.

Support Saves may take a long time with large databases

As databases grow larger from Event, sFlow, and Performance Collector data, the support save operation may

take a long time to run. Larger databases will promote longer support save operations. Make sure you have a

minimum of 20GB disk space for support save and backup operations.

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 (12.2.x) from OEM1 version to OEM2 version:

- Partially uninstall the source BNA 12.2.x OEM1 version

- Now install BNA 12.2.x OEM2 version

- In the ‘copy data and settings’ page, browse to the BNA 12.2.x OEM1 version and continue

with the migration.

Migrating BNA (pre-12.2.x) OEM1 version to BNA 12.2.x OEM2 version:

- Install the source BNA pre-12.2.x OEM1 version

- Now install BNA 12.2.x OEM2 version

- In the ‘copy data and settings’ page, browse to the BNA 12.2.x OEM1 version and continue

with the migration.

Virtual Connect Enterprise Manager (VCEM) Support

The supported and tested versions are listed below:

HP SIM Version v6.2, v7.1

HP VCEM version v6.2, v7.1

OA firmware Onboard Administrator (OA) v2.41 or later

VC E-net module firmware(HP VC 8Gb 20-

Port FC Module &

HP VC 8Gb 24-Port FC Module)

v3.15

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 QMH2562 8Gb 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.


Counter Name Type Protocol

used

Source value Formula

TX FC SNMP .1.3.6.1.3.94.4.5.1.6

TX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

RX FC SNMP .1.3.6.1.3.94.4.5.1.7 RX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

TX GE SNMP .1.3.6.1.2.1.31.1.1.1.10 TX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

RX GE SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

TX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.10 TX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

RX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

Uncompressed

Tx/Rx MB/sec

FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.6 (Delta value1 / (1000 * 1000)) / (Polling

interval2)

TX EE

Monitors

HTTP PortRX (variable from the

return html file)

TX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

RX EE

Monitors

HTTP PortTX (variable from the

return html file)

RX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

TX HBA, CNA HCM API NA TX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

RX HBA, CNA HCM API NA RX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

TX TE SNMP .1.3.6.1.2.1.31.1.1.1.6 TX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

RX TE SNMP .1.3.6.1.2.1.31.1.1.1.10 RX = (Delta value1 / (1000 * 1000)) /

(Polling interval2)

TX% / RX% FC, GE,

FCIP, HBA,

CNA

NA NA TX% / RX% FCIP N/A N/A TX% or RX%

= ((bytes transferred) / (maximum bytes

transmitted))*100

where maximum bytes transmitted =

tunnelspeed * 134217728

Note: Maximum bytes transmitted 1

Gbps

If utilization is less than 1, the value is

0.0.

TX% / RX% FC, GE, HBA, CNA N/A N/A

TX% or RX% = ((TX or RX) /((134217728

* port speed)* (polling interval2)))

TX% / RX% (Pre

6.4.1 Edison

release)

TE NA NA TX% or RX% = ((TX or RX) /

((134217728 * 10)*( Polling interval2)))

* 100

If Utilization is less than 1 then the value

is it to 0.0

Cumulative FCIP .1.3.6.1.4.1.1588.4.1.1.4 Compression Ratio = current value/


Compression Ratio 1000

Since for compression ratio we will take

the current compression ratio value

Receive EOF TE .1.3.6.1.2.1.16.1.1.1.5 Receive EOF = Delta value1 / (1000 *

1000)

Other Counters Other counters = Delta value1

Current

Compression Ratio

FCIP NA NA (ifHCInOctets + ifHCOutOctets) /

fcipExtendedLinkCompressedBytes.

1) Delta value1: is the difference of value retrieved between the two consecutive poling cycles.

2) Polling interval2 : duration between the two polling cycle in seconds

SMI Agent

1. For BNA that has more than 30K instances (2 MB zones), the CIMOM takes more memory to generate

CIM instances.

If user performs Enumerate Instances or Enumerate Instances Names and total number of size is

more than 2 MB for all managed fabrics, then CIM_ERROR_FAILED will be thrown as the "Total Zone

DB size is more than 2 MB. For such configuration, User need to use Association calls

Note: if the total zone DB is more than 1 MB/more than 10000 instances then user should change

the max jvm heap size to 2048MB to fetch the data without failure in 64 bit machine

2. SMI alert indication BRCD60 is not sent out to SMI clients if Fabric OS switches are discovered but

SNMP trap registration has failed. Ensure that Brocade Network Advisor server is successfully

registered for traps on all switches.

3. If DCB switches are running Fabric OS 6.3.x and 6.3.1_cee, VLAN/ACL deployment through SMI-A will

fail. It is required to upgrade the DCB Fabric OS to 6.4.x/6.3.1_dcb/7.0.X for VLAN/ACL deployment

support through SMI Agent.

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

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 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:

accepts WBEM requests over HTTP using SSL on TCP port 5989

accepts WBEM requests over HTTP without SSL on TCP port 5988

slptool findattrs service:wbem:http://IP_Address:Port

o Use this command to verify that Management application SMI Agent SLP service is properly

advertising its WBEM SLP template over the HTTP protocol.

o Example input: slptool findattrs service:wbem:http://10.0.1.2:5988


o Note: Where IP_Address:Port is the IP address and port number that display when you use the

slptool findsrvs service:wbem command.

slptool findattrs service:wbem:https://IP_Address:Port

o Use this command to verify that the Management application SMI Agent SLP service is

properly advertising its WBEM SLP template over the HTTPS protocol.

o Example input: slptool findattrs service:wbem:https://10.0.1.2:5989

o 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 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.

o Type # Management_Application/cimom /bin/slptool findattrs

service:wbem:http://IP_Address:Port and press Enter.

o 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:

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



SLP daemon—Management_Application\cimom\cfg\slp.conf

The SLP daemon can be reconfigure the by modifying this file.

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:

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

2. Click Start to start the SLP service.

3. Open a command window.

4. Type cd c:\Management_Application\cimom \bin and press Enter to change to the directory where

slpd.bat is located.

5. Type > slptool findsrvs service:service-agent and press Enter to verify the SLP service is running as a

Service Agent.

6. Type > slptool findsrvs service:wbem and press Enter to verify the SLP service is advertising its WBEM

services.

7. Choose one of the following options to verify the SLP service is advertising the WBEM SLP template

over its configured client protocol adapters.

• Type > slptool findattrs service:wbem:http://IP_Address:Port and press Enter.

• 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 use the

slptool findsrvs service:wbem command.

Enumeration issue with Brocade 8000 running on Fabric OS 6.3.x or lower

Enumeration instance fails for the following classes:

Brocade_EthernetPortLANEndPoint, Brocade_EthernetAdminDomainHostedLanEndPoint,

Brocade_EndpointOfNetworkPipe, Brocade_EthernetSwitchHostedLANEndPoint,

Brocade_InEthernetLogicalNetwork, Brocade_LANEndpoint, Brocade_PlatformHostedLANEndPoint

When Brocade Network Advisor manages a Brocade 8000 running on Fabric OS 6.3.x or lower, connected to

FDMI enabled CNA.

Instance class key property with special character

Getinstance operation fails if the key property value contains semicolon or non printable character.

FC port type value for imported HBA’s

Brocade_topologyview.AntecedentFCPortType property value corresponding to the imported HBA is shown as L-

port.

Documentation Updates

Network Advisor Installation and Migration guide refers to ‘Professional Plus Trial’ license (Tables 1, 26 and

30). This license is no longer valid and reference to this license will be removed in the subsequent version of

Network advisor documentation.



Enhancements (RFEs) in Network Advisor 12.2.0

Port Mirroring - Configure port mirroring through element manager dialog.

sFlow Configuration, Monitoring for the marked port/ports through element manager dialog.

Card level status should displayed in the element manager dialog.

Display SFP detailed status in the element manager.

Support reset of device counters in the MLX element manager.

Bill of Material (B0M) - Create Bill of Material (BoM) report for each managed network element. Power

supplies, fabrics and optics shall be visible in the device report.

Option to do a MR switchover when selecting a device in the MLX element manager.

Summary Stats per port and device (Ether stats support for Real-time/Historical graphs) should be

displayed in the element manager.

Option to Enable/Disable Ports /preferable also ports inside of an LAG in the element manager

Include Event description in the Email Subject for Notifications

Include the Port details in the Email and Master log event of the Psuedo Event

LSAN Zoning: Support for Configuring Alias

NOS 4.1 Support for NETCONF format change

Honor the Top-N threshold based on the port speed

New measures added for historical data collection for NOS Ethernet ports: Tx Power, Rx Power, Tx

Bias Current, Temperature, Wavelength & Voltage

Optionally publish the Historical Graph to the active dashboard

Support launching trace route for the VMs that are connected to VCS managed

Add Trace Route Launch menu item to VM node context menu on Device Tree, Search dialog ( Auto

complete search, IP address population)

Support for IP related performance statistics for VMs

Support for IP network connectivity for VMs

Defects

Open Defects in Brocade Network Advisor 12.2.0

This section lists defects with High and Medium Technical Severity open in Network Advisor 12.2.0 as of 4:00 PM on Feb 13, 2014. While these defects are still formally “open,” they are unlikely to impede Brocade customers in their deployment of Network Advisor 12.2.0 and have been deferred to a later release.

None of these defects have the requisite combination of probability and severity to cause significant concern to Brocade customers. Note that when a workaround/recovery to an issue is available, it is provided; otherwise, no recommended workaround is available at this time.

Defect ID: DEFECT000465401

Technical Severity: Medium Probability: Medium

Product: Network Advisor Technology: Fault Management

Reported In Release: Network Advisor12.1.0 Technology Area: Event Actions

Symptom: User cannot receive special handling events

Condition: Issue occurs when event action is configured with policy as frequency bound and action type as

special handling



Technical Severity: Medium Probability: Low

Product: Network Advisor Technology: Device Management

Reported In Release: Network Advisor12.0.2 Technology Area: Device configurations

Symptom: Interface details are not shown correctly for Cisco device

Condition: Issue is seen only with Cisco 2950


Technical Severity: Medium Probability: High



Symptom: User will see incorrect error message when configuration backup fails

Condition: Issue occurs when super user password is not updated for the device in Network Advisor





Symptom: AG to Switch Connection details are duplicated in Connection properties dialog

Condition: Issue occurs only when F-port trunk is enabled





Symptom: User is not allowed collect the Support Save and perform config upload using FTP

Condition: This issue is observed when BNA is upgraded to 12.0.2



Product: Network Advisor Technology: Monitoring

Reported In Release: Network Advisor12.1.0 Technology Area: Dashboards

Symptom: Historical Graph options are not persisted on re-launching the Graph Options dialog

Condition: This issue is observed when multiple measures are selected from Graph Options




Reported In Release: Network Advisor12.0.1 Technology Area: Zoning

Symptom: Logging might be blocked while Purge is in Progress

Condition: Issue might occur only when large data is being purged


Technical Severity: High Probability: Medium



Symptom: Fabric Segments with the reason ‘Zone Conflict’ when an alias is created with upper case WWN on

one switch and the same alias with lower case WWN on other switch using CLI.

Condition: Issue occurs only when trying to create the same alias with case sensitive character for WWN through

difference interfaces.






Symptom: Warning icon and TI Zones are displayed incorrectly in the Active Zone Configuration tab .

Condition: Issue is observed only when activating the zone configuration with TI Zones from the CLI

Recovery: Activate the Zone configuration from the Zoning dialog





Symptom: Compare Zone DB dialog becomes non-responsive when comparing 1 MB Zone configurations with

more than 1000 nodes in the switches

Condition: This issue is observed when the user tries to compare two zone configurations with more than 1000

nodes




Reported In Release: Network Advisor12.2.0 Technology Area: VLAN

Symptom: An interface cannot be configured with Untagged mode after removing the interface from the same

VLAN.

Condition: When the user tries to configure the Interface with untagged mode on a VLAN followed by removing

the interface from the same VLAN and again adding it to the same VLAN.



Product: Network Advisor Technology: Partner Integration

Reported In Release: Network Advisor12.0.3 Technology Area: SMI Agent

Symptom: User is not allowed to have the zone configurations when multiple users perform zone transactions at

the same time.

Condition: This issue is observed when more than 1 SMI-A Client is used at the same time





Symptom: Attempting to re-sync a running-configuration from VDX fails

Condition: This issue is observed for any config change on the VDX device





Symptom: All the other VLAN deployments will not be performed if the first deployment fails

Condition: This issue is observed when the user tries to deploy the configuration for tagged and untagged modes

for two different VLANs at a time.

Recovery: Remove the failing configuration from the batch and deploy other configurations






Symptom: Changing the switch port mode from access to trunk or vice versa, removes the VLAN configuration

on the interface

Condition: Issue occurs only for VDX devices.

Recovery: Deploy the required configuration again for the interface



Product: Network Advisor Technology: Other

Reported In Release: Network Advisor12.2.0 Technology Area: Other

Symptom: User will not able to see updated PHV widget

Condition: Issue occurs when the client is launched for the first time after installation

Recovery: Re-launch the client





Symptom: Members are not listed in the alias tree in Fabric Scope.

Condition: Issue occurs only for alias created from LSAN Scope and navigating to Fabric Scope

Recovery: Re-launch the Zoning dialog





Symptom: Re-sync backup fails for a cluster running NOS 4.0.0.

Condition: Issue occurs only on IPV6 with NOS 4.0.

Recovery: Manually initiate the save running configuration operation.



Product: Network Advisor Technology: Security

Reported In Release: Network Advisor12.0.0 Technology Area: Encryption (SAN)

Symptom: User will not be able to register key vault certificate other than Decru for the secondary key vault

Condition: This issue is observed only when the Secondary Key Vault





Symptom: Error Message is thrown when the user tries to search for the members present in one or more aliases

within the Alias in the LSAN Scope

Condition: This issue is observed when trying to search for members present within the aliases.





Reported In Release: Network Advisor12.2.0 Technology Area: SNMP Setup

Symptom: Brocade Network Advisor server entries are not getting deregistered in SNMP and Syslog table on

device when devices are deleted

Condition: Issue occurs only when Preferred IP address is changed to IPV6 from IPV4

Recovery: Manually delete server entries on the device




Reported In Release: Network Advisor12.2.0 Technology Area: L2 ACL

Symptom: User cannot configure Inbound/Outbound L3 ACL Configuration for Virtual Interfaces

Condition: Issue is specific to Virtual Interfaces on Fast Iron products




Reported In Release: Network Advisor12.2.0 Technology Area: L3 ACL (IP)

Symptom: Configuring ACL on a one Virtual Interface gets deployed to all the Virtual Interfaces

Condition: Issue is specific to Virtual Interfaces on Fast Iron products.





Symptom: User cannot configure IP address and subnet for Virtual Interfaces

Condition: Issue occurs only with Fast Iron SX series products





Symptom: Untagged ports from a default VLAN cannot be assigned (or) moved to any other VLANs

Condition: This issue is observed when the user tries to move the untagged interface/port from a default VLAN

to other VLANs





Symptom: User is not allowed to commit all the configured LUNs

Condition: This issue is observed when the user tries to configure multiple LUNs simultaneously.






Symptom: Incorrect Status of Zones and Zone Configuration in the Zoning dialog

Condition: Issue is observed only when creating and activating the zone configuration from the CLI

Recovery: Create and Activate Zone and Zone Configuration from the BNA Zoning dialog


Technical Severity: High Probability: High



Symptom: User is not allowed to view the Network Measures for Virtual Machines

Condition: Issue occurs only when the time range is set more than 1 day




Reported In Release: Network Advisor12.1.1 Technology Area: View Management / Topology

Symptom: L2 Cloud is shown between the links in VLAN Topology

Condition: Issue occurs only when both LLDP and FDP are enabled




Reported In Release: Network Advisor12.1.4 Technology Area: Reports

Symptom: Incorrect time periods are shown to the user in Reports.

Condition: This issue is observed when a weekly report is created on a timely basis using relative time periods

settings



Product: Network Advisor Technology: Partner Integration

Reported In Release: Network Advisor12.0.3 Technology Area: SMI Agent

Symptom: User cannot view all the instances of NPIV CIM_ActiveConnection

Condition: This issue occurs with NPIV connections




Reported In Release: Network Advisor12.0.1 Technology Area: View Management / Topology

Symptom: FCIP Links toggle ON and OFF in topology

Condition: When the Links are configured with I/O running for more than three days the FCIP links toggle.

Recovery: Delete the Fabric and rediscover




Reported In Release: Network Advisor12.1.0 Technology Area: Event Actions

Symptom: Change in unit set for Frequency will have the impact in triggering the Events

Condition: This issue is observed when the user tries to create an Event Action with Frequency bound





Reported In Release: Network Advisor12.0.3 Technology Area: Encryption (SAN)

Symptom: CTC created for one of switch is not displayed in the disk LUN view dialog

Condition: This is a display issue in BNA which will be seen when two fabrics are connected to the same target

node

Defect ID: DEFECT000441413 Technical Severity: High

Summary: Master log does not show slot number for switch error message logs.

Symptom: User does not get slot number details from Master Log.

Feature: Technical Support Function: USABILITY

Reported In Release: Network Advisor12.0.0 Probability: High


Summary: Locale settings cause product configurations to appear without time stamp.

Symptom: User is unable to perform change tracking.

Workaround: Network Advisor server's default system locale should be set to English.

Feature: Change Manager (IP) Function: CONFIGURATION REPOSITORY

Service Request ID: 1164268

Reported In Release: Network Advisor12.0.2 Probability: Medium


Summary: Master log shows the event - 'Overall port status of the connectivity unit has changed' for the Access

gateway switches.

Symptom: Event does not give sufficient information to the user.

Feature: FAULT MANAGEMENT Function: Master Log

Reported In Release: Network Advisor12.0.2 Probability: Low


Summary: C3Discards, Encode Error Out measure values are not collected for VDX devices

Symptom: User does not get data for some of the Network OS measures.

Feature: Performance Management (IP) Function: IP SNMP Monitoring - Collection



Summary: Date format set before upgrade causes product configurations in the Configuration Repository to

appear without a time stamp after upgrade.


Workaround: Network Advisor server's default system locale should be set to English

Feature: Change Manager Function: CONFIGURATION REPOSITORY

Service Request ID: 1164268



Summary: CIMOM server fails to start in LINUX after extending ulimit to 2000.

Symptom: CIMOM server does not start.

Feature: SMI Agent Function: INSTALLER




Summary: After closing and re-opening Network Advisor client, the containers are empty and do not show hosts

or LUNs.

Symptom: User does not get host or LUN information from the contrainers.

Feature: Encryption Function: CONFIGURATION


Defect ID: DEFECT000383940 Technical Severity: Medium

Summary: CPU utilization is about 50% on VDX switches when performing zoning operations with 100 KB

zone configuration.

Symptom: Switch experiences heavy CPU load while performing zoning operations.

Feature: ZONING Function: Online Zoning



Summary: In properties sheet for VDX6730, SFP/port optics data is empty for FC ports.

Symptom: User cannot see the data for SFP/Port optics data for VDX FC ports.

Feature: REPORTS (IP) Function: Wired Devices Report



Summary: Ports are not re-enabled and incorrect error message is shown when moving ports to default switch

Symptom: Port movement summary details doesn't provide enough information to the user

Feature: Virtual Fabrics Function: USABILITY



Summary: In address finder dialog, ‘Interface’ column is showing as ‘Unknown’ for virtual interfaces of VDX

devices

Symptom: User can’t get correct interface detail for VDX virtual interfaces

Feature: Address Finder Function: USABILITY



Summary: Incorrect data is displayed in the 'speed' field for a missing ISL link in connection properties dialog

Symptom: User can’t get the actual speed configured on ports

Feature: DISCOVERY Function: USABILITY



Summary: Decommission operation never completes when any of the discovered CIMOM fails to respond for

decommission request

Symptom: Operation never completes and user unable to proceed with any more decommission request

Feature: Port Decommission Function: F-port commission




Summary: Configuration backup is triggered for IPV6 enabled Logical Chassis even when credetials for the

switch in Network Advisor are incorrect after a password change.

Symptom: User is allowed to trigger backup with incorrect credentials.




Summary: Network Advisor Tehcnical Support data is not collected when a Linux SSH server is used as external

SCP server.

Symptom: Technical support data for Network Advisor is not collected.

Feature: Technical Support Function: Support Save



Summary: ‘Destination Fabrics’ column is shown empty when a LSAN Zone with online members present in the

Alias is activated

Symptom: User cannot see data in the 'Destination Fabrics' column in Zoning dialog.

Feature: ZONING Function: LSAN Zoning Activation Dialog



Summary: % Utilization for a port is fluctuating between 0 and 100 in Real time graph

Symptom: User is not shown proper real time graph for a port

Feature: Performance Management Function: RealTime Graph



Summary: HIFC settings fail for logical fabrics with GE links in in cascaded FICON configuration.

Symptom: User cannot configure HIFC settings.

Feature: FICON Function: Cascaded FICON Configuration



Summary: VE ports are displayed as U-ports in device tree.

Symptom: Correct port type information for VE port is not displayed.




Summary: SAN User manual needs to be updated about the unsupported TPC version in "SSO support for IBM"

section.

Symptom: User manual does not capture information that SSO is not supported with TPC 5.1.1 or higher

versions.

Feature: HELP Function: HELP




Summary: Both Gige and VE Links are shown in the Topology when Gige and VE ports are present in same

Logical chassis.

Symptom: When both shared and gige links are displayed in the topology, it is confusing to the user.

Workaround: Delete and rediscover the Fabric.

Feature: FCIP Function: USABILITY



Summary: Trunk hierarchy is not shown in device tree for a DCX 8510-4 chassis.

Symptom: User does not see the trunk details.

Workaround: Install trunk license to get the ICL trunk details.

Feature: DISCOVERY Function: SAN ISL Discovery



Summary: SIM Ports are displayed as FE ports in Logical Switches dialog

Symptom: User will be misguided by seeing SIM-port type as FE-port in Logical Switches Dialog.

Feature: Virtual Fabrics Function: Partitioning Dialog



Summary: 'Status' in the properties sheet shows 6 PSUs and a MM module for VDX 6740 device

Symptom: Wrong status data is shown for VDX 6740

Feature: DISCOVERY (IP) Function: IP Discovery Service


Closed with Code Change in Brocade Network Advisor 12.2.0

This section lists the defects closed with a code change in Network Advisor 12.2.0 as of 4:00 PM on Feb 13, 2014.



Product: Network Advisor Technology: Application Management

Reported In Release: Network Advisor12.1.2 Technology Area: Licensing

Closed In Release(s): Network Advisor12.2.0(Fixed)

Symptom: User will not be allowed to launch the Fabric Watch dialog and proceed with Fabric Watch

Configurations

Condition: This issue is observed when the user tries to launch the Fabric Watch dialog







Symptom: User is not able to edit all the traps under "RAS Log Events" in the SNMP trap filter of the Trap

forwarding dialog.

Condition: This issue is observed when the user tries to create a Filter containing a Trap with Lower Case






Symptom: User is not allowed to forward Chassis level Traps

Condition: This issue is observed when the user creates a Filter with Chassis Level Traps/MIB's


Technical Severity: High Probability: Low




Symptom: Hexa decimal value is not populated in the Zoning dialog and will have the impact on the sorting

Condition: This issue is observed when the user performs the sorting of FC Address column and moving Node

members to the Zones


Summary: DCFM performance issues.

Symptom: After several system upgrades involving data backups the DCFM application may hang and the user

could experience a decrease in performance

Risk of Fix: Low Probability: Low

Feature: Performance Management Function: USABILITY

Reported In Release: DCFM10.3.2 Service Request ID: 428321

Defect ID: DEFECT000334065 Technical Severity: Low

Summary: Error message is displayed even though Virtual Fabric is successfully disabled

Symptom: VF is successfully disabled, but error message "Failed to disable virtual fabric feature for chassis" gets

displayed

Workaround: Delete the logical switches and then able to disable the VF



Reported In Release: Network Advisor11.1.0


Summary: Software image update for ADX serverIron shows successful but, is actually not, when the ‘Save to

Flash and Reload’ option is selected.

Symptom: User cannot upgrade images on ServerIron ADX if the ‘Save to Flash and Reload’ option is selected.

Workaround: Push the image with the ‘Persistence Properties’ selected as ‘ Don't Save to Flash or Reload’

option


Feature: FIRMWARE MANAGEMENT (IP) Function: USABILITY





zone configuration.


Risk of Fix: Medium Probability: Medium






Risk of Fix: Medium Probability: High




Summary: CLI credentials configured in the user profile is sometimes not used by Network Advisor.

Symptom: Schedule backup fails.

Workaround: use manual config backup

Risk of Fix: High Probability: Low

Feature: Configuration Management (IP) Function: IP - Configuration Wizard

Reported In Release: Network Advisor11.2.1 Service Request ID: 744955




Risk of Fix: High Probability: High





devices


Risk of Fix: High Probability: Medium




Summary: Firmware download for Ironware OS devices failed with built in SCP server

Symptom: User can’t do firmware download on Ironware devices with built in SCP server

Probability: Medium

Feature: FIRMWARE MANAGEMENT (IP) Function: FIRMWARE DOWLOAD




Summary: STP/RSTP deployment fails on Default VLAN for ICX 6610-24.

Symptom: User cannot configure STP/RSTP on default VLAN.

Workaround: STP/RSTP can be enabled on non-default VLANs.

Risk of Fix: Medium Probability: Low

Feature: VLAN Management Function: STP









Summary: Historical data is not collected for the product measures - CPU Utilization, Memory Utilization and

System Uptime

Symptom: User cannot see historical data for CPU Utilization, Memory Utilization and system uptime measures


Feature: Performance Management Function: Data Collection Workers
















Summary: Brocade 7800 is displayed with 'unknown' state icon.

Symptom: User does not see the actual state of the device.

Workaround: Run latest Fabric OS v7.2 on all switches of the fabric.

Risk of Fix: High Probability: Low

Feature: DISCOVERY Function: SAN Switch Discovery











Summary: Network Advisor Tehcnical Support data is not collected when a Linux SSH server is used as external

SCP server.













Summary: Master log shows the event - 'Overall portstatus of the connectivity unit has changed' for the Access

gateway switches.






Summary: Warning icon is shown in the active zone configuration tab of Zoning dialog for FOS Edge after

activating the LSAN Zones with common names from all the Edge fabrics

Symptom: User will not be able to figure out why the warning message is shown in the active zone configuration

tab of Zoning dialog for FOS Edge fabric.


Feature: ZONING Function: Zoning Dialog



Summary: VM Alarms Widget does not honour global time scope in Dashboard.

Symptom: User cannot change time scope for VM Alarms widget.


Feature: VM Monitoring Function: Dashboard Client






Risk of Fix: Low Probability: High




Summary: Incorrect Port Utilization % is shown for 40G ports in Dashboard widget

Symptom: Wrong data is shown for 40G ports in Port Utilization widget


Feature: Dashboard Function: Client




Alias is activated






Summary: Firmware download fails on NI CES using SCP

Symptom: User is not able to proceed with firmware download for NI CES through SCP





Summary: Tests are skipped on changing the link traffic test configurations for F-port connection for Diagnostics

Port Test.

Symptom: D-port diagnostics results are not available to the user.


Feature: Trouble Shooting & Diagnostics Function: USABILITY



Summary: FEC value gets duplicated while running Diagnostics port test.

Symptom: Additional FEC values displayed are confusing to the user.

































section.


versions.

Risk of Fix: Low Probability: Medium





Logical chassis.





















Summary: SMI-A: EnumerateInstance and EnumerateInstanceNames instances counts do not match for

Brocade_NodeFCPort Class.

Symptom: User does not see exact NodeFCPort instances from EnumerateInstance and EnumerateInstanceNames

opearations.


Feature: SMI Agent Function: FC HBA



Summary: 'DEFAULT_QOS_WARN_MSG' message is not displayed when attempting to download firmware

to Fabric OS switches when Adaptive Networking License is not present on the switch.

Symptom: User does not see DEFAULT_QOS_WARN_MSG message when attempting to download firmware.

Workaround: NA


Feature: FIRMWARE MANAGEMENT Function: FIRMWARE DOWLOAD










or LUNs.


Risk of Fix: Low Probability: Medium






Risk of Fix: High Probability: High





Summary: VLAN deployment dialog does not launch for FastIron WS648.

Symptom: User cannot configure VLANs on FastIron WS648.


Feature: VLAN Manager (IP) Function: USABILITY



Summary: Unable to select zone DB from drop down menu in Compare/Merge dialog

Symptom: Cannot select Zone DBs when trying to perform zone merge


Feature: ZONING Function: USABILITY



Summary: MLX discovery fails with PSQL exception.

Symptom: User is unable to discover the MLX router.


Feature: MPLS Manager Function: ENHANCEMENT



Summary: Tagged MCT ports are shown as untagged ports for NetIron devices running firmware less than v5.4.

Symptom: Incorrect tag mode is shown to the user.


Feature: VLAN Management Function: VLAN Manager



Summary: On a 64-bit VM, user cannot restore a backup created by the same version of Network Advisor

running on a 32-bit VM.

Symptom: Client loses connection to the server frequently.


Feature: Backup and Restore Function: Backup and Restore


Closed without Code Change in Brocade Network Advisor 12.2.0

This section lists the defects closed without a code change in Network Advisor 12.2.0 as of 4:00 PM on Feb 13, 2014.




Reason Code: Low User Impact Probability: High








Reason Code: Low User Impact Probability: Medium




Summary: Master log shows the event - 'Overall portstatus of the connectivity unit has changed' for the Access

gateway switches.


Reason Code: Low User Impact Probability: Low






Reason Code: Code Freeze Probability: High



















or LUNs.







Summary: STP/RSTP deployment fails on Default VLAN for ICX 6610-24.

Symptom: User cannot configure STP/RSTP on default VLAN.

Workaround: STP/RSTP can be enabled on non-default VLANs.

Reason Code: Not Reproducible Probability: Low

Feature: VLAN Management Function: STP



Summary: VM Alarms Widget does not honour global time scope in Dashboard.

Symptom: User cannot change time scope for VM Alarms widget.

Reason Code: Fixed Probability: Medium

Feature: VM Monitoring Function: Dashboard Client



Summary: Incorrect Port Utilization % is shown for 40G ports in Dashboard widget

Symptom: Wrong data is shown for 40G ports in Port Utilization widget

Reason Code: Fixed in Other Defect Probability: High

Feature: Dashboard Function: Client



Summary: Firmware download fails on NI CES using SCP

Symptom: User is not able to proceed with firmware download for NI CES through SCP

Reason Code: Fixed Probability: High




Summary: Tests are skipped on changing the link traffic test configurations for F-port connection for

Diagnostics Port Test.

Symptom: D-port diagnostics results are not available to the user.





Summary: Unable to select zone DB from drop down menu in Compare/Merge dialog

Symptom: Cannot select Zone DBs when trying to perform zone merge


Feature: ZONING Function: USABILITY



Summary: On a 64-bit VM, user cannot restore a backup created by the same version of Network Advisor

running on a 32-bit VM.

Symptom: Client loses connection to the server frequently.


Feature: Backup and Restore Function: Backup and Restore





zone configuration.



















devices


Reason Code: Code Freeze Probability: Medium

























Summary: Network Advisor Tehcnical Support data is not collected when a Linux SSH server is used as

external SCP server.







Alias is activated








Reason Code: Code Freeze Probability: Low












Reason Code: Low User Impact Probability: Low






section.


versions.






Logical chassis.



Reason Code: Workaround Available Probability: Medium























Summary: DCFM performance issues.

Symptom: After several system upgrades involving data backups the DCFM application may hang and the user

could experience a decrease in performance

Reason Code: Already Fixed in Release Probability: Low

Feature: Performance Management Function: USABILITY

Reported In Release: DCFM10.3.2 Service Request ID: 428321



Summary: Software image update for ADX serverIron shows successful but, is actually not, when the ‘Save to

Flash and Reload’ option is selected.

Symptom: User cannot upgrade images on ServerIron ADX if the ‘Save to Flash and Reload’ option is selected.

Workaround: Push the image with the ‘Persistence Properties’ selected as ‘ Don't Save to Flash or Reload’

option

Reason Code: Insufficient Info Probability: Low

Feature: FIRMWARE MANAGEMENT (IP) Function: USABILITY



Summary: CLI credentials configured in the user profile is sometimes not used by Network Advisor.

Symptom: Schedule backup fails.

Workaround: use manual config backup

Reason Code: Design Limitation Probability: Low

Feature: Configuration Management (IP) Function: IP - Configuration Wizard



Summary: Firmware download for Ironware OS devices failed with built in SCP server

Symptom: User can’t do firmware download on Ironware devices with built in SCP server

Reason Code: Fixed in Other Defect Probability: Medium




Summary: Historical data is not collected for the product measures - CPU Utilization, Memory Utilization and

System Uptime

Symptom: User cannot see historical data for CPU Utilization, Memory Utilization and system uptime measures

Reason Code: Already Fixed in Release Probability: Low

Feature: Performance Management Function: Data Collection Workers



Summary: Brocade 7800 is displayed with 'unknown' state icon.

Symptom: User does not see the actual state of the device.

Workaround: Run latest Fabric OS v7.2 on all switches of the fabric.

Reason Code: Fixed in Other Defect Probability: Low

Feature: DISCOVERY Function: SAN Switch Discovery



Summary: Warning icon is shown in the active zone configuration tab of Zoning dialog for FOS Edge after

activating the LSAN Zones with common names from all the Edge fabrics

Symptom: User will not be able to figure out why the warning message is shown in the active zone configuration

tab of Zoning dialog for FOS Edge fabric.

Reason Code: Fixed Probability: Low

Feature: ZONING Function: Zoning Dialog




Summary: FEC value gets duplicated while running Diagnostics port test.

Symptom: Additional FEC values displayed are confusing to the user.





Summary: SMI-A: EnumerateInstance and EnumerateInstanceNames instances counts do not match for

Brocade_NodeFCPort Class.

Symptom: User does not see exact NodeFCPort instances from EnumerateInstance and

EnumerateInstanceNames opearations.


Feature: SMI Agent Function: FC HBA



Summary: 'DEFAULT_QOS_WARN_MSG' message is not displayed when attempting to download firmware

to Fabric OS switches when Adaptive Networking License is not present on the switch.

Symptom: User does not see DEFAULT_QOS_WARN_MSG message when attempting to download firmware.

Workaround: NA


Feature: FIRMWARE MANAGEMENT Function: FIRMWARE DOWLOAD



Summary: VLAN deployment dialog does not launch for FastIron WS648.

Symptom: User cannot configure VLANs on FastIron WS648.


Feature: VLAN Manager (IP) Function: USABILITY



Summary: MLX discovery fails with PSQL exception.

Symptom: User is unable to discover the MLX router.


Feature: MPLS Manager Function: ENHANCEMENT



Summary: Tagged MCT ports are shown as untagged ports for NetIron devices running firmware less than v5.4.

Symptom: Incorrect tag mode is shown to the user.


Feature: VLAN Management Function: VLAN Manager



Defect ID: DEFECT000334065 Technical Severity: Low

Summary: Error message is displayed even though Virtual Fabric is successfully disabled

Symptom: VF is successfully disabled, but error message "Failed to disable virtual fabric feature for chassis"

gets displayed

Workaround: Delete the logical switches and then able to disable the VF

Reason Code: Will Not Fix Probability: Low



brocade network advisor 12.2 - · pdf fileswitch type san devices – b-series brocade...

Documents