- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Vpar software upgrade landed in panic-Urgent
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 05:17 AM
тАО09-20-2009 05:17 AM
I am in upgrading process of vPar software version from A.03.03 to A.03.05. After installing the software system crashed with the below error. Please help asap.
MON> vparload -p vPar1 -b /stand/vmunix
[MON] Booting vPar1...
[MON] vPar1 loaded
Stored message buffer up to panic:
System Panic:
linkstamp: Sun Sep 20 08:51:46 EDT 2009
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: Incompatible vPar monitor version
PC-Offset Stack Trace (read across, top of stack is 1st):
[MON]
[MON] vPar1 has halted.
MON> [MON] vPar2 has halted.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 05:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 06:17 AM
тАО09-20-2009 06:17 AM
Re: Vpar software upgrade landed in panic-Urgent
Did you already boot the vpmon?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 06:22 AM
тАО09-20-2009 06:22 AM
Re: Vpar software upgrade landed in panic-Urgent
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 06:28 AM
тАО09-20-2009 06:28 AM
Re: Vpar software upgrade landed in panic-Urgent
@vasanth
Did you follow the procedure on page 85?
http://www.docs.hp.com/en/T1335-90057/T1335-90057.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 11:38 AM
тАО09-20-2009 11:38 AM
Re: Vpar software upgrade landed in panic-Urgent
The error message itself should indicate you that the version of Vpar software installed is not matching with the vpmon being booted before launching any vpar..
The following can be checked to better determine what is occurring:
- setboot
The setboot output should display hardware path of the disk the monitor is being booted from.
Example:
# setboot
Primary bootpath : 0/0/4/0/0/4/0.12.0
Alternate bootpath : 0/0/0/3/0.6.0
Autoboot is ON (enabled)
Autosearch is ON (enabled)
- what /stand/vpmon
The "what" output when run on the disk the monitor is booted from should display the version of the Vpar monitor. Example:
# what /stand/vpmon
/stand/vpmon:
$Revision: vpmon: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:26 PST 2007 $
$Revision: vpmon: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:26 PST 2007 $
$Revision: libdebug.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:53 PST 2007 $
$Revision: libfs.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:50 PST 2007 $
$Revision: libinit.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:44 PST 2007 $
$Revision: libinit-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:24 PST 2007 $
$Revision: libio.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:36 PST 2007 $
$Revision: libio-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:25 PST 2007 $
$Revision: libipmi.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:16 PST 2007 $
$Revision: libldr-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:17 PST 2007 $
$Revision: libmem.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:13 PST 2007 $
$Revision: libmem-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:08 PST 2007 $
$Revision: libpdc-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:09 PST 2007 $
$Revision: libpdcem.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:04 PST 2007 $
$Revision: libsvc.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:05 PST 2007 $
$Revision: libsvc-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:22:00 PST 2007 $
$Revision: libutil-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:21:57 PST 2007 $
vp_config.c $Date: 2004/10/14 17:52:10 $Revision: r11.11/8
NOTE: The above output shows the monitor with version A.03.04.06.
- liflcp /dev/rdsk/c#t#d#:AUTO - -> where c#t#d# is the device file for you boot disk.
Example:
# lifcp /dev/dsk/c8t12d0:AUTO -
hpux /stand/vpmon -a
NOTE: The previous lifcp example output confirms that the system is booting from the Vpar monitor /stand/vpmon .
- what /stand/vmunix | grep ├в I vpar
Example:
# what /stand/vmunix | grep -I vpar
$Revision: libvpar-pdk.a: vw: -- selectors: R11.11_BL2003_1103 'cup2_vpar_pib6' 'cup2_muralid_a.03.04.06' Thu Jan 11 20:18:01 PST 2007 $
NOTE: The "what" on the running kernel shows that the Virtual Partitions version is A.03.04.06, which matches the vpar monitor version from the previous example.
- vparstatus -v -p
vparstatus will display the BOOT path for the given vpar. It will also display the kernel from which it is being booted.
For this case, the BOOT path for the vpar pointed to a different hardware path than setboot. The BOOT disk from vparstatus configured for the given vpar contained an earlier version of the Virtual Partition software, which explained the mismatch.
The vpar successfully booted for this case after using vparcreate -p chx009a1 -a io:0/0/4/0/0/4/0.12.0:BOOT to set the vpar's boot path the same as the Npar's primary boot path from which the monitor was booted.
--------------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 12:52 PM
тАО09-20-2009 12:52 PM
Re: Vpar software upgrade landed in panic-Urgent
Thanks for all your quick replies. I found the issue and definitely my mistake. Its a software incompatibility b/w vPar software and the vpmon. I forgot that vpmon will be updated only after restarting the Npar. After rebooting the vpmon things went well.
Thanks a tons again
ITRC forums and members rocks!! keep rocking!!!
Vasanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2009 12:55 PM
тАО09-20-2009 12:55 PM
Re: Vpar software upgrade landed in panic-Urgent
MON>reboot
Issue Solved