    DESCRIPTION:(                       DECnet/OSI Phase V4                       ------------------------------9                       Making the Transition from Phase IV       L This document introduces DECnet/OSI Phase V -- its design, new features, andM enhancements from DECnet Phase IV.  It also highlights the benefits of making ( the transition from Phase IV to Phase V.H After outlining Phase V concepts and terminology, this document presentsO preliminary guidelines for making the transition from a DECnet Phase IV network I to DECnet/OSI Phase V.  These guidelines introduce appropriate transition < methods and sample procedures for various kinds of networks.M The intended audience comprises network managers and network planners who are G familiar with the DECnet DIGITAL Network Architecture (Phase V) General  Description. Contents+ Phase V:  Digital's Commitment to OSI     1       &         Open Systems Integration     1)         DECnet/OSI Phase V Features     2 %         Phase V Product Support     4 " Phase V:  Elements of Change     7&         Distributed Name Service     7          Network Management     9         Applications     10          Addressing     12          End Nodes     13         Routers     14!         VAXcluster Systems     16 !         Node Configuration     16 & Phase V:  Making the Transition     18+         Preparing for the Transition     18 2         Planning and Creating the Namespace     221         Transition of LANs Without Routers     26 1         Transition of Single-Area Networks     26 .         Transition of Multiarea Networks    29 Key Terms     30)                                         i       % Phase V:  Digital's Commitment to OSI N Digital Equipment Corporation continues as the industry leader in networks andL communications with its fifth generation of the Digital Network ArchitectureD (DNA) -- DECnet/OSI Phase V.  By providing an OSI-based multivendor,O multiprotocol network, Digital is in the forefront of open systems integration.  Open Systems Integration The greatest advance of Phase V is that it offers full OSI support within theThe greatest advance of Phase V is that it offers full OSI support within the DECnet environment. J Open System Interconnection (OSI) refers to the implementation of a set of      G international standards developed by the International Organization for C Standardization (ISO) and the International Telegraph and Telephone D Consultative Committee (CCITT) for networks and networking products.G DECnet/OSI Phase V fully supports the efforts within ISO for successful # interoperation of systems in global  multivendor networks. M DECnet/OSI Phase V uses the OSI addressing scheme.  ISO protocols and the OSI G addressing scheme enable OSI-based products from all vendors, including K Digital, to interoperate.  DECnet/OSI Phase V supports OSI in the following  ways: K o       Automatically delivers OSI to DECnet nodes with an operating system (         upgrade or new network software.L o       Enhances DECnet products with the ISO standards, enabling DECnet/OSIH         Phase V routers to send and receive both Digital and non-Digital         OSI packets.F o       Provides complete OSI implementations.  DECnet/OSI systems can      3         participate in other vendors' OSI networks. )                                         1  DECnet/OSI Phase V Features G DECnet/OSI Phase V provides many new features, including the following: N o       Backward compatibility -- DECnet/OSI Phase V is compatible with DECnetH         Phase IV.  Phase V allows supported Digital products to continue"         successful communications.N o       OSI applications support -- With DECnet/OSI Phase V, Digital continues      D         to support existing OSI applications such as FTAM and X.400.O         DECnet/OSI Phase V also enables support for new OSI applications as new          standards emerge. F o       End node support -- Phase V supports multivendor OSI end nodesK         connected to either LANs or WANs.  DECnet/OSI Phase V end nodes can K         have multiple links.  Phase V end nodes cache information to select M         the appropriate circuit for sending data to a particular destination. J         In addition, after completing the transition to Phase V, end nodes7         automatically generate their network addresses. N o       Distributed Name Service (DNS) -- Phase V uses DNS to store node namesN         and obtain protocol selection information.  The DNS namespace replaces*         the DECnet Phase IV node database.O o       Network management -- Phase V network management includes a new command N         interface, the Network Control Language (NCL), and is based on the ISOK         draft international standard Common Management Information Protocol I         (CMIP).  Modular and consistent for all Phase V products, Phase V       N         network management offers continued support for management of Phase IV         nodes.H o       Data Link layer support -- Phase V supports High-level Data LinkK         Control (HDLC).   HDLC support includes the LAPB protocol, which is L         used for X.25 communications.  Phase V also continues to support the=         Digital Data Communications Message Protocol (DDCMP). J         Phase V supports both the ISO 8802-3 (IEEE 802.3) and the EthernetM         standards for the Carrier Sense Multiple Access with Collision Detect           (CSMA/CD) class of LANs.N         In addition, for DECservers and DECrouters, Phase V provides continued"         down-line loading support.)                                         2       G o       Routing layer support -- ISO refers to the Routing layer as the K         Networking layer.  This layer supports the ISO addressing standard. O         Phase V enables communications among multivendor systems and supports a 8         range of networks from small to extremely large.O         Using the ISO Internetwork Protocol, the Phase V Routing layer supports I         the ISO Connectionless-mode Network Service (CLNS).  Phase V also H         supports the ISO Connection-mode Network Service (CONS), used by3         systems attached to or accessing X.25 WANs. K         The Phase V Routing layer allows Digital and non-Digital systems to N         occupy the same routing domain.  This layer also enables connection toF         other routing domains that are not using Phase V routing.  TwoJ         DECnet/OSI networks can connect and still maintain their autonomy.O o       Transport layer support -- Phase V supports the OSI Transport Protocols F         as well as Digital's Network Services Protocol (NSP).  The OSIH         Transport Protocol is used primarily for communications with OSI      .         systems, including DECnet/OSI systems.)                                         3  Phase V Product Support F DECnet/OSI Phase V supports a variety of current software and hardware	 products.  Networking Software L Current software products that can make the transition to DECnet/OSI Phase V include the following:      
 DECnet-VAX
 DECnet-ULTRIX  DECrouter family of products DECnet for personal computers ' VAX P.S.I. (Packetnet System Interface)  VAX P.S.I. Access 0 VAX FTAM (File Transfer, Access, and Management)" VAX OSAK (OSI Applications Kernel)& VAX MRX (Message Router X.400 Gateway)F DECnet/OSI Phase V continues to support connections to Systems Network  Architecture (SNA) environments.      )                                         4  Communications ControllersJ Digital recommends the following communications controllers for DECnet/OSI Phase V: Synchronous Controllers  DMF32 (UNIBUS)( DMR11 (UNIBUS for DECnet-ULTRIX systems)' DMV11 (Q-bus for DECnet-ULTRIX systems) 
 DSV11 (Q-bus) 
 DMB32 (VAXBI)  DST32 (for MicroVAX 2000) 1 DEC Multicontroller 581 (DSH32 for MicroVAX 2000) / DEC WANcontroller 220 (DSB32 for VAXBI systems)  Asynchronous Controllers DMF32 (UNIBUS)
 CXY08 (Q-bus) 
 DHQ11 (Q-bus) 
 DHV11 (Q-bus) 
 DHB32 (VAXBI) 
 DMB32 (VAXBI)  DHT32 (for MicroVAX 2000) 1 DEC Multicontroller 581 (DSH32 for MicroVAX 2000) )                                         5  802.3/Ethernet Controllers       DELUA (UNIBUS) DEUNA (UNIBUS)
 DELQA (Q-bus) 
 DESQA (Q-bus) 
 DEBNA (VAXBI) ? DESVA (for MicroVAX 2000, VAXstation 2000, and DECstation 3100)  Phase IV Products I The following products will not migrate to Phase V.  However, as Phase IV K systems, they continue full communications with all Phase V nodes that have  Phase IV-compatible addresses.       PDP-11 systems% DECsystem-10 and DECSYSTEM-20 systems / DMR11 and DMV11 hardware for DECnet-VAX systems  DECSA-based dedicated routers % DEQNA hardware for DECnet-VAX systems )                                         6        Phase V:  Elements of ChangeF DECnet/OSI Phase V introduces many new and powerful features, the mostM significant of which is the integration of OSI into the DECnet software.  The N transition of networks from DECnet Phase IV to DECnet/OSI Phase V can occur asN gradually or as rapidly as is necessary for each network.  From the start, twoN tools are essential to the Phase V network: the Distributed Name Service (DNS)' and the new Phase V network management. N Other features, such as new application programming interfaces and the Phase VG routing protocols, need not be adopted until their Phase V benefits are J desired.  Regardless of when these new features are utilized, full supportG exists for the Phase IV programming interfaces and the Phase IV routing 
 protocols.L For network management personnel, the effort required to make the transitionJ depends upon the size and complexity of the network.  However, all Phase VO network managers need to learn and use two new tools -- DNS and Phase V network N management.  Note that in this document, the sections on using DNS and Phase VL network management apply to all Phase V networks.  Discussions about routing. protocols apply only to networks with routers.       Distributed Name ServiceK The Distributed Name Service (DNS) offers consistent, networkwide naming of O network resources or objects, such as nodes, disks, queues, and mailboxes.  DNS E stores object names and attributes, for example, address and protocol N information.  DNS also provides networkwide mapping of names to attributes and" automatically distributes updates.N DNS names are stored in DNS directories.  These directories are organized into+ a networkwide hierarchy called a namespace. ) DNS provides these features and benefits: K o       Location-independent names -- The DNS name of a network resource is N         independent of the resource's physical location.  Location-independentM         naming makes it possible to relocate the resource in a manner that is =         transparent to end users and application programmers.       )                                         7 J o       Caching of frequently used information -- DNS software maintains aG         cache   of information obtained during previous requests to DNS N         servers.  Caching maximizes overall performance and reduces the number#         of requests to DNS servers. M o       Namespace scaling -- Very large namespaces can be partitioned so that L         no one DNS server must contain the entire directory structure.   TheO         namespace can also be replicated; that is, each directory can be stored O         on more than one server to ensure high availability.   Changes to names M         and attributes are automatically made available to the whole network.       I o       Unique networkwide names -- All DNS users and applications in the 7         network use a unique name to access a resource. L o       Simplified management of names -- The consistent, networkwide naming7         scheme simplifies management of resource names. L o       Security -- Access to DNS names can be assigned to individuals or to         groups. O o       Future growth -- DNS can support large or small DECnet/OSI Phase V LANs          or WANs.J o       Choice of management style -- DNS allows for either centralized orI         distributed management of the namespace and the DNS servers.  For K         example, many networks may have one administrator to coordinate the M         namespace, while other networks may distribute the coordination among &         several individuals or groups.      M DNS is based on a client-server model.  In this model, both client and server L work together to perform the naming function.  The client is any applicationM that makes requests of a DNS server.  One or more servers store the namespace M data and perform the name-to-attribute translation.  A clerk, running on each L DECnet/OSI Phase V node, is the interface between the client and the server.R                                         8                                        8 How DECnet/OSI Phase V Uses DNS J DECnet/OSI Phase V uses DNS for mapping DNS node names to attributes.  TwoK universal examples of attributes are node address and protocol information.       L DNS servers store node names and their attributes in a networkwide database.N Nodes use DNS to look up the attributes associated with node names and networkI applications.  For example, when making a connect request, a Phase V node L passes the remote node's name to DNS.  DNS returns the remote node's addressH and other attributes, such as available protocols to use when making theO connection.  The requesting node uses this information to connect to the remote 5 node, and then stores the information for future use. L In addition, Phase V nodes automatically register with DNS.  DNS then stores their name and attributes. Network Management5 Phase V network management offers three new features:  o       OSI-based protocols       / o       Modular and consistent management model + o       New, comprehensive command language 
 ISO Standards L Phase V network management is based on the ISO Common Management InformationL Protocol (CMIP) draft standard for network management operations.  CMIP is aI combination of two protocols: Management Information Control and Exchange O (MICE) protocol used for information exchange and Management Event Notification 7 (MEN) protocol used for event logging.  These protocols F supersede the Phase IV Network Information and Control Exchange (NICE)	 protocol. )                                         9        Management ModelH The design of Phase V network management uses a management model that is= modular and consistent.  This model has two major components: D o       Directors -- management software used by the network managerI o       Entities -- manageable components of the network, such as CSMA/CD 5         circuits, Session Control, and OSI transports E Phase V network management architecture is based on the entity model.  New Network Command Language      C The Network Command Language (NCL) software is a new, comprehensive L command interface.  NCL uses a syntax that reflects the structure of network management. O Network managers use NCL to manage all Phase V nodes.  To manage Phase IV nodes L from a Phase V node, network managers can invoke the Network Control ProgramM (NCP) from NCL.  As a result, Phase IV nodes can be managed from either Phase  IV or Phase V nodes. ApplicationsI DECnet/OSI Phase V allows continued use of existing Phase IV applications 9 without modifications.  DECnet/OSI Phase V also supports: " o       Use of DNS by applications8 o       Additional methods of connecting to applicationsA o       Continued use of Phase IV network management applications *                                         10 Programming InterfacesG Phase V provides continued support for Phase IV programming interfaces. O Applications modified for Phase V do not have to operate within the constraints N of Phase IV.  Thus, these applications can take advantage of Phase V features.N One impact of Phase V on existing applications is the increased length of nodeN names from a maximum of 6 characters to a maximum of 512 characters.  However,L Phase V does not require long node names.  The length of a Phase V node name      D depends on the directory structure that is defined in the namespace.I This change affects existing applications that assume a full node name isIO displayed in a 6-character field.  To handle this situation, Phase V provides a-N facility that allows system managers to define 6-character node names that mapN to their DNS node names, thereby allowing Phase IV applications to continue to4 work without modification.work without modification. DNS Support for ApplicationsG A network application can have its object name and an associated set ofcO attributes defined in the namespace.  If the attributes include the location ofhM this application, it becomes location independent. In this way, Phase V nodesdO can always connect to an application by its DNS object name even if the node onu& which the application resides changes.J If an application is modified to use a Phase V programming interface, thatL application can specify how Session Control uses DNS and how the application9 connects to an object over different transport protocols.  Phase V Application Connections   1   B Phase V allows three methods for applications to make connections.' Applications can provide the following:eL o       Node name and either the application or file name, as with Phase IV.M o       DNS object name.  Session Control then uses the DNS server to look up ,         the object's address and attributes.N o       All connection information to Session Control.  In this case, there is;         no need to look up the node name on the DNS server. *                                         11     2 Network Management ApplicationsoG Existing network management applications that use the NICE protocol can F continue to manage Phase IV nodes from a Phase V node.  However, theseM applications must be modified to use CMIP before they can be used to manage aS
 Phase V node.i
 AddressingI DECnet/OSI Phase V provides an advanced addressing scheme that offers the  following benefits:o= o       Increased addressing capabilities for larger networks.7 o       Backward compatibility with Phase IV addressinge> o       Conformance to the ISO standard for network addressing  p  S! Increased Addressing CapabilitiesvO Phase V's new addressing scheme eliminates the previous Phase IV limits of 1023 O nodes per area and 63 areas per network.  After the transition is complete, thepN size of a Phase V network is limited only by the memory capacity and processor capabilities of its routers.% Compatibility with Phase IV Addresses D Phase V routers can translate Phase IV and Phase V addresses in bothL directions.  To be Phase IV compatible, a Phase V address must have node andM area numbers that fall within the Phase IV limits (1023 nodes per area and 63eL areas per network).  Phase V routers can translate a Phase IV address into aI Phase V address and a compatible Phase V address into a Phase IV address.n$ Address Assignment During TransitionN A Phase V node must have a Phase IV-compatible address in order to communicateN with Phase IV nodes.  For this reason, it is best to use the existing Phase IVO node address during the transition of a node from Phase IV to Phase V software.C     d*                                         12J If new Phase V nodes are added to the network during transition, assigningL Phase IV-compatible node addresses helps to ensure communication between the* new nodes and the existing Phase IV nodes.L After the transition is complete, supplying an address is no longer requiredO for end nodes.  Address assignment for end nodes becomes automated because theyi! can generate their own addresses.a Conformance to OSI AddressingOM Phase V complies with the ISO 8348/AD2 addressing standard and fully supportseK ISO addressing.  To ease the transition, Phase V provides defaults for mostS  p  c! Phase V address field parameters.h Initial Domain PartuN The ISO 8348/AD2 addressing standard introduces a new address component calledN the Initial Domain Part (IDP).  Each Phase V address begins with an IDP field.L The IDP ensures unique network addresses throughout the world and identifies- each DECnet/OSI Phase V or other OSI network.eM A unique IDP allows the network to connect to any other DECnet/OSI Phase V oriN OSI network.  A small network may not need a unique IDP if that network has noO current or planned connections to other OSI networks.  Note that Phase IV nodescM can communicate only with nodes that have the same IDP as the Phase V routerst to which they are connected.H There are several ways to obtain an IDP.  To accommodate customer needs,J Digital will ship products with the same default IDP and will also provide6 customers with a procedure for obtaining a unique IDP.	 End Nodesa  e  tI End nodes, also called end systems in OSI terminology, can be upgraded totN Phase V software at any time.  Because DECnet/OSI Phase V software is backwardJ compatible, Phase IV and Phase V end nodes can coexist within the network." Phase V allows these combinations:D o       A mix of Phase IV and Phase V end nodes within a DECnet area; o       Connection of Phase V end nodes to Phase IV routers ; o       Connection of Phase IV end nodes to Phase V routers *                                         13L Phase V end nodes can reside within an area in which all the level 1 routers  a  VN are running the Phase IV routing protocols (a Phase IV area).  Likewise, PhaseK IV end nodes can reside within an area in which all the level 1 routers are N running the Phase V routing protocols (a Phase V area).  For a mix of Phase IVN and Phase V end nodes to coexist in either area, all node addresses within the! area must be Phase IV compatible.s Routersd; A DECnet/OSI Phase V network can have two types of routers: L o       Level 1 router -- routes data between nodes within its own area, andM         routes data toward a level 2 router when the destination system is ina         another area. N o       Level 2 router -- routes data between nodes within its own area and to#         other areas in the network.t  x  mC DECnet/OSI Phase V routers, also called intermediate systems in OSIRL terminology, use new routing protocols that provide flexibility, as follows:M o       Level 1 routers can run either Phase IV or Phase V routing protocols.(J o       Level 2 routers can run different routing protocols at level 1 and         level 2.K o       Each area in the network can use either Phase IV or Phase V routing O         protocols, regardless of the routing protocols other areas are running.a*                                         14I Phase V software can be installed onto a router at any time.  The routing.      N protocols (Phase IV or Phase V) currently in use within the area and the level0 2 network are specified during the installation. Routers in the Level 2 NetworkI All level 2 routers that connect areas in the network make up the level 2 M network.  With Phase V software, level 2 routers can run  different protocols O at each level.  For example, a level 2 router can run Phase V routing protocolsfL at level 1 and Phase IV routing protocols at level 2.  Level 2 networks needH not make the transition to Phase V at the same time as individual areas. Routers Within an AreaN All level 1 routers within an area must run the same set of routing protocols.I With Phase V software, a router can function as a Phase IV router and canTO coexist in an area with Phase IV routers during the transition.  The ability tosO run Phase IV routing protocols also permits Phase V routers to coexist in areasoJ that will continue to use Phase IV routing protocols for an extended time.L Once all the routers in an area have Phase V software installed, the networkL manager uses Phase V network management to begin the change from Phase IV to Phase V routing protocols.  1  U Phase IV RoutersK Some Phase IV routers, such as PDP-11 systems and DECSA routers, cannot run3F Phase V software.  DECnet/OSI Phase V allows these routers to continueH operating successfully in an area in which all other level 1 routers areL running Phase IV routing protocols.  If a Phase IV router that is not makingI the transition is a time-sharing system, then a viable solution may be tot< reconfigure the system as an end node within a Phase V area.M If desirable, selected routers can be maintained at Phase IV.  For example, aEK router may stay at Phase IV because an existing application running on thato? system depends on the Phase IV version of the operating system.t*                                         15  P  e VAXcluster(TM) SystemsN DECnet-VAX Phase V software will continue to support the cluster alias featureN of VAXcluster systems.  The nodes in the VAXcluster participating in the aliasO must be either all Phase IV nodes or all Phase V nodes.  Also, unlike Phase IV,eM Phase V does not require a routing node within the VAXcluster in order to use 	 an alias.  Node ConfigurationM The activities associated with node configuration are different for Phase IV,  the transition, and Phase V. Node AddressO During the transition, network managers should use the existing Phase IV methodoN to allocate network addresses.  Once the transition is complete, assigning and     eF manually entering network addresses for end nodes becomes unnecessary.C Phase V end nodes can automatically generate their addresses duringsM configuration.  Network managers must continue to allocate node addresses forn: routers in a Phase V network.routers in a Phase V network.	 Node NametK As with Phase IV networks, each node in a Phase V network requires a uniquerN name.  However, Phase V node names are DNS names.  Since DNS names reflect theM structure of the directory hierarchy of the namespace, the coordinator of theq: namespace and the system manager  determine the node name. DNS Server AddressH Phase V requires that each node know the DNS server address.  During theI transition, this address is automatically determined if the DNS server istI located on the same LAN as the node being configured.  If not, the system ( manager must manually enter the address.*                                         16       Adding Nodes to the NetworkhO The following two tables summarize the differences in information and tasks forrN system and network managers when adding nodes to the network.  The first tableO lists the information that the system manager supplies in configuring a node in  the network. System Manager Input7         Phase IV        During Transition       Phase Vp9         Node name       Node name               Node namee3         Node address    Node address            n/aa  d  nC         n/a             DNS server address*     DNS server address*iK         * Only if the node and a DNS server are not located on the same LANeO The following table summarizes the network configuration tasks that the networkm> manager must perform before, during, and after the transition. Network Manager Taskse?         Phase IV                During Transition       Phase V ;         Allocate end node       Allocate end node       n/ai)         addresses               addresses G         Allocate router         Allocate router         Allocate router A         addresses               addresses               addresses ;         Define names/addresses  Define names/addresses  n/ac0         in node database        in node database;         Distribute name/        Distribute names        n/ar5         address translations    addresses to Phase IVo%                                 nodes <         n/a                     Enter Phase IV names/    n/a8                                 addresses into namespaceH         n/a                     Manage namespace        Manage namespaceL         n/a                     Determine node names    Determine node namesL When the transition is complete, the configuration requirements for both theM system manager and the network manager lessen, and node configuration becomese6 significantly easier than in the Phase IV environment.*                                         17       Phase V:  Making the TransitiontL Making the transition to Phase V requires planning.  Consider these factors:K the size of the network, the requirements of the network, preparing for the / transition, and planning the Phase V namespace.n Preparing for the TransitionL The amount of planning and preparation depends on the size and complexity ofJ network.  For many networks, the transition will be similar in scope to anK operating system upgrade and can be planned and executed easily by a singleeN person.  Much of the information in the rest of this document does not pertainL to such networks.  However, the sections that follow contain guidelines that  e   > generally are useful in preparing networks for the transition.M Digital plans to provide training and support services to assist customers ind* the transition of large, complex networks.O For networks of any size, use the following list as a starting point to prepare  for the transition to Phase V:8 o       Identify personnel to coordinate the transition.6 o       Consider the applicable transition guidelines.B o       Gather information about end nodes, routers, and circuits.H o       If the network has dedicated routers, select a node to start the$         transition of these routers.*                                         18  c  o2 Identifying Personnel to Coordinate the TransitionH Each network needs a focal point for gathering and disseminating Phase VM transition information.  This focal point can be either one person or a team. H The current network manager may provide this coordination.  A transitionK coordinator is the first individual to become familiar with and use Phase Vn( features and Phase V network management.< Transition coordinators have the following responsibilities:: o       Gather and maintain information about the network.% o       Ensure that DNS is available.c@ o       Help to design the namespace and the naming conventions.     eM o       Allocate node names and addresses that ensure Phase IV compatibility.iF o       Become knowledgeable about DNS and Phase V network management.N o       Identify Phase IV network management applications that use the NetworkL         Information and Control Exchange (NICE) protocol;  ensure that these*         applications are upgraded to CMIP.M o       Determine whether to use the IDP that comes with the Phase V software I         or whether a different IDP is needed.  Digital plans to provide a %         procedure for obtaining IDPs. N o       Plan the introduction of Phase V into the network, including down-time         schedules., o       Implement the transition to Phase V.*                                         19  m   , Considering Applicable Transition GuidelinesN Consider the following simple guidelines when planning the transition process.K Note that many of the guidelines apply only to large networks with multipleeI areas and routers.  The guidelines apply to these aspects of the network: J o       DNS servers -- During the transition, ensure that the addresses ofH         Phase V DNS servers follow Phase IV addressing conventions. ThisN         addressing allows interoperability in a network that has both Phase IV         and Phase V nodes.H o       Addressing scheme -- Until all nodes can run the Phase V routingK         protocols, continue to use node addresses that adhere to the DECnethO         Phase IV addressing scheme.  Assign a valid Phase IV address to any newhH         nodes that are added to the network during the transition.  This;         ensures continued interoperability among all nodes.l  t  sJ o       End nodes -- DECnet/OSI networks can contain a mix of Phase IV andL         Phase V end nodes in the same area.  Install the Phase V software onM         end nodes, regardless of whether the routers in that area are runningf6         the Phase IV or the Phase V routing protocols.P o       Routing protocol -- Install the Phase V software on routers at any time.I         The software can be set to run either Phase IV or Phase V routingo         protocols.M         After the Phase V software has been installed, a network can continuetM         to use the Phase IV routing protocols indefinitely.  The requirementseJ         of the network, such as the need to support multivendor OSI nodes,D         determine when to begin using the Phase V routing protocols.O o       Areas and level 1 routers -- Before starting the transition of an area,,N         ensure that all routers in that area can run Phase V routing software.M         Change routers that cannot run Phase V routing software to end nodes,aN         or move them to an area that will remain at Phase IV.  Level 1 routersI         can be changed to run the Phase V routing protocols regardless ofd9         whether the end nodes are at Phase IV or Phase V..  f  eO o       Level 2 routers -- Before starting the transition of a level 2 network,eI         ensure that all level 2 routers can run Phase V routing software. K         Change the ones that cannot to end nodes, or change them to level 1e8         routers in an area that will remain at Phase IV.*                                         20< Gathering Information About End Nodes, Routers, and CircuitsN Compile information about the nodes in the network to help locate systems that need particular attention.M Regardless of the network's size, compile a list of node names and addresses.eK This information may be derived from the node name database.  DNS uses thisa5 data to populate the namespace during the transition.t     nO For networks with routers, gather the following information about these routers M and the circuit connections between them.  This information helps to identify % routers that will remain at Phase IV.o- o       DECnet node address (area and number) $ o       Operating system and version( o       DECnet software name and version4 o       Router type (level 1 router, level 2 router) o       VAXcluster information o       Circuit configurationt5 Selecting a Node to Start Dedicated Router Transitiont      L Ensure that DNS exists in the network.  To start the transition of dedicatedO routers, select a Phase V node.  The Phase V software on this node provides ther  required new network management.*                                         21# Planning and Creating the Namespace F Three activities are required for creating the namespace: planning the? namespace, selecting DNS servers, and populating the namespace.m Planning the NamespaceN To help achieve a smooth, successful transition from Phase IV to Phase V, plan  n   J a design for the namespace.  Consider the future growth of the network.  AM well-designed namespace efficiently accommodates changes in an organization'sd$ structure and network configuration.H Use the following guidelines to help meet specific network requirements:L o       Define administrative tasks and responsibilities.  Specify the tasksK         needed for administering the namespace.  Tasks include creating andrL         replicating DNS directories, assigning access rights, and monitoringM         the naming policy.  Also, the duties of a Phase IV node registrar arei;         required as long as the network has Phase IV nodes. H o       Develop naming conventions for network resources.  Choose short,J         meaningful names, such as names of departments, and use consistentK         names for network resources.  For directories immediately under the C         root directory, choose names that are not likely to change.oI o       Design the node name hierarchy.  One approach is to start with aniB         organizational structure and to update the design when theK         organization and the network change.  Designing the namespace is an          ongoing process.  r  dL o       Plan the layout of the namespace.  Determine how the DNS directoriesM         will be arranged within the namespace.  Then decide how the namespace          will be partitioned.*                                         22G The following examples illustrate two ways of placing node names in thes
 namespace. Nonhierarchical Node NamesH In a nonhierarchical namespace, all DNS names may be located in the rootL directory.  This type of namespace is similar to the Phase IV node database.  n  eL Nonhierarchical namespaces are appropriate for networks of approximately 100K nodes or fewer that have minimal projected growth.  Simplicity is the majort' benefit of a nonhierarchical namespace.e Hierarchical Node NamesaM A hierarchical namespace consists of several DNS directories organized into atO hierarchical tree under the root directory.  Creating a DNS directory under the . root directory sets up this type of namespace.n A hierarchical namespace offers the following benefits:A hierarchical namespace offers the following benefits:K o       Allows replication based on frequent access and availability -- The E         hierarchical namespace allows replication of directories withoI         frequently used information on several DNS servers.  This ensures ,         maximum availability of information.M o       Allows flexibility in placement of directories  -- A directory can beiE         located near clerks that use the directory's information mosti  f  aF         frequently.  For example, a directory with scientific researchP         information is located near the systems running scientific applications.L o       Allows future growth -- The hierarchical namespace can store a large         number of DNS names.*                                         23 Selecting DNS ServersrM After planning the namespace, choose the nodes that will be DNS servers.  TheiJ location of DNS servers depends on several factors, including the size andK topology of the network.  DNS is currently implemented on the VMS operating ; system and will be offered on additional operating systems.a  s  eL Considerations for selecting a node that makes a good DNS server include theJ node's availability, reliability, and system performance.  Designating twoG servers with identical contents ensures continuous DNS availability anddF provides a backup of the contents.  DNS performance can be improved byM increasing the capacity of the servers as well as by increasing the number ofn servers in the network.E% Creating and Populating the NamespacenK With the namespace design complete and servers selected, begin creating thedL namespace on the first server.  With Phase IV, installation of the first DNSM server created the namespace and the root directory.  With Phase V, first use J NCL to start the DNS software on servers and then to create the namespace.J Once the namespace exists, begin populating it.  First, set up a shell, orN skeleton, namespace.  This shell is based on the namespace design and consistsH of the root directory and directories that branch from it.   Later theseO directories can be populated with entries, such as Phase V node names.  Add new @ directories at any time to any level of the namespace hierarchy.- Phase IV Node Name Database During Transitione     tH Create a Phase V DNS name for each Phase IV node to allow interoperationM between Phase IV and Phase V nodes.  During transition each Phase IV node has.M two names: a Phase IV name and a Phase V name.  Other Phase IV nodes continueaM to access a node by its Phase IV name, for example, NODE3.  At the same time,t@ Phase V nodes access this node by its Phase V name, for example, .ENG.DEV.NODE3. *                                         24M Phase V nodes can also use the Phase IV name through the node alias database.nF However, the node alias database is primarily a transition tool to aid applications that assume 6-character node names.  It is not a substitute for aapplications that assume 6-character node names.  It is not a substitute for a hierarchical namespace.   e  d Use one of these procedures:L o       Place the entire Phase IV node database in the root directory of theI         Phase V namespace.  With this method, a node's Phase IV name, fortO         example, NODE3, and its Phase V name, for example, .NODE3, are similar.nN         This kind of transfer is appropriate for networks of approximately 1006          nodes or fewer that are not planning to grow.L o       Create the hierarchy of directories.  Then create Phase V node namesE         for Phase IV nodes and place these names in their appropriategJ         directory.  With this method, a node's Phase IV name, for example,L         NODE3, and Phase V name, for example, .ENG.DEV.NODE3, are different.G         Although this method may initially seem time consuming, DigitaliN         recommends it because it is ultimately the most efficient for networks-         with approximately 100 nodes or more. *                                         25  s  E" Transition of LANs Without RoutersO Local area networks and extended LANs without routers are the simplest networkseL to make the transition to Phase V.  Since Phase IV and Phase V end nodes canM coexist in a LAN without the need for a router, the transition of an end nodenI can occur any time the software is available for that node.  Follow these  steps:* o       Create and populate the namespace.? o       Continue to use Phase IV-compatible addresses to ensuredI         interoperability while there are still Phase IV nodes in the LAN. @ o       Install the Phase V software onto end nodes at any time.  m  tO This process does not disrupt communication among other nodes on the LAN duringe the transition to Phase V." Transition of Single-Area NetworksM Many small and medium-sized networks have a single area, such as an area thateN exists entirely within a LAN.  These networks can be converted to Phase V withL a method that requires changing the network routing nodes to run the Phase V routing protocols.I For DECnet-VAX routers, change the routing protocols by shutting down thetO network software that is set to the Phase IV protocols and bring up the networkeK software set to the Phase V protocols.  To change the routing protocols forhO dedicated routers, use the node that was selected to start the transition.  UsenK this node to reboot the router with the network software set to the Phase Vt
 protocols.*                                         26  e   O During the transition of routing protocols from Phase IV to Phase V, there will I be a time during which both protocols exist in the network.  As a result,eJ connectivity through adjacent routers running dissimilar routing protocolsO cannot be maintained.  For this reason, it is important to ensure that once theeJ transition of routing protocols begins, all routers are changed to run theL Phase V protocols.  When the transition is complete, connectivity throughout# the area is automatically restored. M The amount of time required for the total transition depends on the number of F routers in the area and the method used to convert them to run Phase VK protocols.  This process takes only minutes if there are few routers in theo area. O To minimize the impact of the loss of connectivity within an area, consider thep following guidelines:a  a  rM o       Perform the transition at a time that has the least impact on networkg         users.I o       Select a method that balances the resources and time available to           complete the transition.N To help complete the transition, Digital supports two methods of Routing layer transition:rN o       Locally through a coordinated effort with all routers changing at onceO o       Remotely through network management with routers changing one at a timea*                                         27  e  mI Use either method or a combination of the two to meet specific networking  needs.) To use these methods, follow these steps: * o       Create and populate the namespace.1 o       Convert end nodes to Phase V at any time.mI o       Verify that all routing nodes can run Phase V software.  Move thesN         routers that cannot run Phase V software into areas that will continueJ         to use Phase IV routing protocols, or convert these routers to end         nodes. o       Install the Phase V routing software, which continues to use Phase IVo       Install the Phase V routing software, which continues to use Phase IV      H         routing protocols, and change the routers to run Phase V routing         protocols.I         Depending on the needs of the network, select either the local orf         remote method:L         --      With the local method, install the Phase V software onto allI                 routers.  Then set the routers to run the Phase V routingc+                 protocols at the same time.eI         --      If the local method is not appropriate, use the followingnJ                 procedure to change routers remotely.  Install the Phase VM                 software, which is set to run the Phase IV routing protocols,hN                 onto the routers as the software becomes available.  (There isI                 no need to install the software onto all routers at once,nJ                 since this operation does not disrupt communications amongM                 other nodes.)  After installing the Phase V software onto alltL                 routers, use remote network management to change the routers?                 one at a time to run Phase V routing protocols.i  g  eO The network is now running the Phase V routing protocols and supports Phase IV, ' Phase V, and multivendor OSI end nodes.e*                                         28  Transition of Multiarea NetworksO One possible transition method for networks with multiple areas is similar to an< series of small network conversions.   Follow this sequence:* o       Create and populate the namespace.1 o       Convert end nodes to Phase V at any time.m      G o       Convert a few areas using the methods described for single-arearN         networks.  Convert areas independently of each other.  Become familiarO         with DECnet/OSI, DNS, and the Phase V network management tools in theses         areas.L o       Convert the level 2 network.  The process for converting the level 2M         network is similar to the process for converting an area.  Use one ofnM         the methods described for single-area networks to convert the level 2c         network.K         During the transition to Phase V, there will be a time during which K         both protocols exist in the level 2 network.  Although connectivity M         through adjacent level 2 routers running dissimilar routing protocols N         cannot be maintained, routing within areas (level 1 routing) continues         unaffected.eO o       Convert the other areas that are moving to Phase V.  Areas can continuevO         to use the Phase IV routing protocols, as required by some applicationsP         and products.,  c  iK Digital plans to provide facilities to assist customers in converting large. networks to Phase V.*                                         29	 Key TermsT Common ManagementsM         Network management protocol based on ISO standards.   Encompasses the.G         Information Protocol (CMIP)     Phase V MICE and MEN protocols.i$ DECnet/OSI Phase VDECnet/OSI Phase VI         Fifth version of Digital Network Architecture (DNA).  Conforms toh  r  iH         standards set by the International Standards Organization (ISO). Distributed Name Service (DNS)N         Networkwide, distributed system software used for storing object namesN         (such as nodes, applications, files, disks, queues, and mailboxes) andM         attributes (such as address and protocol information).  Also providestD         networkwide mapping of names to attributes and automatically         distributes updates.
 DNS serverA         Node with DNS software that maps object names to a set of j         attributes (including their network address).        attributes (including their network address). Initial Domain Part (IDP)sM         The first part of the Phase V address.  Uniquely identifies a networkw0         among other DECnet/OSI and OSI networks. level 2 networkt8         Level 2 routers that connect areas in a network., Management Event Notification (MEN) ProtocolM         Protocol used by DECnet/OSI Phase V that exchanges event information.b  e  o; Management Information Control and Exchange (MICE) Protocol E         Protocol used by DECnet/OSI Phase V that exchanges managementn         information.	 namespaceIB         Hierarchical tree of DNS directories that store DNS object         names. Network Control Language (NCL)L         Phase V network management language.  Provides the command interface-         for full network and node management.r*                                         30     u
 Phase IV areatC         Area that has Phase IV routing protocols running on all itsu         level 1 routers. Phase V areaB         Area that has Phase V routing protocols running on all its         level 1 routers. Phase V routerF         Router that has Phase V software installed.  A Phase V level 1N         router can run either Phase V or Phase IV routing protocols.   A PhaseK         V level 2 router can run different routing protocols at each level.u Routing domainG         Collection of routers that use the same routing protocols, plush6         the end nodes that use their routing services. Session Control C         Digital Network Architecture (DNA) module that provides the          functions for name-to-address mapping, protocol selection, and        functions for name-to-address mapping, protocol selection, and;         system-dependent, process-to-process communication.r     e*                                         31O For additional information on DECnet /OSI Phase V, refer to the DIGITAL Network C Architecture (Phase V) General Description (Order No. EK-DNAPV-GD).eJ Digital believes the information in this publication is accurate as of itsO publication date; such information is subject to change without notice. Digitalo. is not responsible for any inadvertent errors.O The following are trademarks of Digital Equipment Corporation: CompacTape, DEC, I DECsystem-10, DECSYSTEM-20, DECUS, DECmate, DECnet, DECwriter, DIBOL, thev  2  uK Digital logo, MASSBUS, PDP, P/OS, Professional, Rainbow, RSTS, RSX, UNIBUS,n: VAX, VAXcluster, VMS, and VT.VAX, VAXcluster, VMS, and VT.