Brocade Fabric OS v7.0.2e Release Notes v1.0 May 29, 2014 Document History Document Title Summary of Changes Publication Date Brocade Fabric OS v7.0.2e Release Notes v1.
© 2014 Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Contents Overview ...................................................................................................................................................... 5 Resolution of Important Defects ............................................................................................................................. 5 Features ...................................................................................................................................................................
ICLs on DCX/DCX-4S ............................................................................................................................................. 31 Native Connectivity (M-EOS interoperability)........................................................................................................ 31 Port Mirroring ......................................................................................................................................................... 31 Port Statistics ........
Overview Fabric OS (FOS) v7.0.2e is a patch release based on FOS v7.0.2d. All hardware platforms and features supported in FOS v7.0.2d are also supported in FOS v7.0.2e. In addition FOS v7.0.2e includes support for all of the features supported in FOS v7.0.1. Resolution of Important Defects • DEFECT000454312 With FX8-18, FR4-18i blades, CP may panic while taking over active CP role, resulting in cold recovery. • DEFECT000471333 Switch goes into a rolling reboot.
Features FOS v7.0.2 is a maintenance release that contains fixes for defects including those from FOS v7.0.1a and FOS v7.0.1b patch releases. In addition this release includes the following features and enhancements implemented in FOS v7.0.2: • D_Port Enhancements o • D_Port link saturation capability – ability to drive test traffic to saturate link utilization close to line rate as part of D_Port test Ability to assign individual ports of an optical ICL to logical switches o Prior to FOS v7.0.
FOS v7.0.1 Feature Descriptions New Hardware Support • Brocade 6505 entry level 16G FC switch • FC8-32E and FC8-48E Condor3 based 8G blades for DCX 8510-8 and DCX 8510-4 Enhanced Optical ICL Topology Support for DCX 8510 FOS v7.0.
both the adapter and the switch. For additional information please consult the Brocade Adapter Release Notes for firmware version 3.1 or later, and the Brocade Adapter Administrator’s Guide. Fabric OS v7.0.2e Release Notes v1.
Optionally Licensed Software Fabric OS v7.0.2 includes all basic switch and fabric support software, as well as optionally licensed software that is enabled via license keys. Optionally licensed features supported in FOS v7.0.2 include: Brocade Ports on Demand—Allows customers to instantly scale the fabric by provisioning additional ports via license key upgrade. (Applies to select models of switches).
can be installed to enable full encryption processing power on the BES or on all FS8-18 blades installed in a DCX/DCX-4S/DCX 8510-8/DCX 8510-4 chassis. DataFort Compatibility — This license is required on the Brocade Encryption Switch or DCX/DCX-4S/DCX 85108/DCX 8510-4 with FS8-18 blade(s) to read and decrypt NetApp DataFort-encrypted disk and tape LUNs.
Note that this license requirement does not depend upon the total number of DCX 8510 chassis that exist in a fabric, but only on how many chassis are interconnected via ICLs. This license is only recognized/displayed when operating with FOS v7.0.1 and later. Temporary License Support The following licenses are available in FOS v7.0.
• • • • • • • IEEE 802.3ad IEEE 802.3ae IEEE 802.1Q IEEE 802.1p IEEE 802.1v IEEE 802.1AB IEEE 802.3x Link Aggregation with LACP 10G Ethernet VLAN Tagging Class of Service Prioritization and Tagging VLAN Classification by Protocol and Port Link Layer Discovery Protocol (LLDP) Flow Control (Pause Frames) The following draft versions of the Converged Enhanced Ethernet (CEE) and Fibre Channel over Ethernet (FCoE) Standards are also supported on the Brocade 8000 and FCOE10-24 blade: • • • IEEE 802.
• Brocade 7800 — On the pull-out tab on the front left side of the chassis underneath the serial console and Ethernet connection and on the bottom of the switch in a well on the left side underneath (looking from front) • Brocade 8000 — On the switch ID pullout tab located inside the chassis on the port side on the left and also on the bottom of the chassis • Brocade DCX, DCX 8510-8 — Bottom right of the port side • Brocade DCX-4S, DCX 8510-4 — Back, upper left under the power supply 3.
FOS Migration Considerations This section contains important details to consider before migrating to or from this FOS release. Recommended Migration Paths to FOS v7.0.2e Migrating from FOS v7.0 Any 8G or 16G platforms running any FOS v7.0.0x release can be non-disruptively upgraded to FOS v7.0.2e. Migrating from FOS v6.4.x DCX/DCX-4S units running any FOS v6.4.x release can be non-disruptively upgraded to FOS v7.0.2e.
Important Notes This section contains information that you should consider before you use this Fabric OS release. Brocade Network Advisor Compatibility Brocade® Network Advisor provides the industry’s first unified network management solution for data, storage, and converged networks.
WebTools Compatibility FOS v7.0.2e is qualified and supported with Oracle JRE 1.7.0 update 25, update 45, update 51, and update 55. Launching WebTools with Oracle JRE 1.7.0 update 51 and update 55 through Brocade Network Advisor is only supported on version 12.1.5 or later. With JRE 1.7.0 update 51 to update 55, users could see some browser warning messages that can be ignored. WebTools is supported with Google Chrome browser with FOS v7.0.2e.
Supported Products and FOS Interoperability Brocade 5410, 5480, 5424, 5450, 5460, 5470, NC-5480 v6.2.0 or later6 Brocade DCX, 300, 5100, 5300 v6.1.0e and later 2 6 VA-40FC v6.2.1_vfc 6, v6.2.2 or later 6 Brocade DCX-4S v6.2.0 or later 6 Brocade DCX with FS8-18 blade(s), Brocade Encryption Switch v6.1.1_enc or later 6 Brocade 7800, DCX and DCX-4S with FCOE10-24 or FX8-24 blades V6.3.0 or later Brocade 8000 V6.1.2_CEE1 or later Brocade DCX/DCX-4S with FA4-18 blade(s) DCX requires v6.0.
6 If operating with FOS v6.2.2e or earlier, Adaptive Networking QoS must be disabled when connecting to 16G FC platform. Otherwise, ISL will segment. 7 Connectivity to FC SAN is established via VDX6730 connected to FCR running FOS v7.0.1 or later. FCR platforms supported include 5100, VA-40FC, 5300, 7800, DCX, DCX-4S, DCX 8510-8, DCX 8510-4, 6510.
Next Generation Distance Extension Blade (FX8-24) Up to a max of 4 blades of this type. Note: FR4-18i cannot coexist with FX8-24 in FOS v7.0 or later FCoE/L2 CEE blade FCOE10-24 Up to a max of 4 blades of this type. Not supported in the same chassis with other intelligent blades or the FC8-64 port blade. FC16-32, FC16-48 Not supported Table 1 Blade Support Matrix for DCX and DCX-4S with FOS v7.0.2 Note: The iSCSI FC4-16IP blade is not qualified for the DCX/DCX-4S. Fabric OS v7.0.2e Release Notes v1.
Fabric OS v7.0.2 software is fully qualified and supports the blades for the DCX 8510-8 and DCX 8510-4 noted in the table below. DCX 8510-8/DCX 8510-4 Blade Support Matrix FC16-32, FC16-48 16G FC blades Supported starting with FOS v7.0 FC8-64 64 port 8Gbit port blade With any mix and up to 8/4 of each. No restrictions around intermix. Note: FC8-16, FC8-32, FC8-48 blades are not supported on DCX 8510 platforms FC8-32E, FC8-48E Condor3 based 8G blades Supported starting with FOS v7.0.
Power Supply Requirements for Blades in DCX/DCX-4S Blades Type of Blade FC10-6, FC816, FC8-32, FC 8-48, FC864 Port Blade FR4-18i FS8-18, FX8-24, FCOE10-24 DCX/DCX-4S DCX/DCX-4S @110 VAC (Redundant configurations) @200-240 VAC (Redundant configurations) 2 Power Supplies 2 Power Supplies Intelligent Blade Not Supported 2 Power Supplies Intelligent Blade Not Supported DCX: 2 or 4 Power Supplies Comments • DCX-4S: 2 Power Supplies Distribute the Power Supplies evenly to 2 different AC conne
Typical Power Supply Requirements Guidelines for Blades in DCX 8510-8 (For specific calculation of power draw with different blade combinations, please refer to Appendix A: Power Specifications in the 8510-8 Backbone Hardware Reference Manual) Configured Number of Ports2 Blades Type of Blade DCX 8510-8 @110 VAC (Redundant configurations) DCX 8510-8 @200-240 VAC (Redundant configurations) Comments Any combination of 8Gb or 16Gb ports FC8-64, FC16-32, FC8-32E Port Blade 4 Power Supplies 2 Power Sup
Typical Power Supply Requirements Guidelines for Blades in DCX 8510-8 (For specific calculation of power draw with different blade combinations, please refer to Appendix A: Power Specifications in the 8510-8 Backbone Hardware Reference Manual) Configured Number of Ports2 336 8Gb ports Blades FC8-48E Type of Blade DCX 8510-8 @110 VAC (Redundant configurations) DCX 8510-8 @200-240 VAC (Redundant configurations) Comments Port Blade 4 Power Supplies 2 Power Supplies 200-240VAC: 1+1 Power Supplies 110
Typical Power Supply Requirements Guidelines for Blades in DCX 8510-4 (For specific calculation of power draw with different blade combinations, please refer to Appendix A: Power Specifications in the 8510-4 Backbone Hardware Reference Manual) Configured Blades Number of Ports1 Type of Blade DCX 8510-4 @110 VAC (Redundant configurations) DCX 8510-4 @200-240 VAC (Redundant configurations) Comments 96 ports max FC16-32, FC8-32E Port Blade 2 Power Supplies 2 Power Supplies 1+1 redundancy with 110 o
o Go to Documentation > Tech Notes. o Look for the Tech Note on Access Gateway Device-Based Mapping in VMware ESX Server. Brocade HBA/Adapter Compatibility • Brocade HBA/Adapter should be using driver version 2.3.0.2 or later when attached to 16G ports on Brocade switches. D-Port • FOS v7.0.0a and later support the execution of D-Port tests concurrently on up to eight ports on the switch. • Support of D-Port is extended to R_RDY flow control mode.
• Adding of 3PAR Session/Enclosure LUNs to CTCs is now supported. Session/Enclosure LUNs (LUN 0xFE) used by 3PAR InServ arrays must be added to CryptoTarget (CTC) containers with LUN state set to “cleartext”, encryption policy set to “cleartext”. BES/FS8-18 will not perform any explicit enforcement of this requirement.
• When disk and tape CTCs are hosted on the same encryption engine, re-keying cannot be done while tape backup or restore operations are running. Re-keying operations must be scheduled at a time that does not conflict with normal tape I/O operations. The LUNs should not be configured with auto rekey option when single EE has disk and tape CTCs.
o VE as XISL o 10GigE lossless failover o Modified QoS percentages o 10GigE ARL o IP Configuration where multiple GigEs have same subnet values o For a tunnel configuration on 1GE ports that has more than 4 circuits o Teradata emulation enabled o Circuits configured explicitly to be listeners or an initiators FCoE/DCB/CEE (Brocade 8000 and FCOE10-24) • When upgrading a Brocade 8000 or DCX/DCX-4S with one or more FCOE10-24 blades from FOS v6.x to FOS v7.0.
priority-group-table 1 weight 40 pfc priority-group-table 2 weight 60 priority-table 2 2 2 1 2 2 2 2 • When upgrading from FOS v6.3.x or v6.4.x to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, the CEE start up configuration dcf.conf file will be incompatible with the FCoE provisioning changes implemented in v6.4.1_fcoe and later releases. Users can save the dcf.
• When a FCOE10-24 blade is powered off during configuration replay, the interface specific configuration won’t get applied. Later when FCOE10-24 blade is powered on, all physical interfaces will come up with default configurations. User can execute “copy startup-config running-config” command to apply the new configuration after powering on the FCOE10-24 blade. • When IGMP Snooping is disabled on a VLAN, all configured IGMP groups are removed from that VLAN.
• A maximum of 112 ports may be used for connectivity to loop devices in a single Logical Switch within a chassis in 10-bit dynamic area mode on DCX. • Loop devices continue to be supported when attached to ports on the FC8-16, FC8-32 with no new restrictions. ICLs on DCX/DCX-4S • If a DCX with an 8-link ICL license is connected to a DCX with a 16-link license, the DCX with the 16link license will report enc_out errors. The errors are harmless, but will continue to increment.
switch. Extra caution should be used to verify the FIDs match for all switches in the same Logical Fabric. • A switch with Virtual Fabrics enabled may not participate in a fabric that is using Password Database distribution or Administrative Domains. The Virtual Fabrics feature must be disabled prior to deploying in a fabric using these features. Zoning • The maximum zone database size supported in FOS v7.
• HA failover on DCX/DCX-4S/DCX 8510 platforms while running FOS v7.0 or later firmware • Firmware upgrade from v7.0 to a later release on Brocade 300, 5100, VA-40FC, 5300, 6510 • Firmware upgrade from v7.0.1 to a later release on Brocade 6505 • The QSFP information in the sfpshow output will indicate the ID field as all zeros. This is as designed.
Defects Closed with Code Change in Fabric OS v7.0.2e This section lists the defects with Critical, High, and Medium Technical Severity closed with a code change as of May 29, 2014 in FOS v7.0.2e. Defect ID: DEFECT000361971 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: F-Port was logged out of switch due to laser fault during media access.
Defect ID: DEFECT000430239 Technical Severity: High Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.0.0 Technology Area: FCIP Symptom: FCIP tunnel bounces due to DRAM2 memory allocation failures or BLS-5024 event. Condition: Memory allocation failures lead to VE ports down with circuits InProg. Recovery: FX8-24 requires reset to recover. Defect ID: DEFECT000431101 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.
Defect ID: DEFECT000440137 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.0 Technology Area: BB Credits Symptom: "CRC with good EOF errors" observed and may cause buffer credit loss. Condition: This may occur on DCX-4S with FC8-16 port blades installed in slot 1, 2 Recovery: Manual tuning or auto tuning. Defect ID: DEFECT000453711 Technical Severity: Medium Probability: Medium Product: FOS Technology: Security Reported In Release: FOS7.1.
Defect ID: DEFECT000454580 Technical Severity: Medium Probability: Low Product: FOS Technology: Security Reported In Release: FOS6.4.2 Technology Area: Fabric Authentication Symptom: On director, with SSL configured on Active CP, a newly inserted Standby CP may panic. On switch, hot code load may result in cold recovery due to CP Panic if Time Server becomes unreachable during hareboot. Condition: On Directors, a new/replacement standby CP may panic upon insertion. This may happen if: 1.
Defect ID: DEFECT000459102 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: FC-FC routing Symptom: Domain change caused proxy devices to be stuck in "initializing" state. Condition: If a domain ID was previously changed, proxy devices could get stuck in "initializing" state after adding a new switch to an edge fabric. Recovery: Deleting and re-adding an LSAN zone will permit the devices to recover.
Defect ID: DEFECT000469915 Technical Severity: High Probability: Low Product: FOS Technology: Management Reported In Release: FOS6.4.2 Technology Area: Platform Services Symptom: CLI nscamshow reported "state is unknown" for Port IDs of remote switches, and impacted devices cannot communicate with each other. Condition: This may occur in a setup with Long distance E port due to a rare name server query frame time out condition. Recovery: hafailover to recover.
Defect ID: DEFECT000473087 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: FC-FC routing Symptom: Customer could see different symptoms, such as: 1. RTWR error due to frame drop on 16G FCR 2. Fabric domains are inconsistent between fabric module and routing module, which cause Fport cannot come online. Condition: If non-trunked EX-port is configured, when remote side of the EX-port goes down (i.
Defect ID: DEFECT000476762 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools Symptom: User sees unwanted warning messages while launching Web Tool or Network Advisor. Condition: When a server uses a later revision of JAVA update JRE1.7u45 and JRE1.7u51. Workaround: Launch Web Tools through Network Advisor running version 12.1.4 or higher.
Defect ID: DEFECT000480765 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools Symptom: “Application Blocked by Security Settings” is displayed and fails to launch EZ Manager Condition: This issue will be seen only with older JRE updates (40 and below). Workaround: Use latest JRE Defect ID: DEFECT000481199 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.
Defect ID: DEFECT000489829 Technical Severity: Medium Product: FOS Reported In Release: FOS7.1.0 Probability: Low Technology: Monitoring/RAS Technology Area: End-to-end Performance Monitoring Symptom: RX /Tx performance values higher than 100% on a couple of ports. Condition: These may be seen only when link goes down and comes back up. Defect ID: DEFECT000490754 Technical Severity: High Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.
Defect ID: DEFECT000505359 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.0 Technology Area: CLI Symptom: Switch panics intermittently after Supportsave command is started. Condition: This may occur when supportsave is issued with 4G blades in switch. Recovery: Switch recovers on its own. Closed with Code Change in Fabric OS v7.0.
Defect ID: DEFECT000423389 Technical Severity: High Summary: Switch panic while running suppotsave with 4G blades. Symptom: When RTE portion of supportsave is run on a 4G blade, it may trigger a switch panic. Probability: Low Feature: FOS Software Function: Panic / OOM FOS7.0.0 Reported In Release: Service Request ID: 1094952 Defect ID: DEFECT000429695 Technical Severity: High Summary: Name Server loses FC4 type in routed environment.
Defect ID: DEFECT000436921 Technical Severity: High Summary: Console print hung and caused other process to unable to complete Symptom: In general customer observes switch panic, unable to access switch. Workaround: Check console port and make sure the settings are correct Probability: Low Feature: FOS Function: KERNEL Reported In Release: FOS6.3.
Summary: 7800 Tunnel in DwnPend state after making change to committed rate Symptom: 7800 Tunnel enters DwnPend state after configuration change is made. An IPC error is reported during subsequent attempts to delete the tunnel. Probability: Medium Feature: FOS Software Function: FCIP Reported In Release: FOS7.0.1 Service Request ID: 1147343 Defect ID: DEFECT000446429 Technical Severity: High Summary: ASIC entries are not being cleared upon HA processing leading to server issues.
Summary: Blade fault unnecessarily on rare parity errors. Symptom: Customer experienced frequent blade fault upon detecting transient self-correctable ASIC errors Feature: FOS Software Function: ASIC Driver Reported In Release: FOS7.1.
Defect ID: DEFECT000441913 Technical Severity: High Summary: A 16Gbit switch may panic when an ICL port enters soft fault state. This is very unlikely but may also occur with Backend Internal or Backend External port. Symptom: During switch install, slot power cycle test, observed 16G switch panic. Probability: Medium Feature: 16G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.0.2 Service Request ID: 1032557 Closed with Code Change in Fabric OS v7.0.
Defect ID: DEFECT000410236 Technical Severity: Medium Summary: EE monitors in VF environment with duplicate PID/SID on same ASIC do not function Symptom: Create a logical switch and install EE monitors on the ports (same asic) of both default and logical switch having same sid/pid, then run traffic and the EE monitor counters do not increament as expected. Probability: Low Feature: FOS Software Function: Virtual Fabric Reported In Release: FOS6.3.
Defect ID: DEFECT000420051 Technical Severity: Medium Summary: On DCX with FC8-48 in slot 3, CRC with good eof errors are seen. Symptom: CRC with good EOF onbserved on DCX with FC8-48 in slot 3 on ports 3/42 <-> 8/139 Probability: Medium Feature: FOS Software Function: System Performance Reported In Release: FOS6.4.3 Service Request ID: 1035482 Defect ID: DEFECT000421461 Technical Severity: Medium Summary: On DCX-4S, backend CRC errors detected on core blade port 3/56 connecting FC8-32 port blade.
Defect ID: DEFECT000423054 Technical Severity: High Summary: Specifying 32 character usernames in snmpconfig causes unexpected termination of snmpd and rolling reboot Symptom: Termination of snmpd occurs, message [KSWD-1002] is displayed. Workaround: Specify usernames less than 15 characters in length. Probability: High Feature: FOS Software Function: SNMP Reported In Release: FOS6.3.
Defect ID: DEFECT000430083 Technical Severity: Medium Summary: Unable to delete user account in VF environment created using AD settings Symptom: After modifying a user account with "userconfig --addad lsadmin -a 1-128" command, deleting the user account fails with the following error message: “Cannot manage the target account due to conflicting LF permissions” Probability: Medium Feature: FOS Software Function: Fabric Services Reported In Release: FOS7.0.
