Conference azur::mcc

3429.0. "Wierd Alarms Events with Proteon p4100" by MAIL::CLAYTON (Merlin Clayton DTN 445-7217) Fri Jul 24 1992 19:54

I'm trying to manage a Proteon p4100 router in our demo center using SNMP.

As part of the DECmcc demo I set up a simple alarm to check the SNMP status
(ipreachability) of the p4100 during the demo.  If the ipreachability is not
= "up", or otherwise indeterminate, the alarm would fire.  During the demo
then, I could power off the router and watch the alarm fire.  The seems
realatively simple and straight forward.  

However, when I enable the alarm, while the p4100 is still operational, the 
alarm begins firing because it tests "true".  Then, a few minutes later a 
"clear" notification is posted.   This continues as long as the alarm is
enabled.  While this is going on, if I show the SNMP Status of the p4100,
it always shows ipreachability=up.

I've tried to dance around this in demos, but I need some resoultion, or
at least understanding so I can explain it when it happens.  

Has anyone else ever had any experience with the Proteon p4100?   Could this
indeed be a problem with the router, or might it be a problem with the
mcc alarms procedures?

Any insight would be greatly appreciated.

Thanks.

Merlin