McDATA 4Gb SAN Switch for HP p-Class BladeSystem release notes (AA-RW1ZH-TE, April 2008)

Languages
English
Fixes
This section describes the fixed issues related to the McDATA 4Gb SAN Switch.
Fixes in switch
firmware 6.4.0.13.00
Paths to devices reconnected to Mi10K director sometimes did not recover
When the M cDATA 4Gb SAN Switch was connected to an Mi1 0K director, and the connection of a
device to the Mi10K was interrupted and then reconnected, paths that existed between that device
and a device connected to the McDATA 4Gb SAN Switch sometimes would not be recovered. This
was caused by an error in the M cDATA 4Gb SAN Switch with processing the Address Format bits of
the
SW _RSCN (Inter-Switch Registered State Change Notification) from the Mi10K. This could o ccur
only if the fabric was in Open Fabric/Standard interoperability mode, and did not occur in McDATA
Fabric/Homogeneous interoperability mode.
Certain err oneous responses caused the switch SNMP services to become unresponsive
When the switch encountered erroneous responses to the fibre channel commands, GIELN (Get
Interconnect Element Lo g ical Name) or GMAL (Get Interconnect Element Management Address List), the
switch some
times did not properly handle the errors which caused the internal switch SNMP services to
become unresponsive. When this occurre d, the switch reported this as a Firmware error (Blink
2).
Fixes in switch firmware 6.4.0.11.00
Devices di
dnot always logbackintoswitchfollowing ResetorHardReset
When a Reset or Hard Reset is executed in the switch, connections to devices attached to switch ports are
normally interrupted as they are logged out. When the switch is in McDATA Fabric intero perability mode,
and a Rese
t
or Hard Reset was executed in the switch, there were instances where devices connected to
the
switch did not succeed in logging back in. This was due to an erroneous port ID in the Domain RSCN
that was issued, where the domain ID offset (0x60) was not applied correctly. The workaround for this
wastoset switch portsoffline and then back online, and then devices would log back into the switch.
Fixes in switch firmware 6.4.0.10.00
Nameser
ver error when booting from SAN to storage attached to switch with Domain ID = 1
An error
was introduced in 6.4.0.xx.xx firmware that caused a nameserver error for devices attached to
another switch with D omain ID = 1. This was only encountered when processing Fibre Channel command
GetAll Next (GA_NXT),which allows adevicetoretrieve informationfor thenextportinthe nameserver
database that is included in the zoning for the requesting device. The GA_NXT command is only used by
a
Host Bus Adaptor (HBA) in a server which boots from a SAN, to discover the path to its boot LUN.
The er
ror caused only the first accessible port of the switch with Domain I D = 1 to b e reported, where
the
subsequent GA_NXT c ommand would skip to the next available Domain ID. Other paths to stora ge
attached to the switch with Domain ID = 1 would not be discovered.
Por t fc address error when upgrading firmware from 5.2.x.xx.xx to 6.4.x.xx.xx
When upgrading firmware from 5.2.x.xx.xx to 6.4.x.xx.xx on a switch configured with Domain I D
=
1, the port fc add resses for some ports were changed, and could result in loss of connectivity to
4