HP 316095-B21 - StorageWorks Edge Switch 2/24 Instruction Manual

HP StorageWorks
Director and Edge Switch release
notes
Part number: AA-RW8NA-TE/958–000276–009
First edition: (November 2005)

Legal and notice information
© Copyright 2003 — 2005-NaN 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.
This document contains proprietary information, which is protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The
information is provided “as is” without warranty of any kind and 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. HP shall not be liable for technical or editorial
errors or omissions contained herein.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Printed in the U.S.A.
Director and Edge Switch release notes

About this document
These release notes contain late-breaking and supplemental information for the Director
or Edge Switch products.
Be sure to read these release notes before installing a Director or Edge Switch product.
This information is available and periodically updated on the following HP web site:
http://www.hp.com/country/us/eng/prodserv/storage.html.
This section describes the following:
• Release notes information
• Intended audience
•Firmware0
8.01.00
• Other documentation
• Supported configurations
• Cable requirements
•Importantinformation
•Knownissues
Release notes information
These release notes describe the following:
• PortstateinHAFMBasicmaynotbecorrectunderspecific conditions
• Netscape browser may not allow setting of RADIUS server properties
• HSG80 transparent mode not recommended in SCSI-3 mode with HP-UX
• Error can occur if multiple UPM cards are hot inserted too quickly
• Support for speed Auto-Negotiate
• Certain applications do not receive SNMP traps
• Possible switch reset after power failure or power-down sequence
• Activating very large zone sets may fail when using OSMS and CT_AUTH
• Preferred Domain ID may not update automatically when configuring SANtegrity
features
Intended audience
These release notes are intended for customers who purchased Director or Edge Switch
products.
Director and Edge Switch release notes 1

Firmware 08.01.00
Firmware 08.01.00 isthelatestfirmware released with the Director or Edge Switch
product. Firmware 08.01.00 applies to the following M-Series Fabric Directors and
Edge Switches:
•HP StorageWorks Director 2/140
•HP StorageWorks Director 2/64
•HP StorageWorks Edge Switch 2/32
•HP StorageWorks Edge Switch 2/24
•HP StorageWorksEdgeSwitch2/16
•HP StorageWorks Edge Switch 2/12
•HP StorageWorks SAN Director 64
•Surestore Director FC-64
The firmware is available on the following HP web site: http://h18006.www1.hp.com/
storage/saninfrastructure.html.
For more information on upgrading firmware versions, see the appropriate Director
or Edge Switch service manual.
Other documentation
In addition to these release notes, HP provides additional documentation available on the
following HP web site: http://h18006.www1.hp.com/storage/saninfrastructure.html.
Supported configurations
Operation of multiple switches in a fabric topology is subject to certain topology limits.
Consider the impact of these limits when planning the fabric.
NOTE:
For more information about planning the fabric, see the SAN high availability planning
guide.
•Fabric elements—Each fabric element is defined by a unique domain ID that
ranges between 1 and 31; therefore, the theoretical limit of interconnected
Directors in a single fabric is 31. The supported limit of interconnected switches
inasinglefabricis24.Becausethisnumberissubjecttochange,contactyour
HP-authorized service representative for the current number of interconnected
switches supported in a single fabric.
•Inhomogeneous fabric—To determine if interoperability is supported for a
product, or if restrictions apply, see the product publications or contact your
HP-authorized service representative.
2

•Number of interswitch links (ISLs)—The maximum supported number of ISLs is
75% of installed ports for the Director 2/64, and 50% of installed ports for the
Director 2/140. The maximum supported number of ISLs for Edge Switches is all
available switch ports. For redundancy, at least two ISLs should connect any two
Edge Switch or Director-class fabric elements. Because this number is subject to
change, contact your HP-authorized service representative for the current number
of ISLs supported per Director or Edge Switch.
•Hop count—The Fibre Channel theoretical limit of ISL connections traversed (hop
count) in a single path through a fabric is seven. The maximum supported hop
count in a single path through a fabric is three. Because this number is subject to
change, contact your HP-authorized service representative for the current hop
count supported by a single fabric path.
The hop count is equal to the number of ISL connections traversed in a single
path, not the total number of ISL connections between devices.
Cable requirements
NOTE:
Optical cables for Director and Edge Switch products must be ordered separately.
For cables measuring up to 500 meters (1 Gb/s) or 300 meters (2 Gb/s), use multi-mode
Fibre Channel cables. For longer cables, use single-mode Fibre Channel cables.
Multi-mode optical cables are connected to short-wave optical transceiver modules in
a switch. Single-mode optical cables are connected to long-wave optical transceiver
modules in a switch. Multi-mode cables should use 50/125 optical fibers, and
single-mode cables typically use 9/125 optical fibers for distances up to 10 km.
Verify that connectors interfacing with the Director or Edge Switch products use LC duplex
connectors with a PC finish. In addition, the connector at the opposite end of the cable
must be of either LC or SC type, depending on the requirements of the connected device.
Important information
This section describes important information related to the Director or Edge Switch
product.
Minor code enhancements and fixes in firmware 08.01.00
This release of firmware 08.01.00 incorporates some minor code enhancements and
fixes,andisnotamandatoryupgrade,thoughHPrecommendsthatallDirectorsand
Edge Switches be upgraded to this version of firmware.
Advanced Fabric Diagnostics enhancements
The following enhancements have been made to Advanced Fabric Diagnostics features:
Director and Edge Switch release notes 3

