- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Re: UCS iSCSI boot dual subnets
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
тАО06-11-2014 01:42 AM
тАО06-11-2014 01:42 AM
Hi All,
we have setup a UCS with Nimble CS220G & connecting via the appliance ports. We have set it up as per the guides on this forum & so far we are able to iSCSI boot ESXi from a Nimble volume. Few things we are not clear on are:
1) when a blade boots into ESXi & just after the console logon screen appear, we see two connection initiators from UCS (one from each fabric) in the Nimble GUI, but then a few seconds later the connection initiator from fabric b disappears in the Nimble GUI & it does not re-appear until we go through a reboot again. should that be happening? i would expect to see both initiators from UCS fabric A & B. is that correct?
2) Within ESXi, we see the iSciBootvSwitch is created with one vNic & the IP info for the initiator from fabric A.
3) possibly a stupid question, but under storage adapters > isci adaptors, should we be seeing both initiators from UCS? currently we only see the one from fabric A.
4) Do we need to install anything on the ESXi side?
Any help on this would be appreciated.
We are running the following:
Nimble OS 2.0.8 with Virtual IP's
UCSM 2.2
Dual subnets
Thanks
Kassim
Solved! Go to Solution.
- Tags:
- dual-subnet
- ESXi
- iSCSI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2014 01:22 AM
тАО06-20-2014 01:22 AM
Re: UCS iSCSI boot dual subnets
now resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-23-2014 09:44 AM
тАО06-23-2014 09:44 AM
Re: UCS iSCSI boot dual subnets
I have a similar problem, could you describe how you resolved it for those of us that find your posting later?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2014 04:30 AM
тАО06-24-2014 04:30 AM
SolutionHi Brian,
not sure if i should have put down resolved but we have it working as follows:
1) we only still see one initiator in Nimble pointing the initiator name from fabric A.
2) in the iSciBootvSwitch, we added another port group & added the vNic & IP info for initiator from fabric B
3) we are still seeing only the one initiator from fabric A, but we are "guessing" that could just be a pointer label, as we tested this theory by removing access for that initiator in Nimble & it did not drop the connection. we still have further tests to carry out.
i logged a case with VMware about this & they sent me the following kb link
http://kb.vmware.com/kb/2038869
as initially we created a new vswitch to add the vNic for the initiator from fabric B & when we try to bind it to the iSCSI adapter, it showed as not in use. linked to point 2 above.
4) we installed the Nimble PSP package on each ESXi host.
dont know if this helps, but i can try & help if you have any further questions.