1. How can I verify NSA HTTP is properly installed?
First, execute the “swlist | grep NSAHTTP” command.
The expected output on HP-UX 11i from this command is
NSAHTTP B.11.11.01.02 NSA HTTP Bundle for HP-UX 11i
The expected output on HP-UX 11i version 2 from this command is
NSAHTTP B.11.23.01.02 NSA HTTP Bundle for HP-UX 11i version 2
Then, execute the “swverify NSAHTTP” command to make sure all components of the NSA HTTP product are properly installed on the system. If it displays a “Verification succeeded” statement, then all of the NSA HTTP product files are present on the system.
2. How can I verify if NSA HTTP is active?
a) Make sure the DLKM module delivered with NSA HTTP, nsamod, is loaded. On HP-UX 11i execute the “kmadmin -s” command, which should display:
Name ID Status Type
nsamod 1 LOADED STREAMS
Note that the status for nsamod must be LOADED. If it is not LOADED, execute “/sbin/init.d/nsahttp start” command to re-load the module. Note that the module ID may vary depending on whether any other DLKM modules are installed on the system.
On HP-UX 11i v2 execute the “kcmodule –q nsamod” command, which should display:
Module State Cause Notes
nsamod Loaded Explicit Auto-loadable, unloadable
Note that the state for nsamod must be loaded. If the state is not "loaded", execute the “kcmodule –s nsamod=loaded” command to re-load the module
b) Check if any nsad daemons are running by executing the command "ps –ef | grep nsad | grep –v grep”. The command is the same for both HP-UX 11i and 11i v2. There will be one nsad daemon for each port registered with the NSA HTTP service.
c) If the Web server registered with NSA HTTP is active, you can check how many requests NSA HTTP is servicing by entering the following command: “nsahttp –S on; nsahttp -s”. The first part of this command enables NSA HTTP to collect statistics; the second part of the command displays it. When NSA HTTP is active, this will display non-zero HTTP statistics.
3. How can I find out what ports NSA HTTP services?
You can execute the “nsahttp” command to display which TCP port numbers are registered with NSA HTTP. Once the Web Server listening on the same port number(s) is started, NSA HTTP service will automatically get activated.
In the following sample "nsahttp" command output (collected on HP-UX 11i), only TCP port 80 is registered with NSA HTTP:
Active NSA HTTP ports: 80
Max cache percentage: 50
Max URI data length: 1048576 bytes
Cache Timeout: 600 seconds
Persistent connection timeout: 600 seconds
Log file name: /var/nsa/nsahttp_log
Log file format: ASCII
NSA HTTP logging enabled
NSA HTTP statistics collection disabled
4. When troubleshooting HP-UX 11i NSA HTTP, what data should be collected?
a) Provide a step-by-step process to reproducing the problem, or what actions have led to the problem.
b) Collect outputs from the following commands:
- nsahttp
- nsahttp –s
- ps –ef | grep nsad | grep –v grep
- dmesg
- kmadmin –s (only if on HP-UX 11i)
- kcmodule –q nsamod (only if on HP-UX 11i version 2)
- kmadmin –v –s (only if on HP-UX 11i)
- kcmodule –v –q nsamod (only if on HP-UX 11i version 2)
c) Also, collect the following files: - NSA HTTP configuration file /etc/rc.conf.d/nsahttpconf
- NSA HTTP access log files which have the <PID> (Process ID) extensions of the running nsad daemon processes. By default, they are located in the /var/nsa directory
- Syslog file /var/adm/syslog/syslog.log
- Crush dump(s) if available (located in the /var/adm/crash directory)
d) You should also have detailed information about which Web server you are running (such as the Web server's name, version, etc.). |
Printable version