•Port Fencing—Building on E_port or ISL Fencing introduced in firmware
07.xx.xx, Port Fencing policies have been enhanced to include F_ports to block
malfunctioning devices attached to M-Series Directors and Edge Switches. Users
can configure policies to detect ports that are violating security rules, as well as
link-level problems, such as a port that repeatedly exits the active-link state.
If a user-defined threshold is reached, the port is automatically blocked, and
the user is notified. Users can unblock ports manually to allow the ISL or
node to recover when the source of the problem is identified. Malfunctions in
connected hardware or Denial of Service (DoS) attacks can cause devices to
attempt repeated log-ins, which in extreme cases can impact fabric operations
adversely. Port Fencing can detect many of these conditions and prevent adverse
consequences.
Port Fencing is disabled by default. However, when enabled, default threshold
values are established for the different types of policies if the user has not
configured them manually. In most cases, the default policies provide a
reasonable level of protection, but further refinement may be necessary to
accommodate specificSANbehavior.
During planned maintenance or service operations, HP recommends disabling
appropriate policies to prevent fencing of ports from expected behavior.
New CLI commands support this enhancement. See the config.fenc-
ing.setParams command under CLI enhancements.
•Fibre Channel TraceRoute—Provides the ability to send a Fibre Channel
frame through the fabric and view its route to the destination and return to
the source. TraceRoute aids customers in troubleshooting device connectivity
problems by providing a map of routes through the fabric. See the
show.fabric.traceRoute command under CLI enhancements.
•Embedded Port Log—CLI Enhancements enable users to specify trigger points
that will start and stop events from being written to the Embedded Port Log.
These triggers consist of a data pattern and offset into the Fibre Channel frame.
CLI enhancements
The following commands and command parameters have been added to the CLI:
•config.fencing.setParams—Supported with new commands.
•config.fencing.showTypeTable—Supported with new types.
•config.switch—Commands added to the config.switch branch allow you
to enable/disable the API Interface, Web Interface, and Safe Zoning, and
commands to configure the FSPF cost of ISLs on the switch.config.switch
and the state of zoning request state change notifications (RSCNs).
•show.switch—Command added shows the IP address of the application that
is managing the switch/director and the method for computing the FSPF cost
for ISLs.
•config.snmp—Commands added to the config.snmp branch allow you
toconfigure a USM user entry in the User table, configure an entry in the
Security-to-Group table, configure v1 through v3 community strings, associate
4

