On Wed, Sep 26, 2012 at 7:19 AM, Tom H <[email protected]> wrote: > On Mon, Sep 24, 2012 at 7:25 PM, Nico Kadel-Garcia <[email protected]> wrote: >> >> I've got an SL 6 setup to deal with which I inherited, with hosts that >> only have two NIC's, need to be on three VLAN's, and need to run KVM >> virtual servers. 9Actually, they may wind up as our favorite upstream >> vendor's distribution, but I'm working with what I have now.) >> >> NetworkManager, of course, remains the utterly useless kludge that it >> always has been as far as pair bonding is concerned. I've got the >> VLAN's working on toop of the pair bonds by disabling NetworkManager, >> setting up bond0 as a bonded pair of eth0 and eth1, and adding virtual >> ports called bond0.vlan1, bond0.vlan2, etc., and adding the "VLAN=yes" >> to ifcfg-bond0.vlan1, ifcfg-bond0.vlan2, etc. >> >> No problem so far. But now I need to to bridged ports for KVM, and I'm >> trying to assemble the necessary bits. Do I just need to say "don't do >> the VLAN's", or does someone have a graceful set of options for doing >> KVM briding *on top of * bonded ports doing VLAN's? > > I've never had to layer all of these but my suggestion'd be: > > > > $ cat /etc/sysconfig/network-scripts/ifcfg-eth{0,1} > BOOTPROTO="none" > DEVICE="eth{0,1}" > MASTER="bond0" > ONBOOT="yes" > SLAVE="yes" > > > > $ cat /etc/sysconfig/network-scripts/ifcfg-bond0 > BONDING_OPTS="mode=... [...]" > BOOTPROTO="none" > BRIDGE="br0" > DEVICE="bond0" > ONBOOT="no" > > > > $ cat /etc/sysconfig/network-scripts/ifcfg-br0 > BOOTPROTO="none" > [DELAY="0"] > DEVICE="br0" > ONBOOT="no" > [STP="on|off"] > TYPE="Bridge" > > > > $ cat /etc/sysconfig/network-scripts/ifcfg-vlan9 > BOOTPROTO="dhcp" ## for simplicity on this list > DEVICE="vlan9" > ONBOOT="yes" > PHYSDEV="br0" > VLAN="yes" > VLAN_NAME_TYPE="VLAN_PLUS_VID_NO_PAD" > > or > > $ cat /etc/sysconfig/network-scripts/ifcfg-br0.9 > BOOTPROTO="dhcp" > DEVICE="br0.9" > ONBOOT="yes" > VLAN="yes" > VLAN_NAME_TYPE="DEV_PLUS_VID_NO_PAD"
Looking at another post in this thread and the RH documentation, it seems that it should be 'ONBOOT="yes"' everywhere. I'm surprised because I've used ONBOOT="no" in the past but...
