 There is a per-UNI set of managed objects, the UNI ILMI attributes, that is suffi- cient to support the ILMI functions for each UNI. Outside the scope of this Specification Network Management Station or System Remotely Remotely Accessible Accessible Agent Agent Private Public (SNMP/AAL) (SNMP/AAL) Private Public Network End-System ATM Switch ATM Switch Public (SNMP/AAL) Figure 21.15 Definition and context of ILMI. (From ATM Forum, Figure 4-1, page 106, Ref. 7.) 21.10 NETWORK MANAGEMENT IN ATM 5. The UNI ILMI attributes are organized in a standard MIB structure; there is one UNI ILMI MIB structure instance for each UNI. 6. There is one MIB instance per ATM device, which contains one or more UNI ILMI MIB structures. This supports the need for general network management systems to have access to the information in the UNI ILMI MIB structures. 7. For any ATM device, there is a UNI Management Entity (UME) associated with each UNI that supports the ILMI functions for that UNI, including coordina- tion between the physical and ATM layer management entities associated with that UNI. 8. When two ATM devices are connected across a (point-to-point) UNI, there are two UNI management entities (UMEs) associated with the UNI, one UME for each ATM device, and two such UMEs defined as adjacent UMEs. 9. The ILMI communication takes place between adjacent ATM UMEs. 10. The ILMI communication protocol is an open management protocol (i.e., SNMP/ AAL initially). 11. A UNI management entity (UME) can access, via the ILMI communication pro- tocol, the UNI ILMI MIB information associated with its adjacent UME. 12. Separation of the MIB structure from the access methods allows for the use of multiple access methods for management information. For the ILMI function, the access method is an open management protocol (i.e., SNMP/AAL) over a well- known VPI/VCI value. For example, general network management applications [e.g., from a network management station (NMS) performing generic customer network management (CNM) functions] of the access