[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

3750.0. "Show Identifiers operation is not supported for Node4 circuit" by CUJO::HILL (Dan Hill-Net.Mgt.-Customer Resident) Wed Sep 16 1992 15:13

    I brought up the Icon Map PM after verifying that DECmcc had started
    all AMs in the right order and successfully.  The startup order is as
    follows:
    
    	MCC_BMS_STARTUP.COM
    	MCC_ELM_AM_STARTUP.COM
    	MCC_ELM_FM_STARTUP.COM
        MCC_TS_AM_STARTUP.COM
    
    When I tried looking into a node4 entity, I received the following
    Management Window error messages:
    
    	The Show Identifiers operation is not supported for Node4 DH1
   	 Circuit *
    		Supporting MM may not be enrolled.
    
    	The Show Identifiers operation is not supported for Node4 DH1
    	 Line *
                Supporting MM may not be enrolled.
    
    For each node4 I looked into, I received these messages, and the line
    and circuit enties were absent from the child entity object list.
    
    Everything was fine when command were issued from FCL:
    	MCC> SHOW NODE4 DH1 LINE * ALL IDENT
    	MCC> SHOW NODE4 DH1 CIRC * ALL IDENT
    
    When I restarted the IMPM (DECmcc was not restarted), everything was
    fine.
    
    Any ideas?
    
    -Dan
T.RTitleUserPersonal
Name
DateLines
3750.1---> access re-enrolled <--JASPIE::BALLThu Sep 17 1992 16:0310
    Hi Dan -
    	( 1 ) Is this reproducible?
        ( 2 ) did you reenroll the access module?
    
    
    
    
    
    
    - darryl
3750.2Will try re-enroll of DNA4_AMCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentThu Sep 17 1992 17:168
    Darryl,
    
    	This has happened twice, but I can't reproduce it at will.  When it
    happens again, I'll try a re-enroll of the DNA4_AM from the IMPM and
    see it that fixes the problem.
    
    Thanks,
    Dan