190 likes | 413 Views
CONFIGURATION MANAGEMENT. XML- Based Configuration Management for IP Network Devices by - Sharath Kumar Mallam. Purpose of Configuration Management. As the Internet continues to grow, the tasks of operations and management of IP networks and systems are becoming more difficult.
E N D
CONFIGURATION MANAGEMENT XML- Based Configuration Management for IP Network Devices by - Sharath Kumar Mallam
Purpose of Configuration Management • Asthe Internet continues to grow, the tasks of operations and management of IP networks and systems are becoming more difficult. • Efficient management techniques and tools are necessary to manage these networks
The Simple Network Management Protocol (SNMP) has been the most widely used method for network management. • monitors only fault and performance management
Limitations of SNMP • Structure of Management Information (SMI). • Limited to simple tables of scalar data types. • It does not support a hierarchical information model. • object identifier (OID).
It is difficult to support various operations • Does not support Configuration tasks • Insufficient for bulk configuration data transfers. • Retransmits important data at the SNMP engine because of unreliability
XML technology for configuration management • IETF's latest effort, Netconf (Network Configuration). • guarantees interoperability in managing devices in a multivendor environment • XML-based configuration management system (XCMS).
The features of Netconf protocol • Netconf uses an RPC paradigm • Netconf session • distinguishes between configuration data and state data • distinguish between the distribution of a configuration and the activation of configurations.
Design goals • Design goals of the Netconf protocol are as follows: 1.interoperability 2. transport-neutral protocol 3. Support actions 4. ease of implementation
2.Operation layer : Includes base and additional management operations. • a. Base Operations: <get-config>,<edit-config>, <copy-config>, <delete-config>, <kill-session>, <lock>,<unlock>,<get-all> • Netconf defines configuration datastores, configuration operations.
<running>,<start-up>,<candidate> b. Additional Management Operations <commit>,<discard-changes>,<validate> 3.RPC layer <rpc>,<rpc-reply>,<ok>,<rpc-error> 4.Transport layer Connection oriented,long-lived.
NETCONF TRANSPORT PROTOCOL • Three separate protocol bindings for transport : 1.Secure Shell (SSH) 2.SOAP over HTTP and 3.Block Extensible Exchange Protocol (BEEP)
1.Secure Shell (SSH) : Netconf uses SSH as mandatory transport protocol 2.SOAP over HTTP • Supports its own rpc interface • Client driven, synchronous • Benefits • Parameters of http session state
d.uses TLS,IPsec 4.BEEP • Initiate connection • Asynchronous
MANAGEMENT PROTOCOL • Uses SOAP over HTTP for transport • Provides RPC interface • Communicates stub and skeleton • Generates new definitions • Provides several operations <edit-config>,<get-config>, <kill-session>, <lock>, <unlock>, <get-all> <reboot>,<shutdown>,<log>
The architecture of XCMS Manager Agent SOAP Over HTTP Web browser Mgmt operations a.RPC operations Mgmt operations req • Web interfaces • XSLT b.Local operations b. RPC operations c. Local operations res XML parser XML parser File File Repository Repository Log Config urations Log Configu arations XMLDB XSL
CONCLUSION • Revolutionary approach to solve problems • Resolved issues related to configuration management of large number of network devices • Used XML technology to resolve the problem of configuration management
References • M. Warrerman and T. Goddard. "Using the NETCONF Configuration Protocol over Secure Shell (SSH)." draft-ietf-netconf-ssh-00O. ct., work in progress • T. Goddard. "NETCONF wet SOAP," draft-ietf-netconf-soap-01.,work in progress.