lass. Other applications can be notified when events are added, deleted or modified. Events can be extended if additional properties are needed beyond those pro- vided in the raw event object. 12.2.1 Event Generation Events can be generated in either of the following ways: generated from traps or autonomous messages received received from other applications via event APIs. Events will be generated when SNMP traps or TL1 autonomous messages are received by FMS. First, the raw traps will be converted into useful event objects, using filters and parsers provided by FMS. Second, the event objects will then be added to the Event Manager and stored in the event database. New event objects can be added using API methods. These events are added directly into the Event Manager and processed by event parsers and event filters before being stored in the database. The methods of the EventAPI class can be exported via RMI for remote invocation of the API methods. 12.2.2 Events and Information Flow Network notifications are messages that are sent by the agents of managed objects without any manual intervention or request from the server. These messages are sent when failures occur in the nodes. Notifications are of different types depending upon the protocol which the managed object uses to communicate with the server. Each protocol has a unique way of sending notifications. For example, the agent implementing the TL1 protocol notifies the server through "autonomous messages", which are internally processed so that events are generated accordingly. FMS is an example of a "protocol neutral" product because it supports many of the common network management protocols. 12 Fault Management NETWORK Notifications FILTERING Events CORRELATION Alerts ACTIONS e-Mail Pager Figure 12.1 Event flow. Notifications are received as raw data from the network and must be converted to a format which can be understood by console operators. Information such as whom to call, whom to page and procedures to fix the problem are made readily available t