HP StorageWorks HA-Fabric Manager release notes Part number: AA–RUR6G–TE/958–000288–011 Ninth edition: (August 2005)
Legal and notice information © Copyright 2003 — 2005 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 These release notes describe the contents of the HAFM software kit, and any last-minute additions or notes on the configuration or use of HAFM software. Be sure to read these notes before installing the HAFM. This information is periodically updated and available on the following HP web site: http://www.hp.com/country/us/eng/prodserv/storage.html.
• Duplicate IP addresses erroneously allowed in Discover Setup Available Addresses list • Ethernet event may not be sent • Domain IDs may not display • SNMP traps are not displayed in the Event Log • Disconnected ISL may not generate Event Log entry • Cannot export to disk on remote AIX client • Cannot import a Physical Map • Errors drop down list is not available • Cannot configure a blank nickname • Support for speed Auto-Negotiate • Losing LAN connection to the HAFM appliance when logged in to HAFM • Eff
CD-ROM directory structure The HAFM software kit includes two CDs; the HP StorageWorks ha-fabric manager documentation and software CD (part number 516-000008-000, Rev A) and the HP StorageWorks ha-fabric manager clients CD (part number 516-000009-000, Rev A), which contains the files necessary to install HAFM. The HP StorageWorks ha-fabric manager documentation and software CD contains the following items at the root level directory: • Open_Bridge_Agent_Installer—Directory for installer • version.
• AIX • hpClientInstall.bin • HPUX • hpClientInstall.bin • Linux • hpClientInstall.bin • Solaris • hpClientInstall.bin • Windows • hpClientInstall.exe • version.txt • Documents • README.TXT—HP document structure; late-breaking doc changes • COPYRIGHT.TXT—Contains the copyright information HAFM software version 08.06.00 The HAFM appliance has the latest version of the HAFM software pre-installed.
Firmware files are included in the upgrade process, but release rules are not. Since release rules are required when sending another firmware version to a switch, an error results. To avoid this problem, add the latest firmware file to the firmware library. This also adds the new release rules and resolves the problem. HAFM 07.02.00 is not removed after upgrading to HAFM 08.xx.xx, and if the server is rebooted, both 07.xx.xx and 08.xx.xx services are started. Be sure to remove 07.02.
Table 1 shows HP terminology and McDATA Corporation equivalents used in the McDATA documents.
HAFM and firmware compatibility Table 2 lists the minimum version of HAFM that can run with the various versions of firmware for the directors and edge switches. HAFM 08.06.00 allows managing of directors and edge switches running any of the versions of firmware listed in Table 2: Table 2 HAFM and firmware compatibility Firmware version HAFM version (minimum) 01.01.02 04.00.01 (HP EFCM) 01.02.02-06 04.01.02-14 (SDCM) 01.03.00-35 04.02.00-40 (HP EFCM) 01.04.00-01 04.02.00-40 (SDCM) 02.00.00-33 06.
Prerequisites for installing and using firmware 07.01.02 If you are using HAFM, firmware 07.01.02 requires HAFM 07.01.00 or later (check with HP Customer Support for the latest shipping version of HAFM). HAFM should be at the minimum level before installing the new firmware. NOTE: HAFM is not required for operating hardware products using the firmware. All directors and edge switches in the same fabric should have the same firmware level installed.
Upgrading from an earlier version of firmware Upgrading to firmware 07.01.02-4 is non-disruptive to attached devices. The director or edge switch is not required to be offline before performing an upgrade operation. Limitations to upgrades are clearly identified if there are any limitations to performing the operation. Before upgrading firmware, it is highly recommended that you back up the director or edge switch configuration.
Some customer environments use application or host software that is affected by the restart of the director CTP during a HotCAT download operation. Applications that rely on inband management servers are especially prone to problems caused by processor restart. For example, an application may be configured to poll the director or switch at regular intervals. The polling process could occur during a restart period, causing the application software to react adversely.
NOTE: Step 4 of the following procedure is not required if you are upgrading from 05.xx.xx or later. To safely upgrade firmware on a director, perform the following: 1. Upgrade HAFM software on the HAFM server/appliance to 07.01.00 (minimum). 2. Download firmware 05.02.00-13 using the Firmware Library option under the Product Manager Maintenance menu. 3. Back up the director configuration using the Backup & Restore Configuration option under the Product Manager Maintenance menu. 4.
Before downgrading below 07.01.02-4, there can only be one user assigned access rights as Administrator and one user assigned as Operator for Embedded Web Server and CLI. If additional users were created, you have to delete them before downgrading. Firmware 07.01.02-4 does not allow the last user with Administrator rights in Embedded Web Server or CLI to be deleted. If no Operator user exists, firmware 07.01.02-4 automatically creates one for each interface during the downgrade.
If a Director 2/140 in a multiswitch fabric is downgraded earlier than 06.02.00, ISLs could become segmented if there are any other switches in the fabric operating with a firmware version earlier than 06.01.00. To prevent this situation, downgrade all Director 2/140s in the fabric to 06.01.00 before downgrading any products in the fabric to 05.xx.xx. This problem only exists with Director 2/140s in the fabric. HAFM displays a warning message if a downgrade from 06.02.
Zone FlexPar feature Because zoning is managed on a fabric-wide basis, all switches and directors in the fabric must maintain the same zoning configuration. This configuration is maintained automatically through the Fibre Channel protocol. To keep this information current, RSCN messages are sent through the fabric to inform attached devices when zoning changes occur, when devices become available, or when devices become unavailable.
• • • • • • • This prevents “snooping” of Ethernet connection to capture user login and authentication secret information. RADIUS Server Support—This provides support for IETF RADIUS (Remote Authentication Dial In User Service) protocol for password authentication. Firmware 07.01.02–4 allows users to configure settings for using a RADIUS server. RADIUS provides centralized authentication services for multiple devices on a network.
Advanced Fabric Diagnostics This provides tools to monitor the fabric and identify potential problems before they impact network and application performance. Tools include ISL Fencing, new switch-centric Fabric and Embedded Port Logs, an Audit Log for the embedded user interfaces, and access to the Digital Diagnostic capabilities included with newer SFP transceivers.
The Fabric log is actually implemented as two logs, one that allows entry wrapping and one that stops adding entries when filled. This log is intended to provide information for analyzing fabric and switch behaviors and problems. The Fabric log is available via EWS, CLI, and HAFM. OSMS change Open Systems Management Server (OSMS) is now available as a standard feature. OSMS can be enabled/disabled via EWS, Command Line Interface (CLI), and HAFM.
Zoning change RSCN control Normally, when a zone set is activated, a fabric format domain Register State Change Notification (RSCN) is sent to all devices in the fabric. With firmware 05.00.00 or later, you can disable these RSCNs from being sent. This is done using the Suppress RSCNs on zone set activations check box on the Configure Switch Parameters dialog box. This feature significantly changes the normal behavior of the fabric.
Zoning limitations With firmware 06.00.00 and later, you have the ability to configure large zone sets, including up to 1024 zones and 1024 end ports in a single zone set. Table 3 shows the supported limits for the edge switches and directors.
Firmware 05.03.01-01 is available for the Edge Switch 2/24, and firmware 05.05.01-01 is available for the Edge Switch 2/12. These versions are installed only on the Edge Switch 2/24 and Edge Switch 2/12, and only when these switches are placed in a M-Series SAN running 05.02.00 firmware. A copy of these versions of firmware, are contained on the HP StorageWorks edge switch documentation and firmware CD (Part Number 524-000001-005).
Changing password in CLI When users are prompted to change the password when logging into the Command Line Interface (CLI), they can enter the default password (password). This will be accepted, however at the next login they will again be required to change the password if it is still the default password. When users enter the default password when prompted to change the password, new Security Log entry 10203, Default Password Not Changed, is posted.
The issue arises because either LAN connection on the HAFM appliance can be the public LAN or the private LAN. Though the directors and edge switches can be managed via either LAN, the public LAN is the only one that can support remote client access. Thus, if one attempts to access the HAFM appliance via a remote client session and is unknowingly using what has been designated as the private LAN, the remote session is not allowed.
Workaround If the date/time of the HAFM appliance needs to be set to an earlier time, perform the following: 1. Exit the HAFM application. 2. Select Start > Programs > HP StorageWorks ha-fabric manager 8.6 > Stop Services. 3. Change the date/time on the HAFM appliance. 4. Select Start > Programs > HP StorageWorks ha-fabric manager 8.6 > Start Services. 5. Restart the HAFM application. This procedure works even if you previously set the date/time to an earlier time without using these steps.
Changing or removing the principal switch of a persisted fabric causes two fabrics to be displayed Fabrics are identified by the WWN of the principal switch. If a new principal switch is selected (either manually, or because the current principal switch is removed from the fabric), the fabric is reidentified by the WWN of the new principal switch.
Port Fencing dialog box may not reflect correct count of Affected Ports in ISL Thresholds table This usually occurs when a policy has been applied to an entire switch and there are already ports with a threshold policy applied, even when it is selected not to replace the existing policy on the switch ports.
Ethernet port failure on HAFM appliance may impact HAFM behavior On the HAFM appliance, the SNMP agent may appear to hang or respond slowly if the Ethernet port on the server fails and transmits bad frames. CPU usage and memory usage display abnormally high. AIX client may not connect to HAFM appliance The remote client running on IBM AIX intermittently cannot connect to the HAFM appliance. AIX detects server when attempting login, but then displays a server not found and unable to connect message.
Cannot export to disk on remote AIX client An exception is occurring when an export to disk operation is performed on a remote AIX client platform. Cannot import a Physical Map If an attempt is made to import a Physical Map by itself, the import fails. Workaround A Physical Map can be imported as part of a full SAN import file. Errors drop down list is not available The Errors drop down list is not available in the Performance Graph for HAFM 08.06.00.
Workaround The LAN connection must be restored. Stopping HAFM has no impact on the Fibre Channel operations of any edge switch or director. Monitoring switch operations, logging events, and implementing configuration changes are interrupted only while the LAN is not connected. Effect of no LAN connection to HAFM appliance during boot up If the HAFM appliance has no LAN connection while booting up, but it is connected after booting up, the remote client sessions to the HAFM appliance are not allowed.
Workaround When a switch has been added to HAFM for management, or firmware has been upgraded, observe the switch being shown as discovered by HAFM. Check the event log of the switch to ensure there were no faults that occurred during the short time when HAFM was in the process of discovering the switch. New sound files are not added to Event Manager immediately New sound files do not display in the pull down menu of the Event Manager. They cannot be selected for inclusion in a rule.
Ethernet port on HAFM appliance may encounter problems When you use TightVNC to access the HAFM appliance and you are running HAFM locally on the HAFM appliance, the Ethernet port on the HAFM appliance can appear to hang. When the Ethernet port encounters problems, the following may occur: • There is an apparent loss of communication to switches being managed by HAFM. • The appliance CPU usage and memory usage display abnormally high readings.
