Installing the ATMworks 350 Digital UNIX 3.2C (or later) Driver
---------------------------------------------------------------

CONTENTS
--------

Chapter 1: ATMworks 350 Features and System Requirements
	   1.1 ATM Overview
	   1.2 Features Supported With Digital UNIX 3.2C or Later
	   1.3 System Requirements

Chapter 2: Installation and Support
	   2.1 International Technical Support
	   2.2 Accessing MIBs and RFCs
	   2.3 Loading and Viewing Distribution Diskettes
	   2.4 Software Installation

Chapter 3: Verifying and Troubleshooting the ATMworks 350
	   3.1 Testing and Verifying the NIC
	   3.2 Verifying the ATMworks 350 Configuration
	   3.3 Troubleshooting the ATMworks 350

Chapter 4: Managing the Network
	   4.1 Configuring the ATMworks 350
	   4.2 Configuring an ATM Subsystem
	    

Chapter 1: ATMWorks 350 Features and System Requirements  
--------------------------------------------------------

1.1 ATM Overview

	Refer to the INFO.TXT for details about where to 
	access more ATM information.  This file is on diskette 1 of the
	diskette kit that accompanies the ATMworks 350 NIC.

1.2 Features Supported with Digital UNIX 3.2C or Later

	Classical IP over ATM per RFC 1577.
	Permanent Virtual Circuits (PVCs).
	Switched Virtual Circuits (SVCs).
	Q.93B signaling.
	ATM UNI 3.0.
	IP encapsulation per RFC 1483.
	Class of service UBR.
	FLOWmaster(TM) flow control.
	Supports ATM Adaptation Layer 5 (AAL5). 
	Full-duplex operation.
	2048 virtual channels to receive and 2048 channels to transmit.

1.3 System Requirements:

	Unused PCI bus master full-size slot.
	Rev 2.0 PCI compliant system.
	Operating system version is Digital UNIX 3.2C or later.
	AlphaStations and AlphaServers.
	Console code revision meeting the following requirements.

	  Console Code Revision (minimum required to support ATMworks 350):

	  AlphaServer 1000                        V5.0 *
	  AlphaServer 2000			  V4.1 *
	  AlphaServer 2100			  V4.1 *
	  AlphaServer 8200			  V2.0 *
	  AlphaServer 8400			  V2.0 *
	  AlphaStation 200			  V4.2
	  AlphaStation 250			  V4.2
	  AlphaStation 400			  V4.2
	  AlphaStation 600			  V4.1

          * A full qualification has not been completed on these
	    servers with Digital Unix 3.2c.  Digital cannot
	    guarantee that the ATMworks 350 will work with other
	    untested PCI options.



Chapter 2: Installation and Support  
-----------------------------------

2.1 International Technical Support

	Refer to the INFO.TXT file for a detailed list of contacts.

2.2 Accessing MIBs and RFCs:

	Refer to the INFO.TXT file for details about how to access this
	information.

2.3 Loading and Viewing Distribution Diskettes:

	Insert the appropriate diskette into the 3 1/2" floppy drive bay.
	Each diskette contains a README.TXT file that lists the file
	structure and files on the diskette.  It is recommended that 
	each README.TXT file is printed, along with the INFO.TXT file
	that resides on diskette 1.  

	To view the README.TXT file, you can use a text editor installed
	on your system or the following procedure:

	  MORE < README.TXT

	The text output pauses at the end of each full screen.  The text
	output resumes when you press ENTER.  To stop viewing the 
	README.TXT file, press CTRL-C.

2.4 Software Installation

	Refer to the Digital UNIX kit for instructions about how to install
	or update the UNIX software to support the ATMworks 350.




Chapter 3: Verifying and Troubleshooting the ATMworks 350 
---------------------------------------------------------
	
3.1 Testing and Verifying the NIC

	LEDs located on the ATMworks 350's front panel indicate the operational
	status of the ATMworks 350 and its connection to the network. LED
	status will vary, depending upon the version of Digital UNIX 
	software that the system is running.

3.1.1 Digital UNIX V3.2C (Platinum-Lite)

	The following table shows the ATMworks 350's LED states and their
	meaning when using Digital UNIX V3.2C software. At power-up,
	both the module LED and network link LEDs are off. During the
	system boot, LED status appears as follows:

	_________________________________________________________________
	LED	Status    Meaning     Reference
	_________________________________________________________________
	Network	ON (yel-  Module is   Section 3.2, Verifying the ATMworks
	LED    	low),     correctly   350 Configuration
        	stays     configured
        	lit

	Network	OFF       Module      Section 3.3, Troubleshooting the
	LED        	  is not      ATMworks 350
        	          configured

	Network	blinking  Module      Section 3.3, Troubleshooting the
	LED               is not      ATMworks 350
     			  configured
	_________________________________________________________________


	   ___________________________Note ___________________________
	
	   To verify a PVC or SVC network connection, use Digital
	   UNIX commands. There is no LED state to verify that a
	   successful network connection has been made.

	   ___________________________________________________________


3.1.2 Digital UNIX V4.0 (Platinum)

	The following table shows the ATMworks 350's LED states and their
	meaning when using Digital UNIX V4.0 software.

	________________________________________________________________
	LED	Status    Meaning   Reference
	________________________________________________________________

	Module  ON        Module    Section 3.2, Verifying the ATMworks
        	          is con-   350 Configuration
                	  figured

	Module  OFF       Module    Section 3.3, Troubleshooting the
        	          is not    ATMworks 350
                	  cor-
	                  rectly
	                  config-
	                  ured

	Network Steady    Link is   Section 3.3, Troubleshooting the
	LED     ON        avail-    ATMworks 350
        	          able

	Network OFF       Link is   Section 3.2, Verifying the ATMworks
	LED               unavail-  350 Configuration
        		  able
	________________________________________________________________


3.2 Verifying the ATMworks 350 Configuration

	After the system powers up and gets to the boot prompt you should verify
	that the ATMworks 350 is correctly configured and recognized by the
	system unit. To display the ATMworks 350 information at the console,
	type the following:

	show config

3.3 Troubleshooting the ATMworks 350

	To begin troubleshooting the ATMworks 350 installation and configu-
	ration, check the module LED status. If the module LED is off
	or the configuration display indicates a problem, perform the
	following steps:

	________________________________________________________________
	Step Action
	________________________________________________________________

	1    Power down the system unit.

	2    Check to ensure that the ATMworks 350 is correctly seated. 
	     See "ATMworks 350 Installation and Service" for further 
             information.

	3    Check the SC connectors.

	4    Run diagnostics on all components in the system to
	     determine if the problem is a system problem or an ATMworks
	     350 problem.
	________________________________________________________________

	If a problem persists, contact your Digital Services repre-
	sentative.  Refer to INFO.TXT for further details.



Chapter 4: Managing the Network 
-------------------------------

	This chapter describes how to configure and manage an ATM
	subsystem for a Classical IP network running Digital UNIX.

4.1 Configuring the ATMworks 350

	To verify that the ATMworks 350 is properly installed and configured,
	perform the following steps:

	________________________________________________________________
	Step Action           Command
	________________________________________________________________

	1    Verify ATMworks  netstat -in
	     350 installation

	2    Initiate         atmconfig up driver=driver_name (where
   	     network contact  driver_name uses the format of ltax, and x
                              is 0, 1, 2, etc.)

	3    Configure        ifconfig lis0 <ip_addr> netmask <netmask>
	     the network
	     interface
	     (Digital UNIX
	     V3.2C only
	     supports a
	     single LIS.)
	________________________________________________________________

4.2 Configuring an ATM Subsystem

	The Digital UNIX (V3.2C) supports end-station to end-station
	connections over ATM, it does not support point-to-point
	connections.

	To set up a PVC for a Classical IP network, perform the following
	steps (steps 3 and 4 are only necessary if the local host never
	receives a response to its InARP request):

	________________________________________________________________
	Step Action           Command
	________________________________________________________________

	1    Create a         Refer to the ATM switch documentation.
	     network PVC

	2    Create a         atmconfig +pvc driver=driver_name
	     workstation      converge=atmip vpi=0 vci=#
	     PVC

	3    Map the IP       atmarp -s atm_address ip_address permanent
	     address to the
	     ATM address

	4    Map the IP       atmarp -v +vc vpi_number vci_number ip_
	     address to the   address
	     VCI
	________________________________________________________________

	To set up an SVC for a Classical IP network, one node is set as 
	the ARP server.  All other nodes on the same LIS are set as ARP
	clients.  SVCs are set up automatically when an IP connection is
	established, for example, using ping or ftp.

	________________________________________________________________
	Step Action           Command
	________________________________________________________________

	1    Set the node     atmarp -h client server_atm_address server_
	     as an ARP        ip_address
	     client           
	                      
	2    Set the node     atmarp -h server
	     as an ARP 
	     server

	________________________________________________________________

4.2.1 atmconfig

	Use the atmconfig command to configure an ATM subsystem and
	display information about that subsystem.

	Use atmconfig setup and status commands to:

	o  Create and destroy PVCs, and destroy SVCs.

	o  Enable and disable device drivers.

	o  Display currently active VCs and driver status.

	The format for the atmconfig command is always the command name
	followed by a single command, followed by optional arguments.
	Each atmconfig command uses a different set of arguments.
	Arguments are specified as follows:

	argument_name=argument value

	Arguments can appear in any order after the command. All
	required arguments must be specified.

4.2.1.1	atmconfig Setup Commands:

	To create PVCs, type:

	/usr/sbin/atmconfig +pvc driver=driver_name converge=name vpi=vpi_value
	vci=vci_value [selector=selector_value]

	To destroy PVCs and destroy SVCs, type:

	/usr/sbin/atmconfig {-pvc | -vc} {driver=driver_name vpi=vpi_value
	vci=vci_value } | vcid=VC_identifier

	The following table lists the arguments and definitions:

	________________________________________________________________
	Argument    Description
	________________________________________________________________

	+pvc        Creates and enables a new PVC and attaches it to a
	            convergence module specified in the converge=name
	            argument. The PVC does not have to be enabled on the
	            switch, but should be as the system might attempt to
	            send data as soon as it recognizes the new PVC.
	
	-pvc | -vc  Destroys an existing PVC (-pvc) or VC (-vc). The PVC
	            or VC is disconnected from the convergence module to
	            which it was attached and its resources deallocated.
	            At this point, all data received for the PVC's
	            or VC's VCI is discarded. If you specify the VC
	            identifier, you can obtain this value by using the
	            vclist command.

	________________________________________________________________


	To enable and disable device drivers, type:

	/usr/sbin/atmconfig {up | down | status} driver=driver_name

	The following table lists the arguments and definitions:

	________________________________________________________________
	Argument    Description
	________________________________________________________________
	
	up          Instructs the driver specified in the driver=driver_
	            name argument to initiate contact with the network;
	            the driver is not necessarily online when the
	            command returns. Use the status command to determine
	            the driver's actual state.
	
	down        Instructs the driver specified in the driver=driver
	            name argument to disconnect from the network, re-
	            leasing all VCs in an orderly manner, unregistering
	            all ESIs, and taking down the interface. No new
	            connections can be made while the interface is
	            being taken down. When this command returns, the
	            system has started a shutdown procedure that can
	            take several minutes.

	            If this command is entered twice, the driver will be
	            taken off-line immediately without releasing VCs;
	            the protocol timers for the VCs will expire.
	
	status      Reports the current status of the driver specified
	            in the driver=driver_name argument. The interface
	            can be in the following states:
	
	            o  down - the interface is off-line
	
	            o  up - the interface is online and is synchronized
	               with the switch
	
	            o  disconnected - the driver is up, but currently does
	               not have a live connection to the switch
	
	            o  going down - the interface is up, but is in the
	               process of shutting down

	________________________________________________________________
	
	
4.2.1.2	atmconfig Status Commands:
	
	To display currently active VCs and driver status, use the 
	following commands at the console: 
	
	/usr/sbin/atmconfig {+vfc | -vfc} driver=driver_name
	
	/usr/sbin/atmconfig source [file=filename]
	
	/usr/sbin/atmconfig wait state=up|down|oos driver=driver_name
	
	The following table lists the arguments and definitions:
	
	________________________________________________________________
	Argument         Description
	________________________________________________________________
	
	driver=driver_   Specifies a specific driver or network
	name             interface.
	
	+vfc | -vc       Enables (+vfc) or disables (-vfc) vendor-
	                 specific flow control on the interface
	                 specified by the driver=driver_name argument.
	                 The specified interface must support this type
	                 of flow control.
	
	file=file name   Specifies the path name of a file to be used as
	                 alternate input for a command.
	
	state=up | down  Specifies the interface state to set. up checks
	| oos            that the interface is enabled and is in contact
	                 with the switch. down checks that the interface
	                 is being disabled and is not in contact with
	                 the switch. oos checks that the interface is
	                 enabled, but not in contact with the switch.

	________________________________________________________________
	
	
4.2.2 atmarp
	
	The atmarp command configures an ATM ARP (address resolution
	protocol) module to operate in either the client or server mode.
	The network must have one server and can have any number of
	clients. The atmarp command enables you to create and delete
	entries in the ATM ARP table, display entries in the ATM ARP
	table, toggle the permanent flag for entries, display the
	local host's ATM configuration status, and create and remove
	an association between an established VC and a remote IP entity
	that does not support Classical IP.
	
	To create an association between an established VC (PVC or SVC)
	and a remote IP entity, the ATM ARP entry must be marked as
	permanent and there must be an InARP request pending on that
	VC. An InARP request on a VC is considered to be pending in the
	following cases:
	
	o  A system administrator establishes a PVC and the local host
	   issues an InARP request on the PVC to establish the identity
	   of the remote node.
	
	o  A remote system establishes an SVC for use with IP. The local
	   host issues an InARP request on the SVC to determine the
	   identity on the remote end of the SVC.
	
	In either case, if the remote system does not support RFC 1577,
	the local host never receives a response to the InARP request,
	leaving the request pending.
	
	
4.2.2.1	atmarp Setup Commands
	
	To map an IP address, type:
	
	atmarp -s atm_address ip_address permanent
	
	atmarp -v +vc vpi_number vci_number ip_address
	
	The following table lists the arguments and definitions:
	
	________________________________________________________________
	Argument         Description
	________________________________________________________________
	
	-s atm_address   Creates an ATM address entry for the IP address
	ip_address       in the ATM ARP table. You must specify the
	[permanent]      following arguments:
	
	                 o  atm_address - the ATM address (full 20-byte
	                    NSAP) for the entry
	
	                 o  ip_address - the IP address for the corre-
	                    sponding ATM address
	
	-v +|- vpi_      Creates (+) or removes (-) an association
	number vci_      between an established virtual circuit, either
	number hostname  PVC or SVC, and a remote IP entity that does
	                 not support Classical IP. You must specify the
	                 following arguments:
	
	                 o  vpi_number - the VPI for the virtual circuit
	
	                 o  vci_number - the VCI for the virtual circuit
	
	                 o  hostname - the hostname assigned to the ARP
	                    entry
	
	                 In order to associate an established VC with a
	                 remote IP entity, the ATM address entry must
	                 be marked as permanent (using the atmarp -p
	                 hostname or the atmarp -s command) and there
	                 must be an InARP request pending on that VC.

	________________________________________________________________
	
	
4.2.2.2	atmarp Status Commands
	
	To display the ATM ARP configuration information, type the 
        following command at the console: 
	
	atmarp -h
	
	The following table lists the arguments and definitions:
	
	________________________________________________________________
	Argument         Description
	________________________________________________________________
	
	-h               Displays the configuration information for the
	                 local host on the logical IP subnet (LIS). A
	                 host can be either a server or client.

	________________________________________________________________
	
	
4.2.2.3 Server Mode
	
	In this mode, ATM ARP accepts connections from all ATM ARP
	clients on the LIS and determines both their ATM and IP
	addresses to build a table that is used to map IP addresses
	to ATM addresses. When functioning as a server, ATM ARP accepts
	ARP resolution requests from all clients on the LIS.
	
	Refer to RFC 1577 for a functional description of the ARP
	server. To configure an ATM ARP server, you must inform the
	ATM ARP module that it will be functioning as a server. No
	other data is required. As a result of server configuration,
	the server's full 20-byte (NSAP) ATM address is displayed. Hosts
	on the LIS use this address when they are configured as ATM ARP
	clients.
	
4.2.2.4 Client Mode
	
	In this mode, ATM ARP makes a connection to the ATM ARP
	server and sends all ARP resolution requests to the server.
	To configure ATM ARP clients, you must supply both the ATM
	address and IP address of the ATM ARP server. This is the full
	20-byte (NSAP) ATM address. Both these values are required for
	the client to contact the server.
	
***TRADEMARKS***

AlphaServer, AlphaStation, ATMworks 350, Digital, and FLOWmaster are 
trademarks of Digital Equipment Corporation.
	
UNIX is a registered trademark in the United States and other 
countries, licensed exclusively through X/Open Company, Ltd.
