FCAPS
FCAPS (fault, configuration, accounting, performance and
security), the ISO model for network management, is a functional approach that
segments management areas into discrete categories, which allows the network
manager or management framework to address each in turn and ensure that no area
is overlooked. FCAPS is a model, not a product. Many network management
applications and designs adopt FCAPS, and internally developed procedures and
tools can also be architected along these lines. Even if your management
product, framework, or application does not mention FCAPS, the five areas
covered by this model are probably addressed. If they are not, then there is
value in identifying the gaps in your management strategies. FCAPS is therefore
useful to assist the network manager in ensuring that a structured,
methodological approach is taken to network management and that haphazard or
reactive management techniques and strategies are avoided.
FCAPS was born "in the wired world" of centrally managed
environments. As mentioned earlier, wireless networks present many unique
challenges. Chief among these is the dynamic nature of the transport medium. So
although FCAPS is a useful tool, or indeed a useful mindset, with which to
approach wireless network management, you must ensure that it is either updated
or enhanced to include the distinct aspects of the wireless environment or only
used as a tool to help guide your management strategies.
The next sections briefly examine the five functional areas of
FCAPS and its shortcomings.
Fault Management
In this area, service-impacting events are identified and
resolved. The network is monitored for problems, and when identified, they are
isolated and corrected. This functional area keeps the network running. Downtime
is minimized, and the network is kept operational. Fault management is perhaps
the most well-known area of network management.
Configuration
Management
Within the configuration management functional area, the
network is monitored, the status or design is maintained, and any changes to
network components are carefully planned, recorded, managed, and performed.
Subjects such as the IP addressing scheme, routing tables, wireless VLAN and
Service Set Identifier (SSID) assignment, and information on the physical
devices and their logical layout are handled in the configuration management
area. Moves, adds, and changes are also dealt with here because they affect the
configuration of the network. Reporting on planned and past changes forms part of this
functional area.
Accounting
Management
Accounting management is focused on the user and is the domain
where data about network usage is collected, collated, reported, and then acted
upon. The gathering of statistics allows the network manager to monitor usage,
detect inefficiencies, bill users or groups for access (if applicable), and
produce trending reports to assist in proactive design and reconfiguration.
Accounting management allows you to monitor the actions of users, make better
use of the available resources, and plan accordingly for improvements. Reporting
on historical use, called trend reporting, is an
important facet of this functional area.
Performance
Management
Performance management is similar to accounting management in
that you collect data from the network, but you monitor the physical equipment
and medium rather than users. In the performance management functional area, you
collect data on network resource utilization, set thresholds for reporting and
alerting, and make changes to fine-tune the network. Performance management can
be as simple as monitoring CPU or network interface utilization or as complex as
full end-to-end application monitoring. The concept is simple, however: Monitor
the network, identify problems or chokepoints, and fine-tune the environment.
Security
Management
The security management functional area of FCAPS defines the process and procedures for network
security. The network is monitored for compliance to the
security posture, risks are identified, events are logged, and audit trails are
created.
Where FCAPS Fails
FCAPS addresses management in the traditional environment,
which typically means a wired network with a clearly defined hierarchical
architecture, static endpoints and deterministic behavior. Unlike WLANs,
relatively few external factors can affect a wired environment.
Wireless networks, on the other hand, are subject to many
outside factors, and the endpoints (that is, the wireless client devices) are
mobile in nature. They can change their location, their IP address, and even the
status of their connectivity (online versus offline) on a regular basis in the
dynamic radio environment. The dynamic nature of clients' connectivity often
does not represent a fault. Because of the lack of any specific client
management area in the FCAPS model and the fluid nondeterministic nature of
WLANs in general, FCAPS should not be considered a comprehensive system for
wireless management. Instead, FCAPS is useful in helping you focus on the
traditional areas that require attention. It can be considered a subset
of a robust enterprise-class wireless network management framework. FCAPS is a useful tool, but you should
not use it as the sole method for conceptualizing and even designing your
management toolset.
Sections
