LMS 3.1 Not able to find SYSLOGS messages for few devices.

Unanswered Question
Aug 26th, 2009

CISCO LMS APPLICATION VERSION 3.1. SYSLOGGING IS NOT WORKING for few devices.Devices type catalyst switches IOS and CAT OS based.

I have checked the snmp configuration it is as per the standard configuration recommended by cisco.

Can u let me know how to start troubleshooting on this issue.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Wed, 08/26/2009 - 23:05

Are the syslog messages being sent from the devices? Post the show run from one of the affected devices? Check the syslog.log (Windows) or syslog_info (Solaris) files to see if messages are arriving to the LMS server from these devices. If they are, post sample messages as well as a screenshot of RME > Tools > Syslog > Syslog Message Filters.

mvnaveenforever Thu, 08/27/2009 - 01:16

Hi,Pls check the atttachements.

Are the syslog messages being sent from the devices?Ans:No sys log mes are not sent from this device.

Pls let me what should be the possibilities.Thnaks

Attachment: 
Joe Clarke Thu, 08/27/2009 - 08:45

Assuming 10.145.50.168 is the IP address of the LMS server, then you need to add "set logging server enable" so that messages will be sent to the server.

mvnaveenforever Thu, 08/27/2009 - 22:12

Hi,

the LMS Ip is right as u have assumed. configured set logging server enable

on the switch and but facing the same issue.No syslogs getting generated on LMS.

Joe Clarke Thu, 08/27/2009 - 22:49

What messages do you see generated on the switch itself? that is, if you run "show logging buff" what messages do you see? And just to be clear, the messages you see in the logging buffer are NOT seen in the syslog.log on the server?

Joe Clarke Mon, 08/31/2009 - 22:20

The messages must not be making it to the server. Something must be blocking udp/514 in the network. You can start a sniffer trace on the LMS server filtering on udp/514 traffic from this switch to confirm. Then, if no packets are seen check with your network security team to see if any firewalls or ACLs are blocking that port.

Actions

This Discussion