\chapter{Future network management}
\label{ch:future}

New technologies, management models, and visions of future network management, that are currently under development, are described in this chapter. Section~\ref{sec:xopen} presents Open Group's X/Open Systems Management Reference Model. Web-based network management is discussed in section~\ref{sec:webbased}, and Java Management API in section~\ref{sec:jmapi}. Section~\ref{sec:corba} presents CORBA-based management, and section~\ref{sec:spin} SPIN's vision on network management. Finally, section~\ref{sec:policy} discusses Policy-based network management.

\section{X/Open Systems Management Reference Model}
\label{sec:xopen}

Open Group, a vendor-neutral international consortium for buyers and suppliers, has presented an \textit{X/Open Systems Management Reference Model}. It's goals are~\cite{a18}:
\begin{itemize}
\item to identify the crucial aspects of the distributed systems management problem space, especially those that are unique to this topic,
\item to establish common terminology, and
\item to establish a problem-oriented approach to the realization of distributed systems management solutions.
\end{itemize}

The reference model describes concepts necessary to build a comprehensive distributed systems management environment. It identifies the mapping between the abstract concepts and some technologies that provide suitable implementation bases for the realization of the model. The model is intended to enable a network of heterogeneous systems to be managed as a single system~\cite{a18}.

The X/Open Systems Management Reference Model uses object-oriented techniques in the specification of systems management. These techniques are derived from those used in the OSI Management Model, as well as the Object Management Group Common Object Request Broker Architecture (CORBA).

The Reference Model consists of three basic components: 
\begin{itemize}
\item\textbf{Managers}, which implement Management Tasks and other composite management functions,
\item\textbf{Managed Objects}, which encapsulate the resources, and
\item\textbf{Services}, which provide the X/Open Systems Management Support Environment.
\end{itemize}



\subsection{Anticipated implementation technologies}

It is anticipated that the primary vehicle for implementation of the Reference Model will be the Object Management Group's Object Request Broker (ORB) technology.
% At the time of writing some major issues relating to the practical implementation of ORB based management systems are still to be resolved, particularly those relating to the interoperability of different ORB implementations.
Another significant implementation technology is that embodied by the ISO/CCITT and Internet management protocols, CMIP and SNMP. The X/Open Management Protocols API (XMP) provides a uniform access method to these technologies~\cite{a18}. 

In addition to the above, which represent the anticipated future development of distributed systems management, the Reference Model can also be implemented using currently available technologies. These include those based on existing Remote Procedure Call (RPC) technologies, such as ONC NIS and DCE RPC~\cite{a18}.





\section{Web-based network management}
\label{sec:webbased}

Doing network management operations using Internet/intranet
technologies is called Web-based Network Management.  Web-based
Network management comprises controlling network systems and / or data
gathering, delivery of network management tasks and data analysis.

Basic applications of web based network management are web-based
configuration and management of individual devices, advanced network
wide management capabilities and web reporting of network status
information.

For network element configuration with a WWW browser, a management
agent with a HTML interface must be used.  The HTML agent may
configure the element using WWW forms and give reports as WWW pages.

Advanced network wide management capabilities seem to offer a WWW
interface for traditional network management tools.  Web reporting of
network status means reporting statistics and query information of
network elements on Intranet pages.

A pro for web based network management is the ability to use cheap
hardware and software for user interfaces; the personnel may move
physically and use the web interface for network management.  However,
it seems that web based network management mainly is a user interface
improvement and does not add significantly to the actual network
management.




\section{Java Management API}
\label{jmapi}
\label{sec:jmapi}

Java Management API (JMAPI)~\cite{a3} is intended to provide a standard
interface between different computers and network devices.  The system
can be used by Java programmers, and is created in alliance with Sun
Microsystems, Bullsoft, Computer Associates, Exide Electronics, Jyra,
Lumos Technologies, TIBCO, and Tivoli.  Currently, only specification
version 0.8 is available.  Specification version 2.0 was intended for
publication in March 1999.




\section{CORBA-based Telecommunication Network Management System}
\label{sec:corba}

The Object Management Group (OMG) is a non-profit international trade
association. OMG has presented an outline of an architecture for a
CORBA-based Telecommunications Network Management System. One of the
objectives of this architecture is to ensure a complete compatibility
with proprietary, ITU-T/ISO, SNMP and CORBA based network
elements~\cite{a19}.

CORBA (Common Object Request Broker Architecture) is an architecture
that supports the distribution of management functionality and managed
objects~\cite{a18}.


\subsection{Inter-networking between CORBA and TMN systems}

In the context of TMN, CORBA is seen to offer potential in two
significant areas: in the description and implementation of management
interfaces supported by network devices, and in the description and
implementation of interfaces within and between management operations
systems~\cite{a19}.



\section{Common Information Model}

Common Information Model (CIM) is a common data model developed by
Distributed Management Task Force, Inc. It is implementation-neutral
and can be used to describe management information in a
network/enterprise environment. The model is intended to enable
interchange of management information between management systems and
applications, thus providing for distributed network
management~\cite{a54,a55}.

CIM is currently supported by at least Microsoft (Windows NT/98),
Hewlett-Packard (HP OpenView), and IBM (Tivoli)\footnote{See
ch.~\ref{ch:commercial} for commercial network management products.}.



\section{SPIN's Intelligent Network Management}
\label{sec:spin}

SPIN is a research project in the Institute for Information Technology
at Canada's National Research Council~\cite{a9}.  The SPIN
Intelligent Network Management project studies and develops new
agent-based technologies for controlling, planning and problem
definition of heterogeneous networks.  The application development of
SPIN networks uses integration of the off-the-self NM components, and
testing and usage of popular tools, such as HP Openview.


\section{Policy-Based Networking}
\label{sec:policy}

Policy is a combination of rules and services where rules define the
criteria of resource access and usage. Policies can contain other
policies, they allow to build complex policies from a set of simpler
policies, so they are easier to manage. They also enable to reuse
previously built policy blocks~\cite{b34}.

Policy groups and rules can be classified by their purpose~\cite{b35}:

\begin{itemize}
\item Service Policies 
\item Usage Policies
\item Security Policies
\item Motivational Policies
\item Configuration Policies
\item Installation Policies
\item Error and Event Policies
\end{itemize}

Service policies describe services available in the network. These
services will be available for usage policies. For example, QoS
service classes (Voice-Transport, Video-Transport, ..)  are made by
using Service policies.

Usage policies describe how to allocate the services defined by
Service policies. Usage Policies control the selection and
configuration of entities based on specific usage data. For example
Usage Policies can modify or re-apply Configuration Policies.

Security Policies identify client, permit or deny access to resources,
select and apply appropriate authentication mechanisms, and perform
accounting and audit of resources.

Motivational Policies describe how a policy's goal is
accomplished. For example the scheduling of file backup based on
activity of writing onto disk is a kind of Motivational Policies.


Configuration Policies define the default setup of a managed entity,
for example the setup of the network forwarding service or the
network-hosted print queue.
 
Installation Policies define what can be put on the system, as well as
the configuration of the mechanisms that perform the
installation. Typical installation policies are administrative
permissions, and they can also describe dependencies between different
components.

Error and Event Policies. For example, if a device fails between 8am
and 5pm, call the system administrator, else call the
Help-Desk~\cite{b35}.


Policy-Based Networking (PBN) is gaining a wider acceptance in the IP
management, because it makes possible more unified control and
management in complex IP network~\cite{b36}.







