Sponsored Content
Operating Systems AIX tuning network parameters : parameters not persist after reboot Post 302378674 by dantares on Tuesday 8th of December 2009 12:35:55 PM
Old 12-08-2009
tuning network parameters : parameters not persist after reboot

Hello,

On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command.

tunrestore -R is present in inittab

in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log
Code:
  root#/etc/tunables#ls -ltr
total 40
-rw-r--r--   1 root     system          493 Nov  5 17:38 nextboot
-rw-r--r--   1 root     system          334 Dec  3 17:39 lastboot.log
-rw-r--r--   1 root     system        11735 Dec  3 17:39 lastboot

  root#/etc/tunables#grep keep nextboot
       tcp_keepinit = "40"
       tcp_keepintvl = "20"
       tcp_keepidle = "600"

  root#/etc/tunables#grep keep lastboot.log
Setting tcp_keepidle to 600
Setting tcp_keepinit to 40
Setting tcp_keepintvl to 20
  
root#/etc/tunables#grep keep lastboot
       ndpt_keep = "120"               # DEFAULT VALUE
       tcp_keepcnt = "8"               # DEFAULT VALUE
       tcp_keepidle = "600"
       tcp_keepinit = "40"
       tcp_keepintvl = "20"

But when we checked with the no command, the parameters are not valid

Code:
  root#/etc/tunables#no -L | grep keep |grep -v cnt |grep -v ndpt
tcp_keepidle              6840   14400  600    1      8E-1   halfsecond  C
tcp_keepinit              40     150    40     1      8E-1   halfsecond  D
tcp_keepintvl             110    150    20     1      32K-1  halfsecond  C
  
root#/etc/tunables#no -a | grep keep |grep -v cnt |grep -v ndpt
            tcp_keepidle = 6840
            tcp_keepinit = 40
tcp_keepintvl = 110

is it because of the pre520tune parameter is disabled?

Code:
  root#/etc/tunables#lsattr -E -l sys0 |grep pre520
pre520tune      disable               Pre-520 tuning compatibility mode    
      True

have you a solution for this problem?

thank you for your answers

Last edited by zaxxon; 12-09-2009 at 11:35 AM.. Reason: code tags please
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need Parameters Help.

I can test for one parameter but anything more then that and I get an Error. I forgot I run this batch in a shell #!/bin/sh ------------------------------------------------------------------------- Write a batch program that accepts a keyword as a parameter and finds all the files... (3 Replies)
Discussion started by: james2006
3 Replies

2. Shell Programming and Scripting

parameters

I have a script that needs to check if the given parameters are a combination of 0123456789 and not a word or another irelevant character.please help (6 Replies)
Discussion started by: aekaramg20
6 Replies

3. AIX

Disk tuning parameters

I swapped out 2 72 gb disk drives for 2 146 gb drives, both of which spin at 15k. Are there any I/O parameters I should modify or can modify to get the most out of the new disks? Thanks, Mike M. (1 Reply)
Discussion started by: gravy26
1 Replies

4. UNIX for Advanced & Expert Users

tuning kernel parameters

Can only root do this, or can other users too? if other users can, do they have to be given permission, and if so, is there a file or something that stores this? Thanks. (4 Replies)
Discussion started by: JamesByars
4 Replies

5. Shell Programming and Scripting

parameters

i'm supposed to come up with a script that -accepts a directory as an optional command line parameter -display an error message and terminates if more than one parameter is provided -use the current directory if no parameter is provided -displays an error message and terminates if the provided... (4 Replies)
Discussion started by: jaay
4 Replies

6. Shell Programming and Scripting

More than nine parameters

Hi, please tell me the systax for passing 11 variables(including 4compulsory variables) in shell program. ORA_USERPASS=`echo $1` USERID=`echo $2` USERNAME=`echo $3` REQUESTID=`echo $4` P5=`echo $5` P6=`echo $6` P7=`echo $7` P8=`echo $8` P9=`echo $9` shift P10=`echo $9` shift... (3 Replies)
Discussion started by: anitha126
3 Replies

7. Solaris

Kernel Parameters

Dear All, I want to check whether all essential kernel parameters are installed in my Solaris 10 System. Is there any way to find it. And also how to tune it. Kindly help. Thanks and Regards Rj (8 Replies)
Discussion started by: jegaraman
8 Replies

8. Shell Programming and Scripting

Getting parameters

Hi, I have 2 scripts one master.sh and child.sh. The master runs on a separate server and pushes the child script to the desginated server and runs it.The child script configures the designated server for our day to day use and it has lot of interactive questions which help the... (4 Replies)
Discussion started by: a12ka4
4 Replies

9. Solaris

Delete route so it does not persist after reboot

Solaris 10 I am trying to delete a route using the command: route -p delete 192.0.0.0 192.1.3.254 The route gets delete but for some reason the route pops back up in the routing table after reboot. I also deleted the /etc/inet/static_routes file and the route still persists after reboot.... (6 Replies)
Discussion started by: jastanle84
6 Replies

10. AIX

Network tuning parameters on AIX

Hi, we've a gigabit Ethernet adapter. And we wanted to improve the performance by tuning network parameters. so' as per IBM info center, http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.prftungd%2Fdoc%2Fprftungd%2Fnetw_opt.htm we tried changing the tuning... (2 Replies)
Discussion started by: System Admin 77
2 Replies
tcp(7)							 Miscellaneous Information Manual						    tcp(7)

