HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Problem booting from the VA
HPE EVA Storage
1834462
Members
3336
Online
110067
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
02-25-2004 08:34 AM
02-25-2004 08:34 AM
Problem booting from the VA
Hi,
I have a Superdome partioned 4 ways. Each of the cells has an HBA. Two of the cells are booting off a VA controller.
LUN security is in place to ensure that only the nodes that requires access to the LUNS can see them.
When I reboot the cells that boot off the VA I get a message suggesting that the LUN is unavailable.
bo
Primary Boot Path: 2/0/14/0/0.22.18.0.0.5.1
Do you wish to stop at the ISL prompt prior to booting? (y/n) >> n
Initializing boot Device.
Boot IO Dependent Code (IODC) Revision 2
IODC ENTRY_INIT failed. Error Status: -7
0x0000 00000000fffffff9 0000000000000000 00000000fcfc05ca 000000000000012d
0x0004 00000000fc00009d 0000000000000065 00000000fc00009d 0000000000000065
0x0008 00000000fc00009d 0000000000000065 00000000fc00009d 0000000000000065
0x000c 00000000fc00009d 0000000000000065 0000000000000000 0000000000000000
0x0010 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0014 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0018 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x001c 0000000000000000 0000000000000000 0000000000000000 0000000000000000
If I reset all the cells and boot the VA served partitions first I can see the disks. Also, if I boot off a CD, I can see the disks without resetting the other partitions.
How can I check access to the SAN hosted disks from the GSP before I attempt to boot, secondly does anybody know why I amseeing this.
Thanks
Laurence Oberman
I have a Superdome partioned 4 ways. Each of the cells has an HBA. Two of the cells are booting off a VA controller.
LUN security is in place to ensure that only the nodes that requires access to the LUNS can see them.
When I reboot the cells that boot off the VA I get a message suggesting that the LUN is unavailable.
bo
Primary Boot Path: 2/0/14/0/0.22.18.0.0.5.1
Do you wish to stop at the ISL prompt prior to booting? (y/n) >> n
Initializing boot Device.
Boot IO Dependent Code (IODC) Revision 2
IODC ENTRY_INIT failed. Error Status: -7
0x0000 00000000fffffff9 0000000000000000 00000000fcfc05ca 000000000000012d
0x0004 00000000fc00009d 0000000000000065 00000000fc00009d 0000000000000065
0x0008 00000000fc00009d 0000000000000065 00000000fc00009d 0000000000000065
0x000c 00000000fc00009d 0000000000000065 0000000000000000 0000000000000000
0x0010 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0014 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x0018 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0x001c 0000000000000000 0000000000000000 0000000000000000 0000000000000000
If I reset all the cells and boot the VA served partitions first I can see the disks. Also, if I boot off a CD, I can see the disks without resetting the other partitions.
How can I check access to the SAN hosted disks from the GSP before I attempt to boot, secondly does anybody know why I amseeing this.
Thanks
Laurence Oberman
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2004 02:10 PM
02-25-2004 02:10 PM
Re: Problem booting from the VA
Hi,
Look for the wwidmgr command at the SRM prompt.
With this command you can set the wwid's of the HBA for the 2 partitions that boot off the VA.
You have to enable the wwid path/paths to see the device you are booting from.
Hope this helps.
Regards,
Orrin.
Look for the wwidmgr command at the SRM prompt.
With this command you can set the wwid's of the HBA for the 2 partitions that boot off the VA.
You have to enable the wwid path/paths to see the device you are booting from.
Hope this helps.
Regards,
Orrin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2004 06:35 PM
02-25-2004 06:35 PM
Re: Problem booting from the VA
Orrin,
the 'Superdome' is a HP pre-merger product and likely equiped with PA-RISC CPUs running HP-UX operating system. (can't help with the original problem, sorry)
the 'Superdome' is a HP pre-merger product and likely equiped with PA-RISC CPUs running HP-UX operating system. (can't help with the original problem, sorry)
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2004 12:36 AM
02-26-2004 12:36 AM
Re: Problem booting from the VA
Thanks for attempting to help here.
I have additional information. I can leave cells 0 and 4 up, but in order to boot cell 2, I have to first shutdown cell 6.
Very strange. This is not a VA or FC problem, rather seems to be a console/GSP issue.
The Partitions are as follows:
[Partition]
Par # of # of I/O
Num Status Cells Chassis Core cell Partition Name (first 30 chars)
=== ============ ===== ======== ========== ===============================
0 active 1 1 cab0,cell0 mustang
1 active 1 1 cab0,cell4 Spitfire
2 active 1 1 cab0,cell6 nnm
3 active 1 1 cab0,cell2 nnm2
I have additional information. I can leave cells 0 and 4 up, but in order to boot cell 2, I have to first shutdown cell 6.
Very strange. This is not a VA or FC problem, rather seems to be a console/GSP issue.
The Partitions are as follows:
[Partition]
Par # of # of I/O
Num Status Cells Chassis Core cell Partition Name (first 30 chars)
=== ============ ===== ======== ========== ===============================
0 active 1 1 cab0,cell0 mustang
1 active 1 1 cab0,cell4 Spitfire
2 active 1 1 cab0,cell6 nnm
3 active 1 1 cab0,cell2 nnm2
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP