| J. Case, M. Fedor, M. Schoffstall, and J. Davin. A Simple Network Management Protovol (SNMP). IETF Network Working Group, 1990. RFC 1157. |
....that the events it received does not indicate a failure in its corresponding device or layer, it publishes an impact event. Impact events are viewed as symptoms by their recipients. In the process of event correlation Yemanja entities may initiate database queries (in SQL [5] and or issue SNMP [4] commands to obtain configuration information. If an entity fault is isolated recovery actions may be taken. Recovery actions can include system reconfiguration which is performed by a separate Resource Manager component, or directly by Yemanja through SNMP. In addition, after isolating the ....
....a specified description. Clearing problems. Cleared problems are removed from the database and cancellation of resultant problems is initiated as described above. Note: Problem management will be described in more detail in Section 2.5. 3. Retrieving MIB object values from SNMP agents [4]. 4. Retrieving Configuration data from an SQL database. 5. Canceling events from scenarios. Events can be removed from the current scenario only or from all defined scenarios. 6. Scheduling a predicate for execution at a later time. Predicate delayed method(Delay Time, Method) delays the ....
[Article contains additional citation context not shown here]
J. Case, M. Fedor, M. Schoffstall, and J. Davin. A Simple Network Management Protovol (SNMP). IETF Network Working Group, 1990. RFC 1157.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC