Community discussions

MikroTik App
 
Ifs
just joined
Topic Author
Posts: 4
Joined: Tue Aug 15, 2017 7:30 pm

Crs226 Sfp bonding so that multiple floors can be interconnected

Tue Aug 15, 2017 7:33 pm

I have 6 crs226-24g-2s-rm all on different floors of a building with single mode fiber interconnecting. I am unable to get the second Sfp module to pass any information to the next switch. I am in need of help on how to configure the 2 SFP ports so that I can interconnect all the switches.
 
User avatar
pukkita
Trainer
Trainer
Posts: 3051
Joined: Wed Dec 04, 2013 11:09 am
Location: Spain

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Tue Aug 15, 2017 8:08 pm

You need to make both SFP ports slaves of the master port the switch chip is setup to.

Open a New Terminal, and issue
/export
Pasting the output here.
 
Ifs
just joined
Topic Author
Posts: 4
Joined: Tue Aug 15, 2017 7:30 pm

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Wed Aug 16, 2017 4:49 pm

/interface ethernet
set [ find default-name=ether1 ] name=ether1-master
set [ find default-name=ether2 ] master-port=ether1-master
set [ find default-name=ether3 ] master-port=ether1-master
set [ find default-name=ether4 ] master-port=ether1-master
set [ find default-name=ether5 ] master-port=ether1-master
set [ find default-name=ether6 ] master-port=ether1-master
set [ find default-name=ether7 ] master-port=ether1-master
set [ find default-name=ether8 ] master-port=ether1-master
set [ find default-name=ether9 ] master-port=ether1-master
set [ find default-name=ether10 ] master-port=ether1-master
set [ find default-name=ether11 ] master-port=ether1-master
set [ find default-name=ether12 ] master-port=ether1-master
set [ find default-name=ether13 ] master-port=ether1-master
set [ find default-name=ether14 ] master-port=ether1-master
set [ find default-name=ether15 ] master-port=ether1-master
set [ find default-name=ether16 ] master-port=ether1-master
set [ find default-name=ether17 ] master-port=ether1-master
set [ find default-name=ether18 ] master-port=ether1-master
set [ find default-name=ether19 ] master-port=ether1-master
set [ find default-name=ether20 ] master-port=ether1-master
set [ find default-name=ether21 ] master-port=ether1-master
set [ find default-name=ether22 ] master-port=ether1-master
set [ find default-name=ether23 ] master-port=ether1-master
set [ find default-name=ether24 ] master-port=ether1-master
set [ find default-name=sfp-sfpplus1 ] master-port=ether1-master
set [ find default-name=sfpplus2 ] master-port=ether1-master
/interface ethernet switch port
set 0 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 1 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 2 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 3 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 4 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 5 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 6 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 7 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 8 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 9 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0:\
8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 10 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 11 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 12 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 13 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 14 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 15 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 16 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 17 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 18 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 19 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 20 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 21 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 22 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 23 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 24 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 25 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
set 26 per-queue-scheduling="wrr-group0:1,wrr-group0:2,wrr-group0:4,wrr-group0\
:8,wrr-group0:16,wrr-group0:32,wrr-group0:64,wrr-group0:128"
/ip address
add address=192.168.0.241/24 comment=defconf interface=ether1-master network=\
192.168.0.0
/ip route
add distance=1 gateway=192.168.0.0
/system routerboard settings
set protected-routerboot=disabled
 
Ifs
just joined
Topic Author
Posts: 4
Joined: Tue Aug 15, 2017 7:30 pm

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Wed Aug 16, 2017 5:08 pm

I have the SFP ports configured to be a slave of the master port. Please forgive my ignorance in this.. I am a security integrator not an IT Prof. The switches were specified for a IP based CCTV system and I am attempting to bring online..
 
User avatar
pukkita
Trainer
Trainer
Posts: 3051
Joined: Wed Dec 04, 2013 11:09 am
Location: Spain

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Wed Aug 16, 2017 9:37 pm

Should work as you have it configured, if that same config is on rest of switches.

I assume switches are daisy chained, ie
floor 0 SFP+1 |====| SFP+1 floor 1 SFP+2 |====| SFP+1 floor 3 SFP+2 |====| SFP+1 floor 4
Are you sure SFP modules are linking right? post screenshots of sfp interfaces SFP tab of two interconnected switches.

