Administering Critical Events › Understanding Configuration Manager › Automatic Responses to Event Messages › Event Sources

Event Sources

Event Management receives events from a variety of sources:

• The cawto command, which sends an event to the Event Console.
• The cawtor command, which sends an event to the Event Console and waits for a reply. It appears in the held messages pane and will not be deleted until the operator replies.
• The oprcmd command, which sends a request to execute a command to the designated target machines.
• The careply command, which lets you use any terminal to reply to an event being held by the Event Console.
• Enterprise Management components, which generate events directly to the Event Console.
• SNMP traps that are generated by various devices, such as switches or printers, and other software components. catrapd (an Event Management component), collects, formats, and routes these traps to the Event Management daemon on the local or remote node.
• The Windows Event Logs, which store events generated by the Windows operating system, device drivers, or other products. The Event Management log reader collects these events and forwards them to the Event Management daemon.
• The syslog daemon on UNIX/Linux platforms, where messages are routed through the syslog daemon to the Event Console. Events issued through the logger utility are included as they also use the syslog daemon. These events may have originated on a platform not running CA NSM.
• Agent Technology agents, policies, and DSM.
• Any CA or client programs that use the CA NSM SDK.
• API functions, such as EmEvt_wto, which issue events to Event Management.

For additional information about the cawto, cawtor, oprcmd, careply, and catrapd administrator commands, see the online CA Reference and the CA SDK Reference.