[Digital logo]
[HR]

DECnet-Plus for OpenVMS
Network Management

Previous | Contents

For example: 

NCP> set x25-protocol network mynet profile iso8208  
NCP> set x25-protocol dte 123456789 network mynet line dsv-0-0 state off  
NCP> set x25-protocol dte 123456789 network mynet channels 1024-1  
NCP> set dte 123456789 net mynet state on  

ncl> create x25 access dte class mynet type local  
ncl> set x25 access dte class mynet local dte {dte-0}  
ncl> create x25 protocol dte dte-0 profile "ISO8208"  
ncl> set x25 protocol dte dte-0 x25 address 123456789,inbound dte class mynet  
ncl> set x25 protocol dte dte-0 link service provider LAPB link dsv-0  
ncl> set x25 protocol dte dte-0 outgoing list {[1..1024]}  
ncl> enable x25 protocol dte dte-0

H.2.4 X25-PROTOCOL GROUP Database

The X25-PROTOCOL GROUP database associates individual local DTEs (qualified by their network) with an X.25 closed user group. The Phase IV database design is less flexible than the Phase V one (which allows complicated groups to be configured as one entity). Table H-4 shows the parameter mapping rules.

Table H-4 X25-PROTOCOL GROUP Database
Phase IV Name Phase V Entity Attribute Type
GROUP x25 protocol group Identifier Simple name
NETWORK N/A
DTE x25 protocol group members CUG member
NUMBER x25 protocol group members CUG member
TYPE + x25 protocol group type Enumeration {CUG, BCUG}

+Optional parameter.

For example: 

NCP> set x25-protocol group secret dte 123456789 network mynet type bilateral -  
_ number 99  

ncl> create x25 protocol group secret  
ncl> set    x25 protocol group secret type bcug,members {(dte=dte-0,index=99)}

H.2.5 X25-SERVER Database

The X25-SERVER database serves as the incoming call handler and controls the total number of connections on the system. In DECnet Phase V, it is replaced by three distinct modules. Table H-5 shows the parameter mapping rules.

Note

The x25 server entity is not supported by the X.25 for OpenVMS Alpha software. Therefore, no migration path exists from Phase IV endnodes to OpenVMS Alpha endnodes for the functionality described in this section. You must use a VAX P.S.I. multihost system or a Phase V gateway.

Table H-5 X25-SERVER Database
Phase IV Name Phase V Entity Attribute Type
MODULE X25-SERVER N/A
COUNTER TIMER + N/A
MAXIMUM CIRCUITS + x25 access maximum active ports Unsigned
x25 server maximum session connections Unsigned
x25 client maximum session connections Unsigned
STATE + x25 access N/A ¹
x25 server N/A ¹
x25 client N/A ¹

+Optional parameter.
¹Now controlled by the enable or disable directives.

H.2.6 X25-SERVER Local Destination Database

The local destinations in the X25-SERVER database are identified by the lack of a NODE qualifier.

Each destination points to an entry in the Phase IV OBJECT database, which identifies a command procedure to invoke. (VAX P.S.I. does not support executable images.)

In DECnet Phase V, objects are replaced by x25 access application entities. Each application specifies a set of filters to listen for incoming calls by using the filters attribute. The file attribute identifies a command procedure to invoke when a call is received. The type attribute for these applications should be set to X25.

Table H-6 shows the parameter mapping rules.

Table H-6 X25-SERVER Local Destination Database
Phase IV Name Phase V Entity Attribute Type
DESTINATION x25 access filter ¹ Identifier Simple name
x25 access application ¹ filters Set of simple name
x25 access application type X25 ²
OBJECT x25 access application Identifier Simple name
USER + x25 access application user Latin1String
PASSWORD + N/A N/A N/A
ACCOUNT + x25 access application account ³ Latin1String
CALL MASK + x25 access filter call data mask Octet string
CALL VALUE + x25 access filter call data value Octet string
CALLED ADDRESS + x25 access filter originally called address DTE address
EXTENSION MASK + x25 access filter called address extension mask Octet string
EXTENSION VALUE + x25 access filter called address extension value Octet string
GROUP + x25 access filter group Simple name
INCOMING ADDRESS + x25 access filter incoming dte address DTE address
NETWORK + x25 access filter inbound dte class Simple name
PRIORITY + x25 access filter priority Unsigned
RECEIVING DTE + x25 access filter receiving dte address DTE address
REDIRECT REASON + x25 access filter redirect reason Enumerated {[Not Specified], Busy, Out of Order, Systematic}
SENDING ADDRESS + x25 access filter sending dte address DTE address
SUBADDRESSES + x25 access filter subaddress range Set of range of unsigned

