- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- MPIO for Hardware iSCSI HBAs
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
05-09-2014 06:57 AM
05-09-2014 06:57 AM
Dear community.
I have a setup that is slightly ancient, but trying to get running under best possible configuration.
I am running ESX4 (not ESXi), on Dell servers with HARDWARE QLOGIC iSCSI HBAs.
I only have 2 hardware HBAS and reading the Nimble vmware setup document (page 69) states that the software NCM is not supported with H/W iSCSI. Set my path selection policy to "round robin".
Therefore, when I connect my H/W iSCSI HBA in storage adapters and point this at my Nimble group IP, it shows up the created volumes and allows me to connect.
However, it only speaks to the Nimble on one of the nimble ports, not all FOUR - which I would expect with or without the NCM.
If I disconnect the active link, then I loose my storage.
My question is - what is the best setup practice for ESX 4 with hardware iSCSI HBAs and in doing so, should I expect my storage volumes to path over all 4 iSCSI nics on the nimble?
(Is there anything I am missing, perhaps a way to implement the MPIO or path selection policy?)
Thanks
Egroeg
Solved! Go to Solution.
- Tags:
- esx4
- hardware iscsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2014 07:14 AM
05-09-2014 07:14 AM
SolutionHey George,
Did you follow the MPIO script required to create multiple paths? As the environment is Essentials licensing the VMware PSP would not be applicable - so this would be the best thing to do. I'm pretty sure this should apply for hardware HBAs as it does with software.
From:
Importance of Path Change Settings in VMware
Firstly run:
esxcli nmp satp addrule --psp VMW_PSP_RR --satp VMW_SATP_ALUA --vendor Nimble
Which sets a policy for all volumes from the vendor of Nimble to be automatically set to Round Robin rather than Most Recently Used.
Then:
Set
for i in `esxcli storage nmp device list | awk '/Nimble iSCSI Disk/{print $7}' | sed -e 's/(//' -e 's/)//'`; do
echo $i ;
esxcli storage nmp psp roundrobin deviceconfig set -d $i -t bytes -B 0;
esxcli storage nmp psp roundrobin deviceconfig set -d $i -t iops -I 0 ;
esxcli storage nmp psp roundrobin deviceconfig get -d $i;
done
Which should create multiple paths for you.
Let me know how you get on....
twitter: @nick_dyer_