[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

929.0. "ALARMS in conflict with SNMP?" by KETJE::PACCO () Wed Apr 17 1991 16:03

    Is there a conflict between the ALARMS FM and the TCP/IP AM ?
    
    With the latest version of MCC BMS I always get the MAP Window Message:
    
    Notification Structures may be corrupted, please disable notification,
    
    if I have enabled Alarm notification, an then try to go into a domain
    which has only TCP/IP entities. Once the Alarms notification disabled,
    I can enter that TCP/IP domain.
    
    Any idea ?
    Regards,
    Dominique.

T.R	Title	User	Date	Lines
929.1	really!	TOOK::CALLANDER	`Wed Apr 17 1991 20:16`	10
	This is a new one. The notification structures spoken about in the message are PM structures. They have nothing to do with the Alarms FM. The map calls the notification FM to process the NOTIFY command, the structures are used to store the entity information regarding the nodes in the domain (or so it was my understanding). I have a feeling that since the SNMP AM had to be hard coded for anumber of other items in the map, one of those special cases regarding the naming of the entity might not have made it into the notification structure support. I will ask the originator of those functions to get back to you. But this is my guess, and I am sure Christine will correct any errors in my assumptions.
929.2	bug; here's a workaround	TOOK::HAO	`Wed Apr 17 1991 20:53`	23
	Fortunately (unfortunately?), we just found this problem ourselves today. The problem only exists when attempting to double-click into the last dynamic domain that was added as a member of the parent domain. As a workaround, simply add a dummy domain as a member of the parent domain. You should now be able to double-click into your domain of SNMP entities. For anyone interested in the implementation details of the problem, read on: When notification is enabled, the Iconic Map PM maintains a set of notification structures that correspond to the domain hierarchy. To set up the domain hierarchy, the Iconic Map PM calls the Domain FM. Unfortunately, the Domain FM did not return the last dynamic domain; therefore, the IMPM did not create an entry in the notification structures for it. When double-clicking into that domain, the IMPM attempts to access the notification structures for that domain. Not finding it (which should NEVER happen if the code works properly), the IMPM assumes the structures are corrupted and prints an error message. Christine
929.3	one more thing...	TOOK::HAO	`Thu Apr 18 1991 11:55`	6
	I forgot to mention that in the workaround, you need to re-open your domain after adding your dummy child domain. Things should work fine from then on. Christine
929.4	Help!!!	BSS::T_ESTES	`Wed Nov 06 1991 15:31`	20
	I guess that I don't have it right yet. I too am getting the error and have tried to add the "dummy" domain and still can't get it to work correctly. I currently have: A (domain) \| B (domain) entity 1,2,3... \| C (domain) entity 1,2,3... \| D (domain "dummy") Is this correct placement of the "dummy" domain? If not where does it belong? Help..... Tim
929.5	Help!!! again	GOONS::CHAPMAN	`Thu Dec 12 1991 10:49`	4
	Could someone respond to this? I am also having this problem and it's causing grief. Thanks
929.6	Has this problem been resolved in BMS V1.2?	CX3PT2::SHOTO::W_MCGAW	`Wed Sep 16 1992 14:47`	9
	Hi, Has this problem been fixed for BMS V1.2? We are starting to see more occurances of this problem from customers calling into the Colorado Support Center. Should this be an SPR? Walt
929.7	fixed	NENE::LEMMON	`Thu Sep 17 1992 12:14`	3
	Fixed in v1.2. /Jim