
This is a multi-part message in MIME format. ----_com.samsung.android.email_7576755804572660 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit We checked the port groups, and servers are cabled correctly. After server is rebooted, em1 is the only interface passing traffic. Other 3 nics sitting idle. We can down each port on the switch and confirm it is down on the server. I am pretty sure it is related to the bridge that was created to pass vm-host-altn traffic when the appliance was first installed. -------- Original message -------- From: Chris Adams <cma@cmadams.net> Date: 4/20/17 5:40 PM (GMT-06:00) To: users@ovirt.org Subject: Re: [ovirt-users] LACP Bonding issue _____
From : Chris Adams [cma@cmadams.net] To : users@ovirt.org [users@ovirt.org] Date : Thursday, April 20 2017 17:40:25 Once upon a time, Bryan Sockel said: It seems that is some disconnect between my network bridge, the bond and my interfaces. I would like to some how get my bond to use all 4 interfaces. On reboot, it always seems to reset consistently to EM1.
Are you sure the switch side is all the same LACP group? Sounds like one port may accidentally be in a separate group, and that happens to be em1. You might try swapping wires between em1 and another port and reboot and see which ports come up - if all but the port with the wire formerly in em1 come up, it points to the switch config. -- Chris Adams _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ----_com.samsung.android.email_7576755804572660 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3DUTF-8"></head><body><div>We checked the port groups, and = servers are cabled correctly.</div><div><br></div><div>After server is = rebooted, em1 is the only interface passing traffic. Other 3 nics = sitting idle. We can down each port on the switch and confirm it = is down on the server.</div><div><br></div><div><br></div><div>I am = pretty sure it is related to the bridge that was created to pass = vm-host-altn traffic when the appliance was first installed.</div><div = id=3D"composer_signature"><div style=3D"font-size:85%;color:#575757" = dir=3D"auto"><br></div></div><div><br></div><div><br></div><!-- = originalMessage --><div>-------- Original message = --------</div><div>From: Chris Adams <cma@cmadams.net> = </div><div>Date: 4/20/17 5:40 PM (GMT-06:00) </div><div>To: = users@ovirt.org </div><div>Subject: Re: [ovirt-users] LACP Bonding issue = </div><div><br></div><div = style=3D"margin-left:2px;padding-left:2px;border-left:1px solid = #202020;"><div style=3D"font-size: 10pt; background-color: #ffffff; = color: #000000; font-weight: 400; font-family: = Tahoma,Arial,Verdana,sans-serif;" ><hr /><div><span = style=3D"font-weight: 700">From</span> : Chris Adams = [cma@cmadams.net]</div><div><span style=3D"font-weight: 700">To</span> : = users@ovirt.org [users@ovirt.org]</div><div><span style=3D"font-weight: = 700">Date</span> : Thursday, April 20 2017 17:40:25</div></div>=0A= <pre>Once upon a time, Bryan Sockel <Bryan.Sockel@altn.com> said:
It seems that is some disconnect between my network bridge, the bond = and my=20 interfaces. I would like to some how get my bond to use all 4 = interfaces. =20 On reboot, it always seems to reset consistently to EM1.
Are you sure the switch side is all the same LACP group? Sounds like one port may accidentally be in a separate group, and that happens to be em1. You might try swapping wires between em1 and another port and reboot and see which ports come up - if all but the port with the wire formerly in em1 come up, it points to the switch config. --=20 Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users </pre></div></body></html> ----_com.samsung.android.email_7576755804572660--

Once upon a time, Bryan Sockel <Bryan.Sockel@altn.com> said:
We checked the port groups, and servers are cabled correctly.
After server is rebooted, em1 is the only interface passing traffic. Other 3 nics sitting idle. We can down each port on the switch and confirm it is down on the server.
I am pretty sure it is related to the bridge that was created to pass vm-host-altn traffic when the appliance was first installed.
-------- Original message -------- From: Chris Adams <cma@cmadams.net> Date: 4/20/17 5:40 PM (GMT-06:00) To: users@ovirt.org Subject: Re: [ovirt-users] LACP Bonding issue
_____
From : Chris Adams [cma@cmadams.net] To : users@ovirt.org [users@ovirt.org] Date : Thursday, April 20 2017 17:40:25 Once upon a time, Bryan Sockel said: It seems that is some disconnect between my network bridge, the bond and my interfaces. I would like to some how get my bond to use all 4 interfaces. On reboot, it always seems to reset consistently to EM1.
Are you sure the switch side is all the same LACP group? Sounds like one port may accidentally be in a separate group, and that happens to be em1.
You might try swapping wires between em1 and another port and reboot and see which ports come up - if all but the port with the wire formerly in em1 come up, it points to the switch config.
-- Chris Adams _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Chris Adams <cma@cmadams.net>

For what it's worth I set up my bond0 manually on CentOS before installing ovirt hosted engine and the ovirtmgmt bridge "took over" from bond0.. But it appears to still be working. At least I've not noticed links being down, and "ifconfig" shows decent amount of traffic on both eno1 and eno2. Maybe wipe, re-install, configure it manually, and then install ovirt? -derek On Thu, April 20, 2017 8:58 pm, Bryan Sockel wrote:
We checked the port groups, and servers are cabled correctly.
After server is rebooted, em1 is the only interface passing traffic. Other 3 nics sitting idle. We can down each port on the switch and confirm it is down on the server.
I am pretty sure it is related to the bridge that was created to pass vm-host-altn traffic when the appliance was first installed.
-------- Original message -------- From: Chris Adams <cma@cmadams.net> Date: 4/20/17 5:40 PM (GMT-06:00) To: users@ovirt.org Subject: Re: [ovirt-users] LACP Bonding issue
_____
From : Chris Adams [cma@cmadams.net] To : users@ovirt.org [users@ovirt.org] Date : Thursday, April 20 2017 17:40:25 Once upon a time, Bryan Sockel said:
It seems that is some disconnect between my network bridge, the bond and my interfaces. I would like to some how get my bond to use all 4 interfaces. On reboot, it always seems to reset consistently to EM1.
Are you sure the switch side is all the same LACP group? Sounds like one port may accidentally be in a separate group, and that happens to be em1.
You might try swapping wires between em1 and another port and reboot and see which ports come up - if all but the port with the wire formerly in em1 come up, it points to the switch config.
-- Chris Adams _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

Sorry about the message with nothing new... Once upon a time, Bryan Sockel <Bryan.Sockel@altn.com> said:
We checked the port groups, and servers are cabled correctly.
After server is rebooted, em1 is the only interface passing traffic. Other 3 nics sitting idle. We can down each port on the switch and confirm it is down on the server.
I am pretty sure it is related to the bridge that was created to pass vm-host-altn traffic when the appliance was first installed.
Well, I don't have any problem with that setup on multiple oVirt clusters (including a bunch of R610 servers), so I don't think that's it. I configure oVirt for "custom" bonding options; I use: mode=802.3ad lacp_rate=1 xmit_hash_policy=layer2+3 Is it possible to move the wires around temporarily, so different server ports are connected to different switch ports? It would be interested to see if the "solo" behavior stayed with the port or the wire. -- Chris Adams <cma@cmadams.net>
participants (3)
-
Bryan Sockel
-
Chris Adams
-
Derek Atkins