JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Storage F5100 Flash Array

Product Notes

search filter icon
search icon

Document Information

1.  Sun Storage F5100 Flash Array Product Notes

Special Considerations

Replacing Energy Storage Modules

Shipping Energy Storage Modules

Configuration Guidelines and Limitations

Multipathing on the Sun Storage F5100 Flash Array

Connecting Multiple Arrays or JBODs

Oracle Solaris Device Path Changes After FMod Replacement

System Specifications and Requirements

Current and Legacy Systems

Supported Hosts, HBAs, and OSs

Supported SPARC Configurations

Supported Oracle x86 Configurations

Supported HBA Firmware

Supported System Firmware

Required Patches

Oracle Solaris Performance Patch

HBA Firmware Patch

Windows 2003 Patch

Persistent Log Message Patch

Supported Disk Management Software

Aligning FMODs for Optimal Performance

Known Issues

Documentation Errata

Configuration Guidelines and Limitations

The following configuration limitations exist for the Sun Storage F5100 flash array. Configuring systems that do not adhere to these guidelines might produce unexpected results.


Note - The Sun Storage F5100 Flash Array Installation Guide provides detailed information about the configurations that can be produced using the Sun Storage F5100 flash array.


Multipathing on the Sun Storage F5100 Flash Array

Multipathing is not supported on the Sun Storage F5100 flash array. For additional configuration restrictions, see the Sun Storage F5100 Flash Array Installation Guide.

Connecting Multiple Arrays or JBODs

Cascading a Sun Storage F5100 flash array to other Sun Storage F5100 flash arrays, JBODs, or other SAS-based storage array is not supported. Interconnecting the expanders on the Sun Storage F5100 flash array is also not supported.

Oracle Solaris Device Path Changes After FMod Replacement

After an FMod replacement, the Oracle Solaris device path will change. Applications and utilities that depend on the old device path will need to be reconfigured to work with the new one. For workaround instructions, see known issue 6801166 in Known Issues .