Chương 3 / 519% của kỳ thi

Network Operations

Operations keep a network healthy, documented, and resilient over time. This chapter covers monitoring with SNMP and syslog, performance metrics, quality of service, documentation and policies, and disaster recovery. Strong operational practices prevent problems and shorten recovery when they occur.

Monitoring and Logging

Effective operations depend on visibility into device health and traffic. SNMP polls metrics and sends traps, while syslog centralizes event messages for correlation. Synchronized time ties these records into a coherent timeline.

Collect metrics with SNMP
SNMP polls counters and CPU usage and sends traps for unsolicited alerts.
Centralize logs with syslog
Aggregating logs enables correlation, retention, and alerting across many devices.
Synchronize clocks with NTP
Consistent timestamps are essential for correlating events during investigations.

Performance Metrics and QoS

Networks are measured by throughput, latency, jitter, and loss, and these guide capacity and quality decisions. Quality of Service prioritizes sensitive traffic during congestion. Baselines define normal so anomalies stand out.

Distinguish bandwidth from throughput
Bandwidth is rated capacity; throughput is the measured successful delivery rate.
Control jitter for real-time traffic
Voice and video degrade when packet delay varies excessively.
Prioritize with QoS
Classify and queue critical traffic so it is served first under congestion.
Maintain a baseline
Comparing current metrics to a baseline reveals developing problems early.

Documentation and Policies

Accurate documentation and clear policies keep operations consistent and auditable. Topology diagrams, agreements, and acceptable use policies define the environment and expectations. Change management governs how modifications happen safely.

Keep topology diagrams current
Physical and logical diagrams speed troubleshooting and planning.
Define SLAs and AUPs
SLAs set service commitments while AUPs govern acceptable resource use.
Follow change management
Obtain approval, schedule windows, and prepare rollback plans before major changes.

Disaster Recovery and Availability

Resilient operations plan for failures with backups and recovery sites. Recovery objectives quantify acceptable downtime and data loss. Choosing the right site type balances cost against recovery speed.

Set RTO and RPO
RTO defines acceptable downtime; RPO defines acceptable data loss in time.
Choose recovery sites by need
Hot sites recover fastest, cold sites cost least, and warm sites are in between.
Test backups regularly
Untested backups may fail when needed; verification ensures recoverability.

Automation and Standardization

Automation applies consistent configurations at scale and reduces human error. Standardized templates prevent configuration drift across devices. These practices are increasingly central to modern network operations.

Standardize configurations
Templates and version control keep device settings consistent and auditable.
Automate repetitive tasks
Automation tools deploy changes quickly and reduce manual mistakes.
Monitor for drift
Detecting deviations from the standard configuration prevents inconsistency.
Kiểm tra kiến thức của bạn
Câu hỏi luyện tập về Network Operations
Luyện tập ngay →

Last updated: July 2026

Báo lỗi