and disassociate USM configuration values for trap recipients, configure entries
and set views to the Access table, and enable/disable SNMPv3.
•show.snmp—Commands that display the switch SNMP configuration,
Access table values, Target table values, users configured in the USM table,
Security-to-Group table, and values for the configured VACM views.
•show.epFrameLog.nowrap—Allows users to view the contents of the
nonwrapping portion of the Fabric Log.
•config.security.ssl—Includes commands to enable/disable SSL for the
Web Interface and API Interface.
•config.syslog—Commands added that configure and remove a syslog
server at a given index, enable/disable syslog, enable syslog support for a
specificlog,anddisplaysyslogconfiguration.
•show.port.opticHealth—Displays the overall optic health for all ports that
support enhanced digital diagnostics.
•show.port.opticData—Displays the overall optic health, enhanced digital
diagnostic data, and thresholds for a specified port.
•show.epFrameLog—Commands are available to set/disable trigger values
for the Embedded Port Frame Log and to display the current Embedded Port
Log settings.
•show.fabric.traceRoute—Shows the route between two nodes in a fabric.
HAFM Basic
The Embedded Web Server (EWS) management application has been redesigned to
ensure more consistency with the HA-Fabric Manager (HAFM) interface. Now called
HAFM Basic, this interface is manages products in a small SAN, while HAFM is
manages products in larger SANs.
HAFM Basic provides configuration support for Port Fencing policies, and enables you to
back up configuration settings to an XML file and then restore them by uploading the file.
Predictive optics monitoring
Through HAFM, HAFM Basic, and the CLI, users can monitor the health of the Fibre
Channel optics installed in Edge Switch and Director products. Optics identified as
degraded are flagged and can be replaced during a scheduled maintenance time,
preventing an unplanned outage. This diagnostic can reduce unplanned outages that
could have adverse effects on a fabric.
This feature allows manufacturer-defined limits for a digital diagnostic measurement to
be read from the installed optics and stored. Actual digital diagnostic measurements
are monitored periodically on optics and compared with the stored manufacturer
measurements to determine the overall health of the optics. When any of the digital
diagnostic measurements exceeds a threshold, an event is posted with the date/time,
port number, measurement that exceeded the threshold, and the threshold value that
was exceeded. Measurements include: temperature, voltage, current, transceiver power,
and receiver power.
Director and Edge Switch release notes 5

This feature is supported on all products except the Edge Switch 2/16 and Edge Switch
2/32. Predictive Optics Monitoring is not supported on the fiber port module (FPM) or
the firstrevisionoftheuniversalportmodule(UPM)ontheDirector2/64orDirector
2/140.
Support for this feature in the Edge Switch and Director management applications is
as follows:
•CLI—Includes a new command to display overall optic health for ports that
support enhanced digital diagnostics, and a command that displays the overall
optic health, enhanced digital diagnostic data, and thresholds for a specificport.
•HAFM—Displays events for ports that exceed threshold values.
•HAFM Basic—The Port List page includes a Health Status column that displays the
status of the installed optical transceiver (Normal, Warning, Alarm, or No Info).
Clicking the status in the column displays the health status, port type, and port
number. If the port has a digital diagnostics (DD) enabled optical transceiver,
product firmware displays reported temperature, voltage, current, transceiver
power, and receiver power. Optical transceivers also provide vendor-specific
threshold values.
Interswitch Link (ISL) cost configuration
ISL Cost Configuration gives users more control over how FSPF routing is determined for
aswitch
. Cost is a metric assigned to ISLs by the product’s Path Selection functionality to
determine the shortest path (or the path that takes the least amount of time for trafficto
travel) to a destination. A path with a lower cost is considered faster than a path with a
higher cost. Configuration is provided in HAFM Basic and CLI.
ISL Cost Configuration gives advanced users more control over their fabric configuration.
It allows them to establish all ISLs with equal cost factors, causing the switch not to
account for link speed when assigning flows to ISLs.
•CLI—The config.switch.islFSPFCost command configures the FSPF cost
of ISLs on the switch. When the islFSPFCostState command is set to ignore,
each ISL has the same FSPF cost; the actual FSPF cost is ignored. When set to
port, each ISL has a default cost, which depends on the speed of the port.
•HAFM Basic—Includes an ISL FSPF Cost Configuration field on the Switch
Parameterspagethatallowsuserstoconfigure FSPF cost of ISLs on the switch
By Port Speed or Ignore Port Speed.
•By Port Speed—When selected, the FSPF cost for each port depends on the
speed of the port. In this case, the cost is inversely proportional to the bit rate
of the ISL. The higher the bit rate, the lower the cost. The speed of the ISL is a
factor in determining the shortest path.
•Ignore Port Speed—When selected, every ISL on the switch has the same
FSPF cost. The number of hops is the primary factor in determining the
shortest path; the speed of the ISL is not considered.
6

