[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2614.0. "rename questions" by COL01::LUNT () Mon Mar 23 1992 12:54

Hi,

	Several nodes in our network were recently moved to another
area and we wanted to rename them on our DECmcc machine. We ran into
the following problems/questions.

1. Exactly what steps does a "rename" directive do? Does it effect the
local MCC host database only, or does it actually try to change the address
at the remote node? If this is true, then  how does one only "update" MCC
as to the new address(Updating the NCP database with set/define, corrupts
the DNS name space and the enitity and it's DNS links must then be deleted
via dns$control)?

2. Why the difference when one uses the node4 synonym and the full DNS name?
Example:(the no privilege message is ok, I was just trying to create an
example and didn't really want to change anything)

MCC> rename node4 bylv21 remote node 1.398 address 1.6

Node4 1.82 Remote Node 1.398
AT 23-MAR-1992 18:24:03

The requested operation cannot be completed
            MCC Unhandled Service Reply = No privilege to perform directive 
					  at Node.

MCC> rename node4 .eu.by.byl.bylv21 remote node 1.398 address 1.6

Node4 DECNOS_NS:.eu.by.byl.bylv21 Remote Node 1.398
AT 23-MAR-1992 18:25:14

The requested operation cannot be completed
            MCC Unhandled Service Reply = Node is not registered.

MCC> rename node4 bylv21 remote node byls57 name mist

Node4 1.82 Remote Node 1.398
AT 23-MAR-1992 18:37:45

The requested operation cannot be completed
            MCC Unhandled Service Reply = No privilege to perform directive 
					  at Node
.
MCC> rename node4 .eu.by.byl.bylv21 remote node byls57 name mist

Node4 DECNOS_NS:.eu.by.byl.bylv21 Remote Node byls57
AT 23-MAR-1992 18:38:02

The requested operation cannot be completed
            MCC Unhandled Service Reply = Node is not registered.


3. Although this is given as an example in the book, it doesn"t work:
(page 5-21 of the PHASE IV Access Module Use, Field Test Version)

MCC> rename node4 .eu.by.byl.bylv21 remote node 1.398 name mist

Node4 DECNOS_NS:.eu.by.byl.bylv21 Remote Node 1.398
AT 23-MAR-1992 18:33:46

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-IDMISMATCH, new identifi 
					  type does not match old 
					  identifier type.

                           
MCC> rename node4 bylv21 remote node 1.398 name mist

Node4 bylv21 Remote Node 1.398
AT 23-MAR-1992 18:35:34

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-IDMISMATCH, new identifier
                               type does not match old identifier
                                          type
MCC>



Thanks,

Julie Ann

T.R	Title	User	Date	Lines
2614.1	rename	MCC1::MULLIGAN	`Mon Mar 30 1992 15:14`	105
	>1. Exactly what steps does a "rename" directive do? Does it effect the >local MCC host database only, or does it actually try to change the address >at the remote node? If this is true, then how does one only "update" MCC >as to the new address(Updating the NCP database with set/define, corrupts >the DNS name space and the enitity and it's DNS links must then be deleted >via dns$control)? RENAME dispatches to the REGISTRATION FM which does the following: o Checks that the identifier that you are renaming is the same type as the identifier you are renaming to, for example name to name or address to address. o calls the AM RENAME entry point. If the AM provides a rename directive then this is executed. o If you rename the fullname of a global entity then find all the domains that this global entity is a member of and rename the domain members o Rename the specified identifier in the configuration instance repository. For example NODE4: NODE4 has three identifiers, Registered Name (DNS fullname), Name (phase4name) and Address. MCC> dir node4 rampal Node4 rampal AT 30-MAR-1992 13:14:14 Directory successful. Registered Name = MCC1_NS:.RAMPAL Name = RAMPAL Address = 4.315 You can rename the Registered Name (DNS fullname) with a command like: MCC> rename node4 .rampal registered name = .palram Node4 MCC1_NS:.rampal AT 30-MAR-1992 13:32:37 Rename completed successfully. MCC> dir node4 4.315 Node4 4.315 AT 30-MAR-1992 13:34:36 Directory successful. Registered Name = MCC1_NS:.palram Name = RAMPAL Address = 4.315 You could rename the Name (phase4name) with a command like: MCC> rename node4 rampal name palram Node4 4.315 AT 30-MAR-1992 13:48:35 The requested operation cannot be completed MCC Unhandled Service Reply = No privilege to perform directive at Node. In this case the identifiers were checked and found to be of the same type Name (phase4name). The AM RENAME entry point was called, the AM attempted to change the node name and the command failed with no privilege to perform directive. You could update the local remote node database with a command like this: MCC> show node4 0 remote node rampal Using default ALL IDENTIFIERS Node4 4.775 Remote Node 4.315 AT 30-MAR-1992 13:55:33 Identifiers Examination of Attributes shows: Address = 4.315 Name = RAMPAL MCC> rename node4 0 remote node rampal name = palram Node4 4.775 Remote Node rampal AT 30-MAR-1992 13:55:54 Rename completed successfully. MCC> show node4 0 remote node 4.315 Using default ALL IDENTIFIERS Node4 4.775 Remote Node 4.315 AT 30-MAR-1992 13:56:23 Identifiers Examination of Attributes shows: Address = 4.315 Name = PALRAM >at the remote node? If this is true, then how does one only "update" MCC >as to the new address(Updating the NCP database with set/define, corrupts >the DNS name space and the enitity and it's DNS links must then be deleted >via dns$control)? Using NCP updates the NCP databases, this may put your MCC database out of synch but in will not "corrupt" your MCC database. In the worst case deregister and reregister the affected nodes. Please see note 2519.1 for more information.
2614.2	more questions........	COL01::LUNT	`Fri Apr 10 1992 12:42`	230
	Hi, Well, I just installed MCC t1.2.18 and am trying to figure out this rename stuff again. To recap, I am trying to determine how to update my mcc node when entity identifiers such as address or name change. Below are several examples. I have noticed that from Vt1.2.4 (as used in the original note) differs slightly from t1.2.18. Secondly, it looks as if the rename directive doesn't clean up the different DNS links that create the pointers between node synonym, address and registered name. Thanks in advance for any info/help in this matter, Julie Ann To start off: From what I can tell the following is true: DIRECTORY reads the information out of DNS that was input at time of registration. ex: ex: dir node4 byls57 Node4 byls57 AT 10-APR-1992 14:43:31 Directory successful. Registered Name = DECNOS_NS:.eu.by.byl.byls57 Address = 1.398 Name = byls57 SHOW asks the entity in question to supply the information ex: show node4 byls57 Using default ALL IDENTIFIERS Node4 1.398 AT 10-APR-1992 15:31:14 Identifiers Examination of Attributes shows: Address = 1.398 Name = BYLS57 So assume that "BYLS57" show recieves the new name "MIST": example 1: Rename only the name "BYLS57" -> "MIST" (or Node Synonym): rename node4 0 remote node byls57 name mist Node4 1.82 Remote Node byls57 AT 10-APR-1992 15:03:08 Rename completed successfully. dir node4 byls57 Node4 byls57 AT 10-APR-1992 15:03:17 Directory successful. Registered Name = DECNOS_NS:.eu.by.byl.byls57 Address = 1.398 Name = byls57 dir node4 mist Node4 mist AT 10-APR-1992 15:03:26 The entity Node4 mist is not registered Not Registered Entity = Node4 mist show node4 mist Using default ALL IDENTIFIERS Node4 1.398 AT 10-APR-1992 15:23:14 Identifiers Examination of Attributes shows: Address = 1.398 Name = BYLS57 show node4 byls57 Using default ALL IDENTIFIERS Node4 byls57 AT 10-APR-1992 15:23:39 Identifiers Node does not exist or is not known to local Node. example 2: Rename the name and registered name: "BYLS57" -> "MIST" ".EU.BY.BYL.BYLS57" -> ".EU.BY.BYL.MIST" rename node4 0 remote node byls57 name mist Node4 1.82 Remote Node byls57 AT 10-APR-1992 15:33:39 Rename completed successfully. rename node4 .eu.by.byl.byls57 registered name .eu.by.byl.mist Node4 DECNOS_NS:.eu.by.byl.byls57 AT 10-APR-1992 15:34:54 Rename completed successfully. dir node4 byls57 Node4 byls57 AT 10-APR-1992 15:37:05 Directory successful. Registered Name = DECNOS_NS:.eu.by.byl.mist Address = 1.398 Name = byls57 dir node4 mist Node4 mist AT 10-APR-1992 15:37:44 The entity Node4 mist is not registered Not Registered Entity = Node4 mist show node4 byls57 Using default ALL IDENTIFIERS Node4 byls57 AT 10-APR-1992 15:38:29 Identifiers Node does not exist or is not known to local Node. show node4 mist Using default ALL IDENTIFIERS Node4 1.398 AT 10-APR-1992 15:38:47 Identifiers Examination of Attributes shows: Address = 1.398 Name = BYLS57 example 3: Rename only the Registered name ".EU.BY.BYL.BYLS57" -> ".EU.BY.BYL.MIST" rename node4 .eu.by.byl.byls57 registered name .eu.by.byl.mist Node4 DECNOS_NS:.eu.by.byl.byls57 AT 10-APR-1992 15:41:16 Rename completed successfully. Node4 byls57 AT 10-APR-1992 15:42:26 Directory successful. Registered Name = DECNOS_NS:.eu.by.byl.mist Address = 1.398 Name = byls57 dir node4 mist Node4 mist AT 10-APR-1992 15:42:44 The entity Node4 mist is not registered Not Registered Entity = Node4 mist show node4 mist Using default ALL IDENTIFIERS Node4 mist AT 10-APR-1992 15:43:00 Identifiers Node does not exist or is not known to local Node. show node4 byls57 ode4 1.398 AT 10-APR-1992 15:43:25 Identifiers Examination of Attributes shows: Address = 1.398 Name = BYLS57 show node4 .eu.by.byl.mist Using default ALL IDENTIFIERS Node4 1.398 AT 10-APR-1992 15:43:51 Identifiers Examination of Attributes shows: Address = 1.398 Name = BYLS57 example 4: rename address "1.398" -> "50.1" RENAME NODE4 0 REMOTE NODE 1.398 ADDRESS 50.1 Node4 1.82 Remote Node 1.398 AT 10-APR-1992 15:52:38 The requested operation cannot be completed MCC Unhandled Service Reply = DECnet Phase IV management protocol error.
2614.3	time is running short, need an answer	COL01::LUNT	`Thu Apr 16 1992 14:40`	11
	Hi, I really need some help here. We will moving lots of nodes to new areas in two weeks, and I would like to not have to deregister and newly register them all, because then my reference data is also gone. Perhaps this should be submitted in the QAR system?? Thanks, Julie Ann
2614.4	you may be renaming the wrong entity	KAJUN::NELSON	`Thu Apr 16 1992 14:55`	38
	re: -1 It looks like you are renaming the wrong entity and that is why you are having the problem. The follwing command mcc> rename node4 0 remote node xxx name = yyy ________________________ ^ \| target entity changes the entry in the local phase 4 remote node database from xxx to yyy, it DOES NOT change the name of the phase 4 node xxx to yyy. You need specify the phase 4 node itself as the target of the command, not the entry in the local remote node database. Enter the following command: mcc> rename node4 xxx name = yyy _________ ^ \| target entity mcc> rename node4 4.628 address = 6.112 _________ ^ \| target entity This should work for you. ...kjn
2614.5	Perhaps this should be qared?????	COL01::LUNT	`Tue Apr 28 1992 09:39`	33
	Hello kjn, Just as I feared, when I use the rename as you suggested, it tries to talk with the node and rename the node itself. I NEED a way to update only my mcc node, but not the remote node itself. The remote nodes are managed by the local system manager. The DECmcc node and database is managed by me and I need to keep it uptodate. As of right now, I only see reregistering everything, but is that a pain....... Julie Ann dir node4 byls57 Node4 byls57 AT 28-APR-1992 13:35:47 Directory successful. Registered Name = DECNOS_NS:.EU.BY.BYL.BYLS57 Address = 1.398 Name = byls57 rename node4 byls57 name = mist Node4 1.398 AT 28-APR-1992 13:36:38 The requested operation cannot be completed MCC Unhandled Service Reply = No privilege to perform directive at Node.