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

BladeServers. The issue was due to an error where the port offset (4) and domain ID offset (0x60) were

not applied correctly to the port address when ﬁrmware was upgraded.

Fixes in switch

ﬁrmware 6.4.0.08.00

Nameserver became unresponsive when speciﬁc Fibre Channel commands were issued

The nameserver became unresponsive while processing a GIP_NN (Get IP address by Nodename) of a

device on a remote switch if the device had not registered an IP address in the nameserver, and thus had

null value. The switch was unable to properly process the null IP value. This issue could also occur

in response to GIPP_ID and GIPP_PN Fibre Channel commands.

Implicit hard zoning issue caused CPU overload

With implicit hard zoning, high trafﬁc of bad frames (such as attempting to vio late zoning ) sent to a

switch caused the switch CPU to overload, and fail to process ISL trafﬁc in a timely fashion, resulting in

failed ISL connections.

Changes to port properties were slow to take effect

The por t properties dialog appeared unresponsive (could take many minutes) when "select to propagate

changes to entire column" was checked.

Port went ofﬂineafter acabledisconnect

There were

occasionswhere aswitchportwentofﬂine after a cable to a device was disconnected. The

port require d a por t reset to enable the conne ction to be reestablished.

Changes to port status and port type conﬁguration were not always activated

Por t status and port type selections in the Port Proper ty display in Element Manager, which appears in the

selection window, were not always activated unless ﬁrst selected from the d rop-down menu.

Multiple changes of large zone sets caused the nameserver to become unreponsive

Due to a memory leak, the nameserver became unresp onsive when a large zone set was activated

and

deact

ivated multiple times.

Fixes in switch ﬁrmware 6.4.0.06.00

Switch hang on boot due to internal timing issue with BladeSystem Management Module

If an HP p-Class BladeSystem is running BladeSystem Management Module ﬁrmware version 2. 30 or

later, the switch would frequently hang during the boot process. This was c aused by an interrupt loop that

occurred during switch initialization.

Switch reboot due to very high Ethernet port activity

Due to an Ethernet driver issue, if a switch was subjected to very high Ethernet activity, the switch

would occasionally reboot.

Internal ﬁrmware error due to uncommon SW_RSCN issue

The swi

tch nameserver would crash (reported as an Internal Firmware Error) when re ceiving multiple

SW_RSC

Ns for the same device within 200 msec for which the port states speciﬁed in the SW_RSCNs

not m atch. This only occurred when the switch was in McDATA Fabric interoperability mode.

McDATA 4Gb SAN Switch for HP p-Class BladeSystem release notes