Open Trunking with FMS
Open Trunking Load Balancing is now qualified in FICON environments where FICON
flows are rerouted, without encountering out-of-order frames.
Safe Zoning mode
When this mode is enabled through the CLI or HAFM Basic, zone merges are prohibited
if zone sets from different fabrics do not match, and the default zone (available in
Homogeneous Fabric mode only) cannot be activated. This prevents fabric merge
problems when zones are removed accidentally or when new unzoned devices are
added to the fabric when the default zone is enabled.
The following CLI and HAFM Basic enhancements support this mode:
•CLI—New config.switch.safeZoning command
•HAFM Basic—A Safe Zoning Mode check box on the Security menu
Security enhancements
The following enhancements have been made to Security features:
•Firmware 08.01.00 supports SSL connection for HTTP sessions managing
switches with HAFM Basic, as well as HAFM management sessions. This ensures
that all data transmitted between the switch and these management interfaces
is secure and encrypted. SSL complements the SSH support added to firmware
07.xx.xx for CLI management.
•Support for standard syslog logging functions. You can configure a central
logging service for all log events. Each log can be configured separately for
distribution to the syslog.
•The SNMP interface can be configured to operate in version 3 mode, and
support for authentication is provided. SNMPv3 provides additional security for
you to authenticate any management sessions on your M-Series Fibre Channel
switches. Consider the following:
•Theaut
hentication/privacy password (key) configured for an SNMPv3 user
on a switch is not localized. Therefore, the authentication/privacy password
configured in the SNMP management application must be a non-localized
password in ASCII format.
• Before enabling SNMPv3, ensure that all desired community strings are
configured for SNMPv3 access. If the community strings are not configured
for SNMPv3, then SNMP access will be lost.
QSA Rev 2 and RFCN support
With firmware 08.xx and later, standards-based support for the revision 2 of Query
Security Attributes (QSA) and new remote fabric change notifications (RFCNs) is
available.
Director and Edge Switch release notes 7

Previous QSA support provided a simple query facility in the switch for determining
the status of security attributes enforced on the switch. QSA Rev 2 allows a device to
register to receive RFCNs, so that it can be notified when a security change is made on
the switch or fabric. The registered device can then use QSA to query for the current
security attributes.
Performance enhancements
Firmware 08.01.00 provides significant improvements in nameserver response in
large fabric configurations. When a new zone set configuration is activated or a new
switch is added to the fabric, delays in nameserver responses are dramatically
reduced. This ensures prompt responses to nameserver queries are sent immediately
after applyingconfiguration or zoning modifications.
Documentation released with firmware 08.01.00
To support these products, McDATA Corporation (the product developer) and HP (the
product OEM) provide documentation. The HP documents include all information that
HP has incorporated into the products to date. The McDATA documents include only
basic product information.
Table 1 lists HP terminology and equivalents used in the McDATA documents.
Table 1 HP and McDATA terminology
HP term McDATA term
HP StorageWorks Edge Switch 2/12 Sphereon 4300 Fabric Switch
HP StorageWorks Edge Switch 2/16 Sphereon 3216 Fabric Switch
HP StorageWorks Edge Switch 2/24 Sphereon 4500 Fabric Switch
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
HAFM Basic (formerly, Embedded Web
Server or EWS)
EFCM Basic Edition (formerly, SANpilot)
HA-Fabric Manager (HAFM) Enterprise Fabric Connectivity Manager
(EFCM)
Firmware Enterprise Operating System (E/OS)
HAFM Appliance EFC Server
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.
8

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.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.01.00-09 (Notebook Server)
05.02.00-13 07.02.00-09 (HAFM Appliance)
05.05.00-12 None (Edge Switch 2/12)
06.01.00-18 07.01.00-09 (Notebook Server)
06.01.00-18 07.02.00-09 (HAFM Appliance)
06.01.00-18 08.02.00 recommended (HAFM Appliance)
06.02.00-22 07.01.00-09 (Notebook Server)
06.02.00-22 07.02.00-09 (HAFM Appliance)
06.02.00-22 08.02.00 recommended (HAFM Appliance)
07.00.00-84 07.01.00-09 (Notebook Server)
07.00.00-84 07.02.00-09 (HAFM Appliance)
07.00.00-84 08.06.00 recommended (HAFM Appliance)
07.01.02–4 07.01.00-09 (Notebook Server)
07.01.02–4 07.02.00-09 (HAFM Appliance)
07.01.02–4 08.06.00 recommended (HAFM Appliance)
08.01.00–14 07.01.00-09 (Notebook Server)
08.01.00–14 07.02.00-09 (HAFM Appliance)
08.01.00–14 08.08.00 recommended (HAFM Appliance)
NOTE:
HAFM 08.08.00 will be available in early December 2005.
Director and Edge Switch release notes 9