What have you tested that failed? Is there an external router for these switches? i.e. which device runs DHCP service? I assume cameras will get IPs via DHCP?
 
Ifs
just joined
Topic Author
Posts: 4
Joined: Tue Aug 15, 2017 7:30 pm

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Thu Aug 17, 2017 3:01 pm

Your architecture is correct. The cameras are static. I am able to link sfp1-0 to sfp1-1 but when I connect sfp2-1 to sfp1-3 I do not get a link. Sfp2-1 link light turns on but sfp1-3 does not and am not able to ping the third switch. All switches have the same configuration but with a different ip.
 
User avatar
pukkita
Trainer
Trainer
Posts: 3051
Joined: Wed Dec 04, 2013 11:09 am
Location: Spain

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Fri Aug 18, 2017 11:28 am

Higher OSI layers depend lower ones for everything to work, in your scenario:

Layer 1 - Fiber runs and SFPs linking / running properly
Layer 2 - Proper Switches master/slave ports configuration (fine as per your export)
Layer 3 - Proper IP range assignment

Layer 1
I am able to link sfp1-0 to sfp1-1 but when I connect sfp2-1 to sfp1-3 I do not get a link. Sfp2-1 link light turns on but sfp1-3 does not and am not able to ping the third switch
It's not clear to me still which is connected where, interconnections should be like these:
Captura de pantalla 2017-08-18 a la(s) 11.06.41.png
If a port doesn't link, or doesn't appear as running, problem is physical, either the SFP module or the fiber run has a problem: Layer 1 is broken between switch 2 and 3.

Try:

- Swapping fibers (only at one end of two given switches not linking): put the left fiber strand on the right LC receptacle on the SFP module and the right fiber strand on the SFP left fiber LC receptacle. For fiber runs to link, fibers need to be crossed: Tx-Rx and Rx-Tx.

- Swapping SFP modules for others linking fine on other switches

the point is trying to isolate any misbehaving SFP module/defective fiber run/defective fiber connectors by elimination.

Which SFP modules are you using?

Layer 3:

Additionally, this is wrong:
/ip route
add distance=1 gateway=192.168.0.0
IP cannot be 192.168.0.0, that's the network address of 192.168.0.0/24 address range. It should be the IP of the device acting as internet router, possibly 192.168.0.1.

This is only preventing switches to reach any other address but 192.168.0.0/24 range so hasn't anything to do with SFPs not linking.

Regardless of that, if first switch is 192.168.0.241, and second one is 192.168.0.242, they should be able to ping each other if the SFPs linking them are both running.

As a side note: I would setup DHCP on the main Switch or router and handle IPs to the cameras by DHCP, you can convert the leases to static so that even while cameras get IPs by DHCP, they will always get the same one. The advantage; you control that from a single point, and you'll be able to manage that even remotely w/o the need of connecting to each camera manually.
You do not have the required permissions to view the files attached to this post.
 
User avatar
w177f
newbie
Posts: 27
Joined: Fri Jun 30, 2017 2:21 pm
Location: Dublin, Ire
Contact:

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Sun Aug 20, 2017 8:55 am

What is the make and model of the SFP modules?
The second SFP socket only supports 10G modules.
 
User avatar
acruhl
Member
Member
Posts: 371
Joined: Fri Jul 03, 2015 7:22 pm

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Sun Aug 20, 2017 5:05 pm

Where does this info come from? I might buy one of these. I don't see any indication on the front panel that this is the case, and the documentation says both SFP+ ports support "1.25G or 10G" SFPs... Not disputing what you're saying, I just can't find this information to confirm.
 
User avatar
w177f
newbie
Posts: 27
Joined: Fri Jun 30, 2017 2:21 pm
Location: Dublin, Ire
Contact:

Re: Crs226 Sfp bonding so that multiple floors can be interconnected

Mon Aug 21, 2017 12:04 am

Where does this info come from?
The product description.
It has 24 Gigabit ports and two SFP+ cages for 10G connectivity (first SFP port supports 1.25G/10G modules, second port only 10G modules).
https://mikrotik.com/product/CRS226-24G-2SplusRM

Who is online

Users browsing this forum: karlisi, unhuzpt, vesuviustreamline and 112 guests