OpManager Central-Probe Connectivity

OpManager enterprise edition follows a Central-Probe architecture that allows IT admins to monitor an entire distributed network from a single console.

Data transfer between a Probe and the Central

The entire data communication between a Probe and Central takes place via the push-pull mode to ensure a robust Central-Probe connectivity.


The probes present in remote sites monitor the network and send (push) the data to the Central.

In turn, the Central collects the data from all the connected probes and offers a consolidated view of the geographically distributed networks that are monitored individually by the probes.


Configuration changes done in the Central will be reflected in the Probes. Once a configuration change is made, say adding a new device template, the Probes will fetch (pull) the configuration update.

During the Probe installation process, users have to input the Central URL details in the installation shield to establish connection between the respective Probe and the Central.

Accessing device snapshot data

The device snapshot page in OpManager presents data about availability, response time, associated monitors and other relevant information particular to a monitored device.

This information on the device snapshot page is fetched via two modes.

Via Probe (Unidirectional)

When users access the snapshot page of a device, the monitoring Probe presents the data directly. As only the Probe is involved in presenting data, this is an unidirectional communication. This mode of communication exists when the Probe is not reachable from the Central or when the Probe and Central are in different networks.

Via Central - Probe (Bidirectional)

When users access the snapshot page of a device, the Central presents the data by fetching it from the respective Probe through an API request. Here, as the Central and Probe are in the same network and are capable of accessing the monitored information, the communication approach followed is bidirectional.

Generally, OpManager raises API requests to the clients and gets response from it. Users can enable or disable to make API requests through the Central server.

Settings --> General Settings --> System Settings --> Make API requests via Central server (Enable/Disable).


When this option is disabled, the API requests are made directly from the Probe and the response is received.


When this option is enabled, the API requests are made from the Central and through the Probe. Hence, when this option is enabled, the Probe-Central connectivity is essential to make API calls and receive due responses.


To ensure proper Probe-Central connectivity, the following configurations must be made:

  • The protocol used by the probe to communicate with the client device.
  • The port used by the device must be rightly mentioned in the probe.
  • If SSL Configuration is enabled the common name (CN) of the client must be mentioned rightly.
  • If it is self signed SSL, that certificate should be trusted/imported in respective browser.

Note: The 'Make API requests' via Central server option works from the OpManager build number 125201.