Enterasys Networks Network Card - Manual (Page 32)

20
RiverMaster Administrator’s Guide
Checking Server Status Chapter 2
Getting Started with RiverMaster
The memory and hard disk usage meters in the Aurorean Policy Server
statistics area show how much server resources are being consumed to
manage the Aurorean Virtual Network. High memory usage normally reflects
a large number of authorization messages for both remote user authentication
and server-to-server traffic; generating reports and Aurorean Client Software
installation kits can also consume Aurorean Policy Server memory. High disk
space usage is normally a result of many large log and report files
accumulating on the hard disk.
NOTE
When 85% of the Aurorean Policy Server drive capacity is full, the server
automatically begins deleting logs and reports older than 90 days. Log
and report deletions are not configurable at this time.
Log Maintains a running record of system
events and messages received by each
Aurorean Virtual Network component.
The RiverMaster application displays
these logs and extracts information from
them to produce daily reports. The Aurorean Policy Server will accept
configuration changes and the
Aurorean Network Gateway will accept
tunnel connection attempts. However,
the messages generated by these
actions are not stored in a log file on
the Aurorean Policy Server and cannot
be viewed as they occur from the
RiverMaster. Reports will also be
inaccurate.
Authentication Provides the mechanism for
authenticating remote users against user
databases located on either the Aurorean
Policy Server or an external
authentication server (such as a RADIUS
device). Authentication also serves
another security role, by enforcing a strict
ring level hierarchy for Delivery messages
to prevent unauthorized access to
sensitive information. Configuration changes sent by the
RiverMaster to the Aurorean Policy
Server are rejected because the
Aurorean Policy Server cannot
authenticate them. Also, the Aurorean
Network Gateway will not accept new
tunnel connection attempts because
the remote user cannot be
authenticated. The Aurorean Policy
Server reboots approximately 3
minutes after this service stops.
Table 1 Aurorean Policy Server Services
Service Function If Stopped...