HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 69 (of 108)
Chapter 15 Serviceguard
October 29, 2013
# linkloop –i 2 0x00108318AFED
Link connectivity to LAN station: 0x00108318AFED
--- OK
Sometimes Serviceguard’s discovery does not match the results achieved with linkloop,
because it uses a slightly differerent method. The HP unsupported tool dlpiping (More
information about dlpiping can be found under subsection “Tools”) can be used in such cases.
The dlpiping tool uses exactly the same communcation mechanism that Serviceguard uses.
Therefore the results are more representative than simply using linkloop.
To test connectivity from local PPA 1 to local PPA 2:
# dlpiping 2 1
Bound PPA 2, Ethernet, address 0x00108318afee
Bound PPA 1, Ethernet, address 0x00108318afed
Send from PPA 2 to PPA 1 0x00108318afedaa080009167f
Send from PPA 1 to PPA 2 0x00108318afeeaa080009167f
Recv from 0x00108318afedaa080009167f on PPA 2 0x00108318afeeaa080009167f
Recv from 0x00108318afeeaa080009167f on PPA 1 0x00108318afedaa080009167f
To test connectivity from local PPA 1 to remote PPA 2:
# dlpiping –n <remote node> 2 1
Bound PPA 2, Ethernet, address 0x00108318afee
Bound remote PPA 1, Ethernet, address 0x00108318cff8
Send from PPA 2 to remote PPA 1 0x00108318cff8aa080009167f
Send from remote PPA 1 to PPA 2 0x00108318afeeaa080009167f
Recv from 0x00108318cff8aa080009167f on PPA 2 0x00108318afeeaa080009167f
Recv from 0x00108318afeeaa080009167f on remote PPA 1
0x00108318cff8aa080009167f
Tools
crashinfo
crashinfo is a tool for helping with coredump analysis, in particular system hangs. crashinfo
prints helpful notes and warnings intended for less experienced dump readers, and also things
that may be easily overlooked by more experienced users such as the psw Q-bit being off. It also
tries to be "smart" with certain types of panics. For example, with spinlock deadlock panics
crashinfo will attempt to find and print the lock structure, and the stack trace of the lock holder.
Other examples are for DPF and MPF panics it pulls the trapping address etc from the
save_state, decodes the instruction, and depending on the trapping address calls the kmeminfo -
virtual function. When we are very low on memory, or in the case of a kalloc panic, we again
call kmeminfo routines to display the kernel memory usage.
More information can be found on
http://teams3.sharepoint.hp.com/teams/esssupport/InsideESSSupport/InsideWTEC/HPUX-