Asus ASR-2015S Software User Guide - Page 78

Red Hat Linux, Detai

Get Asus ASR-2015S PDF manuals and user guides View all Asus ASR-2015S manuals
Add to My Manuals
Save this manual to your list of manuals

Page 78 highlights

Storage Manager This window displays a list of the events submitted to the application log by the broadcaster, as well as other applications. Adaptec events are single-line entries that contain the following information: Icon Date Time Source Category Event ID User Computer Indicates the severity of the event. Levels are Error, Warning, Information, Operation, or Unknown. Date the event was logged by the controller. Time the event was logged by the controller. Software component-application, Windows component, or device driver-that triggered the event. Events can have dptelog, dpteng32, or dptscom in their Source field. Includes None, Operation, Warning, or a hexadecimal event code. Number assigned by the broadcaster to identify the event for Windows. Always display N/A. Name of the system where the event occurred. To view additional information about an event, click View > Detail. The Description and Data fields display additional information about the event. The Description field contains a detailed text description of the event. The Data field contains the original controller event log data, generated by the controller. This data might be requested by your technical support representative when troubleshooting problems. Event information can be saved by the Event Viewer to a file. If the file is saved in text format then only the event description is saved. Archiving in event log (.evt) file format saves all event information, which can then be sent out for troubleshooting purposes. Red Hat Linux The broadcaster collects controller events and saves them to files in the /usr/dpt directory for use by Storage Manager. Events can also be sent to an ASCII file, specified devices, or e-mailed as specified in the Event Broadcasting window. 3-37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
3-37
Storage Manager
This window displays a list of the events submitted to the
application log by the broadcaster, as well as other applications.
Adaptec events are single-line entries that contain the following
information:
To view additional information about an event, click
View
>
Detai
l.
The Description and Data fields display additional information
about the event. The Description field contains a detailed text
description of the event. The Data field contains the original
controller event log data, generated by the controller. This data
might be requested by your technical support representative when
troubleshooting problems.
Event information can be saved by the Event Viewer to a file. If the
file is saved in text format then only the event description is saved.
Archiving in event log
(.evt
) file format saves all event information,
which can then be sent out for troubleshooting purposes.
Red Hat Linux
The broadcaster collects controller events and saves them to files in
the
/usr/dpt
directory for use by Storage Manager. Events can also
be sent to an ASCII file, specified devices, or e-mailed as specified
in the Event Broadcasting window.
Icon
Indicates the severity of the event. Levels are
Error
,
Warning
,
Information
,
Operation
, or
Unknown
.
Date
Date the event was logged by the controller.
Time
Time the event was logged by the controller.
Source
Software component—application, Windows
component, or device driver—that triggered the
event. Events can have
dptelog
,
dpteng32
, or
dptscom
in their Source field.
Category
Includes None, Operation, Warning, or a
hexadecimal event code.
Event ID
Number assigned by the broadcaster to identify the
event for Windows.
User
Always display N/A.
Computer
Name of the system where the event occurred.