Hello when you build new host, there are several tabs for the form. Click Interfaces form, then green "+ Add Interface" button. A modal window will appear where you specify attributes I explained in last email. Once you're done with Interfaces tab, let the host provision and verify that at the end (after final reboot) the interfaces are configured according to what you defined in the form.
You can find some information in our manual too, see https://www.theforeman.org/manuals/1.11/index.html#4.4.7Networking Hope this helps -- Marek On Thursday 04 of August 2016 13:28:10 you wrote: > Hi Marek, > > Thank you very much for your help. But I am a little bit confused as I am > new in Foreman Technology. So could you please type step by step (in a > simple way) what should I do to configure the network according to my > scenario. > > Thanks in advance, > Regards, > Mostafa > > On Thu, Jul 28, 2016 at 4:45 PM, Marek Hulán <[email protected]> wrote: > > On Thursday 28 of July 2016 11:04:08 nilelinux . wrote: > > > Hi All, > > > > > > Please I have installed Foreman version 1.8.0 on CentOS 7.1. I > > > could provision CentOS to a HP blade server which has 6 NICs but I > > > don't > > > know how to configure Bonding on these interfaces. I would like to use > > > Forman to configure Bonding as the following:- > > > > > > Eth0 and Eth1 for Bond1 in VLAN 2 with subnet 192.168.2.0/24. > > > Eth2 and Eth3 for Bond2 in VLAN 3 with subnet 192.168.3.0/24 . > > > Eth4 and Eth5 for Bond3 in VLAN 4 with subnet 192.168.4.0/24 . > > > > > > As I am new in Foreman technology, Could you simplify how to configure > > > > the > > > > > Foreman to auto-configure the bonding. > > > > > > *Best Regards,* > > > > > > *Mostafa Yasin* > > > Show trimmed content > > > > Hello, > > > > 1.8 is quite old version so I'd recommend updating to the most recent > > version > > first. > > > > But in general, you should define these interfaces in host form. To create > > a > > bond you have to define bonded interfaces first so create eth0 and eth1. > > Then > > create a new interface of type bond and use identifiers that you used for > > eth0 > > and eth1 as bonded devices. Since you want to also create a vlan on top of > > the > > bond, you have to define 4th vlan interface. To do it, keep type to > > Interface > > but set the identifier to bond0.1 assuming the bond identifier was set to > > bond0. > > Check virtual NIC checkbox and set the tag to 2 and attached to to bond0. > > Repeat the steps above for all eth0-6, bond1-3 and vlans (bond1.2, > > bond2.3, > > bond3.4) so 12 interfaces in total. Note that the networking info like > > subnet, > > IP etc should be configured on vlan interfaces only. Just the mac address > > might > > be needed on others. > > > > If you want to make an interface that is being used for provisioning also > > part > > of the bond, your switch should be configured to LACP passive since the > > bond is > > configure as the last step of the provisioning. In other words, your > > switch > > must allow non-aggregated traffic for provisioning and aggregated traffic > > for > > communication afterwards. > > > > I'm not entirely sure if provisioning can work if it requires a > > provisioning > > interface traffic to be tagged. Maybe with native vlan. > > > > I'm not a network expert so I'm sorry if I misunderstood something. > > > > -- > > Marek -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
