Network management in one paragraph
Network management is the work of configuring, monitoring, securing and maintaining a company's network so that it stays available, fast and safe. The network is everything that connects your people, devices and applications: routers, switches, firewalls, Wi-Fi access points and the links between them. When it is managed well, nobody notices it. When it is not, the office loses internet, cloud applications crawl, or a badly configured device leaves a door open.
This guide is for owners, managers and non-specialist IT contacts at small and medium-sized businesses in the Netherlands. You do not need an IT team to follow it. It explains what network management covers, how it works, how it differs from monitoring, and how to choose between on-premises and cloud-based management and between doing it yourself and outsourcing.
This article was written with AI assistance.
What is network management?
Network management is the combination of tools, routines and people that keep a network working as intended. It has a few parts:
- Devices: routers, switches, firewalls, Wi-Fi access points, and often servers, printers and VoIP phones that sit on the network.
- Traffic: what flows across the network, how much, and whether important applications get the capacity they need.
- Configuration: the settings on every device, such as addresses, rules, VLANs and passwords.
- Security: who and what may connect, which traffic is allowed, and how quickly weak points are patched.
In a small business this can be one firewall, a switch and a few access points. The scope is small, but the questions are the same as in a large company: do we know what we have, is it working, is it set up correctly, and is it safe?
How does network management work?
Whether done by a person or by a network management system (NMS), the work follows the same loop:
- Discovery and inventory. The tool or engineer finds the devices on the network and records what they are, where they are and how they connect.
- Monitoring. Devices are checked regularly. Is it reachable? How busy is the link? Is a port failing? Many systems use standard protocols that devices already support to report their status.
- Alerting. When something crosses a limit or fails, someone is notified. Good alerting separates a real problem from noise.
- Configuration changes. Settings are changed in a controlled way, ideally with a record of who changed what and a stored copy of the previous version.
- Reporting. Reports show trends, such as growing traffic or a device that keeps failing, so you can plan before something breaks.
What kinds of devices can a network management system control?
That depends on the product and on what the devices support, so check before you buy. In general, network management covers core equipment: routers, switches, firewalls and wireless access points. Many setups also watch servers, storage, printers and other connected equipment, usually read-only. Be careful with any claim of "controls everything" and ask for a list of supported device types.
The five functions: fault, configuration, accounting, performance and security
A well-known way to organise the work is the FCAPS model, which splits network management into five functional areas. The examples below are illustrative, not real cases.
Fault management
Detecting, locating and fixing problems. Illustrative example: a switch in the back office stops responding. You are alerted, see which devices are affected, and fix or replace it, ideally before staff call in.
Configuration management
Keeping track of device settings and changing them safely. Illustrative example: a new access point is added in a meeting room. It gets the standard settings and the change is recorded. If it causes trouble, you can roll back.
Accounting management
Knowing who or what uses network resources. In an SMB this is less about billing and more about usage and access. Illustrative example: you notice guest Wi-Fi takes a large share of the office connection and decide to limit it.
Performance management
Measuring how well the network performs and keeping it fast enough. Illustrative example: video calls stutter every afternoon. Performance data shows a link is saturated at that time, so you adjust priorities or upgrade the connection.
Security management
Controlling access and protecting the network. Illustrative example: a firewall rule left open for a former supplier is found and closed in a regular review. No set-up can guarantee that attacks are prevented, but regular security management reduces the number of easy openings.
Network management versus network monitoring
Monitoring is one part of management. It means watching the network and raising alerts: is a device up, is a link busy, is something failing. Management includes that, and also configuration, security updates, documentation, change control and planning improvements.
Proactive versus reactive
Reactive work starts when someone complains: the internet is down, the printer is unreachable, calls are choppy. Proactive monitoring looks for early signs instead, such as a link that is often nearly full, a device that keeps rebooting, or a certificate or licence about to expire. It cannot prevent every outage, but it often turns a surprise into a planned fix, and it gives the engineer a head start when something does break.
Monitoring without management only tells you there is a problem. Management is what makes sure someone owns the fix and the follow-up.
The OSI layers L1 to L4 and troubleshooting
The OSI model describes networking in layers. The first four are enough for most day-to-day troubleshooting, and working through them in order avoids guessing.
- L1, physical: cables, ports, power, Wi-Fi signal. Is it plugged in, and is the link light on?
- L2, data link: switching within the local network, VLANs and MAC addresses. Can devices on the same network see each other?
- L3, network: IP addressing and routing. Does the device have the right address, and can traffic reach other networks and the internet?
- L4, transport: ports and sessions, such as TCP and UDP. Is a firewall rule blocking the port an application needs?
Illustrative example: a colleague cannot reach a cloud application. You check the cable or Wi-Fi (L1), whether others on the same switch are fine (L2), whether the device has a valid address and route (L3), and finally whether the needed port is allowed (L4). Starting at the bottom often finds simple causes quickly.
On-premises vs cloud-based network management
| Aspect | On-premises | Cloud-based |
|---|---|---|
| Control | Full control over the system and where data is kept | Less direct control; you rely on the provider's platform |
| Effort | You install, update and maintain the management system | The provider runs the platform; less upkeep for you |
| Scalability | Adding sites or devices may need more hardware and set-up | Usually easier to add sites and devices |
| Dependence on a provider | Lower for the system itself, but you need your own skills | Higher; check what happens if the service is unavailable |
| Fit for a small business | Can suit special requirements or isolated networks | Often a practical fit when there is no IT team |
Benefits of network management for an SMB
Stated plainly, without promises of exact results:
- Availability: problems are found and fixed sooner, and planned maintenance replaces many surprise outages.
- Security: devices are kept up to date, settings are consistent and old access is removed.
- Visibility: you know what is on your network and how it is used, instead of finding out during a crisis.
- Planning: trend data helps you decide when to upgrade a connection, replace ageing equipment or add Wi-Fi coverage.
- Less disruption for staff: people can keep working on the cloud applications they depend on.
Do it in-house or outsource? A practical checklist
Many small businesses have someone who does the IT next to their real job. That can work for a simple office, but it becomes fragile when that person is away, leaves, or the network grows.
Self-assessment
- Do we have a current list of all network devices, with models, locations and firmware versions?
- Would we know within minutes if the internet or a key switch failed?
- Who is responsible when something breaks in the evening or during holidays?
- Are device settings backed up, and could we restore a failed firewall quickly?
- Does anyone regularly review firewall rules, Wi-Fi access and admin accounts?
- Can more than one person handle the network?
If you answered no to several, consider outsourcing at least part of the work.
What to document either way
- A device inventory with serial numbers, locations and support or licence end dates.
- A simple network diagram.
- Admin accounts and who holds them, stored securely.
- Configuration backups.
- An escalation path: who is called first, who next, and how to reach your provider or internet supplier.
What to ask a provider
- Which devices and locations are covered, and what is not?
- Is monitoring proactive, and who responds to alerts, when and how?
- How are configuration changes requested, approved and recorded?
- How are updates and firewall reviews handled?
- Who will we speak to, and how do we reach them when it is urgent?
- What does the agreement say about response and resolution, in writing?
- What do we receive at the end of the contract: documentation, configurations and access?
Outsourcing makes most sense when you want reliability and security but do not want to build a team for it. A good partner explains things plainly and tells you what they do and what stays with you.
Frequently asked questions
What do you mean by network management?
It is the work of configuring, monitoring, securing and maintaining a company's network so it stays available, fast and safe.
What is the difference between network management and network monitoring?
Monitoring means watching the network and raising alerts. Management includes monitoring, but also configuration, security, updates, documentation and improvements.
What are the five functional areas?
Fault, configuration, accounting, performance and security management, together known as FCAPS.
Is cloud-based or on-premises management better for a small business?
Cloud-based management often suits businesses without an IT team because the provider runs the platform. On-premises can suit special requirements. See the comparison table above for the trade-offs.
Why do OSI layers L1 to L4 matter?
They give a fixed order for troubleshooting: physical connection, local switching, addressing and routing, then ports and sessions.
When does it make sense to outsource network management?
When you depend on the network but lack time, backup staff or expertise to monitor and secure it, or when one person holds all the knowledge.
Talk to us about your network
Jouw Cloud is a managed IT and cloud provider for small and medium-sized businesses in the Netherlands, and offers network management as a service. We work proactively, with personal and direct support, as one partner for cloud, Microsoft 365, security and support. Not sure what your network needs? Tell us about your setup and we will give practical advice without unnecessary complexity. Read about our Management & Monitoring service, where you can use the contact form or call us, see Cloud & Hosting, or visit
This article was written with the help of AI.