Release Notes hp StorageWorks SAN Switch 2/16 Fabric OS 3.1.2 Fifth Edition (April 2004) Part Number: AA–RR85E–TE This document contains last-minute and supplemental information about Fabric OS version 3.1.2 firmware for the HP StorageWorks SAN Switch 2/16. In the event of conflicting information between these Release Notes and other documents in this product release, the Release Notes take precedence. For the latest version of these Release Notes and other Fabric OS v3.1.
© Copyright 2004 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
About This Document About This Document This section identifies the audience of these Release Notes and provides a high-level description of the information it contains. Release Notes Information These Release Notes discuss the following major topics: ■ About This Document, page 3 ■ Standards Compliance, page 6 ■ Important Notes, page 7 ■ Fabric OS v3.1.2 Important Notes, page 11 ■ New Command in v3.1.2, page 12 ■ Commands Modified in v3.1.
About This Document Improvements The following improvements have been made to the Fabric OS software since the last HP StorageWorks Fabric OS version 3.1.1c release: ■ Secure Telnet may now be connected with two LAN cards. ■ Improvements have been made to the reboot code. ■ An increased number of HBAs can be displayed by Web Tools. ■ Improved firmware download reliability in an active fabric. ■ Web Tools events now use adjusted timezone time, rather than coordinated universal time (UTC).
About This Document Documentation This section discusses documentation associated with the Fabric OS v3.1.2. Additional Fabric OS v3.1.2 Documentation Additional documentation, including white papers and best practices documents, is available at the HP web site: http://welcome.hp.com/country/us/eng/prodserv/storage.html. Note: HP has made every effort to provide you with the most up-to-date Web retrieval procedures available at time of print. Note, however, that Web page links are subject to change.
Standards Compliance Standards Compliance HP products conform to Fibre Channel standards in a manner consistent with accepted engineering practices and procedures. In certain cases, HP may add proprietary supplemental functions to those specified in the standards. We verify conformance with Fibre Channel Standards by subjecting our switches to SANmark Conformance Tests developed by the Fibre Channel Industry Association. Our switches have earned the SANmark logo indicating such conformance.
Important Notes Important Notes This section provides information you should be aware of when running Fabric OS v3.1.2. OS Requirements HP recommends using the latest software release versions to get the greatest benefit from the SAN. Mixed Fabric Environment with Different Switch Platforms Fabric OS v2.6.2, v3.1.2, and v4.2.x introduced a new switch PID format: Extended Edge PID (Format 2). Extended Edge PID is useful if you introduce a Fabric OS v4.2.
Important Notes Channel Switch (FCS), as the location to perform zoning tasks, and as the time server. HP also recommends that you use the most recently released firmware to control the fabric. Two-Domain and Four-Domain Fabric Licensing If your fabric includes a switch with a license for a limited number of switches in the fabric and the fabric exceeds the limit, Advanced Web Tools allows a 45-day grace period during which you can still monitor the switch.
Important Notes Browser, OS, and Java Plug-in Support Advanced Web Tools browser, operating system, and Java Plug-in support is updated for Fabric OS v3.1.2. Table 1 identifies the supported browsers, operating systems, and Java Plug-ins for this release. Go to the http://hp.com web site for the latest list of supported operating systems. Table 1: Browsers, OSs, and Java Plug-ins Operating System Browser Java Plug-in HP-UX 11.00 Mozilla 1.4 or later 1.4.2_00 or later (up to but not including 1.
Important Notes Table 2: Limitations Using Mixed OS Versions Launch Switch Environment Issue and Workaround Firmware: Version earlier than Fabric OS v3.1.2 Operating System: Solaris Browser: Mozilla When accessing the Switch Admn, Zoning, Fabric Watch or High Availability Admin, the browser may crash. Workaround: If you must access these options from a Solaris OS, use the Netscape browser (although not supported by Web Tools. Firmware: Version earlier than Fabric OS v3.1.
Fabric OS v3.1.2 Important Notes Fabric OS v3.1.2 Important Notes Table 3 lists important information you should be aware of regarding Fabric OS v3.1.2. Table 3: Fabric OS v3.1.2 Important Notes Area Description Fabric Watch, e-mail alert error message When enabling e-mail alerts in Fabric Watch and an event occurs, the message ErrLog: Error Level=3 [(null)] is captured to the system error log. This message is from SMTP and can be ignored. FARP requests Fabric OS v2.x and v3.
New Command in v3.1.2 New Command in v3.1.2 pathInfo Displays routing and statistics info along a path. Synopsis pathInfo [domain], source port] destination port] [,”-r”] Availability root admin Description The pathInfo command displays detailed routing information from a source port (or area) on the local switch to a destination port (or area) on another switch. This routing information describes the exact path that a user data stream takes to go from the source to the destination.
New Command in v3.1.2 For each hop, the routing information output includes the following: Hop The hop number (the local switch is hop 0. In Port The port (or area) from which the frames come. For hop 0, the source port. For a switch with blades, this is specified s the area number; otherwise, as the port number. Domain ID The domain ID of the switch. Name The name of the switch Out Port The output port that the frames take to reach the next hop.
New Command in v3.1.2 Basic Statistics Basic statistical report variables give an indication of ISL congestion along the path. They include the following: B/x Bytes per second. Txcrdz The time in milliseconds that the port has been prevented from transmitting frames due to lack of buffer-to-buffer credit. This is an indication of downstream congestion. Note that other commands (portShow, for example) may express this value in units other than milliseconds.
New Command in v3.1.2 The source route is expressed as a sequence of switches, a sequence of output ports (or areas), or a combination thereof. The next hop in the source route is described by either the output port (or area) to be used to reach the hop or the domain ID of the next hop.
New Command in v3.1.2 If no operands are specified, pathInfo displays a menu in which the following parameters can be provided: 16 max hops The maximum number of hops that the pathInfo frame is allowed to traverse. The default is 25. domain The ID of the destination domain. This is a mandatory parameter; there is no default. source port The port whose path to the destination domain is sought. It can be an F_Port or an E_Port. The embedded port (-1) is used by default.
New Command in v3.1.
New Command in v3.1.
Commands Modified in v3.1.2 See Also portStatsShow, switchShow Commands Modified in v3.1.2 The following commands have been modified in v3.1.2: ■ quietMode ■ switchShow quietMode This command sets and clears shell quiet mode. Synopsis quietMode [new mode] Availability All users (display) Admin (set and clear) Description This command affects the output displayed on the switch’s console (serial port or Telnet session).
Commands Modified in v3.1.2 Example The following example first displays the current mode and then enables quiet mode: sw5:admin> quietMode Quiet Mode is OFF sw5:admin> quietMode 1 Committing configuration...done. Quiet Mode is now ON switchShow The switchShow command now supports the –portcount option, which returns the number of ports on the switch. The syntax is: switchShow, “–portcount” 20 SAN Switch 2/16 Fabric OS 3.1.
Documentation Updates Documentation Updates Table 4 lists error messages that were not available during the release of the HP StorageWorks Diagnostics and System Error Messages Reference Guide. Table 4: Version 3.1.2 Error Messages Not Previously Available Severity & Message Probable Cause Recommended Action Critical DIAG-BADINT, 1 Port received an unexpected interrupt. This usually indicates an ASIC failure.
Documentation Updates Table 4: Version 3.1.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-CMBISRTO, 1 Critical DIAG-CMERRPTN, 1 Critical DIAG-CMERRTYPE, 1 Critical DIAG-CMICKSUM, 1 Critical DIAG-CMIDATA, 1 Critical DIAG-CMIINVCAP, 1 Critical DIAG-CMINOCAP, 1 Probable Cause Recommended Action The ASIC Central Memory SRAMs did not complete the BISR within the timeout period. This usually indicates an ASIC failure.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-CMISA1, 1 Critical DIAG-CMNOBUF, 1 Critical DIAG-DATA, 1 Critical DIAG-ERRSTAT (2LONG), 1 24 Probable Cause Recommended Action An attempt to send a CMI message from ASIC to ASIC failed. This usually indicates an ASIC failure. This message is generated by the cmitest command, if problems are found. For the SAN Switch 2/16, replace the motherboard FRU.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-ERRSTAT (BADEOF), 1 Critical DIAG-ERRSTAT (BADORD), 1 Critical DIAG-ERRSTAT (CRC), 1 Probable Cause Recommended Action Port Error Statistics counter is nonzero, meaning that a Bad end of file error was detected when receiving frames. This can be caused by a faulty cable or deteriorated SFP. It can also indicate deeper problems in the motherboard or ASIC.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-ERRSTAT(CRL), 1 Critical DIAG-ERRSTAT (DISCC3), 1 Critical DIAG-ERRSTAT (ENCIN), 1 26 Probable Cause Recommended Action Port Error Statistics counter is nonzero, meaning that a Cyclic redundancy check on frame failed error was detected when receiving frames. This can be caused by a faulty cable or deteriorated SFP.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-ERRSTAT (ENCOUT), 1 Critical DIAG-ERRSTAT (TRUNC), 1 Critical DIAG-INIT, 1 Critical DIAG-INTNIL, 1 Probable Cause Recommended Action Port Error Statistics counter is nonzero, meaning that an Encoding error, outside frame error was detected when receiving frames. This can be caused by a faulty cable or deteriorated SFP.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-INTNOTCLR, 1 Critical DIAG-LCMEM, 1 Critical DIAG-LCMEMTX, 1 Critical DIAG-LCMRS, 1 Critical DIAG-LCMTO, 1 Critical DIAG-MEMNULL, 1 28 Probable Cause Recommended Action The interrupt bit could not be cleared. This usually indicates an ASIC failure. This message is generated by the centralmemorytest command, if problems are found.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-MEMORY, 1 Critical DIAG-MEMSZ, 1 Critical DIAG-NOSEGMENT, 1 Critical DIAG-PORTABSENT, 1 Critical DIAG-PORTDIED, 1 Probable Cause Recommended Action Data read from RAM location did not match previously written data into the same location. This usually indicates a CPU RAM failure. This message is generated by the ramtest command, if problems are found.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Probable Cause Recommended Action Critical DIAG-PORTM2M, 1 Port is connected to itself (self-loopback). This port M to M port connection is not allowed by the test. This message usually indicates improper cable connections. This message is generated by the spinsilk command, if problems are found. Reconnect port (M) to a different port (N) and re-execute the test.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-STATS (C3FRX), 1 Critical DIAG-STATS (FRX), 1 Critical DIAG-STATS (FTX), 1 Critical DIAG-TBRAM_INC_ RWTEST, 1 Critical DIAG-TBRAM_INC_ WTEST, 1 Probable Cause Recommended Action Port counter value did not match the number of frames actually transmitted. In this case, C3FRX = number of Class 3 frames received. This can be caused by a faulty cable or deteriorated SFP.
Documentation Updates Table 4: Version 3.1.2 Error Messages Not Previously Available (Continued) Severity & Message Critical DIAG-TIMEOUT, 1 Probable Cause Recommended Action For portloopbacktest and crossporttest: Port failed to receive frame within timeout period. For centralmemorytest: Port failed to detect an interrupt within the timeout period. This can be caused by a faulty cable or deteriorated SFP. It can also indicate deeper problems in the motherboard or ASIC.
