NIC Bonding

From HPCWIKI
Jump to navigation Jump to search

Template:Status

Template:TOC

Overview

NIC Bonding에 대한 기술 문서입니다.

Summary

  • 무엇인가? - NIC Bonding
  • 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
  • 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시


Purpose

이 문서가 존재하는 이유

  • Goal: NIC Bonding에 대한 기술 정보 제공
  • Scope: NIC Bonding의 개념, 사용법, 설정
  • Non-goals: 다른 주제로의 확장


Key Concepts

Concept Description Related
NIC Bonding HPC/서버 환경에서 중요한 기술 개념 Linux, Server


Detailed Explanation

Network bonding is the aggregation or combination of multiple LAN cards into a single bonded interface to provide high availability and redundancy. Network bonding is also known as NIC teaming. This pages shows how to bind multiple network interfaces into a single load balanced or fault-toleranced interface and so on. The Linux bonding driver allows system administrators to set up bonding interfaces with different modes. A bonding mode specifies the policy indicating how bonding slaves are used during network transmission. To achieve the maximum throughput and fault toleration, it is important to choose the proper bonding mode and the corresponding options for the setup[1] In Netplan, the default is balance-rr (round robin). Possible values are balance-rr, active-backup, balance-xor, broadcast, 802.3ad, balance-tlb, and balance-alb. For Open vSwitch active-backup and the additional modes balance-tcp and balance-slb are supported[2]

Mode Description Load balancing Fault tolerance
balance-rr or 0 Round-robin policy. Transmits packets in sequential order from the first available slave through the last. O O
active-backup or 1 Active-backup policy. Establishes that only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. X O


Best Practices

  • 최신 버전 사용 권장
  • 공식 문서 참고
  • 테스트 환경에서 먼저 검증


References


Related Pages

Knowledge Graph

Related

LinuxServerHardwareNetwork