HP StorageWorks 2/140 - Director Switch Instruction Manual

HP StorageWorks
Director release notes
Part number: AA–RTDVH–TE/958–000276–008
Eighth 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.
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 contained in this document is subject to change without notice.
Microsoft®, MS Windows®, Windows®, Windows NT®, and Windows Server® are U.S. registered trademarks of
Microsoft Corporation.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information
is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard
Company products are set forth in the express limited warranty statements for such products. Nothing herein should be
construed as constituting an additional warranty.
Printed in the U.S.A.
Director release notes

About this document
These release notes contain late breaking and supplemental information for the Director
2/64 and Director 2/140.
Be sure to read these release notes before installing a Director 2/64 and Director 2/140.
This information is periodically updated and available on the following HP web site:
http://www.hp.com/country/us/eng/prodserv/storage.html.
This section describes the content reflected in this document, including:
• Release notes information
• Intended audience
•Firmwarev
ersion 07.01.02-4
• Other director documentation
•CD-ROMdirectorystructure
• Supportedconfigurations
• Cable requirements
•Importantinformation
•Knownis
sues
Release notes information
These release notes cover the following major topics:
• HSG80 transparent mode not recommended with controller in SCSI-3 mode
with HP-UX operating systems
• HSG80 transparent mode not recommended with controller in SCSI-3 mode with
• ISL disconnect causes NOS error with the OpenVMS operating systems
• Support for speed Auto-Negotiate
• Ports may accumulate spurious events
• Possible switch reset after power failure or power off sequence
•SNMPissues
Intended audience
This document is intended for customers who purchased the Director 2/64 or Director
2/140.
Firmware version 07.01.02-4
Firmware 07.01.02-4 is the latest (as of this date), firmware released with the
Director 2/64 and Director 2/140. The latest firmware is available on the following HP
web site: http://h18006.www1.hp.com/storage/saninfrastructure.html.
Director release notes 1

For more information on upgrading firmware versions, refer to the appropriate
HP StorageWorks director service manual. The features of this firmware version are
detailed in the following manuals.
Otherdirectordocumentation
In addition to these release notes, HP provides the following corresponding information:
•HP StorageWorks Director Element Manager Licensing Instructions,
AA-RVHAA-TE/958-000282-000
•HP StorageWorks Director Torque Tool Caution Flyer,AA-RTDEC-TE/958-
000282-002
•HP StorageWorks Director Power Cord Advisory, AA-RTDMC-TE/958-000279-
002
•HP StorageWorks Universal Port Module Kit Installation Instructions,
AA-RSS2D-TE/958-000281-002
•HP StorageWorks Director 2/140 Installation Guide,AA-RTDSD-TE/958-
000275-003
•McDATA Intrepid Director 6140 Installation and Service Manual,
620-000157-410
•HP StorageWorks Director Element Manager User Guide,AA-RTDUD-TE
•HP StorageWorks Director 2/64 Installation Guide,AA-RSNGE-TE/958-
000289-003
•McDATA Intrepid Director 6064 Installation and Service Manual,
620-000108-920
•HP StorageWorks M-Series Rack Mount Kit Installation Instructions,
AA-RQZPE-TE/958-000292-002
•McDATA Enterprise Operating System Command Line Interface User Manual,
620-000134-720
•McDATA EOS SNMP Support Manual, 620-000131-620
•McDATA Products in a SAN Environment Planning Manual, 620-000124-500
•HP StorageWorks SAN Design Guide, AA-RMPNT-TE
•McDATA SANpilot User Manual, 620-000160-230
•HP StorageWorks HA-Fabric Manager User Guide,AA-RS2CF-TE
•HP StorageWorks HA-Fabric Manager Transition Guide,AA-RV1MB-TE
•HP StorageWorks HA-Fabric Manager Appliance Installation Guide,
AA-RU5FC-TE/958-000324-002
•HP StorageWorks HA-Fabric Manager Release Notes,AA-RUR6E-TE/958-
000288-009
•HP StorageWorks Director and Edge Switch Glossary,AA-RU5JB-TE
•HP StorageWorks C-FCSWAPI SDK Bridge Agent Installation Instructions,
AA-RVJ1B-TE/958-000405-001
2

