Novell Sentinel Rapid Deployment 6.1, Installation Manual

Page: 25 / 84

Sentinel 6.1 Rapid Deployment System Requirements 25
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09

All events are stored in the database (that is, there are no filters to drop events).

Ninety days worth of data is stored online in the database.

Storage space for Advisor data is not included in the specifications in Table 3-2 on page 25 and
Table 3-3 on page 26 .
 The Sentinel Server has a default 5 GB of disk space for temporarily caching event data that
fails to be inserted into the database.

The Sentinel Server also has a default 5 GB of disk space for events that fail to be written to
aggregation event files.
NOTE: The Advisor subscription requires an additional 50 GB of disk space on the server.
The hardware recommendations for a Sentinel implementation can vary based on the individual
implementation, so it is recommended that Novell Consulting Services or any of Novell Sentinel
partners be consulted prior to finalizing the Sentinel architecture. The recommendations below can
be used as a guideline.
NOTE: Because of high event loads and local caching, the Sentinel Server is required to have a
local or shared striped disk array (RAID) with a minimum of 4 disk spindles.
Table 3-2
Single Machine Configuration
Components RAM Space CPU
Machine 1: Sentinel 6.1 Rapid Deployment
Server (Maximum EPS - 3200)

Collector Manager (1200 MB)

DAS_Core (1024 MB)

DAS_Binary (512 MB)

Correlation Engine (512 MB)

9 General Event Collectors

4 eDirectory Event Sources (generating
250 eps each)

3 Syslog Event Sources (generating 350
eps each)

2 WMS Event Sources (generating 500
eps each)

10 Correlation Rules Deployed

10 unique Active Views

3 simultaneous users

2 Maps Deployed
16 GB 1 TB,
SAS (15K
rpm) Hard
Disk(s)
Hardware
RAID 10
SLES10 SP2- Dell
PowerEdge 2900,2 x
Quad-Core Intel
®
Xeon
®
E5310 (1.6 GHz) with
Gigabit Ethernet NIC