| To: | "NVList \(E-mail\)" <nv-l@lists.us.ibm.com> |
|---|---|
| Subject: | [nv-l] Object Acknowledgement kills Netview |
| From: | "Brian Kraftchick" <Brian.Kraftchick@odfl.com> |
| Date: | Mon, 8 Aug 2005 13:59:17 -0400 |
| Delivery-date: | Tue, 09 Aug 2005 00:47:47 +0100 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
| Thread-index: | AcWcQs9r9Y0clBb2THi3di7WmUWQXA== |
| Thread-topic: | Object Acknowledgement kills Netview |
|
Netvew 7.1.2 on Win2K Could anybody help me figure out why when I acknowledge an "alarmed" (red) object and it's status color propogates the change up through a series of maps that the Netview applications goes to a "Not responding" state, and the NetView.exe process eats up about 50% of the CPU, and NetView itself is unuseable for about 5 minutes ? It does come back, but it seems that this is really performing poorly, and on a system that isn't being taxed in any shape or form. This only happens when the object that is being acknowledged is the last one on a map in an alarmed state such that once acknowledged the propogation of that acknowledgment "up the chain" takes a toll on the server and NetView application. -
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [nv-l] traitor, Allison, Jason \(JALLISON\) |
|---|---|
| Next by Date: | [nv-l] Switch Analyser, Kelly Root |
| Previous by Thread: | [nv-l] traitor, Allison, Jason \(JALLISON\) |
| Next by Thread: | [nv-l] ITSA unset L2 Status, Mario Behring |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web