AI, and Network Operations and Management · Topic 3 of 6
Network Management Approaches
Compare device based, cloud based, controller based and automation based network management, and learn what infrastructure as code means for a network.
- 6 min
- Device based means configuring each device directly, usually by CLI.
- Controller based means central policy pushed to devices, as with Catalyst Center.
- Cloud based means a provider hosted platform managing devices, as with Meraki.
What it is
A network management approach is the way you configure, monitor and change a network. Five approaches appear in the objective, and they build on each other.
At one end, an engineer types commands on each device. At the other end, the whole network is described in text files and a tool makes the network match them. Most real networks use a mix, so the skill is to recognize each approach and know what it is good at.
How it works
Each approach changes where the configuration lives and who applies it.
The order above is a guide to how management has grown. It does not mean one approach replaces another.
Device based management
In device based management, an engineer connects to each device and configures it directly, usually through the CLI over SSH or the console. Each device holds its own configuration.
It is simple, needs no extra platform and gives full control. It is slow and error prone at scale, because every change is typed again on every device, and settings can slowly drift apart between devices.
R1# configure terminal
R1(config)# interface GigabitEthernet0/1
R1(config-if)# description Link to R2
SNMP and syslog, covered in later pages, are device based tools in the sense that each device is queried or reports on its own.
Controller based management
In controller based management, a central system called a controller holds the policy and configuration for many devices. The engineer works in the controller, and the controller pushes the result to the devices.
Examples are Cisco Catalyst Center for campus networks and wireless LAN controllers for access points. The controller gives one view of the whole network, consistent settings and analytics. It becomes an important system that must be protected and kept available.
Cloud based management
In cloud based management, the management platform runs in a provider's cloud and the devices connect out to it. Cisco Meraki is the well known example. The engineer uses a web dashboard, and the cloud platform configures and monitors the devices at every site.
It removes the need to run your own management server and suits many small sites. The devices need a working connection to the cloud to be managed, although traffic normally keeps flowing if that connection is lost.
Automation based management
In automation based management, software carries out tasks that an engineer would otherwise do by hand. A script or tool connects to many devices, runs the same commands or applies the same template, and collects the results.
Ansible is an example, and it has its own page. The benefits are speed, consistency and fewer typing mistakes. The risk is that a mistake is also applied everywhere at once, so testing matters.
Infrastructure as code
Infrastructure as code (IaC) is the idea of describing the network as text files, which are stored, reviewed and applied by a tool.
- The files describe the desired state, not a list of steps typed by hand.
- The files are kept in version control, such as Git, so every change has an author, a time and a way back.
- Changes are reviewed before they are applied, like software changes.
- A tool applies the files, and running them again is safe because the result is the same.
The files become the source of truth. If a device differs from them, the device is the one that is wrong, and the tool can bring it back. This reduces configuration drift.
Comparing the approaches
| Approach | Where the configuration lives | Who applies it | Strength | Weakness |
|---|---|---|---|---|
| Device based | On each device | Engineer, one device at a time | Simple, direct | Slow, inconsistent at scale |
| Controller based | In the controller | Controller, to its devices | One view, central policy | Controller must be protected |
| Cloud based | In the provider's cloud | Cloud platform, to its devices | No local server, many sites | Needs cloud connectivity |
| Automation based | In scripts and templates | A tool, on many devices | Fast and repeatable | Spreads mistakes quickly |
| Infrastructure as code | In files under version control | A tool, from the files | Reviewable, traceable, repeatable | Needs skills and discipline |
Match the clue to the approach. A web dashboard in the vendor's cloud means cloud based. One system pushing policy to many devices on your own network means controller based. Files in Git means infrastructure as code.
How the approaches combine
A company might use a controller for campus switching, a cloud dashboard for small branches and Ansible for the rest. The CLI never disappears, because it is still the tool for troubleshooting.
Common mistakes
Calling every central system a controller. A cloud managed platform and an on premises controller are different approaches, even if both use a dashboard.
Treating automation and infrastructure as code as the same thing. Automation is doing tasks by software. Infrastructure as code adds desired state in files, version control and review.
Assuming a cloud or controller outage stops traffic. Usually it stops changes and visibility, not forwarding.
Thinking the CLI is obsolete. It remains the tool for troubleshooting and for devices that no platform manages.
Automating without testing. A faulty template reaches every device at once.
Automation is just as fast at spreading a bad change as a good one. Test and keep a rollback plan.
What to remember for the exam
- Device based means configuring each device directly, usually by CLI.
- Controller based means central policy pushed to devices, as with Catalyst Center.
- Cloud based means a provider hosted platform managing devices, as with Meraki.
- Automation based means software, such as Ansible, runs tasks on many devices.
- Infrastructure as code describes the network as files, kept in version control and applied by a tool.
- Desired state means the files say what the result must be, not the steps.
- Version control gives history, review and rollback.
- Most networks mix approaches.
Check yourself
What is the main drawback of device based management at scale?
Every change must be made on every device by hand, which is slow and leads to mistakes and configuration drift.
How do cloud based and controller based management differ in where the platform runs?
A cloud based platform runs in the provider's cloud and is reached through a web dashboard, while a controller runs as a central system for the network, often on your own premises.
What makes infrastructure as code more than simple automation?
The network is described as desired state in files held in version control, reviewed before use and applied by a tool, so the files act as the source of truth.
Topic 3 of 6 in AI, and Network Operations and Management
Test yourself on AI, and Network Operations and Management
The full Cisco CCNA 200-301 v2.0 question bank has 1,242 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Cisco. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.