Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[NV\-L\]\s+Netview\s+Status\s+Request\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[NV\-L\]\s+Netview\s+Status\s+Request\s*$/: 4 ]

Total 4 documents matching your query.

1. [NV-L] Netview Status Request (score: 1): Author: "Marcelo Zacchi" <mzacchi AT gmail DOT com>; Date: Tue, 26 Sep 2006 07:51:09 -0300; Dear list members, I've been having a lot of stress in my environment due to oscilations in object status in Netview. We have created an adapter to open up TroubleTickets for each NODE DOWN event tha; /usr/local/webapp/mharc-adsm.org/html/nv-l/2006-09/msg00087.html (12,412 bytes)
2. Re: [NV-L] Netview Status Request (score: 1): Author: Leslie Clark <lclark AT us.ibm DOT com>; Date: Tue, 26 Sep 2006 07:44:55 -0400; The timeouts and retries are set in xnmsnmpconf (Options..SNMP). The defaults are 2 seconds, 3 retries. This is an adjustment that you should increase in very small increments. I can recommend the ne; /usr/local/webapp/mharc-adsm.org/html/nv-l/2006-09/msg00089.html (15,814 bytes)
3. Re: [NV-L] Netview Status Request (score: 1): Author: "Marcelo Zacchi" <mzacchi AT gmail DOT com>; Date: Tue, 26 Sep 2006 09:09:53 -0300; Leslie. Thanks for your replay. I have changed the nvsync_timeout value in the netview.rls and am now waiting to see if it helps. Since the netview.rls is the first ruleset to run, I don't have to ch; /usr/local/webapp/mharc-adsm.org/html/nv-l/2006-09/msg00090.html (18,883 bytes)
4. Re: [NV-L] Netview Status Request (score: 1): Author: "Marcelo Zacchi" <mzacchi AT gmail DOT com>; Date: Tue, 26 Sep 2006 14:45:16 -0300; Leslie, Apparently it worked! Thanks again! The only problem now, though, is that in every polling sequence when Netview is updating the map, the process netview.exe uses 100% of the processor, and t; /usr/local/webapp/mharc-adsm.org/html/nv-l/2006-09/msg00092.html (19,918 bytes)

Current List: 1 - 4
Page: [1]