[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 |
5432.0. "Cannot fully register NODE, NameSpace Access Denied" by KETJE::PACCO (Gallia divisa est in partes tres) Wed Aug 04 1993 12:49
As the documentation of the registration process goes not into enough
details, neither in the general documentation, nor in the NODE V
access module guide, I would like to know from where the following
problem occurs:
I execute: REGISTER NODE <fullname> synonym <synonym>
CREATE DOMAIN <domain> MEMBER <fullname>
and during the registration I get "NameSpace Access Denied"
Previously the node has been registered by decnetdnsregister, and
that node is working perfectly as seen from a DECnet V perspective.
What is preventing the registration_fm to get all the node child
entities being registered? Is there something more the registration FM
is trying to do, beside the modification of attributes of the node
object in DNS ? The registration process did already something on
the dns node object as can be seen in DNS:
dns> sho obj bkc.m.rbkc01
SHOW
OBJECT bc:.bkc.m.rbkc01
AT 04-AUG-1993:11:55:34
DNA$NodeSynonym = rbkc01
DNA$Towers (set) = :
Tower 1 Floor 1 = 01 13 (null)
Tower 1 Floor 2 = 02 00 13 ncacn_dnet_nsp
Tower 1 Floor 3 = 04 (null)
Tower 1 Floor 4 = 06 49 00 04 aa 00 04 00 01 10 20
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test, control
(V) Principal = bc:.gkk.m.origin.root
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = bc:.dns_admin
DNS$ACS (set) = :
Flags = group
Rights = read, write, delete, test
Group = bc:.mcc_admin
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = bc:.DNA_Registrar
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(V) Principal = bc:.bkc.m.rbkc01.DNA$SessCtrl
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = rbkc01::DNA$SessCtrl
(V) Principal = bc:.DNS$IV.rbkc01.DNA$SessCtrl
DNS$ACS (set) = :
Flags = propagate
Rights = read, test
(V) Principal = bc:.*...
DNS$Class = DNA$Node
DNS$ClassVersion = 1.0
DNS$CTS = 1993-08-04-09:04:04.689/08-00-2b-2c-7b-28
DNS$UTS = 1993-08-04-09:29:19.314/08-00-2b-2c-7b-28
MCC_Class = %x01000000
MCC_DOMAIN_LIST = %x08002b2c791e097537b22bf595000c0001036d63630103626b630000
MCC_UID = %x6cd8ad119d90cc010000aa0004000504
MCC_Version = %xa68200089f817d0456010300
mcc_admin, the group under which the DECmcc platform is known
in the network, has read, write, delete and test on the objects, and
node softlinks; and has read,write, test access on their directories.
e.g.mcc_admin has read, write, test in .DNA_NodeSynonym
mcc_admin has read, write, delete, test in .DNA_NodeSynonym.rbkc01
From the iconic map SHOW NODE <node> ALL REFERENCE
gives "Not Registered Entity"
Doing a "REGISTER NODE <node>" tells "The entity is already registered
with MCC."
If in contrast I execute: REGISTER NODE <fullname>
CREATE DOMAIN <domain> MEMBER <fullname>
Telling both "Successful" ...
trying to open the domain in which the node was put (only entity in
that domain) gives the message:
The requested operation cannot be completed,
"%MCC-E-NOATTRIB, no such DNS attribute", of course not telling about
which attribute it handles.
Isn't this confusing !
But more to the ground:
Where in DNS is the REGISTRATION_FM, in combination with the NODE_AM,
is doing what. Does some document clarifies the DNS requirements for
each entity class registration ?
Regards,
Dominique.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5432.1 | same problem, no solution. | KETJE::PACCO | Gallia divisa est in partes tres | Thu Aug 05 1993 05:07 | 90 |
| The same problem, but seen with trace bits on.
MCC_DB_LOG = FF
MCC_REGISTRATION_FM_LOG = FF
Before registration is the object in DNS, without any MCC attributes.
During registration:
MCC> register node .bkc.m.rbkc01 synonym rbkc01
Entering REGISTER
IN_ENTITY:
entity [0] wild = NOT_WILD class = 1 id = 1 type = 5
instance = ..+,y..u72+u......bkc..m..rbkc01..
%X08002B2C791E097537B22BF5950012000103626B6301016D010672626B6330310000
IN_P:
[ 0 ] (
[ 0 ] 72 62 6b 63 30 31 -- rbkc01
)
IN_Q:
Found class node 1 in dict list
Entering routine cfg_get_operation_mode:
p_dsc_in_p is
[ 0 ] (
[ 0 ] 72 62 6b 63 30 31 -- rbkc01
)Leaving routine cfg_get_operation_mode:
Operation mode id is 0
p_new_dsc_in_p is
[ 0 ] (
[ 0 ] 72 62 6b 63 30 31 -- rbkc01
)
Get registration state from DNS:
Global entity
entity [0] wild = NOT_WILD class = 1 id = 1 type = 5
instance = ..+,y..u72+u......bkc..m..rbkc01..
%X08002B2C791E097537B22BF5950012000103626B6301016D010672626B6330310000
DNS attribute name is MCC_REGISTRATION_STATE
Global entity exists
registration state is 0
OUT_P:
[ 6 ] (
)
Returning from Register
Node bc:.bkc.m.rbkc01
AT 1993-08-05-09:57:52.307
NameSpace Access Denied.
MCC>
And after (partial) registration occured the only MCC STUFF in dns is:
dns> ....
DNS$CTS = 1993-08-05-07:52:48.578/08-00-2b-2c-7b-28
DNS$UTS = 1993-08-05-07:57:53.592/08-00-2b-2c-7b-28
MCC_Class = %x01000000
MCC_UID = %x4a43bf775991cc010000aa0004000504
MCC_Version = %xa68200089f817d0456010300
There is no MCC_REGISTRATION_STATE attribute why ?
Regards
Dominique.
|
| 5432.2 | What are the minimal access rights? | KETJE::PACCO | Horum omnium fortissimi sunt Belgae | Thu Aug 05 1993 15:17 | 32 |
| According the NODE4 entity (not NODE !) use manual, DECmcc requires
WRITE and DELETE access to the directories in the network-wide
namespace (This is not very precise !).
I granted explicitely R,W,D,T access to DECmcc for the following
directories:
.dna_nodesynonym
.dna_backtranslation.%x49.%xnnnn
.<working_directory>
With this access setup, the NameSpace Access Denied message still
holds.
If finally I gave ALL rights to ALL directories, I could register
my node.
QUESTION:
1). Which are the required rights in which directories for NODE
registration.
2). Why is DELETE access required to the DIRECTORY (cfg DECnet Phase IV
Access Module Use page 3-4), as a node(4?) object
can be created and deleted with WRITE access to the directory in
which it is created ? DELETE access allows the deletion of the
directory, which is in our case not authorised !
Kind regards,
Dominique.
|