Network interface name: Difference between revisions
(Template migration to LLM-Optimized Wiki Template) |
(Fix: remove --- horizontal lines (7 removed)) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 18: | Line 18: | ||
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | == Purpose == | ||
| Line 28: | Line 27: | ||
* Non-goals: 다른 주제로의 확장 | * Non-goals: 다른 주제로의 확장 | ||
== Key Concepts == | == Key Concepts == | ||
| Line 42: | Line 40: | ||
|} | |} | ||
== Detailed Explanation == | == Detailed Explanation == | ||
| Line 67: | Line 64: | ||
[https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Predictable Network Interface naming] and is part of systemd, to which Ubuntu has been transitioning as of version 15.04. the idea is to set interface name depends on physical location of hardware and can be predicted/guessed by looking at <code>lspci</code> or <code>lshw</code> output. | [https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Predictable Network Interface naming] and is part of systemd, to which Ubuntu has been transitioning as of version 15.04. the idea is to set interface name depends on physical location of hardware and can be predicted/guessed by looking at <code>lspci</code> or <code>lshw</code> output. | ||
== Best Practices == | == Best Practices == | ||
| Line 75: | Line 71: | ||
* 테스트 환경에서 먼저 검증 | * 테스트 환경에서 먼저 검증 | ||
== References == | == References == | ||
| Line 81: | Line 76: | ||
* [https://wiki.hpcmate.com Network interface name] | * [https://wiki.hpcmate.com Network interface name] | ||
== Related Pages == | == Related Pages == | ||
| Line 90: | Line 84: | ||
* [[Network]] | * [[Network]] | ||
[[Category:Network]] | [[Category:Network]] | ||
== Knowledge Graph == | |||
Related | |||
→ [[Network performance test]] | |||
→ [[RDMA]] | |||
→ [[NIC Bonding]] | |||
→ [[Network]] | |||
→ [[IPMI]] | |||
→ [[SDN]] | |||
→ [[NFS]] | |||
[[Category:Configuration]] | [[Category:Configuration]] | ||
Latest revision as of 11:29, 17 July 2026
Overview
Network interface name에 대한 기술 문서입니다.
Summary
- 무엇인가? - Network interface name
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: Network interface name에 대한 기술 정보 제공
- Scope: Network interface name의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| Network interface name | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
The Linux kernel assigns names to network interfaces, nowaday there are multiple network interface naming scheme is available and each has pros and cons.
eth0, eth1, etc were simply assigned by the kernel.
Following step would be the simplest way among many possible way ,
Step 1, Add this to the line below "net.ifnames=0 biosdevname=0"
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
Step 2, Update GRUB, depends on your OS.
Debian based Ubuntu/Mint:
update-grub
Centos/RHEL
grub2-mkconfig -o /boot/grub2/grub.cfg
Step 3, Reboot and check
udev to identify interfaces by MAC address and assign a fixed interface number to any interface by writing the rules to /etc/udev/rules.d/xxx.rules
for example,
#/etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x8086:0x100e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="aa:bb:cc:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
Predictable Network Interface naming and is part of systemd, to which Ubuntu has been transitioning as of version 15.04. the idea is to set interface name depends on physical location of hardware and can be predicted/guessed by looking at lspci or lshw output.
Best Practices
- 최신 버전 사용 권장
- 공식 문서 참고
- 테스트 환경에서 먼저 검증
References
Related Pages
Knowledge Graph
Related
→ Network performance test → RDMA → NIC Bonding → Network → IPMI → SDN → NFS