IBN, NETCONF,SNMP
| Files | Last commit | Last update |
|---|---|---|
| 10 months ago |
IBN_Practice_EN_v0.1
IBN, NETCONF,SNMP Overview
Intent-Based Networking Overview
-
Intent-Based Networking (IBN) is a networking paradigm in which operators specify what the network should achieve, rather than how individual devices should be configured. The system is responsible for translating high-level intents into device-level configurations, enforcing consistency across multiple endpoints, continuously validating the outcome, and maintaining the desired network state over time.
-
This project defines a NETCONF/YANG-based Intent-Based Networking control plane with a strong focus on configuration automation, verification, monitoring, and change management in large-scale, multi-device environments.
Design Goals
- The primary goals of this framework are:
- To provide a vendor-aware but model-driven abstraction layer over device configurations using YANG models.
- To support end-to-end intent realization, including multi-device, multi-endpoint, and multi-domain changes.
- To ensure closed-loop assurance, where configuration changes are continuously verified against intent and operational state.
- To enable safe, auditable, and reversible network changes, suitable for production networks.
Core Concepts
Intent
An Intent represents the desired outcome of a network change, expressed in domain-oriented terms such as Layer 2, Layer 3, VPN, routing protocols, security, or WLAN services.
An intent specifies:
The type of change (e.g., create, update, delete, migrate)
-
The network domain and feature affected
-
The endpoints involved
-
The acceptance criteria that define success
-
Intents are declarative and do not expose device-specific configuration details.
Endpoints
Endpoints
describe the concrete network objects affected by an intent.They may represent devices, interfaces, protocols, logical objects (VLANs, VRFs, bridge domains), policies, or services.
-
Endpoints are explicitly typed and can be resolved using:
-
Direct identifiers (device IDs, interface names)
-
Structured locators (VLAN IDs, VRF names, IP addresses)
-
Dynamic selectors (tags, roles, topology-based selection)
-
This allows intents to scale from single-device operations to multi-device, topology-aware changes.
Translation and Planning
The framework translates intents into executable plans through a planning phase, which:
-
Resolves endpoints into concrete targets
-
Selects appropriate YANG modules based on device capabilities
-
Determines configuration order and dependencies
-
Generates idempotent configuration actions
-
Associates mandatory pre-checks, post-checks, and rollback strategies
This translation process is driven by registries that map intent kinds and endpoint types to YANG paths, payload templates, and verification logic.
Configuration Execution
Configuration changes are executed using NETCONF operations, including:
-
edit-config against candidate or running datastores
-
Confirmed commit and rollback-on-error mechanisms
-
Vendor-specific RPCs where required
Each action is executed within a controlled transaction context to ensure consistency and recoverability.
Verification and Assurance
Verification is an integral part of intent realization and occurs at multiple stages:
Pre-checks validate that prerequisites are met before applying changes
Post-checks confirm that the desired configuration and state have been achieved
Drift checks detect deviations from the intended state over time
Compliance checks enforce policy and operational guardrails
Verification relies on NETCONF state retrieval, operational data, and optional external probes.
Closed-Loop Operation
The system operates as a closed-loop control plane:
-
Intent is declared
-
Configuration is applied
-
Network state is verified
-
Deviations or failures are detected
-
Corrective actions or rollbacks are triggered if required
This loop ensures that the network continuously converges toward the declared intent, even in the presence of partial failures or external changes.
Change Management and Auditability
All intents and executions are tracked through a formal change lifecycle, including:
-
Draft, approval, scheduling, execution, and closure stages
-
Risk and impact assessment
-
Execution records for each action and verification step
-
Complete audit trails, including configuration diffs and evidence
This makes the framework suitable for environments with strict operational, regulatory, or compliance requirements.
Scope and Applicability
This framework is designed for:
-
Large-scale routed and switched networks
-
Multi-vendor environments with vendor-specific YANG models
-
NETCONF-capable devices
-
Scenarios requiring high reliability, controlled change windows, and continuous assurance
It does not replace device configuration models, but rather orchestrates and governs them through intent-driven automation.
Summary
In summary, this project provides a structured, extensible, and production-oriented realization of Intent-Based Networking, combining:
-
Declarative intent modeling
-
NETCONF/YANG-based configuration execution
-
Closed-loop verification and monitoring
-
Robust change management and auditability
It bridges the gap between abstract intent definitions and the operational realities of real-world network devices.