05-19-2008 02:04 AM - edited 03-05-2019 11:04 PM
Hi
Here's my output from "sh log" (note the syslog part):
Syslog logging: enabled (96 messages dropped, 259 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 464 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Trap logging: level informational, 206 message lines logged
Logging to 10.14.9.1, 206 message lines logged, xml disabled,
filtering disabled
Logging to 10.14.9.19, 206 message lines logged, xml disabled,
filtering disabled
Why are messages to my syslog server being dropped (96 so far)?
Regards
Dan
05-19-2008 06:18 AM
Dan
As far as i know sylog messages will be dropped when
a) the router hasn't made a connection to the syslog server yet ie. when it is rebooting the router may try to send a syslog message before it has established a connection with syslog server
b) the syslog server has gone down.
Has either of these things happened ?
Jon
05-20-2008 04:28 AM
The syslog protocol uses port no 514. The destination port 514 must be open in any intermediate or terminal devices like firewall or router.
05-20-2008 04:29 AM
The syslog protocol uses port no 514. The destination port 514 (UDP) must be open in any intermediate or terminal devices like firewall or router.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide