In network management, fault management is the set of functions that detect, isolate, and correct malfunctions in a telecommunications network, compensate for environmental changes, and include maintaining and examining error logs, accepting and acting on error detection notifications, tracing and identifying faults, carrying out sequences of diagnostics tests, correcting faults, reporting error conditions, and localizing and tracing faults by examining and manipulating database information.
When a fault or event occurs, a network component will often send a notification to the network operator using a protocol such as SNMP. An alarm is a persistent indication of a fault that clears only when the triggering condition has been resolved. A current list of problems occurring on the network component is often kept in the form of an active alarm list such as is defined in RFC 3877,the Alarm MIB. A list of cleared faults is also maintained by most network management systems.
Fault management systems may use complex filtering systems to assign alarms to severity levels. These can range in severity from debug to emergency, as in the syslog protocol. Alternatively, they could use the ITU X.733 Alarm Reporting Function's perceived severity field. This takes on values of cleared, indeterminate, critical, major, minor or warning. Note that the latest version of the syslog protocol draft under development within the IETF includes a mapping between these two different sets of severities. It is considered good practice to send a notification not only when a problem has occurred, but also when it has been resolved. The latter notification would have a severity of clear.
A fault management console allows a network administrator or system operator to monitor events from multiple systems and perform actions based on this information. Ideally, a fault management system should be able to correctly identify events and automatically take action, either launching a program or script to take corrective action, or activating notification software that allows a human to take proper intervention (i.e. send e-mail or SMS text to a mobile phone). Some notification systems also have escalation rules that will notify a chain of individuals based on availability and severity of alarm.
Other articles related to "fault management, management, fault, faults":
... There are two primary ways to perform fault management - these are active and passive ... Passive fault management is done by collecting alarms from devices (normally via SNMP) when something happens in the devices ... In this mode, the fault management system only knows if a device it is monitoring is intelligent enough to generate an error and report it to the management tool ...
... A fault is an event that has a negative significance ... The goal of fault management is to recognize, isolate, correct and log faults that occur in the network ... When a fault or event occurs, a network component will often send a notification to the network operator using either a proprietary or open protocol such as SNMP, or at least write a message ...
... was a significant advance over MFT's memory management, but had some weaknesses if a job allocated memory dynamically (as most sort programs and database management systems do), the ... controlled by CICS, which ran in a single address space—and the DB2 relational database management system needed more than 8 MB of application address space to run efficiently ... all such communications had transmit via the operating system.) MVS took a major step forward in fault-tolerance, built on the earlier STAE facility, that IBM called software recovery ...
Famous quotes containing the words management and/or fault:
“The management of fertility is one of the most important functions of adulthood.”
—Germaine Greer (b. 1939)
“Knowledge being to be had only of visible and certain truth, error is not a fault of our knowledge, but a mistake of our judgment, giving assent to that which is not true.”
—John Locke (16321704)