Architecture

Tags:  

An Overview

The Distributed Edition of OpManager offers Internet-based, centralized remote monitoring and management of networks, systems, and applications.

A network has different devices that serve different purposes. There are again numerous applications / processes running in various devices. These applications constantly exercise load on various resources of a device such as, the disk utilization, memory utilization, etc. It is important that the health of the device as well the resources in it (that includes the applications) are constantly monitored. Achieving this by physically monitoring and testing is a mammoth effort. OpManager DE makes this task very simple. It provides an intuitive user interface that has a single point of access to various data of resources in a device. A 'resource' can be any component in a network, hardware and software. The OpManager Distributed Edition precisely monitors both!

The key features of the Solution are,

  • Offers management and monitoring of remote resources from a single console. The remote resources include devices, applications, and host resources.
  • Distributed deployment facilitating remote monitoring.
  • Out-of-the-box support for monitoring all TCP services on servers like Oracle,Web, FTP, DHCP, DNS, MySQL etc.
  • Install Probes in remote networks that perform network-facing functionality like discovery, status
    polling and data collection.
  • The Remote Probe can work behind proxy servers and firewalls.
  • Complete Fault and Performance monitoring support for all the devices distributed across the globe, from the central operating center.
  • The Communication Engine between the Probe and Central Server has a robust persistence mechanism to ensure 0% data loss even when there is a connection loss between the servers.
  • Clear data-segmentation  based on Probe and the remote sites.
  • Snmp Traps are received in the Probes and can be parsed to view meaningful alarms.
  • Ping and TraceRoute requests can be executed in the Probe, from the Central Server.

Distributed Deployment Architecture

The distributed deployment option provides a stable and scalable system.  The components that can be deployed in distribution are, Central Server and Remote Probe and if need be, you can distribute the database onto another server. . Following is the distributed deployment architecture of the product.

OpManager Distributed Edition Architecture


OpManager Distributed Edition: Solving Remote Monitoring and Management Challenges

AdventNet ManageEngine OpManager Distributed Edition (DE) is a centralized remote monitoring and management solution built to meet remote monitoring and management challenges. The highlights of this edition are:
  • Centralized resource management capabilities, offering management from a single console for all the resources distributed across the globe.

  • Out-of-the-box monitoring capability to address the remote monitoring issues with support for monitoring availability of all types of devices in a network, monitoring host resources, TCP Services, traffic in the network, applications like Exchange, MSSQL, Active Directory etc and much much more.

  • A scalable Central server/remote probe architecture that enables the IT Manager or the administrator to stretch the Probes to scale to large environments, with a flexibility to continue adding more Probes if required.

  • Automatic 'Smart' upgrade of the Remote Probes to the new service pack upgrades made to the Central Server.

The Distributed Components and their Functionality

AdventNet OpManager Distributed Edition provides an integrated and centralized network management solution for network resources distributed across the globe. Also, provides intuitive real-time display of network performance and behavior. In case it senses a degradation or failure, it automatically sends an alarm notification with the diagnostic information.

Central Server

The Central Server Back End is installed at the central site (NOC).
  • The Central Server performs the functions, such as event correlation and alarm notification of remote resources.
  • Data and Configuration are segmented and stored on a per-site and per-probe basis in the central server database to provide segmented views.

  • The Central Server Back stores the global (or complete) network management information in the central database to provide a global view of all the remote resources distributed across the globe from the central location.

Remote Probe

Remote probes are deployed in the remote locations, where the resources are to be monitored.
  • The remote probe is capable of performing comprehensive monitoring-related tasks, such as discovery, status polling, and data collection for the resources in the remote locations invoked from the client connected to the Central Server.
  • The remote probes constantly probe and transact with the resources they are monitoring at configurable time intervals to test their availability and responsiveness.
  • The remote probes collect the data from the configured resources and update the Central Server  at configured intervals. The Central Server  processes the data and stores them in a persistent database.
  • Any number of remote probes can be configured depending on the monitoring needs.
  • The remote probes also facilitate upstream tasks, such as filtering, consolidation, and propagation.
  • Communication between the Central Server and the remote probe is through XML over HTTPS. This facilitates the remote probes to function behind proxy servers and firewalls.




 RSS of this page

rtttr
rb