HA-Fabric Manager release notes

HP StorageWorks

HA-Fabric Manager release notes

Part number: AA–RUR6J–TE/958–000288–013Eighth edition: (October 2006)

DescriptionThese release notes contain late-breaking and supplemental information for the HA-Fabric Manager(HAFM) 08.09.01 software.

These release notes are intended for customers who purchased HAFM software.

This information is available and periodically updated on the HP web sitehttp://h18006.www1.hp.com/storage/saninfrastructure/index.html.

Update recommendationRoutine

Devices supportedFor the latest supported devices, see the HP StorageWorks SAN design guide, available athttp://h18006.www1.hp.com/storage/saninfrastructure.html.

Product modelsThis section describes the supported switches and HAFM software.

SwitchesThis section describes Director and Edge Switch product model support.

Table 1 Supported switches, firmware, and software

HP name McDATA name

HP StorageWorks Edge Switch 2/12 Sphereon™ 4300 Fabric Switch(first and second-generation)

HP StorageWorks Edge Switch 2/16 Sphereon 3216 Fabric Switch

HP StorageWorks Edge Switch 2/24 Sphereon 4500 Fabric Switch(first and second-generation)

HP StorageWorks Edge Switch 2/32 Sphereon 3232 Fabric Switch

HP StorageWorks Director 2/64 Intrepid™ 6064 Director

HP StorageWorks Director 2/140 Intrepid 6140 Director

Surestore Director FC-64StorageWorks SAN Director 64

ED-6064 Director

N/A Sphereon 4400 Fabric Switch

N/A Sphereon 4700 Fabric Switch

HAFM Basic (formerly, Embedded WebServer or EWS)

EFCM Basic Edition (formerly, SANpilot)

HA-Fabric Manager (HAFM) Enterprise Fabric Connectivity Manager (EFCM)

Firmware Enterprise Operating System (E/OS)

HAFM Appliance EFCM Server

HA-Fabric Manager release notes 3

http://h18006.www1.hp.com/storage/saninfrastructure/index.html















http://h18006.www1.hp.com/storage/saninfrastructure.html












HAFM software version 08.09.01HAFM 08.09.01 applies to the 1U rack-mount appliance only and cannot be installed on the notebookserver. All remote clients running down-level versions of HAFM are required to reinstall the clientapplication. You must exit HAFM before installing the latest version of HAFM. When logging in to theHAFM appliance through the remote client, an error message is displayed stating that the new versionmust be installed. Follow the instructions to install the new version of the remote client.

HAFM 08.09.01 is available on the HP web sitehttp://h18006.www1.hp.com/storage/saninfrastructure.html.

Upgrading to HAFM 08.09.01If you have an HAFM notebook server or an HAFM appliance and you are upgrading to HAFM08.09.01, you must follow the directions as detailed in the HP StorageWorks HA-Fabric ManagerTransition Guide (part number AA-RV1MD-TE), to successfully transfer your SAN configuration informationto HAFM 08.09.01. This version of this guide was written for HAFM 08.08.00, and also applies toversion 08.09.01.

Downgrading HAFMWhen downgrading from HAFM 08.xx.xx to 07.xx.xx, your zoning configurations and nicknames are notconverted. HP recommends that you backup and save your 07.xx.xx configuration before upgrading to08.xx.xx. You can then restore that backup if you downgrade to HAFM 07.xx.xx. See the HAFM Basicuser guide or EFCM Basic user guide for more information.

Operating systemsHAFM 08.09.01 clients are supported on the following operating systems:

• Windows® Server 2000 Professional, Service Pack 4• Windows Server 2003, Service Pack 1• Windows XP Professional, Service Pack 2• Solaris® 8 and 9• Red Hat® Linux 9.0, kernel 2.4.20• Red Hat Enterprise Linux 3, kernel 2.4.21• HPUX 11.0• IBM® AIX™ 4.3.3• IBM AIX 5.1

LanguagesEnglish

4













FixesTable 2 lists issues that have been fixed in HAFM 08.09.01 since the release of HAFM 08.08.00.

Table 2 HAFM 08.09.01 fixes

Description Problem Category

The Operational Status column does not update correctly when aMcDATA 4Gb SAN Switch is taken offline. Instead of indicatingthat the McDATA 4Gb SAN Switch is offline, the status in theOperation Status column and alert icon (Product List and Topologyview) displays as failed.

Display/Layout/GUI

Topology view has update problems when the principle switch isnot managed by HAFM and the fabric is segmented. The devicelist adjacent to the topology may display the same switch in twodifferent fabrics or the switch may toggle from one fabric to another,at a rate of approximately half of the discovery rate (approximatelyeight seconds).

Display/Layout/GUI

In the product List, Domain ID column not getting sorted properly. Device List/Properties

Unable to discover switch when IP is reused in a switch swap-outscenario.

Discovery

Changing the server time back causes the link to drop or the closesthe Element Manager. When the user attempts to reopen ElementManager, the following message appears: The link to theproduct is not available: Connection lost.

Element Manager

A Preferred Path cannot be enabled intermittently even when theDomain ID is set to Insistent.

Element Manager

With FICON Management style, the Addresses menu item underthe Configure menu (Configure > Addresses) is not availablein the 6140 Element Manager.

Element Manager

When performing a CTP switch over from either CTP 0 or 1, the entireHardware View window is blank until stopping and starting services.

Element Manager

The user is not notified that firmware download on single-CTP systemcauses switch to boot the IPL file rather than the current activeconfiguration.

Element Manager

For an upgrade firmware install, the red progress bar is not updated. Element Manager

Stopping External port diagnostics in the middle of a test may causeport to indicate failure.

Element Manager

Firmware may not update on HP-UX systems. Element Manager

The cooling fan module may display incorrect position informationin the element manager FRU list.

Element Manager

Port status alert indicator may not be removed when a NOS alertis cleared from Ports tab

Element Manager

No log entries generated when a link between switches isdisconnected.

Event Management

User Action Event may not be generated in Master log formodifications done in Call Home dialog.

Event Notification

The HAFM Event Log is missing system power up and standby readyevents after system power down.

Element Manager

When enabling or disabling fabric binding on muliple fabrics, thewrong WWN displays in the Fabric Name field of the Fabric BindingStatus window.

Fabric Binding



Switches added to the fabric binding membership list may not beable to join the fabric.

Fabric Binding

Isolated switches with fabric binding enabled may display informationfrom a prior fabric.

Fabric Binding

User created columns may not import using the CVS import feature. Import

HAFM does not take the NickName file from default folder andimport failed. Browsing and selecting file to import works.

Import

The cursor stays at the Yes option even though you select the Nooption in the Copy Data and Settings menu.

Install

The UNIX remote client install path does not get appended in the 8.8folder, resulting in erasing non-HAFM files during uninstall.

Install/Uninstall

The HAFM client does not automatically launch after installation; youmust manually launch the client.

Install/Uninstall

Embedded Port log may not open if a switch connection goes offline. Logs

Audit Log window may not open when you select Display in a newwindow.

Logs

Events may not be displayed in Audit Log (Monitor menu). Logs

Security Event Information may be displayed in Hexadecimal formatin Security Event Log file.

Logs

Events may not be displayed in the Product Status Log window. Logs

Data Field may be empty in the Event Log window. Logs

Administrator’s password is not migrated from HAFM 7.X to 8.X.Password gets reset to default “password” in HAFM 8.X.

Migration

The Configuration Wizard/Copy Data and Settings dialog box mayallow entry of an invalid migration path.

Migration

Call Home information is not migrated from 8.x to 8.6 duringupgrade.

Migration

Setup tools detail information is not migrated to prevent replacingupdated launch information.

Migration

Prior software versions automatically populated the label field witha default value. The user-defined nickname field has replaced thelabel field. Users may not have defined the label field informationin the prior software release so views may appear to lose data aftermigration.

Migration

The Suppress Zoning RSCNs on zone set activationssetting may not migrate from earlier software versions.The switch parameter may not have been saved properly in theprior software version.

Migration

User edited startup and configuration file settings may be lost aftermigration.

Migration

Persisted fabrics are not migrated from HAFM 7.X to 8.7. Migration

Discovery is not stable after migration. Discovered devices arefrequently getting changed after migrating from HAFM 8.6.

