Brocade Fabric OS v7.2.0a
Release Notes v1.0
September 9, 2013
Document History
Document Title |
Summary of Changes |
Publication Date |
|
|
|
Brocade Fabric OS v7.2.0a Release Notes v1.0 |
Initial Release |
September 9, 2013 |
|
|
|
Fabric OS v7.2.0a Release Notes v1.0 |
Page 1 of 93 |
© 2013 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.
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.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 2 of 93 |
Contents |
|
Overview ...................................................................................................................................................... |
5 |
New Hardware Support ........................................................................................................................................... |
5 |
Summary of New Software Features ...................................................................................................................... |
5 |
New Feature Descriptions .......................................................................................................................... |
6 |
MAPS (Monitoring and Alerting Policy Suite).......................................................................................................... |
6 |
Flow Vision ............................................................................................................................................................... |
8 |
FCR Enhancements ................................................................................................................................................. |
9 |
FCIP Enhancements ................................................................................................................................................ |
9 |
ClearLink Diagnostics: D_Port Enhancements .................................................................................................... |
10 |
Access Gateway Enhancements ........................................................................................................................... |
10 |
Encryption Platform (BES/FS8-18) Enhancements ............................................................................................. |
10 |
FICON Enhancements ........................................................................................................................................... |
10 |
Miscellaneous Enhancements.............................................................................................................................. |
10 |
Optionally Licensed Software.................................................................................................................. |
12 |
Temporary License Support .................................................................................................................... |
15 |
Supported Switches.................................................................................................................................. |
16 |
Standards Compliance ............................................................................................................................. |
16 |
Technical Support ..................................................................................................................................... |
16 |
FOS Migration Considerations ................................................................................................................ |
18 |
FOS Upgrade and Downgrade Special Considerations........................................................................................ |
18 |
Recommended Migration Paths to FOS v7.2.0a ................................................................................................. |
18 |
Important Notes......................................................................................................................................... |
19 |
Brocade Network Advisor Compatibility ............................................................................................................... |
19 |
WebTools Compatibility ......................................................................................................................................... |
19 |
SMI Compatibility ................................................................................................................................................... |
20 |
Fabric OS Compatibility ......................................................................................................................................... |
20 |
SNMP Support ....................................................................................................................................................... |
22 |
Blade Support............................................................................................................................................ |
23 |
Scalability................................................................................................................................................... |
28 |
Other Important Notes and Recommendations ..................................................................................... |
28 |
Adaptive Networking/Flow-Based QoS Prioritization ........................................................................................... |
28 |
Access Gateway ..................................................................................................................................................... |
29 |
Brocade HBA/Adapter Compatibility .................................................................................................................... |
29 |
D_Port..................................................................................................................................................................... |
29 |
Edge Hold Time ...................................................................................................................................................... |
29 |
Encryption Behavior for the Brocade Encryption Switch (BES) and FS8-18 ...................................................... |
30 |
FCIP (Brocade 7800 and FX8-24)......................................................................................................................... |
31 |
FCoE/DCB/CEE (FCOE10-24) ............................................................................................................................... |
32 |
Fabric OS v7.2.0a Release Notes v1.0 |
Page 3 of 93 |
FCR and Integrated Routing .................................................................................................................................. |
33 |
Forward Error Correction (FEC) ............................................................................................................................. |
33 |
FICON...................................................................................................................................................................... |
33 |
FL_Port (Loop) Support.......................................................................................................................................... |
34 |
ICLs on DCX/DCX-4S ............................................................................................................................................. |
34 |
Native Connectivity (M-EOS interoperability)........................................................................................................ |
34 |
Port Initialization .................................................................................................................................................... |
34 |
Port Mirroring ......................................................................................................................................................... |
34 |
Port Statistics......................................................................................................................................................... |
34 |
Virtual Fabrics ........................................................................................................................................................ |
35 |
WebTools................................................................................................................................................................ |
35 |
Zoning..................................................................................................................................................................... |
35 |
Miscellaneous ........................................................................................................................................................ |
35 |
Defects ....................................................................................................................................................... |
37 |
Open Defects in Fabric OS v7.2.0a ...................................................................................................................... |
37 |
Open Defects in Fabric OS v7.2.0......................................................................................................................... |
39 |
Closed with Code Change in Fabric OS v7.2.0a................................................................................................... |
54 |
Closed with Code Change in Fabric OS v7.2.0..................................................................................................... |
58 |
Closed without Code Change in Fabric OS v7.2.0 ............................................................................................... |
88 |
Fabric OS v7.2.0a Release Notes v1.0 |
Page 4 of 93 |
Overview
Fabric OS (FOS) v7.2.0a is a patch release based on FOS v7.2.0. All hardware platforms and features supported in FOS v7.2.0 are also supported in FOS v7.2.0a.
New Hardware Support
FOS v7.2 does not introduce support for any new hardware platform, while it adds support for the existing embedded switches 5431, 6547 and M6505 on a major FOS release.
Summary of New Software Features
FOS v7.2 includes support for several new software features and enhancements:
MAPS (Monitoring and Alerting Policy Suite)
Flow Vision
FCR enhancements
FCIP enhancements
D_Port enhancements
Access Gateway enhancements
Encryption platform (BES/FS8-18) enhancements
FICON enhancements
Miscellaneous enhancements
Fabric OS v7.2.0a Release Notes v1.0 |
Page 5 of 93 |
New Feature Descriptions
MAPS (Monitoring and Alerting Policy Suite)
FOS v7.2 implements a new easy to use policy based monitoring and alerting suite that proactively monitors the health and performance of the SAN infrastructure to ensure application uptime and availability. Brocade MAPS helps users to uncover potential problems in the SAN fabric quickly, before they cause application performance impacts or costly failures.
MAPS is a key component of Brocade’s Fabric Vision technology that is aimed at dramatically reducing the operational complexity in managing the SAN infrastructure and ensuring application uptime and availability.
Note: Usage of MAPS features requires the Fabric Vision license or both the Fabric Watch and Advanced Performance Monitoring (APM) licenses.
MAPS offers the following capabilities:
Policy Based Monitoring
The policy based monitoring feature of MAPS offers the following capabilities:
Pre-defined monitoring groups and pre-defined monitoring policies with customization capability
MAPS enables easier monitoring of the switch by providing pre-defined monitoring groups and prevalidated monitoring policies that users can readily enable, while still providing the flexibility to the end users to create their own custom monitoring groups and custom monitoring policies.
A MAPS monitoring policy is a collection of monitoring rules and actions associated with each rule. Users can define multiple monitoring policies but can activate only one monitoring policy at a time on the switch. This, for example, allows users to use a certain monitoring policy in production and a different monitoring policy during maintenance.
MAPS provides pre-defined monitoring groups for monitoring switch ports attached to servers, switch ports attached to storage, E_ports, short wavelength SFPs, long wave length SFPs, etc. MAPS also provides pre-defined monitoring policies such as aggressive, moderate and conservative policies, based on different monitoring thresholds and actions. Users can choose one of these pre-defined policies, modify select rules within any of the pre-defined policies, or create their own custom groups and custom policies for monitoring the switch.
MAPS customization capability allows users to create custom monitoring groups, such as a group of switch ports that are attached to high priority applications, medium priority applications, low priority applications, etc. and monitor these groups using their own unique rules. For example, users may choose to “port-fence” a problematic port connected to a low priority application, while choosing only to notify via RASlog if that port is connected to a high priority application.
With Brocade Network Advisor 12.1 or later, users can apply a given monitoring policy across multiple switches and multiple fabrics instantly, ensuring consistent monitoring across an entire environment.
Flexible monitoring rules
MAPS provides flexible monitoring rules to monitor a given counter for different threshold values and take different actions when each threshold value is crossed. For example, users can monitor a CRC error counter at a switch port and can generate a RASlog when the error rate is more than two per
Fabric OS v7.2.0a Release Notes v1.0 |
Page 6 of 93 |
minute, send an e-mail notification when the error rate is at five per minute, and fence a port when the error rate exceeds ten per minute.
Ability to monitor both sudden failures and gradual degradations
MAPS provides the ability to not only detect abnormal conditions but also gradually deteriorating conditions in the switch. For example, if a CRC error counter at a switch port increments suddenly at the rate of five per minute, MAPS can detect and alert the end users about that condition. Similarly, if the CRC error counter is gradually incrementing at the rate of five per day, even that condition can be detected and reported by MAPS as well, with a different action taken for each condition.
Support for multiple monitoring categories
MAPS supports various monitoring categories such as: Switch status, Port health, FRU (Field Replaceable Unit) health, Security violations, Fabric state changes, Switch resource, Traffic performance and FCIP health.
This essentially enables monitoring of the overall switch status, switch ports, SFPs, port blades, core blades, switch power supplies, fans, temperature sensors, security policy violations such as login failures, fabric reconfigurations, CPU and memory utilization of the switch, traffic performance at port, FCIP circuits health, etc.
Support for multiple alerting mechanisms and actions
MAPS provides various mechanisms to deliver alerts to the end users via RASlogs, SNMP traps and e- mail notifications when the monitoring thresholds are exceeded. MAPS also allows users to perform port fencing action when errors on a given port exceed a certain threshold. MAPS alerting mechanisms/actions are associated with each monitoring rule. However, users are also given the flexibility to enable or disable these alerting mechanisms/actions for the entire switch. This for example, helps users to suppress all alerts during a maintenance window, or when testing and
“tuning” new rules within a policy.
CLI Dashboard
MAPS provides a CLI based dashboard of health and error statistics to provide an at a glance view of the switch status and various conditions that are contributing to the switch status. This enables users to get instant visibility into any hot spots at a switch level and take corrective actions.
The summary section of the dashboard provides the overall status of the switch health and the status of each monitoring category. If there is any category deemed to be out of “normal” status due to violations of rules, the dashboard shows the rules that were triggered for that category.
The dashboard also provides historical information of the switch status for up to seven days. It provides raw counter information of various error counters such as CRC, Class 3 Transmit Timeout Discard, Link Resets, etc. without requiring users to set any monitoring policy. This historical counter information can also be used to assist the user in fine-tuning their MAPS rules by showing where a particular threshold may be just missing catching a particular behavior on the switch.
Note: Brocade Network Advisor 12.1 or later provides a feature rich dashboard that provides fabricwide visibility of hot spots, deeper historical information and much more. Please refer to Brocade Network Advisor 12.1 documentation for additional details.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 7 of 93 |
Bottleneck Detection integration with MAPS dashboard
Bottleneck Detection information is integrated with MAPS dashboard. The “Summary” section of the dashboard shows bottleneck events detected by the Bottleneck Monitor. The “History” section of the dashboard shows entries for bottlenecked ports, including transient bottlenecks that are not detected by the Bottleneck Monitor. This enables users to get at an instant view of the bottlenecked ports in the switch and enables rapid problem resolution.
Proactive Flow Monitoring using MAPS
MAPS can monitor flows created under Flow Vision’s “monitor” sub-feature and generate alerts based on user defined rules. To monitor a flow using MAPS, users must first create and activate the flows using Flow Monitor, and then import those flows into MAPS for monitoring. This enables users to monitor and be alerted on various conditions such as, when bandwidth utilization at a port for a given flow exceeds a certain threshold or falls under a certain threshold, when number of SCSI reservation frames at a LUN exceeds a certain threshold, etc.
Automated Migration of existing Fabric Watch configuration to MAPS
Users who are currently monitoring a switch using Fabric Watch can automatically import all of their Fabric Watch thresholds into a MAPS policy, allowing them to seamlessly migrate from Fabric Watch to MAPS. This allows users to retain monitoring behaviors that have been developed for their unique environment over time, and also take advantage of the powerful new capabilities in MAPS and usability improvements. (Note that the Fabric Watch and MAPS features are mutually exclusive on an individual switch. Only one or the other can be active at one time.)
Flow Vision
Flow Vision is a key component of Brocade’s Fabric Vision technology being introduced in FOS v7.2 that provides comprehensive visibility into application flows in the fabric and the ability to non-disruptively create copies of the application flows that can be captured for deeper analysis. Flow Vision also provides test flow generation capability that can be utilized to pre-test a SAN infrastructure for robustness before deploying applications. The test flow generation capability is also useful for testing the internal connections on a switch to ensure ideal performance before deploying the switch into a production environment.
Flow Vision includes the following key features:
Flow Monitor:
Provides comprehensive visibility into application flows in the fabric, including the ability to learn (discover) flows automatically.
Enables monitoring of application flows (Example: From a Host to a Target/LUN) within a fabric at a given port.
Provides statistics associated with the specified flows to gain insights into application performance. Some of these statistics include:
Transmit frame count, receive frame count, transmit throughput, receive throughput, SCSI Read frame count, SCSI Write frame count, number of SCSI Reads and Writes per second (IOPS), etc.
When NPIV is used on the host, users can monitor VM (Virtual Machine) to LUN level performance as well.
Enables monitoring of various frame types at a switch port to provide deeper insights into storage I/O access pattern at a LUN, reservation conflicts, and I/O errors.
Example: SCSI Read, SCSI Write, SCSI Reserve, ABTS, BA_ACC, etc.
Integrated with MAPS to enable threshold based monitoring and alerting of flows.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 8 of 93 |
Flow Generator:
Flow generator is a test traffic generator for pre-testing the SAN infrastructure (including internal connections) for robustness before deploying the applications.
Allows users to configure a16G FC capable port as a simulated device that can transmit frames at full 16G line rate.
Users can emulate a 16G SAN without actually having any 16G hosts or targets or SANtesters, and pre-test the entire SAN fabric including optics and cables on ISLs, internal connections within a switch, at full line rate.
The traffic generator port must be a 16G FC capable port while the traffic destination port can be an 8G or a16G capable FC port on any switch in the fabric (the test traffic is terminated at the destination port and does not leave the switch).
Flow Mirror:
Provides the ability to non-disruptively create copies of application flows that can be captured for deeper analysis. Only mirroring to the CPU of the switch is supported in FOS v7.2.
Used for in-depth analysis of flows of interest – SCSI Reservation frames, ABTS frames, flows going to a bottlenecked device, frames during link bring up, etc.
Users can select the type of frames to be mirrored.
Supported only on 16G FC capable platforms.
Note:
Flow Vision features require the Fabric Vision license or both Fabric Watch and APM licenses.
FCR Enhancements
FOS v7.2 supports the following FCR enhancements:
EX_Port support on optical ICLs of DCX 8510
Provides the ability to configure EX_Ports on the ICL links of DCX 8510 platforms connected to other DCX 8510 platforms.
Allows users to build very high performance IFLs (Inter Fabric Links) using ICLs – simplifies cabling as well.
Supported only when Virtual Fabrics (VF) is enabled on DCX 8510.
Increased FCR scalability: FOS v7.2 supports up to 6000 devices per edge fabric (an increase from 2000). Refer to the Brocade SAN Scalability Guidelines document for more information.
Routing enhancements to select the lowest cost links in the FCR fabric when there are multiple routes available between FCR edge fabrics through an FCR backbone fabric.
FCIP Enhancements
FOS v7.2 adds support for a new FCIP Tunnel failover configuration option that provides the following capabilities:
Allows a user to define a Failover Group that includes a subset of the circuits in the FCIP Tunnel.
Provides a more deterministic failover configuration that would allow a mixture of metric 0 and metric 1 circuits to be used in the event of a metric 0 circuit failure.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 9 of 93 |
ClearLink Diagnostics: D_Port Enhancements
FOS v7.2 adds the following D_Port enhancements:
Enhancement to D_Port test results
Starting with FOS v7.2 complete results of the D_Port tests will be available on the responder switch as well. Prior to FOS v7.2, D_Port test results on the D_Port responder switch did not include optical and remote loopback test results. Complete results were only available on the D_Port initiator switch.
D_Port support between Brocade 16G HBA and Brocade 16G Access Gateway.
Dynamic D_Port support between Brocade 16G HBA and Brocade 16G switch
With this enhancement users do not need to explicitly configure D_Port on the switch.
A switch port enters D_Port mode upon request from the HBA, D_Port tests then get performed and the switch port reverts back to the normal mode after the D_Port tests are completed.
This enhancement significantly reduces the operational overhead by eliminating several manual configuration steps.
Access Gateway Enhancements
FOS v7.2 supports the following Access Gateway enhancements:
D_Port diagnostics support on the links between Brocade 16G HBA and Brocade 16G Access Gateway to assess SFP and cable health.
Detect and prevent duplicate PWWN at the time of login.
Encryption Platform (BES/FS8-18) Enhancements
FOS v7.2 introduces the following enhancements for the encryption platforms:
KMIP Support for TEKA (Thales e-Security Key Authority)
Thin Provisioning support for IBM XIV and EMC VMAX
FICON Enhancements
FOS v7.2 implements the following FICON enhancements:
Added the ability for the CUP Diagnostics to determine the firmware version of all the switches in the fabric which allows interoperability with FOS v7.1
Implemented a new Command Reject Error Code provided by IBM to help define “Fabric Errors”.
Miscellaneous Enhancements
FOS v7.2 supports several useful enhancements across various feature categories:
FOS v7.2 allows 10G speed configuration on all ports of a 16G FC blade and 16G switch (6510, 6520 only)
Provides more flexibility to the end users to enable 10G capability on any port
Also provides more flexibility to enable encryption/compression on 10G ports.
Pre-FOS v7.2 limited 10G FC support to only the first 8 ports of a 16G switch or a 16G blade. This also limited the ability to enable encryption/compression to only two of those first 8 ports due to restrictions on the number of ports supported per ASIC. By removing this restriction, FOS v7.2 allows users to enable more 10G FC ports for encryption and compression by spreading them across multiple ASICs.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 10 of 93 |
FOS v7.2 allows buffer credit assignment even for “normal distance” (regular) E_ports
The portCfgEportCredits CLI introduced in FOS v7.2 allows users to perform fine grained performance tuning on normal E_ports by allowing users to specify buffer credits.
In FOS v7.2, the portaddess CLI has been enhanced to display an address as user bound when a user has explicitly bound an address to a port.
FOS v7.2 introduces a new CLI “creditrecovmode” to configure backend link credit loss recovery options
Existing credit loss recovery options of the bottleneckmon CLI continue to be supported in FOS v7.2 but will be removed from FOS v7.3.
Simplifies the bottleneckmon CLI.
FOS v7.2 allows users to provide a reason string when disabling a port via portdisable or portcfgpersistentdisable CLIs – helps to track the user intention for disabling a particular port.
FOS v7.2 introduces new RASlogs (FSPF-1013, FSPF-1014) and new CLI outputs in fabricshow and topologyshow to indicate when the maximum paths (16) to a remote domain are exceeded.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 11 of 93 |
Optionally Licensed Software
Fabric OS v7.2 includes all basic switch and fabric support software, as well as optionally licensed software that is enabled via license keys.
Optionally licensed features 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).
Brocade Extended Fabrics—Provides greater than 10km of switched fabric connectivity at full bandwidth over long distances (depending on platform this can be up to 3000km).
Note:
If a port on 16G FC blades or a 16G switch is configured to operate at 10G speed, Extended fabrics license is not needed to enable long distance connectivity on that port.
Brocade ISL Trunking— Provides the ability to aggregate multiple physical links into one logical link for enhanced network performance and fault tolerance. Also includes Access Gateway ISL Trunking on those products that support Access Gateway deployment.
Brocade Advanced Performance Monitoring—Enables performance monitoring of networked storage resources. This license includes the Top Talkers feature.
Brocade Fabric Watch — Monitors mission-critical switch operations. Fabric Watch includes Port Fencing capabilities.
Brocade Fabric Vision – Enables MAPS (Monitoring and Alerting Policy Suite), Flow Vision, and D_Port to nonBrocade devices. MAPS enables rules based monitoring and alerting capabilities, provides comprehensive dashboards to quickly troubleshoot problems in Brocade SAN environments. Flow Vision enables host to LUN flow monitoring, application flow mirroring for offline capture and deeper analysis, and test traffic flow generation function for SAN infrastructure validation. D_Port to non-Brocade devices allows extensive diagnostic testing of links to devices other than Brocade switches and adapters. (Functionality requires support by attached device, availability TBD).
Fabric Vision license also enables Fabric Watch and Advanced Performance Monitoring functionalities without requiring Brocade Fabric Watch or Brocade Advanced Performance Monitoring license (with FOS v7.2 and later only).
Note:
If installed on a switch operating with FOS v7.1.x, the Fabric Vision license will be displayed as “Fabric Insight”. If installed on a switch operating with FOS v7.0.x or earlier, the Fabric Vision license will be displayed as “Unknown”. Fabric Vision features are not supported under FOS v7.1.x or earlier.
FICON Management Server— Also known as “CUP” (Control Unit Port), enables host-control of switches in Mainframe environments.
Enhanced Group Management — This license enables full management of devices in a data center fabric with deeper element management functionality and greater management task aggregation throughout the environment. This license is used in conjunction with Brocade Network Advisor application software and is applicable to all FC platforms supported by FOS v7.0 or later.
Note: This license is enabled by default on all 16G FC platforms, and on DCX and DCX-4S platforms that are running Fabric OS v7.0.0 or later.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 12 of 93 |
Adaptive Networking with QoS—Adaptive Networking provides a rich framework of capability allowing a user to ensure high priority connections obtain the bandwidth necessary for optimum performance, even in congested environments. The QoS SID/DID Prioritization and Ingress Rate Limiting features are the first components of this license option, and are fully available on all 8Gb and 16Gb platforms.
Note :
With FOS v7.2, the Adaptive Networking license has become part of the base FOS firmware, and features under this license no longer require the license to be installed. Customers that wish to have these capabilities without purchasing the license are required to upgrade to FOS v7.2 or later.
Brocade 6520 does not require the Adaptive Networking with QoS license to enable the capabilities associated with this license. These capabilities are included by default on the Brocade 6520.
Server Application Optimization — When deployed with Brocade Server Adapters, this license optimizes overall application performance for physical servers and virtual machines by extending virtual channels to the server infrastructure. Application specific traffic flows can be configured, prioritized, and optimized throughout the entire data center infrastructure. This license is not supported on the Brocade 8000.
Note :
With FOS v7.2, Server Application Optimization license has become part of the base FOS firmware, and features under this license no longer require the license to be installed. Customers that wish to have these capabilities without purchasing the license are required to upgrade to FOS v7.2 or later.
Brocade 6520 does not require the SAO license to enable the capabilities associated with this license. These capabilities are included by default on the Brocade 6520.
Integrated Routing— This license allows any port in a DCX 8510-8, DCX 8510-4, Brocade 6510, Brocade 6520, DCX-4S, DCX, 5300, 5100, 7800, or Brocade Encryption Switch to be configured as an Ex_port or VEx_port (on some platforms) supporting Fibre Channel Routing. This eliminates the need to add an FR4-18i blade or use the 7500 for FCR purposes, and also provides double or quadruple the bandwidth for each FCR connection (when connected to another 8Gb or 16Gb-capable port). .
Encryption Performance Upgrade — This license provides additional encryption processing power. For the Brocade Encryption Switch or a DCX/DCX-4S/DCX 8510-8/DCX 8510-4, the Encryption Performance License 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 8510- 8/DCX 8510-4 with FS8-18 blade(s) to read and decrypt NetApp DataFort-encrypted disk and tape LUNs. DataFort Compatibility License is also required on the Brocade Encryption Switch or DCX/DCX-4S/DCX 8510- 8/DCX 8510-4 Backbone with FS8-18 Encryption Blade(s) installed to write and encrypt the disk and tape LUNs in NetApp DataFort Mode (Metadata and Encryption Algorithm) so that DataFort can read and decrypt these LUNs. DataFort Mode tape encryption and compression is supported beginning with the FOS v6.2.0 release on DCX platforms. Availability of the DataFort Compatibility license is limited; contact your vendor for details.
Advanced Extension – This license enables two advanced extension features: FCIP Trunking and Adaptive Rate Limiting. The FCIP Trunking feature allows multiple IP source and destination address pairs (defined as FCIP Circuits) via multiple 1GbE or 10GbE interfaces to provide a high bandwidth FCIP tunnel and failover resiliency. In addition, each FCIP circuit supports four QoS classes (Class-F, High, Medium and Low Priority), each as a TCP connection. The Adaptive Rate Limiting feature provides a minimum bandwidth guarantee for each tunnel with full utilization of the available network bandwidth without impacting throughput performance under high traffic load. This license is available on the 7800 and the DCX/DCX-4S/DCX 8510-8/DCX 8510-4 for the FX824 on an individual slot basis.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 13 of 93 |
10GbE FCIP/10G Fibre Channel – This license enables the two 10GbE ports on the FX8-24 and/or the 10G FC capability on FC16-xx blade ports supported on DCX 8510 platforms. On the Brocade 6510, Brocade 6520 this license enables 10G FC ports.
On FX8-24:
With this license installed and assigned to a slot with an FX8-24 blade, two additional operating modes (in addition to 10 1GbE ports mode) can be selected:
10 1GbE ports and 1 10GbE port, or
2 10GbE ports On FC16-xx:
Enables 10G FC capability on an FC16-xx blade in a slot that has this license On Brocade 6510, Brocade 6520:
Enables 10G FC capability on Brocade 6510, Brocade 6520.
This license is available on the DCX/DCX-4S/DCX 8510-8/DCX 8510-4 on an individual slot basis.
Advanced FICON Acceleration – This licensed feature uses specialized data management techniques and automated intelligence to accelerate FICON tape read and write and IBM Global Mirror data replication operations over distance, while maintaining the integrity of command and acknowledgement sequences. This license is available on the 7800 and the DCX/DCX-4S/DCX 8510-8/DCX 8510-4 for the FX8-24 on an individual slot basis.
7800 Port Upgrade – This license allows a Brocade 7800 to enable 16 FC ports (instead of the base four ports) and six GbE ports (instead of the base two ports). This license is also required to enable additional FCIP tunnels and also for advanced capabilities like tape read/write pipelining.
ICL 16-link, or Inter Chassis Links -- This license provides dedicated high-bandwidth links between two Brocade DCX chassis, without consuming valuable front-end 8Gb ports. Each chassis must have the 16-link ICL license installed in order to enable the full 16-link ICL connections. (Available on the DCX only.)
ICL 8-Link – This license activates all eight links on ICL ports on a DCX-4S chassis or half of the ICL bandwidth for each ICL port on the DCX platform by enabling only eight links out of the sixteen links available. This allows users to purchase half the bandwidth of DCX ICL ports initially and upgrade with an additional 8-link license to utilize the full ICL bandwidth at a later time. This license is also useful for environments that wish to create ICL connections between a DCX and a DCX-4S, the latter of which cannot support more than 8 links on an ICL port. Available on the DCX-4S and DCX platforms only.
ICL POD License – This license activates ICL ports on core blades of DCX 8510 platforms. An ICL 1st POD license only enables half of the ICL ports on CR16-8 core blades of DCX 8510-8 or all of the ICL ports on CR16-4 core blades on DCX 8510-4. An ICL 2nd POD license enables all ICL ports on CR16-8 core blades on a DCX 8510-8 platform. (The ICL 2nd POD license does not apply to the DCX 8510-4.)
Enterprise ICL (EICL) License – The EICL license is required on a Brocade DCX 8510 chassis when that chassis is connected to four or more Brocade DCX 8510 chassis via ICLs.
Note that this license requirement does not depend upon the total number of DCX 8510 chassis that exist in a fabric, but only on the number of other chassis connected to a DCX 8510 via ICLs. This license is recognized/displayed when operating with FOS v7.0.1 but enforced with FOS v7.1.0 or later.
Note: The EICL license supports a maximum of nine DCX 8510 chassis connected in a full mesh topology or up to ten DCX 8510 chassis connected in a core-edge topology. Refer to the Brocade SAN Scalability Guidelines document for additional information.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 14 of 93 |
Temporary License Support
The following licenses are available in FOS v7.2 as Universal Temporary or regular temporary licenses:
Fabric (E_Port) license
Extended Fabric license
Trunking license
High Performance Extension license
Advanced Performance Monitoring license
Fabric Watch license
Integrated Routing license
Advanced Extension license
Advanced FICON Acceleration license
10GbE FCIP/10GFibre Channel license
FICON Management Server (CUP)
Enterprise ICL license
Fabric Vision license
Note: Temporary Licenses for features available on a per slot basis enable the feature for any and all slots in the chassis.
Temporary and Universal Temporary licenses have durations and expiration dates established in the licenses themselves. FOS will accept up to two temporary licenses and a single Universal license on a unit. Universal Temporary license keys can only be installed once on a particular switch, but can be applied to as many switches as desired. Temporary use duration (the length of time the feature will be enabled on a switch) is provided with the license key. All Universal Temporary license keys have an expiration date upon which the license can no longer be installed on any unit.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 15 of 93 |
Supported Switches
FOS v7.2 supports the following existing platforms:
300, 5100, 5300, 7800, VA-40FC, Brocade Encryption Switch, DCX, DCX-4S
6505, 6510, 6520, DCX 8510-8, DCX 8510-4
FC16-32, FC16-48, FC8-32E, FC8-48E, FX8-24, FS8-18 on DCX 8510-8/DCX 8510-4
FC8-16, FC8-32, FC8-48, FC8-64, FX8-24, FS8-18, FCOE10-24 on DCX/DCX-4S
5410, 5424, 5430, 5450, 5480, 5470, 5460, NC-5480
Support merged to FOS v7.2: 5431, 6547, M6505
Access Gateway mode is also supported by Fabric OS v7.2, and is supported on the following switches: the Brocade 300, 5100, VA-40FC, 5450, 5430, 5431, 5460, 5470, 5480, NC-5480, M5424, 6547, M6505, 6510, 6505.
The Brocade 8000 is not supported with FOS v7.2.0 and later.
Standards Compliance
This software conforms to the Fibre Channel Standards in a manner consistent with accepted engineering practices and procedures. In certain cases, Brocade might add proprietary supplemental functions to those specified in the standards. For a list of FC standards conformance, visit the following Brocade Web site: http://www.brocade.com/sanstandards
The FCOE10-24 blade conform to the following Ethernet standards:
IEEE 802.1D Spanning Tree Protocol
IEEE 802.1s Multiple Spanning Tree
IEEE 802.1w Rapid reconfiguration of Spanning Tree Protocol
IEEE 802.3ad Link Aggregation with LACP
|
IEEE 802.3ae |
10G Ethernet |
|
IEEE 802.1Q |
VLAN Tagging |
IEEE 802.1p Class of Service Prioritization and Tagging
IEEE 802.1v VLAN Classification by Protocol and Port
IEEE 802.1AB Link Layer Discovery Protocol (LLDP)
IEEE 802.3x 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 FCOE10-24 blade:
IEEE 802.1Qbb Priority-based Flow Control
IEEE 802.1Qaz Enhanced Transmission Selection
|
IEEE 802.1 |
DCB Capability Exchange Protocol (Proposed under the DCB Task Group of IEEE |
|
|
802.1 Working Group) |
|
FC-BB-5 |
FCoE (Rev 2.0) |
Technical Support
Contact your switch supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information immediately available:
1.General Information
Technical Support contract number, if applicable
Switch model
Fabric OS v7.2.0a Release Notes v1.0 |
Page 16 of 93 |
Switch operating system version
Error numbers and messages received
supportSave command output and associated files
o For dual CP platforms running FOS v6.2 and above, the supportsave command gathers information from both CPs and any AP blades installed in the chassis
Detailed description of the problem, including the switch or fabric behavior immediately following the problem, and specific questions
Description of any troubleshooting steps already performed and the results
Serial console and Telnet session logs
Syslog message logs
2.Switch Serial Number
The switch serial number is provided on the serial number label, examples of which are shown here:
FT00X0054E9
The serial number label is located as follows:
Brocade Encryption Switch, VA-40FC, 300, 5100, 5300, 6510, 6505, 6520 — On the switch ID pull-out tab located on the bottom of the port side of the switch
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 DCX, DCX 8510-8 — Bottom right of the port side
Brocade DCX-4S, DCX 8510-4 — Back, upper left under the power supply
3.World Wide Name (WWN)
When the Virtual Fabric feature is enabled on a switch, each logical switch has a unique switch WWN. Use the wwn command to display the switch WWN.
If you cannot use the wwn command because the switch is inoperable, you can get the primary WWN from the same place as the serial number, except for the Brocade DCX/DCX-4S and DCX 8510-8/DCX 8510-4. For the Brocade DCX/DCX-4S and DCX 8510-8/DCX 8510-4 access the numbers on the WWN cards by removing the Brocade logo plate at the top of the non-port side. The WWN is printed on the LED side of both cards.
1.License Identifier (License ID)
There is only one License Identifier associated with a physical switch or director/backbone chassis. This License Identifier is required as part of the ordering process for new FOS licenses.
Use the licenseIdShow command to display the License Identifier.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 17 of 93 |
FOS Migration Considerations
This section contains important details to consider before migrating to or from this FOS release.
FOS Upgrade and Downgrade Special Considerations
DCX/DCX-4S units running any FOS v7.1 can be non-disruptively upgraded to FOS v7.2.0a. This upgrade is nondisruptive to both FC and FCoE traffic (when using FCOE10-24 blades).
Any firmware activation on Brocade 7800, or DCX, DCX-4S, DCX 8510-8, DCX 8510-4 with FX8-24 will disrupt I/O traffic on the FCIP links.
Note:
To achieve non-disruptive firmware upgrade on 5431, 6547 and M6505 embedded switches to FOS V7.2.0a please follow the instructions given below:
5431:
Upgrade 5431 from FOS v7.0.1_hut to FOS v7.0.1_hut1 before non-disruptively upgrading it to FOS v7.2.0a.
6547:
Upgrade 6547 from FOS v7.0.0_pha3 to FOS v7.0.0_pha4 before non-disruptively upgrading it to FOS v7.2.0a.
M6505:
Upgrade M6505 from FOS v7.0.1_ sh to FOS v7.0.1_sh1 before non-disruptively upgrading it to FOS v7.2.0a.
Disruptive upgrades to Fabric OS v7.2.0a are allowed and supported from FOS v7.0.x (up to a two-level migration) using the optional “-s” parameter with the firmwaredownload command.
If there are multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node at a time before downloading on another node.
Recommended Migration Paths to FOS v7.2.0a
Migrating from FOS v7.1
Any 8G or 16G platform running any FOS v7.1. firmware can be non-disruptively upgraded to FOS v7.2.0a.
Migrating from FOS v7.0
Any 8G or 16G platform operating at FOS v7.0.x must be upgraded to FOS v7.1.x before non-disruptively upgrading to FOS v7.2.0a.
Disruptive upgrade to FOS v7.2.0a from FOS v7.0 is supported.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 18 of 93 |
Important Notes
This section contains information that you should consider before you use this Fabric OS release.
Brocade Network Advisor Compatibility
Brocade Network Advisor greatly simplifies the steps involved in daily operations while improving the performance and reliability of the overall SAN and IP networking environment. Brocade Network Advisor unifies, under a single platform, 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.
Brocade Network Advisor provide 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 environments to support non-stop networking, address issues before they impact operations, and minimize manual tasks.
Brocade Network Advisor is available with flexible packaging and licensing options for a wide range of network deployments and for future network expansion. Brocade Network Advisor 12.1.1 is available in
SAN-only edition
IP-only edition
SAN+IP edition.
For SAN Management, Network Advisor 12.1.1 is available in three editions:
Network Advisor Professional: a fabric management application that is ideally suited for small-size businesses that need a lightweight management product to manage their smaller fabrics. It manages one FOS fabric at a time and up to 1,000 switch ports. It provides support for Brocade FC switches, Brocade HBAs / CNAs, and Fibre Channel over Ethernet (FCoE) switches.
Network Advisor Professional Plus: a SAN management application designed for medium-size businesses or departmental SANs for managing up to thirty-six physical or virtual fabrics (FOS) and up to 2,560 switch ports. It supports Brocade backbone and director products (DCX 8510-4/DCX-4S, 48Ks, etc.), FC switches, Fibre Channel Over IP (FCIP) switches, Fibre Channel Routing (FCR) switches/ Integrated Routing (IR) capabilities, Fibre Channel over Ethernet (FCoE) / DCB switches, and Brocade HBAs / CNAs.
Network Advisor Enterprise: a management application designed for enterprise-class SANs for managing up to thirty-six physical or virtual fabrics and up to 9,000 switch ports. Network Advisor SAN Enterprise supports all the hardware platforms and features that Network Advisor Professional Plus supports, and adds support for the Brocade DCX Backbone (DCX 8510-8/DCX) and Fiber Connectivity (FICON) capabilities.
More details about Network Advisor’s new enhancements can be found in the Network Advisor 12.1.1 Release Notes, Network Advisor 12.1.1 User Guide, and Network Advisor 12.1.1 Installation, Migration, & Transition Guides.
Note:
Brocade Network Advisor 12.1.1 or later is required to manage switches running FOS 7.2 or later.
WebTools Compatibility
FOS v7.2 is qualified and supported only with Oracle JRE 1.7.0 update 25.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 19 of 93 |
SMI Compatibility
It is important to note that host SMI-S agents cannot be used to manage switches running FOS v7.2.
If users want to manage a switch running FOS v7.2 using SMI-S interface, they must use Brocade
Network Advisor’s integrated SMI agent.
Fabric OS Compatibility
The following table lists the earliest versions of Brocade software supported in this release, that is, the earliest supported software versions that interoperate. Brocade recommends using the latest software versions to get the greatest benefit from the SAN.
To ensure that a configuration is fully supported, always check the appropriate SAN, storage or blade server product support page to verify support of specific code levels on specific switch platforms prior to installing on your switch. Use only FOS versions that are supported by the provider.
For a list of the effective end-of-life dates for all versions of Fabric OS, visit the following Brocade Web site: http://www.brocade.com/support/end_of_life.jsp
Supported Products and FOS Interoperability
4900, 7500, 7500e, 5000, 200E, 48K |
v6.2.2 or later6 |
Brocade 4012, 4016, 4018, 4020, 4024, 4424 |
|
|
|
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 8 |
VA-40FC |
v6.2.1_vfc 6, v6.2.2 or later 6 |
Brocade DCX-4S |
v6.2.0 or later 6 8 |
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 80009 |
V6.1.2_CEE1 or later |
Brocade DCX/DCX-4S with FA4-18 blade(s) |
DCX requires v6.0.x or later 6, DCX-4S |
|
requires 6.2.x or later5 6 |
Brocade DCX 8510-8/DCX 8510-4 |
FOS v7.0 or later |
|
|
Brocade 6510 |
FOS v7.0 or later |
Brocade 6505 |
FOS v7.0.1 or later |
Brocade 6520 |
FOS v7.1 or later |
|
|
5430 |
FOS v7.1 or later10 |
5431, 6547, M6505 |
FOS v7.2 or later10 |
48000 with FA4-18 blade(s), Brocade 7600 |
V6.2.2 or later 6 |
Mi10k, M6140 (McDATA Fabric Mode and Open Fabric Mode) 1 |
Not Supported |
Fabric OS v7.2.0a Release Notes v1.0 |
Page 20 of 93 |
Multi-Protocol Router Interoperability
Brocade 7500 and FR4-18i blade |
V6.2.2 and higher 4 6 8 |
McDATA SANRouters 1620 and 2640 |
Not Supported |
|
|
NOS (VDX Platform) Interoperability
Brocade VDX6710, VDX6720, VDX6730 |
NOS v2.1.1 or later7 |
Brocade VDX8770 |
NOS 3.0 or later |
|
|
Table Notes:
1When routing to an M-EOS edge fabric using frame redirection, the M-EOS fabric must have a FOS-based product in order to configure the frame redirection zone information in the edge fabric.
2When directly attached to a Host or Target that is part of an encryption flow.
3These platforms may not be directly attached to hosts or targets for encryption flows.
4McDATA 1620 and 2640 SANRouters should not be used with FOS-based routing (FCR) for connections to the same edge fabric.
5FA4-18 is not supported in a DCX/DCX-4S that is running FOS v7.0 or later
6If operating with FOS v6.2.2e or earlier, Adaptive Networking QoS must be disabled when connecting to 16G FC platform. Otherwise, ISL will segment.
7Connectivity 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, 6520 (requires FOS v7.1 or later). For higher FCR backbone scalability (refer to separate “Brocade SAN Scalability Guidelines” documentation for details), please use 5300, 6520, DCX, DCX-4S, DCX 8510-8, DCX 8510-4.
8FR4-18i and FC10-6 are not supported on DCX/DCX-4S on FOS v7.1 or later.
9Brocade 8000 is not supported with FOS v7.2 or later.
10Represents the earliest major FOS version. These embedded platforms running respective dedicated FOS versions can also interoperate with FOS v7.2.
Zoning Compatibility Note:
Users are recommended to upgrade to the following versions of firmware when interoperating with a switch running FOS v7.0 or later in the same layer 2 fabric to overcome some of the zoning operations restrictions that otherwise exist:
|
|
|
|
Patch code levels with full zoning |
|
|
Main code level |
|
|
|
|
|
|
|
compatibility |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FOS v6.2 |
|
|
|
FOS v6.2.2d or later |
|
|
|
|
|
|
|
FOS v6.3 |
|
|
|
FOS v6.3.2a or later |
|
FOS v6.4 |
|
|
|
FOS v6.4.1 or later |
|
|
|
|
|
|
|
If there are switches running FOS versions lower than the above listed patch levels in the same fabric as a switch with FOS v7.0 or later, then cfgsave and cfgenable operations initiated from these switches will fail if
Fabric OS v7.2.0a Release Notes v1.0 |
Page 21 of 93 |
the zoning database is greater than 128KB. In such scenarios zoning operations such as cfgsave/cfgenable can still be performed successfully if initiated from a switch running FOS v7.0 or later.
SNMP Support
Starting with FOS v7.2, the Fabric OS MIB Reference document is not updated. You can obtain the latest MIBs from the downloads area of MyBrocade site after logging in.
For information about SNMP support in Fabric Operating System (FOS) and how to use MIBs, see the Fabric OS Administrator’s Guide.
Obtaining the MIBs
You can download the MIB files required for this release from the downloads area of the MyBrocade site. To download the MIBs from the Brocade Technical Support website, you must have a user name and password.
1.On your web browser, go to http://my.brocade.com.
2.Login with your user name and password.
3.Click the downloads tab.
4.On the downloads tab, under Product Downloads, select All Operating Systems from the Download by list.
5.Select Fabric Operating System (FOS), and then navigate to the release.
6.Navigate to the link for the MIBs package and either open the file or save it to disk.
Changes in MIBs and objects
This release introduces the following changes in MIBs and objects:
New MIBs
There are no new MIBs introduced in this release.
Updated MIBs
SW.mib
The following changes have been made to the SW.mib:
Added a new counter, swConnUnitUnroutableFrameCounter.
Added swFwPowerOnHours in SwFwClassesAreas (supported from v7.0.0).
Added swCpuOrMemoryUsage table support for MAPS enabled switches.
Added swFCPortDisableReason (SwFCPortEntry) to send a port disable reason as part of the swFCPortScn varbind.
Added segmented (incompatible) link remote port/wwn support for connUnitLinkTable/swNBTable.
HA.mib
Added bpTable (blade processor table) to the MIB (supported from v6.2.0 for blade processor).
BRCD-FCIP-EXT.mib
Added support for the following MIB objects at tunnel level in the FCIP Extension tunnel. Until and including 7.1.0 release, the following MIB objects were supported only at connection level.
|
fcipExtendedLinkTcpDroppedPackets |
1.3.6.1.4.1.1588.4.1.1.3 |
|
fcipExtendedLinkTcpSmoothedRTT |
1.3.6.1.4.1.1588.4.1.1.5 |
|
fcipExtendedLinkRtxRtxTO |
1.3.6.1.4.1.1588.4.1.1.9 |
|
fcipExtendedLinkRtxDupAck |
1.3.6.1.4.1.1588.4.1.1.10 |
|
fcipExtendedLinkDupAck |
1.3.6.1.4.1.1588.4.1.1.11 |
Fabric OS v7.2.0a Release Notes v1.0 |
Page 22 of 93 |
Deprecated/Obsoleted MIBs
swFCPortSpeed in SW.mib is obsoleted.
Customized OID is not supported from 7.1.0 release.
Blade Support
Fabric OS v7.2 software is fully qualified and supports the blades for the DCX/DCX-4S noted in the following table:
DCX/DCX-4S Blade Support Matrix
16-, 32-, 48and 64-port 8Gbit port blades (FC8-16, |
Supported with FOS v6.0 and above (FC8-64 requires |
FC8-32, FC8-48, FC8-64) |
FOS v6.4) with any mix and up to 8/4 of each. No |
|
restrictions around intermix. |
|
|
FC10-6 |
Not supported on FOS v7.1 or later |
|
|
Intelligent blade |
Up to a total of 8/4 intelligent blades. See below for |
|
maximum supported limits of each blade. |
|
|
Virtualization/Application Blade (FA4-18) |
Not supported on FOS v7.0 or later |
|
|
FCIP/FC Router blade (FR4-18i) |
Not supported on FOS v7.1 or later |
|
|
Encryption Blade (FS8-18) |
Up to a maximum of 4 blades of this type. |
|
|
Next Generation Distance Extension Blade (FX8-24) |
Up to a max of 4 blades of this type. |
|
|
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, FC8-32E, FC8-48E |
Not supported |
|
|
Table 1 Blade Support Matrix for DCX and DCX-4S with FOS v7.2 Note: The iSCSI FC4-16IP blade is not qualified for the DCX/DCX-4S.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 23 of 93 |
Fabric OS v7.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 |
FOS v7.0 or later. |
|
|
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 |
FOS v7.0.1 or later. |
|
|
Intelligent blade |
Up to a total of 8/4 intelligent blades. See below for |
|
maximum supported limits of each blade. |
|
|
FCIP/FC Router blade (FR4-18i) |
Not supported. |
|
|
Virtualization/Application Blade (FA4-18) |
Not Supported |
|
|
Encryption Blade (FS8-18) |
Up to a maximum of 4 blades of this type. |
|
|
Next Generation Distance Extension Blade (FX8-24) |
Up to a max of 4 blades of this type. |
|
|
FCoE/L2 CEE blade FCOE10-24 |
Not supported on DCX 8510 in FOS v7.x |
|
|
Table 2 Blade Support Matrix for DCX 8510-8 and DCX 8510-4 with FOS v7.2 Note: The iSCSI FC4-16IP blade is not qualified for the DCX 8510-8/DCX 8510-4.
1. Note that 16G SFP+ is not supported in FC8-32E and FC8-48E blades
Fabric OS v7.2.0a Release Notes v1.0 |
Page 24 of 93 |
Power Supply Requirements for Blades in DCX/DCX-4S
|
|
|
DCX/DCX-4S |
|
DCX/DCX-4S |
|
|
|
|
|
|
Blades |
Type of Blade |
@110 VAC |
|
@200-240 VAC |
|
|
Comments |
|
|
|
|
|
|
|
|
|||||
|
|
|
(Redundant |
|
(Redundant |
|
|
|
|
|
|
|
|
configurations) |
|
configurations) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
FC10-61, FC8- |
Port Blade |
2 Power |
|
2 Power Supplies |
|
|
|
|
|
|
16, FC8-32, |
|
Supplies |
|
|
|
Distribute the Power Supplies |
|
||
|
FC 8-48, FC8- |
|
|
|
|
|
|
evenly to 2 different AC |
|
|
|
|
|
|
|
|
|
|
|
||
|
64 |
|
|
|
|
|
|
connections for redundancy. |
|
|
|
FR4-18i1 |
Intelligent |
Not Supported |
|
2 Power Supplies |
|
|
|
|
|
|
|
Blade |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FS8-18, |
Intelligent |
Not Supported |
|
DCX: 2 or 4 Power |
|
|
For DCX with three or more |
|
|
|
FX8-24, |
Blade |
|
|
Supplies |
|
|
FS8-18 Blades, (2+2) |
|
|
|
FCOE10-24 |
|
|
|
|
|
|
220VAC Power Supplies are |
|
|
|
|
|
|
|
DCX-4S: 2 Power |
|
|
required for redundancy. |
|
|
|
|
|
|
|
|
|
For DCX with one or two |
|
||
|
|
|
|
|
Supplies |
|
|
|
||
|
|
|
|
|
|
|
|
FS8-18 Blades, (2) 220VAC |
|
|
|
|
|
|
|
|
|
|
Power Supplies are required |
|
|
|
|
|
|
|
|
|
|
for redundancy. |
|
|
|
|
|
|
|
|
|
|
For DCX-4S, (2) 220VAC |
|
|
|
|
|
|
|
|
|
|
Power Supplies provide |
|
|
|
|
|
|
|
|
|
|
redundant configuration |
|
|
|
|
|
|
|
|
|
|
with any supported number |
|
|
|
|
|
|
|
|
|
|
of FS8-18 Blades. |
|
|
|
|
|
|
|
|
|
|
For both DCX and DCX-4S |
|
|
|
|
|
|
|
|
|
|
with FX8-24 blades, (1+1) |
|
|
|
|
|
|
|
|
|
|
220VAC Power Supplies are |
|
|
|
|
|
|
|
|
|
|
required for redundancy. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 3 Power Supply Requirements for DCX and DCX-4S
1. Note that FC10-6 and FR4-18i are not supported with FOS v7.1 or later
Fabric OS v7.2.0a Release Notes v1.0 |
Page 25 of 93 |
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 |
|
|
|
|
|
|
|
|
DCX 8510-8 |
|
|
DCX 8510-8 |
|
|
|
|
|
|
|
Blades |
|
|
Type of Blade |
|
|
@110 VAC |
|
|
@200-240 |
|
|
Comments |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
Number of Ports |
|
|
|
|
|
|
(Redundant |
|
|
VAC (Redundant |
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
configurations) |
|
|
configurations) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Any combination |
|
FC8-64, FC16-32, |
|
Port Blade |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
of 8Gb or 16Gb |
|
FC8-32E |
|
|
|
|
|
|
|
Supplies |
|
Power Supplies |
|||||
ports with QSFP |
|
|
|
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
|||
ICLs |
|
|
|
|
|
|
|
|
|
|
|
|
|
Power Supplies |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|||||||
256 16Gb ports + |
|
FC16-32, FC16-48 |
|
Port Blade |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
QSFP ICLs |
|
(Maximum of fully |
|
|
|
|
|
|
|
Supplies |
|
Power Supplies |
|||||
|
|
|
|
populated FC16-32 |
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
||
|
|
|
|
blades) |
|
|
|
|
|
|
|
|
|
|
Power Supplies |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Max 8 FC16-32 port |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
blades |
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
256 8Gb ports + |
|
FC8-32E, FC8-48E |
|
Port Blade |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
QSFP ICLs |
|
(Maximum of fully |
|
|
|
|
|
|
|
Supplies |
|
Power Supplies |
|||||
|
|
|
|
populated FC8-32E |
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
||
|
|
|
|
blades) |
|
|
|
|
|
|
|
|
|
|
Power Supplies |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Max 8 FC8-32E port |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
blades |
|
192 16Gb Ports & |
|
FC16-32, FC16-48, |
|
Port / |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
max 2 intelligent |
|
FX8-24, FS8-18 |
|
Intelligent |
|
|
|
|
Supplies |
|
Power Supplies |
||||||
blades (FX8-24 |
|
|
Blade |
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
||||||
/FS8- |
|
|
|
|
|
|
|
|
|
|
|
|
|
Power Supplies |
|||
18/combination) |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
with QSFP ICLs |
|
|
|
|
|
|
|
|
|
|
|
|
|
Max four FC16-48 |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
port blades and max |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 Intelligent blades |
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
192 8Gb Ports & |
|
FC8-32E, FC8-48E, |
|
Port / |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
max 2 intelligent |
|
FX8-24, FS8-18 |
|
Intelligent |
|
|
|
|
Supplies |
|
Power Supplies |
||||||
blades (FX8-24 |
|
|
Blade |
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
||||||
/FS8-18/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
Power Supplies |
|||
combination) with |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
QSFP ICLs |
|
|
|
|
|
|
|
|
|
|
|
|
|
Max four FC8-48E |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
port blades and max |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 Intelligent blades |
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
336 16Gb ports + |
|
FC16-48 |
|
Port Blade |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
QSFP ICLs |
|
(Maximum of |
|
|
|
|
|
|
|
Supplies |
|
Power Supplies |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
|||
|
|
|
|
seven FC16-48 |
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
blades, with one |
|
|
|
|
|
|
|
|
|
|
Power Supplies |
||
|
|
|
|
empty port blade |
|
|
|
|
|
|
|
|
|
|
Max 7 FC16-48 port |
||
|
|
|
|
slot) |
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
blades |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
336 8Gb ports + |
|
FC8-48E |
|
Port Blade |
|
4 Power Supplies |
|
2 Power |
|
200-240VAC: 1+1 |
|||||||
QSFP ICLs |
|
(Maximum of |
|
|
|
|
|
|
|
Supplies |
|
Power Supplies |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
110VAC: 2+21 |
|||
|
|
|
|
seven FC8-48E |
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
blades, with one |
|
|
|
|
|
|
|
|
|
|
Power Supplies |
||
|
|
|
|
empty port blade |
|
|
|
|
|
|
|
|
|
|
Max 7 FC8-48E port |
||
|
|
|
|
slot) |
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
blades |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
Fabric OS v7.2.0a Release Notes v1.0 |
Page 26 of 93 |
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 |
|
|
|
|
|
|
|
|
DCX 8510-8 |
|
|
DCX 8510-8 |
|
|
|
|
|
|
|
Blades |
|
|
Type of Blade |
|
|
@110 VAC |
|
|
@200-240 |
|
|
Comments |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
Number of Ports |
|
|
|
|
|
|
(Redundant |
|
|
VAC (Redundant |
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
configurations) |
|
|
configurations) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
384 16Gb ports + |
|
FC16-32, FC16-48 |
|
Port Blade |
|
Not Supported |
|
4 Power |
|
200-240VAC: |
|||||||
QSFP ICLs |
|
|
|
|
|
|
|
|
|
|
Supplies |
|
For DCX 8510-8, four |
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(2+2)1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
220V AC Power |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Supplies are required |
|
384 8Gb ports + |
|
FC8-32E, FC8-48E |
|
Port Blade |
|
Not Supported |
|
4 Power |
|
200-240VAC: |
|||||||
QSFP ICLs |
|
|
|
|
|
|
|
|
|
|
Supplies |
|
For DCX 8510-8, four |
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(2+2)1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
220V AC Power |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Supplies are required |
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
Any combination |
|
FC16-32, FC16-48, |
|
Intelligent |
|
Not Supported |
|
4 Power |
|
For DCX 8510-8, four |
|||||||
of 8Gb or 16Gb |
|
FC8-64, FC8-32E, |
|
Blade |
|
|
|
|
Supplies |
(2+2)1 |
|
||||||
ports and |
|
FC8-48E, FS8-18, |
|
/Combination |
|
|
|
|
|
|
|
220V AC Power |
|||||
intelligent blades |
|
FX8-24 |
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
Supplies are required |
||||||
with QSFP ICLs |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
when any special |
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
purpose blade are |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
installed |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 4 Power Supply Requirements for DCX 8510-8
Notes:
1.When 2+2 power supply combination is used, the users are advised to configure the Fabric Watch setting for switch marginal state to be two power supplies. Users can use the CLI switchstatuspolicyset to configure this value if the current value is set to zero. In FOS v7.0.x, the default setting for the marginal state due to missing power supplies is incorrectly set to zero, which will prevent Fabric Watch from generating notifications when the switch enters the marginal state due to missing power supplies
Fabric OS v7.2.0a Release Notes v1.0 |
Page 27 of 93 |
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 |
|
|
|
|
|
|
|
|
DCX 8510-4 @110 |
|
|
DCX 8510-4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
@200-240 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
Number of |
|
|
Blades |
|
|
Type of Blade |
|
|
VAC (Redundant |
|
|
|
|
Comments |
|
|
|
|
|
|
|
|
|
|
|
VAC (Redundant |
|
|
|
|||||
|
|
|
|
|
|
|
|
|
configurations) |
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
Ports |
|
|
|
|
|
|
|
|
|
|
configurations) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
96 ports max |
|
FC16-32, |
|
Port Blade |
|
2 Power Supplies |
|
2 Power |
|
1+1 redundancy with 110 |
|||||||
with QSFP |
|
FC8-32E |
|
|
|
|
|
|
|
Supplies |
|
or 200-240 VAC power |
|||||
ICLs |
|
|
|
|
|
|
|
|
|
|
|
|
|
supplies |
|||
|
|
|
|
|
|
|
|
|
|
|
|||||||
Any |
|
FC16-32, |
|
Intelligent Blade |
|
Not Supported |
|
2 Power |
|
200-240VAC: 1+1 Power |
|||||||
combination |
|
FC16-48, |
|
/Combination |
|
|
|
|
Supplies |
|
Supplies |
||||||
of 8Gb or 16 |
|
FC8-32E, |
|
|
|
|
|
|
|
|
|
|
|
|
|||
Gb ports and |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
FC8-48E, |
|
|
|
|
|
|
|
|
|
|
|
|
||||
intelligent |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
FC8-64, |
|
|
|
|
|
|
|
|
|
|
|
|
||||
blades with |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
FS8-18, |
|
|
|
|
|
|
|
|
|
|
|
|
||||
QSFP ICLs |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
FX8-24 |
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 5 Power Supply Requirements for DCX 8510-4
Scalability
All scalability limits are subject to change. Limits may be increased once further testing has been completed, even after the release of Fabric OS. For current scalability limits for Fabric OS, refer to the Brocade Scalability Guidelines document, available under the Technology and Architecture Resources section at http://www.brocade.com/compatibility
Other Important Notes and Recommendations
Adaptive Networking/Flow-Based QoS Prioritization
Any 8G or 4G FC platform running FOS v6.2.2e or lower version of firmware cannot form an E-port with a 16G FC platform when Adaptive Networking QoS is enabled at both ends of the ISL. Users must disable QoS at either end of the ISL in order to successfully form an E-port under this condition.
Users can disable QoS via portcfgQos --disable command. Please consult Fabric OS Command Reference manual for details related to portcfgQoS command.
When using QoS in a fabric with 4G ports or switches, FOS v6.2.2 or later must be installed on all 4G products in order to pass QoS info. E_Ports from the DCX to other switches must come up AFTER
6.2.2is running on those switches.
When FOS is upgraded from v7.1.x to v7.2.0 or later:
If the Adaptive Networking license was NOT installed in v7.1.x, all ports will have QOS disabled following the firmware upgrade and links will come up in normal mode.
If the Adaptive Networking license was installed in v7.1.x, there will be no change in port QOS mode following the upgrade.
If the remote port supports QOS and QOS is not explicitly disabled on the local or remote port, the link will come up in QOS mode.
Otherwise, the link will come up in normal mode.
Fabric OS v7.2.0a Release Notes v1.0 |
Page 28 of 93 |
Loading...