ive. SNMP can however be used for device polling, monitoring with Its MIB concept, It is not considered appropriate for configuration as SNMP Protocol has not been designed that way and Its cumbersome for configuration. Multivendor platform management approach is again a challenge as far as the compatibility with different vendor hardware & software. INTRODUCTION TO NETCONF The challenges that we have in today's IT Infrastructure is multivendor platform compatibility with different hardware and software versions. This adds extra complexity and cost to the existing IT environment. Lack of consistency and visibility becomes a challenge in the multivendor platform environment. SNMP (Simple network management protocol) is the standard for the monitoring & management of network devices but it was not used majorly for configuration management because of the lack of standardization among different vendors and order in which the configuration can be pushed which is again challenging. Due to the complex approach for the configuration, solution is expensive, complex & not scalable. SNMP has not been used extensively for other purposes except monitoring & polling. NETCONF is a network management protocol which defines the management operations of the networking Insfrastructure. is a IETF standard for programming of network elements. Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 NFV Practical Implementation CURRENT NETWORK MANAGEMENT ENVIRONMENT CHARACTERISTICS Lack of programmatic approach to automate the frequently used daily operational tasks. Automation challenge. Not well defined protocol structures to support full fledge management of the devices. Cost & Complexity in multivendor environment. Lack of Integration between different environments. Complete visibility of the resources. SNMP was not designed for network configuration, it was created for the management of the network devices. SNMP is not for the new DevOps Model proposed. SNMP is cumbersome for the management of config