Is it somewhere in the DataCollection wiki or is there another document that would break down what I needed to do?ĪB Newark Brewery Systems Tony Kennedy Monday, 12:32 PM I feel like there should be more detail here.ĭoes this help at all? Where can I check the MIBS and such to see what is being sent/collected? I’m sure the process of adding the correct MIBs to collect data from my 6509s is documented, I just don’t know where. Unknown" changed entity ‘3750SwitchName’_’3750 Switch IP’ from source: 1Ĭisco Event: A Configuration Management event has occurred. When I make a configuration change to the switch I get these events: It looks like the IP of the 3750X is being used as the SNMP community name… Is that what this error means? When I first scanned the node I get this event (I replaced the switch name and IP with text in single quotes): The following example defines an smtp() destination using only the required parameters.I setup one of our 3750X switches in OpenNMS and after enabling Syslog SNMP traps, I get events for Syslog traps the switch is sending. The smtp() destination driver is available only in syslog-ng OSE 3.4 and later.ĭeclaration: smtp(host() port() from() to() subject() body() options()) For the list of available optional parameters, see smtp() destination options. The smtp() driver has the following required parameters: host(), port(), from(), to(), subject(), and body(). For more information on available macros see Macros of syslog-ng OSE.
The subject(), body(), and header() fields may include macros which get expanded in the e-mail. You can customize the main fields of the e-mail, add extra headers, send the e-mail to multiple recipients, and so on.
The smtp() driver uses SMTP, without needing external applications. The smtp() driver sends e-mail messages triggered by log messages. For example, syslog-ng OSE does not verify whether the recipient exists.
It hands mails over to an SMTP server, and that is all it does, therefore the resulting solution is as reliable as sending an e-mail in general. The goal is to send mail to trusted recipients, through a controlled channel. The destination is aimed at a fully controlled local, or near-local, trusted SMTP server. Destination: Forward, send, and store log messages > smtp: Generating SMTP messages (e-mail) from logs
0 kommentar(er)
