With the introduction of Agent-based monitoring in OpManager, users can now install a lightweight piece of software called an "agent" in their network devices such as Windows servers to aid OpManager with monitoring your devices. The agent takes over all polling actions related to that device from OpManager, allowing your OpManager server to function more efficiently. For smooth functioning of OpManager without load configuration changes, it is recommended that the agent be installed on not more than 1000 devices.
Agent monitoring feature in OpManager is available in build 125312 and above.
Before proceeding to install the agent and beginning to monitor your network devices, there are a few prerequisites that need to be addressed as follows:
These are the minimum specifications required in the device where the OpManager agent will be installed:
Parameter | Minimum requirement |
---|---|
Processor speed | 1.0 GHz |
RAM | 512 MB |
Hard disk space | 100 MB |
Supported OS versions:
The OpManager agent supports all major versions of Microsoft Windows as listed below:
To ensure smooth functioning of Agent-based monitoring in OpManager, the following ports need to be opened/available in the firewall, with respect to the device being monitored.
a. Agent - OpManager server communication
Port | Protocol | Direction | Description |
OpManager webserver port* (https) | TCP | Outbound | Used for communicating with the OpManager Server to transmit data. (8061 by default) |
b. Remote agent deployment from UI (Deploy Agent)
For remote deployment, Ports 135 and 445 should be kept open and Inbound with respect to the monitored device. Initially, port 135 is used. RPC later switches it to any random port of TCP Dynamic port range. This dynamic port range must also be opened (Inbound).
NOTE:
To start using Agent-based monitoring mode in OpManager, SSL needs to be enabled to ensure secure communication. Click here to read in detail about how you can enable SSL in OpManager.
Before beginning the installation process, make sure the OpManager webclient is reachable from the end device that you are going to install the agent in.
If any Endpoint Management solutions have been employed in your network to manage your client computers, these applications need to be added in the exclusion list to ensure the OpManager agent can run without any issues:
Usage | Source Server | Destination Server | Source Port | Destination Port | Protocol |
Agent - OpManager server communication | Agent | OpManager | Dynamic Port* | OpManager Webserver Port* (8061 by default) | TCP |
Remote deployment (via Deploy Agent option) | OpManager | Agent | Dynamic Port* | 135, 445, Dynamic Port* | TCP |
The destination Server will also send Ack(Acknowledge) using the same port.
Dynamic Port* - Refers to the TCP Dynamic port range. In order to limit or customize the port range, use the Windows netsh set dynamicport command.
Thank you for your feedback!