I have a internet fiber connection and am using FS GE-BX (#20140) modules 10 and 20 km. Worked perfectly in the hEX-s but not in the 4011. I get all the normal information in the SFP screen and a link OK.
When running Torch I see my PPPoE-discovery being transmitted but there seems to be no answer. The same cable and module in the hEX-s and I have a instant connection.
The wavelength of the modules is transmits 1310/1550nm and looking in a other forum they recommend 1310/1490nm for the 4011. I am puzzled that the module is working but in the 4011 it won’t receive information. I am on 6.47 beta 60 and I could try with at stable version if it works there.
Anyone having a tip how to get this running before I go to buy the ones 131/1490nm?
From the datasheet of the module: 1260 1310 1360nm / 1530 1550 1600nm
From the other module advised: 1260 1310 1360 / 1440 1490 1540nm
I’d assume you have to talk to the ISP first - normally, you cannot change the light color just like that. It works with 1550 nm in hEX, so there is no reason why it should not work in 4011 for the wavelength reason. I.e. it is theoretically possible that the 4011 has some issues with the 1310/1550 nm module, but replacing it by a 1310/1490 nm one would most likely mean very weak or no signal, i.e. you’d fix one issue and create another one.
What are the Rx levels indicated on the hEX and on the 4011?
I will check that tomorrow because I have already placed back the NTU on the fiber to have Internet. I also going to try a direct link between the hEX-s and the 4011 to see if that works. Got plenty of modules and a fiber cable for that.
For this local test, you have to pair a 1310/1550 nm one with a 1550nm/1310 nm one, otherwise they won’t understand each other (one must send at the same wavelenght on which the other one receives, and the different wavelength per direction is used to allow single-fiber operation in full duplex operation).
I have my 4011 just 25 hours and is really a fast router but also it’s edges. IKEv2 is at 800Mhz just a bit faster then two hEX-S in series. On 1400Mhz I ran out of ISP bandwith, just to browse.
I call the 4011 my ‘little stove’ because it such a darn hot router…and looks like that also.
Got already a hEX GR3, two hEX-S and a hEX GR2 (the forgotten one) and more I can’t set out in the family. Sorry anav, no deal.
RB4011 has SFP+ port (10Gbps) while hEX S has SFP port (1 Gbps). So it might be necessary to manually set port speed to 1Gbps on RB4011 to start communicating with the SFP module.
What you see in SFP status is likely read out of DDC port and that’s out-of-band … so yes, quite likely SFP synchronized with partner at the other end of fibre, it’s just RB4011 that can’t communicate with local SFP module.
So…tested it and it is not the SFP but RouterOS. The latest beta does not enforce 1GB if you set it manually instead of Auto-negotiated. I have not tried previous beta’s and rather wait till Mikrotik fixed this problem.
I tried 6.46.6 and that got a connection but the MTU started at 1500 on the PPPoE connection and then switched back to 1480. On 6.45.8 the MTU stayed on 1500 on the PPPoE connection.
I have looked up the information on the NTU that is being used and that is a Genexis MC901. It can do both speeds 100Mbit and 1000Mbit fiber.
The frequency used is Tx 1310 Rx 1490/1550nm and the dBm is Tx -9 -3 and Rx -3 -23. There are 1G SFP Wideband BiDi LX that have a wider bandwidth 1460-1580nm however that one costs almost four times than of the price of one ‘smallband’ SFP.
My dBm is in the ‘middle’ of that so that is OK. The FTTH that is present only does 1GB.
It doesn’t matter much what are the parameters of the optical/electrical converter you want to substitute by your SFP, it is important how the remote side behaves. The fact that the Genesis MC901 can receive on both 1490 nm and 1550 nm doesn’t tell you on which of these wavelengths the remote equipment actually transmits in your particular case. The fact that a Tx 1310/Rx 1550 SFP works fine in the hEX S tells you that either the remote equipment transmits on 1550 nm, or the SFP’s receiver is actually a wideband one and doesn’t care about the received wavelength much, which is also possible - before DWDM came into use, 1310 nm and 1550 nm were used to refer to the whole band, not to a particular wavelength within that band, and it’s still the case outside the DWDM domain.
And your way of handling special symbols twists my eyes 1310-1490/1550 normally means “from 1310 through to 1490 in one direction, 1550 in the opposite one”. Plus, although it is a common habit to indicate the sending wavelength (or frequency) first and the receiving one second, it is always better to state that explicitly like I did above.
It is not a big deal to create a wideband optical receiver (in fact, a wideband one is simpler than a selective one), but to create an SFP which can transmit on a chosen wavelength currently means to include one transmitter per wavelength to it and use one of them at a time; maybe that will change in future.
I have adapted my “way of handling symbols” so you can untwist your eyes again see straight as an arrow.
That the FTTH POP is wideband I expected and the forums never agree on which to use 1490nm or 1550nm, it works both. I have to order the Tx1550/Rx1310nm SFP and some armored cabling so I will also trow a 1490 in there also. Takes a month to arrive.
I got an answer from Mikrotik support that is fixed in a next version(s) of RouterOS.
Now I have changed the setup of the different devices so that I don’t have to take half of them of the wall to just put an other device on the fiber connector. I had extra fiber cables and adapters for and made the following connections:
1310-1490/1550 normally means “from 1310 through to 1490 in one direction, 1550 in the opposite one”. Plus, although it is a common habit to indicate the sending wavelength (or frequency) first and the receiving one second, it is always better to state that explicitly like I did above.