Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- p4000 vmware iscsi configuration help
StoreVirtual Storage
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
Go to solution
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-31-2011 04:48 AM
03-31-2011 04:48 AM
To all,
Attached is an overview of the ESX host iSCSI based connectivity. Page one shows that from the ESX perspective, the software iSCSI initiator (vmhba41) thinks that the connection is to 10.0.2.1 (LSC0,Cluster 0). The datastore map shows the connection reflecting the singular node connection, LSN0 for most of the datastores, and LSN1 for datastore VMFS5.
Digging further (although not represented on this spreadsheet), the iSCSI connection for a virtual server LSS017 as a mounted iSCSI device out of Server 2003 also indicates the connection pointing to 10.0.2.1, but mapping to the specific node LSN2 at 10.0.2.12.
It does seem a little odd that all these devices are at least initiating to the cluster IP, then getting assigned to specific NODE addresses. Hope someone can put a second pair of eyes on this to help.
Thank you in advance,
Todd
Attached is an overview of the ESX host iSCSI based connectivity. Page one shows that from the ESX perspective, the software iSCSI initiator (vmhba41) thinks that the connection is to 10.0.2.1 (LSC0,Cluster 0). The datastore map shows the connection reflecting the singular node connection, LSN0 for most of the datastores, and LSN1 for datastore VMFS5.
Digging further (although not represented on this spreadsheet), the iSCSI connection for a virtual server LSS017 as a mounted iSCSI device out of Server 2003 also indicates the connection pointing to 10.0.2.1, but mapping to the specific node LSN2 at 10.0.2.12.
It does seem a little odd that all these devices are at least initiating to the cluster IP, then getting assigned to specific NODE addresses. Hope someone can put a second pair of eyes on this to help.
Thank you in advance,
Todd
Solved! Go to Solution.
1 REPLY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-31-2011 11:31 AM
03-31-2011 11:31 AM
Solution
The cluster IP is the IP of the cluster and "floats".
The actual endpoint is a physical node so the initiator will show as being connected to a given node(s) for a given LUN.
That's how I understand it anyway - if you look in the CMC at the iSCSI sessions you'll see exactly which nodes each initiator is connected to.
Sorry if I've misunderstood the question.
The actual endpoint is a physical node so the initiator will show as being connected to a given node(s) for a given LUN.
That's how I understand it anyway - if you look in the CMC at the iSCSI sessions you'll see exactly which nodes each initiator is connected to.
Sorry if I've misunderstood the question.
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP