[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

5209.0. "IDP pre-dsp and DNS" by WIZZER::MACLEAN (A Pure Dear in a Wicked World) Wed Jun 16 1993 13:24

Hi ,

I have a customer who has a non-default IDP with a dsp ,he has just upgraded to
MCC/Polycentre Network Manager 1.3 ..On his DNS server node will he now need to
modify the DNS directory structure to reflect the new addition in this  release
of the  pre-dsp as per release notes   ?? ......

"if the pre-DSP is defined for your network, you must include the
 value of the pre-DSP as the IDP value.  The format is afi:idi:pdsp "

...and If so,what is the recommended way of doing so
( sorry if this is documented but we could not find it)

Thanks,

Sandie.../Comm.s
T.RTitleUserPersonal
Name		DateLines
5209.1Anyone ?....WIZZER::MACLEANA Pure Dear in a Wicked WorldThu Jun 17 1993 10:4110
    
    
    .....Has anyone anywhere seen a site using a pre-dsp ,where they 
    could check the DNS namespace for me ?
    
    Yours hopefully,
    
    Sandie..../
5209.2An example of NSAP and Pre-DSPTOOK::KWAKThu Jun 17 1993 10:5539
    
    

The user visible format of an NSAP (network service access point) is shown
below.

	dd:dd-dd-...-dd:xx-xx-...-xx-xx-xx:xx-xx-xx-xx-xx-xx-:xx
      |AFI|   IDI      |  Pre-DSP   |Loc- |  Node-id         |N-sel|
      |   |            |            | Area|                  |     |
      |<----IDP------->|<---------------DSP----------------------->|
 
Where
   AFI - As two decimal digits, in the range "0" to "9",
   IDI - If present, the IDI value is displayed as a series of decimal
	 digits, in the range "0" to "9", with no internal separators,
   Pre-DSP and Loc-Area - These are always displayed together as a 
	 series of hexadecimal digits. Each digit will fall into the
	 range "0" to "F". For readability, octet values (i.e. every
	 two digits) are separated by dashes ("-").
	The "Loc-Area" is always two octets in length.

In the following example

	41:345:06-78-00-8A:02-34-56-78-9A-BC:20

the NSAP consists of the AFI of "41", an IDI of "345", a Pre-DSP of
"678", and Loc-Area of "8A" (the Pre-DSP is padded with a leading
"0" digit, and the Loc-Area is padded with two leading "0" digits).

    
For more information, see NOTED::DNS notes conference topic #878.
    
    
William
    

NOTE: The information is extracted from "Phase V Usage of the DECdns 
      Namespace" written by Stan Goldfarb (1990).
5209.3Leave DNS alone or not?WIZZER::MACLEANA Pure Dear in a Wicked WorldThu Jun 17 1993 11:4015
    
    Thank you for your reply and your DNS pointer,
    
    The Hub of my question I guess is:
    
    Will this addition of a Pre-dsp mean MCC will need it's Remote DNS 
    server directories modified (I presume this is the case). 
    
    What is the best way  of  doing this  given  that  previously  he 
    had  a  Non-default IDP * without * a  pre-dsp under MCC v1.2-3  
    and a DNS Server  directory structure that reflects this ?
    

    Sandie..../
5209.4Use DNS softlink as alternate directory nameTOOK::KWAKThu Jun 17 1993 14:0643
    
>    Will this addition of a Pre-dsp mean MCC will need it's Remote DNS 
>    server directories modified (I presume this is the case). 
>
>    What is the best way  of  doing this  given  that  previously  he 
>    had  a  Non-default IDP * without * a  pre-dsp under MCC v1.2-3  
>    and a DNS Server  directory structure that reflects this ?
    
     The definition of MCC_NODE_IDP to include the Pre-DSP was not
     new addition, but the correction.
    
     If you have subdirectories in .DNA_Backtranslation directory
     which does not take pre-DSP into account, I guess that Phase5
     systems cannot make use of phase4 address backtranslation links
     created by DECmcc in .DNA_Backtranslation.*.*.*.
    
     One way of accessing same directory with different names in DECdns
     is using 'softlink'. Suppose you are accessing directory
     .DNA_Backtranslation.%X470021 (used by V1.2.3 MCC) with new name
     .DNA_Backtranslation.%X47002180001000 (used by V1.3 MCC), you can
     create a softlink:
    	DNS> create link .DNA_Backtranslation.%X47002180001000  
    		.DNA_Backtranslation.%X470021
     In this case, you have one DNS tree rooted at
     .DNA_Backtranslation.%X470021, but can be accessed by
     either MCC_NODE_IDP of 47002180001000 or MCC_NODE_IDP of
     47002180001000.
    
     You may ask questions on how Phase V systems use .DNA_Backtranslation
     directoy in 12dot2::phasev notes file.
    

    The DECmcc is just a user of DECdns directories.
    The DECdns should have been set up properly according to the 
    customer' IDP value.
    
    In order to access .DNA_Backtranslation.... directory from DECmcc,
    the logical MCC_NODE_IDP has to be set properly (IDP plus pre-DSP).
    
    What kind of subdirectories are under .DNA_Backtranslation directory
    in the DECdns namespace?
    You was your customer's MCC_NODE_IDP in V1.2.3?
    You is  your customer's MCC_NODE_IDP in V1.3?