RES: [nv-l] NetView and TEC rules for detection of highly unstabl e link

2002-08-29 06:57:24
Subject: RES: [nv-l] NetView and TEC rules for detection of highly unstabl e link
From: Marcos Antonio Pezzutti Filho <pezzutti AT banespa.com DOT br>
To: "'anand anupam'" <ananda AT bharatpetroleum DOT com>, nv-l AT lists.tivoli DOT com
Date: Thu, 29 Aug 2002 07:57:24 -0300
First of all, you can implement a repeat counter rule in your rule base at T/EC, then it will be generated one event at the first time, after that the repeat counter is gonna be incremented.
Besides that, you can configure a rule-set or a script (in Netview) to filter the exceed messages.
-----Mensagem original-----
De: anand anupam [mailto:ananda AT bharatpetroleum DOT com]
Enviada em: Thursday, August 29, 2002 01:28
Para: nv-l AT lists.tivoli DOT com
Assunto: [nv-l] NetView and TEC rules for detection of highly unstable link

We are running NetView 6.0.2 on AIX 4.3.3 which is being integrated with TEC(3.7).
We are sending all (a) up/down events (b) reliability and (c) CRC error of all the links to TEC which correlates the events based on some logic and subsequently sends the notification alerts as well as automatically open trouble tickets(TT) in TSD.
Our problem is that, some link which becomes highly unstable( for some reason) sends so many events on TEC and TEC sends  excess mails and opens excess trouble tickets.
The exiting logic on TEC is to hold any down event for 5 minutes and if up event comes within 5 minutes then it neutralizes it otherwise it sends notification mails and open TT in TSD. Our purpose is not solved based on this logic for highly unstable links.
Initially, we tried hard to have some rulesets on NetView itself( before TEC)  but even after following PMRs it did not solved the issue and it was decided to address this at TEC level.
Can some one suggest some better logic to take care of this scenario? Is some extra events from routers has to be passed on to TEC from NetView? Just to mention that NetView is already having performance issue and we are less interested to stress it any more.
Looking forward from you guys please.


The information contained in this message is BPCL's Confidential and Proprietary information and is intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient, he/she is hereby notified that any use, dissemination, distribution, or copying of this communication or any of its content is strictly prohibited. In such case, please advise the sender immediately and delete it from your system. Further acknowledges that any views expressed in this message are those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of BPCL.


"Essa mensagem é destinada exclusivamente ao seu destinatário e pode

conter informações confidenciais, protegidas por sigilo profissional ou

cuja divulgação seja proibida por lei. O uso não autorizado de tais

informações é proibido e está sujeito às penalidades cabíveis.

This message is intended exclusively for its addressee and may contain

information that is confidential, protected by a professional

privilege or which disclosure is prohibited by law. Unauthorized use of

such information is prohibited and subject to applicable penalties."

<Prev in Thread] Current Thread [Next in Thread>
  • RES: [nv-l] NetView and TEC rules for detection of highly unstabl e link, Marcos Antonio Pezzutti Filho <=