Migration

Delay may be experienced when importing a sorted nickname file. Nicknames

When Port WWN and Node WWN are the same, the nicknameof node may be displayed as the Port Nickname in the configurenicknames dialog

Nicknames

6


The Nickname size limit is not consistent throughout HAFMapplication.

Nicknames

No data in exported file when exporting WWNs of discovereddevices via Configure Nicknames dialog.

Nicknames

All WWNs are displayed in the configure nicknames dialog whenyou select All WWNs from the display pull-down menu. The configurenicknames dialog should show WWPN for devices that are currentlylogged into a switch, or the WWNNs of switches in fabrics that arebeing managed or discovered.

Nicknames

The Nickname import allowing invalid characters in the WWN field. Nicknames

High and Low critical indicators are not correct when opening PortPerformance Graph from the McDATA principal switch.

Performance

Switch label did not show up on the switch performance graph. Performance

Ports show up twice in the performance graph and a no lightport shows up in the graph.

Performance

The Errors drop-down list not available in the Performance Graphfor HAFM 8.6.

Performance

An exception is displayed when the Performance Graph menu item isselected by right-clicking the switch.

Performance

Performance graph may display a short duration data increaseimmediately after changing discovery method

Performance

Partition that is no longer part of the fabric continues to display onthe topology after setting a switch offline to segment the fabric.

Physical Map

After clicking Remove after applying threshold in the same session,the threshold is still applied.

Port Fencing

Threshold limit dialog is not triggered when fencing policy is appliedat the switch level.

Port Fencing

Security violations do not display yellow alert icon. Port Fencing

Switch threshold dialog does not open in session when a policy hasbeen removed from switch level during the same session.

Port Fencing

Removing switch level threshold causes ports to incorrectly inheritpolicy. The switch inherits the fabric policy. All the subordinateports also inherit the policy regardless of any directly assigned portpolicies.

Port Fencing

Nicknames cannot be left blank. You must select Cancel to do so. Anerror occurs if you attempt to delete a previously added nickname.

Properties

User defined nicknames for node devices do not show in connectionproperties.

Properties

Port WWN is listed in the Node WWN field of Properties dialogbox for a node device. The Properties dialog box of a node devicelists the Port WWN in the Node WWN field.

Properties

Operational Status for a switch may not display in Product list. Properties

Model field may not show correct value in Security Center. Valuemay appear as 001.

SANtegrity

An Operation failed error message window appears afterHAFM Appliance shutdown.

Shutdown/Exit

Unable to enable fabricbinding for switch blade-only fabric. McDATA 4Gb SAN switches



In a blade switch fabric, an invalid attachment is not shown onMcDATA switch port. If there is an invalid attachment between 2ports, one on a switch blade and one on a McDATA switch, theinvalid attachment is not displayed on the McDATA switch port.

McDATA 4Gb SAN switches

Switches may show in the same fabric with no visible connection (ifphysical connection method is not supported).

Topology

Browse user may be able to delete a Group log. User Management

The Copy, Delete, Delete All options may be enabled for a readaccess user.

User Management

An application may not gather active zone sets from HAFM 7.1 ifinvalid port number is discovered.

Zoning

HAFM as well as EWS are labeling port names as node names.In the HAFM Security tab, HAFM is labeling device port names asnode names.

User Management

Cannot import a zone set with more than 2048 members. Zoning

All domain IDs in a fabric do not get displayed in product view. Display

HAFM 8.9. management of Directors and Edge Switches andDirectors running firmware 6.x or earlier, does not display theport state correctly in various parts of the Element Manager:1. Product/Fabric View: Ports that are logged-inintermittently appear and vanish from view.2. Performance View: Ports with established I/O do notdisplay the green bars or water marks. The performancetables do not update port status after a requested "refresh".3. Port Card view identifies all ports as "failed", withflashing red diamond. All of the ports may be operational.

4. Node List: With devices attached, the node list fails topopulate to reflect device attachments.

Display/Layout/GUI

Export successful message displays without any file name and path. Export

No CTA event is logged in Threshold Alert log. Element Manager

FC Address field in Node List View cannot be sorted on all 3 bytes ofthe port Address. HAFM sorts on the Domain/Area fields of the PortAddress only, not on the Port field.

Element Manager

When an Element Manager launch is attempted after IP addressis swapped between the Sphereon 4500 Fabric Switch and theSphereon 4700 Fabric Switch, an error message Invalid Product Typeis displayed for Sphereon 4700 Fabric Switch.

Element Manager

Users can enable the insistent domain ID feature when the preferreddomain ID and current domain ID do not match.

Element Manager

Users can enable the preferred path feature when the active domainID and the preferred domain ID do not match.

Element Manager

Switch Blades and SANtegrity: Cannot activate Fabric Mode on aswitch blade-only fabric mixed-fabric in Open Systems mode.

Enterprise Fabric Mode

Switch Blade and Enterprise Fabric Mode: When attempting todeactivate Switch Binding with Enterprise Fabric Mode enabled, nomessage displays. A message should display stating that switchbinding cannot be deactivated while Enterprise Fabric Mode isenabled.


8


Switch Blades and Enterprise Fabric Mode: switch binding isdeactivated when Enterprise Fabric Mode is deactivated for switchblades.


When an ethernet cable is disconnected, the ethernet event is notsent for switch in a discovered fabric.

Ethernet Event

No SNMP traps are displayed in the event log when sent acrossthrough a firewall.

Event Log

Exception occurs when export- to-disk operation is performed ona remote client on AIX platform.

Export

HAFM 8.7 Fabric Log falsely reports ISLs added and removed. Fabric Persistence

Firmware load failure to a Director due to intermittent timeout. Install/Uninstall

The incorrect firmware version is displayed in fabric tree afterdowngrading to firmware 7.1.3.

Install/Uninstall

FL Ports do not show a destination icon and port in performancegraphs.

Performance

The persist fabric does not work properly if the connection is lost toa non-McDATA principal switch. The persist fabric always keys offthe principal switch. Non-McDATA switches do not display in HAFM.When a non-McDATA switch is the principal switch and the fabric ispersisted, incorrect persist fabric updates occur if connection is lost tothe principal switch.

Persisted Fabric

A fenced port reports as disabled after a clearing problem and theport is placed back online.

Port Fencing

The user must unblock, block then unblock again to recover a portafter a fencing policy has been invoked.

Port Fencing

Cannot enable a show route between the end devices attached to aswitch blades.

Show Route/Hide Route

EnhancementsThis section describes enhancements for HAFM 08.09.01.

4Gb Fibre Channel speed support for Director 2/140This release now provides 4 Gb Fibre Channel speed support in the Director 2/140 when using the 4Gb/s Intrepid 6000 QPM Blade. You can purchase the 4 Gb/s Intrepid 6000 QPM Blade (QPMblade) through an authorized McDATA Reseller.

For information about purchasing the 4 Gb/s Intrepid 6000 QPM Blade, please contact your authorizedMcDATA reseller. You can find the latest McDATA contact information by region on the McDATA web site

http://www.mcdata.com/about/contact/index.html.

For detailed information about the 4 Gb/s Intrepid 6000 QPM Blade, see the latest versions of theIntrepid 6140 and 6064 Directors Element Manager User Manual and the E/OS Command Line InterfaceUser Manual, available on the McDATA web site

http://www.mcdata.com/wwwapp/resourcelibrary/jsp/navpages/indexForSearchBy.jsp?search-FolderName=/tpub/&resourceType=Technical%20Documents&product_line_root=tpub&re-source=tpub_search&mcdata_category=www_resource.


http://www.mcdata.com/about/contact/index.html















http://www.mcdata.com/wwwapp/resourcelibrary/jsp/navpages/indexForSearchBy.jsp?searchFolderName=/tpub/&resourceType=Technical%20Documents&product_line_root=tpub&resource=tpub_search&mcdata_category=www_resource



























PFE key supportFor information about all PFE features, contact your authorized McDATA reseller.You can find the latest McDATA contact information by region on the web sitehttp://www.mcdata.com/about/contact/index.html.

Compatibility and interoperabilityThis section describes Director or Edge Switch products compatibility.

