FW V06.02.00/HAFM SW V08.02.00 HP StorageWorks Edge Switch Release Notes (AA-RTDZF-TE, September 2004)
Table Of Contents
- Edge Switch release notes
- About this document
- Release notes information
- Intended audience
- Firmware version 06.02.00-22
- Other edge switch documentation
- CD-ROM directory structure
- Supported configurations
- Cable requirements
- Important information
- HAFM and firmware compatibility
- Prerequisites for installing and using firmware 06.02.00
- Upgrading from an earlier version of firmware
- Upgrading firmware on an edge switch from 04.xx.xx to 05.xx.xx
- Considerations for downgrading the version of firmware
- HAFM upgrade required for firmware version 06.xx.xx
- Second-generation switch support
- OSMS change
- Default zone is disabled by default
- Some IP addresses must be avoided
- Hard zoning
- Zoning change RSCN control
- SNMP changes
- Zoning limitations
- Using the same firmware
- Reinstalling feature licenses
- Disconnecting the null modem cable
- CTP controls port lights
- Ethernet switch support
- Full Volatility
- CLI threshold alerts
- CLI show.eventLog command
- MIHPTO value
- Route management-Preferred Path
- EWS enhancements
- Full-fabric capability for Edge Switch 2/12
- Hard zoning for Edge Switch 2/12 and Edge Switch 2/24 switch loop ports
- Known issues
- Certain unauthorized devices may increase response time for fabric operations under specific conditions with the Edge Switch 2/24
- HSG80 transparent mode not supported with IBM AIX
- HSG80 transparent mode not recommended with controller in SCSI-3 mode with HP-UX operating systems
- 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
- Deleting a certain switch binding member using EWS may cause an error
- SNMP issues
About this document
18 HP StorageWorks Edge Switch release notes
The feature configures a switch or director so that no frame data is stored after a
power off. Without Full Volatility, if the switch or director experiences a fault
condition, a dump of the embedded memory space is captured into non-volatile
memory. This dump retains the last 30 frames transmitted from and last four
frames transmitted to the embedded port. With Full Volatility installed, this dump
does not occur when a fault condition occurs. Although this limits the amount of
diagnostic information available for potential problem resolution, the vast
majority of problems are typically resolved without the dump files.
Contact your sales representative to purchase a feature key for Full Volatility.
CLI threshold alerts
With firmware 06.00.00 and later, the CLI allows you to set and monitor
Throughput Threshold Alerts (TTAs).
CLI show.eventLog command
With firmware 06.00.00 and later, the CLI show.eventLog command has been
enhanced. The command now displays a link incident (LIN) log and event log.
MIHPTO value
With firmware 06.00.00 and later, the internal Missing Interrupt Handler Primary
Time Out (MIHPTO) value has been changed from 15 seconds to 3 minutes.
Route management—Preferred Path
Preferred Path can be configured using either CLI or HAFM 08.02.00.
Preferred Path allows you to influence the route of data traffic when it traverses
multiple switches or directors in a fabric. If more than one interswitch link (ISL)
connects switches in a fabric, you can specify an ISL preference for a particular
flow. The data path consists of the source port of the switch or director being
configured, the exit port of that switch or director, and the domain ID of the
destination switch or director. Each switch or director must be configured for its
part of the desired path to achieve optimal performance. You may need to
configure Preferred Paths for all switches or directors along the desired path for
proper multi-hop Preferred Path operation.
This feature allows use of the fabric shortest path first (FSPF) for any undefined or
erroneous path definitions and uses standard rerouting algorithms when errors in
the fabric occur. Thus if the defined route is not valid, the standard, automatically
generated route, is used.