💻 Proxmox VE Course III-A-3. Bonding (NIC Teaming) Configuration: Redundancy and Bandwidth Expansion (Active/Backup, LACP)

 

🚀 Extreme #Performance and Non-stop #Stability for Proxmox Networks: Complete Analysis of Bonding Technology

In our previous lecture, we covered the basic #network configuration connecting physical NICs to virtual bridges (vmbr)

However, a single NIC connection carries inherent risks

If a single physical network card fails or a network cable is disconnected, all Virtual Machines (VMs) on that server will be isolated from the outside world, leading to service disruption

The powerful #method to eliminate this Single Point of Failure (SPoF) and even expand network bandwidth is 'Bonding' or 'NIC Teaming'

In this #lecture, we will take an in-depth look at the principles and #optimization settings of bonding technology, which logically groups two or more physical NICs to achieve both redundancy and bandwidth expansion


1. Basic Concept and Necessity of Bonding



Bonding makes multiple physical NICs operate as a single logical interface

A. Eliminating Single Point of Failure (SPoF)

  • Even if a server's physical #NIC or cable is damaged, another NIC immediately takes over its role to prevent service interruption

    This is an essential element of High Availability (HA)

B. Bandwidth Expansion

  • It combines the bandwidth of multiple NICs to provide higher transmission speeds

    For example, bonding two 1Gbps NICs can theoretically yield a #data transmission speed of 2Gbps (varies by mode)

C. Importance in Proxmox Environments

  • Since a Proxmox server processes traffic for multiple VMs, bonding is a crucial #virtualization component for stable VM communication and high-performance I/O


2. Types and Utilization of Bonding Modes (Active/Backup, LACP)

Bonding offers various operation modes, each optimized for a specific purpose

A. Mode 1: Active/Backup (Active-Standby)

  • Principle: Only one NIC is active to process traffic, while others remain on standby. If the active NIC fails, a standby NIC immediately switches over

    This is the simplest and most stable redundancy method

  • Advantages: Can be configured only on the server side without special switch settings

    (Compatible with most basic switches)

  • Disadvantages: Does not provide bandwidth expansion

B. Mode 4: LACP (802.3ad) - Link Aggregation Control Protocol

  • Principle: Activates all NICs to distribute traffic and expand bandwidth

    All NICs work simultaneously, achieving high throughput through load balancing

  • Advantages: Enables bandwidth expansion and is efficient due to packet-level load balancing

  • Disadvantages: The connected network switch must support LACP, and Trunk or Link Aggregation must be configured on the switch side


3. Configuring Bonding via Proxmox GUI



You can easily create and configure bonding interfaces through the GUI

A. Removing IP from Existing NICs

  • Physical NICs (e.g., enp3s0, enp4s0) participating in the bond should not have IP addresses assigned

    Remove any existing IPs from these cards

B. Creating a Bonding Interface

  1. Select the Proxmox node and go to the 'Network' tab\

  2. Click the 'Create' button and select 'Linux Bond'\

  3. Assign a name like bond0 in 'Name', and enter the physical NIC names used for bonding in the 'Slaves' field, separated by commas (,)\

  4. Select the desired bonding mode (e.g., Active-Backup, 802.3ad) in 'Mode'\

  5. Leave the 'Bridge' field blank; IP addresses and gateways will be assigned to the bridge (vmbr), so do not specify them here

C. Adding the Bonded Interface as a Bridge Port

  • You now have a logical interface named bond0

    Add this bond0 to the 'Bridge ports' of the vmbr0 bridge and assign an IP address to vmbr0

    This allows VMs to utilize the redundant bandwidth of bond0 through vmbr0


4. #Troubleshooting and Monitoring After Bonding

Follow-up inspection is essential for a successful bonding setup

A. Checking cat /proc/net/bonding/bond0

  • Run this command in the terminal to check the bonding status

    You can verify which NIC is Active, which is Backup, and check the Link Status

B. Network Cable Test

  • You should test the failover in a #RealOperation environment by intentionally unplugging the active network cable or disabling the switch port to see if it works correctly

    In LACP mode, monitor the changes in bandwidth

C. Driver and Firmware Updates

  • NIC drivers and firmware significantly impact bonding #compatibility and performance

    Keep them updated to the latest versions to prevent potential issues

Bonding technology is a core #infrastructure skill for maximizing the network availability of a single server and ensuring the uninterrupted operation of services

While it may seem complex, accurate understanding and configuration will allow you to upgrade your Proxmox environment to the next level


ProxmoxVE, Performance, Stability, Network, Method, NIC, Data, Virtualization, Troubleshooting, RealOperation, Compatibility, Infrastructure


Optimal performance, best cost efficiency! Experience Proxmox VE-based hosting that perfectly fits your project. Go to Luzen Hosting

댓글

이 블로그의 인기 게시물

💻 Proxmox VE Course II-A-5. CPU and Memory Settings: Understanding Ballooning and NUMA Configuration

Sui (SUI) Mainnet Launch News: Preemptive Buying, Now is the Opportunity!