Which fiber optic cable?

[Psittac]

I'm setting up a 10G connection between two of my servers and have Brocade 1020(B) dual port's on each with Brocade XBR-000180 transceiver's installed, can someone tell me what fiber optic cable this uses?  I don't know the first thing about terminology and don't want to just buy one that looks like it'll fit from the pic's.  I also can't make sense of any googling that I do because I don't know the keywords I'm looking for.  Any help is appreciated, Thanks.

 

*edit: here is the exact ebay listing for the transceivers

https://www.ebay.com/itm/153356536793

 

I can also take pictures of the actual transceivers if that'll help

 

[Windows7ge]

What you need is a LC to LC OM3 or OM4 fiber cable. Something like the following for example: https://www.fs.com/products/40254.html

 

There's many different types of fiber cable with many different specifications but for a home P2P setup this should get it done.

[Psittac]

8 minutes ago, Windows7ge said:

What you need is a LC to LC OM3 or OM4 fiber cable. Something like the following for example: https://www.fs.com/products/40254.html

 

There's many different types of fiber cable with many different specifications but for a home P2P setup this should get it done.

Awesome tyvm!!!!

[Windows7ge]

7 minutes ago, Psittac said:

Awesome tyvm!!!!

yw

 

If you don't mind me asking have you worked with 10Gbit before or would this be your first time? Sometimes depending on accompanying hardware/software some extra configuration is required.

[Psittac]

1 minute ago, Windows7ge said:

yw

 

If you don't mind me asking have you worked with 10Gbit before or would this be your first time? Sometimes depending on accompanying hardware/software some extra configuration is required.

I've never worked with it before, I'm getting all of my information from a friend who has done all of it but I can only bother him so much.

 

My only goal is to be able to share files from one server to the other for Plex, one of them has more processing power than the other.  The R710 has dual cpu's that are each more powerful than the one cpu on the R510

 

If you have any advice I'd greatly appreciate it

[Windows7ge]

2 minutes ago, Psittac said:

I've never worked with it before, I'm getting all of my information from a friend who has done all of it but I can only bother him so much.

 

My only goal is to be able to share files from one server to the other for Plex, one of them has more processing power than the other.  The R710 has dual cpu's that are each more powerful than the one cpu on the R510

 

If you have any advice I'd greatly appreciate it

Before I can list suggestions what OS are each of these machines running/going to run?

[Psittac]

5 minutes ago, Windows7ge said:

Before I can list suggestions what OS are each of these machines running/going to run?

Both are Windows Server 2012 R2

[Windows7ge]

58 minutes ago, Psittac said:

Both are Windows Server 2012 R2

Provided Windows recognizes the NIC most of this should be plug'n'play. Being a server distro of Windows Windows may not automatically assign the NICs IP addresses (169.254.X.X/16) once they both report the link state as up.

 

Personally when configuring IP addresses for peer-to-peer connections I like to use:

NIC1: 10.0.0.1/30

NIC2: 10.0.0.2/30

 

There's no point in using a larger subnet when you can only have two clients.

 

What you will have to experiment and test with is the speed of the connection. If you have a SSD on both servers or a large pool of drives this will be worthwhile. Depending on your hardware/drivers you may see a considerable performance bump on the network by enabling Jumbo Packets. Your NIC should have a MTU (Maximum Transmission Unit) value by which increasing will make each network packet carry a larger payload. With slower processors this can help when you want a single client to saturate the link.

 

Working with Windows to Windows you would set the MTU to 9014

Working with Linux to Linux you would set the MTU to 8972

Working with Windows to Linux you would set each to their above mentioned values.

 

To test if Jumbo Packets are working you would want to run the following where x is the IP of the opposing machine:

ping 10.0.0.x -f -l 8972

If you receive the error:

Packet needs to be fragmented but DF set

Then Jumbo Packets is not enabled. If you receive replies then it's working. You can try file transfers with it enabled & disabled. If there's a improvement leave it enabled. If not you can disable it again.

[Psittac]

7 minutes ago, Windows7ge said:

Provided Windows recognizes the NIC most of this should be plug'n'play. Being a server distro of Windows Windows may not automatically assign the NICs IP addresses (169.254.X.X/16) once they both report the link state as up.

 

Personally when configuring IP addresses for peer-to-peer connections I like to use:

NIC1: 10.0.0.1/30

NIC2: 10.0.0.2/30

 

There's no point in using a larger subnet when you can only have two clients.

 

What you will have to experiment and test with is the speed of the connection. If you have a SSD on both servers or a large pool of drives this will be worthwhile. Depending on your hardware/drivers you may see a considerable performance bump on the network by enabling Jumbo Packets. Your NIC should have a MTU (Maximum Transmission Unit) value by which increasing will make each network packet carry a larger payload. With slower processors this can help when you want a single client to saturate the link.

 

Working with Windows to Windows you would set the MTU to 9014

Working with Linux to Linux you would set the MTU to 8972

Working with Windows to Linux you would set each to their above mentioned values.

 

To test if Jumbo Packets are working you would want to run the following where x is the IP of the opposing machine:

ping 10.0.0.x -f -l 8972

If you receive the error:

Packet needs to be fragmented but DF set

Then Jumbo Packets is not enabled. If you receive replies then it's working. You can try file transfers with it enabled & disabled. If there's a improvement leave it enabled. If not you can disable it again.

Awesome! Thank you very much, I will put that to use when the time comes