 6. Both SNMP and CMIP offer a method for managing devices use the same definition, with other added attributes, for another which do not have SNMP or CMIP capability, via the use of similar object, greatly simplifying the management task. proxy agents. CMIP events may be confirmed or unconfirmed, whereas in SNMP all events (TRAP) are unconfirmed. One can therefore The differences between SNMP and CMIP are primarily related never be certain if the message reached its destination unless to their design aims, i.e. one providing a simple protocol and the supplementary systems, such as handshaking, are introduced. other a powerful, extendible protocol. These differences are as 10. SMFs are being defined in OSI, but no such functions are follows. available in SNMP. Some of the SMFs allow manager to manager communications, this facility being poorly im- plemented within SNMP. 1. SNMP uses a polling based management system, i.e. the man- 11. CMIP has a naming hierarchy which is based on a flexible aged devices are polled for information. CMIP (and CMOT) containment philosophy. Multiple CMIP object instances can use an event based management system, the managed devices be remotely created and deleted, and applications can manage asynchronously sending predefined information (not only alarms) of interest to the manager. This allows CMIP to be objects via names which are not tied to network addressing systems. In SNMP managed devices are named directly, via IP much more efficient than SNMP when controlling large net- addresses, and objects within these devices are named in a works, since polling would result in the generation of volumes of SNMP messages, and give problems with detection and predefined tree, so it is much more restrictive. SNMP naming also does not cover proxy agents, which is required for the response times. management of large networks, for example to enable manager SNMP over UDP has poor security capability. This means that X to manage Z through Y. it is relatively easy for anyone with a LAN analyser to 