Software Product Description ___________________________________________________________________ PRODUCT NAME: DEC Network Integration Server Software, Version 2.1 SPD 36.05.05 DESCRIPTION The DEC Network Integration Server (DECNIS) software runs on any DEC- NIS 500 or 600 hardware unit. It provides multiprotocol routing, bridg- ing, and X.25 services to host systems on Local Area Networks (LANs) connected to the DECNIS or to host systems connected to the DECNIS over Wide Area Network (WAN) connections. Overview The DECNIS software provides a routing service for: o TCP/IP hosts o OSI-compatible systems o DECnet/OSI Phase V nodes o DECnet Phase IV nodes o Novell(R) NetWare(R) nodes o AppleTalk(R) nodes Multiprotocol routing of IP, DECnet, and OSI is implemented using the Integrated Intermediate System to Intermediate System (Integrated IS- IS) Routing Exchange Protocol. Routing of IP traffic is also supported using RIP in DECnet areas without the need for Integrated IS-IS rout- ing in the area. Routing of Novell NetWare and AppleTalk is implemented on the LAN using native protocols and over the WAN using encapsula- tion within IP. DIGITAL March 1993 AE-PQBSF-TE The DECNIS software provides a bridging service between LANs for end systems which support protocols that can not be routed by the DECNIS routing service. The DECNIS software supports local bridging between LANs connected to the same DECNIS unit and remote bridging between LANs connected to different DECNIS units over serial links. The DECNIS software also provides X.25 gateway and relay services to connect end systems on a LAN to X.25 Data Terminal Equipment (DTE) con- nected directly to the DECNIS or connected over an X.25 Packet Switched Data Network (PSDN). The DECNIS software image is installed and configured on any VAX-based OpenVMS or RISC/ULTRIX system: o Located on the same LAN or extended LAN as the DECNIS hardware unit o Accessible from another DECNIS connected directly to the target hard- ware unit over one or more serial links Once configured, the software image can be downline loaded to the hard- ware unit from the Digital load host. It can also be copied to an IP host or PC system for local loading using BOOTP or MOP. Once loaded, the software image can be stored in internal nonvolatile memory so that subsequent software loads can be performed without the need for a downline load over a network interface. This is termed Flash Loading. The DECNIS software can be managed from any OpenVMS or ULTRIX end sys- tem using either the Network Command Language (NCL) or DEC Management Control Center (DECmcc). Monitoring of the IP functions of the soft- ware can be performed from any system supporting the Simple Network Management Protocol (SNMP). A separate data tracing utility available on OpenVMS systems assists problem solving by tracing control messages received or sent by the DECNIS software. DECnet Routing 2 The DECNIS software implements both the DECnet Phase IV routing al- gorithm (routing vector) and the DECnet/OSI Phase V routing algorithm (link-state routing). The DECNIS software supports both intra-area rout- ing (level 1) and inter-area routing (level 2). The DECNIS software can run either the Phase IV or Phase V routing algorithm in either com- bination at each level. When running the Phase V algorithms at either level 1 or level 2, the routing software is still able to handle traf- fic generated by DECnet Phase IV end systems and performs any neces- sary address and header conversions. Communication with DECnet end or intermediate systems over serial con- nections can use DDCMP, Frame Relay, HDLC, PPP, or X.25 data link pro- tocols. The DECNIS software supports path splitting over up to four routing circuits. If the cost between the router and the destination node is the same on multiple serial circuits, then the DECNIS software splits the traffic across all the circuits. The DECNIS can communicate with other routers which support DECnet routing over PPP data links in ac- cordance with RFC 1376. IP Routing The DECNIS software provides support for the following IP routing pro- tocols: o Integrated IS-IS (RFC 1195) o RIP (RFC 1058) o EGP (RFCs 827, 888, and 904) Integrated IS-IS is based on OSI IS-IS Intra-Domain routing with ad- ditions to support IP routing as defined in RFC 1195. An IS-IS rout- ing circuit is required in order to handle IP traffic either within a level 1 area or between areas over a level 2 link. When using In- tegrated IS-IS, the software supports equal-cost path splitting of IP data over up to four equal-cost paths. Variable, but contiguous, IP subnet masks are also supported. 3 The DECNIS can also interoperate with other IP hosts or gateways us- ing RIP or EGP. It is also possible to route IP traffic using RIP within a DECnet Phase IV only network by running RIP over the DECnet Phase IV level 1 or level 2 links. In addition to IP routing protocols, the software also supports IP reachable addresses (static routes). The DECNIS software communicates with IP hosts and gateways on the lo- cal LAN using the ARP protocol (RFC 826). Proxy ARP (RFC 1027) is also supported. The DECNIS software supports Path MTU Discovery technique as speci- fied in RFC 1191. The DECNIS can communicate directly with IP hosts or gateways over CSMA /CD, DDCMP, Frame Relay, HDLC, PPP, or dynamically assigned X.25 cir- cuits. The DECNIS also supports forwarding of IP traffic over X.25 cir- cuits in accordance with RFC 877. When operating over DDCMP, Frame Re- lay, HDLC, and X.25 static circuits, the software communicates directly only with other Digital routers. When operating over X.25 dynamic circuits, the DECNIS can communicate with other routers which support IP routing over X.25 data links in accordance with RFC 877. The DECNIS can also communicate with other routers which support IP routing over PPP data links in accordance with RFC 1332. OSI Routing The DECNIS software fully implements the requirements of an OSI In- termediate System. The DECNIS software exchanges information about reach- ability of end systems using the OSI Intermediate System to Interme- diate System (IS-IS) Intra-Domain Routing Exchange Protocol as spec- ified in ISO/IEC 10589. OSI-compatible end systems on the same Local Area Network can exchange information with the DECNIS software and use the OSI End System to Intermediate System (ES-IS) Routing Exchange Pro- tocol as specified in ISO 9542. 4 The DECNIS software uses the OSI Connectionless Network Protocol (CLNP), as specified in ISO 8473, to communicate with OSI-compatible systems over an ISO 8802/3 or IEEE 802.3 Local Area Network. Communication over the serial links is via Frame Relay, HDLC, PPP, or X.25 protocols. The DECNIS can communicate with other routers which support OSI CLNP rout- ing over PPP data links in accordance with RFC 1377. Novell NetWare Routing The DECNIS software provides support of native Novell NetWare IPX V2.x and V3.x protocols over Ethernet and FDDI. Ethernet-II, 802.2, Encap- sulated Ethernet (802.2 SNAP), and 802.3 RAW (Novell) datalink for- mats are supported. The following Novell NetWare protocols are sup- ported: o Novell NetWare IPX Forwarding o Novell NetWare Routing Information Protocol (RIP) o Novell NetWare Service Access Protocol (SAP) Novell IPX is supported over wide area links via IP encapsulation ac- cording to RFC 1234. Network management of Novell IPX is via Digital's Control Management Information Protocol (CMIP). A DECNIS PC LAN Protocol software license is required for each DEC- NIS hardware unit running Novell NetWare. AppleTalk Routing The DECNIS software provides support of native EtherTalk(R), the Apple(R) specification for AppleTalk over Ethernet and FDDI. EtherTalk uses 802.2 SNAP datalink format. The following AppleTalk protocols are supported: o AppleTalk Phase-II Forwarding o AppleTalk Phase-II EtherTalk o AppleTalk Phase-II Address Resolution Protocol (AARP) o AppleTalk Phase-II Routing Table Maintenance Protocol (RTMP) o AppleTalk Phase-II Name Binding Protocol (NBP) 5 o AppleTalk Phase-II Zone Information Protocol (ZIP) o AppleTalk Phase-II Echo Protocol (echo replies only) AppleTalk is supported over wide area links to other DECNIS systems via IP encapsulation. Network management of AppleTalk is via Digital's Control Management Information Protocol (CMIP). A DECNIS PC LAN Protocol software license is required for each DEC- NIS hardware unit running AppleTalk. Bridging The DECNIS software supports both local and remote bridging of pro- tocols which cannot be routed (e.g., Digital's LAT) or which are not supported by the DECNIS routing software (e.g., Xerox(R) XNS). DECnet, IP, OSI, IPX, and AppleTalk protocols are normally routed and cannot be bridged except in the following cases: o IP, IPX, and AppleTalk traffic can either be individually routed or bridged on a system-wide basis. When routing is not enabled for any one or more of these protocols, it will be bridged on all in- terfaces. Bridge filtering can be enabled for IP, IPX, and AppleTalk on a port-by-port basis. o OSI null-Internet frames will always be bridged over either Eth- ernet or FDDI interfaces. The DECNIS software implements the IEEE 802.1D Spanning Tree Proto- col and will interoperate with other Digital or IEEE 802.1D-compliant bridges in the same extended LAN. When used as a local bridge, the DECNIS software forwards data packets from one LAN interface to another LAN interface. When used as a remote bridge, the DECNIS software forwards data pack- ets from one LAN interface, through the DEC WANcontroller 622 inter- face card, to a similar card on another DECNIS hardware unit. Remote bridging is only supported on the high-speed DEC WANcontroller 622 net- work interface card over HDLC or PPP data links; it is not supported 6 over Frame Relay, X.25 data links, or on the DEC WANcontroller 614 or 618 network interface card. Tinygram compression is supported in accordance with RFC 1220 over PPP datalinks. This allows Ethernet and 802.3 frames which are padded with zeros, such as LAT frames, to be compressed over remote bridging links. Bridging over multiple remote hops is supported subject to the Bridg- ing Configuration Guidelines section of this SPD. Bridge traffic, both local and remote, may be filtered based on a com- bination of source or destination address and protocol type on a port- by-port basis. Information about the operation of the DECNIS as a bridge can be ob- tained using SNMP to access the Bridge MIB variables as defined in RFC 1286. A DECNIS Bridge license is required for each DECNIS hardware unit run- ning local or remote bridging. Frame Relay Networks The DECNIS software supports connections over Frame Relay data links as specified in the Frame Relay Specification jointly developed by Dig- ital Equipment Corporation, StrataCom(R), Inc., Northern Telecom, and Cisco Systems Inc. Multiple virtual circuits can be multiplexed over a single Frame Relay link using the Data Link Control Identifier (DLCI) field of the Frame Relay LAPD header. For details of the Frame Relay options implemented, refer to the System Support Addendum (SSA 36.05.05-x). Support is provided over Frame Relay data links for DECnet, IP, OSI, AppleTalk, and IPX routing protocols and datagrams using PPP encap- sulation within the Frame Relay frame. Remote bridging is not supported over Frame Relay data links. The DECNIS Frame Relay implementation sup- ports both the LMI and ANSI-D switch control procedures. X.25 Routing Circuits 7 The DECNIS software supports the use of statically and dynamically as- signed X.25 routing circuits. Static circuits are established when the routing circuit is enabled and remain set up until the routing cir- cuit is disabled. Dynamically assigned circuits are established only when there is information to send over the routing circuit. They are disconnected when there is no further information to send. The DECNIS software supports more than one connection to one or more X.25 PSDNs. The software can share outgoing calls between all the DTEs connected to a PSDN. The DECNIS software supports routing over either Permanent Virtual Circuits (PVCs) or Switched Virtual Circuits (SVCs). Each X.25 virtual circuit can run only one routing protocol. However, different routing protocols can be run over separate virtual circuits on the same X.25 DTE connection. X.25 Gateway When operating as an X.25 Gateway, the DECNIS software transmits and receives X.25 packets to and from any of the following systems: o Any Digital systems which support the DNA Gateway Access Protocol (GAP). o Any systems located on the same LAN which support the ISO Logical Link Control 2 (LLC2) protocol (as described in ISO 8881). o Any X.25 DTE accessible over an X.25 Public Switched Data Network (PSDN) connected to the DECNIS. o Any X.25 DTE connected directly to a serial port of the DECNIS op- erating in X.25 DCE mode (ISO 8208 point-to-point mode). o Any X.25 DTE connected to any other DECNIS or DEC X.25gateway 100 /500 server accessible to the DECNIS over the DECnet/OSI routing network. When providing wide area access to an X.25 PSDN for end systems on the LAN which use LLC2, the DECNIS software fully implements the recom- mendations in ISO Technical Report 10029 as a CONS LAN/WAN relay. 8 X.25 packets can be relayed locally between any X.25 DTE attached to the DECNIS hardware unit and any other similarly attached X.25 DTE or any X.25 system connected to the same LAN. Additionally, X.25 pack- ets can be relayed to remote X.25 DTEs accessible to other DECNIS or DEC X25gateway 100/500 servers over a DECnet/OSI routing network. The software does not support the relaying of X.25 packets generated from an X.25 DTE connected to an X.25 PSDN to an X.25 DTE connected to an- other X.25 PSDN. The DECNIS software supports both Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs) and allows multiple connections to one or more PSDNs. Most major international public X.25 PSDNs are supported. For a current list of public X.25 PSDNs and X.25 (1984) op- tional facilities supported by the DECNIS, refer to the System Sup- port Addendum (SSA 36.05.05-x). The following accounting information is provided by the DECNIS X.25 Gateway software: o Logging of virtual circuit accounting when calls are cleared o Logging of accounting records to a designated Event Logging sink o Logging to multiple sinks for reliability The following security mechanisms are supported in the DECNIS X.25 Gate- way software: o Inbound and outbound calls can be controlled on the basis of the remote DTE, the application, and, if applicable, the X.25 Access node o Access to accounting sink management is restricted to authorized users o Access to accounting source management is restricted to authorized users Installation and Configuration 9 The minimum requirement is for one VAX-based OpenVMS or RISC/ULTRIX host on which to install and configure the DECNIS software. However, the DECNIS software can be copied to any number of load hosts. This helps to protect against loss of service if a single load host is un- available or unable to load the system for any other reason. Installation is performed using VMSINSTAL (on OpenVMS) or setld (on ULTRIX). The software must be configured using two configuration pro- grams supplied with the product. These configuration programs allow the network manager to set up the configuration files and to define the required DECNIS management entities. DECNIS units can be loaded from any Digital host systems over Ether- net and FDDI using Digital's Maintenance Operation Protocol (MOP) or BOOTP/TFTP. DECNIS units can also be loaded over serial interfaces from any Digital system supporting MOP over HDLC links. DECNIS system im- ages and configuration files can also be copied to any IP end system in the network for loading local DECNIS units over Ethernet or FDDI using BOOTP/TFTP. The DECNIS also supports loading over HDLC links to other DECNIS sys- tems. When loading over HDLC links, the DECNIS system performing the loading operation must be configured to copy the required files from any load host by establishing a DECnet connection to that load host. Loading of DECNIS units may also be daisy-chained over a sequence of serial links. The only restriction is that the first DECNIS in the chain must be on the same LAN as the load host and each member of the chain must be another DECNIS unit. The DECNIS software allows BOOTP requests broadcast over a local area network to be forwarded to a BOOTP server located at an IP address any- where within the network. Once loaded, the DECNIS software and, optionally, the configuration information can be saved in internal nonvolatile memory. Subsequent loads can be performed from this nonvolatile memory rather than from a local or remote load host. This is termed Flash loading. 10 The Flash loading options allow configuration data to be included in a single load file which can be copied to a suitably configured PC and subsequently loaded from the PC into the DECNIS nonvolatile memory for subsequent reload into the DECNIS. Management The DECNIS software conforms to both the Digital Enterprise Manage- ment Architecture (EMA) and the Internet Structure of Management In- formation. Access to the manageable entities is supported using ei- ther Digital's Control Management Information Protocol (CMIP) or the Simple Network Management Protocol (SNMP). Permanent changes to the configuration of the DECNIS software can be made by using the configuration utilities to create a script file and then rebooting the hardware unit. Temporary changes to the configu- ration of the DECNIS software can be made by using any EMA-compliant Director such as NCL, or DECmcc from any available system. Other management tasks can also be performed from Network Management directors allowing the network manager to: o Manage specific connections, for example, set up the data links, enable and disable circuits. o Monitor network traffic, for example, enable event logging, dis- play counters. o Resolve problems, for example, test circuit availability, perform loopback tests. An additional utility called Common Tracing Facility (CTF) is avail- able on OpenVMS systems to assist with problem solving by tracing con- trol messages as they are processed by the DECNIS software. The DECNIS responds to, but can not source, IP and OSI PINGs. The DEC- NIS can also forward echo requests and responses. 11 Information about Internet variables held on the DECNIS software can also be accessed by Network Management systems using the Simple Net- work Management Protocol (SNMP). The DECNIS software implements the Management Information Base-II (MIB-II) and Bridge MIB variables which can be read by any SNMP management station. Note that support is not provided for modifying these variables from an SNMP management sta- tion. Also, SNMP can only be used to access these variables when rout- ing is enabled for IP traffic. Physical Line Support The DECNIS hardware units are modular, expandable, hardware platforms. The DECNIS 500 is a four-slot enclosure while the DECNIS 600 is a nine- slot enclosure. The first two slots are reserved for Management Pro- cessor and Pool Memory cards with the remaining slots available for network interface cards. The DECNIS 500 can therefore support up to two network interface cards while the DECNIS 600 can support up to seven network interface cards. The following network interface cards occupy a single slot of the DEC- NIS enclosure and are supported by the DECNIS 500/600 hardware units: o DEC LANcontroller 601 - Single-port Ethernet/IEEE 802.3 interface o DEC LANcontroller 602 - Dual-port Ethernet/IEEE 802.3 interface o DEC WANcontroller 614 - Four-port, low-speed serial interface sup- porting synchronous operation at line speeds from 1.2 Kbits/s to 128 Kbits/s or asynchronous operation at line speeds from 1.2 Kbits /s to 38.4 Kbits/s o DEC WANcontroller 618 - Eight-port, low-speed serial interface sup- porting synchronous operation at line speeds from 1.2 Kbits/s to 128 Kbits/s or asynchronous operation at line speeds from 1.2 Kbits /s to 38.4 Kbits/s interface o DEC WANcontroller 622 - Dual-port, high-speed serial interface sup- porting synchronous operation at line speeds from 9.6 Kbits/s to 2 Mbits/s 12 The following network interface card occupies two slots of the DEC- NIS enclosure and is supported by the DECNIS 600 hardware unit only: o DEC FDDIcontroller 621 - Single-port FDDI interface, SAS or DAS Communication over serial lines is full-duplex with full modem con- trol on all line(s). HDLC, PPP, and X.25 data links are supported on all serial interface cards. DDCMP data links are only supported on the DEC WANcontroller 614 and 618 in both synchronous or asynchronous op- eration. When operating in asynchronous mode, the maximum line speed supported is 38.4 Kb/s. Frame Relay and remote bridging are only sup- ported on the DEC WANcontroller 622 network interface card. The ta- ble below summarizes data link support on the serial line interface cards. ___________________________________________________________________ InterfaceHDLC__PPP____X.25__DDCMP__FR____RB________________________ W614 Yes Yes Yes Yes No No W618 Yes Yes Yes Yes No No W622____Yes____Yes____Yes___No_____Yes___Yes_______________________ The DEC WANcontroller 614, 618, and 622 serial interfaces support V.24 interchange circuits with the following electrical interfaces: o DEC WANcontroller 614/618: - V.28 (EIA-RS232-D/EIA-RS232-C) - V.36/V.11 (RS449/RS422) - V.35 o DEC WANcontroller 622: - V.36/V.11 (RS449/RS422) - V.35 - CCITT X.21 (Leased line services) 13 - British Telecom Kilostream The number of lines supported depends on the interface and the num- ber of these interfaces installed in the hardware unit. The serial in- terfaces provide only the electrical interface of a DTE rather than a DCE, and do not provide clock signals. An external clock source (such as a modem) is required for each serial connection. For the DEC WANcontroller 614, a multi-standard distribution panel is provided for support of RS232/V.28, RS422/V.11, and V.35 interfaces. Separate adapter cables provide the necessary interchange circuits for each serial line. Different interface standards can be supported on each of the four available ports. Refer to the System Support Adden- dum (SSA 36.05.05-x) for further information on the required adapter cable. For the DEC WANcontroller 618, separate distribution panels are re- quired for support of RS232/V.28, RS422/V.11, and V.35 interfaces. For use with British Telecom Kilostream services, an extra adapter cable is used in conjunction with the RS422/V.11 distribution panel. Refer to the System Support Addendum (SSA 36.05.05-x) for further informa- tion on the required adapter cable. For the DEC WANcontroller 622, separate adapter cables provide the nec- essary interchange circuits for each serial line. Refer to the Sys- tem Support Addendum (SSA 36.05.05-x) for further information on the required adapter cables. When used with T1 or G.703 lines, the additional requirements for op- eration of the DEC WANcontroller 622 are as follows: o The DEC WANcontroller 622 supports only clear channel interfaces. Connection to a T1 or G.703 line requires a V.35/RS422 to T1/G.703 DSU/CSU converter to provide framing to meet CCITT G.704. The DEC WANcontroller 622 does not provide either T1 framing pulses or sep- arate channels for 64 Kbits/s control data for G.703. 14 o The DEC WANcontroller 622 does not guarantee line density. T1 links can offer only 1.536 Mbits/s or 1.344 Mbits/s rates. 1.536 Mbits /s rates require the DSU/CSU converter to offer B8ZS and the line to accept bipolar violations. 1.334 Mbits/s rates require the DSU /CSU converter to offer B7. o Transmit clocking should be provided by the DCE, CCITT 114. The DEC WANcontroller 622 uses CCITT 114 to clock data out of the DTE and will source a CCITT 113 transmit clock. CCITT 113 should be used by the DCE to receive the transmit data. The DEC WANcontroller 622 implements CCITT 113 as a buffered version of CCITT 114. This clock- ing scheme ensures both network synchronization and minimized skew between the clock and data for a range of cable lengths and param- eters. If the above transmit clocking mechanism is not provided by the DCE, this DCE must provide a method of adjusting the phase of the clock used to sample the data with respect to that supplied to the DTE. This re- quires that the DCE provide test points to allow analysis of the clock and data waveforms and that this adjustment be performed on instal- lation and after any subsequent alteration of the connection cable. This alternative method is also required for DCEs utilizing the X.21 interface. For more information about CSU/DSU converters supported by the DEC WAN- controller 622, please refer to the System Support Addendum (SSA 36.05.05- x). Network Size and Supported Circuits DECnet Phase IV networks are hierarchical networks that can be seg- mented into up to 63 areas, each containing up to 1,023 nodes. Note that these are maximum values permitted by the Digital Network Archi- tecture and satisfactory operation in large networks requires proper network planning. 15 DECnet/OSI Phase V domains can be virtually unlimited. However, the actual size of a domain is limited by the product's memory size and processor power. Table 1 lists the values of the parameters used to determine the size of the supported network for DECNIS 500 and 600 se- ries hardware units. Note that these figures are given as a rough guide only. Actual sizes experienced will depend on a number of factors including the topolog- ical characteristics of the network, the mix of protocols and data link interfaces, and the amount of routing control traffic generated by the network. Please consult your local Digital office for more details and for assistance with network sizing and planning. 16 ___________________________________________________________________ Table_1:_Network_Parameter_Sizes___________________________________ Attribute___________________Value__________________________________ Total areas in domain 450 [1] Routing addresses in area 5000 [2] Bridging addresses in LAN 10000 Broadcast end systems 5000 OSI reachable addresses 200 [1] Level 1 routers in area 100 Level 1 broadcast routers 70 Level 1 P-to-P router 30 adjacencies Level 1 P-to-P end system 120 adjacencies Level 1 manual adjacencies 60 Level 2 routers per domain 500 Level 2 P-to-P router 30 adjacencies Level 2 manual adjacencies 200 Level 2 broadcast routers 40 Local IP interface ad- 50 dresses IP nets in domain 1640 IP router adjacencies 700 External IP routes 500 IP reachable addresses 200 IP subnet adjacencies 50 Novell IPX networks 250 Novell IPX services 250 AppleTalk networks 100 AppleTalk zones 100 X.25 DTEs 50 [3] X.25 virtual circuits 128 [3] X.25 DA adjacencies 120 Frame Relay PVCs per W622 32 [4] interface__________________________________________________________ Notes: 1. The total number of areas and OSI reachable addresses cannot ex- ceed 450. If not all 200 reachable addresses are used, then more areas can be supported up to a maximum of 450. 2. Since an end system can have more than one address, the actual num- ber of end systems per area will generally be less than this fig- ure. 3. A maximum of 128 X.25 virtual circuits can be allocated. X.25 DTEs, routing virtual circuits, and gateway virtual circuits are allo- cated from the same memory. The numbers given are the maximum for each. Each of these entities use on average the following number of units from an available pool of 370 units as shown in the X.25 Memory Units table below. ___________________________________________________________________ Table_2:_X.25_Memory_Units_________________________________________ Entity______________________Units__________________________________ X.25 DTE/DCE 10 X.25 DLM virtual circuit 4 X.25 DA virtual circuit 3 X.25 Gateway virtual 1 circuit____________________________________________________________ 4. Although each DEC WANcontroller 622 interface can support up to 32 Frame Relay PVCs, the number of routing circuits for each DECNIS system is limited by the point-to-point router adjacency parame- ter. Attribute Definition 18 Total Maximum number of area addresses in the routing Do- areas in main. This value, plus the number of OSI reachable domain: addresses, is the total number of addresses which can be forwarded to using Level 2 routing. Routing Total number of addresses (IDs) which can be forwarded addresses to using Level 1 forwarding. Each router may have in area: one or two addresses, each end system has one or more addresses (e.g., a Phase IV and a Phase V address; each one counts as a separate address). Bridging Total number of Ethernet addresses which can be han- addresses dled for end systems in the extended LAN connected in LAN: over both local and wide area links. Broadcast Number of end systems which may be connected and ac- end sys- tive via broadcast. tems OSI reach- Number of OSI reachable addresses which may be man- able ually configured on the local router (when the local addresses: router is being used as a Level 2 router). Level 1 Number of Level 1 routers in the area. routers in area: Level 1 Number of Level 1 routers which may be connected and P-to-P active via serial links. router ad- jacencies: Level 1 Number of end systems which may be connected and ac- P-to-P end tive via serial links. system ad- jacencies: Level 1 Number of active L1 reachable addresses. manual ad- jacencies: 19 Level 2 Number of Level 2 routers in the routing domain. routers in domain: Level 2 Number of Level 2 routers which may be connected and P-to-P active via serial connections. router ad- jacencies: Level 2 Number of active Level 2 reachable addresses. P-to-P manual ad- jacencies: Level 2 Number of Level 1 routers which may be connected and broadcast active via broadcast. routers: Local IP Number of IP addresses which can be configured for the interface local interface ports. addresses: IP nets Number of unique nets/subnets reachable within the per do- local routing domain at Level 2. This number is the main: summation of IP subnets propagated from Level 1 IS- IS, IP subnets propagated from RIP and EGP, and IP Reachable Address Prefixes defined at Level 2. IP router Maximum number of IP routes. adjacen- cies: External Number of IP routes learned externally through RIP or IP routes: IGP. IP reach- Number of manually configured IP nets/subnets. able addresses: IP subnet Number of locally connected subnets. adjacen- cies: 20 Novell IPX Number of Novell IPX networks. networks: Novell IPX Number of Novell IPX services. services: AppleTalk Number of AppleTalk networks. networks: AppleTalk Number of AppleTalk zones. zones: X.25 DTEs: Maximum number of physical X.25 connections supported per system. X.25 Maximum number of X.25 virtual circuits (SVC or PVC) Virtual supported per system for both routing and/or X.25 Circuits: gateway use. X.25 DA Maximum number of active X.25 DA circuits. adjacen- cies: Bridging Configuration Guidelines When bridging over remote links using the DEC WANcontroller 622 net- work interface cards, the performance of delay-sensitive protocols (such as LAT) cannot be guaranteed without paying careful consideration to the number of bridging hops and the speed of the lines connecting the DECNIS units. Digital warrants and supports the DECNIS software product when used in extended LAN configurations subject to the following configuration restrictions: o Remote bridging is only supported on the DEC WANcontroller 622 net- work interface card; it is not supported on the DEC WANcontroller 614 or 618 network interface card. o Remote bridging is not supported over X.25 data links. o The minimum line speed supported for remote bridging between DEC- NIS units is 56 Kb/s. o Remote bridging over satellite links is not supported. 21 o A maximum of seven local and remote bridges may be configured in series between any two communicating end stations. Each DECNIS unit, or any other IEEE 802.1D or LANbridge 100 compatible bridge, counts as one bridge towards this maximum configuration of seven bridges. o Local Area VAXclusters are not supported over remote bridging links. o Digital's PC Systems Architecture (PCSA) PATHWORKS services may be restricted over remote bridging links; please refer to the rele- vant Software Product Descriptions for further information. In addition to the above configuration restrictions, Digital also rec- ommends that, when using 56 Kb/s or 64 Kb/s links between DECNIS units for remote LAT access, the following configuration guidelines also be followed to ensure reliable operation: o A maximum of two serial synchronous links is recommended in the span- ning tree path between the LAT server and the LAT host. o A minimum of 3 Kb/s should be allocated for each active LAT ses- sion which needs to be supported simultaneously across the remote link. When using Tinygram compression, 2 Kb/s should be allocated for each active LAT session. o Digital recommends that the link be reserved for LAT usage and not shared with routed traffic such as DECnet, OSI, or IP. Also, other bridged traffic which may generate large packets over the remote link should be filtered using the DECNIS Bridge Filtering facil- ities. Public Networks Supported Refer to the System Support Addendum (SSA 36.05.05-x) for a list of the public networks that are supported by the DECNIS software. Con- nections to public networks not listed in the SSA are not supported by Digital at the time of publication of this SPD. Please consult your local Digital office for any questions you have concerning other pub- lic networks. 22 In addition to the public X.25 PSDNs listed in the SSA, certain pri- vate PSDNs are supported by the DECNIS software. The appropriate pro- files are included in these products. Conformance to Standards The DECNIS software conforms to the following IEEE and ISO standards, CCITT recommendations, and Internet RFCs: o IEEE 802.1D-1990-Media Access Control (MAC) Bridges o ISO 8802-2 - Local Area Networks/Part 2: Logical Link Control o ISO 8802-3 - Local Area Networks/Part 3: CSMA/CD Access Method and Physical Layer Specification o ISO 8473 - Specification of Protocol to Provide the Connectionless- mode Network Service o ISO 9542 - End System to Intermediate System (ES-IS) Routing Ex- change Protocol for Use in Conjunction with ISO 8473 o ISO/IEC 10589 - Intermediate System to Intermediate System (IS-IS) Intra Domain Routing Exchange Protocol for Use in Conjunction with ISO 8473 o ISO 3309 - High-level Data Link Control (HDLC) Frame Structure o ISO 7776 - High-level Data Link Control (HDLC) Procedures: X.25 LAPB- compatible DTE Data Link Procedures o CCITT recommendation X.25 (1978, 1980, or 1984) using the LAPB or LAPBE variants of the data link o ISO 8208 - X.25 Packet Level Protocol for Data Terminal Equipment o ISO 8881 - Use of X.25 Packet Level Protocol in Local Area Networks (LLC2) o ISO TR 10029 Operation of an X.25 Interworking Unit (CONS LAN/WAN Relay) o RFC 768 - User Datagram Protocol (UDP) o RFC 791 - Internet Protocol (IP) 23 o RFC 792 - Internet Control Message Protocol (ICMP) o RFC 826 - Address Resolution Protocol (ARP) o RFC 827, 888 & 904 - Exterior Gateway Protocol (EGP) o RFC 877 - Standard for the transmission of IP datagrams over pub- lic data networks (X.25) o RFC 922 - Broadcasting Internet Datagrams in the Presence of Sub- nets o RFC 950 - Internet Standard Subnetting Procedure o RFC 951 - BOOTSTRAP Protocol (BOOTP) o RFC 783 - TFTP Protocol (Revision 2) o RFC 1009 - Requirements for Internet Gateways o RFC 1027 - Using ARP to implement transparent subnet gateways o RFC 1058 - Routing Information Protocol (RIP) o RFC 1155 - Structure and Identification of Management Information for TCP/IP-based Internets o RFC 1157 - Simple Network Management Protocol (SNMP) o RFC 1191 - Path MTU Discovery o RFC 1195 - Use of OSI IS-IS for Routing in TCP/IP and Dual Envi- ronments o RFC 1213 - Management Information Base for Network Management of TCP/IP-based Internets (MIB-II) o RFC 1220 - Point-to-Point Protocol Extensions for Bridging o RFC 1234 - Tunneling IPX Traffic through IP networks o RFC 1286 - Definitions of managed objects for bridges o RFC 1331 - The Point-to-Point Protocol (PPP) for the Transmission of Multi-Protocol Datagrams over Point-to-Point Links o RFC 1332 - The PPP Internet Protocol Control Protocol (IPCP) 24 o RFC 1376 - The PPP DECnet Phase IV Control Protocol (DNCP) o RFC 1377 - The OSI Network Layer Control Protocol (OSINLCP) Performance When operating over serial line connections the overall packet rate will be less than that indicated by the aggregate line speeds and is determined by such factors as: o Type of traffic (routing updates or data packets) and data rates o Mix of protocol types o Proportion of leased line to X.25 traffic o The path of messages passing through the product (WAN-to-WAN, WAN- to-LAN, or LAN-to-LAN) o Communications line characteristics o Frequency and type of errors on the serial links o Network topology o Protocol overhead Please contact your local Digital office for further details of the performance characteristics of the product. INSTALLATION If the DECNIS hardware unit is to be used for connection to a public X.25 network, Digital recommends that a customer's first purchase of the product include Digital Installation Services. These services pro- vide for installation of the software product by an experienced Dig- ital software specialist. HARDWARE REQUIREMENTS The DECNIS software requires the following hardware: o A DECNIS 500 or 600 hardware unit as specified in the System Sup- port Addendum (SSA 36.05.05-x) 25 o Processor and/or hardware configurations as specified in the Sys- tem Support Addendum (SSA 36.05.05-x) o VT220-compatible terminal for running the configuration utility o Cables and modem equipment supporting the required physical inter- face standards and line speeds SOFTWARE REQUIREMENTS The DECNIS software needs to be installed on a VAX-based system run- ning the OpenVMS operating system, or a RISC-based system running the ULTRIX operating system. Each OpenVMS VAX system acting as a load host or dump receiver requires: o OpenVMS VAX Operating System o DECnet-VAX with DECnet-VAX Extensions installed or DECnet/OSI for OpenVMS VAX Each RISC/ULTRIX system acting as a load host or dump receiver requires: o ULTRIX Operating System or ULTRIX Worksystem Software o DECnet/OSI for ULTRIX for RISC and VAX Each PC acting as a load host requires: o PATHWORKS for DOS When using the DECNIS X.25 Gateway service, the following X.25 client systems are supported: o VAX P.S.I. Access (SPD 27.78.xx) o DECnet-VAX with DECnet-VAX Extensions kit (SPD 29.03.xx) o DECnet/OSI for OpenVMS VAX (SPD 25.03.xx) o DEC X.25 Gateway Client for ULTRIX (SPD 32.34.xx) 26 o DECnet/OSI for DEC OSF/1 (SPD 41.92.xx) Note that when using X.25 Gateway services, access to a Digital Name Service (DNS) server is optional. Refer to the System Support Addendum (SSA 36.05.05-x) for availabil- ity and required versions of prerequisite/optional software. ORDERING INFORMATION The software license allows unrestricted use of the software on the DECNIS 500/600 series hardware unit on which the product is used. Software Licenses: DECNIS Router License: QL-GX7A9-AA DECNIS Bridge License: QL-GZNA9-AA DECNIS PCLAN License: QL-08VA9-AA The DECNIS Router License includes the use of IP, DECnet, and OSI rout- ing, and X.25 routing and gateway services provided by the DECNIS soft- ware. A DECNIS Bridge license is required for each DECNIS hardware unit run- ning local or remote bridging. A DECNIS PCLAN license is required for each DECNIS hardware unit run- ning Novell NetWare and/or AppleTalk. Software Media for OpenVMS VAX Operating System: QA-GX7AA-H* Software Media for RISC/ULTRIX Operating System: QA-GX7AC-H* Software Documentation for OpenVMS and ULTRIX Operating Systems: QA- GX7AA-GZ Software Product Services: QT-GX7A*-** 27 The software media kit includes a Bookreader version of the DECNIS Prob- lem Solving Guide. * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. SOFTWARE LICENSING A separate license is needed for each DECNIS 500/600 series hardware unit on which the software product is used (except as otherwise spec- ified by Digital). The licensing provisions of Digital's Standard Terms and Conditions specify that the software and any part thereof (but excluding those parts specific to the load hosts) may be used only on the single DEC- NIS 500/600 series hardware unit on which the software is operated, but may be copied, in whole or in part (with the proper inclusion of Digital's copyright notice and any proprietary notices on the soft- ware) between multiple load hosts. This software is furnished under the licensing provisions of Digital Equipment Corporation's Standard Terms and Conditions. For more in- formation about Digital's licensing terms and policies, contact your local Digital office. SOFTWARE PRODUCT SERVICES A variety of service options are available. For more information, please contact your local Digital office. SOFTWARE WARRANTY The DECNIS software is warranted for use only with supported DECnet and TCP/IP products supplied by Digital. Any system connected to one of the DECNIS unit's serial link(s) or creating a DECnet circuit over a PSDN must run a current version of a DECnet product using any sup- ported serial interface. 28 Digital has designed or adapted the X.25 portion of this product to operate with equipment conforming to the standards as listed in this SPD, to the public PSDNs as listed in the System Support Addendum (SSA 36.05.05-x), and to certain private PSDNs, for which Digital has in- cluded specific PSDN profiles in this product. Digital cannot offer its standard warranty for this product unless it has been configured appropriately for the PSDN. If the product has not been configured appropriately, the product will not be supported by Digital. Each PSDN listed in the SSA indicates Digital's commitment to support- ing the DECNIS software for that public service. However, it does not imply that the appropriate networking authority has granted network certification for the product. Please contact your Digital office for up-to-date information on certification status. Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum of this SPD. (R) Accunet is a registered trademark of American Telephone and Telegraph Company. (R) Apple, AppleTalk, and EtherTalk are registered trademarks of Apple Computer, Inc. (R) Autonet is a registered trademark of Sanders Associates, Inc. (R) BT is a registered trademark of British Telecommunications plc. (R) CompuServe is a registered trademark of CompuServe, Inc. (R) Novell and NetWare are registered trademarks of Novell, Inc. (R) StrataCom is a registered trademark of StrataCom, Inc. (R) TYMNET is a registered trademark of McDonnell Douglas Corpora- tion. (R) Xerox is a registered trademark of Xerox Corporation. 29 [TM] The DIGITAL Logo, Bookreader, CI, DDCMP, DEC, DECmcc, DECnet, DECNIS, DECstation, DECsystem, Digital, DNA, MicroVAX, Open- VMS, PATHWORKS, TK, ULTRIX, VAX, VAXcluster, VAXft, VAXserver, VAXstation, and VT220 are trademarks of Digital Equipment Corporation. 30 System Support Addendum ___________________________________________________________________ ___________________________________________________________________ PRODUCT NAME: DEC Network Integration Server Software, Version 2.1 SSA 36.05.05-A HARDWARE REQUIREMENTS Processor Support for OpenVMS VAX Host Systems VAX: VAX 4000 Model 100, VAX 4000 Model 200, VAX 4000 Model 300, VAX 4000 Model 400, VAX 4000 Model 500, VAX 4000 Model 600 VAX 6000 Model 200 Series, VAX 6000 Model 300 Series, VAX 6000 Model 400 Series, VAX 6000 Model 500 Series, VAX 6000 Model 600 Series VAX 7000 Model 600 Series, VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840 VAX 9000 Model 110, DIGITAL March 1993 AE-PQBTF-TE VAX 9000 Model 210, VAX 9000 Model 300 Series, VAX 9000 Model 400 Series VAX 10000 Model 600 Series VAXft Model 110/310/410/610/612 VAX-11/730, VAX-11/750, VAX-11/780, VAX-11/785 MicroVAX: MicroVAX II, MicroVAX 2000, MicroVAX 3100 Model 10/10E, MicroVAX 3100 Model 20/20E, MicroVAX 3100 Model 30, MicroVAX 3100 Model 40, MicroVAX 3100 Model 80, MicroVAX 3100 Model 90 MicroVAX 3300, MicroVAX 3400, MicroVAX 3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900 VAXstation: VAXstation II, VAXstation 2000, VAXstation 3100 Model 30, VAXstation 3100 Model 38, VAXstation 3100 Model 40, VAXstation 3100 Model 48, VAXstation 3100 Model 76, VAXstation 3200, VAXstation 3500, VAXstation 3520, VAXstation 3540 VAXstation 4000 VLC, VAXstation 4000 Model 60, 2 VAXstation 4000 Model 90 VAXserver: VAXserver 3100 Model 10/10E, VAXserver 3100 Model 20/20E, VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600, VAXserver 3800, VAXserver 3900 VAXserver 4000 Model 200, VAXserver 4000 Model 300, VAXserver 4000 Model 500 VAXserver 6000 Model 210, VAXserver 6000 Model 220, VAXserver 6000 Model 310, VAXserver 6000 Model 320, VAXserver 6000 Model 410, VAXserver 6000 Model 420, VAXserver 6000 Model 510, VAXserver 6000 Model 520, VAXserver 6000 Model 610, VAXserver 6000 Model 620, VAXserver 6000 Model 630 3 Processors Not Supported: MicroVAX I, VAXstation I, VAX-11/725, VAX-11/782, VAXstation 8000 Processor Support for ULTRIX Host Systems RISC-Based Processors: DECstation:DECstation 2100, DECstation 3100, DECstation 3100s Personal DECstation 5000 Model 20/25 HX, Personal DECstation 5000 Model 20/25 MX, Personal DECstation 5000 Model 20/25 TX, Personal DECstation 5000 Model 20/25 PXG+, Personal DECstation 5000 Model 20/25 PXG Turbo+, DECstation 5000 Model 120/125/133 CX, DECstation 5000 Model 120/125/133 HX, DECstation 5000 Model 120/125/133 MX, DECstation 5000 Model 120/125/133 PX, DECstation 5000 Model 120/125/133 TX, DECstation 5000 Model 120/125/133 PXG, DECstation 5000 Model 120/125/133 PXG+, DECstation 5000 Model 120/125/133 PXG Turbo, DECstation 5000 Model 120/125/133 PXG Turbo+, DECstation 5000 Model 200 CX, DECstation 5000 Model 200 HX, DECstation 5000 Model 200 MX, DECstation 5000 Model 200 PX, DECstation 5000 Model 200 TX, DECstation 5000 Model 200 PXG, DECstation 5000 Model 200 PXG+, DECstation 5000 Model 200 PXG Turbo, 4 DECstation 5000 Model 200 PXG Turbo+, DECstation 5000 Model 240 HX, DECstation 5000 Model 240 MX, DECstation 5000 Model 240 TX, DECstation 5000 Model 240 PXG+, DECstation 5000 Model 240 PXG Turbo+ DECsystem: DECsystem 3100, DECsystem Model 25, DECsystem 5000 Model 200, DECsystem 5000 Model 240, DECsystem 5100, DECsystem 5400, DECsystem 5500, DECsystem 5810, DECsystem 5820, DECsystem 5830, DECsystem 5840, DECsystem 5900 Processor Restrictions A TK50 tape drive is required for standalone MicroVAX 2000 and VAXstation 2000 systems. Every load host on which the DECNIS software is installed must con- tain: o A valid system configuration for the relevant operating system and for the appropriate DECnet product (refer to the DECnet and appro- priate operating system SPDs). o A supported direct LAN or WAN connection to the DEC Network Inte- gration Server hardware unit. or A network connection to a DEC Network Integration Server hardware unit connected directly over a serial link to the unit to be loaded. 5 o An appropriate device available to read the software during instal- lation: - Magnetic tape drive - TK50 tape drive Disk Space Requirements (Block Cluster Size = 1): For OpenVMS VAX Systems: Disk space required for 72,000 blocks installation: (16 Mbytes) Disk space required for 30,000 blocks permanent use: (7.5 Mbytes) For ULTRIX Systems: Disk space required for 72,000 blocks installation: (16 Mbytes) Disk space required for 30,000 blocks permanent use: (7.5 Mbytes) These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. The space in- dicated for permanent occupancy does not include the space required to receive an upline dump if that facility is enabled. The amount of space required for dumps depends on the exact hardware configuration. This could be from 20,000 to 60,000 blocks (10 to 30 Mbytes) for each dump depending on the DECNIS configuration. 6 The DECNIS software requires either a DECNIS 500 or DECNIS 600 series hardware unit and one or more network interface cards. The following network interface cards occupy a single slot of the DECNIS enclosure and supported by the DECNIS 500/600 hardware units: o DEC LANcontroller 601 - Single-port Ethernet/IEEE 802.3 interface o DEC LANcontroller 602 - Dual-port Ethernet/IEEE 802.3 interface o DEC WANcontroller 614 - Four-port, low-speed serial interface sup- porting synchronous operation at line speeds from 1.2 Kbits/s to 128 Kbits/s or asynchronous operation at line speeds from 1.2 Kbits /s to 38.4 Kbits/s o DEC WANcontroller 618 - Eight-port, low-speed serial interface sup- porting synchronous operation at line speeds from 1.2 Kbits/s to 128 Kbits/s or asynchronous operation at line speeds from 1.2 Kbits /s to 38.4 Kbits/s o DEC WANcontroller 622 - Dual-port, high-speed serial interface sup- porting synchronous operation at line speeds from 9.6 Kbits/s to 2 Mbits/s The following network interface card occupies two slots of the DEC- NIS enclosure and is supported by the DECNIS 600 hardware unit only: o DEC FDDIcontroller 621 - Single-port FDDI interface, SAS or DAS Note that remote bridging is only supported when using the DEC WAN- controller 622 network interface card; it is not supported when us- ing the DEC WANcontroller 614 or 618 network interface card. Adapter Cables The DEC WANcontroller 614 and 622 require adapter cables to provide the necessary interchange circuits at the appropriate electrical in- terfaces and ISO standard connections for each serial line. One of these cables is needed for each line used. 7 When connecting to the British Telecom Kilostream service, the DEC WAN- controller 618 requires a special adapter cable to connect to the V.11 /RS422 distribution panel. For all other services, only a modem con- nection cable is required to connect the appropriate DEC WANcontroller 618 distribution panel. When connecting to the BT(R) Kilostream service using the DEC WANcontroller 614 or 622, the CCITT X.21 adapter cable should be used. Table 1 shows the cable numbers for each of the electrical interface types. The serial interfaces provide only the electrical interface of a DTE rather than a DCE, and do not provide clock signals. An exter- nal clock source (such as a modem) is required for each serial con- nection. ___________________________________________________________________ Table_1:___________________________________________________________ Electrical Adapter Connector Interface_Type______Cable______Pinout______________________________ CCITT V.28/V.24 BC23V- ISO 2110 (EIA-RS232-C/D) 02¹ CCITT V.36/X.27 BC19B-02 ISO 4902 (V.11, EIA-RS422 /449) CCITT V.35 BC19F-02 ISO 2593 CCITT X.21 (1980) BC19C-02 ISO 4903 (Leased services) BT Kilostream BC19C- ISO 4903 service 02² BT Kilostream BC21G- ISO 4903 service (WC618 02² only)______________________________________________________________ Notes: 8 1. This should be ordered as part BS23V-02, which contains not only the BC23V-02 adapter cable to provide the V.28/V.24 (RS232-D) in- terface, but also an adapter that allows it to be used for RS232- C as well. It is only supported with the DEC WANcontroller 614; it is not supported for use with the DEC WANcontroller 622. 2. The BC19C-02 adapter cable is used with a 50-way D-type connector with the DEC WANcontroller 614 when connecting to the BT Kilostream service or with the DEC WANcontroller 622 when connecting to the BT Kilostream service or CCITT X.21 leased line services. When con- necting the DEC WANcontroller 618 to use the BT Kilostream service, the BC21G-02 should be used in conjunction with the V.11/RS422 dis- tribution panel. T1 and G.703 Services When connecting the DEC WANcontroller 622 to a T1 or G.703 circuit, a CSU/DSU converter is required. Please contact your local Digital of- fice for a list of compatible CSU/DSU converters available in your coun- try. X.25 Public Networks Table 2 lists public PSDNs which the DECNIS software supports in cer- tain countries. Table 3 lists the X.25 optional facilities supported. ___________________________________________________________________ Table_2:_Public_PSDNs_Supported____________________________________ Country_____Public_Network_and_CCITT_Revisions_____________________ Argentina Arpac Australia Austpac Austria Datex-P Belgium DCS 9 ___________________________________________________________________ Country_____Public_Network_and_CCITT_Revisions_____________________ Brazil Renpac Canada Datapac (1976 or 1980) Faspac Infoswitch Chile VTRNET Denmark Datapak Ireland Eirpac (1980) Finland Datapak France Transpac Germany Datex-P Hong Kong Datapak Intelpak Indonesia SKDP Italy Itapac Japan DDX (1976, 1980) See Note 1 Venus-P (1980) TYMNET(R) Luxembourg LUXPAC Malaysia Maypac Mexico Telepac Netherlands Datanet 1 New Pacnet Zealand Norway Datapak Pakistan Paknet Philippines Datanet Portugal Telepac Singapore Telepac 10 ___________________________________________________________________ Country_____Public_Network_and_CCITT_Revisions_____________________ South Dacomnet Korea Spain Iberpac Sweden Datapak Switzerland Telepac (1978, 1980) Taiwan Pacnet United BT PSS Kingdom Mercury 500 United Accunet(R) States Autonet(R) Bell Atlantic CompuServe(R) ConnNet Digipac Fedexitc Graphnet Impacs Infonet Mark*Net Extended Service PPSNET Pulselink Telenet (US Sprint) TYMNET Western Union PTN-1 ____________Worldnet_______________________________________________ Note: 1. Digital offices in Japan can supply the mandatory additional in- formation that explains the special use of the DECNIS software with the DDX PSDN. 11 ___________________________________________________________________ Table_3:_Optional_X.25_Facilities_Supported_by_the_DECNIS_Software_ DECNIS Software _____Support_____ Para. in CCITT Optional_Facility_______________X.25(84)__________Connector____Relay 1. Extended packet sequence 6.2 Yes Yes numbering 2. Non-standard default window 6.10 Yes Yes size 3. Default throughput class 6.11 N/A See assignment Note 4 4. Packet retransmission 6.4 See Note 1 No 5. Incoming calls barred 6.5 N/A No 6. Outgoing calls barred 6.6 N/A No 7. One-way logical channel 6.7 N/A No outgoing 8. One-way logical channel 6.8 Yes Yes incoming 9. Closed User Group (CUG) 6.14.1 Yes See Note 4 10. CUG with outgoing access 6.14.2 Yes See Note 4 11. CUG with incoming access 6.14.3 Yes See Note 4 12. Incoming calls barred 6.14.4 Yes No within CUG 12 Table_3_(Cont.):_Optional_X.25_Facilities_Supported_by_the_DECNIS__ _________________Software__________________________________________ DECNIS Software _____Support_____ Para. in CCITT Optional_Facility_______________X.25(84)__________Connector____Relay 13. Outgoing calls barred 6.14.5 Yes No within CUG 14. CUG selection 6.14.6 Yes See Note 4 15. CUG with outgoing access 6.14.7 No See selection Note 4 16. Absence of both CUG selec- 6.14.8 Yes See tion facilities Note 4 17. Bilateral CUG 6.15.1 Yes See Note 4 18. Bilateral CUG with outgo- 6.15.2 Yes See ing access Note 4 19. Bilateral CUG selection 6.15.3 Yes See Note 4 20. Reverse charging 6.18 Yes See Note 4 21. Reverse charging accep- 6.19 Yes Yes tance 22. Local charge prevention 6.20 N/A No 13 Table_3_(Cont.):_Optional_X.25_Facilities_Supported_by_the_DECNIS__ _________________Software__________________________________________ DECNIS Software _____Support_____ Para. in CCITT Optional_Facility_______________X.25(84)__________Connector____Relay 23. Network user identifica- 6.21 Yes See tion Note 4 24. Charging information 6.22 Yes See Note 4 25. RPOA selection 6.23 Yes See Note 4 26. Hunt group 6.24 See Note 2 No 27. Call redirection 6.25 N/A No 28. Called line address modi- 6.26 Yes Yes fied notification 29. Call redirection notifica- 6.25.3 Yes See tion Note 4 30. Transit delay selection 6.27 Yes See and indication Note 4 31. Online facility registra- 6.1 No No tion 32. Non-standard packet size 6.9 Yes Yes 33. Flow control parameter 6.12 Yes Yes negotiation 34. Throughput class negotia- 6.13 Yes See tion Note 4 14 Table_3_(Cont.):_Optional_X.25_Facilities_Supported_by_the_DECNIS__ _________________Software__________________________________________ DECNIS Software _____Support_____ Para. in CCITT Optional_Facility_______________X.25(84)__________Connector____Relay 35. Fast select 6.16 Yes See Note 4 36. Fast select acceptance 6.17 Yes See Note 4 37. D-bit modification 6.3 No No 38. Abbreviated address - N/A N/A 39. Datagram queue length - No No selection 40. Datagram service signal - No No logical channel 41. Datagram nondelivery - No No indication 42. Datagram delivery confir- - No No mation 43._Call_statistics_(non-X.25)__-_________________See_Note_3___No__ Notes: 1. This is not applicable to a DTE. This product does not support the reception of a level 3 Reject packet, and will not generate one. 2. Each DTE must be assigned a unique address independent of the hunt group address. The DECNIS software can then ignore the hunt group. Alternatively, each line can be configured as if it were connected to a separate PSDN with each line having the same DTE address. In either case, all the lines must be connected to the same DECNIS soft- ware. 15 3. This product does not generate these statistics. However, an X.25 Client system can obtain statistics supplied by the PSDN through the programming interface. 4. The information contained in these fields is passed transparently and has only end-to-end significance. The DECNIS software does not support the following items of the CCITT X.25 recommendation: - Multi-link protocol - Use of the D-bit in outgoing packets Unless otherwise acknowledged within the product's documentation, the trademarks under which services are offered are proprietary to the re- spective national PTT, the owning or operating companies, or equiv- alent organization. Frame Relay Networks The DECNIS software fully supports the Frame Relay Specification with Extensions document Rev 1.0, September 18, 1990, as follows: o Section 4 is fully supported using either a V.35, X.21 (leased line), RS422, or RS449 physical interface. o Section 5 is fully supported. The frame length dN1 parameter is 1500 octets. o Section 6 is fully supported as user device equipment. The value of the Permanent Virtual Circuits (PVCs) nP1 parameter is 32 PVCs per physical port on the DEC WANcontroller 622 Network Interface Card. o Section 7 is fully supported as DTE equipment. The DECNIS software has been tested and is known to be compatible with the following Frame Relay devices: o StrataCom(R) IPX 16/32 with Frame Relay Interface Card Software V5.2 or later. 16 o Cascade Communications Corporation STDX 3000 and 6000 with V2.0.1 software or later. CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VAXcluster* configuration without restrictions. The HARD- WARE REQUIREMENTS sections of this product's Software Product Descrip- tion and System Support Addendum detail any special hardware required by this product. * V5.x VAXcluster configurations are fully described in the VAXclus- ter Software Product Description (29.78.xx) and include CI, Eth- ernet, and Mixed Interconnect configurations. SOFTWARE REQUIREMENTS The DECNIS software needs to be installed on a VAX-based system run- ning the OpenVMS operating system, or a RISC-based system running the ULTRIX operating system. Each OpenVMS VAX system acting as a load host or dump receiver requires: o OpenVMS VAX Operating System V5.4 - V5.5-2 o DECnet-VAX V5.4 - V5.5 with DECnet-VAX V5.4 Extensions kit installed or DECnet/OSI for OpenVMS VAX V5.5 Each RISC/ULTRIX system acting as a load host or dump receiver requires: o ULTRIX Operating System V4.2 - V4.3 or ULTRIX Worksystem Software V4.2 - V4.3A o DECnet/OSI for ULTRIX for RISC and VAX V5.1 (SPD 34.97.xx) Each PC acting as a load host requires: o PATHWORKS for DOS V4.1A or later (SPD 55.07.xx) 17 When using the DECNIS X.25 Gateway service, the following X.25 client systems are supported: o VAX P.S.I. Access V4.3 (SPD 27.78.xx) o DECnet-VAX V5.4 - V5.5 with DECnet-VAX V5.4 Extensions kit (SPD 29.03.xx) o DECnet/OSI for OpenVMS VAX V5.5 (SPD 25.03.xx) o DEC X.25 Gateway Client for ULTRIX V1.1 (SPD 32.34.xx) o DECnet/OSI Version 1.0 for DEC OSF/1 (SPD 41.92.xx) Note that when using X.25 Gateway services, access to a Digital Name Service (DNS) server is optional. GROWTH CONSIDERATIONS The minimum hardware requirements for any future version of this prod- uct may be different from the hardware requirements of the current ver- sion. DISTRIBUTION MEDIA 9-track 1600 BPI Magtape, TK50 Streaming Tape ORDERING INFORMATION The software license allows unrestricted use of the software on the DECNIS 500/600 series hardware unit on which the product is used. Software Licenses: DECNIS Router License: QL-GX7A9-AA DECNIS Bridge License: QL-GZNA9-AA DECNIS PCLAN License: QL-08VA9-AA The DECNIS Router License includes the use of IP, DECnet, and OSI rout- ing, and X.25 routing and gateway services provided by the DECNIS soft- ware. A DECNIS Bridge license is required for each DECNIS hardware unit run- ning local or remote bridging. 18 A DECNIS PCLAN license is required for each DECNIS hardware unit run- ning Novell(R) NetWare(R) and/or AppleTalk(R). Software Media for OpenVMS VAX Operating System: QA-GX7AA-H* Software Media for RISC/ULTRIX Operating System: QA-GX7AC-H* Software Documentation for OpenVMS and ULTRIX Operating Systems: QA- GX7AA-GZ Software Product Services: QT-GX7A*-** The software media kit includes a Bookreader version of the DECNIS Prob- lem Solving Guide. * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. The above information is valid at the time of release. Please contact your local Digital office for the most up-to-date information. (R) Accunet is a registered trademark of American Telephone and Telegraph Company. (R) Apple, AppleTalk, and EtherTalk are registered trademarks of Apple Computer, Inc. (R) Autonet is a registered trademark of Sanders Associates, Inc. (R) BT is a registered trademark of British Telecommunications plc. (R) CompuServe is a registered trademark of CompuServe, Inc. (R) Novell and NetWare are registered trademarks of Novell, Inc. (R) StrataCom is a registered trademark of StrataCom, Inc. (R) TYMNET is a registered trademark of McDonnell Douglas Corpora- tion. 19 (R) Xerox is a registered trademark of Xerox Corporation. [TM] The DIGITAL Logo, Bookreader, CI, DDCMP, DEC, DECmcc, DECnet, DECNIS, DECstation, DECsystem, Digital, DNA, MicroVAX, Open- VMS, PATHWORKS, TK, ULTRIX, VAX, VAXcluster, VAXft, VAXserver, VAXstation, and VT220 are trademarks of Digital Equipment Corporation. 20