Child pages
  • Configure Pair Bonding, VLANs, and Bridges for KVM Hypervisor

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update individual port settings as needed.

...

  • Ensure that the upstream switches are configured for pair bonding and tagged VLAN's.
    • Get the information about the VLAN's, especially their names, relevant gateways, and net masks
    • Typically, only one gateway on one VLAN is configured.
    • Assume
  • For this example, assume that the VLAN's are called br100 and "br101"100" and "101" on the switches.Do not call them "vlan100" or "vlan100", this causes problems with older RHEL 6 init scripting.
    • The bonded VLAN's will then called "bond0.100" and "bond0.101", respectively.
    • The KVM bridges will be called "br100" and "br101", respectively.
  • Typically, only one gateway on one VLAN is configured.
    • Setting gateways on multiple VLANs can create enormous routing confusion.
  • Get the hostname and other network configurations for VLAN "100" for the new server, especially:
    • Fully qualified Hostname
      • This is tyically the "hostname" used for the host, itself.
    • IP address
    • Netmask
    • Gateway
    • DNS servers
  • Get the hostname and other network configurations for VLAN "101" for the new server, especially:
    • Fully qualified Hostname
      • This *should not match* the hostname on VLAN "100", to allow separate monitoring and controlled access.
    • IP address
    • Netmask
    • Gateway (Secondary VLAN's do not normally have a gateway.)
    • DNS servers
      • Normally matches VLAN 100 DNS server.

...

      • If they do not match, select a consistent set of DNS servers manually.
      • One DNS server on each VLAN is workable if and only if they provide identical information.

Configure the fully qualified hostname

  • Edit /etc/sysconfig/network to contain the information below.
    • The fully qualified hostname, in particular, is the primary hostname desired from the network configurations above.
      Code Block
      HOSTNAME=hostname.example.com
      NETWORKING=yes
      # IPv4
      NETWORKING=yes
      NOZEROCONF=yes
      # IPv6, necessary for bonding
      NETWORKING_IPV6=yes
      IPV6INIT=yes
      
  • Note that IPv6 must, must, must be enabled for bonding and other features to work privately.
    • NOZEROCONF=yes avoids the unnecessary "169.254.*" fallback addresses and routing from being activated, simply to prevent network confusion.

...