Network Management — SNMP, SDN, QoS
458 words
2 min read
Visual companion
Python
Type and operator map
Python Week 1: the first filter for runtime behavior
View
Revision summary
What this note is really saying
Short form
# Network Management — SNMP, SDN, QoS ## 🎯 Learning Objectives - Explain SNMP manager/agent architecture - Describe software-defined networking (SDN) concepts - Implement QoS with DiffServ and IntServ - Analyze network traffic engineering * * * ## 1. SNMP (Simple Network Management Protocol) **Architecture:** - **M...
Network Management — SNMP, SDN, QoS
🎯 Learning Objectives
- Explain SNMP manager/agent architecture
- Describe software-defined networking (SDN) concepts
- Implement QoS with DiffServ and IntServ
- Analyze network traffic engineering
1. SNMP (Simple Network Management Protocol)
Architecture:
- Manager: Central monitoring station
- Agent: Software on managed device (router, switch, server)
- MIB: Management Information Base (tree of variables) Operations: GET, GET-NEXT, SET, TRAP (agent → manager alert) (Diagram)
2. Software-Defined Networking (SDN)
2.1 Traditional vs. SDN
| Aspect | Traditional | SDN |
|---|---|---|
| Control plane | Distributed (each switch) | Centralized controller |
| Data plane | Switch hardware | Switch hardware |
| Forwarding | Distributed routing protocols | Controller installs flows |
| Programming | CLI per device | Northbound API |
| Protocol | OSPF, BGP, etc. | OpenFlow |
2.2 OpenFlow
Match: Switch matches packet fields (MAC, IP, port, VLAN) Action: Forward, drop, modify, send to controller
Flow table entry:
| Match | Priority | Counters | Instructions | Timeout |
|---|---|---|---|---|
| ip_src=10.0.0.1 | 100 | 1024 pkts | output:3 | 30s |
3. Quality of Service (QoS)
| Model | Approach | Granularity | Complexity |
|---|---|---|---|
| Best-effort | No QoS | None | None |
| IntServ | Per-flow reservation (RSVP) | Flow | High |
| DiffServ | Packet marking (DSCP) | Class | Low |
DSCP classes:
- EF (Expedited Forwarding): Low loss, low latency (VoIP)
- AF (Assured Forwarding): 4 classes × 3 drop precedences
- BE (Best Effort): Default
4. Common Pitfalls
Pitfall: SDN Controller Scalability
The mistake: Thinking a single controller handles all flows.
Correct approach: Use controller clustering (e.g., ONOS, OpenDaylight). Install proactive flows for common traffic; only unknown flows go to controller.
5. Key Concepts Reference
| Technology | Purpose | Key Protocol |
|---|---|---|
| SNMP | Monitor devices | UDP 161/162 |
| SDN | Centralized control | OpenFlow |
| QoS | Service guarantees | RSVP, DSCP |
| NetFlow | Traffic analysis | IPFIX |
6. 📝 Practice Questions
Q1: How does an SDN switch handle the first packet of a new flow?Answer: The switch has no matching flow entry. It sends a PacketIn message to the controller via OpenFlow. The controller decides the path, installs flow entries in all switches along the path, and instructs the ingress switch to forward the packet. Subsequent packets match the installed flow entry and are forwarded at wire speed. Q2: DiffServ marks VoIP packets as EF (DSCP 46). Why is this helpful?Answer: EF ensures: (1) Low delay — EF packets are queued first. (2) Low jitter — consistent forwarding treatment. (3) Low loss — dedicated bandwidth allocation. Without QoS, VoIP packets compete with bulk downloads and suffer buffer bloat (100+ms delay), causing voice quality degradation. Q3: What's the difference between SNMP GET and SNMP TRAP?Answer: GET is poll-based (manager asks agent for data). TRAP is event-based (agent alerts manager without being asked). Traps are more efficient for urgent events (link down, authentication failure) but may be lost if not acknowledged. GET ensures reliability but requires polling overhead.
7. 🔗 Cross-References
- Week 3 - IP Routing: Control plane protocols
- Week 6 - Network Security: SDN security
- BSCS4022 (OS): System management Join Discord PreviousSocket ProgrammingNextMultimedia Networking