I am connecting a CRS125-24G-1S with 6.20 to a HP procurve 2626 with H.10.74 using two ethernet cables as lacp trunk ports. (basically dual ethernet uplink)
1+2 are the switch trunk going to 21+22 on the HP. Two tagged VLANs go over the switch trunk. Basic everyday datacenter stuff extending vlans to another switch I’ve done for years with the HP gear.
3 is to plug in the device using the vlan assigned to that port.
23 is my cheater management backdoor, but it should be managed over the trunk link in my real world as it will be in a different site, not on the adjacent rack.
24 is my laptop hookup
markom was kind enough to fill in the missing details of how to get a management IP working on a vlan here: http://forum.mikrotik.com/t/add-management-ip-to-crs-switch-how-to-example-not-working/79251/1
[admin@bhtswitch2014] /interface> export
# oct/16/2014 17:25:09 by RouterOS 6.20
# software id = R4V2-R2TF
#
/interface ethernet
set [ find default-name=ether2 ] master-port=ether1
set [ find default-name=ether3 ] master-port=ether1
/interface vlan
add interface=ether1 l2mtu=1584 name=bhtvl vlan-id=43
/interface ethernet switch
set drop-if-invalid-or-src-port-not-member-of-vlan-on-ports=ether1,ether2,ether3,ether4,switch1-cpu forward-unknown-vlan=no
/interface ethernet switch trunk
add member-ports=ether2,ether1 name=dc-link
/interface ethernet switch egress-vlan-tag
add tagged-ports=dc-link,switch1-cpu vlan-id=43
add tagged-ports=dc-link vlan-id=16
/interface ethernet switch egress-vlan-translation
add customer-vlan-format=untagged-or-tagged ports=dc-link service-vlan-format=untagged-or-tagged
/interface ethernet switch ingress-vlan-translation
add customer-vid=0 new-customer-vid=43 ports=ether3 sa-learning=yes
add customer-vid=0 new-customer-vid=16 ports=ether4 sa-learning=yes
/interface ethernet switch port
set 0 dscp-based-qos-dscp-to-dscp-mapping=no
set 1 dscp-based-qos-dscp-to-dscp-mapping=no
set 2 dscp-based-qos-dscp-to-dscp-mapping=no qos-scheme-precedence=\
pcp-based,sa-based,da-based,dscp-based,protocol-based,vlan-based,pcp-based
set 3 dscp-based-qos-dscp-to-dscp-mapping=no
set 4 dscp-based-qos-dscp-to-dscp-mapping=no
set 5 dscp-based-qos-dscp-to-dscp-mapping=no
set 6 dscp-based-qos-dscp-to-dscp-mapping=no
set 7 dscp-based-qos-dscp-to-dscp-mapping=no
set 8 dscp-based-qos-dscp-to-dscp-mapping=no
set 9 dscp-based-qos-dscp-to-dscp-mapping=no
set 10 dscp-based-qos-dscp-to-dscp-mapping=no
set 11 dscp-based-qos-dscp-to-dscp-mapping=no
set 12 dscp-based-qos-dscp-to-dscp-mapping=no
set 13 dscp-based-qos-dscp-to-dscp-mapping=no
set 14 dscp-based-qos-dscp-to-dscp-mapping=no
set 15 dscp-based-qos-dscp-to-dscp-mapping=no
set 16 dscp-based-qos-dscp-to-dscp-mapping=no
set 17 dscp-based-qos-dscp-to-dscp-mapping=no
set 18 dscp-based-qos-dscp-to-dscp-mapping=no
set 19 dscp-based-qos-dscp-to-dscp-mapping=no
set 20 dscp-based-qos-dscp-to-dscp-mapping=no
set 21 dscp-based-qos-dscp-to-dscp-mapping=no
set 22 dscp-based-qos-dscp-to-dscp-mapping=no
set 23 dscp-based-qos-dscp-to-dscp-mapping=no
set 24 dscp-based-qos-dscp-to-dscp-mapping=no
set 25 dscp-based-qos-dscp-to-dscp-mapping=no
/interface ethernet switch vlan
add ports=dc-link,ether3,switch1-cpu vlan-id=43
add ports=dc-link,ether4 vlan-id=16
[admin@bhtswitch2014] /interface>
It almost works. Two problems…
-
I can unplug one ethernet cable of 1+2 and it keeps working. Plug it back in, it drops a few packets and keeps working. Repeat and service over the trunk goes down. It appears the trunk does not come back up for whatever reason. I’m not going to be able to use trunking till this is corrected. Rebooting the CRS fixes it (accessing it via the ether23 or ether24).
-
If I turn OFF an ethernet port on the HP switch feeding the CRS, the lights go out on the CRS but it does not interface log. Trunk ports going down do not log anything based on my observation. Interface logging is enabled:
/system logging
add topics=interface
Any suggestions for this?