Prerequisites for installing and using firmware 08.01.00
If you are using HAFM, firmware 08.01.00 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.
If you are using HAFM to upgrade firmware, an Edge Switch 2/24 must be managed
with HAFM 8.08.00 or higher before upgrading to firmware 08.01.00. If you upgrade
to firmware 08.01.00 using an HAFM release before 8.08.00, the firmware upgrade
may fail. Firmware 08.01.00 introduced slightly more processor utilization, which can
cause the download to occasionally exceed HAFM’s timeout. In this situation, use the
switch’s HAFM Basic interface (formerly EWS) to upgrade firmware. HAFM 8.08.00
will be available early December 2005.
Firmware upgrades or downgrades should not be performed via HAFM Basic using
Internet Explorer 5.00.3315.1000x. If this operation is performed, the download
operation may not complete and may eventually time out, leaving the switch with the
previous version of 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. Although products can coexist in a fabric running different levels of firmware,
all products must be at the same major functional release level.
Upgradingfromanearlierversionoffirmware
Upgrading to firmware 08.01.00 is nondisruptive 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, HP recommends that you back up the Director or Edge
Switch configuration. See the HP StorageWorks Director Element Manager user guide
for more information. HAFM Basic also provides an option to print or save product
configuration to a file. See the HAFM Basic user guide for more information.
All products must be running firmware 07.01.03 or later before upgrading to 08.01.00.
If a switch is operating with a firmware level earlier than 07.01.03, you must upgrade
to 07.01.03 before installing 08.01.00.
Upgrades and downgrades are supported only within a major release, such as 08..xx.xx
to 08..xx.xx, or from one major release to the next, such as from 06.02.00 to 07.01.03
or 07.01.03 to 08.01.00. If HAFM Basic is used for upgrades and downgrades, and
this rule is not followed, errors occur and there may be a disruption to attached devices.
10

If upgrading firmware requires an upgrade from 04.xx.xx to 05.xx.xx in the process,
there are special considerations, as detailed in the section, Upgrading firmware on a
director from 04.xx.xx to 05.xx.xx.
A small number of early-shipped Surestore Director FC-64 units may display one of the
following messages when upgrading to firmware 05.02.00-13:
•HAFM—Firmware cannot be loaded due to insufficient CTP
memory.
•HAFM Basic—File System Error: Insufficient memory for new
firmware version.
This occurs only in certain units with CTP cards. Units with CTP2 cards do not have
this issue.
If you receive one of these messages during the upgrade, the firmware upgrade has
failed but the unit continues to run with the existing firmware. The upgrade process
checks for sufficient memory before activating the new firmware image. The firmware
upgradecannotcompletewithoutsufficient memory. Contact HP Customer Support if
you receive this message.
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 Edge
Switch at regular intervals. The polling process could occur during a restart period,
causing the application software to react adversely. As a solution, shut down those
applications driving inband requests during a firmware upgrade, and then restart the
applications after upgrade completion.
Upgrading firmware on a Director from 04.xx.xx to 05.xx.xx
An issue has been identified in release 04.xx.xx if the contents of the non-volatile random
access memory (NVRAM) on the active CTP are corrupted. Once the configuration
has been loaded, this corruption is not detected until an IPL/IML, power cycle, or
firmware code load. If the NVRAM on the active CTP has corrupted contents, the
firmware load can cause the configuration to reset to factory defaults, which can cause a
system outage. By using the following procedure to upgrade firmware, configuration is
preserved and a system outage is avoided. This issue has been resolved with firmware
05.02.00-13 and later.
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:
1. Upgrade HAFM software on the HAFM Server/Appliance to 07.01.00 (minimum).
Director and Edge Switch release notes 11

