ieval and handling of information in the ILMI MIB. The ILMI has been deployed by some vendors to perform management tasks across the UNI for some devices. However, since the ILMI provides a solution that is applicable only at the UNI, it cannot support the management tasks that are involved in a network comprising a range of ATM devices. Thus, on its own, the ILMI does not provide the capability to manage multi-vendor ATM networks. 3.3.2 M3 Customer Network Management Interface The M3 MIB defines objects for the customer portion of a public network. The M3 interface, also known as the Customer Network Management (CNM) interface, defines the interaction between the customer and carrier management systems in Table 3.4 Structure of the ILMI MIB. Group Parameters Address group Address of terminator Network prefix group ATM address prefix Virtual path connection group Status, traffic descriptors, service parameters Virtual connection group Status, traffic descriptors, service parameters ATM-layer statistics group Total cells transmitted, total cells received, total cells dropped ATM-layer group Number of VPCs, maximum number of VPCs, number of VCs, maximum number of VCs Physical-layer group Port type, media type 3 ATM Network Management - The ATM Forum Model order to give the customer a view into the carrier's network. Ultimately, carriers plan to extend their CNM offerings to give network managers real-time control over the device services that they use. The most common uses of CNM for ATM networks are testing, receiving event notifications, defining traps, administering and generat- ing trouble reports, supporting security features, and retrieving information on configuration, usage and performance from the M3 MIB. CNM applications exemplify the classical manager/agent model. A CNM applica- tion acts as a manager that communicates with a CNM agent residing in an ATM network. The CNM agent is capable of supplying the required management infor- mation and carrying out management tasks related to the managed resources.