To: | <nv-l@lists.tivoli.com> |
---|---|
Subject: | [nv-l] Flooding TEC |
From: | "Delaire, Patrick" <delairep@aetna.com> |
Date: | Tue, 17 Jun 2003 16:38:21 -0400 |
Delivered-to: | mailing list nv-l@lists.tivoli.com |
Delivery-date: | Wed, 18 Jun 2003 09:16:14 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
List-help: | <mailto:nv-l-help@lists.tivoli.com> |
List-post: | <mailto:nv-l@lists.tivoli.com> |
List-subscribe: | <mailto:nv-l-subscribe@lists.tivoli.com> |
List-unsubscribe: | <mailto:nv-l-unsubscribe@lists.tivoli.com> |
Mailing-list: | contact nv-l-help@lists.tivoli.com; run by ezmlm |
Thread-index: | AcM1EGQB9762hTgaSSiN/eYIPMU//Q== |
Thread-topic: | Flooding TEC |
We are running AIX 4.3 with Netview 7.1.3. Our new IVR (voice response system) is sending SNMP data to our Netview platform which is then forwarded to TEC. The problem we are experiencing a times is our IVR application/s including speechworks and conversant servers machine gun both Netview and TEC when we experience problems. This results in TEC buffering messages and eventually stop functioning. The voice response people cannot do any more filtering from the source. Does any one on this list have any suggestion on how we could stop 'machine gun' type alert processing either on the Netview side or TEC side. Side note: We have filtering on TEC but only after the alerts has been processed through TEC. The buffering issue occurs before the alerts are processed, which at times bring down TEC. P.S. We have disabled MLM. Automation & Systems Monitoring
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Flooding TEC, Ray Westphal |
---|---|
Next by Date: | RE: [nv-l] Flooding TEC, James Shanks |
Previous by Thread: | Re: [nv-l] Flooding TEC, James Shanks |
Next by Thread: | RE: [nv-l] Flooding TEC, Ray Westphal |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web