[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

4407.0. "entity existance...???" by GUMBAH::DAWSON (Subvert the Dominant Paradigm) Tue Jan 19 1993 17:49

    I"m trying to monitor a DECnis 600.  I'm able to get the icon onto
    the map and am able to register the entity...at least is looks like
    it's registered.  When I double click on the icon to try to get at the
    modules beneath it I get the following error message:
    
    The requested operation cannot be completed
    
    Entity Existance info   Entity Existance Cannot Be Determined
    
    VMS Routine Error        %MCC-E-ALERT_TERMREQ, thread
                             termination requested
    
    I got much the same message when I tried to autoregister the beastie.
    
    There are 3 other DECnis 600s on this network that I can play with with
    no problems.
    
    Any ideas?
    
    Thanks,
    
    Mike
T.RTitleUserPersonal
Name
DateLines
4407.1VERNA::V_GILBERTTue Jan 19 1993 20:317
Mike,

First off, can you tell us what version of MCC and whether VMS or Ultrix.

Can you do similar operations using FCL?

Verna
4407.2more infoGUMBAH::DAWSONSubvert the Dominant ParadigmWed Jan 20 1993 11:488
    Sorry,  MCCv1.2 on VMS v5.5-2
    
    If I could figure out the NCL syntax...
    
    actually, I've been able to do some NCL stuff to convince me that the
    router is there and is working.  
    
    MIke
4407.3A couple of things to try...MCDOUG::MCPHERSONpre-retinal integrationWed Jan 20 1993 12:339
Have you tried this:

From FCL (not the map) try to DEregister then Reregister the problem DECnis.
What happens then?

Can you successfully issue "SHOWS" to the DECnis by just specifying address
instead of a registered name ?

/doug
4407.4same thing...GUMBAH::DAWSONSubvert the Dominant ParadigmWed Jan 20 1993 12:4927
    OK...
    
    MCC> deregister node nis01
    
    Node LOCAL_NS:.nis01
    AT 20-JAN-1993 09:46:26
    
    Deregistration Successful
    MCC> register node nis01
    
    Node LOCAL_NS:.nis01
    AT 20-JAN-1993 09:46:39
    
    Partial registration success. Please retry later to complete the
    registration.
            Reason for Partial Registration = The requested operation
    cannot be
                                          completed
                      Entity Existence Info = Entity Existence Cannot Be
    Determined
                          MCC Routine Error = %MCC-E-NOPARAMLIST, no
    parameter list
                                              was supplied in this ILV
    buffer
    
    
    MIke
4407.5a show of sortsGUMBAH::DAWSONSubvert the Dominant ParadigmWed Jan 20 1993 13:0030
    Looks like it's there...by address, do you mean the normal Phase iv
    decnet address? or ethernet address?  Please specify...and I apologize
    for looking stupid...this is the first time I've played with Phase V
    stuff.
    
    MIke
    
    MCC> show node nis01
    Using default ALL IDENTIFIERS
    
    Node LOCAL_NS:.nis01
    AT 20-JAN-1993 09:58:21 Identifiers
    
    Examination of attributes shows:
                                       Name = LOCAL_NS:.
                                    Address = {{{Network Management -- CMIP
    or NICE,
                                                 none}
                                                {DNA Phase V Session
    Control,
                                                 Network Management}
                                                {NSP Transport,
                                                 Session Control}
                                                {OSI network or DNA
    Routing,
                                                 49::00-27:AA-00-04-00-B2-9
    E:20}}}
    
    
    
4407.6Is that Name attribute right?GOSTE::CALLANDERWed Jan 20 1993 15:263
    I don't know much about NODE stuff, but the Name value that is
    returned if LOCAL_NS:. this doesn't look right. Does the 
    device know who he is or not?
4407.7name should be there I thinkGOSTE::CALLANDERWed Jan 20 1993 15:275
    did a quick check here, and got on a local node:
    
    Examination of attributes shows:
                                       Name = DEC:.lkg.quiff
      
4407.8register node nis01 synonym nis01TOOK::S_KOHoot mon!Wed Jan 20 1993 15:344
    
    the SYNONYM argument is required (eg - its phaseIV name).
    
    the error message is pretty bad - but it's fixed in 1.3!
4407.9well, most of that worked...GUMBAH::DAWSONSubvert the Dominant ParadigmWed Jan 20 1993 16:0610
    Ok...I was able to deregister node nis01 successfully, then able to
    register node nis01 synonym nis01 successfully from FCL.  I then
    deregistered it again.  I then went to the map and used the toolbox
    icon to deregister it and remove it fromthe map, which it did
    successfully.  I then used the node5 icon to plac eit back in the map
    and go the two popup windows for registration, however, when I moved
    the mouse to the map and clicked MB! to place it on the map I go a pop
    up window that said ID already in use...what's going on now?  Sheesh!
    
    Mike
4407.10FCL log of previousGUMBAH::DAWSONSubvert the Dominant ParadigmWed Jan 20 1993 16:3825
    From FCL it looks like this:
    
    MCC> register node nis01 synonym nis01
    
    Node LOCAL_NS:.nis01
    AT 20-JAN-1993 13:34:52
    
    ID already in use.
                                    Address = {{{Network Management -- CMIP
    or NICE,
                                                 none}
                                                {DNA Phase V Session
    Control,
                                                 Network Management}
                                                {NSP Transport,
                                                 Session Control}
                                                {OSI network or DNA
    Routing,
                                                 49::00-27:AA-00-04-00-B2-9
    E:20}}}
    
    
    Any ideas how to get rid of the ID?
    
    MIke
4407.11check for entity already registered with that synonymTOOK::S_KOHoot mon!Thu Jan 21 1993 18:409
    
    did you use the double-bar bomb or the single-bar bomb to remove the
    entity from the domain?  single-bar bomb only removes the entity from
    the domain.  double-bar removes AND deregisters the entity.
    
    the error you saw in .10 is returned when another node entity has been
    registered with that synonym.  if you do a dir of your node entities,
    perhaps you can see if there was some typo or something (eg - "O" instead
    of 0)?
4407.121 down, 1 still no workieGUMBAH::DAWSONSubvert the Dominant ParadigmFri Jan 22 1993 16:0013
    That was exactly the case!!!  I had a synonym of nisO1 insteadof
    nis01...frustrating.  
    
    However, I am now able to register the NIS600 and it shows up nicely on
    the map.  BUT, I still can't double click down into it.  From FCL I can
    poke at it and get info back, but not from the map.  After about 10
    minutes of the "looking into node nis01" popup window I cancel it and
    get the previous message, "Entity existance cannot be determined"
    
    
    AAAAAAARG!!!!!!
    
    Mike
4407.13works now!!GUMBAH::DAWSONSubvert the Dominant ParadigmMon Jan 25 1993 18:184
    Well...In the process of this project, I rebooted the DECnis.  Now, I
    can reach it from the map.  Weird...
    
    Mike
4407.14Null name is not a problemMARVIN::COBBGraham R. Cobb (DECNIS development), REO2-G/G9, 830-3917Wed Feb 24 1993 13:2416
For your information...

.6>     I don't know much about NODE stuff, but the Name value that is
.6>     returned if LOCAL_NS:. this doesn't look right. Does the 
.6>     device know who he is or not?

Probably not.   Any  standalone system (router, gateway, etc.) will not know
its  name  unless  you  tell  it.  That is what the RENAME directive is for.
Don't  forget,  it  is perfectly legal for a Phase V node to have no name at
all  --  that  is what the router assumes is happening until you tell it its
name.

The formatting  routines  are incorrect, however.  What is being returned is
the null fullname which should be formatted as "0:." not "LOCAL_NS:.".

Graham