+Optional parameter.
¹Used for more than one attribute, due to a split of function between the X25 Access module and the X25 Access Application entity.
²X25 Access application type should be X25 for this type of destination.
³Not supported in all implementations.

For example: 

NCP> define object psi_mail number 0 file sys$system:psi$mail -  
_ user username password secret  
  
NCP> define module x25-server destination psi_mail object psi_mail -  
_ call mask ffffffffffffffffffffffffffffffff -  
_ call value ff00000056332e30204d41494c2d3131  

ncl> create x25 access filter PSI_MAIL  
ncl> set x25 access filter PSI_MAIL priority 3000 ,  -  
_ncl> call data value %XFF00000056332E30204D41494C2D3131 ,  -  
_ncl> call data mask %XFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF  
  
ncl> create x25 access application PSI_MAIL  
ncl> set x25 access application PSI_MAIL type X25,  -  
_ncl> file sys$system:psi$mail.com , user "mail$server", filters {PSI_MAIL}

H.2.7 X25-SERVER Remote Destination Database

Remote destinations are used when operating as an X.25 Connector (gateway) system. They contain a NODE qualifier, point to the X.25 GAP application at the remote access system, and might include access control information.

Note

The x25 server entity is not supported by the X.25 for OpenVMS Alpha software. Therefore, no migration path exists from Phase IV endnodes to OpenVMS Alpha endnodes for the functionality described in this section. You must use a VAX P.S.I. multihost system or a Phase V gateway.

Table H-7 shows the parameter mapping rules.

Table H-7 X25-SERVER Remote Destination Database
Phase IV Name Phase V Entity Attribute Type
DESTINATION x25 access filter ¹ Identifier Simple name
x25 server client ¹ Identifier Simple name
x25 server client ¹ filters Set of simple name ²
NODE x25 server client node DNS full name
OBJECT + x25 server client application End-user specification
USER + x25 server client user Latin1String
PASSWORD + x25 server client password Latin1String
ACCOUNT + x25 server client account Latin1String
CALL MASK + x25 access filter call data mask Octet String
CALL VALUE + x25 access filter call data value Octet String
CALLED ADDRESS + x25 access filter originally called address DTE address
EXTENSION MASK + x25 access filter called address extension mask Octet string
EXTENSION VALUE + x25 access filter called address extension value Octet string
GROUP + x25 access filter group Simple name
INCOMING ADDRESS + x25 access filter incoming dte address DTE address
NETWORK + x25 access filter inbound dte class Simple name
PRIORITY + x25 access filter priority Unsigned
RECEIVING DTE + x25 access filter receiving dte address DTE address
REDIRECT REASON + x25 access filter redirect reason Enumerated {[Not Specified], Busy, Out of Order, Systematic}
SENDING ADDRESS + x25 access filter sending dte address DTE address
SUBADDRESSES + x25 access filter subaddress range Set of range of unsigned

+Optional parameter.
¹Used for more than one attribute, due to a split of function between the x25 access and x25 server client entities.
²Note that this is a set of filters, not a single value.

For example: 

NCP> set x25-server destination host node mynode object 36 priority 200 -  
_ subaddresses 33-34  

ncl> create x25 access filter host  
ncl> set x25 access filter host priority 200,subaddress range {[33..34]}  
ncl> create x25 server client host  
ncl> set x25 server client host filters {host} ,  -  
_ncl> node LOCAL:.mynode

H.2.8 LINE Database

The LINE database contains information about all types of lines used in DECnet Phase IV. The X.25-related information is for those lines whose protocol parameter is LAPB or LAPBE.

The X.25 entries in the LINE database contain the operating characteristics of each individual connection to the PSDN at X.25 level 2 (frame level). Default values are taken mostly from the profile. Users can modify these values so that their system configurations match their PSDN subscription options. Table H-8 shows the parameter mapping rules.

Table H-8 LINE Database
Phase IV Name Phase V Entity Attribute Type
LINE modem connect line communications port Simple name
lapb link Identifier Simple name
CONTROLLER + modem connect line N/A ¹
COUNTER TIMER + N/A
HOLDBACK TIMER + lapb link holdback timer Unsigned
INTERFACE + lapb link interface type Enumerated {[DTE], DCE}
MAXIMUM BLOCK + lapb link maximum data size Unsigned
MAXIMUM RETRANSMITS + lapb link retry maximum Unsigned
MAXIMUM WINDOW + lapb link window size Unsigned
NETWORK lapb link profile 2,3 Simple name
PROTOCOL lapb link sequence modulus UNSIGNED 8(LAPB) or 128(LAPBE)
RECEIVE BUFFERS + lapb link receive buffers Unsigned
RETRANSMIT TIMER + lapb link acknowledge timer Unsigned
STATE + lapb link N/A 4

