HP StorageWorks Fabric OS 4.4.
Legal and notice information © Copyright 2005, Hewlett-Packard Development Company, L.P. © Copyright © 2005, Brocade Communications Systems, Incorporated. 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.
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 overview These Release Notes cover the following major topics: • Fabric OS 4.4.x enhancements, page 3 • Accessing documentation, page 6 • Standards compliance, page 6 • Important notes, page 7 • Commands modified in Fabric OS 4.4.x, page 21 • Documentation updates, page 22 • Closed issues from previous 4.2.
• Trunking over Extended Fabrics • For the HP StorageWorks 2 GB, Core Switch 2/64 and SAN Director 2/128 switches, two links up to 50 km at 2 Gbit/sec and 4 links at 10km at 2Gbit/sec • For the SAN Switch 4/32, three links up to 250 km at 2Gbit/sec and 100 km at 4 Gbit/sec • Increased scalability to 2560 ports and 50 domains • Port scalability via license keys • Fabric Watch improvements: • Improved notification • Switch health reports • Standardized messaging: for example, including information such as tim
Technical support Contact Hewlett-Packard support for hardware, firmware, and software support, including product repairs and part ordering.
Accessing 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. To access the technical documentation: 1. Locate the Networked storage section of the Web page. 2.
• FC-FG ANSI X3.289: 1996 • FC-PH ANSI X3.230: 1994 • FC-PH-2 ANSI X3.297: 1997 • FC-PH-3 ANSI X3.303: 1998 • FC-PLDA NCIT S TR-19: 1998 • FC-SW-2 Rev 5.3 • FC-VI Rev 1.61 • FC-MI Rev 1.92 • FC-BB Rev 4.7 • FC-FS Rev 1.7 • FC-BB-2 Rev 5.3 • IPFC RFC 2625 • FCP ANSI X3.269: 1996 • FCP-2 Rev 7 Important notes This section provides information you should be aware of when running Fabric OS 4.4.x. 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 4.4.x switch into a fabric consisting solely of Fabric OS v2.x/v3.x switches. Before adding a Fabric OS v4.4.x switch to such a fabric, refer to the HP StorageWorks Fabric OS 4.2.x procedures user guide for information on the Extended Edge PID format.
Browser window response after failover A browser window might stop responding after an HA failover immediately after a zoning configuration is enabled or disabled. It is likely that the web daemon was terminated by the HA failover before the HTTP request was returned. If the HA module does not respond, close the window and relaunch the module. If the module is locked, shut down and relaunch the Web Tools application.
Browser, OS, and Java plug-in support Advanced Web Tools browser, operating system, and Java Plug-in support is updated for Fabric OS v4.4.x. Table 1 identifies the supported browsers, operating systems, and Java Plug-ins for this release. Go to the http://www.hp.com web site for the latest list of supported operating systems. Table 1 Browsers, Operating Systems, 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.
Table 1 Browsers, Operating Systems, and Java Plug-ins (continued) Operating System Browser Java Plug-in Red Hat Enterprise Linux AS 2.1 (IA32) NN7.02 1.4.1_03 Red Hat Enterprise Linux AS 2.1 (IA32 & IA64) Mozilla 1.4 or later 1.4.2_02 or later (up to but not including 1.5) Red Hat Enterprise Linux AS 3.0 (IA32 & IA64) Mozilla 1.4 or later 1.4.2_02 or later (up to but not including 1.5) Red Flag Linux (32-bit) Mozilla 1.4 or later 1.4.2_02 or later (up to but not including 1.
Table 1 Browsers, Operating Systems, and Java Plug-ins (continued) Operating System Browser Java Plug-in Windows XP IE 6.0 SP1 1.4.1_03 (recommended) Windows Server 2003 (IA32) IE 6.0 1.4.1_03 Windows NT 4.0 SP6a IE 6.0 SP1 1.4.
Table 2, Table 3, and Table 4 list important information for switches running Fabric OS v4.4.x. Table 2 Information Specific to SAN Switch 4/32 SAN Switch 4/32 Description SWL and LWL SFP modules release mechanism The SAN Switch 4/32 uses an octal-style SFP cage that places SFPs in close proximity. As a result of the physical space limitation between the SFPs, HP requires the use of approved SFP modules only.
Table 2 Information Specific to SAN Switch 4/32 (continued) SAN Switch 4/32 Description LED, system power The system power LED behaves differently in the SAN Switch 4/32 than in SAN Switch 2/8V and SAN Switch 2/16V switches. In the latter switches, it is solid amber when a power supply FRU has failed. In the SAN Switch 4/32, the system power LED remains green, and the system status LED will blink, indicating an error. The SAN Switch 4/32 uses a new block of WWN numbers.
Table 3 Core Switch 2/64 Information Core Switch 2/64 Description Power supplies Customers reconfiguring SAN Director 2/128-only configurations by adding Core Switch 2/64 blade(s) will have to ensure that all three power supply FRUs are installed, as Core Switch 2/64 blades have greater power requirement Table 4 Fabric OS area information Fabric OS Area Description Compatibility Sometimes in a mixed fabric of Fabric OS v4.x/v3.x/v2.x, fabric reconfiguration is caused by link reset on v3.x/v2.x.
Table 4 Fabric OS area information (continued) Fabric OS Area Description HA switch reboot When a switch reboot or a failover occurs before POST is complete, the HA failure resynchronization is disrupted. HA will not resynchronize until POST completes. CAUTION: Allow POST to complete before performing a switch reboot or failover, to avoid disruptive failover.
Table 4 Fabric OS area information (continued) Fabric OS Area Description Logging, When setting the automatic FTP IP address, userid, password, and supportFTP associated directory path for use with the supportFtp command, the command parameters are not checked immediately for validity. Generate a manual trace dump to confirm the FTP transfer immediately. First, use supportFtp to set up FTP parameters. Next, use traceFtp -e to enable automatic transfer of the trace dumps.
Table 4 Fabric OS area information (continued) Fabric OS Area Description Security: HTTP policy If HTTP_Policy is empty, you will not be able to log in and will receive a Page not found error. This is expected behavior for this policy. Security: invalid certificate Web Tools and Fabric OS are not consistent in how they report switch certificate status.
Table 4 Fabric OS area information (continued) Fabric OS Area Description Security: secure mode, passwd Telnet CAUTION: Using the passwd Telnet command in secure mode to change the password results in all sessions using that password being logged out, including the session that changed the password. This is expected behavior. The session terminates if you change the password in secure mode.
Table 4 Fabric OS area information (continued) Fabric OS Area Description Upgrading to Fabric OS v4.4.x Recommended upgrade procedures to Fabric OS v4.4 include the following: Before loading v4.4: • Run configupload. Creates a backup configuration, should the user want to return to v4.2. • Run supportShow. Captures the previous error logs in v4.2. • Run chassisName. Changes the default factory configuration to a more meaningful name. After loading Fabric OS v4.
Commands modified in Fabric OS 4.4.x The supportSave command was modified in this release, as follows: supportSave Under the supportSave command, in the “Description” section, replace this text: “RASLOGswitchname-slot-YYYYMMDDHHMM-errDumpAll.ss TRACEswitchname-slot-YYYYMMDDHHMM-tracedump.dmp supportShowswitchname-slot-YYYYMMDDHHMM-supportShow (saved in the specified remote directory)” Add this text: “RASLOGchassisname-slot-YYYYMMDDHHMM-errDumpAll.ss TRACEchassisname-slot-YYYYMMDDHHMM-tracedump.
Documentation updates This section provides information on last-minute additions or corrections to the HP StorageWorks Core Switch 2/64 and SAN Director 2/128 installation guide. Replace Table 12 on page 77 with the following: Table12: WWN Bezel LED Patterns LED Name, Location LED Color Status of Hardware Recommended Action 16-Port card/CP card Power Steady green Power is OK No action required.
Table12: WWN Bezel LED Patterns LED Name, Location LED Color Status of Hardware Recommended Action No light (LED is OFF) Port card is either healthy or does not have power. Verify that the port card power LED is on. NOTE: Check the individual port card (see Figure 15 on page 81) or CP card status LEDs (see Figure 16 on page 85) on the port side of the chassis to confirm the LED patterns. Power supply/ Power/Status Steady green Power is OK. No action required.
Closed issues from previous 4.2.2a release Table 5 lists defects that have been closed since the last Fabric OS 4.x release, version 4.2.2a. Table 5 Closed issues for Fabric OS 4.2.2a Fabric OS 4.2.2a Issue Status Switch is rebooting Fabric OS version Fixed. 4.0.0.c. 24 Compact Flash is full due to large wtmp file Fixed. Core Switch 2/64 fails to come online to MVS - Command Rejects.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Track Logging Feature does not detect failure login to the switch via SSH. Fixed. Switch (active CP) reset when switchdisable/enable script running. Fixed. Modifying switch and CP IP addresses caused a telnet hang. Fixed. After fastbooting standby CP of the primary FCS, doing secfcsfailover before HA is in sync results in old primary FCS switch's active CP panicking. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Mechanism needed to monitor or prevent all instances of compact flash using 100% of capacity. Fixed. Under some rare circumstances, the flash file system fills up completely. Switch reboot with CF Error: hda: status timeout ... Fixed. Switch: 0, Critical SCN-SCNQ_OVERFLOW, 1, SCN queue overflow for nsd Fixed. Unable to activate NoNodeWWNZoning with just the cfgenable command. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status If the IP addresses are set up on a network that is configured with IP address that are 10.0.x.x and a subnet mask of 255.255.0.0, there will be routing between eth0 and eth1. This is not the expected behavior, as eth0 traffic should not be routed to eth1. Fixed. Switch ports are set to faulty when certain tasks are performed in Win2003 clustered environment.
Table 5 28 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Fabric Manager: FM Database shows less number of devices for 2+6 fabric than what is seen in nameserver entries. Fixed. Core Switch 2/64 CP failover due to zone daemon failure. Fixed. After zoning is changed from mixed to all wwn zoning, host F-Ports loses access to target F-Ports. Fixed. Fabric Manager does not disable port 126 when FMS mode is enabled. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Some CHPIDs are not able to access the devices after an IOCDS change and 'config POR'. It appears that FLOGI to the devices get F_RJT with reason code x04. A port disable and port enable at the switch for the CHIPID corrects the problem. Fixed. Using Script continuously telnet login/logout, some sessions fail with timeout. Fixed. When POST is running, reset the micro switch on the active CP.
Table 5 30 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status An update to the standards protocols was made for the GATIN command, and the new modes are not supported This is a MS command used to discover the topology of the fabric. Fixed. No log message is generated when one CP resets the other CP. Fixed. When configuring a route the user may in a rare instance receive an incorrect error message "Input port not available for routing". Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Failover during hardware configuration operations may leave the port in an inconsistent state. Fixed. Activating Trunking at the switch level (switchCfgTrunk) when a long-distance port is currently configured causes the error message "No Trunking support of long distance port" to be displayed, which is correct. However, other trunk ports are then left in a disabled state. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status When setting fcpProbeDisable to 1 through configure command fcAL.fanFrameDisable will automatically be set to 1. Fixed. Web Tools displays an incorrect value for the current value on smart SFPs. Fixed. AddSetMember failing to add License key to switch, when 4.1.1 is proxy and other F/W is target. Fixed. SNMP FW-BELOW Trap for EnvFan is not sent after haFailover. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status The message displayed when Web Tools license is removed, and later added, is inaccurate. Fixed. syslogd does not send out the right number of errors to host. Fixed. When the secmodeenable fails due to the absence of certificates on multiple switches in the fabric, an error is reported for only one of the switches missing a certificate. Fixed.
Table 5 34 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status On a large fabric, when using a v4.x switch as a proxy, an ERR_LOGICAL_BUSY is always returned when discovering one particular switch (dev185) with the API. Fixed. If customer has an EE monitor defined that incorporates the last 15 ports and changes the PID format to "2", the resulting EE monitor will change to an out of range port number. E.g. 7f changes to 8f. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Board won't boot all the way if it loses its boot environmental Variables. Console output would look like this: Fixed. The system is coming up, please wait... Unable to read configuration data WARNING: Failed to set EMAC hardware addresses! 1) Start system. 2) Recover password. 3) Enter command shell.
Table 5 36 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status hafailover on SAN Director 2/128 caused port blade vacant, but the status LED on the port blade shows it is in a good state. Fixed. On PID format conversion max cfgsize limit is not enforced. Fixed. In a 4x16 fabric with zone db size 35K,the Zone administration window opened from Fabric Manager does not show the last two zone members properly. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Port log "disable" or "enable" entry is not logged in port log when Fabric Watch's PortLogLock alarm trigger is used to log a port log of a port. Fixed. When using the bladeDisable or bladeEnable command there is no output to the user to let them know whether the command failed or succeeded. Fixed.
Table 5 38 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status When doing chassisconfig 2 on the SAN Director 2/128, occasionally, after CP1 was rebooted twice and after CP1 came back, HA was out of sync. Fixed. When doing zone propagation from one of edge on the SAN Switch 2/32, on core and edge, there was message "Warning BLOOM-TRNK_SLV_DWN" showing up. When switchshow on that port is checked, there is no indication on port offline. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Customer may encounter coldstart trap not being received on the SAN Director 2/128 with all types of reboot methods. Fixed. cpstatus changed and fruhistory traps are not generated while doing hafailover on the SAN Director 2/128. Fixed. Reload of switch configuration causes port to go offline. Fixed. When doing a firmware download on a SAN Switch 2/32, EMD and SNMPD panic may occur, when upgrading firmware from 4.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status When running switchdisable; Fixed. cfgclear; cfgdisable; switchenable on all core switches (2 - 3900s and 1 - 24K), an error message: 0x23b (fabos): Switch: 0, Critical SCN-SCNQ_OVERFLOW, 1, SCN queue overflow for process webd occasionally occurs on the core 24K switch. 40 In the supportShow "Description" section, need to change the third sentence currently reads, "These commands are organization by groups...
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Created an user defined account using userConfig command, after firmwaredowngrade to v4.2.x, still able to login with this user defined account Fixed. Standby CP getting "Failed expression" error in rcs_ha.c. Fixed. The problem happens intermittently. The last time this problem happens when both CPs are rebooted almost at the same time. A message showed up on standby CP console.
Table 5 42 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status When running the test program from the mainframe under heavy stress conditions (multiple LPARs, multiple paths, etc), IFCC errors are observed on the Host. The Channel sends ABTS to a CCW chain after it has timed out waiting 2 seconds for a response. Fixed. Web Tools SID/DID predefined window display "cannot open SID/DID:null" message. Fixed. Using https to access a 4.2.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status NSD panic in deleting timer. Fixed. Symptom: In a fabric of mixed 16 different type of switches (core-edge) design, panic occurred either during power cylce or reboot process using one of the following procedure: 1. Power cycle all switches with diagenablepost active -Invoke diagenablepost in all switches -Power off all switches wait for 10 minutes -Power on all switches 2.
Table 5 44 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status A zone was created on a fabric and the zone was not exported through router. Fixed. FSSME should take on default values if fssme.conf file is corrupted or not present instead of preventing switch from bootup. Fixed. FM: Cryptic Error message showing up in Events table; needs to clearly indicate why the error occurred. Fixed.
Table 5 Closed issues for Fabric OS 4.2.2a (continued) Fabric OS 4.2.2a Issue Status Fan, Temp and Power buttons shows no data if FabricWatch license is not installed. Fixed. After switch install, third party I/O Module management software did not show the last letter of a patch revision number. Fixed. Time in Minutes" scale is wrongly labeled. 5 mins, 10 mins, 15mins. Fixed. Core Switch 2/64 fails backport test when certain Domain IDs are used Fixed. Fabric OS 4.4.
Closed issues from previous 4.2.
