HP StorageWorks 2/32 HP StorageWorks Fabric OS 5.2.1b Release Notes (AA-RWEYC- - Page 12

Firmware upgrade/ downgrade Fabric OS - CU commands Distance mode FC Routing Security Diagnostics HA • When upgrading from Fabric OS 5.1.0x to 5.2.0x, if there are two or more inter-fabric links (IFLs) connected to an edge fabric, one IFL will stay online and the other IFLs will go online and offline. This will cause a temporary traffic disruption going from multiple IFLs to one IFL and then back to multiple IFLs. This is due to the new front domain consolidation feature in Fabric OS 5.2.0, where the IFLs connected to the same edge share the same front domain. • When downgrading from Fabric OS 5.2.0 to 5.1.x, FC traffic will be disrupted if there is front domain consolidation prior to the downgrade, even in the case of a single IFL. • Upon firmware download the FC4-16IP blade does not preserve disabled GE_Ports in disabled state. If you want to retain GE_Ports in a disabled state across firmware download, you must configure them as persistently disabled. • In a large fabric with a large zoning database (for example, 2560 ports with a 1 MB zoning database), a non-disruptive firmware download on a Brocade 3850 or 3900 can result in an E_port offline transition. The E_Port offline transition causes a fabric reconfiguration and can cause momentary frame loss. The 4 Gb/s switches do not experience this issue. • FCIP traffic is disrupted in an upgrade from Fabric OS 5.2.0a to Fabric OS 5.2.0b. • The slotOff and slotOn commands are now obsolete; use slotPowerOff and slotPowerOn instead. The portLogPortShow command is also now obsolete. • The QuickLoop feature and related commands are no longer supported on Fabric OS versions 5.1.0 and later. Distance setting is not persistent. After a configuration uploads and downloads, distance settings are lost and the desired distance is shown as 0. • If an HP StorageWorks MP Router is present in the backbone fabric, the command fcrDisable may take up to 8 minutes to complete. If the MP Router is replaced by a B-Series MP Router blade (FR4-18i) or an HP StorageWorks 400 MP Router, the command completes immediately. • EX_Port trunking is not enabled by default. • Fabric OS 5.2.0 introduces the EX_Port trunking feature. This feature should be enabled only if the entire configuration is running Fabric OS 5.2.0 or later. Enabling the EX_port trunking feature on a switch running Fabric OS 5.2.0 or later in a configuration containing a Fabric OS 5.1.0 switch causes the Fabric OS 5.1.0 switch to panic. • When an unstable edge fabric that has multiple EX_Port connections is in a transitional state, on rare occasions one of the EX_Ports may detect a FID conflict and be disabled. If this occurs, manually re-enable the port. Remove any password enforced expiration of admin or root accounts before downgrading firmware to 5.0.1 or earlier versions. • All offline diagnostics commands should be used only when the switch is disabled. • POST can fail if new SFPs are added during POST. SFPs should be added only while the switch is online or if the switch is powered off. • When you use the diagnostic commands systemVerification and diagSetBurnin, the switch or blade faults when the burn-in error log is full. Clear the burn-in log before running systemVerification or diagSetBurnin. • If there are ISLs present on the switch that are not used for routing because they have higher link costs, disable the links before running spinfab. If there is an already segmented port and backbone devices are exported to an edge fabric, a build fabric/fabric reconfiguration can occur after running haFailover. Ensure that there are no segmented ports before upgrading firmware. 12