Images and connection lines appear in different colors, depending on the state of the connection and the state of the system or console. Operations Sentinel is represented by one or more white horizontal line segments. The connection of each system to Operations Sentinel, except OS 2200, is indicated by a colored, vertical line from the Operations Sentinel line to the image representing the system. Each color represents a different connection state, as described below. For each OS 2200 system, there is a vertical line to each of its consoles, and a colored, vertical line from each console to the Operations Sentinel line.
Connection State Lines
A solid green line indicates an active connection.
A dotted blue line indicates an unmonitored connection, for example, when the Monitor property is set to false.
A dashed red line indicates an inactive connection. The failure of a software component or a failure in communications between the system and the Operations Sentinel server can cause the connection to be lost.
An image in a topology might be unconnected from all other images in a topology for one or more of the following reasons:
For arbitrary systems
Operations Sentinel does not support an architected interface to the system.
Terminal emulation access only is defined for that system, which might be any arbitrary system for which monitoring is not fully integrated with Operations Sentinel.
The system is only being monitored by application software external to Operations Sentinel. User-supplied external software can raise alerts using the spo_event command, the Single Point Interface Pipe (spo_pipe), or an Event Server API client that causes the unconnected system image to change color in a topology. The Operations Sentinel Trap Service can receive SNMP traps from many sources and translate these traps into alert event reports.
For OS 2200 systems, you failed to associate a console with an OS 2200 system. If you do not specify a console, the OS 2200 system is displayed as an unconnected system.