•HP StorageWorks Director release notes, AA-RTDVG-TE/958–000276–007
CD-ROM directory structure
The HP StorageWorks director documentation and firmware CD contains the following
items:
•Manuals.pdf—HP StorageWorks Director 2/64 and Director 2/140
Documentation; links to the following documents and search function
•Documents
•README.TXT—HP document structure; late-breaking doc changes
•AA-RTDSD-TE/
958-000275-003—HP StorageWorks Director 2/140
Installation Guide
• 620-000157-410—McDATA Intrepid Director 6140 Installation and Service
Manual
•AA-RTDUD-TE—HP StorageWorks Director Element Manager User Guide
• AA-RSNGE-TE/958-000289-003—HP StorageWorks Director 2/64
Installation Guide
• 620-000108-920—McDATA Intrepid Director 6064 Installation and Service
Manual
• 620-000134-720—McDATA Enterprise Operating System Command Line
Interface User Manual
• 620-000131-620—McDATA EOS SNMP Support Manual
• 620-000124-500—McDATA Products in a SAN Environment Planning
Manual
• AA-RMPNT-TE—HP StorageWorks SAN Design Guide
• 620-000160-230—McDATA SANpilot User Manual
•AA-RU5F
C-TE/958-000324-002—HP StorageWorks HA-Fabric Manager
Appliance Installation Guide
•AA-RS2CF-TE—HP StorageWorks HA-Fabric Manager User Guide
•AA-RV1
MB-TE—HP StorageWorks HA-Fabric Manager Transition Guide
•AA-RU5JB-TE—HP StorageWorks Director and Edge Switch Glossary
• AA-RVJ1B-TE/958-000405-001—HP StorageWorks C-FCSWAPI SDK Bridge
Agent Installation Instructions
•Firmware
•HPQ_MSF_v07.00.00-84.bin—HP StorageWorks M-Series firmware
•firmwareupdate.txt—Instructions for updating firmware
•Acrobat
•RP505ENU.EXE—Windows installation fileforAcrobatReader5.0with
Search
Director release notes 3

Supported configurations
Operation of multiple switches in a fabric topology is subject to the following topology
limits. Consider the impact of these limits when planning the fabric.
NOTE:
For more information about planning the fabric, refer to HP StorageWorks 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, refer to the product publications, or contact your
HP authorized service representative.
•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. For redundancy, at least two ISLs should connect any
two 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.
•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.
4

Cable requirements
NOTE:
Optical cables for the Director 2/64 and Director 2/140 must be ordered separately.
For cables measuring up to 500 meters (1 Gbps) or 300 meters (2 Gbps), 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 2/64 and Director 2/140 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 2/64 and
Director 2/140.
Minor Code Enhancements and Fixes in fw 07.01.02-4
This release of firmware version 07.01.02-4 incorporates some minor code enhancements
and fixes, and is not a mandatory upgrade, though HP recommends that all directors
and edge switches be upgraded to this version of firmware. Firmware release 07.01.02-4
is based on firmware 07.00.00-84, and contains all fixes included in that version and
prior releases. The following are now incorporated in firmware version 07.01.02-4.
Directors take new action upon detecting a failed UPM port module
A particular type of failure in director UPM port modules could be disruptive to other
port modules in a director. In the release of firmware 07.01.02-4, the action taken by
the director upon detecting this type of failure was changed to power off the failed port
module to prevent it from affecting other working port modules.
Embedded Web Server zoneset activation timeout issue resolved
Under certain conditions, the Embedded Web Server (EWS) would sometimes not allow
theZoneManagersubsystemenoughtimetoprocessaconfiguration change request.
This would cause EWS to time out when waiting for the Zone Manager to respond.
When this occurred, the Zone Manager could hang indefinitely, preventing any further
zone activities from any management location. This timeout issue has been fixed.
Director release notes 5

