How To Preserve an ndd(1M) TCP Tuning Configuration through a reboot on Solaris 10
(Doc ID 1377480.1)
Last updated on JANUARY 30, 2022
Solaris Operating System - Version 10 3/05 to 10 1/13 U11 [Release 10.0] Information in this document applies to any platform.
Because not all tunable parameters can be set in the /etc/system file, it is still possible to configure tcp/ip tuning via start-up scripts.
For NFS, TCP/IP, UDP and other network related tuning parameters specifically identified in the Oracle Solaris Tunable Parameters Reference Manual, the /etc/system file can be used.
While the default settings for tcp/ip on Solaris 10 are appropriate for most situations, some application vendors recommend or require particular tcp/ip tuning.
This example uses the Service Management Facility (SMF) in Solaris to create an FMRI to preserve non-default tcp ndd settings through a reboot on Solaris 10.
Using the Service Management Facility provides specific advantages, as defined in the "System Administration Guide: Basic Administration" Introduction to SMF topic:
* Automatically restarts failed services in dependency order, whether they failed as the result of administrator error, software bug, or were affected by an uncorrectable hardware error. The dependency order is defined by dependency statements.
* Makes services objects that can be viewed, with the new svcs command, and managed, with svcadm and svccfg commands. You can also view the relationships between services and processes using svcs -p, for both SMF services and legacy init.d scripts.
* Makes it easy to backup, restore, and undo changes to services by taking automatic snapshots of service configurations.
* Makes it easy to debug and ask questions about services by providing an explanation of why a service isn't running by using svcs -x. Also, this process is eased by individual and persistent log files for each service.
* Allows for services to be enabled and disabled using svcadm. These changes can persist through upgrades and reboots. If the -t option is used, the changes are temporary.
* Enhances the ability of administrators to securely delegate tasks to non-root users, including the ability to modify properties and enable, disable, or restart services on the system.
* Boots faster on large systems by starting services in parallel according to the dependencies of the services. The opposite process occurs during shutdown.
* Allows you to customize the boot console output to either be as quiet as possible, which is the default, or to be verbose by using boot -m verbose.
* Preserves compatibility with existing administrative practices wherever possible. For example, most customer and ISV-supplied rc scripts still work as usual.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!