[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
1261.0. "How to install MCC in DEC?" by CVG::PETTENGILL (mulp) Wed Jul 17 1991 21:06
I'm trying to install and use MCC in our lab specifically to manage the
DECbridge 600, and our lan devices in general. The problem I've run into
is that we don't have access to the DNS directories that MCC uses, and in
particular to .MCC_BRIDGE_BACKTRANSLATION. I've read the various notes
in this conference that have to do with MCC and DNS, but I haven't found
one that provides a practical solution to the problem presented by these
global DNS directories.
What are people doing, really?
In looking at the DNS directories, there appear to be only about 100 bridges
entered (and only a couple hundred uids), so I'm assuming that there is a
workaround for problem. (We would be managing ~30 bridges just to start
on our lab lan, which are separate from the building lan and the dsteg lan...)
So, I assume that mcc is being used without using these global directories,
right?
Setting up a separate namespace just for MCC will be a major pain since that
will require setting up a system just for the use of MCC, since we normally
use things like elms and tsm from our timesharing system.
Is there some hack, like patching the executable, until such time as v1.2
is available?
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1261.1 | Can you use a ws? | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Thu Jul 18 1991 05:41 | 10 |
| Many people run DECmcc on workstations. They put the DNS
server on that same workstation. For these people, this is a
simple, easy solution.
If you're running DECmcc on a timeshare system that already has
a namespace set up, I'd see if you can get write access to it
or simple find a ws until V1.2 is available. There is no way
to patch out the requirements for DECdns in V1.1
JCE
|
| 1261.2 | There is a workaround. | TRM::KWAK | | Thu Jul 18 1991 10:53 | 22 |
|
MCC, by default, uses .MCC_BRIDGE_BACKTRANSLATION directory to store bridge
address backtranslation link in the DNS namespace.
If your system's default DNS Namespace is DEC:, the bridge address
backtranslation entries will be stored in DEC:.MCC_BRIDGE_BACKTRANSLATION
directory. You need to have R/W/D access rights in the directory in order
to register a bridge using MCC.
You may define MCC Backtranslation directories (except .dna_nodesynonym and
.dna_backtranslation directories) to be placed in non-root directory of
the name space. For example, you can define your MCC Root to be
DEC:.nio.lab.me and use DEC:.nio.lab.me.MCC_BRIDGE_BACKTRANSLATION
directory to store bridge backtranslation links (provided that you have
full access rights in your directory DEC:.nio.lab.me).
The use of MCC Root can avoid access rights problem in the Namespace.
Please note that the use of MCC Root is for internal testing purpose only.
PS: Note that .MCC_UID directory and UID entries are no longer used in
MCC V1.1.
|