HP StorageWorks Multi-protocol Router XPath OS 7.4.
Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L.P. © Copyright 2004, 2007 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.1d. Supersedes history This version supersedes XPath OS 7.4.1c released in December 2006. Effective date March 2007 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.1d. Table 2 XPath OS 7.4.1d 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.5c 2.6.2d 3.2.1b 5.2.0b, 5.1.1a 5.2.0b, 5.1.1a 5.2.
Fixes Table 3 lists critical or high level issues resolved in XPath OS 7.4.1d firmware. Table 3 Resolved issues in XPath OS 7.4.1d firmware Issue Description Name Server client (NSCL) APIs hang while querying for symbolic names. When an F-port is connected remotely, the symbolic name for the port is unavailable. Multi-protocol Router panic, core files are truncated. Core files are created, but truncated due to a lack of file space. A new CLI command has been created.
Table 4 MP Router port modes Mode Port type Fibre Channel EX_Port or U_port (E_Port or F_Port) GbE with FCIP or iSCSI IP port Table 5 MP Router port types functions Port type Function EX_Port Connecting one or more edge fabrics to an MP Router. IP Port Connecting to a GbE network when using FCIP tunneling or iSCSI bridging. U_Port (E_Port) Connecting two or more MP Routers together in a router backbone fabric.
NOTE: If an E_Port connection is inadvertently created to the router from an edge fabric, disconnect the cable, stop the port on the router (as described above), and remove all configuration and zoning from the router (if necessary). If the connection was meant to be an EX_Port, then create it on the router, reconnect the cable, and restart the port. Important information This section describes important information and important notes for the XPath OS 7.4.1c release.
Issue Description Meta-SAN traffic In a non-routed SAN, if there are multiple E_Port links between two switches and fabric reconfigurations occur due to the loss of a single E_Port link, then traffic around the fabric is generally not interrupted (or is interrupted for a very short time: for example, less than one second).
Issue Description Multiple FCIP Links not supported with Continuous Access EVA or HSG80 DRM Support for multiple FCIP Links between locations was added in XPath 7.0.3b. This feature is supported with Continuous Access XP only. FCIP with Continuous Access XP All Continuous Access XP configurations using the MP Router require a minimum of 45 Mbps IP bandwidth. FCIP and firewalls The Multi-protocol Router uses XPP as the transport layer for FCIP transmission.
Table 8 iSCSI Gateway service Releasing the IP address for a GbE port Releasing the IP address of a Multiprotocol Router Gigabit Ethernet port requires setting the IP address of the port to 0.0.0.0. For example: portcfgGbE 15 -i 0.0.0.0 Upon releasing the IP address, the address can be used by other ports. iSCSI Gateway Service support The MP Router provides iSCSI support allowing iSCSI Initiators to access Fibre Channel based storage subsystems.
Issue Description GNU telnet client GNU telnet client sessions on certain workstations (for example, Sun Solaris) will be disconnected from XPath OS upon pressing Ctrl-C twice in succession. This is in contrast to B-Series Fabric OS, on which the same telnet client and the same key sequence does not cause a session disconnect. GNU telnet clients used with the UNIX® tee utility might be disconnected unexpectedly as well. Workaround: Use /usr/bin/telnet instead of /usr/gnu/bin/telnet.
Issue Description SFP media support The MP Router supports only qualified SFP media. A list of the qualified SFPs is available by running the sfpSupport command. Duplicate domain IDs When manually setting domain IDs, avoid duplicates. Under Fabric OS, when duplicate domain IDs are detected, fabrics are segmented. XPath OS handles duplicate domain IDs differently, resulting in repeated failed attempts to merge fabrics. This note does not apply to Fibre Channel Routing Services EX_Ports.
Issue Description Fibre Channel Class XPath OS supports only Fibre Channel Class 3. Testing has shown that Class 2 devices attached to and supported by Fabric OS-based platforms communicate properly through FC-FC routing services on XPath OS 7.30b and are supported. N[L]_Port devices that are connected directly to the MP Router and cannot automatically or manually accept the F_Port’s request for Fibre Channel Class 3 are affected.
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.3.0 xpath_rk_1.4.1 xpath_os_v7.4.0 xpath_rk_1.5.2 xpath_os_v7.4.1 xpath_rk_1.5.
