개발 공부
(Network) SET, Switch-Embedded Teaming, Hyper-V Port 본문
# Windows 서버 환경에서, 2개의 스위치와 각각 연결된 2개의 NIC Teaming 옵션
- LACP (Link Aggregation Control Protocol) + LBFO(Load Balancing and Failover) Teaming
- SET(Switch-Embedded) Teaming
-> LACP는 많은 사람이 안정적이라고 함. 그러나 MS는 LBFO의 지원을 종료하였고 SET를 권장
-> SET는 Switch independent 이며 Hyper-V 환경에서는 Hyper-V Port 설정 권장
| ※ 참고 Teaming Modes - Switch independent mode - Switch dependent mode Load Distribution Modes - Address Hash - Hyper-V Port - Dynamic Teaming 확인 방법 Get-VMSwitch | Format-List * Get-VMSwitchTeam Get-VMSwitch | Select-Object Name, Teamed, LoadBalancingAlgorithm |
# SET 관련 아래 용어 정리 필요
- pNICs = physical NICs on the host or Network Adapters.
- tNICs = Team Interfaces exposed by the team, Team NICs, or tNICs.
- vNICs = Interfaces exposed by the Hyper-V Virtual Switch to the Management OS (host partition).
- vmNICs = Interfaces exposed by the Hyper-V Virtual Switch into a Virtual Machine.
# Hyper-V Port Mode 작동 원리
- Host server는 Hash로 vmNICs별 pNICS를 배정
- VM의 Outbound 요청은 Hyper-V Manager에서 설정한 VM의 MAC 주소를 가지고 위에서 배정된 pNICS를 타고 나감
- External Switch는 MAC Address Table에 위의 pNICS가 연결된 포트로 해당 MAC을 Mapping
- 새로운 포트 정보가 갱신되기 전까지 해당 포트로 중계
# Switch의 MAC Address Learning
- Switch는 개별 포트에서 들어오는 MAC을 MAC Address Table에 학습함
# Switch 관련 발생 가능 이슈
| Issue Type | Description |
| MAC flapping | If a NIC flaps (goes up/down frequently), the switch sees MACs moving fast. |
| Port security/stickiness | Switch may block traffic if it expects a MAC only on one port. |
| Asymmetric routing | If traffic comes in on one NIC and replies go out another, stateful firewalls may drop them. |
| Switch lag in updating MAC | Can cause temporary drops (e.g., reply goes to dead port before switch updates). |
# Tips for Reliable Operation
- Disable MAC security features (like port security or sticky MAC) if you're using SET in switch independent mode.
- Use dynamic distribution mode instead of Hyper-V port if you're worried about NIC load balancing.
- Use multiple physical switches with LACP if you want switch coordination — but that’s not switch independent anymore.
'windows' 카테고리의 다른 글
| (Network) SET teaming.Hyper-V LoadBalancing 이용 시 스위치 power off 와 power on의 차이 (0) | 2025.07.24 |
|---|---|
| (Network) How to overcome SET failover (3) | 2025.07.07 |
| (Network) LAG, LACP, LBFO, SET (0) | 2025.07.07 |
| (Failover Cluster) DNS의 역할 (0) | 2025.05.30 |
| (Failover Cluster) Heartbeat Health Check (0) | 2025.05.30 |