CCR at the CORE - Best Design for Performance

Hi All,

Looking for guide on making sure I get the best performance out of the CCR’s as I plan to install them in our core infrastructure.

The structure is

[SUPPLIER1]         [SUPPLIER2]  [SUPPLIER1]   [SUPPLIER2]
         \                  /                    \                  /
          \                /                      \                /
            [SWITCH1]                       [SWITCH2]
                          \                               /
                           \                             /
                            \                           /
                          [MIKROTIK CCR-1036-8G-2S]

So both suppliers give dual ethernet feed, one feed to each switch in my rack.

Then both switches link back to the CCR. They actually link back via 2 ethernets using LACP bonding, so the CCR has 2x bonding interfaces

Supplier 1 is VLAN200, supplier 2 is VLAN300.

I have created VLAN200 and VLAN300 under both bonding interfaces.

Is it best now to create a bridge interface and bridge the 2x VLAN interfaces together?

These connections will be doing 200-400mbps each. How much of a performance hit would there be in adding the bridge?

The 2nd switch and 2nd bonding is merely for redundancy, rather than load balancing, and was expecting STP to take care of the switching, but I am afraid of pushing the packets to the cpu for processing too many times and limiting the performance on the CCR.

Is bridging the VLAN’s the best way, and having 2 different bridges?

Or should I bridge the 2x bonding interfaces and create VLAN’s under the 1 bridge?

Thanks.

EDIT: text has gone a bit wonky for the network map but should still be followable.

i created same vlan on each bond - then created bridge and add both vlan's to bridge.

do not ask me if this is the correct way - intervlan routing currently tops @ 240Mbit/s not sure why?

\

jul/22/2014 00:02:35 by RouterOS 6.17

/interface bridge
add comment=CORE l2mtu=1590 name=bridgeVLAN10 priority=0x1
add comment=MGMT name=bridgeVLAN99 priority=0x2


/interface bonding
add mode=802.3ad name=bonding-C3750-0 slaves=ether3,ether4 transmit-hash-policy=layer-2-and-3
add mode=802.3ad name=bonding-sg200-0 slaves=ether5,ether6 transmit-hash-policy=layer-2-and-3

/interface vlan
add interface=bonding-C3750-0 name=vlan10-c3750 vlan-id=10
add interface=bonding-sg200-0 name=vlan10-sg200 vlan-id=10
add interface=bonding-C3750-0 name=vlan99-c3750 vlan-id=99
add interface=bonding-sg200-0 name=vlan99-sg200 vlan-id=99

/interface bridge port
add bridge=bridgeVLAN99 interface=vlan99-c3750
add bridge=bridgeVLAN99 interface=vlan99-sg200
add bridge=bridgeVLAN10 interface=vlan10-c3750
add bridge=bridgeVLAN10 interface=vlan10-sg200

/ip address
add address=192.168.1.254/19 interface=bridgeVLAN10 network=192.168.0.0
add address=10.254.1.1/16 interface=bridgeVLAN99 network=10.254.0.0

I would consider to avoid vlan trunking on the ccr as it saves some cpu cycles. You have a switch in front let the HW do the job.