- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vPar no more boot
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
тАО11-30-2010 10:40 AM
тАО11-30-2010 10:40 AM
I am currently in the process of migrating some vPars from one san Netapp cluster storage to a new one.
The vPars rely on an old RP7420 and run under HP-UX 11iv1 / vPar A.03.02.04.
All the vPar are booted from the SAN.
LVM mirror is installed but not used because mirroring is done at the storage side
I have no access to manage the SAN, nor the storage. The client has :-(
To test the procedure, I mirrored the whole vg00 of a given vPar to a lun from the new Netapp Storage. Maybe I did a mistake at this step, but I guess that mirroring was correctly done.
Then to test the new boot pathes, I have stopped the vPar and from a second vPar I have modified boot path and alt boot path to point to the mirror.
Now the modified vPar no more boot : failed to open 1/0/14/1/0/4/0.6.18.0.0.1.5/stand/vmunix :-(((( Same behaviour with the 3 others paths (0/0/10/1/0/4/0.5.21.0.0.1.5, 1/0/14/1/0/4/0.2.18.0.0.1.5 and 0/0/10/1/0/4/0.1.18.0.0.1.5)
Well, I have tried to configure back the original pathes, BUT I CAN'T BOOT ANYMORE from the original LUN :-(((((( [1/0/14/1/0/4/0.6.0.0.0.1.5, 0/0/10/1/0/4/0.5.0.0.0.1.5, 1/0/14/1/0/4/0.2.0.0.0.1.5 and 0/0/10/1/0/4/0.1.0.0.0.1.5]
The original LUN has been presented to an other vPar. I did an import and with a read-only access I have checked that /stand is OK. It is.
I have some doubts around the SAN. Some questions :
- From the SAN switches, the ports where the faulty vPar is connected are seen down. In fact I don't know if, when a vPar is done but the nPar is running vpmon and some other vPars, the ports of the halted vPar should be seen up or not ?
- Each week end all the vPar are rebooted (the nPar is not) and it works. The difference is that I did a stop of the vPar, then a boot. I mean, could we imagine that when a vPar is rebooted the HBA are kept logged in the fabric, but not when the vPar is stopped ?
- Just before the SAN admin leaves the office, I have seen that the port of the san switches are configured at 4 Gb. But the FC cards in the vPars are A9784-60001, that is 2 Gb HBA. How this configuration can work ????
Tomorrow moring (GMT), I plan to try to launch an ignite install to check if I can see the san disks. While waiting for that, any idea ?
Thanks in advance
Eric
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2010 10:52 AM
тАО11-30-2010 10:52 AM
Re: vPar no more boot
In the past I used the "dot only" notation, but I had problems with it. From a certain version on (don't remember exactly), you can use the hardware path (with dots and slashes), like
1/0/14/1/0/4/0.2.0.0.0.1.5:BOOT
instead of
1.0.14.1.0.4.0.2.0.0.0.1.5.0.0.0:BOOT
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
тАО11-30-2010 11:02 AM
тАО11-30-2010 11:02 AM
SolutionThe OS has the control over the HBAs. If the OS is down, the HBA is uninitialized, but powered. AFAIR the card is no longer logged into the fabric once the OS is down.
Depending on the HBA you will see all speed indicator LEDs blinking until the driver takes control.
But if the switch port is fixed at 4Gb, but the HBA is 2Gb only, this cannot work IMHO.
On the other hand, if the connection server <-> switch is at 2Gb and the switch <-> storage is at 4Gb, this is not a problem.
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
тАО11-30-2010 12:19 PM
тАО11-30-2010 12:19 PM
Re: vPar no more boot
Please to meet you back.
"... dot notation ..." : in fact I totally forgot that it was the very first way to design a vpar resource. So I did my tests only with hardware path notation. To apologize myself, I will say that I have not been working with vPars for months and probably years ! I will try tomorrow.
"... AFAIR the card is no longer logged into the fabric" : ok, but when the vpar is trying to acces the LUN, I should catch something on the san switch. I will try ... if I can get IP, user and password of the switchs :-(
"... you will see all speed indicator ..." : no access is possible to the rooms without the san admin. And they leave soon here !
"... this cannot work IMHO. ..." : I think too. I need to clarify this tomorrow
May be I did a big mistake when I took the mirror copy, but the fact that I can access /stand/system from an other vPar let me think that it is not the case. And lvlnboot was OK before I stopped the VM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2010 10:57 PM
тАО11-30-2010 10:57 PM
Re: vPar no more boot
There are some critical points here.
Doing the mirroring wrong (it's easy by mixing up the disk device files - whole disks instead of partition 2 in some steps for example).
Creating the ...:BOOT and ...:ALTBOOT entries in vPars configuration. If this doesn't match the vPar will not boot.
Maybe the vpmon log has more information.
AFAIR this is "vparstatus -e" - but I'm not sure at the moment.
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
тАО11-30-2010 11:29 PM
тАО11-30-2010 11:29 PM
Re: vPar no more boot
1/0/4/0.1.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (0/0/10/1/0/4/0.1.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (0/0/10/1/0/4/0.1.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:25:34 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:25:38 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:25:45 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:25:50 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:25:57 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:26:02 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.2.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.2.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.2.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:26:20 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:26:25 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.2.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.2.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.2.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:26:36 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:26:40 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:29:09 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:29:14 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:30:32 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:30:37 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5.0;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5.0;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5.0;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:31:28 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
INFO:CPU0:MON:[2010-11-30 16:31:32 UTC] Interact has been stopped on manu
INFO:CPU3:masterp:manu: hard reset
INFO:CPU0:MON:[2010-11-30 16:33:39 UTC] Interact has been stopped on manu
INFO:CPU3:masterp:resetting CPU0
INFO:CPU0:MON:[2010-11-30 16:34:08 UTC] Interact has been stopped on manu
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
WARNING:CPU0:MON:Unknown filesystem for path (0/0/10/1/0/4/0.5.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (0/0/10/1/0/4/0.5.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (0/0/10/1/0/4/0.5.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:[2010-11-30 16:34:16 UTC] manu load failed
ERROR:CPU0:MON:Could not load manu, error = -4
root@hp22:/>vparstatus -m
Console path: 1.0.0.0.1.0.0.0.0.0.0
Monitor Boot disk path: 1.0.14.1.0.4.0.6.0.0.0.1.5
Monitor Boot filename: /stand/vpmon
Database filename: /stand/vpdb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2010 11:55 PM
тАО11-30-2010 11:55 PM
Re: vPar no more boot
WARNING:CPU0:MON:Unknown filesystem for path (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to open (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
ERROR:CPU0:MON:Failed to load (1/0/14/1/0/4/0.6.0.0.0.1.5;)/stand/vmunix
When you try to boot from the "old" disks, did you adjust the ...:BOOT device configuration?
Are you able to boot the system in nPar mode?
Doing this may help to check the pathes.
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
тАО11-30-2010 11:56 PM
тАО11-30-2010 11:56 PM
Re: vPar no more boot
------------
c2t1d5 : source dd
c26t1d5 : mirror dd
pvcreate -fB /dev/rdsk/c26t1d5
mkboot -l /dev/rdsk/c26t1d5
lifcp /dev/dsk/c2t1d5:AUTO /tmp/AUTO.$$
mkboot -a "$(cat /tmp/AUTO.$$)" /dev/rdsk/c26t1d5
mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p HPUX -p ISL -p AUTO -p LABEL -p PAD /dev/rdsk/c26t1d5
vgextend vg00 /dev/dsk/c26t1d5
For each lvol, in their order on the source PV :
lvextend -m 1 $LVOL /dev/dsk/c26t1d5
lvlnboot -R
lvlnboot -v
----------------
Did nothing with setboot because I planned to do it with vparmodify from a second vPar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2010 11:59 PM
тАО11-30-2010 11:59 PM
Re: vPar no more boot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 02:19 AM
тАО12-01-2010 02:19 AM
Re: vPar no more boot
May be something became wrong in boot volume
info.
Perhaps you may also test trying LVM maintenance boot mode, for example using:
# vparboot -p vparname -o '-lm'
Albertino