Novell SENTINEL 6.1 SP2, User Manual, Page: 291 / 528

Utilities
13
291
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
13
Utilities

Section 13.1, “Introduction to Sentinel Utilities,” on page 291

Section 13.2, “Starting and Stopping Sentinel Server,” on page 291

Section 13.3, “Sentinel Scripts,” on page 292

Section 13.4, “Version Information,” on page 298

Section 13.5, “Database Cleanup,” on page 299

Section 13.6, “Updating Your License Key,” on page 304
13.1 Introduction to Sentinel Utilities
This section allows you to understand the utilities provided by Sentinel. You can use these utilities
for the following purposes:
 For starting or stopping certain Sentinel services.

For modifying Sentinel configuration.
 To determine the version of a Sentinel library.

For troubleshooting activities.
 For configuring Sentinel email.
13.2 Starting and Stopping Sentinel Server
A Sentinel Server is made up of the following components:

Communication Server
 Correlation Engine

DAS
 Collector Manager
Any combination of the above components can be installed in a particular Sentinel Server.
In a distributed installation of Sentinel, it is likely that there will be more than one machine with a
Sentinel Server running on it. In this case, all of the Sentinel Servers work together to provide the
complete Sentinel functionality.
NOTE: At most one Communication Server and DAS component can be installed across all
Sentinel Servers in a distributed Sentinel installation. On the other hand, multiple instances of
Correlation Engine and Collector Managers are allowed.
When a Sentinel Server is started or stopped, all components installed in that Sentinel Server are
also started or stopped. To start or stop a particular component on a Sentinel Server, use the Servers
View under the Admin tab in Sentinel Control Center.
You need to start or stop a Sentinel Server because of the following routine maintenance:

Upgrades