[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

1459.0. "PROBLEM: Historian & NODE4 (router)-nodes" by STKHLM::BERGGREN (Nils Berggren EIS/Project dpmt, Sweden DTN 876-8287) Fri Sep 06 1991 08:31

I'm forwarding a problem encountered at the bank we're working at
regarding recording on NODE4 -nodes.  The guy having the problem
is one of the operators setting up DECmcc for their network.

I've looked at it and I don't understand it either.

   regards,
   Nils
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
		Problems with Historian FM and NODE4 AM

BACKGROUND:
	I have populated a domain: seb_dmn.router with 4 NODE4 nodes (3 DEC-
	routers 2000 and one X25router 2000). They are called ZH0453, ZH0454, 
	ZGBG50 and ZMLM50. (The first is the X25 router the rest is DECrout-
	ers) Then I submitted the file mcc_historian_background in sys$manager
	with the parameter: "seb_dmn.router" without any problems. Via the 
	Iconic PM I clicked my self to each node to start recording some enti- 
	ties like circuit SYN-1, everything went OK. I also check by the "SHOW
	RECORDING" menue to see that it looked OK. My recording was only used 
       	with partion counters and the default values was chosen in menue.

PROBLEM:
	When I tried to start recording on the last node called ZMLM50 i got 
	back the message "Entity is not registered" for every entity I tried to 
	record. I even tried to record counters for the actual node itself 
	with the same message. Still I can access all these entities by the 
	"SHOW STATUS, COUNTERS.....  menues without any problems, so it seems 
	that the entities indeed are registred (!?) I also checked in DNS to 
	see if the node (ZMLM50) was a member of the domain (seb_dmn.router), 
 	and it was. Any ideas ????

	Michael Zucker
        S-E-Banken/SEB Data
T.RTitleUserPersonal
Name		DateLines
1459.1check "Show ... All Ident" and "Directory..."TOOK::SHMUYLOVICHFri Sep 06 1991 11:0326
	RE: .0

      In order to check if entity specified in the Record command is 
  registered the Historian FM performs the following steps:

	1. Calls "Show <specified entity> All Identifiers";

	2. Calls "Directory <entity_out_from_previous_call>".

      The "Entity is not registered" message tells that the second call
  fails.

     Would you please repeat the following two commands from FCL (IMPM 
  does not allow you to specify <entity_out_from_previous_call> in the 
  second command !!) and put the result of these commands here or 
  mail it to me (TOOK::SHMUYLOVICH):

	1. Show node4 .zmlm50 all ident

	2. Dir node4 <instance_of_entity_out_from_previous_call>

     I hope this can help to locate your problem.

	Sam
1459.2RE: .1 -- event more confused...STKHLM::BERGGRENNils Berggren EIS/Project dpmt, Sweden DTN 876-8287Mon Sep 09 1991 06:5744
RE: .1
    
    
I tried the following commands after your advice:
    
MCC> show node4 .mlm.dna_node.zmlm50 all id

Node4 1.899
AT  9-SEP-1991 09:55:30 Identifiers

Examination of Attributes shows:
                                Address = 1.899
                                   Name = ZMLM50
MCC> dir node4 1.899

Node4 1.899
AT  9-SEP-1991 09:55:41

No such entity: Node4 1.899
                         Unknown Entity = Node4 1.899


Since the node exists and looks normal in DNS, I got this "wild" idea to
correct the problem by DEREGISTER and REGISTER the node in MCC from FCL
I got the following results:


MCC> deregister node4 1.899

Node4 1.899
AT  9-SEP-1991 10:48:23

No such entity: Node4 1.899
                         Unknown Entity = Node4 1.899
MCC> register node4 seb:.mlm.dna_node.zmlm50 synonym zmlm50

Node4 SEB:.mlm.dna_node.zmlm50
AT  9-SEP-1991 10:49:51

The requested operation cannot be completed
                  Entity Existence Info = Entity Exists
MCC>

Any ideas ??
1459.3nodeaddress link is missing from DNSTOOK::SHMUYLOVICHMon Sep 09 1991 17:1328
	Thanks for your experiment, it helped a lot.
 It shows that it's nothing wrong with Historian FM.
 When Historian tries to call Directory it receives
 "No such entity" message and converts it to the
 "Entity is not registered".

 Now the problem is "What is wrong with node4 ZMLM50
 and Registration". Thanks to Jill C. and Edison T. 
 they explained me  how directory works using node address.
 When node address is specified a special link in DNS
 is used to find a requested object. In your case 
 it looks like this link is missing ( or has been deleted
 using DNS). If more details are desired, please, ask 
 for description of the Directory command.

  This is a procedure how to correct your situation:

	1. > mcr dns$control
	2. dns> delete link .dna_nodesynonym.zmlm50
	3. dns> delete object .mlm.dna_node.zmlm50
	4. dns> exit

   Now you can register this node4 and set up recordings.


	Regards Sam