Ignite-UX Custom Configuration files

Tuning SD-UX for concurrent access
Generally, SD will not be able to handle more than three installation sessions by remote systems
without introducing either delays or timeouts. The following information also applies to swm on HP-
UX 11i v3, since it uses swagentd to access SD-UX depots.
In a default setup, SD-UX is able to handle no more than six concurrent RPC connections. Any
excess RPC connection attempts to swagentd will be queued, and if they take too long to service,
may fail due to timeout or rejection.
A swinstall session may require up to two active RPC connections to swagentd. What
happens when you want 10 systems to be able to install from your Ignite
85
server?
In this case there is no documented solution for increasing the number of RPC connections that SD-
UX can handle concurrently, however the following undocumented SD-UX setting can be put into
the /usr/lib/sw/sys.defaults file:
swagentd.rpc_max_calls=n
Where n is two times the number of expected concurrent sessions SD-UX needs to handle. For
temporary changes (or testing) you can stop swagentd and restart it with the option –x
rpc_max_calls=n. You could use the following command to do this:
# swagentd –r –x rpc_max_calls=n
When choosing a value for n, please take into account that local swlist commands do not make
RPC connections to swagentd.
So to allow for 10 systems to install concurrently, and to allow a few RPC connections for the local
system to perform swlist and other SD-UX commands, you would need 20 RPC connections for
the installing systems (10x2). A few extra RPC sessions (4) are added to allow for local SD
command usage (swlist, swcopy, etc), and some padding is added to ensure that if usage
grows no problem will be immediately encountered (an extra 4). In this case you would need to set
rpc_max_calls to be 28.
Issues to consider related to the HP-UX revision
There are some considerations for SD-UX related to the version of HP-UX used. On 11i v2 and later
releases of HP-UX, SD-UX is kernel threaded; on 11i v1 SD-UX uses CMA or user space threads.
Increasing rpc_max_calls will increase the number of kernel threads in use in swagentd. This
may have an impact on the following kernel tunables on HP-UX 11i v2:
1. nproc – There will be additional swagent processes running (one process per swagent;
one swagent per SD command that is issued to communicate to SD-UX on this system.)
The increase in processes caused by swagent is unlikely to add enough additional
processes on the system to force a change to nproc.
85
The SD-UX server may be different from your Ignite server. This discussion assumes they are the same system.
192