2. Download firmware 05.02.00-13 by selecting Firmware Library from the Product
Manager Maintenance menu.
3. Back up the Director configuration by selecting Backup & Restore Configuration
from the Product Manager Maintenance menu.
4. Using the Product Manager, execute a CTP swap:
a. From the Product/Element Manager Hardware view, verify that an amber
LED indicator is not displayed for either CTP card.
b. Right-click the CTP card you believe to be active, and then select FRU
Properties. VerifythatitistheactiveCTPcard.
c. Right-click the active CTP card and select Switchover.
The Director loses its Ethernet connection for a short time during the
switchover process.
When switchover occurs, the green LED illuminates on the backup CTP
card to indicate that it is now the active card.
NOTE:
You must have maintenance authorization rights to access the HAFM
Product/Element Manager menu options used in this procedure.
5. Upgrade the firmware to 05.02.00-13 on each Director by selecting Send in the
Firmware Library dialog box.
Upgrading firmware on an Edge Switch from 04.xx.xx to 05.xx.xx
An issue has been identified in release 04.xx.xx if the contents of the NVRAM on the
CTP are corrupted. Once the configuration has been loaded, this corruption is not
detected until an IPL/IML, power cycle, or firmware code load. If the NVRAM on the
CTP has corrupted contents, the firmware load can cause the configuration to reset to
factory defaults, which can cause a system outage.
Edge switch products already running 05.01.00 or later continually validate the NVRAM
configuration, so risk of an outage is extremely low. For Edge Switch products running
an earlier version of firmware, the risk of an outage increases due to the NVRAM
issue. If an outage compromises system integrity, HP recommends that the Edge Switch
firmware upgrade be a scheduled maintenance action that anticipates the failure of
switch connectivity. This issue has been resolved with firmware 05.02.00-13 and later.
To safely upgrade firmware on an Edge Switch:
1. Upgrade HAFM software on the HAFM Server/Appliance to 07.01.00 (minimum).
2. Download firmware 05.02.00-13 by selecting Firmware Library from the Product
Manager Maintenance menu.
3. BackuptheEdgeSwitchconfiguration by selecting Backup & Restore Configuration
from the Product Manager Maintenance menu.
12

4. Upgrade the firmware to 05.02.00-13 on each Edge Switch by selecting Send in
theFirmwareLibrarydialogbox.
Considerations for downgrading the firmware version
Directors or Edge Switches are not required to be offlinebeforeperformingafirmware
downgrade operation. Limitations to downgrades are clearly identified if there are any
limitations to performing the operation.
Before downgrading firmware, HP recommends that you back up the Director or Edge
Switch configuration. Refer to your Director or Edge Switch Element Manager user
guide for more information. EWS (HAFM Basic) also provides an option to print or
save product configuration to a file. Refer to your HAFM or EFCM Basic user guide for
more information.
Before downgrading to a release prior to 07.00.00, there can be only one user assigned
as Administrator and one user assigned as Operator for HAFM Basic and CLI. If
additional users were created, you must delete them before downgrading. Firmware
07.xx.xx does not allow the last user with Administrator rights in HAFM Basic or CLI to
be deleted.IfnoOperatoruserexists,firmware 07.xx.xx automatically creates one for
each interface during the downgrade. If more than one Administrator and/or one
Operator exists for HAFM Basic and/or CLI, when attempting to downgrade, you are
prompted to delete one of them first.
When downgrading to a release prior to 07.00.00, any modifications to the port
RX BB_Credit settings using the new enhanced port configuration capability must
be changed back to a configuration supported by older firmware. This enables the
configuration to comply with the previous releases configuration database. Firmware
07.xx.xx services verify compatibility and prevent downloads until the configuration
conflict is resolved.
For procedures to download firmware to the Edge Switch or Director using the HAFM
Element Manager interface or HAFM Basic interface, see the following:
•The Edge Switch or Director installation and service manual—Provides complete
procedures for obtaining firmware from the HP web site and downloading
firmware to the Edge Switch or Director using HAFM.
•TheEdgeSwitchorDirectorElementManageronlinehelpanduser
guide—Provide instructions for downloading firmwaretotheEdgeSwitchor
Director using the HAFM interface.
•HAFM Basic user guide—Provides procedures for downloading firmware to
the Edge Switch or Director.
•HAFM Basic online help—Provides procedures for downloading firmware to
the Edge Switch or Director.
Downgrading directly to a release prior to 07.00.00 from 08.01.00 is not allowed. To
downgrade to a release prior to 07.00.00, you must first downgrade to 07.xx.xx.
Director and Edge Switch release notes 13

