IP Service Activator is supported on the following Solaris operating systems (OS):

• Solaris 11.4 (or later)

For supported versions of third-party software, including Solaris, see "Supported Devices and Operating Systems".

To check the Solaris OS version, enter:

$ uname -r

or

$ uname -a

The SunOS version is returned. For Solaris 11 systems, 5.11 is returned.

For a more detailed indication of your Solaris version, check the /etc/release text file:

Go to the /etc directory of the installed image and enter:

# more release

The installed version is returned.

For example:

Oracle Solaris 11.3 SPARC
Copyright (c) 1983, 2018, Oracle and/or its affiliates.  All rights reserved.
Assembled 09 May 2018

Ensure that the latest recommended Solaris patch cluster is installed on each IP Service Activator host machine. This includes those patches recommended for Solaris by Sun.

Patches are available for download on Oracle Technology Network at:

http://www.oracle.com/technetwork/topics/security/whatsnew/index.html

To check which patch revision numbers you have installed:

On the Solaris 64-bit platform, enter:

$ showrev -p | more

The following tables list IP Service Activator support for vendor devices and operating systems in this release. For more information about which services are supported on each device and OS combination, refer to the respective cartridge guide or device support guide.

For Solaris, you must verify that the COREADM_PROC_ENABLED is enabled in the system core configuration file: coreadm.conf. If COREADM_PROC_ENABLED is enabled, the corresponding core file is generated for the IP Service Activator process when a core dump occurs. You can use the pstack tool to review and troubleshoot any core dump of a process.

To see the values of the core dump parameters in the coreadm.conf file, you can use this command:

cat /etc/coreadm.conf

The parameters of this file are as follows:

COREADM_GLOB_PATTERN=
COREADM_GLOB_CONTENT=default
COREADM_INIT_PATTERN=core
COREADM_INIT_CONTENT=default
COREADM_GLOB_ENABLED=no
COREADM_PROC_ENABLED=yes
COREADM_GLOB_SETID_ENABLED=no
COREADM_PROC_SETID_ENABLED=no
COREADM_GLOB_LOG_ENABLED=no

To set the core dump parameters, you can run the following command:

coreadm

With some applications requiring Linux, the coreadm tool is missing. Instead, core file management is configured in the kernel configuration file: /etc/sysctl.conf.

You need to enable core dumps from setuid process, remove file size limits for core dumps, and save them in an appropriate location using meaningful names. To do this, you need to add the following lines into the /etc/sysctl.conf file.

• fs.suid_dumpable = 2

• kernel.core_pattern = /var/core/core_%h_%e_%u_%g_%t_%p

To make sure you are not imposing limits on the core files, you need to add the following to the /etc/sysconfig/init file:

• DAEMON_COREFILE_LIMIT='unlimited'

After you update the /etc/sysctl.conf and /etc/sysconfig/init files, you can refresh the settings by running systctl, as follows:

[root@altix ~]# /sbin/sysctl -p
< list of kernel tunables >
fs.suid_dumpable = 2
kernel.core_pattern = /var/core/core_%h_%e_%u_%g_%t_%p
< list of kernel tunables >

A host supporting IP Service Activator must be configured to support a certain minimum number of available open files (File Descriptors) in order for IP Service Activator to successfully discover large numbers of devices (up to 65535) within one device discovery task. The setting for the number of available file descriptors should be 1024 or greater.

To permanently set the File Descriptors value on the Policy Server host:

1. Open the /etc/system file.

2. Add the following two lines:

   set rlim_fd_cur=1024 (or greater)
   set rlim_fd_max=1024 (or greater)
   

3. Save and close the file.

To determine the current Solaris kernel settings, enter:

ulimit -a

If the value of the nofiles (descriptors) is greater than or equal to 1024, enough file descriptors are available.

There is no advantage, from a scalability or performance standpoint, to have more than 1024 file descriptors available. Setting these parameters higher uses additional memory resources with no improvement in IP Service Activator performance.

You should synchronize the system time between IP Service Activator host machines using time synchronization software. Where machines are not synchronized, delays are likely to occur when configuring devices.

Ensure you synchronize the NTP times correctly.

The IP Service Activator administrator (user ID ipsaadm) is the UNIX user account given permissions (during installation) to start and stop the naming service and component manager manually. You must create this user account prior to IP Service Activator software installation.

When creating the ipsaadm user, specify the following details:

• Username: ipsaadm

• Group: ipsagrp

• Secondary group: sys

• Login shell: /bin/bash

• Home directory: select any location (known in this document as Service_Activator_home)

Throughout this document, ipsaadm is used as the UNIX user ID associated with IP Service Activator. If you have defined another UNIX user ID for specific uses with IP Service Activator, use it instead of ipsaadm where appropriate.