HAFM and firmware compatibilityTable 3 lists the minimum version of HAFM that can run with the various versions of firmware for Directors,Edge Switches, and the McDATA 4Gb SAN Switch.

Table 3 HAFM and firmware compatibility

Firmware version HAFM version

Director and Edge Switches

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.00.00-45 (HP EFCM)

02.00.02-01 06.00.02-06

04.01.02-04 06.03.01-05

05.02.00-13 07.02.00-09 (HAFM Appliance)07.01.00-09 (Notebook Server)

05.05.00-12 None (firmware for Edge Switch 2/12 only)

06.01.00-1806.02.00-22

08.02.00 recommended (HAFM Appliance)07.02.00-09 minimum (HAFM Appliance)07.01.00-09 minimum (Notebook Server)

07.00.00-8407.01.02–407.01.03


08.01.0008.01.0108.02.00


09.00.00 08.09.01 recommended (HAFM Appliance)07.02.00-09 minimum (HAFM Appliance)07.01.00-09 minimum (Notebook Server)

McDATA 4Gb SAN Switch

5.2.2.15.00 08.09.01 recommended (HAFM Appliance)08.08.08 minimum (HAFM Appliance)

Important informationThis section lists information that you should consider before you using HAFM.

10
















Disabling the SNMP ProxyBy default, the SNMP Proxy is enabled on all McDATA 4Gb SAN Switches. To ensure proper HAFMfunctionality, disable the SNMP Proxy feature before attempting to discover the McDATA 4Gb SANSwitches in HAFM.

To disable the SNMP Proxy:

1. Telnet to the switch.2. Login to the switch.3. Enter:

admin start

4. Enter:

set setup snmp

5. Set the ProxyEnable setting to False.6. Enter Y at the following prompt:

Do you want to save and activate the snmp setup? (y/n): [n]

E-Mail filter considerationsThe firmware e-mail filter overrides the HAFM e-mail filter. The firmware determines that certain events donot generate an e-mail notification. In this situation, the e-mail message is not sent for these events even ifyou add this type of event to the selected events section of the HAFM email filter dialog.

Managing McDATA 4Gb SAN Switch considerationsDO NOT use the Element Manager Fabric Binding feature on McDATA 4Gb SAN Switches. ElementManager Fabric Binding does not synchronize with HAFM Fabric Binding. If both Fabric Binding featuresare used, a disconnect can occur between the two features.

Examples

• If you activate an ISL set while a port set is already active, the ISL set takes over and vice versa.This is working as designed.

• If you activate Switch Binding using the Element Manager, and then activate Fabric Binding usingHAFM, the McDATA 4Gb SAN Switch copies and appends the Fabric Binding to the currentSwitch Binding security policy. This is working as designed. However, if you then deactivateFabric Binding using HAFM, it only deactivates on legacy M-Series and McDATA switches.You must deactivate the policy using the Element Manager to deactivate it on the McDATA4Gb SAN Switch.

If you also had Switch Binding activated and the learned Fabric Binding policy is merged, SwitchBinding becomes deactivated. A security hole exists if you do not realize this; however, it is apparentthat this happens when you look at the active policy. Activate the policy you created using theElement Manager again to enable Switch Binding.

• If there is no Switch Binding activated in the Element Manager and Fabric Binding is activatedusing HAFM, Fabric Binding can be deactivated only by using HAFM. This is working asdesigned.

• If Switch Binding is activated using the Element Manager with an F-Port logged in to the McDATA4Gb SAN Switch that is not in the Switch Binding membership list (for example, an administratorcommand has not logged out the unwanted port), Fabric Binding cannot be activated usingHAFM.


Adding McDATA 4Gb SAN Switch to HAFM managementA McDATA 4Gb SAN Switch is added to HAFM management the same way as other M-Series switches,with one additional configuration requirement. The username and password for the Administrator accountof the switch must be configured in HAFM. The default username and password for a McDATA 4Gb SANSwitch are preconfigured for the switch in HAFM when the switch is added to HAFM management. If theswitch username and password have not been changed from the default settings, no change is required.The default user name is admin, and the default password is password.

To configure the username and password though HAFM:

1. Select Discover > Setup.

The Discover Setup dialog box is displayed.

