HP-UX test - qualification

[Fredric Vådegård]

Hi !

I??m going to qualify a HP-UX L1000 server and need help with what I could test. I trust that HP have test everything, but I need some tests that verify that everything works fine. For exemple, add a user and see if it works, create a VG/LV and mount it and create a file on it -> Dummy tests :-)
Do you have a list of tests or have done something simmilar, let me know a.s.a.p.

Thanks!
Fredric

[G. Vrijhoeven]

Hi,

Install diagnostics on your system (cstm or stm) and check out the hardware. The OS should work fine!

Gideon

[Fredric Vådegård]

The problem is that I know everything works fine, but I have to prove it :-(

[Marcin Wicinski · Accepted solution]

Hi,
Its very hard to prove that everything works fine, but use:
dmesg - reports hardware status
ioscan - if all devices are attatched proporly and system sees them,
lanscan
netstat -in
ping to and fron server
stm is very good to check hardware configuration
perform some basic LVM operations (creating pv, vg, lvols)
check rc.log and syslog.log
perform a reboot to check if the machine reboots correctly
swlist -l fileset -a state | grep -v ^# | grep -v conf (the result should be empty - all filesets are installed and configured)
...
I hope this helps,

[G. Vrijhoeven]

Hi again,

The only sencible test i can think of is installing installing the allication that the server is intended for so you know if that works. Creating logical volumes, adding users etc. does not tell anyting about how a system reacts in production situation.

Gideon

[Wodisch]

Hello Fredri[ck],

you could try to compare the output of "nickel" of an already *proven* system to the new one, same for the output of the patch-list (there was an e-mail based service from one of the RC-guys in france, once: you sent the output of your "swlist" and got the list of missing patches).
Then you can check for the output of "swlist" and "swverify" to check for not-configured packages, and those with missing files/wrong owners/groups/permissions.
You can go for the checks against the "bastion" host setup for security...

Just my ???0.02,
Wodisc

[Roger Baptiste]

Fredrik,

1) check #dmesg output to see if there are any error or console related messages

2) ioscan -nf >/tmp/ioscan.out
grep -i NO_HW /tmp/ioscan.out
-> if everything is fine, this should not return anything

3) vgdisplay -v >/tmp/vgdisplayv.out
-> see whether all vg and lv's are visible including the pv devices

4) swapinfo -mt -> see whether swap is configured as you want it to be.

5)lvlnboot -v -> confirms the boot record is fine (should have root,swap and dump volumes configuration)

6) From SAM, you can create a user/group to check up. But, i think this test is unnecessary, though there is no harm in trying.

7) Look at /var/adm/syslog/syslog.log for any messages

8) Do netstat -in to look at network interfaces

9) do netstat -nr to see routing tables

10) try telnet/ftp out of the box

11) try telnet/ftp into the box from other systems

12) if system is using mails, try
sendmail -vt mailaddress
test
.

This should send the mail out

# Run top and see whether it shows all the CPU's

#run Glance and look at system information

**


This tests should ensure that your system
is fine from the O/S and H/W angles.
The application tests is totally dependent on the applications.

HTH
raj