# @(#)README - INTERPHASE CORPORATION - HP-UX 9.x EISA ATM ************************************************************************* **** Please read this document in its entirety prior to product **** **** installation. Note that this document supersedes the **** **** Installation Guide if differences arise. **** ************************************************************************* 1. Introduction This README file describes the new features in the Integrated Driver 1 (ID1) release of the ATM adapter software. This file should be read carefully before the ID1 software is installed on your system. The ID1 driver provides the following functions in the same driver. All these functions can be enabled and used simultaneously. - LAN Emulation client (SVC). o Ethernet o Token Ring - LAN Emulation services (LES, BUS and LECS). o Ethernet o Token Ring - IP-ATM (RFC-1577) client (SVC) - IP-ATM (RFC-1577) server - Bridged PVCs based on RFC-1483 o LLC Encapsulated Ethernet/802.3 o LLC Encapsulated 802.5 o Null Encapsulated Ethernet/802.3 o Null Encapsulated 802.5 - Routed PVCs based on RFC-1483 o LLC Encapsulated o Null Encapsulated The configuration and the statistics display of the driver software is done with a GUI based utility, CellView. 2. Installation First time installation will require the following steps: i) Copy the file INP5000.CFG to the /etc/eisa/ directory. As su: cp /INP5000.CFG /etc/eisa/\!INP5000.CFG ii) Run eisa_config -run the command "show" to see if any boards are currently loaded -run the command "add INP5000 " using slotnum as the number of the physical slot you will be placing the Interphase board in. See HP documentation for description of slot numbers -use the "?" command if you have any questions about eisa_config iii) Reboot the computer iv) Install the Interphase ATM driver software as su as follows: update -r -s //INPHID1.TAR "*" Note: Running the update command will cause the kernel to be rebuilt and the system will be rebooted. **After installation, the driver must be configured. Determine the IP address of the ATM adapter. Note that if there are other IP nodes on the host system (e.g. an Ethernet interface), the IP address used for each ATM interface must be in a totally separate network segment. If the same segment as the Ethernet is used (for example), then routing and broadcast problems will occur as the network layer will assume that both devices are physically on the same segment. To configure the driver to automatically start at boot time, it will be necessary to add the correct net addresses and netmask values for each li interface to the INPHID1 startup file. i) Edit the file /etc/inphid1rc, uncomment the lines relating to the interfaces you wish to configure and replace the and options with those you will be using on your system. These values will be used during startup on succeeding bootup operations. ii) After editing the file run /etc/inphid1rc iii) Use Cellview to set up lec's See Cellview man page if needed 3. New Features This driver supports multiple LECs on the same ELAN. 4. Configuration After the software is installed on a system, the system should be rebooted before the driver software can be configured with CellView. Once the software is configured, it does not have to be configured again after each system reboot. In the ID1 release, all the configuration data is stored in a single configuration file, /etc/atm/cvconf. Configuration files /etc/lecconf.(n) and /etc/atmconf.(n) in pre-ID1 releases do not exist in this release. There is an on-line man page for cvconf that describes the format of this file. When the ID1 package is removed from a system, the configuration file /etc/atm/cvconf is saved as /etc/atm/cvconf.save. If an ID1 package is installed again, /etc/atm/cvconf.save can be moved to /etc/atm/cvconf to quickly restore the configuration of the previous installation. 5. CellView CellView is a GUI based utility for ATM software configuration and statistic display. When an entity, such as LECS, is configured with CellView, in addition to configuring the software, the configuration information is stored in the configuration file so that upon subsequent system reboots, the software configuration can be restored without having to configure the software manually again. At the system boot time, all the software entities are initialized with the configuration information in the configuration file. With the configuration capabilities of CellView, command line configuration utilities such as les, lecs, etc. are not needed. The command line configuration utilities are included in the package but their usage is not recommended unless for some reason you can not run CellView on your system. Command line configuration utilities configure the software based on the options specified, but do not update the configuration file. In the "Setup" mode, CellView displays the configuration stored in the configuration file. In the "Stats" mode, CellView displays the actual configuration of the software. Normally the configuration file mirrors the software configuration. If the command line configuration utilities are used, the configuration file and the software configuration may get out of synchronization. This can cause subsequent configuration changed from CellView to not work properly. 6. PVCs The LAN Emulation and IP-ATM clients include both SVC and PVC capabilities. In LAN Emulation clients, SVC capabilities are based on ATM Forum's "LAN Emulation Over ATM Specification - Version 1.0". The PVCs supported are bridged PVCs as described in RFC-1483. Clients can be enabled in PVC only or PVC and SVC mode. A 6 byte unicast MAC address and a VCI number is associated with each PVC. Packets received from the upper layers whose destination MAC address match the MAC address of a PVC are transmitted on that PVC. Each PVC can be individually enabled as "Broadcast PVC". If enabled as "Broadcast PVC", all the broadcast/multicast packets received by that client from the upper layers are transmitted on that PVC. A maximum of 16 PVCs can be enabled as "Broadcast PVC". In IP-ATM clients, SVC capabilities are based on RFC-1577. The PVCs supported are routed PVCs as described in RFC-1483. Clients can be enabled in PVC only or PVC and SVC mode. An IP address and a VCI number is associated with each PVC. Packets received from the upper layers whose first hop (an end-station or a router) match the IP address of a PVC are transmitted on that PVC. Like RFC-1577, IP-ATM PVCs do not support transmission of broadcast/multicast packets. 7. Other Notes - If the signaling parameters are changed from CellView, the changes will not take effect until the system is rebooted or signalling deamon is restarted. Signaling deamon can be restarted by entering the command "restart_signald". - The mapping of IP interface number to LANE and IP-ATM clients is as follows: LANE clients: IP interface number = (board number * 4) + client number IP-ATM clients: IP interface number = 32 + board number If there are two adapters installed in the system, IP interface number for all the clients that can be enabled is shown below. 'li' is the IP interface prefix for Interphase ATM adapters. li0 Board 0, LAN Emulation client 0 li1 Board 0, LAN Emulation client 1 li2 Board 0, LAN Emulation client 2 li3 Board 0, LAN Emulation client 3 li4 Board 1, LAN Emulation client 0 li5 Board 1, LAN Emulation client 1 li6 Board 1, LAN Emulation client 2 li7 Board 1, LAN Emulation client 3 li32 Board 0, IP-ATM client li33 Board 1, IP-ATM client - MAC address for Bridged PVCs should be entered in the natural order of the emulated LAN. For Ethernet emulation, the MAC address should be entered in the conical format. For Token Ring emulation, MAC address should be entered in the non-conical format. - After the software package is installed, all the entities, including the LAN Emulation and IP-ATM clients, are initially configured as disabled. Run CellView or edit the file /etc/atm/cvconf to enable and configure desired entities. - Set "Enable Advanced Settings" in the "Global" dialog box in CellView to access LAN Emulation services from CellView. 8. Bug (missing features) list