red Alert: 2 IF-vasus 985943361726 IF-vasus Interface failure. Status poll failed. 14:39:22:277 PM Filtered Alert: 2 vasus 985943362066 vasus : Node failure. This probably means one or more interfaces have failed. 14:39:30:899 PM Filtered Alert: 2 IF-nns-server 985943370799 IF-nns-server : Interface failure. Status poll failed. 14:39:31:099 PM Filtered Alert: 2 nms-server 985943370979 nms-server : Node failure. This probably means one or more interfaces have failed. Figure 12.9 Log file generated is similar to plain text log files generated in other fault and alarm management software. 12 Fault Management works and how it contributes to network management OSS more generally, and how it particularly assists with fault management. We shall first review the role of the element management system and its relation- ship with higher level management systems. A network management OSS monitors the managed objects whereas a fault management system draws on this functional- ity to achieve its own aims. In the case of AdventNet's offering, the Element Management System product makes it possible to monitor specific elements in the network. The main functions performed by an NMS are to: discover objects recognise topology and condition of various devices detect network or device faults automatically send messages on encountering an Event or Alert obtain configuration information and gather performance information of various devices confirm the connectivity and reachability between the Manager and the devices being managed. The EMS is used to manage a specific set of devices or a number of devices con- nected in a network. The EMS is also used to manage different nodes such as SNMP or TL1 nodes. The EMS communicates with network devices directly using network management protocols. The functions usually expected from an EMS are to: provide common information about the NE, such as system up-time and system monitor the operational state of the NE, such as startup and shutdown monitor the occurrence of NE malfunctions gather and pr