- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: setboot no longer give access to stable storag...
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
Forums
Discussions
Discussions
Discussions
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
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
06-16-2006 01:42 AM
06-16-2006 01:42 AM
setboot no longer give access to stable storage variables in vpar mode
i am working with vPar A.03.02.04 / HP-UX 11iv1 on an RP7420.
For documentation purpose (read only) i need to get stable storage primary path and alternates path.
But setboot gives BOOT and ALTBOOT values of the vPar on which i run the command, not the boot variables in nonvolatile memory. Of course i cannot ask my client to stop all the complex to get those values !
So any idea on how to do that ?
Thanks in advance
Eric
PBFWME
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2006 01:51 AM
06-16-2006 01:51 AM
Re: setboot no longer give access to stable storage variables in vpar mode
The only way to access the stable storage is to reboot and stop at BCH.
If you set pri and alt path to the both disks of your first vPAR, you won't need to change it later, regardless of the configuration of other vPars.
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
06-16-2006 01:59 AM
06-16-2006 01:59 AM
Re: setboot no longer give access to stable storage variables in vpar mode
unfortunatly i know all of that. What i do search for is a way to bypass this f.....g behavior.
Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2006 03:08 AM
06-16-2006 03:08 AM
Re: setboot no longer give access to stable storage variables in vpar mode
The only way out IMHO is to go to GSP/MP and scroll back the console log, maybe you can see the messages from last boot.
Try it!
MP> cl
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
07-20-2006 02:12 AM
07-20-2006 02:12 AM