![background image](http://html1.mh-extra.com/html/3com/3c15500-network-director-pc/3c15500-network-director-pc_user-manual_441352328.webp)
324
C
HAPTER
8: T
HE
E
VENT
L
OG
Events may also be manually resolved. See
“Manually Resolving Events”
on
page 334
for more information.
Smart Event Analysis
The
Events System
provides a set of features that work together to filter
and interpret the generated events and provide you with the best
possible picture of the state of your network. These features are
event
correlation
,
recurring event handling
,
event suppression
and
SNMP trap
filtering
, and are known collectively as
Smart Event Analysis
. See
“Controlling Smart Event Analysis”
on
page 352
for more information.
Event Correlation
The event correlation feature analyzes the events that are being
generated, determines sets of events that have been caused by the same
issue, and replaces each set with a single event that more clearly
describes the issue.
For example, if there is a set of
Device not responding
and
Link is
unavailable
events generated for a group of connected devices within a
short period of time, then the event correlator will analyze these events,
determine that they are caused by a loss of connectivity to that section of
the network and replace the set of events with a single
Section of
network down
event.
Recurring Event Handling
Events may be generated repeatedly if a monitor regularly crosses a
threshold or if the same SNMP trap type is received repeatedly from a
device. If all of these events were logged separately in the event system
then they would quickly outnumber other events, making it difficult to
determine the real problems in your network.
The recurring event handler helps avoid this situation by determining
when the same event is being generated repeatedly for a particular
device or link, and then replacing all occurrences of the event with a
single event that has the recurring severity. The recurring event handler
then continues to scan for further occurrences of this event, prevents
them from being logged and updates the already logged recurring
severity event with the total number of times that the event has been
generated.
Recurring events take longer to resolve than non-recurring events as
3Com Network Director
waits to ensure that no further events of the
same type and source are being generated.
Summary of Contents for 3C15500 - Network Director - PC
Page 4: ......
Page 34: ......
Page 38: ...34 ABOUT THIS GUIDE ...
Page 50: ...46 CHAPTER 1 GETTING STARTED ...
Page 64: ...60 CHAPTER 2 PRODUCT ACTIVATION ...
Page 213: ...Components 209 Figure 75 Export to Visio Dialog Box ...
Page 220: ...216 CHAPTER 5 WORKING WITH THE MAP Figure 84 Double Clicking on a Router in the Tree ...
Page 264: ...260 CHAPTER 6 VIEWING DEVICE DETAILS Figure 117 Security Tab for a Device ...
Page 276: ...272 CHAPTER 6 VIEWING DEVICE DETAILS ...
Page 322: ...318 CHAPTER 7 MONITORING THE NETWORK ...
Page 385: ...Examples 381 Figure 189 Attach Alerts Dialog Box ...
Page 406: ...402 CHAPTER 9 PERFORMANCE REPORTING ...
Page 431: ...Components 427 History View dialog box Figure 210 History View Dialog Box ...
Page 440: ...436 CHAPTER 10 RMON Host View dialog box Figure 219 Host View Dialog Box ...
Page 476: ...472 CHAPTER 11 CREATING REPORTS ...
Page 502: ...498 CHAPTER 12 CONFIGURING SINGLE DEVICES ...
Page 526: ...522 CHAPTER 13 VLAN MANAGEMENT Figure 272 Options Dialog Box VLANs Tab ...
Page 567: ...Components 563 Figure 305 Selecting the Link to the End Station on the Map ...
Page 626: ...622 CHAPTER 14 BULK CONFIGURATION ...
Page 684: ...680 CHAPTER 16 UPGRADING DEVICE SOFTWARE ...
Page 814: ...810 CHAPTER 19 BACKING UP DEVICE CONFIGURATIONS ...
Page 838: ...834 CHAPTER 20 LIVE UPDATE ...
Page 894: ...890 APPENDIX G ADDING MAC ADDRESS VENDOR TRANSLATIONS ...