Hello All,
I'm having some issues setting up a syslog server for our old router, which is not currently in use. I'm just testing it out, trying to learn how to do syslog stuff before we go ahead and do it on our main one. So as it is now, the rouer is connected to our network and has an IP address 66.29.152.xx while our syslog server has an IP address of 66.29.152.xx as well. I've set everything up as per the Cisco documentation and still the syslog server does not appear to be retrieving any messages. I've tried power cycling the router to see if I could do anything that would generate some messages but still the syslog server picks up nothing. Logging is turned on in the Cisco configuration and configured as per below:
logging trap debugging
logging facility local3
logging 66.29.152.7
And a quick check to see if it is indeed logging shows:
1602router#show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level debugging, 7 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: disabled
Trap logging: level debugging, 11 message lines logged
Logging to 66.29.152.xx, 11 message lines logged
Is this telling me that messages are being logged that SHOULD be sent to the syslog server?
/etc/hosts on the syslog server contains the line:
66.29.152.xx (the machine's IP, not the router's IP, yes?) fred fred.domain.net loghost
and /etc/syslog.conf contains the line:
local3.debug (5 tabs here) /var/log/cisco.log
The router is set to broadcast messages to server facililty local3 as shown above in the running-config.
Syslog is running (rebooted it after making changes)
/var/log/cisco.log exists and is writeable.
Still, no matter how long I wait or how many times I reboot the router, /var/log/cisco.log remains an empty file. Is this normal for a router not actually "routing"?. I would think debug messages would be happening even if its not really doing anything (messages in the router's boot sequence, for example).
Anyway, if anyone has some insight on this I'd greatly appreciate the input! Thanks a bunch.
By the way the router IOS is 12.0 and the syslog is running on Fedora 3.
I'm having some issues setting up a syslog server for our old router, which is not currently in use. I'm just testing it out, trying to learn how to do syslog stuff before we go ahead and do it on our main one. So as it is now, the rouer is connected to our network and has an IP address 66.29.152.xx while our syslog server has an IP address of 66.29.152.xx as well. I've set everything up as per the Cisco documentation and still the syslog server does not appear to be retrieving any messages. I've tried power cycling the router to see if I could do anything that would generate some messages but still the syslog server picks up nothing. Logging is turned on in the Cisco configuration and configured as per below:
logging trap debugging
logging facility local3
logging 66.29.152.7
And a quick check to see if it is indeed logging shows:
1602router#show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level debugging, 7 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: disabled
Trap logging: level debugging, 11 message lines logged
Logging to 66.29.152.xx, 11 message lines logged
Is this telling me that messages are being logged that SHOULD be sent to the syslog server?
/etc/hosts on the syslog server contains the line:
66.29.152.xx (the machine's IP, not the router's IP, yes?) fred fred.domain.net loghost
and /etc/syslog.conf contains the line:
local3.debug (5 tabs here) /var/log/cisco.log
The router is set to broadcast messages to server facililty local3 as shown above in the running-config.
Syslog is running (rebooted it after making changes)
/var/log/cisco.log exists and is writeable.
Still, no matter how long I wait or how many times I reboot the router, /var/log/cisco.log remains an empty file. Is this normal for a router not actually "routing"?. I would think debug messages would be happening even if its not really doing anything (messages in the router's boot sequence, for example).
Anyway, if anyone has some insight on this I'd greatly appreciate the input! Thanks a bunch.
By the way the router IOS is 12.0 and the syslog is running on Fedora 3.
