Hello,
I have to provision a server via foreman that has lacp setup on the 2
switch ports it is connected to and the default fallback timeout is
set too high which I cannot control. This means that I cannot
provision the host using a single nic and have to setup a bond during
the pxe process. I have tried to setup the bond in the interfaces
section of my host when creating it in foreman but during pxe bootup
it does not even seem to load the bonding driver and no bond interface
is setup. Is this even possible using foreman? If so, can someone
help me with this please. I have a urgent need to get this server up
and any assistance would be greatly appreciated!
Thanks in advance.
-J
I have a few question that might help me research a solution to this.
Do the ports on you switch allow traffic to pass on one of the ports, even if LACP isn’t running?
Are you able to PXE boot with the LAG on the switch, and just the single interface on the client?
Is there any LAG configuration settings in your machines network boot config? If so did you configure a lag there?
Thanks,
—Perry
We regularly do PXE provisioning over ports that are generally configured
for bonding. The network guys have to set the force-up parameter (forgive
me if that's not absolutely accurate, but they translate my non-network
speak and get it working). This is on Juniper switches.
The result is that the PXE can happen over one of the ports for a limited
time after the port comes up (the time here is configurable) before it
reverts to bonding-only operation.
D
···
On Wednesday, 25 October 2017 17:12:08 UTC+1, Jagga Soorma wrote:
>
> Hello,
>
> I have to provision a server via foreman that has lacp setup on the 2
> switch ports it is connected to and the default fallback timeout is
> set too high which I cannot control. This means that I cannot
> provision the host using a single nic and have to setup a bond during
> the pxe process. I have tried to setup the bond in the interfaces
> section of my host when creating it in foreman but during pxe bootup
> it does not even seem to load the bonding driver and no bond interface
> is setup. Is this even possible using foreman? If so, can someone
> help me with this please. I have a urgent need to get this server up
> and any assistance would be greatly appreciated!
>
> Thanks in advance.
> -J
>
Yes. LAGs (or bonds as they are called in Linux-land) usually use a
protocol called LACP. The two stations (in your case the network switch,
and the server) will send special LACP packets between all ports on the LAG
to (among other things) detect which ports will be used in the LAG. One of
the primary reasons for this is to ensure ports are not plugged in
incorrectly and to prevent loops from occurring.
By default (on most vendors devices) if a port can not complete a LACP
negotiation, it will default to not forward traffic. The "force-up"
parameter you described overrides this behavior allows and puts the port in
the forwarding state for a limited period of time.
In order to use LACP on a bond in Linux, the bond mode has to be set to
"8023ad". This can be set on the interface screen for the bond in foreman.
If sounds like you found a solution to the problem? or are you still trying
to find a way to provision without having to use the "force-up" option?
–Perry
···
On Wed, Nov 1, 2017 at 6:45 AM, Duncan Innes wrote:
We regularly do PXE provisioning over ports that are generally configured
for bonding. The network guys have to set the force-up parameter (forgive
me if that’s not absolutely accurate, but they translate my non-network
speak and get it working). This is on Juniper switches.
The result is that the PXE can happen over one of the ports for a limited
time after the port comes up (the time here is configurable) before it
reverts to bonding-only operation.
D
On Wednesday, 25 October 2017 17:12:08 UTC+1, Jagga Soorma wrote:
Hello,
I have to provision a server via foreman that has lacp setup on the 2
switch ports it is connected to and the default fallback timeout is
set too high which I cannot control. This means that I cannot
provision the host using a single nic and have to setup a bond during
the pxe process. I have tried to setup the bond in the interfaces
section of my host when creating it in foreman but during pxe bootup
it does not even seem to load the bonding driver and no bond interface
is setup. Is this even possible using foreman? If so, can someone
help me with this please. I have a urgent need to get this server up
and any assistance would be greatly appreciated!
Thanks in advance.
-J
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/bWo9D5RtFn0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