2. Click Add.The Address Properties dialog box is displayed.

3. Enter the description, IP address, and subnet mask in the appropriate boxes.

4. Select the Product Type and Access tab.The Address Properties dialog box with Product Type and Access tabis displayed.

5. Enter the switch user ID and password for the Administrator account.

6. Click OK.

Formatting is required for new backup CD-RW disksIf you use a different CD-RW disk to backup other than the one provided with the HAFM appliance, youmust access the desktop of the HAFM appliance in order to enable the formatting of the new disk.Backups cannot be performed until the new disk is formatted.

Default zone is disabled by defaultThe default zone on the Directors, Edge Switches, and McDATA 4Gb SAN Switches is disabled by default.

You must cofigure zoning so that connected devices can communicate with the Director, Edge Switch, orMcDATA 4Gb SAN Switch.

Some IP addresses must be avoidedIf you use HAFM to manage other M-Series Fabric Directors and Edge Switches, do not use IP addressesin the following range:

192.168.0.0 through 192.168.0.255—This subnet is used internally by the HAFM Appliance. Using an IPaddress in this range causes the Call Home feature to function incorrectly.

Logging out of Microsoft Windows after access to HAFM appliance isrecommended

After you access the HAFM appliance desktop via a web browser using the TightVNC application, HPrecommends that you log out of Microsoft Windows before disconnecting your web browser access.This prevents unauthorized access to the HAFM appliance by someone using the TightVNC applicationto access the HAFM appliance. When the new user attempts to log into the HAFM appliance, theWelcome to Windows screen is displayed, and a Windows user name and password are required toaccess the HAFM appliance Windows desktop. HAFM remote client access does not require the HAFMappliance to be logged in to Windows.

12

Backup to networkWhen configuring backup to network using the Options dialog, the path for the backup output directorymust be in the folowing format:

\\Networkname\sharedfolder\subfolder

You must manually create a subfolder under a shared folder. HAFM backup does not recognize theshared folder; only the subfolder.

For complete information for configuring backup to a network drive, see the McDATA manual, EFCManager Software User Manual, part number 620-000170-060, Rev A.

Known issuesThis section describes the known issues related to the 1U HAFM appliance and the HAFM software.

External Loop diagnostic may show incorrect resultIf an External Loop test is run on a port and the required external loopback plug is not inserted into thatport, the test result should show the test as failed. However, it shows the test as incomplete. The Event Logcorrectly shows the Loopback diagnostics port failure event.

Port fencing issuesThe Alert bar may not count the correct number of ports blocked by fencing. More than one port may beblocked, however, only one is displayed.

Zoning restrictionsWhen you activate zoning with the maximum number of zones (2048) in a zoneset, the HAFMapplication may hang.

For Solaris, Linux, and AIX remote clients, a zoneset cannot be imported from a directory not containinga DTD file.

Workaround

Do not activate a zoneset with 2048 or more zones.

For Solaris, Linux, and AIX remote clients, add the zoneset XML file and either remove the reference to theDTD file or specify the full path to the DTD file.

Issue concerning HAFM remote client access to the HAFM appliance with dual LANconfiguration

When using a single public LAN connection at the HAFM appliance for all Ethernet communications, thesingle LAN connection operates correctly for the following functions:

• Directors and Edge Switches that the HAFM appliance manages• Computers seeking remote client access to the HAFM appliance• SAN management applications such as HP OpenView SAN Area Manager

When using two LAN connections (public and private) at the HAFM appliance, Microsoft Windowsand HAFM determine the following:

• Which LAN is to be the private LAN for communication between the HAFM appliance, and theDirectors and Edge Switches that the HAFM appliance manages?

• Which LAN is to be the public LAN for communication between the HAFM appliance andcomputers seeking remote client access to the HAFM appliance?


The issue arises because either LAN connection on the HAFM appliance can be the public LAN or theprivate LAN. Though the Directors and Edge Switches can be managed via either LAN, the publicLAN is the only one that can support remote client access. Thus, if one attempts to access the HAFMappliance via a remote client session and is unknowingly using what has been designated as the privateLAN, the remote session is not allowed. The IP address that the HAFM appliance has determined tobe the public LAN which supports remote client access, displays HAFM which displays after selectingSAN > Server Properties.

HAFM designates the public LAN as the first LAN detected whose IP address is not the reserved privatesubnet 10.x.x.x. Thus, if neither IP address is 10.x.x.x, the first LAN detected by HAFM is designatedas the public LAN. This order of detection is influenced by Microsoft Windows and is not guaranteed.

For a dual LAN configuration, both LANs must be connected when the HAFM appliance is booted up. Ifonly one is connected, HAFM interprets this as a single LAN configuration, and the connected LAN isdesignated as the LAN for remote client sessions.

Workaround

There are two ways to ensure the public and private designations of the LANs.

• If you use a private LAN IP address, this causes this LAN to be designated as the private LAN.You must also have the public LAN connection active when the HAFM appliance is booting up, orelse HAFM interprets this as a single LAN connection configuration, and the 10.x.x.x LAN isdesignated as the LAN for remote client sessions.

• You can configure a specified Ethernet interface on the HAFM appliance to be the public LAN (tolisten for remote client connections). To configure this feature, you must manually edit a file on theHAFM appliance to explicitly specify which IP address HAFM should use as the public LAN.

For detailed instructions, see HP StorageWorks HA-Fabric Manager User Guide.

If the public LAN IP address of the HAFM appliance is ever changed, this file must be edited again toreflect the new IP address.

Support for speed Auto-NegotiateAuto-negotiate is supported. However, HP recommends that the port speed for E_Ports (for Interswitchlinks, or ISLs) be set to a specific port speed (1Gb/sec, 2Gb/sec, or 4GB/sec as appropriate for thespeed of the Directors or Edge Switches being connected) instead of to Negotiate. Using a specificport speed decreases the time for a fabric build in response to some perturbation event in the fabric.Similarly, setting a specific port speed for N_Ports also decreases fabric build time. However, setting aspecific port speed for N_Ports is not required.

There are a few older HBA devices that do not always succeed in logging in to a switch port whenthe port speed is set for auto-negotiate.

Workaround

If an older HBA has difficulty logging into a switch port that has its port speed configured as Negotiate,configure that port speed to 1Gb/sec, 2Gb/sec, or 4GB/sec according to the operation speed of theHBA connected to that port.

Losing LAN connection to the HAFM appliance when logged in to HAFMIf the LAN connection to the HAFM appliance is lost while you are logged in to HAFM, the applicationmay stop.

Workaround

The LAN connection must be restored. Stopping HAFM has no impact on the Fibre Channel operationsof any Edge Switch or Director. Monitoring switch operations, logging events, and implementingconfiguration changes are interrupted only while the LAN is not connected.

14

Effect of no LAN connection to HAFM appliance during boot upIf the HAFM appliance has no LAN connection while booting up, but it is connected after booting up, theremote client sessions to the HAFM appliance are not allowed. Also, the IP address that is displayedwhen you select SAN > Server Properties is possibly incorrect.

Workaround

This is corrected by restoring the LAN connection and rebooting the appliance. Rebooting the appliancehas no impact on the Fibre Channel operations of any switch or Director. Only monitoring switchoperations, logging events, and implementing configuration changes are interrupted.

Setting HAFM appliance LAN to use DHCP is activated to wrong LANWhen setting the IP configuration for an older HAFM appliance (delivered with HAFM server boot/restore3.01.00 Rev A or earlier) using the LCD panel, setting DHCP configuration for LAN 1 causes LAN 2,not LAN 1, to be configured for DHCP. Similarly, setting DHCP configuration for LAN 2 causes LAN 1,not LAN 2, to be configured for DHCP.

Workaround

To configure LAN 1 for DHCP, select LAN 2 instead of LAN 1 at the start of the configuration procedure.If you wish to configure LAN 2 for DHCP, select LAN 1 instead of LAN 2 at the start of the configurationprocedure.

New sound files are not added to Event Manager immediatelyNew sound files do not display in the pull down menu of the Event Manager. They cannot be selected forinclusion in a rule. In order for the new sound files to be available, HAFM services must be stopped andrestarted, or the HAFM appliance must be rebooted. This is not disruptive to managed switches, butmonitoring and logging functions are interrupted while the appliance is rebooting.