Zonesets containing domain/port number zones while in Open Fabric interop mode no longer
cause zoning to hang
When directors and edge switches in a fabric were configured for Open Fabric 1.0
interop mode, and the fabric’s zoneset contained a zone with members defined by
domain/port number instead of World Wide Name, activating changes to the zoneset
could cause the Zone Manager to hang. When this occurred, the Zone Manager could
hang indefinitely, preventing any further zone activities from any management location.
It should be noted that domain/port number zones are not supported in Open Fabric
1.0 interop mode, and are ignored. The Zone Manager will no longer hang under these
conditions, and these zones are still ignored in Open Fabric 1.0 interop mode.
Occasional Ethernet hang issue is resolved
Under certain conditions, the Ethernet communications could intermittently hang on
director 2/140, edge switch 2/24, and edge switch 2/12. This issue has been
corrected.
Features not supported in this release
The following director and edge switch feature is not supported in this release:
•SANtegrity Authentication
The following HAFM features are not supported in this release:
•SANtegrity Security Center
•Group Configuration Manager
These features are described in the documentation released with firmware 07.00.00 and
HAFM 08.06.00. Some of these features may be available in a future release.
6

Documentation released with firmware 07.00.00 and HAFM 08.06.00
To support these products, we are providing documentation from both McDATA
Corporation (the product developer) and from HP (the product OEM). The HP documents
include all information HP has incorporated into the products to date. The McDATA
documents include only the basic product information.
Table 1 shows HP terminology and McDATA Corporation 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
Embedded Web Server (EWS) SANpilot
HA-Fabric Manager (HAFM) Enterprise Connectivity Manager (EFCM)
Firmware Enterprise Operating System (E/OS)
HAFM Appliance EFC Server
Director release notes 7

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.
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-2207.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)
8

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. Although products may co-exist in a fabric running different levels of firmware,
all products must be at the same major functional release level.
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. Refer to your HP StorageWorks Director Element Manager
User Guide for more information. Embedded Web Server (EWS) also provides an
option to print or save product configuration to a file. Refer to the HP StorageWorks
Embedded Web Server User Guide for more information.
All products must be running firmware 06.00.00 or later before upgrading to
07.01.02-4. If a switch is operating with a firmware level earlier than 06.00.00, you
mustupgradeto06.xx.xxbeforeinstalling07.01.02-4.
Upgrades and downgrades are supported only from one major release to the next, such
as from 06.xx.xx to 07.01.02-4. If EWS is used for upgrades and downgrades, and this
rule is not followed, errors occur and there may be a disruption to attached devices.
If upgrading to firmware 06.02.00-22 requires you to 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 receive one of the
following messages when they upgrade to firmware 05.02.00-13:
•HAFM—Firmware cannot be loaded due to insufficient CTP memory.
•EWS—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 get one of these messages during the upgrade, the firmware upgrade failed, but
the unit continues working with the existing firmware without an interruption in service.
Director release notes 9

