When you configure your PacketFence to send log data to USM Appliance, you can use the PacketFence plugin to translate raw log data into normalized events for analysis. The table below provides some basic information for the plugin.
| Device | Details |
|---|---|
| Vendor | Inverse Inc. |
| Device Type | Network Access Control |
| Connection Type | Syslog |
| Data Source Name | packetfence |
| Data Source ID | 1876 |
Integrating PacketFence
Before you configure the PacketFence integration, you must have the IP Address of the USM Appliance Sensor.
To configure PacketFence to send Syslog messages to USM Appliance
Log data collection and Syslog output to
USM Appliance is configured by modifying log.conf with a SYSLOG appender. For example:
log4perl.rootLogger=DEBUG, LOGFILE, SYSLOG
log4perl.category.pf.SNMP = INFO
log4perl.appender.LOGFILE=Log::Log4perl::Appender::File
log4perl.appender.LOGFILE.filename=/usr/local/pf/logs/packetfence.log
log4perl.appender.LOGFILE.mode=append
log4perl.appender.LOGFILE.layout=PatternLayout
log4perl.appender.LOGFILE.layout.ConversionPattern=%d{MMM dd HH:mm:ss} %X{proc}(%X{tid}) %p: %m (%M)%n
log4perl.appender.SYSLOG = Log::Dispatch::Syslog
log4perl.appender.SYSLOG.ident = packetfence
log4perl.appender.SYSLOG.facility = local5
log4perl.appender.SYSLOG.layout = Log::Log4perl::Layout::SimpleLayout
After creating the appender file, make sure you include your entry in /etc/rsyslog.conf (RHEL), for example:
local5. * @your_syslog
After making changes to the log configuration, restart syslog to have the changes take effect.
Note: Make sure you configure the correct log that you want to send under /usr/local/pf/conf/log.conf.d/.
Plugin Enablement
For plugin enablement information, see Enable Plugins.
Additional Resources and Troubleshooting
https://packetfence.org/support/faq/article/packetfence-and-remote-syslog.html?no_cache=1
For troubleshooting, refer to the vendor documentation:
Feedback