Configure logging on network devices based on Cisco IOS, PIX-OS (ASA), and other network device operating systems.
Papertrail supports two ways of identifying a device:
These two methods cover nearly all network devices. If neither are suitable, please let us know.
Don’t see your device here? If it can send logs, Papertrail almost certainly can receive them. Here’s how.
Since this device only supports logging to the default syslog port (514), explicitly register the device’s IP.
Papertrail will provide a hostname to use with the Aruba controller’s “logging” command. For example:
configure terminal
logging logs.papertrailapp.com
exit
write memory
If the device doesn’t accept a DNS name, replace logs.papertrailapp.com with its IP address from nslookup.
More: Aruba log verbosity
Barracuda Spam Firewall can send its Mail Syslog (SMTP activity) and Web Syslog (GUI activity) to Papertrail.
Per Syslog and the Spam Firewall, browse to Advanced, then Troubleshooting. As of this writing, Barracuda Spam Firewall supports non-default syslog ports but only supports logging to a destination IP address, not a DNS hostname. To log to Papertrail, use the settings shown on Add Systems. Instead of configuring a hostname (such as logs.papertrailapp.com), resolve that hostname into IP addresses using nslookup. Configure the device to log to any one of the IP addresses returned by nslookup.
Configure each of the 2 message types, like this:

Most home wireless access points and cable/DSL routers can be configured to transmit events. In the device’s Web management interface, set the log or event destination to the hostname and port provided by Papertrail. If the device can only log to the default syslog port, 514, visit Add Systems and click the “Sender requires port 514” link.
To send from Cisco IOS-based devices, connect via SSH or telnet and run enable to become administrator. Enter the following:
configure terminal
logging host logsN.papertrailapp.com transport udp port XXXXX
logging facility syslog
logging trap debugging
exit
write memory
Replace logsN and XXXXX with the details provided by Papertrail in log destinations. Most IOS releases after 12.2 support user-supplied ports. The configuration assumes that the router has been told about DNS servers.
For older IOS versions which only support logging to the default port, the configuration could be:
logging logs.papertrailapp.com
If the device does not have DNS enabled, check the Papertrail account’s log destinations to see which hostname has been assigned, then replace logsN.papertrailapp.com with its IP address from nslookup.
We recommend the following to make IOS messages interoperate better with the syslog protocol. Disable an extra timestamp and sequence numbers:
no service sequence-numbers
no service timestamps debug uptime
no service timestamps log uptime
logging enable
logging host outside logsN.papertrailapp.com udp/XXXXX
logging trap informational
logging severity 5
outside is the name of the Internet-facing interface on the device. Replace logsN and XXXXX with the details provided by Papertrail in log destinations.
After verifying that logging is functioning, we strongly suggest changing to a less verbose setting like:
logging trap notification
In devices which support rate-limited logging (such as FWSM), this will rate-limit the log volume to 10 debug-level messages per 30 second interval:
logging rate-limit 10 30 level debugging
If you explicitly register the device with Papertrail so that it can log to the default syslog port, this will work:
logging host outside logs.papertrailapp.com
Since this device only supports logging to the default syslog port (514), explicitly register the device’s IP.
For Cisco Catalyst OS devices, connect via SSH or telnet and run enable to become administrator. Enter the following:
set logging server enable
set logging server logs.papertrailapp.com
set logging level all 5
set logging server severity 6
Instead of configuring a hostname (such as logs.papertrailapp.com), resolve that hostname into IP addresses using nslookup. Configure the device to log to any one of the IP addresses returned by nslookup.
Cisco Meraki supports logging to syslog. Syslog servers can be defined in the Dashboard from Network-wide > Configure > General.
Click the Add a syslog server link to define a new server, using the port details from Add Systems. Instead of configuring a hostname (such as logsN.papertrailapp.com), resolve that hostname into IP addresses using nslookup. Configure the device to log to one of the IP addresses returned by nslookup. Finally, select one or more roles that will send logs to Papertrail.

The DD-WRT firmware package provides two different methods for configuring syslog to send log messages to Papertrail: the User Interface and via a startup script on boot.
Since this device only supports logging to the default syslog port (514), explicitly register the device’s IP.
In the DD-WRT Web interface:
logs.papertrailapp.com.Instead of configuring a hostname (such as logs.papertrailapp.com), resolve that hostname into IP addresses using nslookup. Configure the device to log to any one of the IP addresses returned by nslookup.
To configure syslog to use a port other than 514, create a startup script via the router’s telnet/SSH connection and enter the following set of commands:
$ killall syslogd
$ /sbin/syslogd -l <SEVERITY> -L -R <LOG DESTINATION IP ADDRESS>:XXXXX
Check the Papertrail account’s log destinations to see which hostname has been assigned, then replace XXXXX with the port, and <LOG DESTINATION IP ADDRESS> with the hostname’s IP address from nslookup.
DD-WRT firmware versions other than “micro” can also send security events. To enable security events, visit the “Security” tab, scroll to “Log Management,” and enable desired options.
F5 BIG-IP runs the syslog-ng daemon as its native local log collector. Its syslog-ng can be configured to send to Papertrail. To add Papertrail as the only destination for TMOS logs (using UDP), run:
tmsh modify sys syslog remote-servers add {papertrail {host 1.2.3.4 remote-port XXXXX}}
Replace 1.2.3.4 with an IP address of the log destination hostname provided by Papertrail. It can be found with nslookup. Replace XXXXX with the log destination port provided by Papertrail.
More: syslog in TMOS 9.x/10.x, syslog in TMOS 11.x, TMOS concepts
Excerpting from page 29 of FortiOS Logging & Reporting:
To configure FortiOS to log to a syslog server via the management Web interface:
Log & Report > Log Config > Log SettingSyslogName/IP, enter the log destination hostname provided by PapertrailPort, enter the log destination port provided by Papertrail.Level, select a log level the Fortinet unit will log all messages at or above that logging severity level. Popular values are warning (4), error (3), or notification (5).Alternatively, to configure syslog via the FortiOS command line, run:
config log syslogd setting
set status enable
set server logsN.papertrailapp.com
set port XXXXX
end
Replace logsN and XXXXX with the name and port number provided by Papertrail.
More: FortiOS Logging & Reporting, log message reference
Instead of configuring a hostname (such as logs.papertrailapp.com), resolve that hostname into IP addresses using nslookup. Configure the device to log to any one of the IP addresses returned by nslookup.
Summarizing VSP Audit Log User Guide section 2-5 (“Transferring audit log files to syslog servers”):
More: VSP Audit Log User Guide (section 2-5 on page 39)
To configure Papertrail in Junos, run:
configure
to enter configuration mode. Enter these configuration commands, replacing logsN and XXXXX with the name and port provided by Papertrail:
set system syslog host logsN.papertrailapp.com any notice
set system syslog host logsN.papertrailapp.com authorization info
set system syslog host logsN.papertrailapp.com port XXXXX
commit and-quit
Confirm the settings with:
show system syslog host logsN.papertrailapp.com | display set
To configure Papertrail in ScreenOS, enter these configuration commands, replacing logsN and XXXXX with the name and port provided by Papertrail:
set syslog config "logsN.papertrailapp.com"
set syslog config "logsN.papertrailapp.com" facilities local7 local7
set syslog config "logsN.papertrailapp.com" port XXXXX
set syslog enable
set syslog backup enable
set log serial-number enable
MikroTik RouterOS supports logging to syslog. To configure syslog via the RouterOS command line, run:
system logging action add bsd-syslog=yes name=papertrail remote=IP_ADDRESS remote-port=XXXXX target=remote
Check the Papertrail account’s log destinations to see which host has been assigned (it should appear as logsN.papertrailapp.com), use nslookup to find its IP address, then replace IP_ADDRESS with that value. Replace XXXXX with the port number.
Once that’s been configured, send all or nearly all topics to the newly-created target:
system logging add action=papertrail disabled=no prefix="" topics=!async
To confirm it, run /system logging export. You should see an entry like this
/system logging action add bsd-syslog=yes name=papertrail remote=IP_ADDRESS remote-port=XXXXX target=remote
/system logging add action=papertrail topics=!async
More: RouterOS logging actions, MikroTik Wiki
To configure OpenWrt to send to Papertrail, connect via SSH and then run the following:
uci set system.@system[0].log_ip=IP_ADDRESS
uci set system.@system[0].log_port=XXXXX
uci commit
Check the Papertrail account’s log destinations to see which host has been assigned (it should appear as logsN.papertrailapp.com), use nslookup to find its IP address, then replace IP_ADDRESS with that value.
To confirm the configuration, execute: uci show system
Since this device only supports logging to the default syslog port (514), explicitly register the device’s IP.
Papertrail will provide a destination hostname for your router to log to. In the ZoneDirector Web management interface, browse to Configure > System. Scroll to “Log Settings.” Enable “Remote Syslog.” Instead of configuring a hostname (such as logs.papertrailapp.com), resolve that hostname into IP addresses using nslookup. Configure the device to log to any one of the IP addresses returned by nslookup.
The EdgeMAX router supports logging to a destination hostname and port. Log in to the router and choose the System tab at the bottom of the screen. Look for the Management Settings heading and enter your account’s destination under System Log.

Click Save at the bottom and the setting will be applied.
The UniFi Controller supports logging to a destination hostname and port. Log in to the Controller and choose the Settings gear
. Under Remote Logging, enter your account’s destination and port.

Click Apply Changes and the destination settings will be pushed to all devices under the UniFi controller’s watch including access points, switches, and routers.
Since this device only supports logging to the default syslog port (514), explicitly register the device’s IP.
Papertrail will provide a destination hostname for your router to log to. Provide that hostname to the VyOS router with:
set system syslog host <hostname>
You may also want to set the log facility and/or level of log messages which are sent to Papertrail. See Brocade Vyatta 5400 manual or VyOS user guide:
To configure ZyWALL to send to Papertrail, connect via SSH or telnet and then run:
enable
configure terminal
logging syslog 1 port XXXXX
logging syslog 1 format cef
logging syslog 1 address logsN.papertrailapp.com
exit
write
exit
Replace XXXXX and logsN with Papertrail-provided values from log destinations.
See ZyXEL Knowledge Base.
Papertrail supports the industry standard remote syslog protocol, which is the protocol used by nearly all network devices.
To send logs from a device not shown here, consult the device manual under “Logging” or “Syslog,” or search Google for the device name plus the word “syslog.” For example, juniper qfx syslog or hp procurve syslog. Most device manufacturers publish this documentation.
Follow the manufacturer’s instructions for remote logging. Use the Papertrail hostname and port shown on Add Systems.