For managed UNIX and Linux systems, information is provided to Operations Sentinel as ASCII text messages through a configured console connection, which can be any of the following:
Direct serial connection
Direct connection is not recommended when there are other options, because of limited resiliency. Switching to a secondary Operations Sentinel server requires a change in cabling.
Connection over a LAN, using a terminal/communications server
Each terminal/communications server connects to one Operations Sentinel server at a time, but the secondary Operations Sentinel server can automatically establish a connection if the primary fails.
For simultaneous connection to two servers, which provides concurrent monitoring, the console data connection from the managed system must be split to go to two terminal/communications server ports.
TELNET session
Each TELNET session connects to one Operations Sentinel server at a time. Simultaneous connection to two servers requires two TELNET sessions.
SSH session
Each SSH session connects to one Operations Sentinel server at a time. Simultaneous connection to two servers requires two SSH sessions.
Information can also come from agents running on managed UNIX and Linux systems. They can provide information through the LAN in the form of event reports. This includes any Event Server API client programs supplied by your site. See the Operations Sentinel Event Server Application Program Interface Programming Guide for more information.