| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2831.1 | Probably works; not tested | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Thu Apr 23 1992 09:36 | 6 |
| We expect that DECmcc works with "DNS V1.1 (or later)"
We have done some limited testing with an ULTRIX DNS V2 server,
but haven't tested with a VMS DNS V2.
-- Erik
|
| 2831.2 | DECmcc won't work with DECnet-OSI and DNS V2? | OSLACT::BJORN_P | Woops, now I have to learn changing diper's | Mon Jun 29 1992 08:12 | 16 |
| I've now installed DECnet-OSI for VMS BL10 on my DECmcc Mngmnt station. I'm
having problems with DNS and access rights, but I've solved some of them by
running DNS with a diag switch that overrides access control checking enabled.
I'm gonna turn this off once I've got my access rights O.K.
I'm having trouble using MCC_DNS_SETUP, which reports back that DNS$CONTROL.EXE
and DNS$CONTROL.BIN AND DNS$LIB.EXE does not exist.
From the IMPM. I also get an error message, when trying to open a domain.
Has anyone run DECmcc on a VMS node using the DNS SERVER that installs with BL10
of DECNET-OSI?
Give me your recommendations of what to do.
Bj�rn Olav
|
| 2831.3 | DNS V2 and DECmcc V1.2 comments | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Tue Jun 30 1992 01:37 | 24 |
| Though I haven't tried it yet, there should be no reason why DECmcc
will not work with DNS V2. One of the things V2 offers you is
increased ability to manage the namespace. There will soon be some
very nice tools available to do just that.
Here is a bit of info on DNS V2 and V1.1 :
* Access in V1.1 defaults to full privileges. Under DNS V2, the
default is no privileges.
* DNS V2 must be installed on a Phase V (DECnet/OSI) node. DECnet
Phase IV and Phase V can not run concurrently on the same node.
(Watch out with Phase V. It hammered Pathworks for DOS.)
* You may run DNS V1.1 and V2 servers concurrently to manage the same
namespace; HOWEVER, you must be certain that you select the OPTION
of V1.1-style DNS directories. V1.1 is the default.
* If you are bringing a VMS Phase V node (DNS V2) in to the namespace
to act as a support server for the other DNS V1.1 servers, be sure
the new node is registered in the namespace before you install.
-Dan
|
| 2831.4 | No DNS V2 doesn't work with DECmcc, yet. | OSLACT::BJORN | Woops, now I have to learn changing diper's | Tue Jun 30 1992 05:49 | 23 |
| >> Though I haven't tried it yet, there should be no reason why DECmcc
>> will not work with DNS V2. One of the things V2 offers you is
>> increased ability to manage the namespace. There will soon be some
>> very nice tools available to do just that.
I'm not so sure that it will work. DECmcc is complaining about some files
that don't exist, which are V1.1 Server files. When installing the Wave2
BL10L-kit, these files are obsolete. SO, I deleted them.
Do I have to re-instal DECmcc to get it running?
The situation I have now is,
DNS Client software comes with VMS V5.5. I've renamed these files
DNS Server V1.1 where earlier installed on the system, I've deleted
these files.
DNS Server V2 comes with the DECnet-OSI kit (BL10L), but does not replace
the old V1.1 files. I have to manually rename the old files.
What is the right thing to do? I'm very confused. I've entered a note
in DECNet-OSI also, but haven't got any smart ideas yet.
Bj�rn Olav
|
| 2831.5 | Works for us | TOOK::MINTZ | Erik Mintz, dtn 226-5033 | Tue Jun 30 1992 08:16 | 5 |
| We have run DECmcc with a DNS V2 server.
Perhaps I missed something in your configuration. Does the problem
occur when you install DECmcc, or when you try to run?
|
| 2831.6 | DECmcc doesn't "like" DECdns V2 Server | OSLACT::BJORN | Woops, now I have to learn changing diper's | Wed Jul 01 1992 04:28 | 16 |
| As I said, I'm trying to open a domain from IMPM, and it's giving me an error
message with a number, when I'm trying to filter domains.
From FCL. when doing MCC> DIRECTORY DOMAIN *, I get some of the domains listed
out, but not all. The one's I get, is located under root, and the rest in
.NWO.MCC.DOMAIN directory. I'm sure this is a protection problem.
The second problem I get is when running MCC_DNS_REGISTER. It gives me a message
that tells me to look for the DNS$LIB.EXE, DNS$CONTROL.EXE and DNS$CONTROL.BIN
files, which are all V1.1 Server files. These files I've deleted from the system
because of problems I had earlier, with V1.1 and V2 mismatch.
I'm still working on this, when I have time between customer visits.
Bj�rn Olav Haugom
oslo, Norway
|
| 2831.7 | | TRM::KWAK | | Wed Jul 01 1992 10:47 | 57 |
| RE: .6
The mcc_system:MCC_DNS_SETUP.COM utility program needs to be run on DNS
V1.1 server system because the DNS$CONTROL program was only available
on DNS server system. And the utility program checks if all the
required files for running DNS$Control exist before performing
functions - e.g. creating a backtranslation directory.
The MCC_DNS_SETUP.COM program is meant to run on DECnet Phase4 systems.
If you are running DECnet WaveII, the DECdns namespace has been
properly setup (Access controls, DNA Backtranslation directories, and
DNA_NodeSynonym directory, etc.). Only thing you need to do to DECdns
namespace in order to use DECmc is to create MCC directories. Please do
the following (you do not have to run MCC_SYSTEM:MCC_DNS_SETUP.COM):
$ mcr dns$control
DNS> create directory .MCC
DNS> create directory .MCC_Bridge_BackTranslation
DNS> create directory .MCC_Concentrator_BackTranslation
DNS> create directory .MCC_SNMP_BackTranslation
DNS> create directory .MCC_Station_BackTranslation
DNS> create directory .MCC_Terminal_Server_BackTranslation
DNS> create directory .MCC_Sample_BackTranslation
After creating these directories, you can use DECnet OSI utility
programs to change access rights if needed. (The above set of commands
is provided in Ultrix DECmcc kit - DECdns runs on Ultrix DECnet OSI
systems only)
RE: MCC> directory domain *
(NOTE: this command traverses entire namespace, or stops when an
error is encountered - imagine traversing entire DEC: namespace.
You could use "MCC> directory domain .NWO.*" - this will traverse a
subtree rooted at ".NWO".)
Are you using DECmcc T1.2.7 or later version?
The DECmcc T1.2.7 contains some code changes to handle protected DNS
directories which can cause problems in wildcard operation on DNS
namespace.
In the fullwild card directory operation, MCC enumerate the current
directory for child directories and the enumerate each child directory
for all objects in the directory.
Suppose, a directory .site.secret, is completely protected.
When directory .site is enumerated for its child directories, the DNS
returns the protected directory (.site.secret) name in enumeration.
However, when the child directory (.site.secret) is enumerated, the DNS
returns "no such directory". The MCC DNS routines treat the protected
directory as an empty directory and continue to complete the wildcard
operation.
I am very interested in knowning how your namespace is setup. Do you
have protected DNS directories or objects in the namespace?
William (TOOK::KWAK)
|
| 2831.8 | | OSLACT::BJORN | Woops, now I have to learn changing diper's | Thu Jul 02 1992 07:52 | 33 |
| Re .7
I'm not sure I expressed myself clearly enough. But here's another chance to
get an understanding of my problems.
I was (earlier) running T1.2.7 of DECmcc with DNS Server V1.1 running on the same
system as DECmcc. The DNS V1.1 server was not contributing in a distributed name-
space, but had it's own namespace. Everything was running just fine, DNS was open
for everyone, and I hadn't touched the ACS's in any way. Of course, I did run the
MCC_DNS_SETUP some year ago, or so, and I've used the procedure to generate new
directories, so that I did get the ACS's right. DNA_REGISTRAR-group does have
access to all the directories and objects.
2� week ago, I installed DECnet-OSI for VMS (Wave 2) BL10L. I had a lot of
problems, but I've ended up with a DNS V2 Nameserver and a V2-format Clearing-
house.
So, Now I'm having problems getting my .NWO.MCC.DOMAIN.NORGE domain up in the
Iconic Map. When trying to open this specific domain I get an error message
in a window saying
The requested operation cannot be completed
MCC Routing Error %NONAME-E-NOMSG, Message number
01DE8022
And as I said, DNS-directories and objects was accessible as is the default
scheme in V1.1 of DNS.
Bj�rn Olav
Anyone to answer for this error message?
|
| 2831.9 | | TRM::KWAK | | Thu Jul 02 1992 10:15 | 25 |
|
RE: .8
The error message number belongs to DNS:
$ search sys$share:dns*.h 31359010
******************************
SYS$COMMON:[SYSLIB]DNSMSG.H;1
#define DNS$_NOCOMMUNICATION 31359010
Please try the following commands to see if the problem is in DNS or
MCC:
$ mcr dns$control
DNS> show object .NWO.MCC.DOMAIN.NORGE
For each member in the DNS$Members attribute of .NWO.MCC.DOMAIN.NORGE
DNS> show object -------
These commands will tell you whether DECdns can read domain object and
the members from DNS namespace.
William
|
| 2831.10 | I can't access DNS V2 from MCC. | OSLACT::BJORN | Woops, now I have to learn changing diper's | Fri Jul 03 1992 10:34 | 19 |
| re .9
From DNS I can get information on the objects representing domains.
DNS> SHOW OBJECT .NWO.MCC.DOMAIN.NORGE returns all info I want.
There are no members of domain Norge, as I can see from DNS, although
I know I created a sub-domain earlier. But this is something else.
My problem is that when trying to open the domain from IMPM or
trying to create a new domain from FCL, or adding a member to
NORGE, I get the same error status, which translates to NOCOMMUNICATION.
So, I don't know what's wrong. I'm running from the same user.
Perhaps something to do with mismatch between DNS CLient and Clerk
and Server? I'm confused of what I should proceed with now.
DECNet-OSI is working O.K now, MCC has problems.
Bj�rn Olav
|
| 2831.11 | More commands to try ... | TRM::KWAK | | Mon Jul 06 1992 09:42 | 18 |
| RE:. 10
Please try following mcc commands and post results:
MCC> show domain .NWO.MCC.DOMAIN.NORGE
MCC> show domain .NWO.MCC.DOMAIN.NORGE member * all char
And, issue the following DNS$Control commands and post the output:
(please make sure the following commands prints all the attribute
values)
DNS> show object .NWO.MCC.DOMAIN.NORGE
DNS> show object .NWO.MCC.DOMAIN.NORGE_MCC_EXT000
DNS> show object .NWO.MCC.DOMAIN.NORGE_MCC_EXT001
William
|
| 2831.12 | Here is the output from MCC and DNS | OSLACT::BJORN | Woops, now I have to learn changing diper's | Mon Jul 06 1992 11:23 | 141 |
| Re .11
Here is the output;
*****
MCC> SHOW DOMAIN .NWO.MCC.DOMAIN.NORGE
Using default ALL IDENTIFIERS
Domain NORWAY_MCC:.NWO.MCC.DOMAIN.NORGE
AT 6-JUL-1992 16:07:34 Identifiers
Examination of attributes shows
DomainName = NORWAY_MCC:.NWO.MCC.DOMAIN.NORGE
*****
MCC> SHOW DOMAIN .NWO.MCC.DOMAIN.NORGE MEMBER * ALL CHAR
Domain NORWAY_MCC:.NWO.MCC.DOMAIN.NORGE Member *
AT 6-JUL-1992 16:10:03 Characteristics
No such entity: Domain NORWAY_MCC:.NWO.MCC.DOMAIN.NORGE Member *
Unknown Entity = Domain
NORWAY_MCC:.NWO.MCC.DOMAIN.NORGE
Member *
After this I have to wait some minutes, or else I'll get the NOCOMMUNICATION-
message, and no other output.
The DNS output follows;
DNS> SHOW OBJECT .NWO.MCC.DOMAIN.NORGE
SHOW
OBJECT NORWAY_MCC:.nwo.mcc.domain.norge
AT 06-JUL-1992:16:17:06
%X4D43435F01000800000000000000000000000 = %xa6820027bf817b820012a082000e8101028201008301008401008500bf817a8200098c07424a4f524e5f50
%X4D43435F01000800000000000000000000000 = %xa6820032bf817b820012a082000e8101028201008301008401008500bf817a8200148d1253595324555345523a5b424a4f524e5f505d
%X4D43435F01000800000000000000000000000 = %xa6820021bf817b820012a082000e8101028201008301008401008500bf817a8200038e0100
%X4D43435F11000800000000000000000000000 = %xa6820055bf817b820012a082000e8101028201008301008401008500bf817c820037a1820033810105822baa00040095ca00f3a1afd36095001b0001036e776f01036d63630106646f6d61696e01056e6f7267650000830100
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test, control
(IV) Principal = NWOMCC::BJORN_P
(V) Principal = NORWAY_MCC:.DNS$IV.NWOMCC.BJORN_P
DNS$ACS (set) = :
Flags = none
Rights = test
(IV) Principal = *::DNS$SERVER
(V) Principal = NORWAY_MCC:.DNS$IV.*.DNS$SERVER
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = *::*
(V) Principal = NORWAY_MCC:.DNS$IV.*.*
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = NORWAY_MCC:.dna_registrar
DNS$ACS (set) = :
Flags = propagate
Rights = read, test
(V) Principal = NORWAY_MCC:.*...
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(V) Principal = NORWAY_MCC:.nwo.nwomcc.bjorn_p
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(V) Principal = NORWAY_MCC:.nwo.nwomcc.dns$server
DNS$Class = DNS$Group
DNS$ClassVersion = 1.0
DNS$CTS = 1992-02-18-10:01:09.202000000/aa-00-04-00-95-ca
DNS$UTS = 1992-07-02-10:22:05.770000100/08-00-2b-1b-21-3d
MCC_Class = %x08000000
MCC_DOM_EXT_LIST = %xaa00040095ca00f3a1afd3609500260001036e776f01036d63630106646f6d61696e01106e6f7267655f4d43435f4558543030300000
MCC_DOM_EXT_NEXT = %x01000000
MCC_DOM_MEM_CUR = %x0a000000
MCC_DOM_MEM_MAX = %x0a000000
MCC_REGISTRATION_STATE = %x63000000
MCC_UID = %x830b2239ccedca010000aa00040095ca
MCC_Version = %xa68200089f817d0456010200
DNS> SHOW OBJECT .NWO.MCC.DOMAIN.NORGE_MCC_EXT000
SHOW
OBJECT NORWAY_MCC:.nwo.mcc.domain.norge_mcc_ext000
AT 06-JUL-1992:16:17:20
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test, control
(IV) Principal = NWOMCC::BJORN_P
(V) Principal = NORWAY_MCC:.DNS$IV.NWOMCC.BJORN_P
DNS$ACS (set) = :
Flags = none
Rights = test
(IV) Principal = *::DNS$SERVER
(V) Principal = NORWAY_MCC:.DNS$IV.*.DNS$SERVER
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = *::*
(V) Principal = NORWAY_MCC:.DNS$IV.*.*
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = NORWAY_MCC:.dna_registrar
DNS$ACS (set) = :
Flags = propagate
Rights = read, test
(V) Principal = NORWAY_MCC:.*...
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(V) Principal = NORWAY_MCC:.nwo.nwomcc.dns$server
DNS$Class = DNS$Group
DNS$ClassVersion = 1.0
DNS$CTS = 1992-02-18-10:01:10.052000000/aa-00-04-00-95-ca
DNS$Members (set) = :
Group = NORWAY_MCC:.nwo.mcc.DEC_OSLO
DNS$Members (set) = :
Group = NORWAY_MCC:.nwo.mcc.domain.oslo
DNS$UTS = 1992-07-06-12:56:30.760000100/08-00-2b-1b-21-3d
MCC_Class = %x7f000000
MCC_DOM_EXT_OF = %xaa00040095ca00f3a1afd36095001b0001036e776f01036d63630106646f6d61696e01056e6f7267650000
MCC_DOM_MEM_CUR = %x0f000000
MCC_DOM_MEM_MAX = %x50000000
MCC_Version = %xa68200089f817d0456010200
DNS> SHOW OBJECT .NWO.MCC.DOMAIN.NORGE_MCC_EXT001
SHOW
OBJECT NORWAY_MCC:.nwo.mcc.domain.norge_mcc_ext001
AT 06-JUL-1992:16:17:31
Error on entity: NORWAY_MCC:.nwo.mcc.domain.norge_mcc_ext001
%DNS-E-UNKNOWNENTRY, Requested name does not exist
|
| 2831.13 | Check DNS objects in Domain Extension | TRM::KWAK | | Mon Jul 06 1992 12:01 | 28 |
|
RE: .12
When you do "MCC> show domain .NWO.MCC.DOMAIN.NORGE mem * all char",
the following happens in MCC DNS routines:
1. Read the MCC_Class attribute of the DNS object .NWO.MCC.DOMAIN.NORGE,
2. Read DNS$Members attibute of the object (, which is empty in this
case),
3. Read domain extension attribute MCC_DOM_EXT_LIST
(what is printed in 2831.12 is .NWO.MCC.DOMAIN.NORGE_MCC_EXT000 in
opaque format)
4. Read DNS$Members attribute of .NWO.MCC.DOMAIN.NORGE_MCC_EXT000
If the attribute is not empty, read the MCC_Class attribute of each
member stored in DNS$Members attribute.
(i.e. read MCC_Class attribute of NORWAY_MCC:.nwo.mcc.DEC_OSLO
and NORWAY_MCC:.nwo.mcc.domain.oslo)
Please check if you can read DNS objects in Step 4:
DNS> show object NORWAY_MCC:.nwo.mcc.DEC_OSLO
DNS> show object NORWAY_MCC:.nwo.mcc.domain.oslo
William
|
| 2831.14 | Problem solved with a patch. | OSLACT::BJORN_P | Woops, now I have to learn changing diper's | Tue Jul 07 1992 03:31 | 42 |
| It's now solved with a patch. See note #259 in the decnet-osi_for_vms conference.
<<< BULEAN::BULEAN$USER:[NOTES$LIBRARY]DECNET-OSI_FOR_VMS.NOTE;1 >>>
DECnet/OSI for VMS (aka DECnet-VAX Wave2)
Created: 21-FEB-1991 23:45 268 topics Updated: 6-JUL-1992 12:01
====================================================================================
Note 259.14 How do I install BL10 on top of DNS Server V1.1? 14 of 16
TUXEDO::DONAHUE "Un-Phased" 21 lines 6-JUL-1992 08:36
--------------------------------------------------------------------------------
Try this:
- extract the following PATCH command file.
- invoke it to patch sys$loadable_images:sys$name_services.exe
- reboot the system, so the patched image gets loaded
Let me know what happens. This might solve your problem.
Patch COM file to patch SYS$NAME_SERVICES.EXE dated 5-May-1992
***************************************************************************
SYS$NAME_SERVICES.EXE
SE M
I
EXI
RE
^X00000883
'ADDL2 #^X00000005,R0'
EXIT
'ADDL2 #^X00000000,R0'
EXI
U
EXI
============================================================================
Note 259.16 How do I install BL10 on top of DNS Server V1.1? 16 of 16
TUXEDO::DONAHUE "Un-Phased" 3 lines 6-JUL-1992 12:01
--------------------------------------------------------------------------------
prevented the dns clerk from sticking a null address for a
clearinghouse into it's cache.
Glad to hear it solved your problem. Let us know if you have more...
|
| 2831.15 | other notes on DECnet/OSI for VMS | TUXEDO::ZEE | Pretty soon, you'll be driving him to the airport! | Thu Jul 09 1992 21:33 | 11 |
| - Coming with the next field test release of DECnet/OSI for VMS, obsolete
DNS V1 files will be deleted (except clearinghouse information) or replaced
with their V2 counterparts (both clerk and server).
- As DECnet/OSI for VMS is still in field test, if you believe you have found
a problem, you should submit a QAR on machine PHVQAR, username QE_INTERNAL,
password QAR. Any problems we can find in field test hopefully won't
make it out to customers. There's also the DECNET-OSI_FOR_VMS conference
on BULEAN. Thanks for the testing.
--Roger
|