JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Tunable Parameters Reference Manual     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Overview of Oracle Solaris System Tuning

2.  Oracle Solaris Kernel Tunable Parameters

3.  Oracle Solaris ZFS Tunable Parameters

4.  NFS Tunable Parameters

5.  Internet Protocol Suite Tunable Parameters

Where to Find Tunable Parameter Information

Overview of Tuning IP Suite Parameters

IP Suite Parameter Validation

Internet Request for Comments (RFCs)

IP Tunable Parameters

_icmp_err_interval and _icmp_err_burst

_respond_to_echo_broadcast and _respond_to_echo_multicast (ipv4 or ipv6)

_send_redirects (ipv4 or ipv6)

forwarding (ipv4 or ipv6)

ttl

hoplimit (ipv6)

_addrs_per_if

hostmodel (ipv4 or ipv6)

ip_squeue_fanout

IP Tunable Parameters With Additional Cautions

_pathmtu_interval

_icmp_return_data_bytes (ipv4 or ipv6)

TCP Tunable Parameters

_deferred_ack_interval

_local_dack_interval

_deferred_acks_max

_local_dacks_max

_wscale_always

_tstamp_always

send_buf

recv_buf

max_buf

_cwnd_max

_slow_start_initial

_local_slow_start_initial

_slow_start_after_idle

sack

_rev_src_routes

_time_wait_interval

ecn

_conn_req_max_q

_conn_req_max_q0

_conn_req_min

_rst_sent_rate_enabled

_rst_sent_rate

smallest_anon_port

largest_anon_port

TCP/IP Parameters Set in the /etc/system File

ipcl_conn_hash_size

ip_squeue_worker_wait

TCP Parameters With Additional Cautions

_keepalive_interval

_ip_abort_interval

_rexmit_interval_initial

_rexmit_interval_max

_rexmit_interval_min

_rexmit_interval_extra

_tstamp_if_wscale

_recv_hiwat_minmss

UDP Tunable Parameters

send_buf

recv_buf

max_buf

smallest_anon_port

largest_anon_port

IPQoS Tunable Parameter

_policy_mask

SCTP Tunable Parameters

_max_init_retr

_pa_max_retr

_pp_max_retr

_cwnd_max

_ipv4_ttl

_ipv6_hoplimit

_heartbeat_interval

_new_secret_interval

_initial_mtu

_deferred_ack_interval

_ignore_path_mtu

_initial_ssthresh

send_buf

_xmit_lowat

recv_buf

max_buf

_rto_min

_rto_max

_rto_initial

_cookie_life

_max_in_streams

_initial_out_streams

_shutack_wait_bound

_maxburst

_addip_enabled

_prsctp_enabled

smallest_anon_port

largest_anon_port

Per-Route Metrics

6.  System Facility Parameters

A.  Tunable Parameters Change History

B.  Revision History for This Manual

Index

Per-Route Metrics

You can use per-route metrics to associate some properties with IPv4 and IPv6 routing table entries.

For example, a system has two different network interfaces, a fast Ethernet interface and a gigabit Ethernet interface. The system default recv_maxbuf is 128,000 bytes. This default is sufficient for the fast Ethernet interface, but may not be sufficient for the gigabit Ethernet interface.

Instead of increasing the system's default for recv_maxbuf, you can associate a different default TCP receive window size to the gigabit Ethernet interface routing entry. By making this association, all TCP connections going through the route will have the increased receive window size.

For example, the following is in the routing table (netstat -rn), assuming IPv4:

192.123.123.0        192.123.123.4         U        1      4  hme0
192.123.124.0        192.123.124.4         U        1      4  ge0
default              192.123.123.1         UG       1      8

In this example, do the following:

# route change -net 192.123.124.0 -recvpipe x

Then, all connections going to the 192.123.124.0 network, which is on the ge0 link, use the receive buffer size x, instead of the default 128,000 receive window size.

If the destination is in the a.b.c.d network, and no specific routing entry exists for that network, you can add a prefix route to that network and change the metric. For example:

# route add -net a.b.c.d 192.123.123.1 -netmask w.x.y.z
# route change -net a.b.c.d -recvpipe y

Note that the prefix route's gateway is the default router. Then, all connections going to that network use the receive buffer size y. If you have more than one interface, use the -ifp argument to specify which interface to use. This way, you can control which interface to use for specific destinations. To verify the metric, use the route(1M) get command.