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
settune(2)							System Calls Manual							settune(2)

NAME
settune() - set the value of a kernel tunable parameter SYNOPSIS
DESCRIPTION
This function sets the value of the kernel tunable parameter named tunable to the supplied value. This new value takes effect immediately, except in the cases noted below. Some parameters cannot be changed without rebooting the kernel. These parameters cannot be changed using Some parameters represent limits on resources that can be consumed by individual processes. In general, changes to these parameters do not affect processes that are running at the time the change is made; they affect only new programs started (with or an equivalent) after that time. Some specific parameters may be exceptions to this general rule; see the man pages for those parameters for details. Valid values for the flags parameter and their connotations are: The value of the tunable parameter is set by the kernel. The value parameter to is ignored. Sets the tunable parameter to the value and turns off any automatic tuning done by the kernel. The call can give information about whether or not changes to a parameter are allowed or will require a reboot. Some individual parameters may have specific notes regarding their behavior when changed; consult the parameter man pages for details on each specific parameter. Security Restrictions The actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
This function returns one of the following values: The value of the specified parameter has been changed. The function did not complete successfully. The value of the specified parameter has not been changed. ERRORS
If this function returns to indicate an error, the global variable will be set to one of the following values to indicate the error that occurred: The specified tunable parameter does not exist. tunable specifies an address that is inaccessible. The caller does not have the privilege. The specified value is not within the acceptable range for the specified parameter. The value of the parameter could not be changed immediately. The specified parameter cannot be changed without rebooting the kernel. The Kernel Registry Service was unavailable or encountered an error. Insufficient memory to accommodate the new parameter value. WARNINGS
It is possible to seriously degrade system performance, or even render a system unbootable, with incorrect tunable settings. Use care when setting tunable values. Always have a known working kernel configuration saved as a backup; if the system fails to boot after a tunable change, boot from that backup kernel configuration. Keep good records of all tunable changes so that they can be reversed if they degrade system performance. Tunable changes made with are automatically logged to If the tunable being changed through is used in expressions that set the values of other tunables, those expressions will not be re-evalu- ated and those tunable values will not be updated. Note that this behavior may change in future releases of HP-UX. If expression evalua- tion is desired, use to set tunable values. Changes to parameter values made with may not remain effective across reboots. Note that this behavior may change in future releases of HP-UX. If persistence across reboots is desired, use to set tunable values. AUTHOR
was developed by Hewlett-Packard Company. SEE ALSO
kctune(1M), mk_kernel(1M), gettune(2), tuneinfo2(2), privileges(5), and the individual tunable parameter man pages in section 5. settune(2)
All times are GMT -4. The time now is 06:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy