The configuration tool included with SMS is used to modify the configuration of the Event to Trap Translator through an SMS job. It allows the user to provide a data file that creates, deletes, and modifies the configuration of translated events. The tool can also be used to modify trap destinations and communities.
The tool generates an SMS status MIF file after it runs to indicate the overall status of the operation. It also generates a text log file with detailed information on which statements succeeded or failed. If any particular line results in an error, an error is written to a log file and processing continues with the next line in the file.
This tool is called EVENTCMx.EXE, where x is I for Intel, A for Alpha, and M for MIPS. This tool is located in the MSTEST directory on all SMS logon servers.
The syntax for adding or deleting events using the configuration tool format is:
#pragma {add | delete} eventlog eventsource eventID [count=#] [time=#]
add
Adds the specified event to the list of events to be translated to traps. If there are any errors in the add parameters, the event is not added and an error is returned. If the specified event and event source are already configured, then the count and time values are modified.
delete
Deletes the specified event from the translation list. If the event specified is not in the configuration, an error is returned.
eventlog
The Windows NT event log that contains the event. There are three possible values for this entry: System, Application, and Security.
eventsource
The source specified in the Windows NT event log. If the event source is more than one word, it should be enclosed in quotation marks.
eventID
The 32-bit event identification number. This is partially based on the 16-bit event number specified in the Windows NT event log.
count
The number of times that the event must occur before generating a trap. For example, you can specify that the event must occur 5 times before it is translated.
time
The time period for the count. For instance, you can specify that the event must occur 5 times in an hour to be translated.
The syntax for modifying SNMP trap destinations is:
#pragma {add_trap_dest | delete_trap_dest} community address
add_trap_dest
Adds the specified address to the list of trap destinations for the specified community. If the community does not exist, it is created and the address is added. If the specified address already exists in the specified community, the statement is ignored.
delete_trap_dest
Deletes the specified address from the specified community. If the community does not exist or the address is not in the community, an error is written to the log.
community
The group of computers to which the pragma should be applied.
address
The trap destination TCP/IP address.
A semicolon in the first column of any line indicates a comment line. A sample CNF file follows:
; this is a sample CNF file ; ; the next line configures Rdr event 8003 #pragma Add System "Rdr" 3221227472 1 0 ; ; the next line sets up the trap destination address #pragma Add_Trap_Dest public 198.255.255.255 ; end of file