NE that supports TL1, in most scenarios TL1 is usually hidden from user by management application. For using TL1 in daily management tasks scripting needs to be added. 6.4 Overview of CMIP (Common Management Information Protocol) The CMIP is defined as part of the X.700 series of OSI management standards. It follows the manager/agent model similar to SNMP. CMIP was developed as a replacement protocol to fix the deficiencies in SNMP. By the time CMIP work was complete, SNMP had already gained huge popularity. CMIP was a strong well- defined management protocol but the additional features of CMIP made it complex to implement and maintain. Hence vendors were not willing to switch from SNMP to CMIP and SO it did not get a wide acceptance. Unlike SNMP, CMIP uses a reli- able connection-oriented transport mechanism. It also has built-in security features of access control, authorization, and security logs. CMIP is based on an object-oriented (OO) framework and the CMIP objects support: Containment: Each object can be a repository of other objects, attributes, or combination of object and attribute. Inheritance: A class defining an object can be derived from another object. Allomorphism: Ability to interact with modules through a base set of interfaces. Some of the message interactions in CMIP are: Operation Explanation GET (Request/ This is a request from the manager to the agent to get Response) the value of a managed object instance followed by a response from agent to manager. SET (Request/ This is a request from the manager to the agent to set Response) the value of a managed object instance followed by a response from agent to manager. DELETE (Request/ This is a request from the manager to the agent to Response) delete an instance of a managed object followed by a response from agent to manager. CREATE (Request/ This is a request from the manager to the agent to Response) create an instance of a managed object followed by a response from agent to manager. Fundamentals of EMS, NMS and OSS/BSS ACTION (Request/ This 