Infiniband Connection to ESXi 5.0 Server

Hi, I have an ESXi 5.0 host with a mix of Server 2008R2 and 2012 Servers guests.  I am trying to connect a second physical Server 2012 machine to this host via Infiniband so that I'll have a fast link to the host for backup purposes.  This is a direct connection - I don't have an infiniband switch; just two cards and a cable.  OpenSM is running on the standalone Server 2012 machine.

Ideally, I would like to set the Mellanox as pci-pass-through to one of the VM's; especially a Server 2012 VM so that I can take advantage of the new SMB 3.0 functionality.  However, I have not been able to do this as the Server 2012 VM will crash whenever I add the card to its configuration.  Interesting however, that in this paper, it appears that pci passthrough is possible:  http://labs.vmware.com/publications/ib-researchnote-apr2012  But after some googling, others are having the same reboot problem I have.

Therefore, my second alternative is not to pass-through, but to setup the card as IPoIB at the ESXi host level.  I've done this and at this point, I can ping between a VM and the standalone Server 2012 Server.  On the guest VM, I have two vNIC's, a "regular" one with internet access which has an IP of 192.168.1.2/255.255.255.0.  The second vNIC is on the "infiniband" network which is set to 192.168.2.1/255.255.255.0 - there is no default gateway set on this second vNIC.

On the standalone server, the setup is similar - 192.168.1.3 for "regular" and 192.168.2.2 for the infiniband card.  On this server, I removed Windows File and Printer sharing on the regular NIC, but kept it checked on the Infiniband NIC with the hope that this will "channel" all the file sharing / copying packets via the fast infiniband connection (not sure if this is the best way to do it, but the only way I thought of).

My problem at this point is that while I can ping from each machine to the other via the Infiniband connection (eg ping 192.168.2.1 and ping 192.168.2.2), this connection is showing up as "public and unidentified" by Windows on both the VM guest and the standalone server.  As such, I can't see the shared folders I have set up and without that, I can't copy the files to be backed up to the standalone 2012 Server.

Any thoughts either to solve the public and unidentified network problem or is there a better way to accomplish what I an trying to do.  

If there is a way to pass through the Infiniband card, that would be best, but I can live with an alternative.  The cards I have are MHQH19B-XTR and both have been updated with the latest firmware from the Mellanox website.

Thank you!
Hammer8Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Hammer8Connect With a Mentor Author Commented:
Hi, just to update readers.  I was able to solve my problem by creating a new VM Group under my existing vSwitch with just the Infiniband NIC and called it VM Network - IB.  Then in each VM that I would like access to the external server via Infiniband, I added a new vNIC and set that as belonging to the new VM Group.  This method avoids having to use a new subnet and I'm able to use 192.168.1.x on all NIC's including the Infiniband NIC on the standalone server.

The downside is I don't have internet access on the standalone server...

I was not able to figure a way to do hardware passthrough...
0
 
IanThCommented:
see

http://social.technet.microsoft.com/Forums/en-US/winserver8setup/thread/ac1de5fe-335a-46bc-8fc2-45a96397f937

infiniband does your host see the infiniband in the pass-though config as a device
0
 
Hammer8Author Commented:
Yes, my hose sees the infiniband adapter as a passthrough device and I can add it as a PCI device to my Server 2012 guest VM, but when I go to start the VM, it crashes during start up.

I was able to set the network to private using mmc - basically change unidentified networks to be private instead of public.  But it still does not share properly - to share properly, I had to disable the non infiniband vNic (eg, the 192.168.1.2 adapter) and now, I can connect to 192.168.2.2 and see the shares on that server.  However, that defeats the purpose of this as I need the our regular clients on 192.168.1.x to see that server in order to access the files on it - the same files I want to backup via infiniband to 192.168.2.2!
0
 
Hammer8Author Commented:
Did not see an acceptable solution.
0
All Courses

From novice to tech pro — start learning today.