- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Optimum multipath configuration with P4500 Nodes.
StoreVirtual Storage
1754279
Members
3265
Online
108813
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-01-2011 06:06 AM
тАО06-01-2011 06:06 AM
Optimum multipath configuration with P4500 Nodes.
Hi there,
We've just recently set up a new VMWare Cluster and a 3-node P4500 SAN.
So far everything is working quite well. I used this document to configure the MPIO: http://www.scribd.com/doc/24586958/Configuring-Left-Hand-ISCSI-and-VSPHERE-MPIO
Our configuration was just a little different. The VMWAre host has 4 on-board NIC's plus another 4 added by using a PCI-X board. We've therefore got 3 NIC's allocated for the data/management network, 3 for the Storage Network and then 2 just for vMotion. It seems though that the configuration is working as for each LUN I can see 3 paths are being established (one for each NIC).
I understand that in Storage Views the multipathing status shows as 'Partial/No Redundancy' and this is because all connections ultimately rely on the software iSCSI initiator.
However, in my case I can also see that the 4-port NIC i've added to the Server reports as being a 'Broadcom iSCSI Adapter'. Below the interface it shows me 4 vmhba entries which I guess must relate to the 4 NIC ports.
Does this mean that I can use the 'esxcfg-vmknic' command to bind the appropraite vmk interface to these vmhba ports? And would doing so provide me better resilience as I wouldn't be relying on the software initiator?
Thanks for any pointers that you might be able to offer. :)
Pete
We've just recently set up a new VMWare Cluster and a 3-node P4500 SAN.
So far everything is working quite well. I used this document to configure the MPIO: http://www.scribd.com/doc/24586958/Configuring-Left-Hand-ISCSI-and-VSPHERE-MPIO
Our configuration was just a little different. The VMWAre host has 4 on-board NIC's plus another 4 added by using a PCI-X board. We've therefore got 3 NIC's allocated for the data/management network, 3 for the Storage Network and then 2 just for vMotion. It seems though that the configuration is working as for each LUN I can see 3 paths are being established (one for each NIC).
I understand that in Storage Views the multipathing status shows as 'Partial/No Redundancy' and this is because all connections ultimately rely on the software iSCSI initiator.
However, in my case I can also see that the 4-port NIC i've added to the Server reports as being a 'Broadcom iSCSI Adapter'. Below the interface it shows me 4 vmhba entries which I guess must relate to the 4 NIC ports.
Does this mean that I can use the 'esxcfg-vmknic' command to bind the appropraite vmk interface to these vmhba ports? And would doing so provide me better resilience as I wouldn't be relying on the software initiator?
Thanks for any pointers that you might be able to offer. :)
Pete
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2011 07:29 AM
тАО06-01-2011 07:29 AM
Re: Optimum multipath configuration with P4500 Nodes.
Just to clarify - I got my config the wrong way around. The onboard NIC's are Broadcom and the additional NIC's are provided by a NetXen PCI-X board.
I've managed to get a configuration working which describes things as 'fully redundant' but I need to get my head around how it should actually be constructed in the system. ;)
I've managed to get a configuration working which describes things as 'fully redundant' but I need to get my head around how it should actually be constructed in the system. ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2011 04:31 AM
тАО06-02-2011 04:31 AM
Re: Optimum multipath configuration with P4500 Nodes.
Hi,
What you need to do is create a VMKernel port for each NIC you will use for iscsi trafic. Than all these VMKernel ports must be bound to the vmhba adapter of the iscsi initiator...
All is explained in the following document: http://h41112.www4.hp.com/promo/master_ESS-Trilogy-4/uk/en/pdf/Documentations/Virtualization/Running%20VMware%20vSphere%204%20on%20HP%20P4000%20SAN.pdf
So you enable full mpio and load balancing inside ESX...
Kr,
Bart
What you need to do is create a VMKernel port for each NIC you will use for iscsi trafic. Than all these VMKernel ports must be bound to the vmhba adapter of the iscsi initiator...
All is explained in the following document: http://h41112.www4.hp.com/promo/master_ESS-Trilogy-4/uk/en/pdf/Documentations/Virtualization/Running%20VMware%20vSphere%204%20on%20HP%20P4000%20SAN.pdf
So you enable full mpio and load balancing inside ESX...
Kr,
Bart
--------------------------------------------------------------------------------
If my post was useful, clik on my KUDOS! "White Star" !
If my post was useful, clik on my KUDOS! "White Star" !
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