[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

3491.0. "FDDI registration problem" by VCSESU::WADE (Bill Wade, VAXc Systems & Support Eng) Mon Aug 03 1992 16:39

    I'm getting the following error when I try to register an FDDI entity-
    
    
    MCC> register fddi newfddi add=08-00-2b-28-d2-67
    
    FDDI LOCAL_NS:.newfddi
    AT  3-AUG-1992 15:43:10
    
    The requested operation cannot be completed
                     MCC Routine Error = %MCC-E-INV_IN_ENTITY,software error:
                           invalid in_entity (input entity) parameter
    
    
    
    DECmcc and ELMS V1.2 
    
    MCC> show mcc 0 fddi_am all att
    
    MCC 0 FDDI_AM
    AT  3-AUG-1992 15:53:09 All Attributes
    
                            Available Ports = { "XQA0:" }
                          Component Version = V1.2.0
                   Component Identification = "DECmcc FDDI AM"
    MCC>
T.RTitleUserPersonal
Name		DateLines
3491.1SLINK::CHILDSPractice passive aggression.Tue Aug 04 1992 11:505
    Did you previously have ELM T1.2.7 installed on your system with FDDI
    devices in your namespace?  If so, check out note 3236 here.  The FDDI
    entity was renamed to FDDI_STATION and the entity code was changed. 
    This might be the problem you are experiencing.  [The ELM release notes
    also address this change.]
3491.2Auto topology uses "REGISTER FDDI".VCSESU::WADEBill Wade, VAXc Systems & Support EngTue Aug 04 1992 16:397
    This is a new install.  I see where I went wrong, thanks.  
    
    I noticed the same errors generated by  the fddi auto registration file 
    that's created from the auto topology aplication.  The  registration 
    commands that it generates fail as it uses fddi and not fddi-station.
                     
    Bill
3491.3Using "FDDI" still worksQUIVER::HAROKOPUSTue Aug 04 1992 17:148
You can still abreviate "FDDI-Station" as "FDDI".  The problem is if you have 
old FDDI entities in your database then these may conflict with new
FDDI-Station entities.   For example, if you registered FDDI entity "foo" 
with ELM T1.2.7, then you try to access it or register it again as FDDI-Station
then MCC will not allow you to do this.   This is why note 3236 indicates that
FDDI entities should be deregistered before installing MCC V1.2.

Bob