FW 07.01.02/HAFM SW 08.06.00 HP StorageWorks Director Release Notes (AA-RTDVH-TE, August 2005)

Cable requirem
ents
NOTE:
Optical cables for the Director 2/64 and Director 2/140 must be order ed 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 shor t-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 bers, and
single-mode cables t ypically use 9/125 optical bers for distances up to 10 km.
Verify that c onnectors interfacing with the Director 2/64 and Director 2/140 use LC
Duplex connectors with a PC nish. In addition, the connector a t the opposite end
of the c able must be of either LC or SC type, depending on the requirements of the
connected device.
Important information
This section describes impor tant 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 rmware version 07.01.02-4 incorporates some minor code enhancements
and xes, and is not a manda tor y upgrade, though HP recommends that all directors
and e dge switches be upgraded to this version of rmware. Firmwar e release 0 7.01.0 2-4
is based on rmware 07.00.00-84 , and contains all xes included in that version and
prior releases. The following are now incorporated in rmware version 0 7.01.02-4.
Directors take n ew action upon detecting a failed UPM port mo dule
A particular type of failure in director UPM port modules could be disruptive to other
port mod ules in a director. In the release of rmware 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 Ser ver zoneset activation timeout issue resolved
Under cer tain conditions, the Embedded Web Server (EWS) would sometimes not allow
theZoneManagersubsystemenoughtimetoprocessaconguration 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 indenitely, preventing any further
zone activities from any management location. This timeout issue has been xed.
Director release notes
5