Key Concepts 323Director logs a single event and updates it with details of the number oftimes the condition that led to the event has occurred.For example, a Security Violation event logged with recurring severity mayindicate that someone is trying to crack user passwords on your network,alternatively, it may indicate that a user has forgotten their password andis repeatedly trying to log in.Event Severity ColorsEach level of event severity has a color associated with it that is usedwithin the list in the Events window for easy identification as shown inthe following table:Table 51 Event List Color Coding KeyEvent Resolution Any logged event that represents an abnormal network condition isinitially logged as an unresolved event to indicate that the condition thatled to the event being generated is, as far as 3Com Network Director candeduce, still occurring. Unresolved events allow you to see theoutstanding abnormal network conditions that may be affecting yourusers, and so can help you determine how to prioritize any actions youmay need to take on your network.When the condition that led to the original event being logged is laterdetermined to have returned to normal the event is marked as resolved.Resolved events allow you to see historical occurrences in your network,which can help your awareness of problems that arise on a regular basisand allow you to see emerging patterns of network behavior. You mayuse this information to help you determine what action you need to taketo prevent these problems from occurring in future, and so improve thereliability and performance of your network.Information severity events are not logged as either unresolved orresolved events, as they do not represent an abnormal network condition,therefore there is nothing to resolve.Color SeverityBlack RecurringDark Red CriticalRed HighYellow WarningTurquoise Information