メインコンテンツまでスキップ

1. Introduction

この節では network fault and problem management terminology の RFC 原文を保持し, Event, State, Fault, Problem, Symptom, Cause, Alert, Alarm, workflow figures, security, privacy, IANA considerations を含めます.

1.  Introduction

Successful operation of large networks depends on effective network
management. This requires a virtuous circle of network control,
network observability, network analytics, network assurance, and back
to network control. Network fault and problem management [RFC6632]
is an important aspect of network management and control solutions.
It deals with the detection, reporting, inspection, isolation,
correlation, and management of events within the network. The
intention of this document is to focus on those events that have a
negative effect on the network's ability to forward traffic according
to expected behaviors that may reduce the network's ability to
deliver services. Such events may also impact the ability to control
and operate the network. The document also considers other faults
that reduce the quality or reliability of the delivered service. The
concept of fault and problem management extends to include actions
taken to determine the causes of problems and to work toward recovery
of expected network behavior.

A number of work efforts within the IETF seek to provide components
of a fault management system, such as YANG data models or management
protocols. It is important that a common terminology be used so that
there is a clear understanding of how the elements of the management
and control solutions fit together and how faults and problems will
be handled.

This document sets out some terms that are fundamental to a common
understanding of network fault and problem management. While
"faults" and "problems" are concepts that apply at all levels of
technology in the Internet, the scope of this document is restricted
to the network layer and below; hence, this document is specifically
about "network fault and problem management." The concept of
"incidents" is also touched on in this document, where an incident
results from one or more problems and is the disruption of a network
service.

Note that some useful terms are defined in [RFC3877] and [RFC8632].
The definitions in this document are informed by those documents, but
they are not dependent on that prior work.