Conference netcad::hub_mgnt

179.0. "Unexplained DECagent Behavior w/MCC on VMS" by MAIL::CLAYTON (Merlin Clayton DTN 445-7217) Tue Mar 09 1993 12:42

Since I have not received a response to this note in the MCC notes file,
I'll try it here with hope for better success.

--------------------------------------------------------------------------------
In my demo center environment which I manage with mcc on VMS, I have a DEChub 
with the DECagent 90 installed and a Proteon p4100 router both running SNMP 
agents.

I have both SNMP devices set up to generate traps to the IP address of my 
mcc station.  I have a few different alarms rules defined to capture the traps
generated by the SNMP agents.  One rule is an "Occurs" rule for 'Any Event'
from any SNMP entity.  The other rule is an "Occurs" rule for a 'coldStart'
event from any SNMP entity.

With thes rules enabled, I reset the Proteon router to generate the 'coldStart'
trap.  Sure enough, the Proteon box generates the trap, but when I receive
notifications on the mcc map and notifications windows, both the DECagent 90
and Proteon entities show the notification for the proteon router - both icons
turn color, and I get two notifications posted in the notification window one 
for each entity.

The notification for Proteon 'coldStart' was passed through the DECagent 90,
but my question is "why?".

This is undesirable behavior I think - any other opinions?

Is there something that I have set up incorrectly, or is there something that
the DECagent is doing that it shouldn't?

Thanks.

Merlin
DTN 445-7217
TRIGG::CLAYTON

    What version of the DECagent 90 are you running?  V1.0 does not
    generate any traps.  Why the router's trap seems to be going "through"
    the DECagent is a mystery.
    
    ...Roger...