The upgrade process checks for sufficient memory before activating the new firmware
image. The firmware upgrade does not complete without sufficient memory. Please
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 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, then restart the applications after
upgrade completion.
Upgrading firmwareonadirectorfrom04.xx.xxto05.xx.xx
An issue has been identified in release 04.xx.xx if the contents of the nonvolatile storage
(NVRAM) on the active CTP become corrupted. Once the configuration has been
loaded, this corruption is not detected until an IPL/IML, power cycle, or firmware code
load. If theNVRAMintheactiveCTPhascorruptedcontents,thefirmware load can
cause the configuration to reset to factory defaults, which could cause a system outage.
By using the following procedure to upgrade firmware, configuration is preserved and a
system outage is avoided. This issue was corrected 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, 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. Using the Product Manager, execute a CTP swap:
a. From 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. From the right-click pop-up
menu, choose FRU Properties. Verify that it is the active CTP card.
c. Right-click the active CTP card and choose Switchover from the pop-up
menu.
The director loses its Ethernet connection for a short period during the
switchover process.
10

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 firmwareto05.02.00-13oneachdirectorusingtheSend option on
theFirmwareLibrarydialogbox.
Considerations for downgrading the version of firmware
Directorsoredgeswitchesarenotrequiredtobeofflinebeforeperformingafirmware
downgrade operation. Limitations to downgrades are clearly identified if there are any
limitations to performing the operation.
Before downgrading firmware, it is highly recommended that you back up the director or
edge switch configuration. Refer to your HP StorageWorks Director Element Manager
User Guide for more information. EWS also provides an option to print or save product
configuration to a file. Refer to your HP StorageWorks Embedded Web Server User
Guide for more information.
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 more than one
Administrator and/or one Operator exists for Embedded Web Server and/or CLI, when
attempting to downgrade you are prompted to delete one of them first.
When downgrading to a release prior to 07.01.02-4, 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.Thisisnecessarytoallow
the configuration to comply with previous releases’ configuration database. Firmware
07.01.02-4 services verify compatibility and prevent downloads until the configuration
conflict is resolved.
For procedures to download firmware to the switch or director using the HAFM Element
Manager interface or EWS interface, refer to the following:
•The switch or director Installation and Service Manual. This publication
provides complete procedures for obtaining firmware from the HP web site and
downloading firmware to the switch or director using HAFM.
•The switch or director Element Manager online help and User Manual. These
includes instructions for downloading firmware to the switch or director using the
HAFM interface.
Director release notes 11

•EWS User Manual. This provides procedures for downloading firmware to the
switch or director.
•EWS online help. This provides procedures for downloading firmware to the
switch or director.
Downgrading directly to a release before 06.00.00 from 07.01.02-4 is not allowed. To
downgrade to a release before 06.00.00, you must first downgrade to 06.YY.ZZ.
Upgrades and downgrades are supported only from one major release to the next, such
as from 06.xx.xx to 07.01.02-4. If EWS 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 6.0 with the Preferred Path feature configured could cause loss
of this function. HP recommends that Preferred Path be disabled before downgrading.
To do this, deselect the check box for Enable Preferred Path in the Configure Preferred
Paths dialog box.
NOTE:
The Director 2/140 and the Edge Switch 2/24 cannot be downgraded earlier than
04.01.00, and the Edge Switch 2/12 cannot be downgraded earlier than 05.05.00.
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.00 is attempted, but you can continue
with the downgrade if desired.
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.
Firmware downgrades should not be performed using EWS and Internet Explorer
v5.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.
12

HAFM upgrade required for firmware version 07.xx.xx
To upgrade to firmware 07.01.02-4, you must first upgrade the HAFM software to
07.01.00-9 minimum, if you are using the notebook HAFM server to manage the
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 license for previous versions. 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 07.01.02-4 firmware, but to be able to use all the new features and
enhancements, you need to upgrade HAFM to 08.06.00, which runs only on the 1U
rack-mount HAFM appliance.
As an alternative, you can perform the firmware upgrade directly to the director or edge
switch using their EWS.
Please contact your local HP technical resource if you need to obtain a new HAFM
version.
Please contact your local HP technical resource to confirm compatibility with devices
in your SAN before upgrading to this firmware version.
For more information on upgrading software versions, refer to the HP StorageWorks
HA-Fabric Manager User Guide. The features of this software version are detailed in the
accompanying manuals listed in section Other director documentation.
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. In the case where devices become available or
unavailable, RSCNs are sent only to the devices in the same zone. Zoning changes,
however, trigger RSCNs to be sent to all of the devices in the fabric. As fabrics grow
larger and larger, the quantity of RSCNs from zoning changes can create congestion
and disrupt devices, causing them to pause normal activity to determine the status of
the other devices. This can occur even if the new device is not zoned to talk to the
other devices in the fabric.
Director release notes 13

