NO and use_isno

From: Jason delaFuente (jason.delafuente_at_GBE.COM)
Date: 08/31/04

  • Next message: Chafik,Basim: "Re: remote mksysb for AIX 5.2" 
    Date:         Tue, 31 Aug 2004 10:53:45 -0500
To: aix-l@Princeton.EDU

    About a week ago I sent out some IBM recommended settings that were given to us when we experienced Veritas backup slowdowns through our GE interface after going to ML3 for 5.2. They were as follows....

    (en? is the GE adapter)

    chdev -l en? -a rfc1323=1
    chdev -l en? -a tcp_sendspace=131072
    chdev -l en? -a tcp_recvspace=131072
    no -o use_isno=0

    We did not really question these settings since they came directly from IBM but while looking into another issue I came across something. According to the SysMgmt guide

    http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/commadmn/tcp_interfaces.htm

    the use_isno option has to be set to 1 for interface specific attributes to override the global no settings. What this led me to believe was that the three interface specific chdev commands we ran are having no effect becuase we changed use_isno to 0 at the same time. I called IBM again to ask them about this and they agreed but I wanted to ask the list to see if anyone else had any comments.

    Thanks,

  • Next message: Chafik,Basim: "Re: remote mksysb for AIX 5.2"