HP StorageWorks Multi-protocol Router XPath OS 7.4.
Legal and notice information © Copyright 2006 Hewlett-Packard Development Company, L.P. © Copyright 2004-2006 Brocade Communications Systems, Incorporated The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Description These release notes contain information about installing, operating, and maintaining the HP StorageWorks Multi-protocol (MP) router running XPath OS 7.4.1c. Supersedes history This version supersedes XPath OS 7.4.1b released in October 2006. Effective date December 2006 Update recommendation Routine Product compatibility Table 1 lists compatible HP MP Routers and transceivers.
Devices supported Table 2 summarizes the B-Series Fibre Channel switch models and firmware versions that are supported with XPath OS 7.4.1c. Table 2 XPath OS 7.4.1c supported B-Series switches and firmware Versions Brocade 4Gb SAN Switch for HP c-Class and p-Class Blade Systems B-Series 1Gb/s switches 2/8, 2/8-EL, 2/16, 2/16-EL 2/8V, 2/16V, 2/16N, 2/32, 2/128 4/8, 4/16, 4/32, 4/64, 4/256 Fabric Manager1 HP recommended Versions 5.0.5b 2.6.2d 3.2.1b 5.2.0a 5.2.0a 5.2.
Fixes Table 3 lists critical or high level issues resolved in XPath OS 7.4.1c firmware. Table 3 Resolved issues in XPath OS 7.4.1c firmware Issue Description FCIP tunnel may not synchronize. The fcipshow command always indicates "Time sync state:: not synchronized". MP Router panics, then reboots. The FCR daemon "iswitchd" may experience a segmentation fault. MP Router panics, then reboots. The MP Router panics and reboots after continual access using SMI-S.
IMPORTANT: U_Port/E_Port connections are supported between two or more routers only for the purpose of creating a router backbone fabric. If an E_Port connection is made from an MP Router to an edge fabric, you must remove the edge fabric configuration and zone settings from the router as the edge fabric configurations and zone settings would propagate to the router when connected. You must use the EX_Port type when connecting edge fabrics to an MP Router.
Table 6 Fibre Channel routing services Issue Description Unexpected LSAN Zone Update messages or unexpected physical device offline messages These messages can occur during normal operation. However, if the MP Router reports numerous occurrences that cannot be correlated to actual initiated events, such as planned device reconfigurations or reboots, examine low-level port error counts using the portstatsshow command.
Issue Description Edge fabric switch booting and EX_Ports Certain configuration values and versions of Fabric OS switches in edge fabrics might cause EX_Ports on the Router to be disabled when the switches are rebooted. Evidence of the unexpected disabled EX_Port can be seen in the Router’s port display: # switchshow : 7 id AN No_Light disabled EX_PORT (Last error: Failed to init in time) Workaround for switches running FOS 3.x /4.
Issue Description FCIP and firewalls The Multi-protocol Router uses XPP as the transport layer for FCIP transmission. When a firewall is in the path of the FCIP tunnel, the firewall must be configured to allow protocol type 206 in the IP header. The purpose of this protocol type is to establish a connection and enable the FCIP traffic that traverses the firewall. FCIP link The FCIP selective acknowledgement feature was added in a previous version of firmware.
Table 9 XPath OS Base Operating System and Fibre Channel Service Issue Description The configdownload command does not restore the previously saved configuration. When using the configdownload command to restore a previously saved configuration, translate (xlate) domains may not restore properly when the xlate domains were created manually. To resolve this: 1. Identify the xlate domains that were created previously.
Issue Description Fibre Channel Layer 2 fabric parameter management It is not possible to manage the following fabric parameters from Advanced Web Tools: • RA_TOV • ED_TOV • RSCN_Mode These parameters can be managed from the CLI. NVRAM-related cleanup XPath 7.3.0b or later explicitly checks for NVRAM corruption that might have occurred during use of earlier XPath releases. It also provides a utility for cleaning the corruption.
Issue Description Fabric OS Web Tools vs. XPath OS Web Tools The Fabric OS implementation of Web Tools is different from the XPath OS implementation of Web Tools. The Fabric OS Web Tools application runs entirely on the Fabric OS switch while presenting an HTML interface to the client browser. XPath OS Web Tools is implemented with Java™ objects running as plug-ins on the client browser.
Issue Description Name Server and Zone Server database sizes The Name Server and Zone Server databases support fabrics within (and actually far larger than) the scalability guidelines. Fabric and zone merge attempts with fabrics beyond the scalability limits presented in this document will prevent fabrics from merging.
XPath OS migration procedures The XPath OS migration procedures are described in the HP StorageWorks XPath OS administrator guide. Refer to this guide for explicit instructions on upgrading or downgrading your XPath OS. Table 12 lists the XPath OS file and its associated recovery kernel file for each firmware version. Table 12 XPath OS file and recovery version XPath OS File Recovery Kernel (rk) File xpath_os_v7.4.1 xpath_rk_1.5.2 xpath_os_v7.4.1b xpath_rk_v1.5.2 xpath_os_v7.4.1c xpath_rk_v1.5.
