Conventions

Syntax

The following table lists the syntax conventions used in this document:

Convention

Description

Italic

Variables for which you must supply values; for example, internet‑address.

[ ]

Brackets enclose parts of statements (phrases) that are optional.

They are also used to identify information that applies only to specific types of systems.

{ }

Braces group similar information in which one of the values is required.

|

The vertical bar is used between two items, indicating that you can select either of the items.

It is a required part of the syntax for event reports, where it is used as a separator between attribute value pairs.

It also represents the pipe command in UNIX and Linux shell syntax.

Ctrl-key

Hold down the Ctrl key while pressing the specified key. Then release both keys.

Terms and Definitions

The variable names used in this guide and their definitions are listed below. Default values are given for these variables. If you use values that differ from these defaults, substitute that value whenever you see the variable name. x.y.z refers to the release level of Operations Sentinel.

installation-folder

The folder on the Operations Sentinel server and on each Operations Sentinel workstation where the Operations Sentinel software is installed. Default: C:\Program Files\Unisys\Operations Sentinel\x.y.z

data-folder

The folder on the Operations Sentinel server containing Operations Sentinel site-dependent data such as managed systems and consoles, zones, automation databases, alert scripts, agent filter definitions, alert policies, and help text. Default: C:\ProgramData\Unisys\Operations Sentinel\x.y.z\data

log-folder

The folder on the Operations Sentinel server that contains the logs. Default: C:\ProgramData\Unisys\Operations Sentinel\LOG

output-folder

The folder on the Operations Sentinel server and workstation that contains the output. Default: C:\ProgramData\Unisys\Operations Sentinel\x.y.z\output

SystemFolder

The Windows folder containing system information. Default: C:\WINDOWS\system32

System Types

This document contains information for monitoring and controlling several types of computer systems. The following labels, and combinations of these labels, identify information that applies only to specific types of managed systems. Information in this document not using these labels applies to all types of systems.

Label

Description

[OS 2200]

OS 2200 partitions in ClearPath Dorado Enterprise Systems

[MCP]

MCP nodes of ClearPath LX systems and FS Series systems, and MCP partitions in a ClearPath Libra Enterprise Systems

[UNIX/Linux]

UNIX and Linux (SLES12, SLES15, RHEL 7, RHEL 8, CentOS 7, and Oracle Linux7.2) systems and UNIX or Linux partitions in ClearPath Enterprise Systems.

[Windows]

Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012, Windows Server 2012 R2, Windows 11, Windows 10, Windows 10 IOT, Windows 8.1; the Windows nodes of Unisys ClearPath LX, and ClearPath NX systems; and the Windows partitions in ClearPath Enterprise Systems.

[Other]

Systems compliant with the ANSI X3.64 display protocol other than UNIX

These computer system labels can appear in headings, lists, and page headers.

Examples

In the following example, all the information in this second-level topic, including any third-level topics, applies only to Windows and MCP systems:

20.3. Using Operations Sentinel Console [Windows, MCP]

The next example shows a paragraph set apart from the rest of its block of text. The text following the label [Windows] applies only to Windows systems; the information before it applies to all types of computer systems (including Windows) because the block heading Minimum Configuration is unlabeled.

Minimum Configuration

A minimum configuration must include the following elements:

[Windows]

If you are managing a Windows system, the minimum configuration must include at least two users.

The following example shows a typical procedure in numbered steps.

Use the following procedure to

  1. Create a zone.

  2. [Windows]

    Configure alert policies.