Events and Logs
106
"FD 100/320Gbps NT and FX NT IHub System
Basics, Management and OAM Guide"
3HH-11982-AAAA-TQZZA Issue: 10
• A subject identifying the affected object.
• A short text description.
Event control assigns the severity for each application event and whether the event
should be generated. The severity numbers and severity names supported in the
ISAM conform to ITU standards M.3100 X.733 & X.21 and are listed in Table 107.
Table 107 Event Severity Levels
Event control maintains a count of the number of events generated (logged) for each
application event. The severity of an application event can be configured in event
control.
An event log within the ISAM associates the event sources with logging destinations.
For now, events can only be directed to the current CLI session. A log filter policy can
be associated with the event log to control which events will be logged in the event
log based on combinations of application, severity, event ID range, VRF ID, and the
subject of the event.
6.3 Log Destinations
Event logs use a common mechanism for referencing a log destination. ISAM
supports the following log destinations:
• Session
Only a single log destination can be associated with an event log. An event log can
be associated with multiple event sources, but it can only have a single log
destination.
Severity Number Severity Name
1 cleared
2 indeterminate (info)
3critical
4 major
5 minor
6 warning
To Next Page
Loading...
