Below is a snippit of the pertinant part of a config on one of my routers. The "show logging" indicates that items are being logged (via trap), but nothing's being sent to the logging host, "192.168.145.16". What am I missing? Is syslog on Cisco equipment via TCP, where if the syslog daemon isn't running, it won't log? --Otherwise, I thought syslog was UDP, so the routers blasts out packets & doesn't care if they reach a syslog daemon.
syslog on Cisco uses UDP so it should not be a TCP issue. Configuration looks ok and the show log info looks like the router thinks that it is sending to the syslog server.
From the config it looks like the syslog server should be connected on the local subnet through FastEthernet0/0. Can you confirm connectivity to the syslog server by pinging the 192.168.145.16 address from the router?
There are no access lists on the router interface, and assuming that the server is on the connected subnet there should not be any possibility of other router access lists along the path to the server.
Is there a possibility that the server is not configured correctly to receive and process the syslog messages from this router?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...