UNIX and Linux System Properties (Operations)

The following table describes the properties displayed for a managed UNIX or Linux system. Use this table to help you interpret data when monitoring and managing these systems.

Property	Definition
Default Action	The action that is initiated when you double-click the UNIX or Linux system or press Enter while it is selected in a table or topology.
Identifier	The name of the system preceded by the names of the objects that contain it. For example, the identifier of a system in a server is <server> . <system>.
Image	The image that represents the system in a topology.
Name	The name by which the system is known within Operations Sentinel. The name is used in alerts and log files to identify the system; it is also the image label for the system in a topology.
Server	The server the system belongs to, if any.
System Type	The type of system. In this case, the value is always Unix.
Tag	A property that your site uses however it chooses. It is often used as an identifier to make filtering of managed objects easier.
Automation Mode	The property used to control automation for the system and the amount of automation information written to the SP-AMS log for the system. The value is one of the following: Normal Automation actions are performed, but are not written to the SP-AMS log. Trace Automation actions are performed and automation trace information is written to the SP-AMS log. Automation trace information includes the original message text, the identifier of the matching pattern, and all actions performed. Debug Automation actions are not performed, but all automation trace information is written to the SP-AMS log. Debug mode is used to test which automation actions would be performed without actually performing them. You can click Log Viewer on the Tools menu to view the log SP-AMS.
Console Server	Specifies the network name or IP address of the device used to remotely access the system console, such as Unisys Console Manager or another network console management device.
External Network Name	The Internet name of the system. The external network name is made available to external applications launched for the UNIX or Linux system. Typically, External Network Name is the same as the Network Name. However, these names might differ if the workstation running Operations Sentinel Console uses a different name to identify the system than the Operations Sentinel server does.
Monitor	Indicates whether the UNIX or Linux system is monitored by the Operations Sentinel server. The value is either True The system is being monitored. FalseThe system is not being monitored. Logging for the system and automation using SP-AMS are not performed. You cannot open a console window to the system unless the Monitor value is True for the system.
Network Name	The network name of the system. A UNIX or Linux system can be connected to the Operations Sentinel server in one of three ways: Directly through a serial port on the Operations Sentinel server Through a terminal/communications server Through a TELNET connection Network Name has a different significance for each. Direct connection There is not a value in the Network Name property. Terminal/communications server The Network Name is the name of the terminal/communications server which is connected to the system. TELNET The Network Name is the name of the managed system to which your TELNET connection is made. This property is empty if the system is directly connected to a serial port on the Operations Sentinel server. More than one managed system can have the same Network Name (provided their Service Names differ). This means that the same terminal/communications server is connected to each system, or that you have multiple TELNET sessions managing the same system.
Service Name	The name used to create a communication link to the system. For a connection through a terminal/communications server, the Service Name identifies the port on the terminal/communications server which is connected to the system. For a TELNET connection, the Service Name identifies the port (normally 23) on which the system's TELNET server is listening. More than one managed system can have the same Service Name (provided their Network Names differ). This is useful for TELNET connections, as generally all TELNET servers listen on port 23.
Timeout Period	The time interval between the receipt of console messages before a timeout alert is generated. Operations Sentinel can use the Timeout Period value to determine if its connection with the managed system is functional. If the timeout value is set to 0, this process is disabled. You never see a timeout alert for the system and the Operations Sentinel Server services cannot determine whether their connection to the UNIX or Linux system remains functional.
Command Security	The level of security access for the submission of commands to the system through command event reports. The value is one of the following: NoAccess All command event reports for the system are discarded. AutomationAccessCommand event reports originating in an autoaction database managed by SP-AMS or CP-AMS are allowed. All others are discarded. UnlimitedAccess Command event reports from all sources are allowed, including the Single Point Interface Pipe and client programs built using the Event Server API.
Automation State	The automation state of the system. The value is either Active SP-AMS is monitoring the system and is actively processing system messages. Inactive SP-AMS is not currently monitoring the system. *Note:* SP-AMS only monitors a system when a database is active and the system’s Monitor property is True
Connection State	The state of the connection between the Operations Sentinel server and the system. This value affects the display of the connection line to the system in topologies. The value is one of the following: Connected Operations Sentinel has successfully made a connection to the system using the information specified in the Network Name and Service Name properties.The connection line around the system in the topology is a solid green. Disconnected Operations Sentinel could not make a connection to the system using the information specified in the Network Name and Service Name properties. The connection line in a topology is red-dashed. Unmonitored Operations Sentinel is not attempting to establish a connection to the system because the Monitor property for the system is False.No connection line is drawn around the system. Unknown Operations Sentinel has no information on the state of the connection to the system. The connection line in a topology is red-dashed. If the state of the connection is Disconnected or Unknown, an alert is raised.
Console State	The operational state of the system. The value is one of the following: Active If the value of Monitor is True, the system and the connection to it are in a state where data can be exchanged. SP-AMS is processing message traffic and performing automation actions. Inactive The connection to the system has not been established or has been broken. If the value of Monitor is True, the Inactive state indicates a problem. If the value of Monitor is False, this represents a normal condition. Timeout No message traffic or heartbeat has been received from the system within the timeout period defined for that system. This can indicate a problem on the managed system, such as a system hang, console hang, or a problem with the communications required to monitor that system. Busy The Operations Sentinel server cannot connect to the managed system. For systems that are connected to the Operations Sentinel server through a terminal server, another process on the server has control of the Operations Sentinel server port and is preventing Operations Sentinel from exclusively attaching to the port. Unrecognized The configuration information needed to access the connection is incorrect or incomplete. This usually means that the Network Name or Service Name specified for the system is not known on the Operations Sentinel server. If the Connection State value is Unmonitored, the Console State value is always Unrecognized.