[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

6266.0. "Notify on SNMP-traps doesn't work...?" by STKHLM::BERGGREN (Nils Berggren,DC Sweden, 876-8287) Mon Apr 10 1995 15:22

Hi,

I'm having some strange problems at a customer site:

We have an alarm rule like:


MCC> sho domain SE_NS:.TELIA.C.HAN.CRT-LAN Rule TRAP_TEST all char

Domain SE_NS:.TELIA.C.HAN.CRT-LAN Rule TRAP_TEST
AT 10-APR-1995 14:10:35 Characteristics

Examination of attributes shows:
                             Expression = (occurs(snmp * any configuration
                                          event))
                               Severity = Minor
                         Probable Cause = Unknown

I have started a notification request for the domain in question like:

MCC>  notify domain .TELIA.C.HAN.CRT-LAN

This rule works fine when, for instance, a LinkUp or LinkDown trap is sent
to the DECmcc station.


But, if I start a notification request like:

MCC> notify domain .TELIA.C.HAN.CRT-LAN entity=(snmp *), -
                                        events=(any configuration event)

I don't get any notifications.

Issuing a GETEVENT-command works ok, though...


Why doesn't the notification request display the traps?  

Looking at the counters for MCC 0 TCPIP_AM SINK I see the traps coming in....

We're running DECmcc BMS V1.3 on VMS 5.5-2.


	Any ideas?
	
	Thanks,
	Nils Berggren
T.RTitleUserPersonal
Name
DateLines
6266.1User error, now fixed!STKHLM::BERGGRENNils Berggren,DC Sweden, 876-8287Wed Apr 26 1995 11:3614
Well,

it was a user error....

They had changed the IP-address on the node we tested the LinkDown 
and LinkUp traps on, so I guess that Notification Fm couldn't match
the event-sender to any object in the domain in question.

Now, when they have the correct address in MCC, everything works as
expected.


	Regards,
	Nils