Page of 48

HP 4400 Release Note

Hp storageworks fabric os 6.2.2e release notes (5697-0809, february 2011 - includes all 6.2.2x versions).
Hide thumbs
HP Fabric OS 6.2.2e Release Notes
HP Part Number: 5697-0809
Published: February 201 1
Edition: First

Advertising

   Also See for HP 4400

   Related Manuals for HP 4400

   Summary of Contents for HP 4400

  • Page 1

    HP Fabric OS 6.2.2e Release Notes HP Part Number: 5697-0809 Published: February 201 1 Edition: First...

  • Page 2

    © Copyright 201 1 Hewlett-Packard Development Company, L.P. © Copyright 201 1 Brocade Communications Systems, Incorporated...

  • Page 3

    Version 6.2.2e NOTE: This software conforms to the Fibre Channel (FC) standards and accepted engineering practices and procedures. Description Fabric OS 6.2.0b introduced support for the HP StorageWorks Encryption SAN Switch and the HP DC Switch Encryption FC Blade. Fabric OS 6.2.2e continues this support. These products provide the following features: Data encryption support for B-series fabrics Key management support for HP Secure Key Manager (SKM)

  • Page 4

    Security enhancements IPv6 auto-configuration ◦ IPsec with IPv6 (for management port) ◦ Configurable switch-wide policy requiring authentication of all host bus adapters (HBAs) ◦ ◦ Remote Authentication Dial-In User Service (RADIUS) enhancements allowing password expiration and source IP address information LDAP enhancement allowing for an alternate domain userPrincipalName (UPN) ◦...

  • Page 5

    Supersedes Fabric OS 6.2.2d, released October 2010 New feature descriptions This section describes new features introduced in Fabric OS 6.2.0a and carried forward with Fabric OS 6.2.2e. Virtual Fabrics VF is supported on the HP StorageWorks DC SAN Backbone Director, DC04 SAN Director, HP StorageWorks 8/80 SAN Switch, and HP StorageWorks 8/40 SAN Switch.

  • Page 6

    NOTE: For information on specific switches and switch firmware supported for interop applications, see the HP StorageWorks Fabric Interoperability: Merging Fabrics Based on M-series and B-series Fibre Channel Switches Application Notes. Security enhancements Configurable stateless IPv6 auto-configuration is supported. IPsec with IPv6 support provides greater security for management ports and configurable security policies for IPv4/IPv6 addresses.

  • Page 7

    Optionally licensed software The following are optionally licensed features in Fabric OS 6.2.x: Ports on Demand—Allows customers to instantly scale the fabric by provisioning additional ports via a license key upgrade (applies to select switch models). Extended Fabrics—Provides greater than 10 km of switched fabric connectivity at full bandwidth over long distances.

  • Page 8: Standards Compliance

    Temporary license support HP now supports temporary licenses or Universal Temporary Licenses. To obtain the Universal Temporary Licenses, select the StorageWorks Software Demo & Evaluation Downloads option at the HP website: http://www.software.hp.com Previously licensed software now included with base Fabric OS The capabilities described in this section are included as part of the base Fabric OS.

  • Page 9: Operating Systems

    HP StorageWorks 16 Port 4-Gb Blade (FC4- 1 6) HP StorageWorks 32 Port 4-Gb Blade (FC4-32) HP StorageWorks 4/48 SAN Director Blade (FC4-48) HP StorageWorks Multi-Protocol Router Blade (Brocade FR4- 1 8i) HP StorageWorks iSCSI Director Blade (Brocade FC4- 1 6IP), compatible with the 4/256 SAN Director model only (not supported in the DC SAN Backbone Director or DC04 SAN Director) HP StorageWorks 8/8 and 8/24 SAN Switches (Brocade 300) HP StorageWorks 8/40 SAN Switch (Brocade 5100)

  • Page 10

    HP StorageWorks 8/24 SAN Switch (Brocade 300) HP StorageWorks 8/40 SAN Switch (Brocade 5100) IMPORTANT: Although the HP StorageWorks 4/8 SAN Switch uses the same hardware as the 4/16 SAN Switch, it does not support Access Gateway. The same applies to the HP StorageWorks 8/8 and 8/24 SAN Switches.

  • Page 11

    Cisco switches: MDS 9216, MDS 9216A, MDS 9506, MDS 9509 running SAN OS 3.0(2a) with Brocade Fabric OS 6.1.0x Cisco switches: MDS 9216, MDS 9216A, MDS 9216i, MDS 9506, MDS 9509, MDS 9120, MDS 9140, MDS 9124, MDS 9134 running SAN OS 3.2(3) with Brocade Fabric OS 6.2.0x, 6.2.1x, and 6.2.2x Secure Fabric OS feature not compatible with Fabric OS 6.x and later Fabric OS 5.3.x is the last Fabric OS version compatible with SFOS.

  • Page 12

    Table 1 Supported Fabric OS versions (continued) Model Earliest compatible version Recommended version HP StorageWorks 4/8 SAN Switch 6.2.1b 6.2.2e HP StorageWorks 4/16 SAN Switch HP StorageWorks 4/256 SAN Director 6.2.1b 6.4.1a HP StorageWorks 4/64 SAN Switch HP StorageWorks Multi-Protocol Router Blade (FR4- 1 8i) HP StorageWorks 16 Port 4-Gb Blade (FC4- 1 6) HP StorageWorks 32 Port 4-Gb Blade (FC4-32)

  • Page 13

    Table notes: In a fabric with products running older versions of Fabric OS, all zoning and fabric operations must be performed using interfaces to products running the latest version of Fabric OS. This is important for Brocade 3xxx series switches that do not support zoning configuration for newer products.

  • Page 14

    DC SAN Backbone and DC04 SAN Director blade support Fabric OS 6.2.2e is fully qualified and supports the DC Director blades listed in Table 3 (page 14). Table 3 DC Director blade support matrix Director blade Number of blades FC8- 1 6 Supported with Fabric OS 6.0.0b or later with any mix, with up to eight blades of each type on the DC SAN Backbone Director.

  • Page 15: Important Notes

    Table 4 Power supplies required for blades in director chassis (continued) DC SAN Backbone Director and DC04 SAN Director Director blade 4/256 SAN Director FR4- 1 8i (FCIP/FC Router blade) Four power supplies Two power supplies. The FC4- 1 6IP blades are not supported in the DC SAN Backbone Director FC4- 1 6IP (iSCSI blade) and DC04 SAN Director.

  • Page 16

    OUI value. However, there are some exceptions and limitations to consider before adding a switch utilizing the new OUI to an existing fabric or environment. Fabrics with encryption products: If an HP StorageWorks encryption switch or blade using the new OUI is added to an edge fabric of a Fibre Channel routed fabric, Frame Redirection capability could be impacted across the FCR backbone, thus impacting the encryption functionality.

  • Page 17

    When using either the HP StorageWorks Encryption SAN Switch or the HP StorageWorks DC Switch Encryption FC Blade, switches attached to hosts and targets, or switches that are part of the encryption flow, must operate with the following minimum levels: 2-Gb platforms must operate with Fabric OS 5.3.2b or later.

  • Page 18

    Table 5 Feature support in interopmodes 2 and 3 (continued) Fabric OS Features (supported in interopmode 0) Fabric OS 6.2.2e IM = interopmode IM 2 IM 3 Advanced Performance Monitoring (APM) APM: Top Talkers Admin Domains Secure Fabric OS Fabric Watch Ports on Demand (POD) NPIV Timer Server Function (NTP)

  • Page 19: Firmware Upgrades And Downgrades

    SCC policies supported only in conjunction with L2 Fabric Binding support. Not supported in Fabric OS 6.0 or later. Mode 3 qualified only with M-EOS switches. Not on FCR. Supported only locally within the Fabric OS switch. All routers (EX_Ports) must reside in a backbone fabric running in interopmode 0 only. Only edge fabrics with devices imported to the backbone fabric or other edge fabrics can operate in IM 2 or IM 3.

  • Page 20: Ficon Support

    The HP StorageWorks DC SAN Director with HP StorageWorks DC Switch Encryption FC Blade and the HP StorageWorks Encryption SAN Switch cannot be downgraded to a version earlier than Fabric OS 6.2.0b. After upgrading the Encryption SAN Switch and the DC SAN Director with DC Switch Encryption FC Blade to Fabric OS 6.2.2e, you cannot downgrade them to a version earlier than Fabric OS 6.2.0d if HP SKM key vault is configured.

  • Page 21

    Other important notes and recommendations This section contains additional information that you should consider before you use this Fabric OS release. Virtual Fabrics On VF-capable platforms, the VF feature must be enabled after upgrading to Fabric OS 6.2.x in order to utilize the related capabilities, including Logical Switches and Logical Fabrics. When creating Logical Fabrics that include switches that are not VF-capable, it is possible to have two Logical Switches with different FIDs in the same fabric.

  • Page 22

    distance configuration for these ports or explicitly disabling QoS on other ports, freeing up buffers for the last four ports. With the Fabric OS 6.2.1 and later firmware upgrade, the default behavior of the Adaptive Networking QoS feature changes as follows: ◦...

  • Page 23: Access Gateway, Port Mirroring

    Access gateway When in Access Gateway (AG) mode, the Automatic Port Configuration policy may not work when attached to M-EOS switches. M-EOS ports should be set to G_Port to prevent problems with port type discovery. FCS Automatic Distribution When using the FCS Automatic Distribution feature in Fabric OS 6.0 or later, all switches in the fabric must be running Fabric OS 6.0 or later.

  • Page 24

    port, Source Device, and Destination Device or ISL, if the Destination Device is located on another switch. The ASIC port groups are 0- 1 5, 16-31, 32-47, 48-63, and 64-79. The routes will be broken if the port mirror resources are spread across multiple port groups. Port Mirroring is not supported on a switch with the VF feature enabled.

  • Page 25

    errors; that is, the next time the user-set threshold level (or default threshold level) is reached. This prevents a port from being disabled due to normal link transition behaviors. When using the Port Fencing feature, you must first run the fwalarmsfilterset command. This command enables the port and allows you to receive Port Fencing messages.

  • Page 26

    Overview The FC Physical Interfaces (FC-PI) standard defines the requirements for a physical layer. It considers all aspects of transmit, receive, and cable-plant performance requirements for optical and electrical links. The FC-PI standard has been modified to support new physical-layer variants that operate at higher data rates than those specified in FC-PI-2.

  • Page 27

    With Fabric OS 6.1.2x and 6.2.0d and later, the default reverted to the IDLE implementation. The new portCfgFillWord command was also implemented beginning with these versions, and enables the user to configure the ARB(FF) configuration. ◦ Existing product For products in the field, this change has no effect on current configurations. The mode is currently 0, and during a firmware upgrade, the mode will remain 0 and no devices will be impacted.

  • Page 28

    All 8-Gb switches except 8-Gb SAN 8-Gb SAN Switch for HP BladeSystem Fabric OS version Switch for HP BladeSystem c-Class c-Class Fabric OS 6.1.2x and Regardless of the Fabric OS version that – If Fabric OS 6.2.0d was 6.2.0d through 6.2.x was previously installed, all ports default factory-installed, all internal ports to IDLE [mode 0].

  • Page 29

    Table 7 Web Tools functionality in DCFM (continued) Function Web Tools 6.1.0 DCFM Device accessibility matrix Zone Admin Configure > Zoning The Compare dialog provides the Storage-Host and Host-Storage view in a tree representation that is comparable to the Device Accessibility Matrix when all devices are selected.

  • Page 30

    exceed 25 LUNs will fail with a warning. Note that there is also a five-second delay before the commit operation takes effect. Always ensure that any previously committed LUN configurations or LUN modifications have taken effect before committing additional LUN configurations or additions. All LUNs should be in an Encryption Enabled state before committing additional LUN modifications.

  • Page 31

    When creating an HA Cluster or EG with two or more HP encryption switch/encryption blades, the GE_Ports (I/O sync links) must be configured with an IP address for the eth0 and eth1 Ethernet interfaces using ipaddrset. In addition, both eth0 and eth1 Ethernet ports should be connected to the network for redundancy.

  • Page 32

    If writes are done to a LUN that is undergoing first time encryption or rekeying, you may see failed I/Os. HP recommends that host I/O operations are quiesced and not started again until rekey operations or first time encryption operations for the LUN are complete. When all nodes in an EG (HA Cluster or DEK Cluster) are powered down (due to catastrophic disaster or a power outage to the data center) and later nodes come back online (in the event of the Group Leader (GL) node failing to come back up or the GL node being kept powered...

  • Page 33

    Relative to the HP Encryption switch and HP Encryption blade, all nodes in the Encryption Group must be at the same firmware level before starting a rekey or First Time Encryption operation. Make sure that existing rekey or First Time Encryption operations complete before upgrading any of the encryption products in the Encryption Group.

  • Page 34

    Table 8 Fabric OS 6.2.1 closed defects Closed defect summary Solution Sshd allows admin login to execute root-level Linux commands, but admin Fixed in Fabric OS 6.2.1 CLI commands fail with a command not found error. Workaround prior to update: A workaround to facilitate execution of admin level CLI commands using ssh, is to use syntax similar to ssh -l admin...

  • Page 35

    Table 8 Fabric OS 6.2.1 closed defects (continued) Closed defect summary Solution The following SNMP-related issues exist in code: Fixed in Fabric OS 6.2.1 The cpLastEvent value is shown incorrectly in the browser. The cpStatusChange trap is not sent to the trap recipients. There is an incompatibility with client using older MIBs (pre-Fabric OS 6.2.0 MIB).

  • Page 36

    Table 8 Fabric OS 6.2.1 closed defects (continued) Closed defect summary Solution In an FCR environment (with a router or switch configured for FCR), a switch Fixed in Fabric OS 6.2.1 runs out of memory when it is connected with the Mi10k. The Mi10k sends continuous RRQ frames because the Fabric OS-based switch did not handle RRQ frames with either accept or reject.

  • Page 37

    Table 8 Fabric OS 6.2.1 closed defects (continued) Closed defect summary Solution HP StorageWorks DC SAN Director temperature sensor reported spurious Fixed in Fabric OS 6.2.1 readings leading to the CRITICAL HIL-1502 message without having Workaround prior to update: Ignore first issued the HIL-1501 warning.

  • Page 38

    Table 9 Fabric OS 6.2.1a closed defects (continued) HP StorageWorks DC SAN Director panics due to termination of msd during Fixed in Fabric OS 6.2.1a fabric reconfiguration while doing switchdisable, agshow, switchenable loop, in a fabric with an Access Gateway device with more than 56 switches.

  • Page 39

    Table 1 1 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution Numerous Reliable Transport Write and Read errors (RTWR) observed when Fixed in Fabric OS 6.2.2 going to translate domain. Switch-to-switch NameServer frames are intended for the LE domain but use any valid F/E-port instead of using the LE port ID.

  • Page 40

    Table 1 1 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution A switch panic occurs due to third-party management application giving Fixed in Fabric OS 6.2.2 bad response or no response to FCP LUN request. SwNs table lists one fewer name server entry than the actual number of Fixed in Fabric OS 6.2.2 devices (first entry shown in nsallshow CLI command) The urouteshow command lags for several seconds while displaying the...

  • Page 41

    Table 1 1 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution When running the Zone admin, with 48 port blade where there is port Fixed in Fabric OS 6.2.2 address sharing, devices show up on the wrong port. When port index and port address of the given port is different, end device will be seen connected to a different port (U port) than the original one (F_Port).

  • Page 42

    Table 1 1 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution When port 254 is used in directors in non-FICON setup, after multiple Fixed in Fabric OS 6.2.2 hafailovers, port 254 may lose its name server entry, and/or CP reports Workaround prior to update: Reboot a synchronization error while overall system HA maintains sync.

  • Page 43

    Table 12 Fabric OS 6.2.2a closed defects (continued) Closed defect summary Solution While running Fabric OS 6.2.2, the switch can panic after executing a Fixed in Fabric OS 6.2.2a fcplunquery or iscsicfg CLI command for the target entity on HP StorageWorks iSCSI Director Blade.

  • Page 44

    Table 13 Fabric OS 6.2.2b closed defects (continued) Closed defect summary Solution In a very rare circumstance, a configuration file for dynamic area mapping Fixed in Fabric OS 6.2.2b gets corrupted after firmwarecommit, leading to both CPs failing and Workaround prior to update: Remove the switch not booting up.

  • Page 45

    Table 14 Fabric OS 6.2.2c closed defects Closed defect summary Solution 8 Gb Directors with an 8 Gb blade in slot 1 or 8 Gb Fixed in Fabric OS 6.2.2c. switches can see a frame drop in the fabric when Workaround prior to update: Ex/VEx ports are configured in the same ASIC as an Avoid configuring an EX_Port or a VEx_Port near an F/E_Port...

  • Page 46

    Table 14 Fabric OS 6.2.2c closed defects (continued) Closed defect summary Solution On B-series 4 Gb switches, multiple critical level With Fabric OS v6.2.2c, this specific occurrence of CDR- 1 003 CDR- 1 003 raslog entries seen during is updated to log as a warning rather than critical. It can be supportsave after non-disruptive upgrade from FOS safely ignored unless it becomes persistent, or does not happen during supportsave.

  • Page 47

    Table 15 Fabric OS 6.2.2d closed defects (continued) Closed defect summary Solution After upgrading to FOS 6.2.x firmware on 4 Gb Fixed in Fabric OS 6.2.2d. switches, critical messages (CDR- 1 003) are posted to Workaround prior to update: the RASLOG when a SupportSave operation is Customers can ignore the CDR- 1 003 critical messages logged executed.

  • Page 48

    Table 16 Fabric OS 6.2.2e closed defects (continued) Closed defect summary Solution A switch panic occurs when a management Fixed in Fabric OS 6.2.2e. application polls for Access Gateway device information or when agshow command is executed. WARNING raslog messages of "[CDR- 1 003]" Fixed in Fabric OS 6.2.2e.

This manual also for:

Fabric os 6.2.2e

Comments to this Manuals

Symbols: 0
Latest comments: