https://community.hpe.com/t5/operating-system-hp-ux/panic-situ-need-emergency-reply/m-p/4643947#M379671 In other words, you've made a full reboot. This causes the system to run a *long* self-test sequence before each nPar reboots. You may be unfamiliar with this, because a vPar reboot happens quite fast. If the number of Logs in the vfp display keeps increasing, don't worry: just switch to the console mode and wait.<BR /><BR />If the Logs number in the vfp display stops, <BR />there are two possibilities:<BR />1.) The system has finally completed diagnostics and entered the boot phase. If the nPar is not configured with a valid boot target, you may have to switch to the console mode and use EFI to select a valid boot target (if you're using vPars, this would be vpmon).<BR />or<BR />2.) you may have a hardware problem. You must then use the MP logs (the SL command) to diagnose the problem.<BR /><BR />If your hardware partition is configured with vPars, the hardware partition will first boot the vPar monitor, which will then boot the vPars in that hardware partition.<BR /><BR />vPars are virtual partitions, created by the vPar monitor (vpmon). When vpmon is not running, all its vPars are not active and cannot be accessed.<BR /><BR />MK Tue, 08 Jun 2010 06:09:44 GMT Matti_Kurkela 2010-06-08T06:09:44Z https://community.hpe.com/t5/operating-system-hp-ux/panic-situ-need-emergency-reply/m-p/4643946#M379670 hi ,<BR />due to env problem my server (rx8640)gone to normal shutdown.nowi am trying to connect MP ,its not getting my v-pars.but it shows the pars like par 0 par 1.the vfp is shows like<BR /> # Partition state Activity<BR /> - --------------- --------<BR /> 0 Memory interleave FPAR_PHASE_IS_INTERACTING 245 Logs<BR /> 1 Memory interleave FPAR_PHASE_IS_INTERACTING 199 Logs<BR />please anybody help me ..........<BR />and i am not gettting individual vpars thruogh putty also.<BR /><BR />help me-------- Tue, 08 Jun 2010 05:22:48 GMT https://community.hpe.com/t5/operating-system-hp-ux/panic-situ-need-emergency-reply/m-p/4643946#M379670 RAKUNTA 2010-06-08T05:22:48Z https://community.hpe.com/t5/operating-system-hp-ux/panic-situ-need-emergency-reply/m-p/4643947#M379671 In other words, you've made a full reboot. This causes the system to run a *long* self-test sequence before each nPar reboots. You may be unfamiliar with this, because a vPar reboot happens quite fast. If the number of Logs in the vfp display keeps increasing, don't worry: just switch to the console mode and wait.<BR /><BR />If the Logs number in the vfp display stops, <BR />there are two possibilities:<BR />1.) The system has finally completed diagnostics and entered the boot phase. If the nPar is not configured with a valid boot target, you may have to switch to the console mode and use EFI to select a valid boot target (if you're using vPars, this would be vpmon).<BR />or<BR />2.) you may have a hardware problem. You must then use the MP logs (the SL command) to diagnose the problem.<BR /><BR />If your hardware partition is configured with vPars, the hardware partition will first boot the vPar monitor, which will then boot the vPars in that hardware partition.<BR /><BR />vPars are virtual partitions, created by the vPar monitor (vpmon). When vpmon is not running, all its vPars are not active and cannot be accessed.<BR /><BR />MK Tue, 08 Jun 2010 06:09:44 GMT https://community.hpe.com/t5/operating-system-hp-ux/panic-situ-need-emergency-reply/m-p/4643947#M379671 Matti_Kurkela 2010-06-08T06:09:44Z