FCAPS
From Wikipedia, the free encyclopedia
FCAPS is the ISO Telecommunications Management Network model and framework for network management. FCAPS is an acronym for Fault, Configuration, Accounting, Performance, Security which are the management categories into which the ISO model defines network management tasks. In non-billing organizations Accounting is sometimes replaced with Administration.
The comprehensive management of an organization's information technology (IT) infrastructure is a fundamental requirement. Employees and customers rely on IT services where availability and performance are mandated, and problems can be quickly identified and resolved. Mean time to repair (MTTR) must be as short as possible to avoid system downtimes where a loss of revenue or lives is possible.
Contents |
[edit] History
In 1996 the ITU-T introduced M.3010 which introduced the Telecommunications Management Network (TMN) framework for carriers to manage their service delivery networks. In 1997 M.3400 introduced FCAPS. The ISO applied FCAPS to data networks in the OSI Network Management Model.[citation needed]
[edit] Fault Management
A fault is an event which has a negative significance. The goal of fault management is to recognize, isolate, correct and log faults that occur in the network. Furthermore, it uses trend analyses to predict errors so that the network is always available. This can be established by monitoring different things for abnormal behavior.
When a fault or event occurs, a network component will often send a notification to the network operator using a proprietary or open protocol such as SNMP, or at least write a message to its console for a console server to catch and log/page. This notification is supposed to trigger automatic, or manual activities. E.g. the gathering of more data to identify the nature and severity of the problem or to bring backup equipment on-line.
Fault logs are one input used to compile statistics to determine the provided service level of individual network elements, as well as sub-networks or the whole network. They are also used to determine apparently fragile network components which require further attention.
The leading Fault Management systems are HP OpenView, IBM, Micromuse Netcool, Clarity etc.. Fault Isolation tools like Delphi are also available which are basically used to isolate the fault in any telcom network.
[edit] Configuration Management
The goals of configuration management include:
- to gather and store configurations from network devices ( this can be done locally or remotely).
- to simplify the configuration of the device
- to track changes which are made to the configuration
- to configure ('provision') circuits or paths through non-switched networks
As networks increase in size, an important task is automated configuration. Some examples of this task are DNS name<->address mappings, RANCID config change history, Cfengine managed files, RCS version control.
The leading Configuration Management systems are Cramer and Metasolv.
[edit] Accounting Management
Accounting is often referred to as billing management. The goal is to gather usage statistics for users.
Using the statistics the users can be billed and usage quota can be enforced.
Examples:
- Disk usage
- Link utilization
- CPU time
RADIUS, TACACS and DIAMETER are examples of protocols commonly used for accounting.
For non-billed networks, 'Administration' replaces 'Accounting'. The goals of Administration is to administer the set of authorized users, by establishing users, passwords and permissions; and to administer the operations of the equipment such as by performing software backup and synchronization.
[edit] Performance Management
Performance management enables the manager to prepare the network for the future, as well as to determine the efficiency of the current network, e.g. in relation to the investments done to set it up. The network performance addresses the throughput, percentage utilization, error rates and response times areas.
By collecting and analysing performance data, the network health can be monitored. Trends can indicate capacity or reliability issues before they become service affecting.
Performance thresholds can be set in order to trigger an alarm. The alarm would be handled by the normal fault management process (see above). Alarms vary depending upon the severity.
[edit] Security Management
Security Management is the process of controlling access to assets in the network. Data security can be achieved mainly with authentication and encryption. Authorization to it configured with OS and DBMS access control settings.
[edit] Other models
Other models for network management are available. One example is the ITIL model.
[edit] External links
[edit] References
- Burke Richard, 2004, "Network Management. Concepts and Practice: A Hands-on Approach", Pearson Education, Inc.
- ITU-T, 1996, "M.3010 Principles for a telecommunications management network"
- ITU-T, 1997, "M.3400 TMN management functions"
