NETCONF (Network Configuration Protocol) is designed for configuring, modifying, deleting, and monitoring network devices using XML and Remote Procedure Call (RPC). It addresses limitations of CLI and SNMP by providing a structured, secure, and standardized approach to network management, supporting automation and big data networks. The protocol operates through a client-server architecture, facilitating various network operations such as modifying device settings and querying status.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
9 views9 pages
Iot based system
NETCONF (Network Configuration Protocol) is designed for configuring, modifying, deleting, and monitoring network devices using XML and Remote Procedure Call (RPC). It addresses limitations of CLI and SNMP by providing a structured, secure, and standardized approach to network management, supporting automation and big data networks. The protocol operates through a client-server architecture, facilitating various network operations such as modifying device settings and querying status.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9
Network Configuration Protocol
(NETCONF)
• Embedded systems & iot design
• Presented by: Muthu santhosh & Muthu eswaran What is NETCONF?
• • NETCONF = Network Configuration Protocol
• • Used to configure, modify, delete, and monitor network devices. • • Uses XML to encode data. • • Uses Remote Procedure Call (RPC) for communication. Problems with CLI and SNMP
• • CLI is vendor-specific, hard to manage.
• • SNMP supports monitoring only, not configuration. • • No transaction mechanism. • • Not secure or standardized. Advantages of NETCONF
• • Supports cloud, automation, and big data networks.
• • XML + RPC = structured, readable messages. • • Works with YANG model to reduce manual errors. • • Provides authentication and authorization for securi NETCONF Architecture • • Two roles: Client and Server • • Client: Sends RPC requests (e.g., NMS) • • Server: Network device that responds • • Also sends alarms/events back to client. NETCONF Communication Flow
• • Change IP address • • Restart network device • • Query current device status Conclusion
• • NETCONF simplifies network management.
• • Solves CLI and SNMP limitations. • • Essential for modern, automated, and secure netwo • • Acts like a universal remote for all network devices. Thank You!