C H A P T E R  4

Release Notes

This chapter contains the latest supplementary information for the preceding chapters in this guide. It contains the following topics:

For additional information related to the Sun StorageTek 4 Gb FC NEM 20-Port HBA, see the Sun Blade 8000 Module System documentation set.


Using the NEM With Sun StorEdge 3510 and 3511 Arrays

You cannot connect the Sun StorEdge 3510 RAID array or Sun StorEdge 3511 FC with SATA RAID array to the NEM on the same channel that use different speeds (1 Gb and 2 Gb). You can, however, mix 1-Gb and 2-Gb FC HBAs on different controller channels. This limitation is due to the design of the Sun StorEdge 3510 RAID array's port bypass circuitry and the inability of FC to support auto-negotiation in a multi-drop loop configuration.

Host connectors channels 4 and 5 of the 3511 FC cannot auto-negotiate to 1 Gbit which limits the number of hosts that can be direct-attached using 1 Gbit HBAs. Channels 0 and 1 are able to auto-negotiate to 1 Gbit and allow up to four connections in a dual-controller configuration or two connectors each in a single-controller configuration.


Solaris OS-Specific Issues

The following known issues are related to installing, configuring, or operating the NEM with the Solaris 10 OS.

Out of Option ROM Memory Error in System BIOS

Problem: A fully populated Sun Blade 8000 chassis with at least one NEM installed, could cause the Out of Option ROM Memory Space error to occur during BIOS POST.

Workaround: Disable some of the slots in the Basic Input/Output System (BIOS) using the BIOS Setup utility. For information about disabling Option ROM, see BIOS Option ROMs in the Sun Blade 8000 Series Online Information System.

For information about how to boot from a FC storage device connected to the NEM, see Appendix A in the Sun Blade 8000 Series Installation Guide.


SUSE Linux Enterprise-Specific Issues

Problem: The HBA driver distributed with SUSE Linux Enterprise Server 9 Service Pack 3 (SLES9-SP3) has the following known problems:

Workaround: To resolve these problems, update to the Emulex driver version 8.0.16.27 as described in To Update the Driver.


Windows Server 2003 OS-Specific Issues

See the Emulex driver manuals for any known issues with the Windows OS drivers.