NAME
tcp - Internet Transmission Control Protocol (TCP) SYNOPSIS
#include <sys/socket.h> #include <netinet/in.h> The following is the socket call for AF_INET sockets: s = socket(AF_INET, SOCK_STREAM, 0); The following is the socket call for AF_INET6 sockets: s = socket(AF_INET6, SOCK_STREAM, 0); DESCRIPTION
The TCP protocol provides reliable, flow-controlled, two-way transmission of data. It is a byte-stream protocol used to support the SOCK_STREAM abstraction. The TCP protocol uses the standard Internet address format and, in addition, provides a per-host collection of port addresses. Thus, each address is composed of an Internet address specifying the host and network, with a specific TCP port on the host identifying the peer entity. Sockets utilizing the TCP are either active or passive. Active sockets initiate connections to passive sockets. By default, TCP sockets are created active; to create a passive socket the listen function must be used after binding the socket with the bind function. Only pas- sive sockets may use the accept function to accept incoming connections. Only active sockets may use the connect function to initiate con- nections. Passive sockets may underspecify their location to match incoming connection requests from multiple networks. This technique, termed wild- card addressing, allows a single server to provide service to clients on multiple networks. To create a socket that listens on all net- works, the Internet address INADDR_ANY (for AF_INET sockets) or in6addr_any (for AF_INET6 sockets) must be bound. The TCP port may still be specified at this time; if the port is not specified the system will assign one. Once a connection has been established, the socket's address is fixed by the peer entity's location. The address assigned to the socket is the address associated with the network interface through which packets are being transmitted and received. Normally this address corresponds to the peer entity's network. TCP supports the following socket options: Under most circumstances, TCP sends data when it is presented; when outstanding data has not yet been acknowledged, it gathers small amounts of output to be sent in a single packet once an acknowledgement is received. For a small num- ber of clients, such as window systems that send a stream of mouse events which receive no replies, this gathering of output can cause sig- nificant delays. Therefore, TCP provides a Boolean option, TCP_NODELAY (from the netinet/tcp.h header file), to defeat this algorithm. This option takes an int value. The maximum size of a TCP segment is based on the network MTU for destinations on local networks or on a default MTU of 576 bytes for destinations on nonlocal networks. The default behavior can be altered by setting the TCP_MAXSEG option to an integer value from 1 to 65,535. However, TCP will not use a maximum segment size smaller than 32 or larger than the local network MTU. Setting the TCP_MAXSEG option to a value of zero results in default behavior. The TCP_MAXSEG option can only be set prior to calling lis- ten or connect on the socket. For passive connections, the TCP_MAXSEG option value is inherited from the listening socket. This option takes an int value, with a range of 0 to 65535. When the SO_KEEPALIVE option is enabled, TCP probes a connection that has been idle for some amount of time. The default value for this idle period is 2 hours. The TCP_KEEPIDLE option can be used to affect this value for a given socket, and specifies the number of seconds of idle time between keepalive probes. This option takes an int value, with a range of 1 to N (where N is tcp_keepidle divided by PR_SLOWHZ). For more information on tcp_keepidle see the information on the inet subsystem con- figuration attributes in the System Configuration and Tuning guide. PR_SLOWHZ is defined in the <sys/protosw.h> header file. When the SO_KEEPALIVE option is enabled, TCP probes a connection that has been idle for some amount of time. If the remote system does not respond to a keepalive probe, TCP retransmits the probe after some amount of time. The default value for this retransmit interval is 75 seconds. The TCP_KEEPINTVL option can be used to affect this value for a given socket, and specifies the number of seconds to wait before retrans- mitting a keepalive probe. This option takes an int value, with a range of 1 to N (where N is tcp_keepintvl divided by PR_SLOWHZ). For more information on tcp_keepintvl see the information on the inet subsystem configuration attributes in the System Configuration and Tuning guide. PR_SLOWHZ is defined in the <sys/protosw.h> header file. When the SO_KEEPALIVE option is enabled, TCP probes a connection that has been idle for some amount of time. If the remote system does not respond to a keepalive probe, TCP retransmits the probe a certain number of times before a connection is considered to be broken. The default value for this keepalive probe retransmit limit is 8. The TCP_KEEP- CNT option can be used to affect this value for a given socket, and specifies the maximum number of keepalive probes to be sent. This option takes an int value, with a range of 1 to tcp_keepcnt. For more information on tcp_keepcnt see the information on the inet subsystem configuration attributes in the System Configuration and Tuning guide. If a TCP connection cannot be established within some amount of time, TCP will time out the connect attempt. The default value for this initial connection establishment timeout is 75 seconds. The TCP_KEEPINIT option can be used to affect this initial timeout period for a given socket, and specifies the number of seconds to wait before the connect attempt is timed out. For passive connections, the TCP_KEEPINIT option value is inherited from the listening socket. This option takes an int value, with a range of 1 to N (where N is tcp_keepinit divided by PR_SLOWHZ). For more information on tcp_keepinit see the information on the inet subsystem configuration attributes in the System Configuration and Tuning guide. PR_SLOWHZ is defined in the <sys/protosw.h> header file. These options can be retrieved with the getsockopt function and set with the setsockopt func- tion. The option level for the setsockopt and getsockopt functions is the protocol number for TCP, available from the getprotobyname function. Options at the IP transport level may be used with TCP; see ip(7). Incoming connection requests that are source-routed are noted, and the reverse source route is used in responding. ERRORS
If a socket operation fails, errno may be set to one of the following values: The option_len parameter provided to the setsockopt or get- sockopt function is less than sizeof(int) or the option_value parameter provided to the setsockopt function is outside the valid range for the option. The socket to be connected already has a connection. The system ran out of memory for an internal data structure. Setting the TCP_MAXSEG option is not supported after connect or listen. A connection was dropped due to excessive retransmissions. The remote peer forced the connection to be closed. The remote peer actively refuses connection establishment (usually because no process is listen- ing to the port). An attempt is made to create a socket with a port which has already been allocated. An attempt is made to create a socket with a network address for which no network interface exists. RELATED INFORMATION
Functions: getsockopt(2), socket(2) Network Information: netintro(7), inet(7), ip(7) delim off tcp(7)
All times are GMT -4. The time now is 02:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy