HP A7533A - Brocade 4Gb SAN Switch Base Release Note
HP A7533A - Brocade 4Gb SAN Switch Base Release Note

HP A7533A - Brocade 4Gb SAN Switch Base Release Note

Hp storageworks fabric os 6.1.0h release notes (5697-7961, january 2009)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:

Advertisement

HP StorageWorks Fabric OS 6.1.0h

release notes

Part number: 5697-7961
Fifth edition: January 2009

Advertisement

Table of Contents
loading

Summary of Contents for HP A7533A - Brocade 4Gb SAN Switch Base

  • Page 1: Release Notes

    HP StorageWorks Fabric OS 6.1.0h release notes Part number: 5697-7961 Fifth edition: January 2009...
  • Page 2 Legal and notice information © Copyright 2008-2009 Hewlett-Packard Development Company, L.P. © Copyright 2008-2009 Brocade Communications Systems, Incorporated Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
  • Page 3: Effective Date

    Version 6.1.0h NOTE: This software conforms to the Fibre Channel Standards in a manner consistent with accepted engineering practices and procedures. Supersedes Fabric OS 6.1.0g released in November, 2008. Effective date January 2009 Description Fabric OS 6.1.0a integrated many new features that are listed below. Fabric OS 6.1.0h also provides these same features, but does not add any new features since 6.1.0a.
  • Page 4: Access Gateway

    New feature summaries This section lists features and improvements implemented with Fabric OS 6.1.0a. Fabric OS 6.1.0h continues this support. Enhanced connectivity with McDATA products McDATA connectivity enhancements include: • M-EOS Native Fabric Mode support—HP supports Interop Mode 2 on Fabric OS 6.1.x on the 4/256 SAN Director &...
  • Page 5: Port Mirroring

    Traffic Isolation Zones over FCR This enhancement enables traffic isolation across EX ports and VEX ports. This benefits applications like Tape Pipelining and Fast Write that traverse VE ports where customers want to control the exact path and ports that are used. Port Mirroring Fabric OS 6.1.x adds support for Port Mirroring to 8-Gb ports.
  • Page 6: New Hardware Support

    LDAP FOS 6.1 includes enhancements to LDAP allowing Active Directory server roles to be mapped to the various switch roles. Parameter added for slotshow command An optional –m parameter has been added for the slotshow command, to display Model Names for each blade installed in a DC SAN Director or 4/256 SAN Director chassis.
  • Page 7 • HP StorageWorks SAN Director 32 Port 8-Gb FC blade (Brocade FC8-32) • HP StorageWorks SAN Director 48 Port 8-Gb FC blade (Brocade FC8-48) NOTE: The HP StorageWorks SAN Director 16 Port 8-Gb FC blade (FC8-16) is supported in the 4/256 beginning with Fabric OS 6.0.0b.
  • Page 8: Devices Supported

    • HP StorageWorks SAN Switch 2/16V (Brocade 3850 switch) • HP StorageWorks SAN Switch 2/16, which operates with Fabric OS 3.2.x (Brocade 3800 switch) • HP StorageWorks SAN Switch 2/32 (Brocade 3900 switch) • HP StorageWorks Multi-protocol (MP) Router, which operates with XPath OS 7.4.x (Brocade AP7420) IMPORTANT: Any enhancements for the above models will be delivered in Fabric OS 3.2.x, Fabric OS 5.0.5x,...
  • Page 9 Access Gateway support Access Gateway mode is supported on the following HP products only: • Brocade 4-Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012) • Brocade 4-Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024) • HP StorageWorks 4/16 SAN Switch (Brocade 200E) •...
  • Page 10 • McDATA fabrics running EOS 09.06.xx with Brocade Fabric OS 5.3.1, 5.3.1a, 6.0.0b and 6.0.1a • Cisco MDS 9506, 9509, 9216 and 9216a Multilayer Director switches • Cisco fabrics running SAN-OS 3.0(2a) with Brocade Fabric OS 5.2.1b • Cisco fabrics running SAN-OS versions 3.1(2a), 3.1(3), 3.1(3a) with Brocade Fabric OS 5.3.0, 5.3.0a, 5.3.0b, 5.3.0c, 5.3.0d •...
  • Page 11 Model Earliest compatible ver- Recommended version sion HP StorageWorks Core Switch 2/64 5.0.5d 5.0.5f HP StorageWorks SAN Director 2/128 in Chassis Config modes 3 and 4 only HP StorageWorks SAN Switch 2/8V 5.1.1b 5.3.2 HP StorageWorks SAN Switch 2/16V HP StorageWorks SAN Switch 2/32 HP StorageWorks SAN Director 2/128 HP StorageWorks 4/256 SAN Director 5.1.1b...
  • Page 12 Model Earliest compatible ver- Recommended version sion HP StorageWorks 8/80 SAN Switch 6.1.0a 6.1.0h Fabric Manager 5.2.0a 4/256 SAN Director blade support Fabric OS 6.1.x is fully qualified and supports the Director blades listed in Table Table 2 4/256 SAN Director blade support matrix Director blade Number of blades FC4-16...
  • Page 13: Firmware Upgrade Instructions

    Power supply requirements for Director blades Table 4 lists power supply requirements for Director blades to provide full redundancy (220V power is assumed). IMPORTANT: Director blades must meet minimum Fabric OS levels to operate in Director chassis. For example, the FC8-32 is not supported in the 4/256 SAN Director with Fabric OS 6.0.x.
  • Page 14 Under Storage, select Storage Networking. Select the link for the appropriate switch, select your product, and then select Cross operating system (BIOS, firmware, Diagnostics, etc.). Select Firmware. Select V6.x Firmware for HP StorageWorks B-Series Fibre Channel Switches for v6.1.0h: • To download the firmware, select Download. •...
  • Page 15: Important Notes

    Important notes Table 5 provides information you should know before upgrading to Fabric OS 6.1.0h. Table 5 Important release information Topic Description PID Format Beginning with Fabric OS version 6.x, the only supported PID format is core pid (1). See the HP StorageWorks Fabric OS 6.1.x administrator guide for details.
  • Page 16 Topic Description Traffic Isolation over FCR • All switches and Fibre Channel Routers both in edge and backbone fabrics must be running Fabric OS 6.1.0 in order to support this feature. • It is essential to have “fail-over” policy enabled in all edge fabrics that are part of the Traffic Isolation Zones, in order for the proper functioning of Traffic Isolation over FCR.
  • Page 17 • Logs a RASLog message when a 2.x switch joins the fabric. • HA failover and user notification occurs on the 4/256 SAN Director when there is a failed Ethernet chip (oscillator chip). HP StorageWorks Fabric OS 6.1.0h release notes...
  • Page 18 Fabric OS 6.1.0 fixes Table 6 lists defects closed in the Fabric OS 6.1.0 firmware release. Table 6 Fabric OS 6.1.0 closed defects Closed defect summary Solution Autonegotiation with specific HBAs does not bring the ports to the Fixed in Fabric OS 6.1.0 correct maximum speed.
  • Page 19 Closed defect summary Solution An "ipfilter --transabort" command running in one Telnet Fixed in Fabric OS 6.1.0 session can be aborted from another Telnet session. Cannot set "Portlog events enable" accurately. Fixed in Fabric OS 6.1.0 The DC Director may ASSERT in a specific test scenario while running Fixed in Fabric OS 6.1.0 a particular FICON test program (SAK IRNDUP).
  • Page 20 Closed defect summary Solution If a device tries to login to an NPIV port using a port WWN, which Fixed in Fabric OS 6.1.0 is already used by another device that has already logged in, the switch simply drops the new login (FDISC) request instead of rejecting Incorrect FRU Update date is received for Brocade_Chassis class.
  • Page 21 Closed defect summary Solution On disabling the proxy switch (FOS 6.0 ), no event received on the Fixed in Fabric OS 6.1.0 SMIA agent side. When HA sync was stopped, a SAN Director 2/128 did not output Fixed in Fabric OS 6.1.0 the FW-1433 message.
  • Page 22 Closed defect summary Solution The switch status is shown as Healthy with one core blade even when Fixed in Fabric OS 6.1.0 the policy is set to show as marginal on removal/failure of a core blade. FICON Tape Pipelining with specific tape devices results in block count Fixed in Fabric OS 6.1.0 mismatch errors.
  • Page 23 Fabric OS 6.1.0a fixes Table 7 lists defects closed in the Fabric OS 6.1.0a firmware release. Table 7 Fabric OS 6.1.0a closed defects Closed defect summary Solution Under rare conditions, fabric mode TopTalker monitor does not display Fixed in Fabric OS 6.1.0a correct flow values.
  • Page 24 Fabric OS 6.1.0b fixes Table 8 lists defects closed in the Fabric OS 6.1.0b firmware release. Table 8 Fabric OS 6.1.0b closed defects Closed defect summary Solution I2C response failure and subsequent reset will occasionally result in Fixed in Fabric OS 6.1.0b DC Director fan fault errors.
  • Page 25 Fabric OS 6.1.0c fixes Table 9 lists defects closed in the Fabric OS 6.1.0c firmware release. Table 9 Fabric OS 6.1.0c closed defects Closed defect summary Solution HP StorageWorks 8/40 SAN Switch running Fabric OS 6.1.0 may Fixed in Fabric OS 6.1.0c generate over-temperature warnings while at ambient temperature after booting up.
  • Page 26 Fabric OS 6.1.0d fixes Table 10 lists defects closed in this Fabric OS 6.1.0d firmware release. Table 10 Fabric OS 6.1.0d closed defects Closed defect summary Solution Cannot establish FCIP tunnel between a 400 Multi-protocol Router and Fixed in Fabric OS 6.1.0d a B-Series MP Router blade with WAN optimization controllers in between the two FCIP devices.
  • Page 27 Fabric OS 6.1.0e fixes Table 11 lists defects closed in this Fabric OS 6.1.0e firmware release. Table 11 Fabric OS 6.1.0e closed defects Closed defect summary Solution TCP RX window advertisement can be much smaller than the actual Fixed in Fabric OS 6.1.0e. size of the RX window.
  • Page 28 Fabric OS 6.1.0f fixes Table 12 lists defects closed in this Fabric OS 6.1.0f firmware release. Table 12 Fabric OS 6.1.0f closed defects Closed defect summary Solution A failed Pause frame, sent during firmwaredownload process in Fixed in Fabric OS 6.1.0f. Interop Modes 2 and 3, causes a fabric rebuild Workaround: Use the firmwaredownload —o option to...
  • Page 29 Closed defect summary Solution With FC fastwrite zones (connecting local hosts to remote devices) and Fixed in Fabric OS 6.1.0g. non-FC fastwrite zones (connecting local hosts to local devices) going Workaround: Run portdisable and to the same devices, not all host ports receive RSCNs after device logon portenable on the initiator port to and link down.

Table of Contents