"Davis, Donald" <donald.davis AT firstcitizens DOT com> writes:

> Is anyone using their NetView server as a Cisco Syslog Server.
> I have configured my Cisco equipment to send their syslog messages to my
> NetView server using the standard syslog port 514. I have written a perl
> script that continuously tails this log and generates SNMP traps for
> Emergency, Alert and various other messages and key words that appear in the
> log.
> 
> By the way, I have not configured the Cisco equipment to forward Cisco syslog
> messages as SNMP traps. The trapd log becomes a mess!
> 
> I am concerned that this might have been a bad idea.
> If both syslogd and trapd are being stormed with thousands of messages (syslog
> and traps) from hundreds or even thousands of routers and switches, what
> impact can syslogd have on the NetView application?

Syslogd isn't very processor intensive--it's IO intensive.  You could
mitigate this concern by throwing another interface in the box.  Use
the IP NIC1 as snmp trap destination and the default route out of the
box (so NetView uses it for its outbound traffic), and then nic2's IP
address as the syslog target for all the Cisco boxen. 

We do this and it seems to be working nicely. 

-- 
Todd H.
http://www.toddh.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)