![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Specifically, the guidelines for the software on the OpenVMS Freeware CD-ROM are as follows:
The original OpenVMS Internet Product Suite, which debuted in September 1996, provided the opportunity to turn existing OpenVMS VAX or Alpha systems into high performance, highly-available web servers and browsers. Version 1.1 of this product, which is available with OpenVMS Version 7.1, adds the following new components: the Netscape Communications and Commerce servers and an enhanced Purveyor Encrypt web server. This comprehensive and conveniently packaged portfolio of third-party and Digital products gives you an expanded choice of Internet tools to meet your business needs.
Digital's portfolio of OpenVMS Internet products offers you a choice of the commercial HyperText Transport Protocol (HTTP) web servers described in the following sections.
Netscape Communications Server
The Netscape Communications Server Version 1.12 enables you to publish hypermedia documents using the HyperText Markup Language (HTML) on the Internet and internal TCP/IP-based networks (intranet) using HTTP. The server's compatibility with network standards and document formats makes it easy to integrate with other applications and systems in your enterprise.
The easy-to-use graphical user interface (GUI) makes installation, configuration, and management simple and fast. And, it supports industry-standard multimedia document formats for the presentation of rich text, graphics, audio, and video.
Easy-to-navigate hyperlinks connect related information across the network, creating a seamless web that lets you share product information, corporate news, and customer support and service information.
Netscape Commerce Server
The Netscape Commerce Server Version 1.12 provides secure electronic commerce and communications on the Internet and intranets. The Netscape Commerce Server lets you publish hypermedia documents using HTML and deliver them over the Internet and other TCP/IP networks using HTTP. To ensure data security, Netscape Commerce Server provides advanced security features such as server authentication, data encryption, data integrity, and user authorization. Communications are based on open standards including HTML, HTTP, the Common Gateway Interface (CGI), and the Secure Sockets Layer (SSL) protocol.
Purveyor Encrypt WebServer for OpenVMS
The Purveyor Encrypt WebServer for OpenVMS Version 1.2 replaces the original Purveyor WebServer packaged in the first version of the OpenVMS Internet Product Suite. Purveyor Encrypt WebServer combines the reliability, security and scalability of the OpenVMS platform with the graphical ease-of-use and functionality of World Wide Web technologies. Purveyor Encrypt lets you easily web-enable your existing OpenVMS applications, develop a corporate intranet, or create a robust external Web presence all within a secure web environment.
Using Secure Sockets Layer (SSL) encryption and authentication, Purveyor Encrypt ensures the security of access, traffic and requests made to web-enabled OpenVMS systems, which typically house mission-critical data. Purveyor WebServer will also run without encryption services, eliminating unnecessary network overhead.
Purveyor Encrypt runs over TCP/IP for OpenVMS or any other TCP/IP for OpenVMS implementation and can be configured to run in a clustered environment for high availability. Other features include:
Table 2-1 lists and describes the products, tools, and utilities available in the OpenVMS Internet Product Suite. For more detailed information, see the online documentation that accompanies the individual products in the OpenVMS Internet Product Suite.
The Point-to-Point Protocol (PPP) is an internet layer protocol which is now the widely accepted replacement for the Serial Line Interconnect Protocol (SLIP). PPP support enhances the connectivity and Internet capabilities of OpenVMS Alpha by providing a way to establish a dynamic Internet Protocol (IP) network connection over a serial line --- without extensive router or server hardware.
Based on code originated at Carnegie Mellon University, this serial protocol features:
To support this protocol, OpenVMS Alpha Version 7.1 offers a Point-to-Point Protocol utility (PPPD) and related device driver described in the following sections.
Point-to-Point Protocol Utility
The Point-to-Point Protocol utility (PPPD) is a DCL-level tool that you can use to initiate and manage an IP network connection over an asynchronous, serial data line. PPPD extends the networking capability of OpenVMS Alpha by enabling you to:
Refer to the TCP/IP Networking on OpenVMS Systems for a detailed description of this utility and its related subcommands. Sample PPPD connection procedures are also provided online in an ASCII (.TXT) and PostScript (.PS) file. Once you install the OpenVMS Alpha Version 7.1 kit, you can retrieve either file from the following location:
SYS$SYSROOT:[SYSHLP.EXAMPLES.PPPD.DOC]PPP_CONNECT.TXT (or .PS)
Note
The Point-to-Point Protocol utility (PPPD) included with OpenVMS Alpha Version 7.1 provides point-to-point networking capability to the base operating system. However, for this utility to be fully functional, your current TCP/IP vendor must also develop and integrate the appropriate callback images into their Internet Protocol (IP) stack.The Digital TCP/IP Services for OpenVMS team is currently integrating these images into the next version of their product. Digital is also working in tandem with our third-party TCP/IP vendors to provide this functionality; contact your individual TCP/IP vendor for more details.
Point-to-Point Protocol Driver
OpenVMS Alpha Version 7.1 includes a new device driver which provides support for PPP connection management, a state engine, and the link negotiation code. This driver interfaces with the upper layers of the network through the VMS Communications Interface (VCI).
Information about the PPP driver is provided online in both ASCII (.TXT) and PostScript formats (.PS). Once you install the OpenVMS Alpha Version 7.1 kit, you can retrieve either file from the following location:
SYS$SYSROOT:[SYSHLP.EXAMPLES.PPPD.DOC]PPP_INTERFACES.TXT (or .PS)
This chapter provides information about new features, changes, and enhancements for system managers.
OpenVMS Alpha Version 7.1 supports and manages with the LANCP utility the following networking features:
Table 3-1 shows the ATM devices supported by OpenVMS Version 7.1.
| LAN | Device Examples | Description |
|---|---|---|
| ATM | ATMWORKS 350, ATMWORKS 750 | The ATMWORKS 350 supports PCI-based systems. The ATMWORKS 750 supports TURBOchannel systems. |
OpenVMS Version 7.1 supports the standards defined by the ATM Forum's LANE Version 1.0 specifications for LAN emulation over an ATM network. By implementing an emulated LAN over an ATM network, you enable a group of ATM stations to act like a traditional LAN. LAN emulated over an ATM network allows you to run your existing applications basically unchanged, while the computers on which your applications are running are connected to the ATM network.
Digital implements only the LAN emulation client (LEC) and does not implement the LAN emulation server (LES), or the Broadcast and Unknown server (BUS). The LES and BUS servers must be provided by some other facility such as Digital's GIGAswitch/ATM.
Table 3-2 shows the characteristics of LAN emulation over ATM media.
| Characteristics | Description |
|---|---|
| Speed | 155 Mb/s |
| Max. frame size | 1516, 4544, and 9234 |
| Max. stations | LAN server determines number of stations supported |
| Max. LAN size | Unrestricted |
OpenVMS Alpha Version 7.1 implements the standards defined in RFC 1577 (Classical IP over ATM). This implementation introduces the necessary system interface for Classical IP (CLIP) over an ATM network, and enables IP and Address Resolution Protocols (ARPs) in an ATM network environment to be configured as a logical IP subnetwork (LIS). Consult your IP product documentation for the status of support of IP over this interface.
Section 3.1.3 describes the LANCP commands to manage LAN emulation over an ATM network. Section 3.1.4 describes the commands to manage CLIP over an ATM network.
LAN emulation over an ATM network is managed by using special LANCP command qualifiers. These qualifiers are presented in the following sections.
Table 3-3 shows the LAN emulation qualifiers for the DEFINE DEVICE command.
| Qualifier | Description |
|---|---|
| /ATMADDRESS |
On Alpha systems, defines the LAN emulation server (LES) address for
asynchronous transfer mode (ATM). Usually the address is not user
specified, and this qualifier is used only if you want a specific
address. By default, the address is determined by software from the
configuration server for the LES. The /ATMADDRESS qualifier's syntax is
as follows:
DEFINE DEVICE/ATMADDRESS=([NO]LES=the ATM address)
|
| /DLL | Same as the /MOPDLL qualifier. |
| /ELAN |
The /ELAN qualifier controls the state of the LAN emulation and has two
values: enable and disable. With /ELAN=ENABLE and the keyword STARTUP,
the LAN emulation is loaded when LANCP starts. With /ELAN=DISABLE, the
same parameters as ENABLE can be used. The /ELAN qualifier's syntax is
as follows:
DEFINE DEVICE/ELAN=(...
|
| /ELAN (continued) |
The meanings for the syntax for /ELAN are as follows:
|
Keywords and their meanings for /ELAN are as follows:
|
|
| /MOPDLL=( option) |
Provides the MOP downline load service settings for the device.
With this qualifier, you can specify:
|
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
Table 3-4 shows the qualifiers for the LANCP LIST DEVICE command that support LAN emulation.
| Qualifier | Description |
|---|---|
| /ALL | Lists all devices that match device names. |
| /CHARACTERISTICS | Same as the /PARAMETERS qualifier. |
| /DLL | Same as the DEFINE DEVICE/MOPDLL qualifier. Lists downline load characteristics. |
| /PARAMETERS | Displays status and related information about the device. |
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
Table 3-5 shows the qualifiers for the LANCP SET DEVICE command that support LAN emulation.
| Qualifier | Description |
|---|---|
| /ATMADDRESS |
On Alpha systems, sets the LAN emulation server (LES) address for
asynchronous transfer mode (ATM). Usually the address is not user
specified, and this qualifier is used only if you want a specific
address. By default the address is determined by software from the
configuration server for the LES. The /ATMADDRESS qualifier's syntax is
as follows:
SET DEVICE/ATMADDRESS=([NO]LES=the ATM server)
|
| /DLL | Same as the DEFINE DEVICE/MOPDLL qualifier. |
| /ELAN |
Sets LAN emulation parameters. The /ELAN qualifier's syntax is as
follows:
SET DEVICE/ELAN=(...
|
The meanings for the syntax for /ELAN are as follows:
|
|
| /ELAN (continued) |
Keywords and their meanings for /ELAN are as follows:
|
| /PERMANENT | Reads the permanent database and creates device entries in the volatile database. |
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
Table 3-6 shows the LAN emulation qualifiers for the SHOW DEVICE command.
| Qualifier | Description |
|---|---|
| /ALL | Shows all devices that match device names. |
| /CHARACTERISTICS | Same as the /PARAMETERS qualifier. |
| /DLL | Same as the DEFINE DEVICE/MOPDLL qualifier. It shows downline load characteristics. |
| /PARAMETERS | Displays status and related information about the device. |
6480P001.HTM OSSG Documentation 5-DEC-1996 13:49:04.39
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.