- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: iSCSI considerations on MSA 2050
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
Discussions
Discussions
Forums
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
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
тАО02-26-2021 05:38 AM
тАО02-26-2021 05:38 AM
iSCSI considerations on MSA 2050
Hello,
My english is not very good, please, excuse me...
We have a HPE MSA 2050 with 4 iSCSI 10Gb adapters (2 per controllers) connected to a Nexus switch.
A1 : 10.10.1.10 / B1: 10.10.2.10
A2 : 10.10.1.11 / B2 : 10.10.2.11
ESXi 6.5 U3 is using this storage with 10Gb dedicated cards.
On ESXi, we have 2 vmkernel with diffrent ip subnet associated to 2 d├йdicated cards :
-1 10GB card with subnet 10.10.1.0/22
-a second 10GB card subnet 10.10.2.0/22.
We use a software iSCSI adapter without port binding (as preconised by vmware) from ESXi host.
All LUNs of the MSA are visible.
But, As preconised by tech specs HPE, msa volumes starts at LUN number 1 to free up "LUN 0" (enclosure reserved)
Consequence : ISCSI software on the ESXI shows a LUN0 named "enclosure". Why ? How to mask it ? So, it counts a total of 20 patchs instead of 16 (8/subnets), and LUN0 is not an array storage...
I activate onthe msa the option "Missing LUN response : Illegal Request"
Thanks for your help !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2021 06:07 AM
тАО02-26-2021 06:07 AM
Re: iSCSI considerations on MSA 2050
I forget to indicate that ESXi have not yeat rebooted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2021 01:43 AM
тАО03-01-2021 01:43 AM
Re: iSCSI considerations on MSA 2050
Hi,
The HPE MSA Storage enclosure is presented to vSphere as a Fibre Channel enclosure using LUN 0. This means all volumes mapped to the vSphere hosts or clusters must not use LUN 0. The SMU software doesnтАЩt automatically detect this and for each mapping created, it defaults to LUN 0.
Reference page 27 of MSA best practices guide for VMWARE:
https://psnow.ext.hpe.com/doc/4aa4-7060enw?jumpid=in_lit-psnow-red
Do not make any changes to MSA enclosure entry showing up in ESXI.
Its the command console lun id for control commands.
While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2021 01:38 PM
тАО03-08-2021 01:38 PM
Re: iSCSI considerations on MSA 2050
Hello,
Thanks but i've already read this paper. Under vCenter, because of enclosure, i see 2 additionnal path with my iSCSI adaptater pointing to enclosure LUN 0 ! Instead of 4 paths to my volumes, it adds 2 paths to enclosure. Is it normal ?
Under MSA, i start LUN number at number 1.
In the beginning, i fogot the rule of LUN 0. So i had a volume on MSA starting with LUN0 and vCenter seeing just 4 paths. I recreated the volume with LUN0 and then, vCenter shows 6 paths...