<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: parameter tuning tcp_conn_request_max in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680732#M611522</link>
    <description>Hi , &lt;BR /&gt;&lt;BR /&gt;There are already so many threads on this. &lt;BR /&gt;You can put an entry if it is not there. &lt;BR /&gt;If you want to set temporary, you can use &lt;BR /&gt;&lt;BR /&gt;ndd -set command&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943817" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943817&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From Rick's document &lt;BR /&gt;&lt;A href="ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt" target="_blank"&gt;ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;tcp_conn_request_max:&lt;BR /&gt;&lt;BR /&gt;    Maximum number of outstanding inbound connection requests.&lt;BR /&gt;    [1, - ] Default: 20 connections&lt;BR /&gt;&lt;BR /&gt;This is also known as the maximum depth of the "listen queue." The&lt;BR /&gt;actual maximum for any given TCP endpoint in the LISTEN state will be&lt;BR /&gt;the MINIMUM of tcp_conn_request_max and the value the application&lt;BR /&gt;passed-in to the listen() socket call.&lt;BR /&gt;&lt;BR /&gt;For this parameter to take effect for a given application, it must be&lt;BR /&gt;set BEFORE said application makes its call to listen(). So, if you use&lt;BR /&gt;ndd to set this value after the application has started, it will have&lt;BR /&gt;no effect unless you can get the application to recreate its LISTEN&lt;BR /&gt;endpoint(s).&lt;BR /&gt;&lt;BR /&gt;You can see if tcp_conn_request_max MIGHT be too small by looking at&lt;BR /&gt;the output of either "netstat -s" or "netstat -p tcp" and looking for&lt;BR /&gt;the line displaying the number of connection requests dropped due to&lt;BR /&gt;full queue. If the number of drops is zero, the value of&lt;BR /&gt;tcp_conn_request_max is fine. If the value is non-zero, either&lt;BR /&gt;tcp_conn_request_max is too small, or the values the applications are&lt;BR /&gt;using in their calls to listen() are too small.&lt;BR /&gt;&lt;BR /&gt;Setting this value higher has no particular downside. Editing&lt;BR /&gt;/etc/rc.config.d/nddconf to set this value to say 1024 is probably not &lt;BR /&gt;a bad idea for any "internet server" system.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj</description>
    <pubDate>Mon, 30 Aug 2010 06:43:37 GMT</pubDate>
    <dc:creator>SoorajCleris</dc:creator>
    <dc:date>2010-08-30T06:43:37Z</dc:date>
    <item>
      <title>parameter tuning tcp_conn_request_max</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680731#M611521</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I need to tune the parameter tcp_conn_request_max=8192.&lt;BR /&gt;&lt;BR /&gt;I have checked nddconf file above line is not availble and how to make it.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;panneer&lt;BR /&gt;</description>
      <pubDate>Mon, 30 Aug 2010 06:32:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680731#M611521</guid>
      <dc:creator>GTFSpanneer</dc:creator>
      <dc:date>2010-08-30T06:32:43Z</dc:date>
    </item>
    <item>
      <title>Re: parameter tuning tcp_conn_request_max</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680732#M611522</link>
      <description>Hi , &lt;BR /&gt;&lt;BR /&gt;There are already so many threads on this. &lt;BR /&gt;You can put an entry if it is not there. &lt;BR /&gt;If you want to set temporary, you can use &lt;BR /&gt;&lt;BR /&gt;ndd -set command&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943817" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943817&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From Rick's document &lt;BR /&gt;&lt;A href="ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt" target="_blank"&gt;ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;tcp_conn_request_max:&lt;BR /&gt;&lt;BR /&gt;    Maximum number of outstanding inbound connection requests.&lt;BR /&gt;    [1, - ] Default: 20 connections&lt;BR /&gt;&lt;BR /&gt;This is also known as the maximum depth of the "listen queue." The&lt;BR /&gt;actual maximum for any given TCP endpoint in the LISTEN state will be&lt;BR /&gt;the MINIMUM of tcp_conn_request_max and the value the application&lt;BR /&gt;passed-in to the listen() socket call.&lt;BR /&gt;&lt;BR /&gt;For this parameter to take effect for a given application, it must be&lt;BR /&gt;set BEFORE said application makes its call to listen(). So, if you use&lt;BR /&gt;ndd to set this value after the application has started, it will have&lt;BR /&gt;no effect unless you can get the application to recreate its LISTEN&lt;BR /&gt;endpoint(s).&lt;BR /&gt;&lt;BR /&gt;You can see if tcp_conn_request_max MIGHT be too small by looking at&lt;BR /&gt;the output of either "netstat -s" or "netstat -p tcp" and looking for&lt;BR /&gt;the line displaying the number of connection requests dropped due to&lt;BR /&gt;full queue. If the number of drops is zero, the value of&lt;BR /&gt;tcp_conn_request_max is fine. If the value is non-zero, either&lt;BR /&gt;tcp_conn_request_max is too small, or the values the applications are&lt;BR /&gt;using in their calls to listen() are too small.&lt;BR /&gt;&lt;BR /&gt;Setting this value higher has no particular downside. Editing&lt;BR /&gt;/etc/rc.config.d/nddconf to set this value to say 1024 is probably not &lt;BR /&gt;a bad idea for any "internet server" system.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj</description>
      <pubDate>Mon, 30 Aug 2010 06:43:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680732#M611522</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2010-08-30T06:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: parameter tuning tcp_conn_request_max</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680733#M611523</link>
      <description>in fact you can add any ndd configuration to nddconf.&lt;BR /&gt;just add&lt;BR /&gt;TRANSPORT_NAME[0]=tcp&lt;BR /&gt;NDD_NAME[0]=tcp_conn_request_max&lt;BR /&gt;NDD_VALUE[0]=8192&lt;BR /&gt;&lt;BR /&gt;in fact the 0 is the index of the table so if you already have configurations in your ndd conf, you must use index+1 for your cnfiguration&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 31 Aug 2010 12:10:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/parameter-tuning-tcp-conn-request-max/m-p/4680733#M611523</guid>
      <dc:creator>Laurent Menase</dc:creator>
      <dc:date>2010-08-31T12:10:51Z</dc:date>
    </item>
  </channel>
</rss>

