GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Boot from MSA1000
MSA Storage
1848187
Members
4411
Online
104022
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
Forums
Discussions
back
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
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-19-2003 05:59 AM
02-19-2003 05:59 AM
Boot from MSA1000
I have 5 identical ML350G3 servers with FCA2101 hba's. The first server i have set up for boot from san, no problems there.
However the additional servers can not see their respective bootdevices when configuering the HBA. I follow the whitepaper "Boot fra MSA1000" to a tee.
I have created a LUN for each server to boot from, and assigned it to the proper HBA using SSP. But its a no go.
I have updated firmware and drives to the latest editions, tried different Scan settings (bullet point 6) in the HBA bios config.
The servers are unable to see their boot LUN.
When booting from the MSA1000-cd the servers kan see the MSA1000, and its arrays and LUN's.
What to do ?
However the additional servers can not see their respective bootdevices when configuering the HBA. I follow the whitepaper "Boot fra MSA1000" to a tee.
I have created a LUN for each server to boot from, and assigned it to the proper HBA using SSP. But its a no go.
I have updated firmware and drives to the latest editions, tried different Scan settings (bullet point 6) in the HBA bios config.
The servers are unable to see their boot LUN.
When booting from the MSA1000-cd the servers kan see the MSA1000, and its arrays and LUN's.
What to do ?
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 2026 Hewlett Packard Enterprise Development LP