You want to collect and save system logging messages over long periods of time, but you don't want to constantly manage the disk space availability on your routers.
You can set up a log server on your network that has many gigabytes of storage space and then redirect the router's logging messages to that server.
[edit system syslog] aviva@router1#
This configuration redirects all
logging messages to the file server
172.17.12.30. You can also specify the hostname instead of the IP address. The file server must be running a standard
syslogd utility. You find the system logging messages in the /var/log/messages file on the server, unless the server has been configured to save them some-place else:
tail /var/log/messagesMar 23 09:27:29 server1 /kernel: linux: syscall mmap2 is obsoleted or not implemented (pid=12624) %INTERACT-5-UI_DBASE_LOGIN_EVENT: User 'aviva' entering configuration mode Mar 23 17:48:40 router1-fxp0.mycompany mgd: %INTERACT-5-UI_COMMIT: User 'aviva' performed commit: no comment Mar 23 17:48:44 router1-fxp0.mycompany xntpd: %NTP-5: ntpd 4.0.99b Sat Mar 12 07:43:39 GMT 2005 (1) Mar 23 17:48:44 router1-fxp0.mycompany xntpd: %NTP-5: using kernel phase-lock loop 2001 Mar 23 17:48:44 router1-fxp0.mycompany xntpd: %NTP-5: using kernel phase-lock loop 2041 Mar 23 17:48:45 router1-fxp0.mycompany ...