HP-UX parameters may need to be changed before you run the HAFM clientThe following two HP-UX 11.0 kernel parameters are set too low for most Java applications. Usuallyyou will see this problem as a java.lang.OutOf MemoryError: unable to create newnative thread error. To resolve the issue, edit the following parameter limits:

• max_thread_proc—The maximum number of threads allowed in each process. The minimumvalue (and default) is 64, which is often too low for most Java applications. Set the value ofthe max_thread_proc higher than the expected maximum number of simultaneously activethreads. The maximum value is the value of nkthread.

• nkthread—The total number of kernel threads available in the system. This parameter is similarto the nproc tunable except that it defines the limit for the total number of kernel threadsable to run simultaneously in the system. The value must be greater than nproc. The default isapproximately twice that of nproc. The maximum is 30000. The suggested value of nkthreadis 2*max_thread_proc. If you have many Java processes running and each running processuses many threads, you should increase this value.

Ethernet port on HAFM appliance may encounter problemsWhen you use TightVNC to access the HAFM appliance and you are running HAFM locally on theHAFM appliance, the Ethernet port on the HAFM appliance can appear to hang. When the Ethernet portencounters 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.


Workaround

If this condition persists, it may be necessary to reboot the HAFM appliance. This is not disruptive tomanaged switches, but monitoring and logging functions are interrupted while the appliance is rebooting.

Disabled Show Route/Hide Route menu itemThe the Show Route menu item, from the Right-click on a port in the Product Tree, is disabled (grayed out)after installing HAFM on an HAFM Appliance that has not previously had HAFM installed. For example,installing on a restored HAFM Appliance or a replacement HAFM Appliance.

Workaround

Activate or reactivate the zoneset to enable the Show Route menu item, making it available from theRight-click menu.

Fibre Channel Logical Address error in the Zoning dialog boxThe Fibre Channel Logical Address may appear as 000000 on the zoning panel.

Workaround

Restart the HAFM client to display the correct Fibre Channel Address.

Unconnected ports showing different speedsIn the Port List View, unconnected ports may show speeds different than what has been configured.

Workaround

Restart the HAFM client to display the correct speed.

Inaccurate Node Descriptor informationNode Descriptor information in the Node Properties dialog may occasionally be inaccurate.

Workaround

Restart the HAFM client to display the correct information.

HAFM client for Solaris does not respond to short cut keysWhen using the HAFM client for Solaris, the client application does not respond to a small numberof shortcut keys.

Workaround

Choose one of the following workarounds:

• You may use an HAFM client for a different operating system.• For those shortcuts that are not available, you must use the mouse.

Node Nickname does not appear in Port Properties dialog boxThe Attached Port WWN field of the Port Properties dialog box does not display the nickname of theattached device if there is one configured to it.

Workaround

The nickname for the Attached Port WWN can be observed from the Node Properties dialog box.

16

HAFM Client cannot log in to a server through a Cisco router with strict ACLsAn HAFM Client cannot log in to a server when it is required to cross a Cisco router with strict ACLs.

Workaround

Remove the strict ACLs enforcement.

Topology view does not load with HAFM and a McDATA 4Gb SAN SwitchWhen using HAFM to manage a McDATA 4Gb SAN Switch for HP p-Class BladeSystem, if you performa logout instead of an exit, and if you log back as a different user, a problem is encountered and thetopology view does not load. The following error message appears:

SAN not loaded, no devices present

Workaround

Select exit from the menu instead of logout and relaunch the client.

Switch Binding dialog box does not display all the NPIV nodesIf NPIV is installed, the Switch Binding dialog box does not display all the NPIV nodes. The HAFM8.09.01 switch binding dialog displays only the first NPIV device.

Workaround

Use HAFM Basic instead. All the logged-in NPIV devices are displayed in the Switch Binding dialog box.

Determining current versionTo display the HAFM version, select Help > About HAFM from the HAFM menu bar.

Supersedes historyThis version supersedes HAFM 8.08.00.

Effective dateOctober 2006


HA-Fabric Manager release notes

Documents

Transcript of HA-Fabric Manager release notes