[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

5010.0. "MCC alarms and DNS-E-NOCOMMUNICATION" by MLNCSC::BARILARO () Thu May 06 1993 06:29

    
    Cross posted on DNS notes file
    
    
    Hi,
    
    	I've a randomly problem on the communication between MCC v1.2 and
    	DNS v1.1.
    
    	Sometime (randomly...) the alarm rules of MCC generate exceptions,
    	the reason is: DNS-E-NOCOMMUNICATION unable to communicate with
    	DNS server....
    
    	It isn't a protection or access problem, in my own opinion the 
    	problem is the number of polling that the alarm rules generate,
    	my customer use only polling like alarm rules, something like:
    	
    	SNMP * ipreachability up	or
    	Bridge * device state <> operating  	etc.etc.
    
    	As I said it's a randomic problem, for 10 minutes all the alarm
    	rules generate exceptions, after this period they restart..
    	A more rapid workaround to make the rules working is to stop and
    	restart DNS manually.
    
    	So, I know that the SOLUTION is to modify the alarms to reduce the
    	number of polling, BUT I'd like to know if exist a workaround or
    	a patch directly on DNS, I tried to augment the paramater (BUFIO,
    	Working set, AST etc.etc.) on the DNS processes but doesn't help,
    	I also tried to augment the DECNET buffers...
    
    	Could somone address me in the right direction ????
    
    					Thanks in advance,
    					Ciao 	Luciano
T.RTitleUserPersonal
Name		DateLines
5010.1Check CSC for DNS patchesCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentTue May 11 1993 14:3912
    Luciano,
    
    There are numerous patches for DNS V1.1.  There are two or three
    specifically created to fix DECmcc problems.
    
    Contact the Colorado Customer Support Center for more info.  Try
    CSC32::BINGHAM (Scott) if you have direct questions.  The CSC will be
    able to search through their database to determine which patches are
    available for specific problems.  Also, they can tell you exactly what
    images (with link date & version) that you should be running.
    
    -Dan
5010.2Basic DNS TroubleshootingCSC32::BINGHAMScott Bingham �� Windows NT Focus Team, CSCMon Oct 18 1993 13:5242
                Hello DECmcc people,

                I appreciate Dan's kind words, but I am no longer
        the person to call for this product set.  (I never was for
        folks outside of the USA -- there are very good DNS people
        in other parts of the world.)

                This sounds like a DNS management problem.  For
        this particular symptom, I would suggest beginning via the
        following steps:

                  1.  Enable DECnet Events for *all* DNS
                  Events -- 352.* and 353.* events.  Do
                  the command which causes the problem,
                  which should now cause a network event,
                  which should now provide an underlying
                  status, which should lead a DNS-
                  knowledgeable person to the problem.

                  2.  If you get no underlying status,
                  then the most common problem is that
                  the user has replaced some or all of
                  their DNS clerk files with the older
                  files that were originally released
                  with the DNS V1.1 Server kit.  Those
                  older files have been obsolete since
                  VMS V5.3, which is when DNS clerk files
                  were first released as part of VMS. 
                  Use ANALYZE/IMAGE to get link dates and
                  times.  Files from before ~1990 are bad
                  news.

                  3.  I know of no *patch* for this
                  particular symptom.  Generally, patches
                  for DNS should be in Stars and TIMA.

                Caveat:  I was a DNS person; I was never a DECmcc
        person.  DECmcc's stuff is considered data by DNS.

                I hope that this helps,
                _Scott
5010.3Example: Proper versions for VMS V5.5-2CSC32::BINGHAMScott Bingham �� Windows NT Focus Team, CSCMon Oct 18 1993 14:0831
DNS Clerk files for VMS V5.5-2
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSEXE]DNS$ADVER.EXE;2        0 err
ors
                image file identification: "DNS V5.5-100"
                link date/time:  8-JUL-1992 01:21:51.23
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSEXE]DNS$ANALYZE.EXE;2      0 err
ors
                image file identification: "V1.0"
                link date/time:  8-JUL-1992 01:22:48.56
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSEXE]DNS$SOLICIT.EXE;2      0 err
ors
                image file identification: "V1.0"
                link date/time:  8-JUL-1992 01:22:26.49
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSLIB]DNS$CLIENT.EXE;2       0 err
ors
                image file identification: "DNS V5.5-100"
                link date/time:  8-JUL-1992 01:21:13.87
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSLIB]DNS$RTL.EXE;2          0 err
ors
                image file identification: "DNS V5.5-100"
                link date/time:  8-JUL-1992 00:48:45.95
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSLIB]DNS$SHARE.EXE;2        0 err
ors
                image file identification: "DNS V5.5-100"
                link date/time:  8-JUL-1992 00:48:29.70
%ANALYZE-I-ERRORS, SYS$SYSDEVICE:[VMS$COMMON.SYSMSG]DNS$MSG.EXE;1          0 err
ors
                image file identification: "DNS V1.0-000"
                link date/time: 12-OCT-1991 05:07:37.62