[Digital logo]
[HR]

DECnet-Plus for OpenVMS
Network Management


Previous | Contents

Figure 8-18 Entity Relationships for Outgoing Connections



Incoming Connections

Figure 8-19 shows the entity relationships for incoming connections.

Figure 8-19 Entity Relationships for Incoming Connections



The following initialization actions take place before incoming connections can be accepted.

  1. OSAK opens a port to OSI transport for every TSAP required by OSAK applications.
  2. OSI transport activates any x25 access filter entities specified in the osi transport cons filters attribute.
  3. X.25 and X.25 Access software open a channel to each LAPB link during initialization, and in turn, each LAPB link opens channels to their associated modem connect line entity.

The following occurs upon receipt of an incoming call on an X.25 DTE:

  1. X.25 and X.25 Access software use the protocol dte inbound dte class attribute to determine which X25 access DTE class applies to the call.
  2. X.25 and X.25 Access software extract the NSAP address from the address extension facilities, if they exist. If the facilities do not exist, X.25 and X.25 Access software convert the X.25 network addresses to NSAP addresses using the x25 access dte class attributes.
  3. X.25 and X.25 Access software search the X.25 access filters for a match with the attributes of the incoming call. If a match exists, X.25 and X.25 Access software pass the message up to the application that activated the filter.
  4. OSI transport searches for an osi transport template entity with inbound characteristic= true, network service=cons, and cons template having the name of the X25 access filter. If found, OSI transport accepts the X.25 call with the X25 access template specified in the cons template attribute. With this procedure, the x25 access filter and x25 access template entities must use the same entity name.
  5. OSI transport passes the message up to OSAK if the transport connect request PDU's called TSAP ID field matches the TSEL specified by OSAK during initialization step 2.
  6. OSAK passes the message up to the OSI application if the SSEL and PSEL match those defined during initialization step 1. OSAK ignores the AP-Title and AE-Qualifiers.

    8.8.2.3 Configuring OSI Transport Over X.25 CONS

    The DECnet-Plus configuration procedure always configures the CLNS stack. You cannot use this procedure to configure the CONS stack alone.

    By default, the DECnet-Plus for OpenVMS configuration procedure configures HDLC on WAN devices. This blocks X.25 access to the same devices. Use the advanced configuration procedure to override this default.

    Manually add specific NCL commands to the configuration procedures to complete the configuration, as shown in the following examples.

    All DECnet-Plus end system products support manual x25 access reachable addresses entities, allowing mapping of NSAPs to any X.25 network address. Set the default configuration to perform X.121 mapping without address extension facilities, as shown in this document. Use manual X.25 access reachable addresses only for destinations with non-X.121-based NSAPs.

    X.25 and X.25 Access software provide controls to screen incoming calls with the x25 access filter and x25 access security filter entities. These mechanisms allow you to define access to the system based on call data such as source and destination addresses. The examples below do not use them. See X.25 documentation for more information.

    The following subsections show examples from procedures used to configure OpenVMS Alpha and VAX systems. The procedures were performed on pristine systems that include only the base operating system and the minimum appropriate licenses. The system parameters are set as defined in the DECnet-Plus and X.25 documentation.


    Note

    The addresses shown in these examples differ from the ones listed in Table 8-18. DECnet-Plus for OpenVMS requires an extra octet containing the NSAP length in digits to precede the actual NSAP value.

    OpenVMS Alpha Configuration of OSI Transport Over X.25 CONS

    Take the following steps to configure FTAM (and other OSI applications) with OSI Transport over X.25 CONS on an OpenVMS Alpha system. For more information on FTAM configuration, see the DECnet-Plus for OpenVMS FTAM and Virtual Terminal Use and Management guide.

    1. Install the DECnet-Plus base kit, as follows:
      $ PRODUCT INSTALL DECNET_OSI  
      
    2. Configure DECnet-Plus with WAN drivers and an additional OSI template for the CONS protocol stack. Do not configure WAN devices for routing.
      $ @NET$CONFIGURE ADVANCED      
      

      Respond to the prompts as shown:
      • Do you want to configure Wide Area Devices? Y
      • Configure WANDD? Y
      • Configure built in serial port as synchronous? Y
      • Data Link protocol for ZRA0 (SSCC)? NONE
      • Do you want to create additional OSI templates? Y
      • Type of network service (CLNS/CONS/RFC1006)? CONS
      • Name of the OSI template? CONS
      • Transport classes to support? 0,2
      • Do you want to create additional OSI templates? N
    3. Install X.25 for OpenVMS Alpha, as follows:
      $ PRODUCT INSTALL X.25      
      
    4. Configure and start X.25, as follows:
      $ @X25$CONFIGURE ADVANCED      
      

      Respond to the prompts as shown:
      • Configuring WANDD...
      • Change your current configuration: N
      • Create a new configuration script (from menu)
      • Do you want to configure any Remote DTE Classes? N
      • Do you want to configure any synchronous lines? Y
      • X.25 Address: 61712345
      • Profile Name: ACCUNET
      • Outgoing Logical Channel Range:{[1..127]}
      • Do you want to use LLC2 communications? N
      • Do you want to create any applications? N
      • Do you want to set up additional filters? N
      • Do you want to set up additional templates? N
      • Do you want to specify reachable addresses? N
      • Allow all X.25 calls (from menu)
    5. The configuration procedures in steps 2 and 4 do not account for local X.25 address formats. Modify the configuration by adding the following NCL commands to SYS$STARTUP:X25$EXTRA_SET.NCL:
      set  lapb link link-0 sequence modulus 8      
      set x25 access dte class accunet internationalprefix 0      
      set x25 access dte class accunet dnic 3134      
      set x25 access dte class accunet strip dnic true      
      set x25 access reachable address x121d dte class accunet      
      set x25 access template "osi transport" local subadd 6171234540      
      
    6. Install FTAM and the other OSI applications so that you can actually use OSI transport over CONS, as follows:
      $ PRODUCT INSTALL OSAK, FTAM, VT  
      
    7. Configure FTAM, as follows:
      $ @OSIF$CONFIGURE      
      
    8. Add FTAM service aliases to the OSI applications database, as follows:
      $ EDIT/EDT SYS$SYSTEM:ISOAPPLICATIONS.DAT     
      
    9. Start OSAK and FTAM, as follows:
      $ @SYS$STARTUP:OSAK$START      
      $ @SYS$STARTUP:OSIF$STARTUP      
      
    10. Manually enter the following NCL commands:
      NCL> ADD OSI Transport CONS NSAP Addresses {/103631346171234540 }      
      NCL> SET OSI Transport Template CONS Loc NSAP/103631346171234540      
      NCL> SET OSI Transport Template CONS Classes {0, 2 }      
      

      OpenVMS VAX Configuration of OSI Transport Over X.25 CONS

      Take the following steps to configure FTAM (and other OSI applications) with OSI Transport over X.25 CONS on OpenVMS VAX systems. For more information on FTAM configuration, see the DECnet-Plus for OpenVMS FTAM and Virtual Terminal Use and Management guide.

      1. Register the OpenVMS operating system in POLYCENTER. Specify your actual OpenVMS operating system version in the /VER= switch, as follows:
        $ PRODUCT REG PROD VMS /VER=V7.0 /SOURCE=SYS$UPDATE:     
        
      2. Install DECnet-Plus base kit with the X.25 Access software, as follows:
        $ PRODUCT INSTALL DECNET_OSI     
        
      3. Configure DECnet-Plus with WAN drivers and an additional OSI template for the CONS stack. Do not configure WAN devices for routing.
        $ @NET$CONFIGURE ADVANCED     
        

        Respond to the prompts as shown:
        Do you want to configure Wide Area Devices? Y     
        Do you wish to use WANDRIVER? Y     
        Will you use DEC HDLC? N     
        Will you use LAPB/E? Y     
        Do you have any soft-loadable microcode devices on this system? Y     
        Do you want asynchronous datalink support? N     
        Data Link protocol for DSV-0-0 (DSV-11)? NONE     
        Data Link protocol for DSV-0-1 (DSV-11)? NONE     
        Do you want to create additional OSI templates? Y     
        Type of network service (CLNS/CONS/RFC1006)? CONS     
        Name of the OSI template? CONS     
        Transport classes to support? 0,2     
        Do you want to create addional OSI templates? N     
        
      4. Configure and start X.25 Access software, as follows:
        $ @PSI$CONFIGURE ADVANCED     
        

        Respond to the prompts as shown:
        Type of VAX P.S.I. configuration? Native     
        Do you want to configure any synchronous lines? Y     
        Select a line speed for your DTE: 9.6     
        X.25 DTE Address: 61712345     
        Logical Channel Ranges: [[1..127]]     
        Profile Name: ACCUNET     
        Do you wish to set up any PVCs? N     
        Do you wish to create any Closed User Groups? N     
        Do you wish to use LLC2 communications? N     
        Do you wish to set up any applications? N     
        Do you wish to set up additional templates? Y     
        Template Name: "OSI Transport"     
        DTE Class: ACCUNET     
        Call Data: %x03010100     
        Charging Information: NO     
        Local Subaddress: 40     
        NSAP Mapping: YES     
        Do you want X.25 or X.29 programs to specify filter names in $QIO calls? YES     
        Do you want IO$_ACPCONTROL calls issued by your programs to name any     
        static filters? YES     
        Filter Name: "OSI Transport"     
        Call Data Value: %x03010100     
        Call Data Mask: %xFFFFFFFF     
        Do you want to set up X.25 Security? NO     
        Do you wish to create an NCL script now? Yes     
        
      5. The configuration procedures in steps 3 and 4 do not account for local X.25 address formats. Modify the configuration by adding the following NCL commands to the SYS$STARTUP:PSI$ENABLE_DECNET_CLIENTS.NCL file:
        create x25 access reachable address x121d address prefix /36     
        set x25 access reachable address x121d mapping x.121     
        set x25 access reachable address x121d dte class accunet     
        set x25 access reachable address x121d address extensions true     
        add osi transport cons nsap addresses {/103631346171234540 }     
        
      6. Install FTAM and the other OSI applications, as follows:
        $ PRODUCT INSTALL OSAK, FTAM, VT  
        
      7. Configure FTAM, as follows:
        $ @OSIF$CONFIGURE     
        
      8. Add FTAM service aliases to the OSI applications database, as follows:
        $ EDIT/EDT SYS$SYSTEM:ISOAPPLICATIONS.DAT     
        
      9. Start OSAK and FTAM, as follows:
        $ @SYS$STARTUP:OSAK$START     
        $ @SYS$STARTUP:OSIF$STARTUP     
        

      8.8.3 Configuring Routing Over X.25 Dynamically-Assigned Circuits

      Dynamically-assigned circuits are used for making infrequent connections to destinations outside the routing domain of your DECnet-Plus system. (A routing domain is a collection of systems that automatically configure to each other and exchange network topology information using consistent Network layer protocols.) Dynamically-assigned circuits are established upon arrival of data and are cleared when no more data is transmitted or received during a specified time (idle time).

      8.8.3.1 Addressing Issues for Dynamically Assigned Circuits

      When using dynamically-assigned X.25 routing circuits, the sending and receiving nodes must be in separate routing domains. The routing domain is defined with a unique AFI, IDI, and PreDSP combination in the NSAP address (see Figure 8-16). The format of the CLNS address must conform to that described in the DECnet-Plus Planning Guide.

      The requirement for separate routing domains places two restrictions on addressing:

      • The NSAP address used at the Routing layer for the source and destination can be any CLNS address except ones beginning with AFI 49.
      • DECnet Phase IV network traffic cannot span dynamically-assigned X.25 routing circuits. Phase IV address translations apply only within a single routing domain.

      If your DECnet-Plus system is isolated from the network and uses the dynamically-assigned X.25 routing circuit for communication, you may find it convenient to assign an NSAP address to your system that is based on your X.25 network address. If you do this, you must use the binary format of an X.121 address (AFI 37 or 53), as opposed to the decimal format described in Section 8.8.2.1 for X.25 CONS configurations. Section 8.4.1.6 explains how to use manual network entity titles to define the NSAP address for your system.

      For each dynamically-assigned X.25 routing circuit, you must configure one or more reachable addresses. A reachable address defines a mapping between network service access points (NSAPs) and data terminal equipment (DTE) addresses used in X.25. An NSAP identifies a system in the network and is used by both the Network and Transport layers of DECnet-Plus. X.25 uses a DTE address to identify the end point of an SVC. Reachable addresses identify which NSAP or group of NSAPs should be sent over a particular X.25 circuit.


      Note

      Use the routing circuit reachable address entity when configuring routing over X.25 dynamically-assigned circuits. Do not use the x25 access reachable address entity. The x25 access reachable address entity applies only to OSI transport over X.25 CONS configurations, as described in Section 8.8.2.

      Consider the following example of two systems connected by an X.25 network:
      System A System B
      NSAP 48::00-5F:08-00-2B-16-A8-72:21 43:15082267643:0045:08002B16DE4F:21
      DTE 075527537 18628935742674

      The reachable address on System A specifies that if the destination NSAP matches the value 43:15082267643:0045:08002B16DE4F:21, then an X.25 circuit should be created by connecting to the DTE address 18628935742674. This example is a case of one-to-one NSAP-to-DTE mapping. The reachable address could also be set up such that any NSAP with the initial digits 43:15082267643 should be sent over that X.25 circuit, which would potentially cause many different NSAPs to be mapped to that particular X.25 circuit.

      The NCL commands to create and initialize reachable addresses are created in the SYS$STARTUP:NET$OSI_TRANSPORT_STARTUP.NCL script (for OSI transport using CONS) and the SYS$STARTUP:NET$ROUTING_STARTUP.NCL script (for Routing using X.25).

      The following example shows how to manually create a reachable address for routing using NCL. For more information on configuring routing, see Section 8.4.

      ncl> create routing circuit x25_circuit-1 reachable address ughh_v -      
      _ncl> address prefix /4145418715004108002b0ed41e      
            
      ncl> set routing circuit x25_circuit-1 reachable address ughh_v -      
      _ncl> dte address { 2267643 }      
            
      ncl> set routing circuit x25_circuit-1 reachable address ughh_v -      
      _ncl> mapping manual      
            
      ncl> enable routing circuit x25_circuit-1 reachable address ughh_v      
      

      Specify the address prefix when you create the routing circuit entity. You cannot modify this attribute with the setcommand.

      The X.25 configuration procedure automatically creates the following two X25 Access reachable addresses:

      • X121 with address prefix 37:
      • X121D with address prefix 36:

      8.8.3.2 Configuring Routing to Use a Dynamically-Assigned X.25 Circuit

      The following subsections explain how to configure routing to use X.25 circuits on OpenVMS Alpha and VAX systems. On either system, you can use the advanced configuration procedure (invoking NET$CONFIGURE ADVANCED) to configure routing to use an X.25 data link. The procedure checks for network devices on the system that are supported by NET$CONFIGURE and then configures them. If the procedure finds that your system has WANDD or X.25 installed but not configured, you will see the following information:

      You have installed wide area device support, but it has not been      
      configured.  You may configure it now if you want.      
            
      * Do you want to configure Wide Area devices?          [YES] :       
      

      Answer yes.

      OpenVMS Alpha Systems

      For an Alpha system, the procedure displays the following information:

      DEC X.25 software has been installed on this system.  You have      
      the option of configuring DECnet to run over X.25.      
            
      * Do you want to configure DECnet over X.25?            [NO] :      
      

      Answer yes.

      You will see a list of choices for the type of X.25 circuit to use:

           Types of X.25 circuits:      
            
           [1] - X.25 Dynamic Assigned (DA)      
           [2] - X.25 Static Incoming (IN)      
           [3] - X.25 Static Outgoing (OUT)      
           [4] - X.25 Permanent (PVC)      
            
      * Which type of X.25 circuit do you want to use?             :      
      

      Select the X.25 dynamically-assigned circuit (Menu Option 1). The procedure then asks information about the circuit, including:

      • Routing circuit name to use.
      • Template name for the X25 Access template, which X.25 routing circuits use to make or accept network connections. For dynamically-assigned circuits, the X25 Access template is needed for specifying data terminal equipment (DTE) class and call data.
      • Filter name for the X25 access filter. For dynamically-assigned circuits, the x25 access filteris needed for specifying inbound DTE class, call data value, and call data mask.
      • Whether you want to configure reachable addresses, and if yes, information about reachable addresses. If you configure a dynamically-assigned X.25 routing circuit, you must configure one or more reachable addresses used for managing the circuit. Each reachable address specifies a mapping of an NSAP address to a DTE address.

      When you have entered the circuit, template, filter, and reachable address information, the procedure asks if you want to configure any other circuits. If you do not want to configure any other routing circuits, press the Return key for the default ([NO]). The configuration procedure continues with the next series of questions.

      OpenVMS VAX Systems

      If you answer yesto the question, "Do you want to configure wide area devices?" and you are using a VAX system, the procedure displays the following information:

      The VAX P.S.I. software has been installed on this system.  You have      
      the option of configuring DECnet over P.S.I. (i.e., configuring      
      DECnet over X.25 datalink mapping).      
            
      * Do you want to configure DECnet over P.S.I.?          [NO] :      
      

      Answer yes to configure DECnet over X.25 Access (P.S.I.). The procedure displays the following list of choices:

           Types of X.25 circuits:      
            
           [1] - X.25 Dynamic Assigned (DA)      
           [2] - X.25 Static Incoming (IN)      
           [3] - X.25 Static Outgoing (OUT)      
           [4] - X.25 Permanent (PVC)      
            
      * Which type of X.25 circuit do you want to use?             :      
      

      Select the X.25 dynamically assigned circuit (Menu Option 1). The procedure continues to ask for information, as described in Section 8.8.3.2.

      8.8.3.3 NCL Commands for Configuring X.25 Routing Circuits

      To use NCL to manually configure X.25 routing circuits, following these steps:

      1. Set up and enable routing.
        ncl> create routing type endnode      
              
        ncl> set routing dna address format true, lifetime 63, -       
        _ncl> manual network entity titles {}, probe rate 20      
              
        ncl> enable routing      
        
      2. Create and set up the routing circuit with the appropriate values for its attributes, including the circuit name, type, data link, X.25 filter, and the reachable address. (You must configure a reachable address if you have configured one or more dynamically-assigned routing circuits.)
        ncl> create routing circuit x25_circuit-1 type x25 da      
        ncl> set routing circuit x25_circuit-1 data link entity x25 access      
        ncl> set routing circuit x25_circuit-1 template template-name      
        ncl> set routing circuit x25_circuit-1 x25 filter { filter-name}      
        ncl> enable routing circuit x25_circuit-1      
        ncl> create routing circuit x25_circuit-1 reachable address ughh_v -      
        _ncl> address prefix /4145418715004108002b0ed41e      
              
        ncl> set routing circuit x25_circuit-1 reachable address ughh_v -      
        _ncl> dte address { 2267643 }      
              
        ncl> set routing circuit x25_circuit-1 reachable address ughh_v -      
        _ncl> mapping manual      
              
        ncl> enable routing circuit x25_circuit-1 reachable address ughh_v      
        

        Specify the address prefix when you create the routing circuit entity. You cannot modify this attribute with the setcommand.
        For more information about reachable addresses for routing circuits, see Section 8.8.3.1.
      3. Create the X25 Access module and enable it:
        ncl> create x25 access      
        ncl> enable x25 access      
        
      4. Create the X25 Access template (identified when you set up the routing circuit), and set its attributes:
        ncl> create x25 access template template-name       
              
        ncl> set x25 access template template-name -      
        _ncl> destination dte address dte-address, -      
        _ncl> dte class dte-class-name      
        
        1. A routing circuit that invokes outbound X.25 calls uses an X25 Access template to supply most of the parameters for setting up the call. A routing circuit that receives inbound X.25 calls uses an X25 Access template to negotiate call parameters.
          Each X.25 routing circuit that you configure names an X25 Access template in its template attribute. You must, therefore, configure each of the X25 Access templates named in your X.25 routing circuits.
      5. Create the X25 Access filter (identified when you set up the routing circuit):
        ncl> create x25 access filter filter-name       
              
        ncl> set x25 access filter filter-name -      
        _ncl> inbound dte class dte-class-name,  -      
        _ncl> sending dte address dte-address      
              
        ncl> enable x25 access filter      
        
        1. A routing circuit that receives inbound X.25 calls requires one or more X25 Access filters. An X25 Access filter listens for incoming calls and passes them to the appropriate destination.
          Each X.25 static-incoming or X.25 dynamically-assigned routing circuit that you configure specifies the name of one or more X25 Access filters in its filter attribute. You must, therefore, configure the specified X25 Access filters.
          When setting up a filter for use with an X.25 static-incoming or X.25 dynamically-assigned circuits, specify the following X25 Access filter values:
          • call data mask%xff
          • call data value%x81

          8.8.4 Configuring Routing Over X.25 Static Circuits

          X.25 static circuits emulate a permanent point-to-point circuit over an X.25 switched virtual circuit. The underlying X.25 connection is established when DECnet-Plus starts up, and the connection remains until explicitly terminated (normally at system shutdown).

          When two systems communicate using X.25 static circuits, one system must define the circuit as incoming, while the other system must define it as outgoing. The system with an incoming circuit establishes communication with the X.25 network provider and waits for a connection from the other end. The system with the outgoing circuit initiates the X.25 call to the waiting system. If the call fails, the system keeps retrying until a successful connection is made. After the X.25 connection is established, the two systems automatically exchange routing layer configuration information, autoconfigure their routing databases, and begin two-way communications.

          8.8.4.1 Configuring Outgoing X.25 Static Circuits

          Take the following two steps to configure an outgoing X.25 static circuit:

          1. Use the X.25 or P.S.I. configuration procedure to define an x25 access template entity with the parameters necessary to establish a call to the destination system. See the appropriate X.25 or P.S.I. documentation.
          2. Create a routing circuit with the following commands:
            NCL>create routing circuit circuit-name type x25 static outgoing  
            NCL>set routing circuit circuit-name template template-name  
            NCL>enable routing circuit circuit-name 
            
            1. The routing circuit type must be x25 static outgoing.
            2. The routing circuit template attribute must contain the name of the x25 access template entity.

          8.8.4.2 Configuring Incoming X.25 Static Circuits

          Take the following three steps to configure incoming X.25 static circuits:

          1. Use the X.25 or P.S.I. configuration procedure to define the x25 access template and x25 access filter entities with the parameters necessary to accept a call from the source system. See the appropriate X.25 or P.S.I. documentation.
          2. Create a routing circuit with the following commands:
            NCL>create routing circuit circuit-name type x25 static incoming  
            NCL>set routing circuit circuit-name template template-name  
             
            NCL>set routing circuit circuit-name x25 filter {filter-name}   
            NCL>enable routing circuit circuit-name 
            
            1. The routing circuit type must be x25 static incoming.
            2. The routing circuit template entity must contain the name of the x25 access template entity.
            3. The routing circuit x25 filter entity must contain the name of the x25 access filter entity.


          Chapter 9
          Setting Up an OpenVMS Cluster Environment for DECnet-Plus

          This chapter provides information about:

          • Configuring OpenVMS Cluster satellite nodes
          • Setting up an OpenVMS Cluster alias
          • Sharing network applications in the OpenVMS Cluster environment

          9.1 Configuring OpenVMS Cluster Satellite Nodes in a DECnet-Plus Environment

          The information presented in the following sections supplements the material provided by the OpenVMS Cluster Systems for OpenVMS guide.

          9.1.1 Adding, Modifying, or Deleting an OpenVMS Cluster Satellite Node

          You must have planned your OpenVMS Cluster and have at least one OpenVMS Cluster boot node set up before using the information in this section. The following information is based on the CLUSTER_CONFIG.COM procedure found in the SYS$MANAGER directory. The OpenVMS Cluster Systems for OpenVMS guide describes this procedure. Digital has modified the procedure to make it compatible with the DECnet-Plus software. In the following sections, only those portions of CLUSTER_CONFIG.COM that have been modified are discussed in detail.


          Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

          [HR]

            PROFILE_VMS_014.HTML
            OSSG Documentation
             2-DEC-1996 12:35:09.05
          

          Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

          Legal