- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- ESX on EVA - Console LUN ID?
HPE EVA Storage
1819872
Members
2648
Online
109607
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
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
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
08-29-2006 01:39 AM
08-29-2006 01:39 AM
ESX on EVA - Console LUN ID?
I have ESX 2.5.3 in production on an EVA 4000. Whenever I go to Storage Management I always get a pop-up about the partition table & "geometry info is invalid". After clicking OK to rescan the SAN, everything is fine. I have been told this is due to a management LUN on the SAN (Console LUN ID = 0 ?).
Is there some way to mask this management LUN or change it to a higher number to prevent this pop-up all the time? I have attached a screenshot of the pop-up & CommandView EVA settings. We only have one shelf and it is partitioned as a single 655GB vdisk\LUN - we might be getting another shelf, but I'm not worried about hitting the default maximum LUN count for awhile.
thanks,
mike
Is there some way to mask this management LUN or change it to a higher number to prevent this pop-up all the time? I have attached a screenshot of the pop-up & CommandView EVA settings. We only have one shelf and it is partitioned as a single 655GB vdisk\LUN - we might be getting another shelf, but I'm not worried about hitting the default maximum LUN count for awhile.
thanks,
mike
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2006 05:08 AM
08-29-2006 05:08 AM
Re: ESX on EVA - Console LUN ID?
The SACD (Storage Array Controller Device, in EVA's terminology) is needed for in-band management and SCSI-3 style LUN detection. It cannot be disabled or moved to another LUN *address*.
You can change, what is shown as the so-called "Console LUN ID" in CV-EVA, but:
- it does *not* change the LUN *address*
-- (the last zero in "vmhba1:0:0")
- VMware ESX server does not use this *ID* anyway
I currently have ESX V2.5.3 patch3 running on an EVA4000 and I do not get that message, by the way. What value did you choose as "Host OS Type"?
Some other notes:
- the minimum required XCS revision is V5.031, but you EVA is at V5.020
- there should be a minimum of 5 raw GigaBytes free in a disk group, your array is *way* below this level
You can change, what is shown as the so-called "Console LUN ID" in CV-EVA, but:
- it does *not* change the LUN *address*
-- (the last zero in "vmhba1:0:0")
- VMware ESX server does not use this *ID* anyway
I currently have ESX V2.5.3 patch3 running on an EVA4000 and I do not get that message, by the way. What value did you choose as "Host OS Type"?
Some other notes:
- the minimum required XCS revision is V5.031, but you EVA is at V5.020
- there should be a minimum of 5 raw GigaBytes free in a disk group, your array is *way* below this level
.
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP