| Previous | \Contents | ^Index |
F The following sections contain information on OpenVMS Networking with @ IP and DECnet, and on clustering and volume shadowing, on Fibre 4 Channel, and on related products and configurations. ] 15.1 How to connect OpenVMS to a Modem?
F Please see the Ask The Wizard area topics starting with (81), (1839), (2177), (3605), etc.
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9. V 15.2 OpenVMS and IP Networking?
= The following sections contain information on OpenVMS and IP * networking, as well as IP printing topics. J 15.2.1 How to connect OpenVMS to the Internet?
E Some tutorial information and tips for connecting OpenVMS systems to the Internet are available at:
AF To connect a printer via the IP telnet or lpr/lpd protocols, you will H need to install and configure an IP stack on OpenVMS, and configure the appropriate print queue.
A With current OpenVMS IP implementations, the choice of telnet or G lpr/lpd really amounts to determining which of these works better with the particular printer involved.
E To support network printing, the printer must include an internal or external E NIC or JetDirect; an adapter connecting the network and the printer.
E While it is normally possible to use a host-connected printer---when F the host supports an LPD or telnet daemon, and OpenVMS and most other F operating systems have the ability to serve locally-attached printers H to other hosts on the network---it is generally far easier and far more H effective to use a printer that is directly attached to the network. If D your present printer does not have a NIC or a JetDirect, acquire an E internal (if available) or external NIC or JetDirect. Or replace the E printer. And obviously, most any operating system that can serve its E local printers usually also provides a client that can access remote network-connected printers.
@ please see the Ask The Wizard area topics---starting with topic A (1020)---for additional information on IP-based network printing.
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9.
e Please see Section 15.2.3 for information on Postscript printing. U 15.2.3 How do I connect a PostScript printer via TCP/IP?
C Using TCP/IP Services (UCX) as the TCP/IP stack, it is possible to C configure queues using the UCX$TELNETSYM (TCP/IP Services prior to D V5.0) or TCPIP$TELNETSYM (with V5.0 and later) in order to print to F Postscript printers. This assumes however that the printer itself can D convert whatever is passed to it into something intelligible. As an F example, if the printer has an IP address of 123.456.789.101 and jobs $ should be passed to port 9100 then :
|
" / $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" - /PROCESSOR=UCX$TELNETSYM - my_ip_queue |
|
" / $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" - " /PROCESSOR=TCPIP$TELNETSYM - my_ip_queue |
D The port number of 9100 is typical of HP JetDirect cards but may be ( different for other manufacturers cards.
F As a better alternative, DCPS Version 1.4 and later support IP queues H using either HP TCP/IP Services for OpenVMS software or Process Software Multinet G for OpenVMS. The usage of this type of interface is documented in the D DCPS documentation or release notes, and the DCPS$STARTUP.TEMPLATE startup template file.
E For general and additional (non-Postscript) IP printing information, B please see topic (1020) and other topics referenced in that topic ) elsewhere within the Ask The Wizard area.
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9. Also see:
n Please see Section 15.2.2 for pointers to an introduction to IP printing. [ 15.2.4 How do I set a default IP route or gateway on OpenVMS?
F If you have TCP/IP Services, then use the command for TCP/IP Services V5.0 and later:
|
" $ TCPIP ) SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT |
: And for earlier TCP/IP Services versions, use the command:
|
" $ UCX ) SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT |
F Though it may seem obvious, Telnet and LAT are quite different---with ( differing capabilities and design goals.
D Please see the documentation around the TCP/IP Services for OpenVMS E TELNET command CREATE_SESSION. This command is the equivilent of the E operations performed in LTLOAD.COM or LAT$SYSTARTUP.COM. There is no G TELNET equivilent to the sys$qio[w] control interface for LTDRIVER (as A documented in the I/O User's Reference Manual) available, though B standard sys$qio[w] calls referencing the created TN device would likely operate as expected. \ 15.2.6 Why can't I use PPP and RAS to connect to OpenVMS Alpha?
H OpenVMS Alpha IP PPP does not presently support authentication, and the C Microsoft Windows NT option to disable authentication during a RAS D connection apparently doesn't currently work---RAS connections will D require authentication---and this will thus prevent RAS connections.
H Future versions of OpenVMS and TCP/IP Services may add this, and future H versions of Microsoft Windows may permit operations with authentication disabled. ^ 15.3 OpenVMS and DECnet Networking?
A The following sections contain information on OpenVMS and DECnet networking. E 15.3.1 Can DECnet-Plus operate over IP?
G Yes. To configure DECnet-Plus to operate over IP transport and over IP F backbone networks, install and configure DECnet-Plus, and install and configure the PWIP E mechanism available within the currently-installed IP stack. Within G TCP/IP Services, this is a PWIPDRIVER configuration option within the D UCX$CONFIG (versions prior to V5.0) or TCPIP$CONFIG (with V5.0 and later) configuration tool. _ 15.3.2 What does "failure on back translate address request" mean?
The error message:
|
" ; BCKTRNSFAIL, failure on the back translate address request |
E indicates that the destination node is running DECnet-Plus, and that B its naming service (DECnet-Plus DECdns, LOCAL node database, etc) E cannot locate a name to associate with the source node's address. In E other words, the destination node cannot determine the node name for 7 the node that is the source of the incoming connection.
H Use the DECNET_REGISTER mechanism (on the destination node) to register H or modify the name(s) and the address(es) of the source node. Check the & namespace on the source node, as well.
H Typically, the nodes involved are using a LOCAL namespace, and the node H name and address settings are not coherent across all nodes. Also check D to make sure that the node is entered into its own LOCAL namespace. ? This can be a problem elsewhere, however. Very rarely, a cache G corruption has been known to cause this error. To flush the cache, use the command:
|
" $ RUN SYS$SYSTEM:NCL - flush session control naming cache entry "*" |
H Also check to see that you are using the latest ECO for DECnet-Plus for ? the version you are running. DECnet-Plus can use the following namespaces:
G Of these, searching DNS/BIND and LocalFile, respectively, is often the most appropriate configuration. L 15.3.3 Performing SET HOST/MOP in DECnet-Plus?
/ First, issue the NCL command SHOW MOP CIRCUIT *
|
" $ RUN SYS$SYSTEM:NCL SHOW MOP CIRCUIT * |
E Assume that you have a circuit known as FDDI-0 displayed. Here is an E example of the SET HOST/MOP command syntax utilized for this circuit:
|
" 8 $ SET HOST/MOP/ADDRESS=08-00-2B-2C-5A-23/CIRCUIT=FDDI-0 |
= Also see Section 15.6.3. j 15.4 How to determine the network hardware address?
E Most Alpha and most VAX systems have a console command that displays D the network hardware address. Many systems will also have a sticker C identifying the address, either on the enclosure or on the network controller itself.
B The system console power-up messages on a number of VAX and Alpha A systems will display the hardware address, particularly on those < systems with an integrated Ethernet network adapter present.
D If you cannot locate a sticker on the system, if the system powerup C message is unavailable or does not display the address, and if the @ system is at the console prompt, start with the console command:
|
" HELP |
G A console command similar to one of the following is typically used to display the hardware address:
|
" SHOW DEVICE SHOW ETHERNET SHOW CONFIG |
F On the oldest VAX Q-bus systems, the following console command can be @ used to read the address directly off the (DELQA, DESQA, or the ; not-supported-in-V5.5-and-later DEQNA) Ethernet controller:
|
" E/P/W/N:5 20001920 |
F Look at the low byte of the six words displayed by the above command. H (The oldest VAX Q-bus systems---such as the KA630 processor module used B on the MicroVAX II and VAXstation II series---lack a console HELP > command, and these systems typically have the primary network H controller installed such that the hardware address value is located at & the system physical address 20001920.)
H If the system is a VAX system, and another VAX system on the network is ? configured to answer Maintenance and Operations Protocol (MOP) E bootstrap requests (via DECnet Phase IV, DECnet-Plus, or LANCP), the / MOM$SYSTEM:READ_ADDR.EXE tool can be requested:
|
" B/R5:100 ddcu Bootfile: READ_ADDR |
H Where ddcu is the name of the Ethernet controller in the above command. A The primarly local DELQA, DESQA, and DEQNA Q-bus controllers are E usually named XQA0. An attempt to MOP download the READ_ADDR program G will ensue, and (if the download is successful) READ_ADDR will display the hardware address.
F If the system is running, you can use DECnet or TCP/IP to display the 4 hardware address with one of the following commands.
|
" $! DECnet Phase IV $ RUN SYS$SYSTEM:NCP SHOW KNOWN LINE CHARACTERISTICS |
|
" $! DECnet-Plus $ RUN SYS$SYSTEM:NCL " SHOW CSMA-CD STATION * ALL STATUS |
|
" ! $! TCP/IP versions prior to V5.0 $ UCX SHOW INTERFACE/FULL |
|
" " $! TCP/IP versions V5.0 and later $ TCPIP SHOW INTERFACE/FULL |
F A program can be created to display the hardware address, reading the B necessary information from the network device drivers. A complete A example C program for reading the Ethernet or IEEE 802.3 network F controller hardware address (via sys$qio calls to the OpenVMS network 4 device driver(s)) is available at the following URL:
D To use the DECnet Phase IV configurator tool to watch for MOP SYSID # activity on the local area network:
|
" $ RUN SYS$SYSTEM:NCP ; SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLED |
F Let the DECnet Phase IV configurator run for at least 20 minutes, and 5 preferably longer. Then issue the following commands:
|
" $ RUN SYS$SYSTEM:NCP > SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txt < SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED |
D The resulting file (named filename.txt) can now be searched for the E information of interest. Most DECnet systems will generate MOP SYSID G messages identifying items such as the controller hardware address and D the controller type, and these messages are generated and multicast roughly every ten minutes.
D Information on the DECnet MOP SYSID messages and other parts of the E maintenance protocols is included in the DECnet network architecture * specifications referenced in section DOC9. ] 15.4.1 How do I reset the LAN (DECnet-Plus NCL) error counters?
On recent OpenVMS releases:
|
" $ RUN SYS$SYSTEM:LANCP 3 SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devname |
B On OpenVMS V7.1, all DECnet binaries were relocated into separate @ installation kits---you can selectively install the appropriate F network: DECnet-Plus (formerly known as DECnet OSI), DECnet Phase IV, , and HP TCP/IP Services (often known as UCX).
G On OpenVMS versions prior to V7.1, DECnet Phase IV was integrated, and G there was no installation question. You had to install the DECnet-Plus A (DECnet/OSI) package on the system, after the OpenVMS upgrade or installation completed.
A During an OpenVMS V7.1 installation or upgrade, the installation F procedure will query you to learn if DECnet-Plus should be installed. G If you are upgrading to V7.1 from an earlier release or are installing H V7.1 from a distribution kit, simply answer "NO" to the question asking A you if you want DECnet-Plus. Then---after the OpenVMS upgrade or B installation completes -- use the PCSI PRODUCT INSTALL command to B install the DECnet Phase IV binaries from the kit provided on the " OpenVMS software distribution kit.
G If you already have DECnet-Plus installed and wish to revert, you must E reconfigure OpenVMS. You cannot reconfigure the "live" system, hence D you must reboot the system using the V7.1 distribution CD-ROM. Then < select the DCL ($$$ prompt) option. Then issue the commands:
|
" ' $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0: - $$$ DEFINE/SYSTEM PCSI$SPECIFIC DKA0:[SYS0.] = $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON] |
H The above commands assume that the target system device and system root B are "DKA0:[SYS0.]". Replace this with the actual target C device and root, as appropriate. The RECONFIGURE command will then H issue a series of prompts. You will want to reconfigure DECnet-Plus off B the system, obviously. You will then want to use the PCSI command D PRODUCT INSTALL to install the DECnet Phase IV kit from the OpenVMS distribution media.
H Information on DECnet support, and on the kit names, is included in the 4 OpenVMS V7.1 installation and upgrade documentation.
H Subsequent OpenVMS upgrade and installation procedures can and do offer 3 both DECnet Phase IV and DECnet-Plus installations. q 15.5 How can I send (radio) pages from my OpenVMS system?
C There are third-party products available to send messages to radio E paging devices (pagers), communicating via various protocols such as 7 TAP (Telocator Alphanumeric Protocol); paging packages.
RamPage (Ergonomic Solutions) @ is one of the available packages that can generate and transmit E messages to radio pagers. Target Alert (Target Systems; formerly the DECalert product) is another. = Networking Dynamics Corp has a product called Pager Plus. The A System Watchdog package can also send pages. The Process Software H package PMDF can route specific email addresses to a paging service, as well.
D Many commercial paging services provide email contact addresses for G their paging customers---you can simply send or forward email directly + to the email address assigned to the pager.
F Some people implement the sending of pages to radio pagers by sending E commands to a modem to take the "phone" off the "hook", and then the F paging sequence, followed by a delay, and then the same number that a ? human would dial to send a numeric page. (This is not entirely H reliable, as the modem lacks "call progress detection", and the program E could simply send the dial sequence when not really connected to the 3 paging company's telephone-based dial-up receiver.)
j See Section 13.1 for information on the available catalog of products. f 15.6 OpenVMS, Clusters, Volume Shadowing?
D The following sections contain information on OpenVMS and Clusters, 8 Volume Shadowing, and Cluster-related system parameters. U 15.6.1 OpenVMS Cluster Communications Protocol Details?
A The following sections contain information on the OpenVMS System ' Communications Services (SCS) Protocol. S 15.6.1.1 OpenVMS Cluster (SCS) over DECnet? Over IP?
> The OpenVMS Cluster environment operates over various network E protocols, but the core of clustering uses the System Communications E Services (SCS) protocols, and SCS-specific network datagrams. Direct (full) connectivity is assumed.
F An OpenVMS Cluster does not operate over DECnet, nor over IP.
& No SCS protocol routers are available.
C Many folks have suggested operating SCS over DECnet or IP over the C years, but SCS is too far down in the layers, and any such project H would entail a major or complete rewrite of SCS and of the DECnet or IP G drivers. Further, the current DECnet and IP implementations have large E tracts of code that operate at the application level, while SCS must @ operate in the rather more primitive contexts of the system and G particularly the bootstrap---to get SCS to operate over a DECnet or IP G connection would require relocating major portions of the DECnet or IP G stack into the kernel. (And it is not clear that the result would even - meet the bandwidth and latency expectations.)
A The usual approach for multi-site OpenVMS Cluster configurations H involves FDDI, Memory Channel (MC2), or a point-to-point remote bridge, D brouter, or switch. The connection must be transparent, and it must C operate at 10 megabits per second or better (Ethernet speed), with G latency characteristics similar to that of Ethernet or better. Various 4 sites use FDDI, MC2, ATM, or point-to-point T3 link. W 15.6.1.2 Configuring Cluster SCS for path load balancing?
? This section discusses OpenVMS Cluster communications, cluster C terminology, related utilities, and command and control interfaces. D 15.6.1.2.1 Cluster Terminology?
F SCS: Systems Communication Services. The protocol used to communicate E between VMSCluster systems and between OpenVMS systems and SCS-based E storage controllers. (SCSI-based storage controllers do not use SCS.)
H PORT: A communications device, such as DSSI, CI, Ethernet or FDDI. Each F CI or DSSI bus is a different local port, named PAA0, PAB0, PAC0 etc. 8 All Ethernet and FDDI busses make up a single PEA0 port.
F VIRTUAL CIRCUIT: A reliable communications path established between a G pair of ports. Each port in a VMScluster establishes a virtual circuit & with every other port in that cluster.
D All systems and storage controllers establish "Virtual Circuits" to ; enable communications between all available pairs of ports.
F SYSAP: A "system application" that communicates using SCS. Each SYSAP D communicates with a particular remote SYSAP. Example SYSAPs include:
( VMS$DISK_CL_DRIVER connects to MSCP$DISK
E The disk class driver is on every VMSCluster system. MSCP$DISK is on A all disk controllers and all VMSCluster systems that have SYSGEN parameter MSCP_LOAD set to 1
( VMS$TAPE_CL_DRIVER connects to MSCP$TAPE
E The tape class driver is on every VMSCluster system. MSCP$TAPE is on A all tape controllers and all VMSCluster systems that have SYSGEN parameter TMSCP_LOAD set to 1
) VMS$VAXCLUSTER connects to VMS$VAXCLUSTER
B This SYSAP contains the connection manager, which manages cluster ? connectivity, runs the cluster state transition algorithm, and F implements the cluster quorum algorithm. This SYSAP also handles lock < traffic, and various other cluster communications functions.
( SCS$DIR_LOOKUP connects to SCS$DIRECTORY
3 This SYSAP is used to find SYSAPs on remote systems
MSCP and TMSCP
G The Mass Storage Control Protocol and the Tape MSCP servers are SYSAPs G that provide access to disk and tape storage, typically operating over G SCS protocols. MSCP and TMSCP SYSAPs exist within OpenVMS (for OpenVMS B hosts serving disks and tapes), within CI- and DSSI-based storage G controllers, and within host-based MSCP- or TMSCP storage controllers. H MSCP and TMSCP can be used to serve MSCP and TMSCP storage devices, and D can also be used to serve SCSI and other non-MSCP/non-TMSCP storage devices.
E SCS CONNECTION: A SYSAP on one node establishes an SCS connection to D its counterpart on another node. This connection will be on ONE AND + ONLY ONE of the available virtual circuits.
| Previous | YNext | \Contents | ^Index |