Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Invalid Syslog Messages

We are running Ciscoworks 3.1 with RME 4.2.0 and have about 600 devices sending syslog messages to the server. In the Syslog Collector Status we see a small number of Invalid messages.

How can I figure out which devices are sending the Invalid syslog messages? If I copy the syslog.log file from the server, what do I need to search for to identify Invalid messages and is there any documentation on CCO that defines what Ciscoworks Syslog Collector considers an Invalid message format?

1 ACCEPTED SOLUTION

Accepted Solutions
Blue

Re: Invalid Syslog Messages

One possible source of invalid logs is PIX firewalls sending syslogs in non-EMBLEM format.

3 REPLIES
Blue

Re: Invalid Syslog Messages

One possible source of invalid logs is PIX firewalls sending syslogs in non-EMBLEM format.

New Member

Re: Invalid Syslog Messages

We have an FWSM module and several ASA-5505 all reporting syslog messages to Ciscoworks successfully using the Emblem format.

I'll check with the rest of my group to see if there are any other PIX devices that we don't manage that might be configured to forward syslog messages to our Ciscoworks server.

Thanks.

New Member

Re: Invalid Syslog Messages

We have an FWSM module and several ASA-5505 all reporting syslog messages to Ciscoworks successfully using the Emblem format.

I'll check with the rest of my group to see if there are any other PIX devices that we don't manage that might be configured to forward syslog messages to our Ciscoworks server.

Thanks.

191
Views
0
Helpful
3
Replies