Upgrades and downgrades are supported only from one major release to the next, such
as from 07.xx.xx to 08.01.00. If HAFM Basic is used for upgrades and downgrades, and
this rule is not followed, errors occur and there may be a disruption to attached devices.
Downgrading to release 06.xx.xx with the Preferred Path feature configured can
cause loss of this function. HP recommends that Preferred Path be disabled before
downgrading. To do this, deselect the Enable Preferred Path check box in the Configure
Preferred Paths dialog box.
NOTE:
The Director 2/140, Director 2/64, and Edge Switch 2/24 cannot be downgraded to
a version earlier than 04.01.00, and the Edge Switch 2/12 cannot be downgraded to
aversionearlierthan05.05.00.
Downgrades directly to 05.03.01 from 06.xx.xx are not concurrent when the
second-generation Edge Switch 2/24 is configured in Open Fabric operating
mode. In other words, downgrades in Open Fabric mode cannot be done with the
second-generation Edge Switch 2/24 online without disrupting port operations. Since
second-generation Edge Switch 2/24 switches cannot be downgraded to a version
earlier than 05.03.01, they must be configured in Homogeneous Fabric Interoperability
mode to remain concurrent. If this process is not followed, I/O through the switch may
be significantly disrupted or stopped. Recovery for this situation is accomplished by
reactivating the current zone set.
If you are installing a new or replacement second-generation Edge Switch 2/12 or Edge
Switch 2/24 in an existing 05.xx.xx fabric, HP recommends that you downgrade the
unit before installation.
Downgrading to 05.05.00 is supported only on first-generation Edge Switch 2/12
switches. Second-generation Edge Switch 2/12 switches can be downgraded only to
05.05.01. Second-generation Edge Switch 2/24 switches can be downgraded only
to 05.03.01.
If a Director 2/140 in a multiswitch fabric is downgraded to a version earlier than
06.02.00, ISLs can 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.00 is attempted,
butyoucancontinuewiththedowngradeifdesired.
NOTE:
The warning message is displayed when downgrading any model from 06.02.00, but
only applies to downgrade operations for the Director 2/140.
14

HAFM upgrade required for firmware 08.xx.xx
To upgrade to firmware 08.01.00, you must first upgrade the HAFM software to
07.01.00-9(minimum)ifyouareusingtheNotebookHAFMServertomanagethe
Director or Edge Switch. The HAFM software is contained on the HP StorageWorks
ha-fabric manager documentation and software CD (Part Number 516-000024-820).
An upgrade kit to HAFM 07.01.00-9 is also available (Part Number 320908-B22) for
owners of a licensed version of HAFM. This HAFM upgrade is also available on the
following HP web site: http://h18006.www1.hp.com/storage/saninfrastructure.html.
If you are using the 1U rack-mount HAFM Appliance to manage the Director or Edge
Switch, the minimum HAFM version required is 07.02.00-9, which is the minimum version
installed. This HAFM software is contained on the HP StorageWorks ha-fabric manager
documentation and software CD (Part Number 516-000024-720).
The previous minimum versions of HAFM allow you to manage Directors or Edge Switches
running 08.01.00 firmware. However, to use all the new features and enhancements,
you need to upgrade HAFM to 08.08.00, which runs only on the 1U rack-mount HAFM
Appliance. HAFM 8.08.00 will be available in early December 2005.
As an alternative, you can perform the firmware upgrade directly to the Director or Edge
Switch using the switches HAFM Basic.
Please contact your local HP technical resource if you need to obtain a new HAFM
versionortoconfirm compatibility with devices in your SAN before upgrading to this
firmware.
For more information on upgrading software versions, see the HP StorageWorks
HA-Fabric Manager user guide. The features of this software version are described in
the documents listed in Other documentation.
Default zone is disabled by default
The default zone on the Director and Edge Switches disabled by default. Zoning must be
configured in order for devices connected to the Director or Edge Switch to communicate.
Some IP addresses must be avoided
If you use HAFM to manage other M-Series Fabric Directors and Edge Switches, do not
use IP addresses in the following range:
192.168.0.0 through 192.168.0.255—This subnet is used internally by the HAFM
Appliance. Using an IP address in this range causes the Call Home feature to function
incorrectly.
Zoning limits
Table 3 lists the supported zoning limits for the Edge Switches and Directors.
Director and Edge Switch release notes 15

