[Date Prev]   [Date Next] [Thread Prev]   [Thread Next] [Date Index]   [Thread Index]

 

     [nocol-users] BGPMon - Too quick on the draw 
Hi,

	Wondering if anyones seen this with BGPMON.  The RCS header on the
one I'm running is 2.1 .

	If I have something in the file such as :

severity        13945    E_CRITICAL

	It appears that if that peer goes down, it goes straight from 
WARNING to CRITICAL in the same second :

 Warning - Sat Sep 30 10:52:00 2000 [bgpmon]: SITE ttsg 172.16.101.1 VAR BGP
/ttsg 0 0 State LEVEL Warning LOGLEVEL Warning NOCOP down
===
 Warning - Sat Sep 30 10:52:00 2000 [bgpmon]: SITE ttsg 172.16.101.1 VAR BGP
/ttsg 0 0 State LEVEL Error LOGLEVEL Error NOCOP down
===
 Error - Sat Sep 30 10:52:00 2000 [bgpmon]: SITE ttsg 172.16.101.1 VAR BGP/t
tsg 0 0 State LEVEL Error LOGLEVEL Error NOCOP down
===
 Warning - Sat Sep 30 10:52:00 2000 [bgpmon]: SITE ttsg 172.16.101.1 VAR BGP
/ttsg 0 0 State LEVEL Critical LOGLEVEL Critical NOCOP down
===
 Error - Sat Sep 30 10:52:00 2000 [bgpmon]: SITE ttsg 172.16.101.1 VAR BGP/t
tsg 0 0 State LEVEL Critical LOGLEVEL Critical NOCOP down
===
 Critical - Sat Sep 30 10:52:00 2000 [bgpmon]: SITE ttsg 172.16.101.1 VAR BG
P/ttsg 0 0 State LEVEL Critical LOGLEVEL Critical NOCOP down

(Copy of a dump from a script called out of noclogd)

	Has anyone else run into this?  Is there a newer version that doesn't
do this?

		Tuc/TTSG