- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- P4300 / Procurve 2910AL / VMWare 4 ESXi
StoreVirtual Storage
1753852
Members
7796
Online
108808
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
тАО06-30-2010 09:29 PM
тАО06-30-2010 09:29 PM
P4300 / Procurve 2910AL / VMWare 4 ESXi
Hi all,
We are having lots of trouble with a brand new P4300 and getting redundancy to work..
I've included the two SAN configures, but otherwise we have the following:
2x dl380g6 with additional HP NC364T PCI Express Quad Port Gigabit Server Adapter per server
Part of P4300
Two switches have been configured for redundancy for the P4300's in the case of
a switch failure.
In all cases, our VMware server loses connectivity to all path's (there are two
per Lun) when one of the switch is
off, or just one of the paths (which is expected) when the other is off. This is
however random and can change from switch to switch.
We have tried the SAN in both non bonded and bonded (using ALB).
We are seeing wierd things like all of the SAN's ports showing up on an show arp on the procurve showing as directly connected to just one switch, even though they have cables redundanty connected from port 1 to san-sw011 and port 2 to san-sw02 and so on...
It doesn't seem that there is any documentation on how to configure a Procurve with the Lefthand and VMWare, which I would have thought was a pretty common scenario..
We have also read and implemented from the following:
http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-0261ENW.pdf
http://virtualgeek.typepad.com/virtual_geek/2009/09/a-multivendor-post-on-using-iscsi-with-vmware-vsphere.html
I'm sure you will have more questions of me..
We are having lots of trouble with a brand new P4300 and getting redundancy to work..
I've included the two SAN configures, but otherwise we have the following:
2x dl380g6 with additional HP NC364T PCI Express Quad Port Gigabit Server Adapter per server
Part of P4300
Two switches have been configured for redundancy for the P4300's in the case of
a switch failure.
In all cases, our VMware server loses connectivity to all path's (there are two
per Lun) when one of the switch is
off, or just one of the paths (which is expected) when the other is off. This is
however random and can change from switch to switch.
We have tried the SAN in both non bonded and bonded (using ALB).
We are seeing wierd things like all of the SAN's ports showing up on an show arp on the procurve showing as directly connected to just one switch, even though they have cables redundanty connected from port 1 to san-sw011 and port 2 to san-sw02 and so on...
It doesn't seem that there is any documentation on how to configure a Procurve with the Lefthand and VMWare, which I would have thought was a pretty common scenario..
We have also read and implemented from the following:
http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-0261ENW.pdf
http://virtualgeek.typepad.com/virtual_geek/2009/09/a-multivendor-post-on-using-iscsi-with-vmware-vsphere.html
I'm sure you will have more questions of me..
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2010 04:02 AM
тАО07-01-2010 04:02 AM
Re: P4300 / Procurve 2910AL / VMWare 4 ESXi
Sounds like you may have MAC flapping. But I believe the SAN side of the equation should only receive on one port (arp on one switch) but send from both when using ALB. So you should see the mac on one switch, and then on failure of that switch...it should be on the second.
Do you have a trunk setup between the switches? You will not want two completely independent cables connecting the two or it will cause STP issues.
Do you have a trunk setup between the switches? You will not want two completely independent cables connecting the two or it will cause STP issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-03-2010 04:58 AM
тАО07-03-2010 04:58 AM
Re: P4300 / Procurve 2910AL / VMWare 4 ESXi
Andrew,
When you say you have multiple paths do you mean multiple storage paths (configuration -> storage adapters) or just multiple network paths (configuration -> networking)? My preferred configuration is to create two storage paths (must use command line, can't do it in the GUI) and bond them to two different adapters. This way a physical link failure translates directly into a single storage path failure and storage connectivity isn't (shouldn't) be lost when a single switch goes down. With a single storage path and multiple network links the iSCSI connection will often drop and reconnect during a switch failure or restart.
When you say you have multiple paths do you mean multiple storage paths (configuration -> storage adapters) or just multiple network paths (configuration -> networking)? My preferred configuration is to create two storage paths (must use command line, can't do it in the GUI) and bond them to two different adapters. This way a physical link failure translates directly into a single storage path failure and storage connectivity isn't (shouldn't) be lost when a single switch goes down. With a single storage path and multiple network links the iSCSI connection will often drop and reconnect during a switch failure or restart.
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