You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn’t find any clear instructions online for configuring a high-availability network adapter setup to support cloud infrastructure.
I have 6× 10Gb network adapters per host and would like to configure them as follows:
Host/Compute nodes:
2× Management
2× Tenant traffic
1× iSCSI Port A
1× iSCSI Port B
Management node:
1× Management
I have already set up bonding and bridging on Ubuntu 24.04 hosts. From the Linux perspective the network works correctly (connectivity, pings, etc. all function as expected). However, the cloud agent/management services cannot connect because the management service does not recognise the software bridge interface (mgmtbr).
Does anyone have experience with this kind of setup? Any suggestions or recommended configurations would be greatly appreciated.
publicbr: # Dedicated to Public Internet Access
interfaces: [vlan11-public]
parameters: { stp: false, forward-delay: 0 }
overlaybr: # Dedicated to VXLAN Overlay
interfaces: [vlan31-vxlan]
addresses: ["10.0.31.11/24"] # This is your VTEP IP for VXLAN
parameters: { stp: false, forward-delay: 0 }
`
management-server.log
2026-03-27 14:59:52,146 DEBUG [c.c.a.m.ClusteredAgentAttache] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Seq 5-8892638939219755009: Routed from 345040297085 2026-03-27 14:59:52,146 DEBUG [c.c.a.t.Request] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Seq 5-8892638939219755009: Sending { Cmd , MgmtId: 345040297085, via: 5(node1), Ver: v1, Flags: 100111, [{"com.cloud.agent.api.CheckNetworkCommand":{"networkInfoList":[{"physicalNetworkId":"210","privateNetworkName":"mgmtbr","storageNetworkName":"mgmtbr"},{"physicalNetworkId":"211","publicNetworkName":"publicbr"},{"physicalNetworkId":"212","guestNetworkName":"overlaybr"}],"wait":"0","bypassHostMaintenance":"false"}}] } 2026-03-27 14:59:52,189 DEBUG [c.c.a.t.Request] (AgentManager-Handler-14:[]) (logid:) Seq 5-8892638939219755009: Processing: { Ans: , MgmtId: 345040297085, via: 5, Ver: v1, Flags: 110, [{"com.cloud.agent.api.CheckNetworkAnswer":{"_reconnect":"false","result":"false","details":"Can not find network: mgmtbr","wait":"0","bypassHostMaintenance":"false"}}] } 2026-03-27 14:59:52,189 DEBUG [c.c.a.m.ClusteredAgentAttache] (AgentManager-Handler-14:[]) (logid:) Seq 5-8892638939219755009: No more commands found 2026-03-27 14:59:52,189 DEBUG [c.c.a.t.Request] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Seq 5-8892638939219755009: Received: { Ans: , MgmtId: 345040297085, via: 5(node1), Ver: v1, Flags: 110, { CheckNetworkAnswer } } 2026-03-27 14:59:52,189 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Details from executing class com.cloud.agent.api.CheckNetworkCommand: Can not find network: mgmtbr 2026-03-27 14:59:52,189 WARN [o.a.c.e.o.NetworkOrchestrator] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Unable to setup agent Host {"id":5,"name":"node1","type":"Routing","uuid":"f04d374b-2944-4bbb-ab81-ba09becb42e3"} due to Can not find network: mgmtbr 2026-03-27 14:59:52,190 WARN [c.c.a.AlertManagerImpl] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) alertType=[7] dataCenterId=[4] podId=[3] clusterId=[null] message=[Incorrect Network setup on agent, Reinitialize agent after network names are setup, details : Can not find network: mgmtbr]. 2026-03-27 14:59:52,193 WARN [c.c.a.AlertManagerImpl] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) No recipients set in global setting 'alert.email.addresses', skipping sending alert with subject [Incorrect Network setup on agent, Reinitialize agent after network names are setup, details : Can not find network: mgmtbr] and content [Incorrect Network setup on agent, Reinitialize agent after network names are setup, details : Can not find network: mgmtbr]. 2026-03-27 14:59:52,193 INFO [c.c.u.e.CSExceptionErrorCode] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Could not find exception: com.cloud.exception.ConnectionException in error code list for exceptions
root@node1:~# brctl show
bridge name bridge id STP enabled interfaces
cloud0 8000.4e3408889113 no
mgmtbr 8000.fe091abdf136 yes mgmt-bond
overlaybr 8000.4a880338adc5 no vlan31-vxlan
publicbr 8000.4a880338adc5 no vlan11-public
`
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Dear CloudStack Community Members,
I need help :)
I couldn’t find any clear instructions online for configuring a high-availability network adapter setup to support cloud infrastructure.
I have 6× 10Gb network adapters per host and would like to configure them as follows:
Host/Compute nodes:
2× Management
2× Tenant traffic
1× iSCSI Port A
1× iSCSI Port B
Management node:
1× Management
I have already set up bonding and bridging on Ubuntu 24.04 hosts. From the Linux perspective the network works correctly (connectivity, pings, etc. all function as expected). However, the cloud agent/management services cannot connect because the management service does not recognise the software bridge interface (mgmtbr).
Does anyone have experience with this kind of setup? Any suggestions or recommended configurations would be greatly appreciated.
Netplan
`network:
version: 2
renderer: networkd
ethernets:
ens160: {}
ens161: {}
ens224: {}
ens256: {}
ens193: { addresses: ["192.168.251.11/24"] }
ens225: { addresses: ["192.168.252.11/24"] }
bonds:
mgmt-bond:
interfaces: [ens224, ens160]
parameters:
mode: active-backup
primary: ens224
mii-monitor-interval: 100
overlay-bond:
interfaces: [ens256, ens161]
parameters:
mode: active-backup
mii-monitor-interval: 100
vlans:
vlan11-public:
id: 11
link: overlay-bond
vlan31-vxlan: # New dedicated VLAN for Overlay/VXLAN
id: 31
link: overlay-bond
bridges:
mgmtbr:
interfaces: [mgmt-bond]
addresses: ["10.0.30.11/24"]
nameservers:
addresses:
- 10.0.30.8
search: [poc.local]
routes:
- to: default
via: "10.0.30.1"
metric: 10
parameters: { stp: false, forward-delay: 0 }
`
management-server.log
2026-03-27 14:59:52,146 DEBUG [c.c.a.m.ClusteredAgentAttache] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Seq 5-8892638939219755009: Routed from 345040297085 2026-03-27 14:59:52,146 DEBUG [c.c.a.t.Request] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Seq 5-8892638939219755009: Sending { Cmd , MgmtId: 345040297085, via: 5(node1), Ver: v1, Flags: 100111, [{"com.cloud.agent.api.CheckNetworkCommand":{"networkInfoList":[{"physicalNetworkId":"210","privateNetworkName":"mgmtbr","storageNetworkName":"mgmtbr"},{"physicalNetworkId":"211","publicNetworkName":"publicbr"},{"physicalNetworkId":"212","guestNetworkName":"overlaybr"}],"wait":"0","bypassHostMaintenance":"false"}}] } 2026-03-27 14:59:52,189 DEBUG [c.c.a.t.Request] (AgentManager-Handler-14:[]) (logid:) Seq 5-8892638939219755009: Processing: { Ans: , MgmtId: 345040297085, via: 5, Ver: v1, Flags: 110, [{"com.cloud.agent.api.CheckNetworkAnswer":{"_reconnect":"false","result":"false","details":"Can not find network: mgmtbr","wait":"0","bypassHostMaintenance":"false"}}] } 2026-03-27 14:59:52,189 DEBUG [c.c.a.m.ClusteredAgentAttache] (AgentManager-Handler-14:[]) (logid:) Seq 5-8892638939219755009: No more commands found 2026-03-27 14:59:52,189 DEBUG [c.c.a.t.Request] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Seq 5-8892638939219755009: Received: { Ans: , MgmtId: 345040297085, via: 5(node1), Ver: v1, Flags: 110, { CheckNetworkAnswer } } 2026-03-27 14:59:52,189 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Details from executing class com.cloud.agent.api.CheckNetworkCommand: Can not find network: mgmtbr 2026-03-27 14:59:52,189 WARN [o.a.c.e.o.NetworkOrchestrator] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Unable to setup agent Host {"id":5,"name":"node1","type":"Routing","uuid":"f04d374b-2944-4bbb-ab81-ba09becb42e3"} due to Can not find network: mgmtbr 2026-03-27 14:59:52,190 WARN [c.c.a.AlertManagerImpl] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) alertType=[7] dataCenterId=[4] podId=[3] clusterId=[null] message=[Incorrect Network setup on agent, Reinitialize agent after network names are setup, details : Can not find network: mgmtbr]. 2026-03-27 14:59:52,193 WARN [c.c.a.AlertManagerImpl] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) No recipients set in global setting 'alert.email.addresses', skipping sending alert with subject [Incorrect Network setup on agent, Reinitialize agent after network names are setup, details : Can not find network: mgmtbr] and content [Incorrect Network setup on agent, Reinitialize agent after network names are setup, details : Can not find network: mgmtbr]. 2026-03-27 14:59:52,193 INFO [c.c.u.e.CSExceptionErrorCode] (AgentConnectTaskPool-553:[ctx-996add69]) (logid:1be161e5) Could not find exception: com.cloud.exception.ConnectionException in error code list for exceptions`root@node1:~# virsh nodedev-list --cap net
net_ens160_00_50_56_01_1c_61
net_ens160_ba_27_30_8c_c6_9e
net_ens160_fe_09_1a_bd_f1_36
net_ens161_4a_88_03_38_ad_c5
net_ens193_00_50_56_01_1c_65
net_ens224_00_50_56_01_1c_62
net_ens224_fe_09_1a_bd_f1_36
net_ens225_00_50_56_01_1c_66
net_ens256_4a_88_03_38_ad_c5
net_lo_00_00_00_00_00_00
root@node1:~# brctl show
bridge name bridge id STP enabled interfaces
cloud0 8000.4e3408889113 no
mgmtbr 8000.fe091abdf136 yes mgmt-bond
overlaybr 8000.4a880338adc5 no vlan31-vxlan
publicbr 8000.4a880338adc5 no vlan11-public
`
Kind Regards, Matt
Beta Was this translation helpful? Give feedback.
All reactions