Conference azur::mcc

    I've tried following these instructions in the 'DECmcc Use' document:
    
    
     "To complete registration of the entity, make sure the entity can be
      reached over the network, then select the entity again on the Map
      window, pull down the Operations menu, and select the Register
      command. The Management window displays any values that you
      entered during the partial registration. Click on Start in the
      Management window to register the entity."
    
    I didn't have the entity on any map (I'm the guy with the undisplayable
    map from Autotopology), so I created a domain, started Toolbox, clicked
    on the bridge icon, and entered the name of my bridge.  A bridge icon
    appeared in my domain.  I click on Start and see:
    
    "The entity is already registered with MCC."
    
    What else should I try?
    
    tl
    
    

| How can I use FCL to fix a partially registered entity.  I've tried to
| REGISTER ad DEREGISTER it, to no avail.

    First, make sure the bridge is on the network and reachable.  You can
    check this several ways.  Try one of the following:

    MCC> test bridge 08-00-2B-xx-yy-zz (use the bridge's address, labeled
                                        on the back of the machine)
    MCC> show station 08-00-2B-xx-yy-zz

    Once you know that the bridge is actually on your network and
    reachable, merely re-issue the REGISTER command again:

    MCC> register bridge <bridgeName> address 08-00-2B-xx-yy-zz

    You should see a "Registration successful" message.

MCC> test bridge 08-00-2b-26-dc-67

Bridge {08-00-2B-26-DC-67}
AT 17-AUG-1992 13:34:34

Insufficient information, entity has only been partially registered
MCC> show station 08-00-2b-26-dc-67
Using default ALL IDENTIFIERS

Station 08-00-2B-26-DC-67
AT 17-AUG-1992 13:34:44 Identifiers

Examination of attributes shows:
                                Address = 08-00-2B-26-DC-67
MCC> register bridge l1a3 address 08-00-2b-26-dc-67

Bridge HLOMCC_NS:.l1a3
AT 17-AUG-1992 13:35:08

The entity is already registered with MCC.
MCC> show bridge 08-00-2b-26-dc-67
Using default ALL IDENTIFIERS

Bridge {08-00-2B-26-DC-67}
AT 17-AUG-1992 13:35:15 Identifiers

Insufficient information, entity has only been partially registered
MCC>

Any other thoughts?

Thanks,
tl

    Eeeeek!  Looks like the name space is really hosed!

    I've tried to reproduce the problem here, and I can't seem to.  Here's
    what I did:

    (1) Unplug the bridge so it's not reachable.

MCC> reg bridge debet100 address 08-00-2b-0a-c9-39

Bridge LOCAL_NS:.debet100
AT 17-AUG-1992 17:09:17

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = Cannot communicate with target

    (2) Plug it back in and make sure it's reachable.

MCC> test bridge 08-00-2b-0a-c9-39

Bridge {08-00-2B-0A-C9-39}
AT 17-AUG-1992 17:10:41

Cannot communicate with target
MCC> test bridge 08-00-2b-0a-c9-39

Bridge {08-00-2B-0A-C9-39}
AT 17-AUG-1992 17:16:39

Test successful.

    (3) Re-issue the register command.

MCC> reg bridge debet100 address 08-00-2b-0a-c9-39

Bridge LOCAL_NS:.debet100
AT 17-AUG-1992 17:16:41

Registration Successful

    (4) Use directory to see it in the namespace.

MCC> dir bridge debet100

Bridge LOCAL_NS:.debet100
AT 17-AUG-1992 17:16:50

Directory successful.
                                   Name = LOCAL_NS:.debet100
                                Address = { 08-00-2B-0A-C9-39 }

    I'm using the Local MIR as my namespace, not DNS, so I'm guessing that
    it's a DNS-specific problem?

    
    I have the same problem with the name that I gave to one bridge. I
    can not re-produce the problem. This was the first FDDI bridge that
    we used and incorrectly tried to register it as an FDDI-STATION. I can
    only presume that this has something to with the problem. 
    
    There are no FDDI-STATIONS registered and we are using DNS.

I'm willing to do some ugly things to get this resolved.  Can I, using just
DNS$CONTROL, delete the appropriate things to make this entity go away?  Clearly,
I've found a bug (right?), but how do I get out of the situation I'm in?

Thanks
tl