MonitorWare Knowledge Base

I'm testing logger as a syslog server on routers. I'm failing an interface as a test, but the messages are not being captured by the syslog server. The syntax I am using for logger is as follows:

logger -f C:\Syslog\Logs\logfile.txt -l 172.24.32.109 -a 514

Am I missing something?

Thanx,
Greg

Hi,

what is the exact response you get when you execute this command?

Hi...

I see you banner page and in the DOS Window, I get the Adiscon welcome along with:

logging to 172.24.32.109:514

I believe 514 is the port Cisco uses for Syslog. I've tried with and without the -a 514 option.

hrm as syslog uses UDP there is no way to make sure that message was received 100%.

Well in order to test if logger works on your machine, you can try WinSyslog for receiving Syslog messages: see www.winsyslog.com .

And what kind of Cisco are you using? I mean which kind of device ?

I'm testing using a Cisco Router, 3640 to be exact. The router is on the same segment as the Syslog server, so there is no firewall or other gateway device in between. Here are the Cisco commands I have configured.
logging history debugging
logging trap debugging
logging source-interface Ethernet0/0
logging 172.24.32.109

The e0/0 address is 172.24.32.2

w, when I click on the link specified, I get the following message:

Directory Listing Denied
This Virtual Directory does not allow contents to be listed.

there was a DOT to much in the link
If you have a Cisco router, it maybe only *sends* it's logging information and not receive it.

Then WinSyslog will be the right application for you in order to receive logs from your router.

This article also might help you: http://www.monitorware.com/en/FAQ/How-t ... syslog.asp

That worked

Last question, can I get WinSyslog to run as a service so that it doesn't have to be started manually across reboots and so that I do not have to leave system logged in?

Hi,

The WinSyslog Service is installed as a system service during setup. The WinSyslog Service can be "engine only" installed. In this case, only the service is installed onto a machine. It can be customized either by directly editing the registry or copying a registry snapshot from a machine with installed client. Please note that "Engine Only" installs need a full WinSyslog license.

Regards,
Tamsila Siddique.
Adiscon.

elittos, WinSyslog already runs as Service so it automatically works when you reboot