[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

2948.0. "Notification being stopped" by MQOSWS::S_CHARBONNEA () Wed May 06 1992 17:11

    
    
Map Window Message: Notification being stopped for Domain ....
                      %MCC-E-DNSERROR, unknown DNS error

BMS 1.1.0 
I am polling Chipcom devices with SNMP access module

I have the above message every day at a custumer site.

Question: How could I trace to get more information on this error.
          (logical name for debugging, log file to look at...)


Any help please

NIS consultant 
Sylvain
    
                
T.RTitleUserPersonal
Name
DateLines
2948.1getting more infoDADA::DITMARSPeteThu May 07 1992 16:2923
Depending on when you're getting this, it could be something detected by the
IMPM or something detected by the notification FM.

When does it happen?  At/near startup?  At random times?  In response to certain
user activities (e.g. opening a new domain), or in response to certain alarms 
firing?

Until we know these kinds of things, it'd be useless to have you start turning 
on logbits.

Does the site use DNS for anything else and, if so, have they been encountering
errors in those applications?


Perhaps try running an equivalent set of notify requests in FCL.  The equivalent
set would be 

	notify domain <domain>

one for each domain in the customer's dynamic domain hierarchy that is open
when these errors occur.  This may help you to determine if its a certain
alarm rule firing that causes it.  It may also help narrow it down to either
IMPM or Notification FM.
2948.2More infoMQOSWS::S_CHARBONNEAFri May 08 1992 12:5819
Thanks Pete 

Here are some more information

The station is used ONLY for DECmcc
DECmcc is the unique program using DNS
The problem occurs at the end of the day, in response to certain alarms firing.
The alarm firing is on CHIPCOM HUB using SNMP AM.
3 patches are installed:
  ALARMS, KERNEL1, and KERNEL2.


I will try the FCL and I will get back to you

Thanks again

NIS Consultant

Sylvain
2948.3backtranslation problems?DADA::DITMARSPeteFri May 08 1992 13:2112
Good work.

Do a show all ident of the entity that is being polled by the alarm rule.

Do the same from FCL using all of the alternate identifiers of the entity.

Perhaps we're failing trying to translate the primary SNMP identifier (which
is what comes up through alarms/notification) back into a fullname.  The IMPM 
does this in order to perform correlation.  If this is it, it's been so long 
since I encountered this stuff, that I forget if I ever knew how to fix it. 
I'll ask around.

2948.4if it turns out to be a problem getting the identifiers....DADA::DITMARSPeteTue May 12 1992 11:087
you may have to de-register and re-register the specific entity.  this can
be ugly, as the UID for the entity may be stashed in various places.  If the
entity only exists in one domain, it's probably best to do this from IMPM
and immediately save the map file.  Then it's down to historian/exporter.

Anybody else who's had experience in fixing this stuff, please correct the
above suggestion if it's wrong.