Create Bond for management
-
@jbamford said in Create Bond for management:
@OskarNTT you select the both which will automatically assign it to management just like in XCP-ng Center. I’ve done it like this on 3 nodes in a cluster.
Exactly, when selecting both eth0 and eth1 the mgmt interface will be moved ontop of the bond0 as an untagged vlan.
In your switch, just configure the native vlanid of your mgmt network to that lacp interface and you're good to go. -
@nikade correct. But I strongly recommend putting Management in a management VLAN. Do away with Native VLANs. Bond0 should never have a IP on it. Build Bond0 then VLANs on top I.e MGMT VLAN, Servers that are going to be exposed in an isolated VLAN. It is good practice to not use Native VLAN 1 and working in a Data Center like myself VLAN everything.
-
@jbamford said in Create Bond for management:
@nikade correct. But I strongly recommend putting Management in a management VLAN. Do away with Native VLANs. Bond0 should never have a IP on it. Build Bond0 then VLANs on top I.e MGMT VLAN, Servers that are going to be exposed in an isolated VLAN. It is good practice to not use Native VLAN 1 and working in a Data Center like myself VLAN everything.
Im not talking about using VLAN 1, you can change the native vlan-id on the interface to your management vlan.
Also, if you dont have a dedicated nic for management you'll need to put it on the bond0 and that means bond0 having an ip on it, we've done this for about 10 years without any issues so im not really sure why you are against it.For example, our management vlan is vlan-id 99 and our server has 2 NIC's.
We then create a lacp bond on eth0 and eth1 and the mgmt interface is automatically moved from the default eth0 to bond0.
We then go to the switch and we configure the native vlan-id on the lacp interface to vlan-id 99. -
@nikade that is wrong. Bond0 never has a IP. It is one of the weaknesses with TCP-IP and 802.3ad. When I did my CCNA/CCNP it was well documented.
-
@jbamford said in Create Bond for management:
@nikade that is wrong. Bond0 never has a IP. It is one of the weaknesses with TCP-IP and 802.3ad. When I did my CCNA/CCNP it was well documented.
I don't think you are correct, this is how it looks on all 18 of our XCP-NG's with management on top of the lacp/bonded interfaces:
But anyway, end of discussion, you've been presented with a solution that works, if you don't want to use it that's your decision.
-
@nikade no management VLAN looks a mess. Don’t moan when you get compromised and you wonder why data breaches happen
-
Have the same problem.
We use LACP fallback in the switch so if the ports in the LACP not receive LACP one port goes into standard mode/non LACP. That's what is active now.Trying to create a bond with the eth0 (currently used to manage) and eth1 but can't select bond mode.
Have also in the switch enabled native vlan that is the manage vlan.
-
Weird
@MathieuRA any reason for bond mode to be empty? -
What happends if you just try choosing eth0 and paste the output view and then do the same with eth1?
Atleast we can narrow it down to which interface it is causing the inoperability. -
@nikade
It is solved.
Reinstalled the nodes since the setup is not in production yet.
Bond worked fine and the switch ports went from LACP fall back into LACP active/active.
-
@Chr57 Good job, always nice to have everything sorted out before going live
-
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
