Redirecting OS level events to a remote server
OS level events from the BMC Discovery appliance can be forwarded to a remote syslog server.
This procedure only affects the operating system logs, not the BMC Discovery product logs.
You must have a syslog server that is configured to accept logs from remote clients.
To configure BMC Discovery to send OS logs to a remote server
If your appliance is running on CentOS 6
If your appliance is running on CentOS 6, you should follow this procedure in the BMC Discovery 11.2 documentation.
As the root user, edit the syslog configuration file,
/etc/rsyslog.confadding the following entry at the top. Replace the IP address with that of your syslog server:
# Send everything to the remote syslog server *.* @192.168.1.100
Restart the syslog service on the appliance.
If you are using CentOS7, Enter:
[tideway@localhost]$ sudo /usr/bin/systemctl restart rsyslog.service [tideway@localhost]$
If you are using CentOS6, Enter:
[tideway@localhost]$ sudo /sbin/service rsyslog restart [tideway@localhost]$
Test that the integration works. Use the logger utility to send a syslog message. For example:
[tideway@localhost ~]$ logger this is a test of remote logging [tideway@localhost ~]$ su - Password: [root@localhost ~]$ tail -n5 /var/log/messages Aug 20 13:38:15 localhost systemd: Created slice User Slice of tideway. Aug 20 13:38:15 localhost systemd-logind: New session 369 of user tideway. Aug 20 13:38:15 localhost systemd: Started Session 369 of user tideway. Aug 20 13:38:18 localhost tideway: this is a test of remote logging Aug 20 13:38:33 localhost su: (to root) tideway on pts/1 [root@localhost ~]$
Then log in to the remote syslog server and check that the same messages appear.
Log in or register to comment.