HP StorageWorks Director and Edge Switch release notes (5697-8176, April 2009)

Known issues in firmware 09.09.02
Table 6 lists the known issues in firmware 09.09.02.
Table 6 Firmware 09.09.02 known issues
WorkaroundIssue
If the switch has been configured as described, review
and modify the PDCM as needed after a power cycle.
If a switch has been managed with HAFM/EFCM
Management Style configured to FICON Manage-
ment Style, and the Prohibit Dynamic Connectivity
Matrix (PDCM) has been configured with Act-
ive=Saved disabled, and the HAFM/EFCM Man-
agement Style is changed to Open Systems
Management Style, and the switch is power
cycled, when the switch power on reset is executed,
the PDCM configuration is set to the previously act-
ive configuration instead of the configuration of the
contained in the IPL file.
Two workarounds can be used:
1. If the switches are still in a fabric with FR zones
activated, perform the CLI “cfgsave” command on any
Brocade switch running FOS. This will push the FR zones
to all M-EOS switches and directors in the fabric.
2. If the switches are no longer in a fabric with FR zones
activated, run the CLI command “disableSplZoneSet” on
each M-EOS switch or director that was power cycled
to clear the invalid FR zone database.
After completing either of these two workarounds, any
port with an attached device that was blocked will
become unblocked. The device will then be allowed to
login.
If Frame Redirection (FR) zones are being used with
M-EOS switches and directors and there are FR
zones loaded on all switches in the fabric, FR zones
will be lost on the M-EOS switches and directors
upon power cycle. When this happens, any device
that attempts to log in on any port will have the port
it uses blocked (via Event #012: “Redirect Zones
database no longer intact. Blocking all N-ports.”)
If this issue is encountered, the Ethernet port may recover
by removing and reconnecting the Ethernet cable from
the port. If this does not work, you can execute an IML
by momentarily pushing the IML button on the switch,
which will reset the Ethernet port.
After upgrading firmware from 9.6.x or later, rarely
the Ethernet port may become unresponsive, which
prohibits management of the switch.
The slower rerouting of data by Open Trunking can be
tolerated and will correct itself. This can be avoided by
disabling Reroute Delay when using Open Trunking.
When Open Trunking is in use and Reroute Delay
is enabled, and traffic is rerouted by the Open
Trunking function, the anticipated changes in data
flow are not correctly accounted for in the Open
Trunking algorithms. This can cause delays in
rerouting traffic by the Open Trunking function.
The switch will recover from this automatically, and the
event can be disregarded.
When firmware is upgraded or downgraded
between versions 9.6.2 and 9.8 in an M4700
switch using EFCM, an Event #411 Firmware Fault
may be reported in the Event Log.
16