Oracle SuperCluster Setup/Configuration Best Practices
(Doc ID 1997411.1)
Last updated on APRIL 11, 2024
Applies to:
Oracle SuperCluster M6-32 HardwareOracle SuperCluster T5-8 Half Rack
SPARC SuperCluster T4-4 Full Rack
Oracle SuperCluster T5-8 Full Rack
SPARC SuperCluster T4-4
Oracle Solaris on SPARC (64-bit)
Purpose
The goal of this document is to present the best practices for the deployment of Oracle SuperCluster in the area of Setup and Configuration.
Scope
General audience working on Oracle Supercluster Systems
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| ZFS root rpool and zone roots capacity should not exceed recommended utilization |
| ZFS Pool /u01 should not exceed recommended utilization |
| LDom Configuration should not be altered with the ldm command |
| Only the latest version of SuperCluster documentation should be used |
| All hosts should have DNS properly configured, including the ZFSSA. ALL HOSTS means ALL LDOMS/ZONES/CELLS/SWITCHES/ARRAYS. |
| iSCSI timeout con-login-max default of 180 should be increased to 240 or 480 Seconds |
| Enabling 802.1Q VLAN Tagging on SuperCluster |
| Ensure RDS services are enabled |
| Ensure Multicast is Disabled |
| Use an additional InfiniBand-connected ZFS Storage Appliance to host I/O intensive operations rather than the included ZFS Storage Appliance |
| Ensure that NTP Daemon (ntpd) Configuration Best Practices are Followed |
| Ensure the Solaris Image Packaging System Configuration (IPS Repo) is correct |
| Best Practices for Aligning Zone CPU Pools to Whole Cores |
| High-Availability IP (HAIP) is not supported on SuperCluster |
| Limit the number of nodes per Grid Infrastructure |
| Monitoring applications should not be installed on the target system being monitored |
| References |