| I think the only problem you might have is that you need to remember to grant
appropriate access rights to the _new_ MCC system (different DECnet address,
correct?) on the DNS server running on the 'old' MCC system. If I understand
your problem, that should cover you.
Actually, the supposition made for using DNS as MCC's datastore is that
multiple directors *should* share a single DNS server. After all, DNS is a
pretty heavy burden to bear if you're not planning on _sharing_ the data, isn't
it?
/doug
|
| Doug,
That is what I was hoping to hear, but how is this problem resolved...
If my understanding is correct, when you register an entity (eg node4) in MCC,
then a uid is created for that entity, and is stored in both the MIR, and as an
attribute of the object in DNS. A softlink is also created in the .MCC_UID
directory which points the UID back to the object. All future references by MCC
to that entity are done via the UID rather than the entity name (particularly
the historian/exporter functions). If I register the same entity from my new
Director will it use the existing UID attribute in DNS and put that into it's
own MIR, or will it try to create a new one? If so, won't there be a conflict
between the existing MIR and the new one?
I recall having similiar problems in the early days of MCC, and I know that
there are/were plans to change the way MCC uses UID's and DNS, have any changes
been made? or is my understanding above totally incorrect?
Ian
|
| The UIDs and the (no longer used) .MCC_UID namespace directory
are both red herrings (ie. irrelevant).
MCC was designed to allow multiple users on the same or separate
machine to be able (subject to access controls, of course) to share
the same namespace and hence be able to manage the same objects
(again, subject to access controls). Having a single user or a single
machine is only a special case of the more general case we implemented.
If you find a situation (other than relating to access control) where
it doesn't appear to work, please let us know. It certainly works for
us!
Colin
|