Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+Off\s+Subject\s+\[syslog\]\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+Off\s+Subject\s+\[syslog\]\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [nv-l] Off Subject [syslog] (score: 1): Author: Leslie Clark <lclark AT us.ibm DOT com>; Date: Fri, 17 Jan 2003 14:04:06 -0500; Would it help, or make sense, to have a second adapter on the Netview box, and have that one used for incoming traps and syslog data, and the other one used by netview (its default) for status pollin; /usr/local/webapp/mharc-adsm.org/html/nv-l/2003-01/msg00206.html (14,607 bytes)
2. Re: [nv-l] Off Subject [syslog] (score: 1): Author: netview AT toddh DOT net (Todd H.); Date: 17 Jan 2003 13:29:33 -0600; 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; /usr/local/webapp/mharc-adsm.org/html/nv-l/2003-01/msg00208.html (12,337 bytes)
3. Re: [nv-l] Off Subject [syslog] (score: 1): Author: Stephen Hochstetler <shochste AT us.ibm DOT com>; Date: Fri, 17 Jan 2003 12:39:36 -0600; Hi Don, Been a while since I have seen you! A long time ago setup some Cisco Firewalls to send their syslogs to a NetView server. When I think about what the issues are for storms I think of.... 1) s; /usr/local/webapp/mharc-adsm.org/html/nv-l/2003-01/msg00210.html (12,582 bytes)
4. [nv-l] Off Subject [syslog] (score: 1): Author: "Davis, Donald" <donald.davis AT firstcitizens DOT com>; Date: Fri, 17 Jan 2003 12:49:54 -0500; 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 writt; /usr/local/webapp/mharc-adsm.org/html/nv-l/2003-01/msg00211.html (12,331 bytes)

Current List: 1 - 4
Page: [1]