We have two 2901 routers and want to log the messages to a syslog server. This works, but only a few messages are send to the server:
For example, while the "show logging" command shows up all logged messages like this:
Oct 8 16:30:57.824 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0/0, changed state to down
Oct 8 16:30:57.824 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan5, changed state to down
Oct 8 16:30:58.828 CEST: %LINK-3-UPDOWN: Interface FastEthernet0/0/0, changed state to down
Oct 8 16:31:08.620 CEST: %LINK-3-UPDOWN: Interface FastEthernet0/0/0, changed state to up
Oct 8 16:31:09.620 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0/0, changed state to up
Oct 8 16:31:37.625 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan5, changed state to up
Oct 8 16:45:10.553 CEST: %SYS-5-CONFIG_I: Configured from console by console
.Oct 8 16:48:02.514 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0/0, changed state to down
.Oct 8 16:48:02.514 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan5, changed state to down
.Oct 8 16:48:03.514 CEST: %LINK-3-UPDOWN: Interface FastEthernet0/0/0, changed state to down
.Oct 8 16:48:03.514 CEST: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.0.7 port 514 started - CLI initiated
.Oct 8 16:48:10.202 CEST: %LINK-3-UPDOWN: Interface FastEthernet0/0/0, changed state to up
.Oct 8 16:48:11.202 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0/0, changed state to up
.Oct 8 16:48:39.206 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan5, changed state to up
Oct 8 16:52:06.667 CEST: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 16:54:10.092 CEST: %SYS-5-CONFIG_I: Configured from console by console
The logfile of out syslog server receives only part of this messages:
Oct 8 12:29:48 192.168.0.10/192.168.0.10 44: Oct 8 10:30:48.937 UTC: %SYS-5-CONFIG_I: Configured from console by admin on vty0 (192.168.0.7)
Oct 8 12:36:52 192.168.0.10/192.168.0.10 45: Oct 8 10:37:52.319 UTC: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 13:28:46 192.168.0.10/192.168.0.10 46: Oct 8 12:29:46.686 UCT: %SYS-6-CLOCKUPDATE: System clock has been updated from 11:29:46 UTC Fri Oct 8 2010 to 12:29:46 UCT Fri Oct 8 2010, configured from console by console.
Oct 8 13:30:51 192.168.0.10/192.168.0.10 47: Oct 8 13:31:52.315 CEST: %SYS-6-CLOCKUPDATE: System clock has been updated from 12:31:52 UCT Fri Oct 8 2010 to 13:31:52 CEST Fri Oct 8 2010, configured from console by console.
Oct 8 13:32:44 192.168.0.10/192.168.0.10 48: Oct 8 13:33:44.691 CEST: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 13:51:06 192.168.0.10/192.168.0.10 49: Oct 8 13:52:06.649 CEST: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 13:52:19 192.168.0.10/192.168.0.10 50: Oct 8 13:53:19.701 CEST: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 16:13:14 192.168.0.10/192.168.0.10 57: Oct 8 16:14:14.651 CEST: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 16:27:57 192.168.0.10/192.168.0.10 58: Oct 8 16:28:57.732 CEST: %SYS-5-CONFIG_I: Configured from console by console
Oct 8 16:53:09 192.168.0.10/192.168.0.10 64: Oct 8 16:54:10.092 CEST: %SYS-5-CONFIG_I: Configured from console by console
We are using a Linux syslog-ng server, but this problem is not limited to this server, as a kiwi syslog server with windows also receives the same messages as the linux server. Therefore, I think this is not a configuration problem of the syslog-servers.
Especially the LINK-3-UPDOWN and LINEPROTO-5-UPDOWN messages are not logged.
The logging is configured as follows:
cisco-1(config)#logging 192.168.0.6
cisco-1(config)#service timestamps debug datetime localtime show-timezone msec
cisco-1(config)#service timestamps log datetime localtime show-timezone msec
cisco-1(config)#logging facility local6
cisco-1(config)#logging trap debugging
cisco-1(config)#logging count
cisco-1(config)#end
