F5F Stay Refreshed Power Users Networks Which type of fiber optic cable?

Which type of fiber optic cable?

Which type of fiber optic cable?

A
Absolute_Zer0z
Junior Member
41
09-21-2021, 02:19 PM
#1
You're looking into setting up a 10G connection using Brocade XBR-000180 transceivers on dual-port fiber optics. The cable type depends on the specific transceiver model and its rated specifications. Since you're unsure about the exact terminology, it's best to confirm the transceiver's datasheet or contact Brocade directly for the recommended fiber size (typically 59/62 OM4 or similar). Taking photos of the transceivers can help clarify their configuration before purchasing. Let me know if you need further guidance!
A
Absolute_Zer0z
09-21-2021, 02:19 PM #1

You're looking into setting up a 10G connection using Brocade XBR-000180 transceivers on dual-port fiber optics. The cable type depends on the specific transceiver model and its rated specifications. Since you're unsure about the exact terminology, it's best to confirm the transceiver's datasheet or contact Brocade directly for the recommended fiber size (typically 59/62 OM4 or similar). Taking photos of the transceivers can help clarify their configuration before purchasing. Let me know if you need further guidance!

D
delaneyandian
Member
180
09-22-2021, 02:48 PM
#2
You require an LC to LC OM3 or OM4 fiber cable. Similar products like the one at the link above can work for your home P2P configuration.
D
delaneyandian
09-22-2021, 02:48 PM #2

You require an LC to LC OM3 or OM4 fiber cable. Similar products like the one at the link above can work for your home P2P configuration.

S
SkyLIKE1
Member
174
09-22-2021, 03:21 PM
#3
Great job!
S
SkyLIKE1
09-22-2021, 03:21 PM #3

Great job!

G
gamer2hokv
Member
198
09-22-2021, 04:30 PM
#4
If you're okay with it, I haven't worked with 10Gbps before, or is this your first experience? Occasionally, certain hardware or software needs additional setup.
G
gamer2hokv
09-22-2021, 04:30 PM #4

If you're okay with it, I haven't worked with 10Gbps before, or is this your first experience? Occasionally, certain hardware or software needs additional setup.

H
Hidekih
Posting Freak
849
09-23-2021, 12:51 PM
#5
I'm new to this setup and only got my data from a friend who did everything, but I'm struggling to reach him. My main aim is to move files between servers for Plex, where one has more processing power than the other. The R710 uses two CPUs that are stronger than the single CPU in the R510. If you have any tips, I'd really value them.
H
Hidekih
09-23-2021, 12:51 PM #5

I'm new to this setup and only got my data from a friend who did everything, but I'm struggling to reach him. My main aim is to move files between servers for Plex, where one has more processing power than the other. The R710 uses two CPUs that are stronger than the single CPU in the R510. If you have any tips, I'd really value them.

M
Max16Def
Member
61
09-23-2021, 01:47 PM
#6
First, identify the operating systems by checking the machine's details or running a diagnostic tool.
M
Max16Def
09-23-2021, 01:47 PM #6

First, identify the operating systems by checking the machine's details or running a diagnostic tool.

D
destructor2_0
Junior Member
2
10-09-2021, 10:43 AM
#7
Both systems run Windows Server 2012 R2
D
destructor2_0
10-09-2021, 10:43 AM #7

Both systems run Windows Server 2012 R2

D
50
10-12-2021, 01:08 AM
#8
Windows seems to handle the NIC setup mostly smoothly, making plug-and-play easier. As a Windows server distribution, IP assignments might not be automatic once both devices report connectivity. For peer-to-peer setups, I prefer: NIC1 at 10.0.0.1/30 and NIC2 at 10.0.0.2/30. Using a bigger subnet isn't necessary when only two clients are involved. You'll need to experiment with connection speeds. If both servers have SSDs or a large drive pool, it can be beneficial. Adjusting Jumbo Packets can improve performance on slower hardware by allowing larger packets. Ensure your NIC supports the MTU size—higher values let each packet carry more data. On slower processors, this helps prevent a single client from overwhelming the link. When switching between Windows and Linux, set MTU accordingly: Windows uses 9014, Linux 8972. Test Jumbo Packets by running ping with -f -l 8972 to your opponent's IP. If you get an error about fragmentation needing to be split but DF is set, jumbo packets aren't enabled. Successful replies confirm it works. Try file transfers with and without jumbo enabled; keep it on if improvements appear.
D
DapperEnderman
10-12-2021, 01:08 AM #8

Windows seems to handle the NIC setup mostly smoothly, making plug-and-play easier. As a Windows server distribution, IP assignments might not be automatic once both devices report connectivity. For peer-to-peer setups, I prefer: NIC1 at 10.0.0.1/30 and NIC2 at 10.0.0.2/30. Using a bigger subnet isn't necessary when only two clients are involved. You'll need to experiment with connection speeds. If both servers have SSDs or a large drive pool, it can be beneficial. Adjusting Jumbo Packets can improve performance on slower hardware by allowing larger packets. Ensure your NIC supports the MTU size—higher values let each packet carry more data. On slower processors, this helps prevent a single client from overwhelming the link. When switching between Windows and Linux, set MTU accordingly: Windows uses 9014, Linux 8972. Test Jumbo Packets by running ping with -f -l 8972 to your opponent's IP. If you get an error about fragmentation needing to be split but DF is set, jumbo packets aren't enabled. Successful replies confirm it works. Try file transfers with and without jumbo enabled; keep it on if improvements appear.

F
FRANDC_BR
Member
162
10-14-2021, 07:16 AM
#9
Great! I appreciate it, and I’ll keep it in mind for when the opportunity arises.
F
FRANDC_BR
10-14-2021, 07:16 AM #9

Great! I appreciate it, and I’ll keep it in mind for when the opportunity arises.