Filter
Top Products
Cable requirements
NOTE:
Optical cables for
theEdgeSwitch2/12,EdgeSwitch2/12,andEdgeSwitch2/32
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 Edge Switch 2 /12, Edge Switch 2/24, and
Edge Switch 2/32 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 Edge Switch 2/12, Edge
Switch 2/24, and Edge Switch 2/32 .
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 0 7.01.02-4
is based on firmware 0 7.00.00-84, and contains all fixes included in that version and
prior releases. The following are now incorporated in firmware version 0 7.01.02-4.
Directors take new action upon detecting a failed UPM port module
A particular type of failure in director UPM por t 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 Ser ver 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 ha ng indefinitely, preventing any further
zone activities from any management location. This timeout issue has been fixed.
Edge Switch release notes
5