+Optional parameter.
¹If the CONTROLLER mode is LOOPBACK, then the startloop directive may be issued on the modem connect line using the mode attribute.
²See notes for X25-PROTOCOL NETWORK databases.
³See note on NETWORK for the X25-PROTOCOL DTE database.
4Now controlled by the enable or disable directives.

For example: 

NCP> define line dsv-0-0 network mynet protocol lapb state on  

ncl> create modem connect line dsv-0 communication port DSV-0-0 -  
_ncl> , profile  "NORMAL"  
ncl> set modem connect line dsv-0 -  
_ncl> modem control full, speed 9600 , suppress test indicator true  
ncl> create lapb link dsv-0 profile  "ISO8208"  
ncl> set lapb link dsv-0 physical line modem connect line dsv-0 ,  -  
_ncl> acknowledge timer 2718 ,  holdback timer 1359 ,  maximum data size 1031 -  
_ncl> ,  window size 7

H.2.9 X29-SERVER Database

The X29-SERVER database serves as the incoming X.29 call handler and controls the number of incoming X.29 connections on the system. In DECnet Phase V, it is merged with the X.25 call handler (X25 Access module and x25 access application entity). Table H-9 shows the parameter mapping rules.

Table H-9 X29-SERVER Database
Phase IV Name Phase V Entity
MODULE X29-SERVER N/A
COUNTER TIMER + N/A
MAXIMUM CIRCUITS + N/A
STATE + x25 access application x29_login

+Optional parameter.

H.2.10 X29-SERVER Destination Database

Each destination either points to an entry in the DECnet-VAX OBJECT database or it contains no object record. In the former case, the object identifies a command procedure to invoke. (VAX P.S.I. does not support executable images.) In the latter case, the call is considered to be for LOGINOUT.

In DECnet Phase V, objects are replaced by x25 access application entities. Each application specifies a set of filters to listen for incoming calls by using the filters attribute. The file attribute identifies a command procedure to invoke when a call is received. The type attribute for these applications should be set to X29 or X29 login if the call goes to LOGINOUT.

Table H-10 shows the parameter mapping rules.

Table H-10 X29-SERVER Destination Database
Phase IV Name Phase V Entity Attribute Type
DESTINATION x25 access filter ¹ Identifier Simple name
x25 access application ¹ filters Set of simple name
x25 access application type X29 or X29 login ²
OBJECT + x25 access application Identifier Simple name
USER x25 access application user Latin1String
PASSWORD N/A N/A N/A
ACCOUNT + x25 access application account ³ Latin1String
CALL MASK + x25 access filter call data mask Octet string
CALL VALUE + x25 access filter call data value Octet string
CALLED ADDRESS + x25 access filter originally called address DTE address
EXTENSION MASK + x25 access filter called address extension mask Octet string
EXTENSION VALUE + x25 access filter called address extension value Octet string
GROUP + x25 access filter group Simple name
INCOMING ADDRESS + x25 access filter incoming dte address DTE address
NETWORK + x25 access filter inbound dte class Simple name
PRIORITY + x25 access filter priority Unsigned
RECEIVING DTE + x25 access filter receiving dte address DTE address
REDIRECT REASON + x25 access filter redirect reason Enumerated {[Not Specified], Busy, Out of Order, Systematic}
SENDING ADDRESS + x25 access filter sending dte address DTE address
SUBADDRESSES + x25 access filter subaddress range Set of range of unsigned

+Optional parameter.
¹Used for more than one attribute, due to a split of function between the x25 access filter and x25 access application entities.
²X25 Access Application type should be X29 for this type of destination unless no object is specified, in which case it is X29 login.
³Not supported in all implementations.

H.2.11 X.25 Information in the CIRCUIT Database

The CIRCUIT database contains information on several distinct types of X.25 circuits. There are two major types: those used by Routing (DLM circuits) and those used by X.25 applications ("native" PVCs).

Although the PVC entities in Phase IV management are contained in the CIRCUIT database, they are invalid unless they can use an X25-PROTOCOL DTE database. This fact is important in DECnet Phase V because PVCs are child entities of x25 protocol dte entities.

Phase IV DLM circuits correspond to the X.25 static incoming, static outgoing, and permanent circuits used by DECnet Phase V routing over the Connectionless-Mode Network Service (CLNS). The following sections describe how these circuit types are configured for DECnet Phase V.

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

[HR] 

  PROFILE_VMS_026.HTML
  OSSG Documentation
   2-DEC-1996 12:35:30.63

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal