[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

6074.0. "How to define alarms for traps" by COL01::LOPEZ (Arturo Lopez drinks K�lsch at Cologne) Tue Aug 09 1994 13:26

Hi Friends,

a customer uses DECmcc V1.3 and the Mike managament modul for Hirschmann star
coupler.

He defined an alarm for the snmp traps of this card.

One trap is VenLinErr, which is sent, when the Fiber Optic line changes status.
This trap contains more information as text information.

The customer defined the trap with

	(OCCURS (SNMP * VenLinErr))
	severity = critical

The problem he has, is that the trap is sent, when the line goes DOWN and
UP.

So he cannot see the difference by just looking at the color of the icon.

I tried to define a CHANGE_OF rule for this trap. But it did not work.

Is there a possibility to use the text information in the information field 
to define the severity of a trap ?

Which RFC defines the traps ?


Arturo Lopez
Cologne Germany

T.R Title User Personal
Name Date Lines

6074.1 some answers AZUR::PHOBOE::Flauw C.E.M. Technical Office, Valbonne Thu Aug 11 1994 10:04 32

T.R	Title	User	Personal Name	Date	Lines
6074.1	some answers	AZUR::PHOBOE::Flauw	C.E.M. Technical Office, Valbonne	`Thu Aug 11 1994 10:04`	32
	Arturo, I am not an SNMP specialist, but as your note has been left un-answered by the SNMP specialist so far, I will give it a try. Up to my knowledge, in SNMP V1, the trap is defined in the SNMP protocol and the trap PDU format does not include a severity field. The fact that the trap might be a high severity alarm or a clearance alarm is only coming from the value of an attribute in the VarBindList. The Alarms FM is doing what you are asking it to do : generate an alarm of severity critical when receving this trap. The Change_of rule can only be used for change of value of an attribute and does not apply to events. One thing which is not clear in your original note is the access module that you are using : is it the SNMP AM or is it a specific access module ? Depending on the answer, you might have different way of fixing the problem, but the only ones I see involve some coding. If it is a private AM, change the getevent entry point to analyze the incoming event and depending on the value of the attribute add in the getevent response the appropriate target severity. If you are using the SNMP AM, then you will have to do a small FM that provides at function level the getevent entry point for your entity. The FM waits on the events coming from the SNMP AM (might be only the event you are interested in) and when receiving one, does the same processing as above. Hope this helps, Best regards, Marc.

Arturo,

I am not an SNMP specialist, but as your note has been left un-answered by 
the SNMP specialist so far, I will give it a try. 

Up to my knowledge, in SNMP V1, the trap is defined in the SNMP protocol 
and the trap PDU format does not include a severity field. The fact that 
the trap might be a high severity alarm or a clearance alarm is only coming 
from the value of an attribute in the VarBindList. 

The Alarms FM is doing what you are asking it to do : generate an alarm of 
severity critical when receving this trap. The Change_of rule can only be 
used for change of value of an attribute and does not apply to events. 

One thing which is not clear in your original note is the access module 
that you are using : is it the SNMP AM or is it a specific access module ?

Depending on the answer, you might have different way of fixing the 
problem, but the only ones I see involve some coding. If it is a private 
AM, change the getevent entry point to analyze the incoming event and 
depending on the value of the attribute add in the getevent response the 
appropriate target severity. If you are using the SNMP AM, then you will 
have to do a small FM that provides at function level the getevent 
entry point for your entity. The FM waits on the events coming from the 
SNMP AM (might be only the event you are interested in) and when receiving 
one, does the same processing as above.

Hope this helps,

Best regards,

Marc.