With the Zone FlexPar feature enabled, RSCN messages for a zoning change are
handled like RSCNs for availability/unavailability changes. Specifically, RSCNs are
restricted to only those devices sharing at least one common zone with the device that
changed. This way, only devices that are impacted by the change in connectivity
receive RSCNs.
TheZoneFlexParfeatureisavailableinbothOpenFabric1.0andHomogeneous
Fabric 1.0 Interop modes, as well as in environments with loop-attached devices. In
Homogeneous Fabric 1.0 mode, the default zone is treated like any other zone, and
RSCNs are sent only to the affected devices if the default zone is enabled or disabled. A
PFE key is not required for the Zone FlexPar feature, and it can be enabled or disabled
through CLI for a specific switch. When upgrading to firmware 07.01.02-4 or installing
anewswitchwithfirmware 07.01.02-4 the feature is enabled by default, allowing it
to work immediately. If the Zone FlexPar feature is not enabled on all switches in the
fabric, the restricted RSCN distribution only applies for devices attached to switches
with the feature enabled.
Enhanced SANtegrity Security Suite
SANtegrity Security Suite enhanced features include authentication support for device
login, interswitch connections and management interfaces. The Secure Access features
are included as a standard part of the SANtegrity Security Suite in firmware 07.01.02–4.
Standard features
The following SANtegrity features do not require a license or SANtegrity Binding.
•CHAP Authentication for HAFM/SWAPI—Thisprovidesauthenticationof
connections from the HAFM appliance service processor and SWAPI Direct
Connect. This ensures that requested HAFM management sessions or SWAPI
Direct Connect sessions are from a trusted source.
•Encryption of Passwords and Secrets Shared with HAFM—All secrets and
password information are passed in encrypted format for greater security.
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. This means that several switches can be configured to use a
single RADIUS server.
•Prompted Change of EWS and CLI Passwords from Default—This prompts users
to modify the password settings for both the CLI and EWS interfaces the first time
they log in using either of these interfaces.
14

•RBAC Phase I: Enhanced User Rights Configuration—RBAC is role based access
control. This is the first phase of more comprehensive role-based access control
planned for the CLI and EWS interfaces. Multiple users can now be configured
for EWS or CLI, or both, through either interface. This allows users to configure
additional user name/password combinations.
•SSH for CLI—Secure Shell (SSH) provides an encrypted connection, as an
alternative to Telnet, to secure CLI access to switches and directors.
•Enhanced Maintenance Port Security—This allows users to enable enhanced
authorization on the maintenance port, which is the switch or director RS-232
connection. Enhanced Authorization mode enforces stronger security policies,
requiring users to change the well-known password to a case- sensitive private
password the first time they use the maintenance port. Subsequent access by
service personnel requires log in through the private customer-level access.
•Security Log—TheSecurityLogisanewlogavailableinEWS,CLI,andHAFM
that records various events concerning the integrity of a switch. This includes
authorization or authentication problem detection, and approved and invalid
access attempts. Each log entry provides an event number or reason, a date/time
stamp, a trigger level (a type of security event severity), an event count, and a
category and data pertaining to the specific event. The log wraps at 200 entries.
This log provides customers with details to track down attempted security threats
and identify the source of problems that might jeopardize the switch integrity.
•IP Access Control List—This allows users to establish a list of IP addresses from
which the switch is allowed to accept connections. This prevents users who
have access to the Ethernet LAN from attempting to access the Fibre Channel
switches. Connection attempts from unauthorized IP addresses are ignored by
the switch, making it appear that no device is connected. This is primarily
intended for environments that are not on a private, inaccessible subnet, such as
when installed in most cabinet configurations with a dual-NIC HAFM appliance
processor.
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.
ISL Fencing
Also called Port Fencing, this feature allows customers to set up policies for blocking
an ISL when problems occur that cause an ISL to “bounce” or repeatedly attempt to
establish a connection. Any time an ISL is brought up or down, a fabric rebuild occurs,
whichcancausedisruptioninsomeenvironments.ISLFencingwilllessenthelikelihood
of having a problematic ISL connection disrupt a SAN.
Director release notes 15

