- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Failed to set ndd tunable parameters
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 11:57 PM
тАО12-28-2006 11:57 PM
Failed to set ndd tunable parameters
Configure LAN interfaces
Output from "/sbin/rc2.d/S340net start":
----------------------------
Invalid tunable name: 'tcp_rexmit_int' for this module,
for a list of valid names, use name '?'
ERROR: Failed to set ndd tunable parameters
"/sbin/rc2.d/S340net start" FAILED
My nddconf file you can see below
RANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_time_wait_interval
NDD_VALUE[0]=60000
TRANSPORT_NAME[1]=tcp
NDD_NAME[1]=tcp_conn_request_max
NDD_VALUE[1]=2048
TRANSPORT_NAME[2]=tcp
NDD_NAME[2]=tcp_ip_abort_interval
NDD_VALUE[2]=60000
TRANSPORT_NAME[3]=tcp
NDD_NAME[3]=tcp_keepalive_interval
NDD_VALUE[3]=900000
TRANSPORT_NAME[4]=tcp
NDD_NAME[4]=tcp_rexmit_interval_initial
NDD_VALUE[4]=1500
TRANSPORT_NAME[5]=tcp
NDD_NAME[5]=tcp_rexmit_interval_max
NDD_VALUE[5]=60000
TRANSPORT_NAME[6]=tcp
NDD_NAME[6]=tcp_rexmit_int
NDD_VALUE[6]=500
TRANSPORT_NAME[7]=tcp
NDD_NAME[7]=tcp_xmit_hiwater_def
NDD_VALUE[7]=32768
TRANSPORT_NAME[8]=tcp
NDD_NAME[8]=tcp_recv_hiwater_def
NDD_VALUE[8]=32768
TRANSPORT_NAME[9]=ip
NDD_NAME[9]=ip_ire_gw_probe
NDD_VALUE[9]=0
TRANSPORT_NAME[10]=tcp
NDD_NAME[10]=tcp_fin_wait_2_timeout
NDD_VALUE[10]=4000
TRANSPORT_NAME[11]=ip
NDD_NAME[11]=ip_forwarding
NDD_VALUE[11]=0
Regards
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2006 12:25 AM
тАО12-29-2006 12:25 AM
Re: Failed to set ndd tunable parameters
Take the parameter its complaining about out and try again.
I've always just used the ndd command myself, have not had the need to set up a configuration file.
I think some of your values are a problem as well
TRANSPORT_NAME[10]=tcp
NDD_NAME[10]=tcp_fin_wait_2_timeout
NDD_VALUE[10]=4000
The default is 60, why are you raising it so high? This can cause problems when a disconnect is needed sooner.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2006 12:59 AM
тАО12-29-2006 12:59 AM
Re: Failed to set ndd tunable parameters
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2006 01:42 AM
тАО12-29-2006 01:42 AM
Re: Failed to set ndd tunable parameters
In your case, the [6] value does not exist. If you run:
mdd -get /dev/tcp ? | grep rexmit
you will see no value "tcp_rexmit_int" so the message is self-explanatory. The output of the above command is:
ndd -get /dev/tcp ? |grep rex
tcp_rexmit_interval_initial (read and write)
tcp_rexmit_interval_max (read and write)
tcp_rexmit_interval_min (read and write)
tcp_rexmit_interval_initial_lnp(read and write)
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2007 10:33 PM
тАО01-07-2007 10:33 PM
Re: Failed to set ndd tunable parameters
I have done the changes you suggest
and every thing works fine.
Thank you
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2007 10:35 PM
тАО01-07-2007 10:35 PM
Re: Failed to set ndd tunable parameters
Regards
Michael