HP StorageWorks Reference Information Storage System V1.5 Administrator Guide (T3559-96044, June 2006)

Application Ev
ents features
Table 8 Applica
tion Events features
Feature
Description
Event
Information describing the event or error , including the service or
application name.
Machine
The name of the
server on which the event is occurring.
IP
TheIPaddressoftheserveronwhichtheeventisoccurring.
Date
The date of the event.
Level
The status of t
he event. In Application Events, the only status shown is
critical.
Appliance Performance
This area of t
he o verview pr ovides information from the Storage Status v iew (see Storage
Status on pag
e29). Thetableontheleftdisplaysthenumberofdocumentsstored,theamountofused
and total di
sk space, the document storage rate, and the document index rate for each domain. The bar
graph displays the system’s stora ge space ratio. The line graph on the right shows the messages per
second that the system stored in the past day, ending with the current tim e.
Account Manager Ser vice
The Account Manager Service provides a brief summary of information from the PCC Account Manager
(see Account Manager (AM) on page 47) . This area displays the number of individual RISS users and
groups, pending users and groups, and the number of RISS repositories. It also displays the number of
synchronization errors, if any, pertaining to RISS user accounts. Synchronization errors can be corrected
in the Error Recovery view (see Account Error Recovery on page 58).
Failed I
ndexed Documents and CatchAll
This area of the Overview displays the following information:
• Failed Indexed: The number of documents that were not indexed. (For example, the system
might no
t have been able to index the particular file type.) These documents are in the failed
indexing repository, which can be viewed in the Account Manager (see Account Manager
(AM) on page 47. Click the Repository radiobuttoninAM,clicktheOther tab, then o pen the
failed indexing repository.
• CatchA
ll: The number of messages in the system’s catch-all repository, including messages too
large to be indexed, m essages that cannot be parsed, and messages that cannot be routed to a
registered RISS user. The number includes messages that went into catch-all from the SMTP portals
as well as those from the smart cell indexers.
Messages that cannot be parsed have malformed message structures (MIME) or unsuppor ted
chara
cter sets.
Messages that cannot be routed do not correspond to any system routing rule. They are not
recogni zed as destined for a registered RISS user. Mailing-list messages cannot be routed if the
recipient’s name is not included in the message as a destination.
The c
atch-all repository can be viewed in the Account Manager (see Account Manager
(AM) on page 47 by clicking the Repository radio button in AM, clicking the Other tab, then
opening the catch-all repository.
The failed indexing and catch-all repositories are automatically created when the system is started.
26 System Status