12.1 Remote Monitoring Using Web NMS RME



 

Distributed Mediation Server : An Introduction

 

Distribution of the network-facing functions is key to management of carrier-class and geographically distributed networks. This also makes network management efficient and scalable, enabling the central site to focus on the analysis of the collected network statistics.

 

Distributed Mediation Servers (DMS) are servers that can be deployed along with central Web NMS Server in large scale or remotely distributed networks. Each Distributed Mediation Server performs network-facing functions for a segment of the network. The collected data can then be correlated to transfer relevant information to the central Web NMS Server. Thus compared to a centralized data collection, deployment with Distributed Mediation Servers builds a scalable and highly available system.

 

Distributed Scenarios

 

Distribution is effective in providing scalability and remote management capabilities to management applications (EMS/NMS). The following sections describe both these :

 

The Distributed Mediation Server can also be used by OEMs and equipment manufacturers to provide scalable remote management capability to their Element Management Systems by deploying the DMS in the distributed environments.

 

Components in  Distributed Setup

 

When deploying Web NMS using Distributed Mediation Servers, the following components are deployed:

 

Component

Description

Central Server

The Central server is a logical server and is made up of two servers, namely, the back-end server and the front-end server.

  • Front-end Server : These are the servers to which the clients and the Distributed Mediation Servers connect. A scalable architecture enables multiple front-end servers for load distribution and high availability. The number of front-end servers depend on the planned performance and scalability metrics. The front-end servers are physically at the central site.

  • Back-end Server : The back-end server stores all network data in a centralized database and processes requests from clients through the front-end servers. The back-end server is physically at the central site

The front-end and back-end servers can be on the same or different machines depending on the need for scalability and expected system performance.

Distributed Mediation Server

The Distributed Mediation Server performs the network-facing functionality, such as discovery, status poll, traps reception, collection of performance, and other data from the network in which it is deployed. The collected data are stored in a local database and correlated by the Distributed Mediation Server. This ensures that only summary and critical data are sent to the central Web NMS Server. The Distributed Mediation Server uses a secure and fail-proof transport mechanism to transfer the data to the Central Web NMS Server.

User Interface

The following types of user interfaces are available:

 

  • Standalone Application Client: This can be installed separately. The standalone application client connects to the Central server through proper authentication.

  • Read-only WebClient: The DMS has a read-only WebClient. You can connect to the DMS server at the specified port to view the data available in the DMS database.  

 

 

Salient Features of Distributed Mediation Setup

 

The following are some of the salient features of the Distributed Mediation Server:



Copyright © 1996-2004, AdventNet Inc. All Rights Reserved.