| 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 |
Hello, We have MCC 1.3 on ULTRIX. We use DNS. Could someone explain what the difference between MCC> show bridge ..... and MCC> dir bridge ... is? I mean the different from the DNS point of view. I ask this question because we have bridges on that we can not do a show --> not registered message. But with a dir command we can see the bridge. We can't register nor deregister this bridge. Maybe it has to do with the installation. Our customer ran MCC on VMS with DNS and now he changed to MCC ULTRIX. This means that all entities were already in DNS when the MCC machine came to the network. Could someone more excactly explain the relationships between DNS and MCC when an object is already in DNS and someone wants to register this object (entity). Or does someone know a pointer to a docu where it is written in? Thanks Roland
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5384.1 | broken soft links? | TRKWSH::COMFORT | Here beside the rising tide | Fri Jul 23 1993 13:15 | 22 |
As far as I know, a dir will go into the DNS directory structure and
return information that it finds there. A show command against a
bridge or station entity will go to the namspace and lookup the address
against the name provided then use that address to make a network
connection to the entity and retrieve the rest of the information
requested. If the DNS soft link pointing from the name to the address
is not there for some reason, I believe you will see the situation you
are experiencing. At this point MCC cannot deregister the device cause
it cannot find all the information necessary to remove it from the
namespace and it cannot re-register it because the name already exists.
When the softlink problem happened to me, I had to go into DNS$CONTROL
and manually remove it, which is not fun.
However, on the lighter side, maybe there is an access control issue
for your new station against one of the DNS directories that is
preventing a full lookup.
Hope some of this helps.
Dave
| |||||
| 5384.2 | We will check | ZUR01::SCHNEIDERR | Mon Jul 26 1993 02:58 | 6 | |
Dave, We will check. Thanks!! Roland | |||||