1. Installing and Configuring an Oracle Solaris Cluster 4.4 Environment
  2. Planning the Oracle Solaris Cluster Configuration
  3. Planning the Oracle Solaris OS
  4. Oracle Solaris OS Feature Requirements and Restrictions

Oracle Solaris OS Feature Requirements and Restrictions

Consider the following points when you plan the use of the Oracle Solaris OS in an Oracle Solaris Cluster configuration:

  • VNIC – When using VNICs for zone clusters, the name of the VNIC must be less than 16 characters long. Otherwise, you might not be able to choose the VNIC during system configuration.

  • Minimum Oracle Solaris Package – Oracle Solaris Cluster software requires at least the solaris-minimal-server group package of Oracle Solaris software. To use the GUI form of the clinstall utility to perform a centralized installation of the Oracle Solaris Cluster software, the solaris-desktop group package must be installed.

  • Oracle Solaris Operating System – Oracle Solaris Cluster 4.4 core software and Oracle Solaris Cluster 4.4 Quorum Server software require a minimum of Oracle Solaris 11.4 software.

  • Required Java Version – Java 1.8 is required by Oracle Solaris 11.4 software and Oracle Solaris Cluster 4.4 software.

  • Oracle Solaris Zones – Install Oracle Solaris Cluster framework software only in the global zone.

  • Loopback file system (LOFS) – During cluster creation, LOFS capability is enabled by default. If the cluster meets both of the following conditions, you must disable LOFS to avoid switchover problems or other failures:

    • HA for NFS is configured on a highly available local file system.

    • The automountd daemon is running.

    If the cluster meets only one of these conditions, you can safely enable LOFS.

    If you require both LOFS and the automountd daemon to be enabled, exclude from the automounter map all files that are part of the highly available local file system that is exported by HA for NFS.

  • Power-saving shutdown – Automatic power-saving shutdown is not supported in Oracle Solaris Cluster configurations and should not be enabled. See the poweradm(8) man page for more information.

  • Packet Filter (PF) feature – When IP network multipathing (IPMP) is used for public network, Oracle Solaris Cluster relies on IPMP for public network monitoring. Any PF configuration must be made in accordance with IPMP configuration guidelines and restrictions concerning PF.

  • fssnap – Oracle Solaris Cluster software does not support the fssnap command, which is a feature of UFS. However, you can use the fssnap command on local systems that are not controlled by Oracle Solaris Cluster software. The following restrictions apply to fssnap support:

    • The fssnap command is supported on local files systems that are not managed by Oracle Solaris Cluster software.

    • The fssnap command is not supported on cluster file systems.

    • The fssnap command is not supported on local file systems under the control of HAStoragePlus.

  • hostmodel Parameter for IPv4 or IPv6 - On a global cluster and in zone cluster nodes, set IP strict multihoming to weak or src-priority. See hostmodel Parameter (IPv4 or IPv6) in Oracle Solaris 11.4 Tunable Parameters Reference Manual.

    For example, the following commands set IPv4 and IPv6 strict multihoming to weak: 

    # ipadm set-prop -p hostmodel=weak ipv4
# ipadm set-prop -p hostmodel=weak ipv6