- ✓Network management encompasses fault, configuration, accounting, performance, and security management, often referred to as the FCAPS model.
- ✓Proactive monitoring involves continuously measuring network performance metrics to detect and address issues before users notice them.
- ✓Capacity management ensures that the network has sufficient bandwidth and resources to meet current demand and planned growth.
- ✓Network documentation including topology maps, configuration records, and change logs is essential for effective ongoing management.
- ✓Service Level Agreements define the performance standards that a network must meet and provide a framework for measuring and reporting network quality.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: We're starting Unit 12: Network Management today. Sam, what's the difference between networking, which we covered in Unit 2, and network management?
Sam: Unit 2 was about understanding how networks work: protocols, devices, topology, design. Network management is about the operational discipline of keeping networks working well once they're built. It's the ongoing processes of monitoring, controlling, maintaining, and improving a network infrastructure throughout its operational lifetime.
Alex: How is network management structured as a discipline?
Sam: The classic framework is FCAPS, an acronym that covers the five main areas. Fault management is about detecting, isolating, and resolving network faults. Configuration management is about controlling and recording the configuration of network devices. Accounting management, also called performance accounting, is about measuring and reporting on network usage. Performance management is about monitoring and optimising network performance. And security management is about protecting the network from threats.
Alex: Let's start with fault management. What does that involve in practice?
Sam: Fault management starts with monitoring: continuously checking the status of network devices and services and generating alerts when problems are detected. When a fault occurs, the first step is triage: is this a minor degradation or a critical failure? Then isolation: which device or link is causing the problem? Then resolution: fix the immediate issue. Then root cause analysis: understand why the fault occurred and what can be done to prevent it happening again. Good fault management dramatically reduces the mean time to repair and minimises the impact of failures on users.
Alex: And performance management?
Sam: Performance management involves continuously measuring key metrics: bandwidth utilisation, latency, packet loss, and error rates, and comparing them against defined thresholds. When performance degrades below acceptable levels, the management team investigates and takes action, whether that's upgrading link capacity, reconfiguring QoS settings, or troubleshooting a device that's generating excessive traffic. Proactive performance management catches degradation before it affects users.
Alex: What are Service Level Agreements and how do they relate to network management?
Sam: SLAs define the performance standards that a network or network service provider must meet. They specify things like minimum uptime percentage, maximum latency, and maximum time to resolve faults of different severities. SLAs create accountability and provide a clear framework for measuring whether the network is meeting requirements. Network management processes generate the data needed to report against SLA metrics and to identify where investment is needed to meet those commitments.
Alex: Is documentation as important in network management as in other computing disciplines?
Sam: Absolutely essential. Network documentation needs to be kept accurate and up to date at all times because it's used constantly: for troubleshooting, for planning changes, for training new staff, and for demonstrating compliance. The most important documents are topology diagrams, IP addressing plans, device configuration records, and change logs. Organisations with poor network documentation spend far more time troubleshooting and experience more prolonged outages than those with accurate, current records.
Alex: Brilliant. Thanks Sam. Next we plan and design a managed network.