1 Introduction
The operation and maintenance support in OTP consists of a generic model for management subsystems in OTP, and some components to be used in these subsystems. The model that this support is based upon is described in "OAM Principles".
This document describes one of these components, the Measurement Handler application MESH. MESH consists of functions which support, create and control measurement types and objects, and associated logs.
MESH uses the applications SASL, Mnesia, and EVA.
1.1 Architecture
MESH is designed to work as a distributed application, which means that it always executes on one node, but will be restarted on a standby node if the current node crashes. MESH should run on the same node as other operation and maintenance applications, specifically the management protocol termination application, to minimize internal network traffic.
MESH is designed to be protocol independent, and may be used with different management protocols. For each such protocol, a MESH adaptation must be written. Currently, an SNMP adaptation is included, and other adaptations (e.g., HTTP, CORBA) may follow in the future.
The Measurement Handler system can run in both server mode and in client mode. In client mode, no processes are running, but the code implementing the API is loaded. There must always be one MESH server running on a node in a network of Erlang nodes.
For MESH, all involved nodes are seen as one (distributed) system. This means for example that there is one active alarm list (in EVA) for the entire system.