HP-UX Network Server Accelerator HTTP B.11.31.01.03 Release Notes (5900-0837, September 2011)

1. Stop the web server being used with the NSA HTTP service.
2. Unregister the NSA HTTP application port used by the web server (the default port
number is 80 or otherwise configured in /etc/rc.config.d/nsahttpconf):
nsahttp -D -p port_num
3. Restart the web server.
4. If you want to retain any NSA HTTP log files in the /var/nsa directory, copy the
files to a backup medium or move them to another directory such as /tmp. Removing
NSA HTTP in the next step also removes the /var/nsa directory.
5. Remove NSA HTTP by running the following command:
swremove -x autoreboot=true NSAHTTP
The swremove utility requires the -x autoreboot=true option because the NSA
HTTP product includes a DLKM (nsamod), and it cannot determine if a reboot is
required at the time you issue the swremove command. In most cases, no reboot
is necessary.
Limitations
NSA HTTP cache size management is not currently integrated with file system buffer
cache management. If the NSA HTTP product is installed, HP suggests that you verify
and possibly decrease the size of the file system buffer cache.
By default, the NSA HTTP maximum cache size percentage is 50 (50% of the available
system memory). If the NSA HTTP maximum cache size percentage plus the minimum
file system buffer cache percentage (filecache_min) is 100 percent or more, it is
possible to have all of system memory used for the NSA HTTP and file system caches.
This will cause system performance to degrade. The default value for filecache_min
is 5 (5%).
You can change the NSA HTTP maximum cache size percentage by editing the /etc/
rc.config.d/nsahttpconf file or running the nsahttp command. To change the
file system buffer cache values, set the filecache_min and filecache_max system
parameters with the kctune command. For more information, see kctune (1M).
Known problems and workarounds
Problem
If both the web server and the web client are running on the same system, the NSA HTTP
module, nsamod, may be busy even when no web server is running. This condition may
happen if the web client sends an HTTP GET request but does not immediately retrieve
the reply. In this case, nsamod will remain “busy” until the web client reads the reply
(for example, by completing a recv() request).
Limitations 9