Symantec 11281411 Administration Guide - Page 62

How Alert Management System works

Page 62 highlights

62 Setting up the Alert Management System How Alert Management System works ■ Send an SNMP trap ■ Load an NLM Note: Alerts generated through SNMP traps can be sent to any third-party SNMP management console. To receive SNMP traps from Symantec AntiVirus, you must have the Symantec System Center and AMS2 installed. (Only a primary server will run AMS2. You must use the Symantec System Center to designate the primary server.) See "Configuring the Send SNMP Trap alert action" on page 74. How Alert Management System works AMS2 alerts are transferred from Symantec AntiVirus into AMS2 through the Symantec AntiVirus service. On a computer running the Symantec AntiVirus client, the Symantec AntiVirus service waits for an event thread that requires an alert. These threads can be generated by the following events: ■ Configuration change ■ Default Alert ■ Symantec AntiVirus startup/shutdown ■ Scan Start/Stop ■ Virus Definitions File Update ■ Threat Found If you have configured an alert for any of these events, when the event occurs it will generate a thread. The thread prompts the Symantec AntiVirus service to create a threat information block, which it forwards to the client's parent server. When the parent server receives the threat information block, it enters it into its AMS2 log. The threat information is then forwarded to the primary server, which makes a call to AMS2. AMS2 enters the information into the AMS2 database and acts on it. The action taken depends upon how you have the alert configured. Communication in AMS2 is carried out through CBA, which is part of the Intel Communication Method.

  • 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
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216

62
Setting up the Alert Management System
How Alert Management System works
Send an SNMP trap
Load an NLM
Note:
Alerts generated through SNMP traps can be sent to any third-party SNMP
management console. To receive SNMP traps from Symantec AntiVirus, you
must have the Symantec System Center and AMS
2
installed. (Only a primary
server will run AMS
2
. You must use the Symantec System Center to designate
the primary server.)
See
“Configuring the Send SNMP Trap alert action”
on page 74.
How Alert Management System works
AMS
2
alerts are transferred from Symantec AntiVirus into AMS
2
through the
Symantec AntiVirus service. On a computer running the Symantec AntiVirus
client, the Symantec AntiVirus service waits for an event thread that requires an
alert.
These threads can be generated by the following events:
Configuration change
Default Alert
Symantec AntiVirus startup/shutdown
Scan Start/Stop
Virus Definitions File Update
Threat Found
If you have configured an alert for any of these events, when the event occurs it
will generate a thread. The thread prompts the Symantec AntiVirus service to
create a threat information block, which it forwards to the client’s parent server.
When the parent server receives the threat information block, it enters it into its
AMS
2
log. The threat information is then forwarded to the primary server,
which makes a call to AMS
2
. AMS
2
enters the information into the AMS
2
database and acts on it. The action taken depends upon how you have the alert
configured.
Communication in AMS
2
is carried out through CBA, which is part of the Intel
Communication Method.