You didn't mention which version of CiscoWorks suite or the platform you're using.
It should be stated that the Syslog reception is really a component of the operating system - not the CiscoWorks Common Services or RME components.
On Solaris the syslog daemon manages the process through the configuration of /etc/syslog.conf. Part of the install process modifies that file and punts the 'local7' facility and 'info' severity.
Windows 2000 didn't have an embedded Syslog receiver so we had to add one to the operating system. Same prinicpal tho - Syslog comes in, operating system grabs it and puts into a file - CiscoWorks RME watches the file for updates and injects the info into an embedded database for processing.
On Solaris you could simply enhance the /etc/syslog.conf file to put the messages in /var/log/syslog_info (default) AND forward to another machine, but when you do that the syslog's source address becomes the Syslog forwarding system - that's not desirable in many cases.
In this kind of scenario I'd recommend you look at the Syslog-NG open source tool and replace your syslog daemons with that. It WILL preserve your Syslog headers and allow a multi-tiered solution, if you need to.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.