SAIL System Properties

The following table describes the properties displayed in the details pane for a managed SAIL system. Use this table to interpret and enter data in the details pane.

Property	Definition
Class	Indicates the fully qualified class of the object. It is used to match events reports to the object. This property is read-only.
Instance	Indicates the fully qualified instance of the object. Used to match events reports to the object. This property is read-only.
Label	Specifies the name that identifies this managed object in a topology.
Persist	Controls whether or not this object is retained when the Operations Sentinel Services are terminated. Use the arrow in the Persist property to select True or False.
Notes	A multiline property that you may use however you choose. You can alter its value by running the SPO.MakeNote external application for the managed device.
Default Action	Indicates the external application that is initiated when you double-click the system or press Enter while it is selected in a table or topology. Use the arrow in the Default Action property to select one of the available external applications for the UNIX or Linux system or <None>. The default action is <Default>, followed by the name of default action. <None> is available as a selection and indicates no action. The list of available actions can include external applications you have defined and predefined actions supplied by Unisys. The external applications included in the selection list depend on the Object Filters you specify in the External Applications node. The default action you specify for an individual system has precedence over the default action specified for the UNIX/Linux System class.
Identifier	Specifies the name of an object preceded by the names of the objects that contain it. For example, the identifier of a system in a server is server.system. This property is read-only.
Image	Displays the image that represents the system in a topology. The default value of this property is the default specified for the UNIX/Linux System object class. To select an image different from the default, click the arrow in the Image property. The new image should be small for better performance and visibility. Regardless of the type or size you use, Operations Sentinel automatically converts the image into a 24 x 24 bitmap. You must know the location of the new image before selecting it for the Image property.
Name	Indicates 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. It is recommended that you specify a system name that matches the system's external network name. You can rename a UNIX or Linux system by editing this property. The name of the new system Must be unique; no other system defined in the Managed Objects node can have the same name. Cannot be more than 64 characters in length. Cannot contain any of the following characters: \ / : * ? " < > \| Cannot start with a period (.). After you rename a UNIX or Linux system, messages and event reports for the system are written to log files with the new name. However, any existing Operations Sentinel log files for that system are not renamed.
Server	Specifies the server the system belongs to. Use the arrow in the Server property to select a previously defined server or < None >.
Tag	A property that your site can use however you choose. You do not need to specify a Tag value when you define a UNIX or Linux system. You might want to use the Tag property as an identifier to make filtering of managed objects easier. A consistent scheme for Tag values can eliminate the need for complex filters or naming conventions. See Setting the Tag Property for an example on how to use this property.
Automation Mode	Controls automation for the system and the amount of automation information written to the SP-AMS log for the system. Use the arrow in the Automation Mode property to select 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. You can specify a network name or IP address by editing this property.
Monitor	Specifies whether the communication link between the UNIX or Linux system and the Operations Sentinel server is monitored by Operations Sentinel. Use the arrow in the Monitor property to select either True (default) The status of the connection is monitored. False The status of the connection is not monitored. Logging system messages and automation using SP-AMS are not performed. When the value is False, the connection is not monitored; however, alerts are still raised against the system. Typically you set Monitor to False if a system is switched off frequently (for example, at the end of every day), but you want to receive alerts from the system whenever it is up and running.
External Network	Name Specifies the Internet name of the system. The External Network Name is made available to external applications launched for a UNIX or Linux system. You can specify a different External Network Name by editing this property. Typically, the external network name is same as the network name of the system. However, these names might differ if the workstations running Operations Sentinel Console uses a different name to identify the system other than the Operations Sentinel server uses. The external network name must be included in the hosts file on the Operations Sentinel server, in the Domain Name Server, or in the Windows Internet Naming Service. Before you edit the External Network Name value, it is recommended that you first add or change the desired name in the hosts file on the Operations Sentinel server, in the Domain Name Server, or in the Windows Internet Naming Service.
Network Name	Specifies the Internet name of the managed UNIX or Linux system or the terminal/communications server used to connect it to the Operations Sentinel server. The network name must be included in the hosts file on the Operations Sentinel server, in the Domain Name Server, or in the Windows Internet Naming Service. Specify a Network Name only when the connection between the managed system and the Operations Sentinel server requires that Operations Sentinel Console access the LAN. This is the situation when using a TELNET or SSH connection, a terminal/communications server, or a ping monitoring interface. If the system is directly connected to a serial port on the Operations Sentinel server, do not specify a network name. You can specify a different Network Name by editing this property. The name can have a maximum of 64 characters. The first character must be a letter. The last character must be a letter or a digit. The remainder might be letters, digits, hyphens, underscores, or periods. This name is not case-sensitive. Multiple UNIX and Linux systems can have the same network name, as long as their service names differ.
Service Name	Identifies an entry in the services file that completes the definition of the communications link that Operations Sentinel uses to connect to the managed system. The service name defaults to spo_ping, which assumes you are monitoring the system using ping. If you are monitoring using any of the other methods, you must change this value. The name can consist of any sequence of characters, except a space, tab, newline, and the comment character (#). The name is case-sensitive. Multiple UNIX and Linux systems can have the same service name as long as their network names differ. This is useful for TELNET connections, since all TELNET servers generally listen on port 23. Except for spo_telnet, spo_ssh, spo_ssh1, and spo_ssh2, the service name you specify must be in the services file on the Operations Sentinel server.
Timeout Period	Defines the maximum time (in seconds) between the receipt of consecutive console messages from a UNIX or Linux system before Operations Sentinel considers that system to have timed out. The Operations Sentinel server uses the Timeout Period property to determine whether its connection with the console is functional. To ensure the Operations Sentinel server receives console messages from the system, you can use the heartbeat script provided by Operations Sentinel. The heartbeat script echoes output messages from the system at specific intervals. The script is located at data-folder: \agents\spo_heartbeat. See the Operations Sentinel Administration and Configuration Guide for more information. The Timeout Period property does not apply when using ping monitoring (that is, when you specify spo_ping as the service name). You can enter a Timeout Period value by editing this property. The default value is 0. *Note:* Zero value means this process is disabled and you will never see a timeout alert for the system.
Command Security	Specifies the level of security access for the submission of commands to the system through command event reports. Use the arrow in the Command Security property to select one of the following: NoAccess All command event reports for this system are discarded. AutomationAccess Command event reports originating in an autoaction database managed by SP-AMS and 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	Displays the automation state of the system. The value is either Active SP-AMS is connected to 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 Monitor property value is True for the system. This property is read-only.
Connection State	Displays 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 established a connection to the system. The connection line around the system in the topology is a solid green. Disconnected Operations Sentinel cannot establish a connection to the system. The connection line around the system in the 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 connection to the system. The connection line around the system in the topology is red-dashed. If the connection status is Disconnected or Unknown, an alert is raised. This property is read-only.
Policy Current	Indicates whether the version of the resource policy on the monitored system is same as the version of the policy on the Operations Sentinel server. The value is True, if the version of the policy on the monitored system matches the version of the policy on the Operations Sentinel server. Otherwise the value is False.
Policy Enabled	Indicates whether the resource monitor agent (ULRM) is using the policy to monitor the system. The value is True, if the resource monitor agent is using the policy to monitor the system. Otherwise the value is False.
Resource Policy	Indicates the name of the resource policy that is loaded on the monitored system. A resource policy dictates what resources should be monitored and the conditions under which alerts should be sent to Operations Sentinel.
Agent Version	Displays the agent level of the UNIX/Linux Resource Monitor running on the UNIX/LINUX system. If the Agent Level is "blank", either ULRM is not connected to Operations Sentinel or the version of ULRM is prior to ULRM 12.0.
Console State	Displays the operational state of the system. The value is one of the following: Active If the value of Monitor is True, the connection is in a state where data can be exchanged. Inactive The connection to the managed system has not been established or has been broken. If the value of Monitor is True, an 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 managed system within the timeout period defined for that system. This indicates 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 for the connection is not known on the Operations Sentinel server. If the Connection State value is Unmonitored, the Console State value is always Unrecognized. This property is read-only.
Agent State	Displays the agent connection state of the UNIX/Linux Resource Monitor running on the UNIX/LINUX system. The following are the possible values of the Agent State: Unknown - The agent on the managed server is not connected to Operations Sentinel. There may not be an agent on the managed server. Connected - The agent on the managed server is connected to Operations Sentinel. Disconnected - The agent connection has been lost.