- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: Problem with an EVA 3000 and VMware ESX 3.0
MSA Storage
1752866
Members
3927
Online
108791
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
Forums
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
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
тАО09-14-2006 07:44 AM
тАО09-14-2006 07:44 AM
Problem with an EVA 3000 and VMware ESX 3.0
Hi
I have one EVA 3000, 2 ESX 3.0 servers ( with one QLA2340 each server ), and two Brocade Switches.
I have created two Port Zones and applied the configuration
Zone ESX1
Port 0 Controller A port 1
Port 4 Controller B port 1
Port 7 ESX1 ( Server name )
Zone ESX2
Port 0 Controller A port 2
Port 4 Controller B port 2
Port 7 ESX2 ( Server name )
I have created a LUN ( Lun number 1) of 30GB, masking to both ESX servers.
In Virtual Infrastructure Client - > Configuration -> Storage Adapter I have done a rescan but I see two LUN 0 but not LUN 1 (30GB). LUN 0 seems to be the controller, is correct?. Why can't see the LUN1?.
If I delete Port 4 of the Zone ESX1 and Zone ESX 2 and apply the configuration, I see correctly LUN 0 and LUN 1 but in the event of a controller failure I don't have redundancy. How can I get this redundancy?. Is correct my configuration with only one HBA and EVA 3000?.
Could anyone help me?.
Thanks in advance,
I have one EVA 3000, 2 ESX 3.0 servers ( with one QLA2340 each server ), and two Brocade Switches.
I have created two Port Zones and applied the configuration
Zone ESX1
Port 0 Controller A port 1
Port 4 Controller B port 1
Port 7 ESX1 ( Server name )
Zone ESX2
Port 0 Controller A port 2
Port 4 Controller B port 2
Port 7 ESX2 ( Server name )
I have created a LUN ( Lun number 1) of 30GB, masking to both ESX servers.
In Virtual Infrastructure Client - > Configuration -> Storage Adapter I have done a rescan but I see two LUN 0 but not LUN 1 (30GB). LUN 0 seems to be the controller, is correct?. Why can't see the LUN1?.
If I delete Port 4 of the Zone ESX1 and Zone ESX 2 and apply the configuration, I see correctly LUN 0 and LUN 1 but in the event of a controller failure I don't have redundancy. How can I get this redundancy?. Is correct my configuration with only one HBA and EVA 3000?.
Could anyone help me?.
Thanks in advance,
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2006 09:01 AM
тАО09-14-2006 09:01 AM
Re: Problem with an EVA 3000 and VMware ESX 3.0
> LUN 0 seems to be the controller, is correct?
yes. it is the "Storage Array Controller Device" which is used for in-band management and LUN inquiry.
It sounds like the virtual disk is owned by controller A, but ESX is confused by the standby path from controller B. Did you check within the adapter BIOS (Fibre Disk Utility) whether it can see LUN 1?
For redundancy, I really would equip both servers with two fibre channel adapter ports (either two adapters or one dual-port adapter).
yes. it is the "Storage Array Controller Device" which is used for in-band management and LUN inquiry.
It sounds like the virtual disk is owned by controller A, but ESX is confused by the standby path from controller B. Did you check within the adapter BIOS (Fibre Disk Utility) whether it can see LUN 1?
For redundancy, I really would equip both servers with two fibre channel adapter ports (either two adapters or one dual-port adapter).
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2006 01:23 AM
тАО09-15-2006 01:23 AM
Re: Problem with an EVA 3000 and VMware ESX 3.0
Hi,
what version of VCS do you have on the EVA3000?
If you have VCS 3.xxx then your cabling is wrong - Controller A Port 1 and Controller B Port 2 should be on the one switch, and A2/B1 on the other.
If you have VCS 4.xxx then the cabling is correct, but this VCS is not supported for ESX 3.0. It's not in VMware's support matrix, and there is no support stream from HP for ESX 3 with EVA3000 VCS 4.x.
Regards,
Stephen
what version of VCS do you have on the EVA3000?
If you have VCS 3.xxx then your cabling is wrong - Controller A Port 1 and Controller B Port 2 should be on the one switch, and A2/B1 on the other.
If you have VCS 4.xxx then the cabling is correct, but this VCS is not supported for ESX 3.0. It's not in VMware's support matrix, and there is no support stream from HP for ESX 3 with EVA3000 VCS 4.x.
Regards,
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2006 11:48 PM
тАО09-18-2006 11:48 PM
Re: Problem with an EVA 3000 and VMware ESX 3.0
Thank you very much for your help.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP