Brocade Network OS 2.1.1_fuj Release Notes v1.1 September 6, 2012 Document History Document Title Summary of Changes Publication Date Brocade Network OS 2.1.1_fuj Release Notes v1.0 Initial release Aug 27, 2012 Brocade Network OS 2.1.1_fuj Release Notes v1.
Copyright © 2012 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron, TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health, OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents Overview ...................................................................................................................................................... 5 Descriptions of Key NOS Features ........................................................................................................... 5 VDX 2730 ...................................................................................................................................................... 6 Hardware Feature Descriptions ......
APPENDIX A .............................................................................................................................................. 21 Show enclosure......................................................................................................................................................
Overview Brocade NOS 2.1.1_fuj is the platform-specific release that supports the VDX 2730 Connection Blade for the Fujitsu BX900 and BX400 Blade Server. Other than the expectations noted in this document, this software release is functionally similar to NOS 2.1.1. Release NOS 2.1.1_fuj is based on Brocade Network Operating System (NOS) v2.1.1, which provides the basis for Brocade VCS™ technology that runs on Brocade VDX™ switches.
VDX 2730 The Brocade VDX 2730 10GbE Connection Blade for the Fujitsu PRIMERGY BX900 and BX400 Blade Servers is a 10 Gbps Ethernet Data Center Bridging (DCB) embedded switch module that provides six external native 8-Gbps or 4-Gbps Fibre Channel (FC) ports, and six external 10-Gbps Ethernet ports, allowing you to combine storage and network traffic on a single network.
• One internal I2C connection to the PRIMERGY BX Management Blade provides control and status collection. • One internal serial port (RS-232) connection to the PRIMERGY BX Management Blade provides switch control. • Two internal 10/100 Mbps Ethernet interfaces over the midplane to the Management Blade support switch management. • Port status LEDS indicate status of the ports, and system status LEDs indicate UID, health, and module status using color indicators and patterns.
Link Aggregation • Port channel 802.3ad providing Link Aggregation Control Protocol (LACP) and static support • Virtual Link Aggregation Group (vLAG) (a LAG that spans multiple physical switches) • QoS • 802.1x and 802.
• VM-Aware Network Automation with 8000 MAC Addresses • VLAGs with 32 ports New Features VCS Fabric to FC SAN Connectivity A VDX 2730 running NOS v2.1.1_fuj can form an Inter Fabric Link (IFL) by connecting to an EX-port on most Brocade 8-Gbps or 16-Gbps FC platforms operating FOS v7.0.1 or later. In most common deployment scenarios, a VDX 2730 connects directly to an FCR “backbone” fabric (an FC fabric with a switch acting as a Fibre Channel Router, or FCR).
New Enhancements and Support Support for USR Optics NOS v2.1.1_fuj supports Ultra Short Range (USR) optics. Please refer to the Brocade VDX 2730 10GbE Connection Blade for the Fujitsu PRIMERGY BX900 and BX400 Blade Servers hardware Reference Manual for actual part numbers. VLAG support VLAG is supported on internal as well as external Ethernet ports. VM-Aware Network Automation with vSphere 5.0 The VM-Aware Network Automation feature is validated with VMware vSphere 5.0 in NOS v2.1.1_fuj.
The VDX 2730 also has an enterprise SKU SM-VDX2730-0001 that enables 24-port 10G Ethernet ports, FCoE/FC and VCS capabilities in the same SKU. Standards, Compatibility, Interoperability, and Scalability Standards Compliance This software generally conforms to Ethernet standards in a manner consistent with accepted engineering practices and procedures.
Scalability All scalability limits are subject to change. Limits may be increased once further testing has been completed, even after the release of a particular Network OS version. The limits noted in this table are derived from the NOS_2.1.1 release notes.
NOS Scalability Limits Standalone Switch VCS Fabric Maximum size of Zoning Database (in bytes) N/A 150K Maximum # of Management ACL 256 256 Maximum # of VMs supported in VM Aware Network Automation 8000 8000 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 available: 1.
Documentation Updates For detailed NOS documentation refer to NOS 2.1.1 release notes. When using the NOS 2.1.1 documentation, the VDX 2730 is equivalent to the VDX 6720 except where noted in this section. Refer to www.brocade.com or my.brocade.com http://my.brocade.com/ for the latest versions of the documents. The following three NOS 2.1.
Compatibility The following tables list the interoperability matrix with Brocade and non-Brocade parts. The tested software versions on the parts are also provided in the table. For Brocade parts, it is recommended that you use the latest software versions to get the best benefits. Latest information on the effective end-of-life dates for all versions of software (NOS or FOS) is available on the Brocade website at: http://my.brocade.com SUPPORTED SWITCH SOFTWARE RELEASE BROCADE BR8000 v7.0.
LOM RedHat EL 6.1 64-bit, Windows Server 2008 R2, BX920 S3 Windows Server 2003 SP1 64-Bit RedHat EL 6.1 64-bit, Windows Server 2008 R2, BX924 S3 Windows Server 2003 SP1 64-Bit BX960 S1 RedHat EL 6.1 64-bit, Windows Server 2008 R2 *Intel Niantic-based LOM BX924 S2 Emulex BE3-based LOM BX400 CHASSIS SUPPORT Server Blade Type OS Type BX920 S3 RedHat EL 6.1 64-bit, Windows Server 2008 R2 BX924 S3 RedHat EL 6.1 64-bit, Windows Server 2008 R2 BX924 S2 RedHat EL 6.
Important Notes This section contains information that you should consider before you use this Network OS release. This information is derived from NOS 2.1.1 release notes. Command Line Interface (CLI) • Some commands will not produce paginated output. • For certain commands (including the no form with some commands), “?” will show unsupported additional options. • Tab completion and -c (cancel) does not work for some commands.
• A SPAN destination port cannot be a profiled port. • All AMPP features that were supported only on a physical interface on NOS v2.0 are now supported on a VLAG in NOS v2.1, with the exception of FCoE sub-profile, which is not supported in LAG/VLAG mode. • While migrating from a legacy AMPP environment to VM Aware Network Automation, it is recommend that you delete all manually created port profiles to facilitate smooth migration.
• On both ISL and Edge ports, sFlow sampling is supported only in the inbound direction. • The DNS configuration is primarily used for LDAP. It should be noted that DNS look-up will not be used by PING, Traceroute, or any other services. These services will still require specifying the actual IP address. • VM-Aware Network Automation will work only with VMware vSphere version 4.0, 4.1 and 5.0. • Enabling VM-Aware Network Automation will cause the Brocade VDX switch to drop CDP packets.
• Critical NOS services may terminate, resulting in a switch reboot if the switch is loaded with a large number of VLANs configured for "no shutdown." Configuring the switch with all VLAN interfaces set to “shutdown” will prevent this from occurring and will not affect any functionality. • The VCS replace command is not supported on VDX 2730.
APPENDIX A This section details the NOS feature/commands specific to the VDX 2730. Show enclosure Overview Shows the chassis model name and module bay ID in which the switch is inserted.
