SDN

From HPCWIKI
Revision as of 15:16, 16 July 2026 by Clara (talk | contribs) (Template migration to LLM-Optimized Wiki Template)
Jump to navigation Jump to search

Template:Status

Template:TOC

Overview

SDN에 대한 기술 문서입니다.

Summary

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

---

Purpose

이 문서가 존재하는 이유

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

---

Key Concepts

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

---

Detailed Explanation

SDN timeline

SDN architecture) defines how a networking and computing system can be built using a combination of open software-based technologies and commodity networking hardware to supports dynamic programmable network configuration. SDN uses the controller for network device management, network service orchestration, and service traffic scheduling, which features low costs, centralized management, flexible scheduling and dynamic network environment. Automatic operation, management and centralized management brought by SDN have great application space in automatic scheduling and capacity expansion of scaleable network in large-scale data centers. Many network device vendors have adopted the concept of SDN. such as Avaya, HP, Brocade, Cisco, Hewlett Packard (HP) and Vmware NSX.

Comparison between the traditional network architecture and SDN architecture.png

The traditional distributed networks, reachability information is broadcast between devices at Layer 2, and topology information is transmitted through standard routing protocols at Layer 3. This requires that all devices, regardless of their vendors, use the same network protocol for successful communication. To well adapt to varying requirements and scenarios, traditional networks are becoming more and more complex. even the traditional network devices are managed one by one using commands, leading to low network management and service scheduling efficiency and high operation costs. the applications can build an abstracted view of the network. These applications could include networking management, analytics, or business applications used to run large data centers. SDN controller is a 'brain” of the SDN network. The SDN controller is a logical entity that receives instructions or requirements from the SDN application layer and relays them to the networking components. The controller also extracts information about the network from the hardware devices and communicates back to the SDN applications with an abstract view of the network, including statistics and events. For example, Cisco's APIC-EM is a commercial version of SDN controller that was created for Enterprise hardware. The SDN networking devices control the forwarding and data processing capabilities for the network. This includes the forwarding and processing of the data path. The SDN architecture APIs are often referred to as northbound and southbound interfaces.

  • Northbound interface is defined as the connection between the controller and applications
  • Southbound interface is the connection between the controller and the physical networking hardware.
Type of SDN product .png
  • Open SDN: Network administrators use a protocol like OpenFlow to control the behavior of virtual and physical switches at the data plane level.
  • SDN by APIs: Instead of using an open protocol, applica... [내용 계속]

---

Best Practices

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

---

References

---

Related Pages

---