NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port-Channel / MLAG Configuration for Ubuntu-Server on two M4500 switches
Hi folks,
we need some assistance to setting up a port channel for an Ubuntu server on two Netgear M4500 switches, which we have already connected to each other and configured as MLAG (peer link). Now we would like to operate an Ubuntu server with two network interfaces as a bond and distribute it to the individual switches with one connection each. We have already set up a bond on the Ubuntu server (LACP -> 802.3ad). Bond configuration on our Ubuntu Server as follows:
-------------- /etc/netplan/01-netcfg.yaml --------------
network:
ethernets:
eno12399np0:
dhcp4: false
dhcp6: false
eno12409np1:
dhcp4: false
dhcp6: false
bonds:
bond0:
addresses: [10.0.0.30/24]
routes:
- to: default
via: 10.0.0.1
metric: 100
nameservers:
addresses: [10.0.0.10]
search: [my.domain]
interfaces:
- eno12399np0
- eno12409np1
parameters:
mode: 802.3ad
mii-monitor-interval: 100
version: 2
----------------------------------------------------------
If we now set up a port channel on the switches and define it as MLAG, then I can no longer get a connection to the Ubuntu server. If we remove the MLAG configuration entry, than we get the connection back. Can anyone help us to set up an MLAG for an Ubuntu server. What basic steps are necessary to create a port-channel (multi chassis Link Aggregation Group) for a server in LACP mode. At this time only one network adapter is connected to one of the switches. The Connection to the Ubuntu-Server does not operate as Trunk-Port and no VLAN information needed to be transfered. It is necessary create the similar port-channel on both switches? If someone need further information, please ask.
best regards
mr.bit
Hi schumaku,
thank you for your post. The problem could be solved with the support of Netgear L3 Support. The MLAG and the peer link between both switches were correctly configured and operative. There was a faulty line in the configuration of the port channel and misunderstanding of the VLAN-Tagging behaviour (switchport acceptable-frame-types untagged, switchport tagging 1, removing switchport tagging 1 gets server back responding again). Additional on the bond configuration we configured the "lacp-rate: fast" option to recognize faster link failures.
regards
mr.Bit
2 Replies
Personally, I'm still more than confused about the feature set supported on the M4500 - MLAG -looks- to me like stacking (clustering or the like), however on an older thread this was discussed there was no common "agreement" (if not even @msi knows....)
LaurentMa please, or contact the Netgear ProAV Design Team.
Hi schumaku,
thank you for your post. The problem could be solved with the support of Netgear L3 Support. The MLAG and the peer link between both switches were correctly configured and operative. There was a faulty line in the configuration of the port channel and misunderstanding of the VLAN-Tagging behaviour (switchport acceptable-frame-types untagged, switchport tagging 1, removing switchport tagging 1 gets server back responding again). Additional on the bond configuration we configured the "lacp-rate: fast" option to recognize faster link failures.
regards
mr.Bit
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
