Child pages
  • Configure VLAN Tagging Only for TUSK Hypervisor
Skip to end of metadata
Go to start of metadata

Configure VLAN  Tagging Only for TUSK Hypervisor

Why Configure VLAN Tagging Only?

There is a known problem with RHEL and CentOS version 6 in environments where all 3 features of pair bonding, VLAN tagging, and KVM bridging are needed. It simply does not work with the default kernel from the 6.3 release. An update of the kernel package and, ideally, the initscripts package, is critical. But getting the network set up to register an RHEL host and get updates, or to download a kernel for CentOS, can be tricky.

If there is no direct access to a USB drive or hand-burned CD with the extra software, that means it's necessary to activate network, temporarily, with just a tagged VLAN.

Disable pair bonding and other complex setups

Other VLAN tagged ports from bonded, bridged, and other setups will interfere with the minimum VLAN tagging setup and should be disabled.

  • Find out the VLAN tagged ID.
    • We'll assume the VLAN is tagged as "100" on the upstream switches.
    • If the VLAN ID is unknown, stop here.
  • Gain console access to the KVM hypervisor.
    • If network access to the system is working, none of these steps are necessary!!!
  • Back up the existng network setup.
    • cp -a /etc/sysocnfig/network /etc/sysconfig/network-backup
    • rsync -av --delete /etc/sysconfig/network-scripts/ /etc/sysconfig/network-scripts-backup/
  • Delete existing KVM bridges.
    • Review /etc/sysoncifg/network-scripts for any "iffcfg-br*" files
      • Delete any "ifcfg-br*" files.
  • Delete existing bonded and tagged ports.
    • Review /etc/sysonfig/network-scripts for any "ifcfg-bond*.'[vlanid]" files
      • Delete any "ifcfg-bond*.[vlanid]" files.
  • Delete existingi bonded ports.
    • Review /etc/sysonfig/network-scripts for any "ifcfg-bond*" files
      • Delete any "ifcfg-bond*.[vlanid]" files.
    • Ignore any /etc/modprobe.d/bond*.conf files, they're harmless for this.
  • Disable bonding in any "ifcfg-eth* files.
    • Review /etc/sysconfig/network-scripts for any "ifcfg-eth*" files.
      • Delete any lines that start "MASTER=*" lines from them.
      • Delete any lines that start line "SLAVE=" from them.
      • Make sure that the line starting "ONBOOT=" is set to "ONBOOT=yes" for all these ifcfg-eth* files.
      • Make sure that the line starting "BOOTPROTO=" is set to "BOOTPROTO=none" for all these ifcfg-eth* files.

Enable a Tagged VLAN Connection

The setup is well documented in Red Hat's own documentation, at

Update the System

  • SSH to toe the system should now work.
  • Register the system if it is RHEL,
    • No registration is needed for CentOS.
  • Update the operating sytem with the latest patches.
    • yum -y update
  • Only the "kernel" patch is critical for this, but "initscripts" also has some useful updates for complex network setups.
  • Reboot with the new kernel.

Switch to Pair Bonding, VLAN Tagging, and KVM Bridging

  • No labels