[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

91.0. "Questions about TCPIP/SNMP name translation" by ASD::MINTZ (Erik Mintz, MS ZKO3-2/S11, dtn 381-2331) Tue Apr 03 1990 19:10


  We have the SNMP access module up and running.  A few questions

1) If UCX has a host defined with an uppercase alias, why is it
   still necessary to enter a quoted name in a show command?

2) You are right, it is not possible to access an entity that is
   defined by the bind service rather than the local UCX database.
   Is that related to the lack of native support for IP domain style
   names?  I would have thought that MCC> SHOW TCPIP XPLORE should work
   since UCX> SHOW HOST XPLORE works.

3) Once there is support for TCPIP entities in DOMAIN and it is possible
   to REGISTER them, will it still be necessary to define the host
   names in the local UCX database as well?  If so, this leads to messy
   results to a MCC> show tcpip *, since domain may return many entities,
   and each one will generate a failure if the name is not also defined
   in the local database. The comparable problem exists for NODE4;
   See not 71 and replies.

T.R Title User Personal
Name Date Lines

91.1 more info CSEVEN::DANIELE SNMP, right here & now. Tue Apr 03 1990 19:41 30

T.R	Title	User	Personal Name	Date	Lines
91.1	more info	CSEVEN::DANIELE	SNMP, right here & now.	`Tue Apr 03 1990 19:41`	30
	Hi Erik, Glad to hear from you! 1. Latin1Strings must be enclosed in quotes, whatever they are used for. That's just how they work in mcc. 2. There are really 2 aspects of internet domain names to consider, and I forgot one of them in the release notes. What I mentioned was that domain names like "took.nac.dec.com" won't work. This is because the temporary parsing routines in the AM assume anything with a "." is an IP address. You'll get an "internal logic error". What I didn't mention was that the UCX 1.3 FT software does NOT use the BIND resolver for SHOW HOST requests issued thru their QIO interface. Since that's what the AM uses, mcc doesn't get access to BIND for now. UCX 1.3 will eventually support this, in which case you are correct, the name resolution of MCC> show tcpip "xplore" will be exactly that of UCX> show host xplore. 3. Yes, REGISTERing tcpip systems presents problems analogous to phase IV, probably even worse. I don't have any answers yet. Cheers, Mike

	Hi Erik,

	Glad to hear from you!

	1.  Latin1Strings must be enclosed in quotes, whatever they are used 
	    for.  That's just how they work in mcc.

	2.  There are really 2 aspects of internet domain names to consider,
	    and I forgot one of them in the release notes.

	    What I mentioned was that domain names like "took.nac.dec.com" 
	    won't work.  This is because the temporary parsing routines in the
	    AM assume anything with a "." is an IP address.  You'll get an
	    "internal logic error".

	    What I didn't mention was that the UCX 1.3 FT software does NOT
	    use the BIND resolver for SHOW HOST requests issued thru their
	    QIO interface.  Since that's what the AM uses, mcc doesn't get
	    access to BIND for now.
	    
	    UCX 1.3 *will* eventually support this, in which case you are 
	    correct, the name resolution of MCC> show tcpip "xplore" will 
	    be exactly that of UCX> show host xplore.

	3.  Yes, REGISTERing tcpip systems presents problems analogous to
	    phase IV, probably even worse.  I don't have any answers yet.


	Cheers,
	Mike