[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

4020.0. "Re-register Phase V with 1.2.3 ?" by WELLIN::MCCALLUM () Tue Nov 03 1992 13:07

    
    In the release notes for 1.2.3 is suggests that you can deregister and
    reregister Phase V end systems to get performance improvements.
    
    I had some problems when I deregistered Phase V systems with MCC, as it
    deleted everything from the namespace, including things which had been
    put there by auto-registration by DECnet. Also after I had done this
    autoregistration wouldn't work for the node I had de-registered (this
    may have been because of DNS problems - it was a DNS server and
    obviously couldn't join the namespace properly as there was no entry
    for it in the namespace.
    
    Is the deregistering and re-registering of Phase V nodes easy - how
    will towers be set up ?
    
    Dave.

T.R Title User Personal
Name Date Lines

4020.1 Don't Re-register, add children TOOK::CAREY Mon Nov 09 1992 17:16 32

T.R	Title	User	Personal Name	Date	Lines
4020.1	Don't Re-register, add children	TOOK::CAREY		`Mon Nov 09 1992 17:16`	32
	No, it's not easy. Thanks to other notes in here we have pulled the reference in the release notes and restructured the approach to solving this problem. We don't run our test environment here in the same namespace as the DECnet/OSI auto-registration, so while we're aware of this problem it is too easy to overlook. On the expectation that most of our sites have only a few DECnet/OSI nodes active at this time, here is how you do it (as documented in the release notes to go to customers): 1) Get the list of DECnet/OSI nodes in your network. 2) Hand register all of the first level children of the DECnet/OSI node (at least all of the modules). We are putting a sample into the release notes that can be cut out to create a one parameter .COM file or shell script for performing this registration for an entire global entity. If you have only a limited number of Nodes in your setup, this is easy and fast. Let us know if you are dealing with a large DECnet/OSI environment. We understand that hand re-registering a large number of Nodes can be a major hassle. We are taking steps to solve this problem for V1.3, and will try to help on a case by case basis. -Jim Carey

    
    No, it's not easy.
    
    Thanks to other notes in here we have pulled the reference in the
    release notes and restructured the approach to solving this problem.
    
    We don't run our test environment here in the same namespace as the
    DECnet/OSI auto-registration, so while we're aware of this problem it
    is too easy to overlook.
    
    On the expectation that most of our sites have only a few DECnet/OSI
    nodes active at this time, here is how you do it (as documented in the
    release notes to go to customers):
    
    1) Get the list of DECnet/OSI nodes in your network.
    
    2) Hand register all of the first level children of the DECnet/OSI
       node (at least all of the modules).  We are putting a sample into
       the release notes that can be cut out to create a one parameter .COM
       file or shell script for performing this registration for an entire
       global entity.
       
    If you have only a limited number of Nodes in your setup, this is easy
    and fast.
    
    Let us know if you are dealing with a large DECnet/OSI environment.  We
    understand that hand re-registering a large number of Nodes can be a
    major hassle.  We are taking steps to solve this problem for V1.3, and
    will try to help on a case by case basis.
    
    -Jim Carey