Nothing needs to be done in CiscoWorks. You just need to configure your device to send syslog messages to the RME server. This is typically done with the command:
Where x.x.x.x is the IP address of the RME server. RME will then process the messages, and add them to its database (assuming the device is already managed). Once in the database, you can run reports to see the collected messages.
Thanks clarke, as you are helping me second time over here.. previous problem was high memory utilization for which i opened a case and tac is helping me. Ok, in here, i am getting all the logs from the devices except the logs like "device has rebooted", rather getting only link down logs. Is it possible to get such logs which clearly says that the device has got rebooted or like that.
The device will send all of its syslog messages to RME. However, some messages may not make it since the network has not converged, and there is no way to send the UDP packet. RME has a built-in report to track device reloads called the Reload Report (under RME > Reports > Report Generator > Syslog). If the device could send one of the messages matching the patterns:
Could you please give me some document on how to optimize the ciscoworks so as to increase the performance. And would like to know what to be done when LMS is getting hung intermetenly and unable to access the portal.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...