at the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.</descriptor> </event> <event> <objIdf>.1.3.6.1.6.3.1.1.5.2</objIdf> <eventIdf>warmStart</eventIdf> <eventLabel>SNMPv2-MIB defined trap event: warmStart</eventLabel> <description> A warmStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself such that its configuration is unaltered.</descriptor> </event> <!-- End of xml generated from MIB: SNMPv2-MIB Example 2: Output for IF-MIB <!-- Start of xml generated from MIB: IF-MIB --> <event> <objIdf>.1.3.6.1.6.3.1.1.5.3</objIdf> <eventIdf>linkDown</eventIdf> <eventLabel>IF-MIB defined trap event: linkDown</ eventLabel> <description> A linkDown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state) . This other state is indicated by the included value of ifOperStatus. </ descriptor> </event> Fundamentals of EMS, NMS and OSS/BSS <event> <objIdf>.1.3.6.1.6.3.1.1.5.4</objIdf: <eventIdf>linkUp</eventIdf> <eventLabel>IF-MIB defined trap event: linkUp </eventLabel> <description> A linkUp trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state) . This other state is indicated by the included value of ifOperStatus.</descriptor> </event> <!- End of xml generated from MIB: IF-MIB 32.6 Conclusion The intent of this chapter is to introduce the reader to the basic concepts of imple- menting NETCONF. The chapter started with a basic overview of NETCONF. Then the layers that are relevant for NETCONF application development were discussed. The chapter concludes with an implementation example for converting MIB file to XML with libsmi libra