To configure this feature, users set policies with thresholds based on the number of
port events occurring during a set time period. If a port generates enough events to
exceed the policy threshold, the port is automatically blocked and the user is notified.
Transmit and receive traffic is disabled until the user can investigate, solve the problem,
and manually unblock the port.
Embedded Audit Log
The Audit log is a new log available through CLI and EWS. This is not the same Audit
Log available through HAFM. The log records all configuration changes to the switch to
provide data for analyzing problems caused by configuration changes.
Embedded Port Log
The Embedded Port Log is a new log that records all Fibre Channel trafficfromorto
the embedded port. This log is actually implemented as two logs, one that allows entry
wrapping and one that stops adding entries when filled. The logs allow filtering based
on Class F frames, as well as by port number, to isolate specificeventsorproblems.
This feature is intended for advanced users to diagnose and troubleshoot trafficproblems
withinaSAN.TheEmbeddedPortLogisavailableviaEWS,CLI,andHAFM.
Embedded Fabric Log
The switch-based fabric log records events related to the following services:
•Fabric Controller
•Path Selection
•Login Server
•Name Server
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.
Default zone is disabled by default
The default zone on the Director 2/64 and the Director 2/140 is disabled by default.
Zoning must be configured in order for any devices connected to the director to
communicate.
16

Some IP addresses must be avoided
If you use HAFM to manage other M-Series Fabric directors and edge switches, when
you select IP addresses for edge switches, directors, and for the HAFM appliance, do
not use IP addresses in the following range:
192.168.0.0 through 192.168.0.255—This subnet is used internally to the HAFM
appliance. Using an IP address in this range causes the call-home feature to function
incorrectly.
Hard zoning
Hard zoning is a security enhancement introduced in firmware 05.01.00-24 that
prevents ports from accessing devices outside their zones. Hard zoning is enabled
by default when using firmware 05.01.00-24 or greater and cannot be disabled. All
HP-approved host bus adapters (HBAs) limit access to devices within their zones, so you
will not see a change in fabric behavior unless you are using nonstandard HBAs. Hard
zoning improves security against intruders that load nonstandard HBA drivers.
Hard zoning is compatible with legacy zone definitions, including World Wide Name
(WWN) and port zoning. You can use your existing zones and zone sets without any
changes. There are no changes to the zoning interfaces, so you do not need to modify
your zone management practice, modify your documentation, or retrain Storage Area
Network (SAN) administrators.
Hard zoning controls access at the ingress port. When a port attempts to send a frame
to a destination outside its zones, the frame is blocked. A Class 2 frame is fabric
rejected, and a Class 3 frame is dropped.
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. Devices will have no
warning when zones change and will not automatically update their zoning information.
The ability to suppress RSCNs is disabled (check box is not selected) by default. This
feature can be configuredthroughHAFM,EWS,andCLI.
SNMP changes
Firmware 07.01.02-4 supports the following management information base (MIB)
versions on all products:
•Fabric Element MIB: 1.1
•MIB-II MIB: RFC-1213, non-implemented sections are not included
Director release notes 17

•FCEOS MIB: 2.0
•SNMP Framework MIB: RFC-2271 (1997/09/30)
•FA MIB: 3.0
•FA MIB: 3.1
SNMP requests can be received in either 3.0 or 3.1 of the Fibre Alliance (FA) MIB, and
the switch responds in the same version. The switch can also be configured to use a
specific version for traps generated by the switch.
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.
Table 3 Zoning parameters supported 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 in HAFM Zoning Library 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
All directors and edge switches in the same fabric should have the same firmware level
installed—whether 1 Gbps or 2 Gbps capable, this firmware operates correctly.
The recently released Edge Switch 2/12 had an interim firmware specificfortheEdge
Switch 2/12, 05.05.00-12. This firmwarecannotbeusedforanyotheredgeswitch
or director. This interim version is compatible with the M-Series firmware 05.02.00-13
used for the rest of the M-Series fabric products. The firmware 07.01.02-4 is a common
firmware for all the M-Series fabric products, including the Edge Switch 2/12.
18