[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

2636.0. "Can't have NODE and NODE4 in same namespace!?" by RUMOR::FALEK (ex-TU58 King) Thu Mar 26 1992 14:01

    I'd like to put together a spiffy demo in which you can double click in
    the MCC iconic map on the icon for a node, and see all the components
    (EMA compliant servers and applications) running there.   I have a working
    MOM for DECscheduler, built with the VMS common agent and DMS. I am doing
    my testing in the DEC: namespace, since we want to test MCC the way we
    hope it might eventually be used in the Company (in the enterprise
    namespace, not 100's of disjoint private namespaces)
    
    Unfortunately, we can't do this demo the way we'd like, because we
    can't have a NODE and a NODE4 with the same name in the same namespace;
    they share the same DNS backlinks, so if I try to REGISTER my node, it
    tells me there is already a NODE4 entity with that name registered.
    
    Can something be done about this ?

T.R	Title	User	Personal Name	Date	Lines
2636.1		TOOK::STRUTT	Management - the one word oxymoron	`Tue Apr 07 1992 11:33`	8
	Lou, Although this does not answer the question directly, you can certainly create a 'domain' that represents the one system, and within the domain have the different 'components' represented (such as a NODE, NODE4, and any other software components that might have their own global entities) Colin
2636.2	Domains are not a solution	RACER::dave	Ahh, but fortunately, I have the key to escape reality.	`Tue Apr 07 1992 12:49`	14
	Colin, I don't see how using a domain to "represent the system" solves the problem. The basic issue is that NODE and NODE4 have special interrelated actions. Even with a special "domain" for the system, you still need to register that end system as both a node4 and node within that domain, somthing that cannot, currently, be done.
2636.3	Needs some hacking	BIKINI::KRAUSE	European NewProductEngineer for MCC	`Fri Apr 10 1992 10:43`	31
	I just managed to register a DECnet/VAX Extension system both as NODE and NODE4. But it needed some DNS hacking... Here is what I did: Do a Phase V register register node .muh.pv.munosi syn munosi Use DNS$CONTROL to delete the - just created - links in dna_nodesynonym and in dna_backtranslation.%x49.%x00nn Do a Phase IV register register node4 .muh.dn.munosi syn munosi Note the different DNS directory (.pv. vs .dn.) You cannot use the synonym for Phase V (pretty obvious, because you deleted it...). This turned out to be a real problem, because a DECnet/VAX Extension system needs to be managed by both Phase IV and Phase V protocols (you need Phase V for X.25). *Robert P.S.: To register a DECnet/VAX Extension system as Phase V (node) you need BYPASS privilege at this system. Otherwise it will refuse to respond to requests for the node entity!