RHEL 6 kickstart with bonding and vlan
Hi,
I need to install some machines and I've tried installing throught a vlan wich works well but I need to install configuring a bond and several virtual interfaces tagged to different vlans, ¿is this possible with kickstart?
Thanks.
Responses
Guru
6863 points
Configuring a bond at build time is fairly simple:
bond=bond0:em1,em2:mode=active-backup,primary=em1
vmlinuz initrd=initrd.img ks=http://rhnsat01.company.com/ks/cfg/org/1/label/kickstart6 dns=10.98.230.27,10.98.230.28 hostname=rhvsrv91.company.com ip=10.98.196.132 netmask=255.255.254.0 gateway=10.98.196.1 bond=bond0:em1,em2:mode=active-backup,primary=em1
The following indicates that VLAN tagging is also possible (and appears simple as well)
https://access.redhat.com/site/solutions/25133
network --hostname host.example.com --device eth0 --vlanid 123 --bootproto static --ip 5.6.7.8 --netmask 255.255.255.0 --gateway 5.6.7.1
Active Contributor
162 points
I've been trying to get this to work for 2 years over mode=4 bonding. I always have to get our network team to change the ports back to mode=1 though. Anyone have experience with this? Trying it on RHEL7.0 now but it remains un-pingable and cannot reach the ks server:
linux text ip=10.11.132.238 gateway=10.11.132.1 netmask=255.255.252.0 nameserver=10.11.7.121 ks=http://10.12.7.206/ks/podb032-ch3 vlanid=132 bond=bond0:p3p1,p3p2:mode=802.3ad,miimon=100,lacp_rate=fast ksdevice=bond0
This setting worked for me with mode = 4, without requesting Network team to change the ports at switch end
linux ks=http://10.20.79.88/kickstart/elastic_ks6.8_64.cfg ip=10.50.90.38 netmask=255.255.255.0 gateway=10.50.91.1 dns=57.12.18.35 bond=bond0:eth0,eth1:mode=802.3ad,miimon=100,lacp_rate=slow,primary=eth0
Having same situation as Brad here. KS is not working over mode=4 on rhel6 , though rhel7.2 has no problems to KS over LACP enabled network. This definitely big inconvenience as this is default network configuration for physical servers in our company. And using single NIC is not an option just for ks as LACP enabled switches will not allow this.
Whenever I search for answers for my particular situation, I keep seeing this result over and over again. Hopefully someone with a similar situation can help me?
I'm trying to install RHEL7.2 via kickstart and PXELinux. The PXELinux part with a bonding device and a vlan tag works fine. I can verify that during Anaconda's installation in the provided shell. However after the kickstart installation is done, the network configuration is not what I expected.
How do you get a correct kickstart network section that makes sure you: - enslave em1 and em2 to the bond0 master - assign a vlan id to bond0 and configure a static IPv4 address on that vlan interface?
Active Contributor
162 points
Dennis, you could force it to be exactly what you want with a ks postscript (or put it in a snippet to make it easier to maintain). Something like:
# bonding for VLAN132
cat << EOF > /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
BONDING_OPTS="mode=1 downdelay=100 updelay=100 miimon=100 xmit_hash_policy=0 use_carrier=1"
EOF
cat << EOF > /etc/sysconfig/network-scripts/ifcfg-bond0.132
DEVICE=bond0.132
IPADDR=PUBIP
NETMASK=PUBNM
ONBOOT=yes
VLAN=yes
BOOTPROTO=none
USERCTL=no
EOF
cat << EOF > /etc/sysconfig/network-scripts/ifcfg-p3p1
DEVICE=p3p1
ONBOOT=yes
MASTER=bond0
SLAVE=yes
EOF
cat << EOF > /etc/sysconfig/network-scripts/ifcfg-p3p2
DEVICE=p3p2
ONBOOT=yes
MASTER=bond0
SLAVE=yes
EOF
I'm getting the same feeling Brad. We're running Satellite 6(.2) and it includes snippets in %post that are supposed to do this stuff automagically, but you guessed it: it doesn't. Satellite isn't able to create a TFTP file when I create a network configuration in Satellite for a host with 2 physical interfaces, bonding on those 2 interfaces and a VLAN tag on that bonding interface.
I've got a support case open for that issue, but the TFTP file is step 1. The kickstart template that does the actual configuration of the server is step 2. From what I understand from the manuals on redhat.com, step 2 should work with a "regular" kickstart file, whether you're using Satellite or not. But from my experience, it just doesn't work.
Thank you for your response, I'll go ahead with a %post like you suggest.
Expert
851 points
Any updates from your support ticket? I'm using satellite 6.2.8 and having issues with setting em1,em2 a bond interface with those attached. It creates the bond now, but but can't assign it as the 'primary'
No, unfortunately nothing else but that there's RFE that's been set to private. They'll keep me updated.
The %post snippet works as expected. Predictable, as I like it.
Expert
851 points
Thanks for the reply. I've got bonding working now on 6.2.8.
I create new systems, edit the first interface, enter mac, set identifier and uncheck provision and primary, remove dns and subnet. Then add my 2nd interface, add mac only. Then add interface type bond, set mac of interface 1, set primary and provision, and set ip, attached devices and my mode.
When I provision the host, it works and all the configuration are correct.
Expert
851 points
Thanks for the reply. I've got bonding working now on 6.2.8. I create new systems, edit the first interface, enter mac, set identifier and uncheck provision and primary, remove dns and subnet. Then add my 2nd interface, add mac only. Then add interface type bond, set mac of interface 1, set primary and provision, and set ip, attached devices and my mode.
When I provision the host, it works and all the configuration are correct.
Do you press the apply button between those actions? I'll try these steps when we've updated to 6.2.8 (running 6.2.7 at the moment)
Expert
851 points
Here's the steps I follow.
Go to Interfaces tab in 'New Host', > click edit on existing interface
- enter/edit the following information:
- type: leave as interface
- MAC: enter MAC of 1st nic
- Device Identifier: nic name, ie eth0
- DNS: clear field
- Domain: clear
- Subnet: clear
- IP: clear
- Primary: uncheck
- Provision: uncheck
- click Ok
- Add 2nd nic by clicking add Interface and repeat the above for eth1(nic) but uncheck provision and put in 2nd nic Mac
Add bond0 interface. Click on 'Add Interface' and enter the following:
-Type: Bond
- Mac : nic1 mac address
- Device Identifier: bond0
- dns name: short hostname (ie, myhost)
- domain: choose domain
- subnet: choose subnet
- Primary: check
- Provision: check
- Remote Execution: check
- Mode: active-backup
- Attached devices: eth0,eth1
- Click ok
Then click submit for new host. Note, you may have to enter hostname again in hosts, because when you uncheck primary it removes the name on the host tab.
How can I configure team at build time ? It seems only option allowed is team=team0:en0,en1 . I am unable to specify runner or mode during boot for a team interface.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.