Crew,
I've been experimenting with implementing TCP syslog with multiple devices in my network, and I've come across a few instances where it stops and doesn't recover. For instance, there was an extended maintenance where we reloaded one of our routers and it never seemed to restart the TCP syslog.
Here's what I get from a "show logging"
Trap logging: level informational, 681 message lines logged
Logging to 10.1.40.159 (tcp port 5170, audit disabled,
link down),
0 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 10.1.121.27 (udp port 5170, audit disabled,
link up),
183 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging Source-Interface: VRF Name:
Loopback64
Here are the logging-related configuration elements:
service timestamps debug datetime msec show-timezone year
service timestamps log datetime msec show-timezone year
logging buffered 64000
clock timezone EST -5
clock summer-time EDT recurring
logging source-interface Loopback64
logging host 10.1.40.159 transport tcp port 5170
logging host 10.1.121.27 transport udp port 5170
And here is my IOS version:
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Mon 16-Apr-12 16:12 by prod_rel_team
The server is up but was unreachable for a time. However, I am concerned that once the link is down, it seems to stay down and there are no outward signs that it has tried to reconnect. On at least one other device, removing and readding the host worked, but that's not something I want to continuously test and alert on.
Any ideas?
++I;
