HP B–series Fabric OS 6.3.
© Copyright 2010–2012 Hewlett-Packard Development Company, L.P.
Contents Version....................................................................................................................................5 Description..............................................................................................................................5 Update recommendation.......................................................................................................5 Supersedes.......................................................................................
FC FastWrite.....................................................................................................................28 Native connectivity.............................................................................................................28 FCS Automatic Distribution..................................................................................................28 FCAP......................................................................................................................
Version 6.3.2e NOTE: This software conforms to the Fibre Channel (FC) standards and accepted engineering practices and procedures. Description Fabric OS 6.3.2e is a patch release based on Fabric OS 6.3.2. All hardware platforms and features supported in Fabric OS 6.3.2 are also supported in version 6.3.2e. This release contains several fixes since the 6.3.2 release. Fabric OS 6.3.2a added a new CLI command as documented in the section titled (page 33) in these release notes.
• Addition of Class 3 frame transmit timeout discard counter support for 4Gb platforms. Previously, 4Gb platforms supported only receive (Rx) timeout counters. See the Fabric Watch Administrator's Guide for details on use and configuration. • Addition of configurable "edge hold time" option to timeout frames for F_Ports sooner than for E_Ports.
Prioritization and Ingress Rate Limiting features are the first components of this license and are available on all 8Gb platforms. • Integrated Routing license—Allows ports on a DC SAN Backbone Director, DC04 SAN Director, 1606 Extension SAN Switch, HP 8/80 SAN Switch, or HP 8/40 SAN Switch to be configured as EX_Ports, supporting FCR.
increased element management functionality and management task aggregation throughout the environment. This license is used in conjunction with the DCFM application software. • 2408 FCoE Converged Network Switch FC Ports on Demand—This license enables all eight FC ports on the 2408 FCoE Converged Network Switch. IMPORTANT: Most 2408 FCoE Converged Network Switch units shipped with Fabric OS 6.1.2_cee1 did not include this license and must have it installed before upgrading to Fabric OS 6.3.0 or later.
Standards compliance This software conforms to the FC standards and accepted engineering practices and procedures. In certain cases, HP might add proprietary supplemental functions to those specified in the standards. For a list of standards conformance, see the HP website: http://www.hp.com. The 2408 FCoE Converged Network Switch and DC SAN Director Switch 10/24 FCoE Blade conform to the following Ethernet standards: • IEEE 802.1D, Spanning Tree Protocol (STP) • IEEE 802.
• HP 400 Multiprotocol Router (Brocade 7500) • HP Encryption SAN Switch (Brocade BES) • HP DC04 SAN Director (Brocade DCX-4S) • HP DC SAN Backbone Director (Brocade DCX) • HP SAN Director 16 Port 8Gb FC Blade (Brocade FC8-16) • HP SAN Director 32 Port 8Gb FC Blade (Brocade FC8-32) • HP SAN Director 48 Port 8Gb FC Blade (Brocade FC8-48) • HP SAN Director 6 Port 10Gb FC ISL Blade (Brocade FC10-6) • HP DC Switch Encryption FC Blade (Brocade FS8-18) • HP EVA4400 Embedded Switch Module (Brocad
Access Gateway connectivity is supported by the switches listed in this section and also by the following B-series switches: • HP 4/16 SAN Switch (Brocade 200e) • HP 4/32 SAN Switch • HP 4/32B SAN Switch • HP 4/64 SAN Switch • HP 4/256 SAN Director • Brocade 4Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012) • Brocade 4Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024) • HP 8/80 SAN Switch • HP DC SAN Backbone Director • HP DC04 SAN Director • HP 400 Multiprotocol Router •
NOTE: Do not configure zoning through a switch operating with Fabric OS 3.x in a fabric that has products operating with later versions of Fabric OS. Prerequisites Table 1 (page 13) lists the supported Fabric OS firmware versions. HP recommends using the latest supported firmware versions to get the greatest benefit from the SAN. For a list of retired products, see the HP website: http://www.hp.
Table 1 Supported Fabric OS versions Model Earliest compatible version Recommended version HP MSA SAN Switch 2/8 3.2.1c 3.2.
Table 1 Supported Fabric OS versions (continued) HP 8/80 SAN Switch HP Encryption SAN Switch 6.3.2d 7.0.1 HP 1606 Extension SAN Switch (Brocade 7800) 6.3.2d 7.0.1 HP 2408 FCoE Converged Network Switch (Brocade 6.3.2d 8000) 7.0.1 HP DC SAN Director Switch 10/24 FCoE Blade (Brocade FCOE10-24) 6.3.2d 7.0.1 HP DC SAN Director Multiprotocol Extension Blade (Brocade FX8-24) 6.3.2d 7.0.1 HP DC Switch Encryption FC Blade 6.3.2d Mi10k 7.0.1 3 M-EOS 9.9.5 M-EOS 9.9.8 or later3 10.4.0 10.4.5a 11.
Table 2 4/256 SAN Director blade support matrix Director blade Number of blades FC4-16 Supported with any mix, with up to eight blades of each type. No intermix restrictions. The 4/256 SAN Director must run Fabric OS 6.0.0b or later to support the FC8-16 port blade, and Fabric OS 6.1.0a or later to support the FC8-32 and FC8-48 port blades. FC4-32 FC4-48 FC8-16 FC8-32 FC8-48 FC10-6 FC4-16IP (iSCSI blade) Up to four blades of this type FR4-18i (FCIP/FC Router blade) Up to two blades of this type.
Table 4 Power supplies required for blades in Director chassis Director blade 4/256 SAN Director DC SAN Backbone Director and DC04 SAN Director FC4-16 Two power supplies Two power supplies1 Four power supplies Two power supplies2 Four power supplies Two power supplies. The FC4-16IP blades are not supported in the DC SAN Backbone Director or DC04 SAN Director.2 Not supported Two power supplies.
should be downgraded to a version of Fabric OS that does not recognize this new OUI. It is also important to note that specific minimum requirements for recognition of the new OUI will neither be validated nor enforced by Fabric OS. Impact of products with the new OUI to existing fabrics/environments In most situations, a switch that uses the new OUI can be seamlessly added to an existing fabric, even if the other switches in that fabric are not using Fabric OS versions that are aware of the new OUI value.
DCFM is available in three versions (see the DCFM release notes for full support details): • DCFM Professional—An application bundled with B-series switches that is ideally suited for small- and medium-size businesses that need a lightweight management product to manage their smaller fabrics (one physical fabric at a time, up to 1,000 ports).
Web Tools compatibility • Fabric OS 6.3 is supported with JRE 1.6.0 Update 13. • If the JRE 1.6.0 version is not Update 13, the DCFM server/client and B-series Element Manager (Web Tools) crashes on launch. • Web Tools tunnel and TCP graphs support tool tips only for the first enabled TCP connection graph. Fabric OS feature compatibility in native connectivity modes Some Fabric OS features are not fully supported when operating in the native connectivity modes for deployment with M-EOS-based products.
Table 5 Feature support in interopmodes 2 and 3 (continued) Adaptive Networking QoS No No Adaptive Networking: Ingress Rate Limiting No* No* Advanced Performance Monitoring (APM) No* No* APM: Top Talkers No* No* No No N/A N/A Fabric Watch Yes Yes Ports on Demand (POD) Yes Yes NPIV Yes Yes Timer Server Function (NTP) No No N/A N/A Broadcast Zoning No No FDMI No No Remote Switch No No Port Mirroring Yes Yes Extended Fabrics Yes Yes7 Alias Server No No Platform S
3 DPS is supported outbound from Fabric OS-based switches. M-EOS can provide reciprocal load balancing using Open Trunking. 4 SCC policies are supported only in conjunction with L2 Fabric Binding. 5 Not supported in Fabric OS 6.0 or later. 6 Mode 3 is qualified only with M-EOS switches. 7 Not on FCR. 8 Supported only locally on the Fabric OS switch. 9 All routers (EX_Ports) must reside in a backbone fabric running in interopmode 0 only.
Firmware upgrade instructions IMPORTANT: HP recommends that you upgrade to Fabric OS 6.3.2e as soon as possible to take advantage of the fixes and new features. Upgrading to Fabric OS 6.3.2e is allowed only from Fabric OS 6.2.x. For more guidelines, see Update recommendation . To access the latest Fabric OS 6.3.2e firmware, configuration files, and MIB files, see the HP website: http://www.hp.com/support/downloads On the website: 1. Under Storage, select Storage Networking. 2.
after the addition or deletion of the circuit. This allows the switch to adjust the internal routes to fully utilize the new bandwidth. • Switching modes between 10G and 1G is disruptive to FCIP traffic. • Keep Alive Timeout (ms). The valid range is 500 ms to 7,200,000 ms (inclusive). The default value is 10,000 ms (10 seconds). If FICON is configured, the recommended value is 1000 ms (1 second), otherwise the recommended value is the default of 10 seconds.
• Both ends of a tunnel must be identically configured for the Compression, FastWrite, and Tape Pipeline options. If a mismatch exists, the tunnel will not be established and the TCP virtual connections will be removed. • Under traffic isolation (TI) zone configurations with failover enabled, non-TI zone traffic will use the dedicated path if no other E or VE paths through the fabric exist, or if the nondedicated paths are not the shortest paths.
• HP recommends that Spanning Tree Protocol and its variants be disabled on CEE interfaces that are connected to a server. • The Fabric Provided MAC Address (FPMA) and Fibre Channel Identifier (FCID) assigned to a VN_Port cannot be associated with any front-end CEE port on which the FLOGI was received. • LLDP neighbor information may be released before the timer expires when DCBX is enabled on a CEE interface. This occurs only when the CEE interface state changes from active to any other state.
• When rebooting a DC SAN director or DC04 SAN director with DC SAN 10/24 FCoE blade, Qlogic CNA and LSAN zoning, the switch becomes unresponsive for a period of time. This is due to the CNA sending excessive MS queries to the switch. • A DC SAN 10/24 FCoE blade installed in the highest numbered slot of a DC SAN director or DC04 SAN director does not send out FIP unsolicited advertisements. Therefore, it does not support FCoE functionality when installed in this slot.
Director or DC04 SAN Director to other switches must come up after 6.0 is running on those switches. • Flow-based QoS is not supported on any 8-Gb Fibre Channel blades in the 4/256 SAN Director. • Any products that cannot operate with Fabric OS 6.x cannot exist in a fabric with flow-based QoS. Major problems occur if previous-generation 2-Gb products exist in the fabric. • QoS is supported on switches in Access Gateway mode with Fabric OS 6.3x and later.
Integrated routing • To allow HCL on an 8/40 SAN Switch when using Integrated Routing, the edge switch connected to the 8/40 SAN Switch must be running Fabric OS 6.1 or later. • Integrated Routing and Top Talkers cannot run concurrently in Fabric OS 6.3.x. To use Integrated Routing, be sure to disable Top Talkers before configuring EX_Ports.
FL_Port (loop) support • The 8-Gb 48-port Fibre Channel blade now supports the attachment of loop devices in the DC SAN Backbone Director and DC04 SAN Director. • VF must be enabled on the chassis, and loop devices can be attached only to ports on a 48-port blade assigned to a nondefault logical switch operating with the default 10-bit addressing mode. (Loop devices may not be in the default logical switch.
Zoning Beginning with Fabric OS 6.2.0, all WWNs containing uppercase characters are automatically converted to lowercase when associated with a zone alias and stored as part of a saved configuration on a switch. For example, a WWN entered as either AA.BB.CC.DD.EE.FF.GG.HH or aa.bb.cc.dd.ee.ff.gg.hh when associated with a zone alias will be stored as aa.bb.cc.dd.ee.ff.gg.hh on a switch operating with Fabric OS 6.2.0 or later.
When connecting to an extension device that does not support ARB primitives (such as some TDM products), the following configuration must be used: • portcfgqos -disable • portcfgcreditrecovery –disable • portcfglongdistance 0 The fabric parameter fabric.ops.mode.longdistance is now deprecated and should not be used. 8-Gb link initialization and fill words Overview The Fibre Channel Physical Interfaces (FC-PI) standard defines the requirements for a physical layer.
• Other scenarios The portCfgFillWord command has no effect on 1-Gb, 2-Gb, or 4-Gb devices, but the mode is persistent. If a device attempts to negotiate or is fixed at 8 Gb, the configured mode will take effect. The persistent configuration is on a port-by-port basis; that is, if an 8-Gb device is connected to a 2-Gb or 4-Gb SFP, and that SFP is replaced with an 8-Gb SFP, then the current behavior of the mode is activated. • The following table provides a portcfgfillword summary.
command are persistent, and will therefore remain at mode 1 after Fabric OS upgrade. to a version later than 6.3.1c does not affect the current mode settings. ◦ If a pre-6.2.0d version was installed in the factory, the default setting for all internal and external ports is mode 0. The setting can be changed by the user on a port-by-port basis and will be persistent. Upgrading to version 6.3.1a or later does not affect the current mode setting, with the exception of version 6.4.
issued. Fabric OS 6.3.1b and later now reclassifies these messages as warnings, rather than critical errors. • A new command has been introduced in Fabric OS 6.3.2a that allows configuration of the fault delay on individual ports. The command portCfgFaultDelay allows a port to be configured to a 1.2 second fault delay versus the default setting of R_A_TOV. ◦ NAME: portCfgFaultDelay - Configures the fault delay for a single FC port.
6.2.x to 6.3.2. Note that the following procedure is required only under the above-mentioned conditions. 1. Before the firmware upgrade, change the Failback Mode to manual for all containers configured as auto. Take note of which Encryption Engines currently own which containers. 2. Upgrade all nodes in the Encryption Group to Fabric OS 6.3.2, one node at a time. 3.
There is no outstanding zoning transaction 36 • Each LUN is uniquely identified by the HP Encryption Switch or HP Encryption Blade using the LUN’s serial number. The LUN serial numbers must be unique for LUNs exposed from the same target port. The LUN serial numbers must also be unique for LUNs belonging to different target ports in nonmultipathing configurations.
crypto operations or commands (except node initialization) being available on the member nodes after the power-cycle. This condition persists until the GL node is back online. ◦ Workaround. In the case of a data center power down, bring the GL node online first, before bringing the other member nodes online. In the event of the GL node failing to come back up, the GL node can be replaced with a new node.
• SKM is supported with Multiple Nodes and Dual SKM Key Vaults. Two-way certificate exchange is supported. See the Encryption Admin Guide for configuration information. If you are using dual SKMs on Encryption SAN Switch/Encryption FC blade Encryption Group, these SKM Appliances must be clustered. Failure to cluster will result in key creation failure. Otherwise, register only one SKM on the Encryption SAN Switch/Encryption FC blade Encryption Group.
EE Attributes: Link IP Addr : 10.32.50.36 Link GW IP Addr: 10.32.48.1 Link Net Mask : 255.255.240.0 Link MAC Addr : 00:05:1e:53:8a:86 Link MTU : 1500 Link State : UP Media Type : DISK System Card Label : System Card CID : Remote EE Reachability : Node WWN/Slot IO Link State 10:00:00:05:1e:53:77:80/0 10:00:00:05:1e:53:b7:ae/0 • EE IP Addr 10.32.53.107 10.32.53.
Documentation Updates This section provides information on last minute additions and corrections to the documentation. The most recent Fabric OS 6.3 documents are available on www.hp.com in the "manuals" section for switches that support that version of Fabric OS (the “manuals” section is accessible once you navigate to a particular switch). The updates noted in this section are in addition to those included in the previous Fabric OS 6.3.0x Release Notes.
Table 6 Fabric OS 6.3.2 closed defects Closed defect summary Solution A switch panic occurs during firmwaredownload with termination of msd Fixed in Fabric OS 6.3.2. (management server daemon). If a request was cancelled in the midst of processing, a race condition between two threads can occur, triggering an msd panic and hareboot/hafailover of switches. Observed in fabric with EOSc switch that ignores GMAL request.
Table 6 Fabric OS 6.3.2 closed defects (continued) Access Control Lists are not getting populated, even though the ACL Policies Workaround prior to upgrade: Use the are set on the switch. As a result, ACL related configuration is not possible CLI. through DCFM or other common access layer (CAL) interfaces, even though Fixed in Fabric OS 6.3.2. it can be done through the CLI. This issue affects only the HP 2408 FCoE switch and 10/24 FCoE blade.
Table 6 Fabric OS 6.3.2 closed defects (continued) Rolling asserts occur on 4/256 SAN Director with Multiprotocol Router blade, Workaround prior to upgrade: Disable or on 400 Multiprotocol Router when attempting to connect to an encryption the E_Port on the encryption switch to SAN switch via EX_Port. recover the switch. Fixed in Fabric OS 6.3.2. PLOGI ACC is dropped when there is back-to-back plogin to a well-known Fixed in Fabric OS 6.3.2. address such as msd, nsd, fabric controller, etc.
Table 6 Fabric OS 6.3.2 closed defects (continued) CALD terminated and logical switch delete failed with reason Could not Fixed in Fabric OS 6.3.2. get port details from EM when attempting to delete two of six logical switches in a DC SAN Backbone director from DCFM. In AG mode, N_Port failover results in F_Ports with attached hosts getting Fixed in Fabric OS 6.3.2. stuck as G_Ports.
Table 6 Fabric OS 6.3.2 closed defects (continued) In an encryption environment, tape devices intermittently show offline condition to the host. Observed in setup where some Physical Initiators do not register as FC4 type devices and some do. Fixed in Fabric OS 6.3.2. On 4Gb switches, when a frame comes into the embedded port and there Fixed in Fabric OS 6.3.2. is no memory to hold it temporarily, the switch panics. This is likely to happen when there are spurious interrupts from a device.
Table 7 Fabric OS 6.3.2a closed defects Closed defect summary Solution In a fabric containing the encryption switch and/or encryption blade, numerous weblinker termination and restart messages can be seen due to timeouts in handling multiple stats calls in parallel. Fixed in Fabric OS 6.3.2a. After doing a firmware upgrade or an hafailover on a 4/256 director with Fixed in Fabric OS 6.3.2a. 4Gb 48 port blade installed, the CP blade faults and traffic is disrupted.
Table 7 Fabric OS 6.3.2a closed defects (continued) on a primary shared area port after a secondary shared area F_Port goes though a route recalculation. Level of disruption varies from causing a SCSI abort, RTWR error, to hosts and targets losing the ability to communicate. Fabric gets into a mode where communications between the local switch and remote switch flow in only one direction, causing the remote switch to disable the local switch without any notification or reason being logged.
Table 8 Fabric OS 6.3.2b closed defects (continued) do not match, causing the command to fail and resulting in data corruption on the tape. The fans on an HP DC SAN Backbone Director Switch may erroneously be flagged as bad and get logged with a[PLAT-5042], FAN I2C reset error code in the Raslog, even though they are operating properly. Workaround prior to upgrade: Reseat the fans to allow them to recover from the faulty state. Fixed in Fabric OS 6.3.2b.
Table 8 Fabric OS 6.3.2b closed defects (continued) In an AG fabric, DXFM/FM/SMI proxy switch sends a GAGI request to Fixed in Fabric OS 6.3.2b. another switch in the fabric with Brocade_AG query. This sometimes triggers verify and floods the raslog, which may cause high CPU load and switch panic. With Virtual Fabrics (VF) enabled and Radius server configured, customers Fixed in Fabric OS 6.3.2b.
Table 9 Fabric OS 6.3.2c closed defects (continued) Closed defect summary Solution After upgrading a fabric switch from Fabric OS from 6.2.x to 6.3.x, the N_Port was stuck in G_Port when the fabric switch is attached to an Access Gateway switch with QoS enabled. Fixed in Fabric OS 6.3.2c. FAN frames are not being sent by the switch to loop devices after LIP when fcAL.fanFrameDisable is set to 0. Fixed in Fabric OS 6.3.2c.
Table 9 Fabric OS 6.3.2c closed defects (continued) Closed defect summary Solution There previously was no easy way to diagnose link level errors on backend Fixed in Fabric OS 6.3.2c. ports. This release includes a new diagnostic command, pterrshow, to display ASIC backend errors. Ports cannot negotiate at 8G speed on the following switches: Fixed in Fabric OS 6.3.2c.
Table 11 Fabric OS 6.3.2e closed defects (continued) Closed defect summary Solution Migration failures may occur between servers when a switch running in Fixed in Fabric OS 6.3.2e. Access Gateway mode does not clean up the fabric channel frame exchange properly. This occurs when a FLOGI/FDISC is received from different ports with same exchange ID (OX-ID).
