[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

1807.0. "MCC-E-FULLNAME_ERROR" by VF::LANGASQUE () Wed Nov 13 1991 10:40

	Hello,

 I've the following error (on 2 DEMSA registered in MCC as phase V nodes)
 when I perform: 

MCC> show node foo 
or
MCC> show node .foo
or
MCC> show node .dna_node.foo
or
MCC> show node lab:.dna_node.foo
   
Examination of attributes shows:
					Name=
				
%MCC-E-FULLNAME_ERROR, error in full name value

%MCC-E-FULLNAME_ERROR, error in full name value

 If I do 

MCC> show node foo all status
or any other syntaxes I obtain or any other parameters every thing is ok,
 so what is this full name value error.

	Thanks,

		Eric

   
T.RTitleUserPersonal
Name
DateLines
1807.1see 1797.1TOOK::MATTHEWSWed Nov 13 1991 12:001
    Please check note 1797.1. 
1807.2MCC-E-FULLNAME_ERRORVF::LANGASQUEThu Nov 14 1991 03:3912
>================================================================================
>Note 1807.1                   MCC-E-FULLNAME_ERROR                        1 of 1
>TOOK::MATTHEWS                                         1 line  13-NOV-1991 12:00
>--------------------------------------------------------------------------------
>                                -< see 1797.1 >-
>
>    Please check note 1797.1. 
>
	Yes just read 1797 2 min ago, same question teh same day, sorry.
   The rename solution works for me. Thanks.

		Eric
1807.3Please read the release notes!MARVIN::COBBGraham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917Fri Nov 15 1991 14:2914
Note that the requirement to issue a RENAME directive to the WANrouter after
configuring  and  loading  is  in  the  release  notes.  There is also other
important information in there so please make sure you read them.

Graham

P.S.  It would be nice if the MCC group either put pressure on the DNS group
to  fix  DNS  to  correctly  translate  a  null fullname to external form or
adopted  Ben's ULTRIX NCL solution: special case the null fullname and don't
call DNS at all for it!

Technically, the  MCC-E-FULLNAME_ERROR  is an MCC bug and should be QAR'd --
the  node  has  a  legal  name  (the  QAR can then be transferred to the DNS
group!).