Table 3 Zoning limits
Zoning parameter Maximum value
Number of zone members in a zone 2048
Number of zones in a zone set 1024
Number of unique zone members in a zone set 2048
Total number of zone members in a zone set (where a zone
membercanbeinmultiplezones)
4096
Characters per zoning name 32
Number of unique zone members in HAFM Zoning Library 2048
Number of zones inHAFMZoningLibrary 1024
Number of zone sets in HAFM Zoning Library 64
Number of end ports 1024
Number of devices supported (including loop devices) 1024
Using the same firmware level
All Directors and Edge Switches in the same fabric should have the same firmware level
installed—whether 1Gb/s, 2Gb/s, or 4Gb/s capable—to ensure that this firmware
operates correctly.
TheEdgeSwitch2/12hadaninterimfirmware 05.00.00-12. This firmware cannot be
used for any other Edge Switch or Director. This interim version is compatible with
the M-Series firmware05.02.00-13usedfortherestoftheM-Seriesfabricproducts.
Firmware 08.01.00 is common for all M-Series fabric products, including the Edge
Switch 2/12.
Firmware 06.02.00-22 provides support for second-generation Edge Switch 2/12 and
Edge Switch 2/24 switches. This is the minimum M-Series firmware supported on the
second-generation Edge Switch 2/12 and Edge Switch 2/24.
Reinstalling feature licenses
Feature licenses (or keys) must be reinstalled after performing a factory reset on an
Edge Switch or Director to regain use of the licensed features (for example, SANtegrity
Binding).
CTP controls port lights
Port lights on the Edge Switches and Directors are controlled by the CTP. Certain activities
such as firmware updates, IPLing the CTP, or switching over to the backup CTP (Director)
16

can cause these port lights to extinguish momentarily until control is reasserted by the
CTP. The actual Fibre Channel traffic is not affected during these times.
Full-fabric capability for Edge Switch 2/12
Unlike other Edge Switch and Director products, a product feature enablement (PFE) key
controls Edge Switch 2/12 E_Port-to-E_Port connections. After purchasing and installing
the feature key, you can configure for E_Port connections on any of the active ports.
The feature key includes distance support. With firmware 06.00.00 and later, the Edge
Switch 2/12 ships with five BB_credits allocated to each port. After activation of the
Full Fabric feature on a switch, each port has 12 BB_Credits allocated to support up to
12 km links at 2 Gb/s speed.
Known issues
This section describes the known issues related to the Director 2/64 and Director 2/140.
Port state in HAFM Basic may not be correct under certain conditions
Port state information may not update correctly in HAFM Basic when an unresponsive
node becomes active again. The port may report Invalid Attachment even if it is
active and trafficisflowing across the link.
Workaround
The display of port state can be corrected by blocking and then unblocking the port.
Note that this is disruptive to the connected node, and should only be done as part of
scheduled maintenance.
Netscape browser may not allow setting of RADIUS server properties
You may not be able to set RADIUS server properties using the Security > RADIUS Server
page using Netscape to access HAFM Basic.
Workaround
Use another browser such as Microsoft Internet Explorer.
Restore configuration for Edge Switch 2/24 does not complete successfully if
there are a large number of zones
Restore configuration does not complete successfully if the backup switch configuration
contains more than 2,047 zones. This should not affect most customers, as this is a
large number of zones.
Director and Edge Switch release notes 17

Workaround
None.
ErrorcanoccurifmultipleUPMcardsarehotinsertedtooquickly
Event 507, Loopback diagnostics port failure, may occur after hot insertion of multiple
UPM cards in the Director 2/64. This has only been encountered when cards are
inserted at one-minute intervals. This is caused by timing of diagnostics that are run on
the newly inserted UPM cards.
Workaround
To avoid this problem, wait longer than one minute between hot insertion of each UPM
card. HP recommends waiting at least two minutes between UPM card hot insertions. If
you encounter this error, reseat the UPM card.
Support for speed Auto-Negotiate
Auto-negotiate is supported. However, HP recommends that the port speed for E_Ports
(for Interswitch Links, or ISLs) be set to a specificportspeed(1Gb/sec or 2Gb/sec,as
appropriate for the speed of the Directors or Edge Switches being connected) instead
of to Negotiate.Usingaspecific port speed decreases the time for a fabric build in
response to some perturbation event in the fabric. Similarly, setting a specificportspeed
for N_Ports also decreases fabric build time. However, setting a specificportspeedfor
N_Portsisnotrequired.
There are a few older HBA devices that do not always succeed in logging in to a switch
port when the port speed is set for auto-negotiate.
Workaround
If an older HBA has difficultyloggingintoaswitchportthathasitsportspeed
configuredasNegotiate,configure that port speed to 1Gb/sec or 2Gb/sec according to
the operation speed of the HBA connected to that port.
Certain applications do not receive SNMP traps
With SNMPv3, users with authentication protocol MD5 do not receive SNMP traps.
MGSoft 8.0.0 receives the traps, but MGSoft 9.0.0 does not.
Workaround
Do not useMD5orMG-SOFT9.0.0toreceiveSNMPtraps.
18