Configure Pair Bonding, VLANs, and Bridges for KVM Hypervisor

Why do all the work for tagged VLAN's

Red Hat does not publish a network GUI to configure pair bonding, KVM bridges, or full VLAN interaction for their OS. These have to be done manuallys, even though they've been built into Red Hat's available scripting and options for years. They're used to provide these features:

Tagged VLANs allow individual network ports to exist on multiple VLAN's, and should not be used without careful planning and review.

There are potential ussues with Tagged VLANs.

If you don't need the tagged VLANs, see: Configure Pair Bonding and Bridges for KVM Hypervisor

Get the network configurations

Configure the fully qualified hostname

Configure pair bonding on bond0

Activate the pair bonding kernel module

Create bond0 slaves for individual network ports.

Note: These directions assume that the physical network ports are reported as eth0 and eth1. Adjust to em0 and em1 or other devices as needed.

Other network devices, such as "eth3", "eth4", or "em0" or :em2, can also be added as needed .

Configure bond0 itself

Configure VLANs on bond0

Configure bridges on bond0

Reboot

Fully activating, and testing, the new network configuration requires a reboot.