I did a write up on this too because I found little to no info. I am happy that you posted this video. It would have helped me out a lot!
Not to hi-jack your thread, but here is my info as well.
I used fiber optic connections because I found the NICs to be cheaper. Copper works just as good.
Equipment (all retired enterprise equipment from ebay):
Cache Drives - 2x Kingston 240gb SSDs in raid 0
Unraid Nic -HP Dual Port 10Gb Ethernet PCIe Card for Proliant 468349-001 ($38.00)
Client Nics -HP 10GB MELLANOX CONNECTX-2 PCIe 10GBe ETHERNET NIC671798-001 ($12.00)
Trancievers - 4xHPE BladeSystem 455883-B21 Compatible 10GBASE-SR SFP+ 850nm 300m DOM Transceiver ($20.00)
Cables -LC UPC to LC UPC Duplex 2.0mm PVC(OFNR) OM3 Multimode Fiber Optic Patch Cable ($6.00)
FYI - for the next person looking to do this here is the process.
If you are not able to completely saturate the 10gbe connection, it is likely because the hard drive at one of the ends is too slow. this is why my cache is 2x SSDs in raid 0. Another cause could be that the share you are using it not set to use the SSD cache.
Windows 10:
1.install the 10gb NIC and give it a static IPaddress in a different subnet (if your other NIC's IP is 192.168.0.6 - change the value of the 3rd octet to anyunusednumber 1-254, such as 192.168.66.6)
2.turn on network discovery(without this your computer will not respond to pings or any other kinds of remote requests). Simply open a windows explorer window and click the "network option". it will attempt to find computers and devices on your network, if network discovery has not been enabled you will be prompted to do so.
3. Your done for now, but you will need to force windows to use the 10gb NIC for connections to unraid (keep reading)
Unraid:
1.install your 10gb NICand make sure you can see it in the "system info". Make note of the "eth#" shown
2. go to "settings > network settings" and scroll down to the "eth#" from the previous step. If it is in a "bond group", the array must be stopped and the "eth#" removed.
3.assign the "eth#" a static IP address.this address must be in the same subnet/netmask as your windows PC (in other words, 192.168.66.* - see windows sample from above).
4. hit apply
5. use Putty or something similar to connect to your unraid server. Ping the windows PC's 10gb NIC using it's address (our sample is 192.168.66.6). Because you have multiiple NIC's you must specify what NIC to use for ping.
ping -I eth# 192.168.66.6 (the -i switch allows you to ping using a spcific NIC. replace the # with your NIC id).
if the windows 10 computer responds all is well. Go back to windows to complete the configuration.
if the windows 10 computer does not respond, you missed one of the above steps or have some other issue.
Back to Win 10 Again (rhymes right?)
There are 2 ways to force windows to use the 10gb connection. For the purposes of documentation (keeping all info in 1 place) I have both listed, but in no way would I ever recommend using method 2.
Method 1: add unraid server to your "host" file
go to "C:\Windows\System32\drivers\etc" and open the "hosts" file with notepad
scroll all the way to the bottom and on a blank line enter the unraid servers 10gb NIC address followed by a space then an alias (I like to use the Hostname)
192.168.66.6 Hostname
now save the file and attempt to ping "Hostname". You should find that "Hostname" now resolves to the IP address you have specified in the "host" file.
If you ever have need to access the unraid server from this PC but do NOT want to use the 10gb NIC you can simply enter another line in your "host" file.
192.168.66.6 Hostname-10g
192.168.0.6 Hostname
line 1: will resolve the alias "Hostname-10g" to the servers 10gb NIC address
line 2: will resolve the alias "Hostname" to the servers 1gb NIC address
Method 2: NOT RECOMMENDED
Windows 10 now has more than 1 NIC that can connect to the unraid server. How will it know what one to use?
You would normally go in and change the NIC priority, but this is no good in windows 10. Change the settings all you want and they will just revert back. You are expected to manually change the "metric" (although it's not well documented).
go to the "network connections" in the control panel and select the properties of the 10gb connection.
now select the IPv4 option in the "networking" tab, then select the "advanced" button in the new window.
You should now see the "advanced TCP/IP settings" window. At the bottom of this window uncheck the "automatic metric" button and set a value.
keep in mind that lower numbers have a lower priority. I manually set a value of "10" for the 10gb NIC and "20" for my wireless NIC so the priority for one is higher than the other. This method uses one connection as a "failover" for the other. It will always try the 10gb connection first and use the other if 10gb fails. The problem with this is that it uses 10gb for everything and does so at the expense of giving your other NIC a lower priority.
Sending BIG files to/from Unraid? Configure Jumbo packets (OPTIONAL):
It's basically what it sounds like. You can configure the connection to send larger packets of data at a time. This is more of a feature for those using the 10gb connection exclusively to transfer large files.
for this to work jumbo packets must be configured the same on both ends (unraid and windows).
If using a 10gb switch, the port(s) used to make this connection must be configured to use jumbo packets as well.
Windows 10
Go back to your windows computer and in the 10gb NICs driver properties you should find an option to configure jumbo packets. Simply set the MTU to 9000 and apply your changes.
Unraid
Go to "Settings > Network settings". Scroll down to your 10gb's "eth#" and change the MTU to 9000 and hit apply.
Now Go to "Settings > Global Share Settings -> Tunable" (enable direct IO): set to Yes
Edited by smaka510
