It is not inconceivable that an instance of HP-UX will hang, possibly due to a software or hardware fault. On a non-vPar server/n-Par, we can deal with this in two ways: We can issue a hard reset (the RS command from the GSP/console) or a soft reset (the TC command from the GSP/console, invoking a system crashdump ). If we perform either of these tasks on a vPar-enabled server/n-Par, we will reset all vPars and vpmon not a good idea. If we want to issue a hard or soft reset on an individual vPar, we use the vparreset command. The “h option is a hard reset (the RS command). The “t option is a soft reset (the TC command).
The hex data is gathered from the Processor Information Module (PIM). This will be displayed whenever we perform a hard or soft reset of a vPar. After a TOC, we will find the crashdump under the directory configured to store crashdumps, /var/adm/crash by default. It should be noted that any root user logged into a vPar within a server/n-Par is able to reset any other vPar within the same server/n-Par.