Solaris 11.4 Hardware Requirements
Roman Bayramdurdiyev
Oracle Solaris provides several system installation group packages. The text installer and the default AI manifest in an Automated Installer installation install the solaris-large-server group package. The default installation manifest for non-global zones installs the solaris-small-server group package. The solaris-minimal-server group package installs the minimum supported set of packages required to run Oracle Solaris. You might want to modify a default installation manifest to install solaris-minimal-server, and then install additional packages as needed.
Oracle Solaris 11.4 supports systems based on the Oracle SPARC T4 or later processors; the Fujitsu SPARC64 X, X+, or XII processors; or x64 CPUs supporting either the Intel EM64T or AMD AMD64 instruction sets.
You will not be able to upgrade to Oracle Solaris 11.4 on any of the following platforms. See Oracle Solaris 11.3 Support (Doc ID 2382427.1) for information about keeping these systems up to date with critical fixes for Oracle Solaris 11.3 until you can upgrade the hardware:
Some capabilities that were available in Oracle Solaris 11.3 and earlier releases are nowobsolete and have been removed from Oracle Solaris 11.4. An upgrade to Oracle Solaris 11.4 willremove any obsolete capabilities that are currently installed on the system. For example, driversfor some legacy devices have been deprecated in Oracle Solaris 11.4. If you upgrade systems withthese devices, you might lose the ability to access those devices from Oracle Solaris 11.4. Beforeyou upgrade, review the End ofFeature Notices for Oracle Solaris 11.
Although Oracle SPARC T4, SPARC T5, SPARC M5, SPARC M6, and Fujitsu SPARC M10 systems were released with firmware versions to boot Oracle Solaris 11.4, the firmware must be updated if Oracle Solaris kernel zones support is required. Oracle SPARC M7, SPARC M8, SPARC T7, and SPARC T8 systems do not require firmware updates to support kernel zones on Oracle Solaris 11.4.
For information about hardware and software requirements for kernel zones, see Software and Hardware Requirements for Oracle Solaris Kernel Zones in Creating and Using Oracle Solaris Kernel Zones.
See Creating Package Repositories in Oracle Solaris 11.4 for information about downloading and installing a local package repository, configuring the solaris publisher to use the local repository, and providing access to the local repository from other systems.
The detailed system requirements information is the complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.
Db2 supports hypervisors being fully embedded in hardware and firmware while operating system requirements are met. Some examples are systems equipped with Power Hypervisor, VMware ESX 3i, or Hitachi Virtage.
Db2 11.5 (non-pureScale) runs on any operating system (OS) that is virtualized by any virtualization technology. Hypervisors in use must run a supported enterprise OS (For example, KVM with RHEL Enterprise support. KVM running CentOS is not recommended).
Note: This statement does not apply to Db2 pureScale clusters in any Db2 releases. For a detailed list of supported virtualization for pureScale, refer to the reports for each release.
If IBM believes that an issue is specific to a virtualization technology (such as performance or communication with peripheral and hardware components), IBM might require that the customer reproduce the issue in a nonvirtualized configuration.
If you have ideas or requests for new features, use the Splunk Ideas portal to search for, vote on, and request new enhancements (called an idea) for any of the Splunk solutions. See Splunk Ideas in the Get Started with Splunk Community manual.
The following tables list the computing platforms for which Splunk Enterprise has support. The first table lists availability for *nix operating systems and the second lists availability for Windows operating systems.
Each table shows available computing platforms (operating system and architecture) and types of Splunk software. A bold X in a box that intersects the computing platform and Splunk software type you want means that Splunk software is available for that platform and type.
If you do not see the operating system or architecture that you are looking for in the list, the software is not available for that platform or architecture. This might mean that Splunk has ended support for that platform. See the list of deprecated and removed computing platforms in Deprecated Features in the Release Notes.
X: Splunk software is available for the platform.
D: Splunk supports this platform and architecture, but might remove support in a future release. See Deprecated Features in the Release Notes for information on deprecation.
An empty box indicates software is not supported for this platform.
The official repository containing Dockerfiles for building Splunk Enterprise and Universal Forwarder images can be found on Splunk-Docker on GitHub. The list of requirements for Docker and Splunk software is available in the Support Guidelines on the Splunk-Docker GitHub.
For container orchestration, the Splunk Operator for Kubernetes on GitHub enables you to quickly and easily deploy Splunk Enterprise on your choice of private or public cloud provider. The operator simplifies scaling and management of Splunk Enterprise by automating workflows while implementing Kubernetes best practices.
Some parts of Splunk Enterprise on Windows require elevated user permissions to function properly. See the following topics for information on the components that require elevated permissions and how to configure Splunk Enterprise on Windows:
The Splunk Enterprise Monitoring Console works only on some versions of Linux and Windows. For information on supported platform architectures for the Monitoring Console, see Supported platforms in the Troubleshooting Manual. To learn about the other prerequisites for the Monitoring Console, see Monitoring Console setup prerequisites in Monitoring Splunk Enterprise.
As we update Splunk software, we sometimes deprecate and remove support of older operating systems. See Deprecated features in the Release Notes for information on which platforms and features have been deprecated or removed entirely.
Splunk software expects configuration files to be in ASCII or Universal Character Set Transformation Format-8-bit (UTF-8) format. If you edit or create a configuration file on an OS that does not use UTF-8 character set encoding, then ensure that the editor you use can save in ASCII or UTF-8.
To evaluate Splunk Enterprise for a production deployment, use hardware that is typical of your production environment. This hardware should meet or exceed the recommended hardware capacity specifications. See Reference hardware in the Capacity Planning Manual.
If you run Splunk Enterprise in a virtual machine (VM) on any platform, performance decreases. This is because virtualization works by providing hardware abstraction on a machine into pools of resources. VMs that you define on the system draw from these resource pools. Splunk Enterprise needs sustained access to a number of resources, particularly disk I/O, for indexing operations. If you run Splunk Enterprise in a VM or alongside other VMs, indexing and search performance can degrade.
If you run Splunk Enterprise on a file system that does not appear in this table, the software might run a startup utility named locktest to test the viability of the file system. If the locktest utility fails on the target file system or protocol, then that file system or protocol is not suitable for use with Splunk Enterprise.
(C) See "Considerations regarding Network File System (NFS)" later in this topic for information on the limitations for storing index buckets on the NFS protocol.
(D) See "Considerations regarding Common Internet File System (CIFS)/Server Message Block (SMB)" later in this topic for information on the limitations for storing index buckets on the CIFS and SMB protocols on Windows.
When you use Network File System (NFS) as a storage medium for Splunk indexing, consider all of the ramifications of file level storage. Use block level storage rather than file level storage for indexing your data.
In environments with reliable, high-bandwidth, low-latency links, or with vendors that provide high-availability, clustered network storage, NFS can be an appropriate choice. If you choose this strategy, work with your NFS vendor to confirm that their storage platform operates to the vendor specification in terms of performance, feature support, and data integrity.
When you use a CIFS resource for storage, confirm that the resource has write permissions for the user that connects to the resource at both the file and share levels. If you use a third-party storage device, confirm that its implementation of CIFS is compatible with the implementation that your Splunk Enterprise instance runs as a client.
Splunk Enterprise allocates system-wide resources like file descriptors and user processes on *nix systems for monitoring, forwarding, deploying, and searching. The ulimit command controls access to these resources which must be tuned to acceptable levels for Splunk Enterprise to perform adequately on *nix systems.
The more tasks your Splunk Enterprise instance performs, the more resources it needs. You should increase the ulimit values if you start to see your instance run into problems with low resource limits. See I get errors about ulimit in splunkd.log in the Troubleshooting Manual.
The following table shows the system-wide resources that Splunk Enterprise uses. It provides the minimum recommended settings for these resources for instances that are not forwarders, such as indexers, search heads, cluster manager, license manager, deployment servers, and Monitoring Consoles (MC).
e59dfda104