I have CCR1009 running fine with DSL modem (DSL internet as backup) via FO link. Here is my setup:
- CCR1009 - SFP+ port equipped with S-35LC20D
- Patchcord FO: LC/LC SM 35m
- cheap sfp media converter with 10/100/1000M link at copper side - model: MC220S, name: "10/100/1000M SFP Ethernet Converter" (cheap "black box with 6 leds, sfp socket and copper ethernet port" - I believe it's clone of tplink MC220) in SFP port: S53LC20D
- Modem: ADSL modem from my telephone company ("NetiaSpot" cra*, but at least can be switched to modem mode)
This setup work very good.
I got recently RBFTC11, so I wanted to replace the cheap MC220 with something better (and wall-mounted - that's the primary reason of replacing something that work ok ) , but....
I moved the SFP module from MC220 to RBFTC11 , connected to modem (via PoE injector) and FO cable... and in winbox I got "no link" status, so I started to play with rate and eventually I got "link ok" at 100M (that's seems ok because the modem have 100M port only), I can see in port traffic tab that CCR is sending something but I don't see any replies from modem, so: I have traffic from router to modem but nothing back (from modem to router).
Here is dump of my settings from CCR (with RBFTC11):
Code: Select all
[admin@MT-ROUTER] /interface ethernet> monitor 1
name: WAN2-DSL-SFP+
status: link-ok
auto-negotiation: disabled
rate: 100Mbps
full-duplex: yes
tx-flow-control: yes
rx-flow-control: yes
sfp-module-present: yes
sfp-rx-lose: no
sfp-tx-fault: no
sfp-type: SFP-or-SFP+
sfp-connector-type: LC
sfp-link-length-9um: 20000m
sfp-vendor-name: Mikrotik
sfp-vendor-part-number: S-35LC20D
sfp-vendor-serial: S1T35252500610
sfp-manufacturing-date: 15-07-01
sfp-wavelength: 1310nm
sfp-temperature: 64C
sfp-supply-voltage: 3.264V
sfp-tx-bias-current: 29mA
sfp-tx-power: -6.176dBm
sfp-rx-power: -7.381dBm
eeprom: 0000: 03 04 07 00 00 00 40 00 00 00 00 03 0d 00 14 c8 ......@. ........
0010: 00 00 00 00 4d 69 6b 72 6f 74 69 6b 20 20 20 20 ....Mikr otik
0020: 20 20 20 20 00 00 00 00 53 2d 33 35 4c 43 32 30 .... S-35LC20
0030: 44 20 20 20 20 20 20 20 00 00 00 00 05 1e 00 a4 D ........
0040: 00 1a 00 00 53 31 54 33 35 32 35 32 35 30 30 36 ....S1T3 52525006
0050: 31 30 20 20 31 35 30 37 30 31 20 20 68 b0 01 e6 10 1507 01 h...
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0080: 64 00 d8 00 5f 00 dd 00 8c a0 75 30 88 b8 79 18 d..._... ..u0..y.
0090: c3 50 00 fa b9 8c 01 f4 1f 07 03 1a 18 a5 03 e8 .P...... ........
00a0: 1f 07 00 0c 18 a5 00 10 00 00 00 00 00 00 00 00 ........ ........
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00c0: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00 ....?... ........
00d0: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 0e ........ ........
00e0: 40 80 7f 80 3a 34 09 6c 09 8e 00 00 00 00 00 00 @...:4.l ........
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
Code: Select all
[admin@MT-ROUTER] /interface ethernet> monitor 1
name: WAN2-DSL-SFP+
status: link-ok
auto-negotiation: disabled
rate: 1Gbps
full-duplex: yes
tx-flow-control: yes
rx-flow-control: yes
sfp-module-present: yes
sfp-rx-lose: no
sfp-tx-fault: no
sfp-type: SFP-or-SFP+
sfp-connector-type: LC
sfp-link-length-9um: 20000m
sfp-vendor-name: Mikrotik
sfp-vendor-part-number: S-35LC20D
sfp-vendor-serial: S1T35252500610
sfp-manufacturing-date: 15-07-01
sfp-wavelength: 1310nm
sfp-temperature: 64C
sfp-supply-voltage: 3.264V
sfp-tx-bias-current: 29mA
sfp-tx-power: -6.196dBm
sfp-rx-power: -7.266dBm
eeprom: 0000: 03 04 07 00 00 00 40 00 00 00 00 03 0d 00 14 c8 ......@. ........
0010: 00 00 00 00 4d 69 6b 72 6f 74 69 6b 20 20 20 20 ....Mikr otik
0020: 20 20 20 20 00 00 00 00 53 2d 33 35 4c 43 32 30 .... S-35LC20
0030: 44 20 20 20 20 20 20 20 00 00 00 00 05 1e 00 a4 D ........
0040: 00 1a 00 00 53 31 54 33 35 32 35 32 35 30 30 36 ....S1T3 52525006
0050: 31 30 20 20 31 35 30 37 30 31 20 20 68 b0 01 e6 10 1507 01 h...
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0080: 64 00 d8 00 5f 00 dd 00 8c a0 75 30 88 b8 79 18 d..._... ..u0..y.
0090: c3 50 00 fa b9 8c 01 f4 1f 07 03 1a 18 a5 03 e8 .P...... ........
00a0: 1f 07 00 0c 18 a5 00 10 00 00 00 00 00 00 00 00 ........ ........
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00c0: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00 ....?... ........
00d0: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 0e ........ ........
00e0: 40 e0 7f 80 39 d0 09 61 09 d0 00 00 00 00 00 00 @...9..a ........
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
I did tested other PoE injectors too - no change. ETH port led (on RBFTC11) is lit on/blink (green) - but that's all. The moment I swap for MC220S the comm kick in (Rx packet show up on graph).
I did read when I was researching the connection of DSL modem over FO link and I read that there might be MCs (media converters) that don't want work well in that kind of link. - Is this case?
Ps. Info for those wondering why the FO link to dsl modem: I have a main server rack "galvanic separated" from rest of network(s), only one copper cable is main power but this one is protected by few voltage surge protectors in fuse box.
In attachments is photo of MC220S.