GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- VMWare 2.5 and HSG80 support
MSA Storage
1849367
Members
5938
Online
104044
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-22-2006 09:46 PM
02-22-2006 09:46 PM
VMWare 2.5 and HSG80 support
Has anybody configured a HSG80 to run with VMWare 2.5 - did you use scsi_version 2 and not scsi_version 3.
Any help is appreciated
Any help is appreciated
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2006 10:57 PM
02-22-2006 10:57 PM
Re: VMWare 2.5 and HSG80 support
Haven't tried it - I assume you know that this configuration is unsupported, but if you are willing to try:
the difference between SCSI_VERSION = SCSI-2 and SCSI-3 is that with SCSI-3 the CCL is permanently mapped to LUN #0. The kernel moans about 'unknown device type 12' (right, 12 means array device!), but the same message appears when using other storage arrays like the EVA or MSA which always map their equivalent of the CCL at LUN #0.
It is my understanding the VMware ESX server does a LUN scan instead of a 'REPORT LUNS' function anyway, so it should 'work' with both settings.
the difference between SCSI_VERSION = SCSI-2 and SCSI-3 is that with SCSI-3 the CCL is permanently mapped to LUN #0. The kernel moans about 'unknown device type 12' (right, 12 means array device!), but the same message appears when using other storage arrays like the EVA or MSA which always map their equivalent of the CCL at LUN #0.
It is my understanding the VMware ESX server does a LUN scan instead of a 'REPORT LUNS' function anyway, so it should 'work' with both settings.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2006 03:15 AM
02-23-2006 03:15 AM
Re: VMWare 2.5 and HSG80 support
Hi Thanks,
I have managed to get working on the HSG80 with scsi_version=scsi-3 on the controller config (VMware GSX does not support scsi-3 -only scsi-2)
Also:
VMWare ESX by default only will scan for the first 8 presented LUNS so there is a GUI switch required called DiskMaxLunif needing to see more than 8 luns.
I have managed to get working on the HSG80 with scsi_version=scsi-3 on the controller config (VMware GSX does not support scsi-3 -only scsi-2)
Also:
VMWare ESX by default only will scan for the first 8 presented LUNS so there is a GUI switch required called DiskMaxLunif needing to see more than 8 luns.
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