Atm NP_ATM_Rel2_Managers_Guide_Mar98 NP Rel2 Managers Guide Mar98
NP_ATM_Rel2_Managers_Guide_Mar98 NP_ATM_Rel2_Managers_Guide_Mar98
User Manual: NP_ATM_Rel2_Managers_Guide_Mar98
Open the PDF directly: View PDF 
.
Page Count: 44
| Download | |
| Open PDF In Browser | View PDF |
NP (ATM Release 2) Manager’s Guide AUSPEX Preliminary and Confidential AUSPEX Copyright Copyright ©1998, Auspex Systems, Inc. All rights reserved. Printed in the United States of America. Part Number 850479-001. No part of this publication may be reproduced, in any form or by any means, without the prior written consent of Auspex Systems, Inc. Auspex Systems, Inc., reserves the right to revise this publication and make changes in content from time to time without obligation on the part of Auspex Systems to provide prior notification of such revision or change. Portions of this documentation incorporated by permission of FORE Systems, Inc. U.S. GOVERNMENT RIGHTS: As specified in 48 C.F.R.12.212 of the FAR and in 48.C.F.R 227-7202-1 of the DFARS, the use, duplication or disclosure of licensed commercial software and documentation is subject to the Auspex System's license. Such rights and restrictions are similar to those set forth in FAR 52.227-19(c)(1)&(c)(2). Trademarks Auspex, the Auspex logo, Functional Multiprocessor, Functional Multi-processor, Functional Multi-processing, Functional Multiprocessing Kernel, FMK, and FMP are registered trademarks of Auspex Systems, Inc. NS 7000, NS 6000, NS 6002, NS 5500, NS 5502, NS 5000, NS 3000, NetServer, DataGuard, ServerGuard, Functional Multiprocessing, NeTservices, and Thrive Carefully are trademarks of Auspex Systems, Inc. AT&T is a registered trademark of AT&T Corporation. Microsoft, MS, MS-DOS, Windows, Windows NT, and Backoffice are either registered trademarks or trademarks of Microsoft Corporation. Sun, Sun Microsystems, the Sun Logo, Solaris, SunOS, ONC, ONC/NFS, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. All SPARC trademarks are used under license and are the trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries of The Open Group. VMEbus is a trademark of VMEbus Manufacturers Group. DEC and VT 510 are trademarks of Digital Equipment Corp. ForeRunner is a trademark of FORE Systems, Inc. Acrobat is a trademark of Adobe Systems, Inc. Auspex NetServer System Software is derived from UNIX® licensed from The Santa Cruz Operation, Inc. and SunOs™ 4.1.4 and ONC/NFS 4.1 licensed from Sun Microsystems, Inc. Auspex NetServer System Software Version 1.10 incorporates AT&T’s Advanced Server for UNIX Systems. Auspex Optional Products Premier Software Series for NeTservices incorporates AT&T’s Advanced Server for UNIX Systems and NETBIOS/ix. NETBIOS/ix is a registered U.S. trademark of Micro Computer Systems, Inc. Microsoft may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Microsoft. Auspex Systems, Inc. 2300 Central Expressway Santa Clara, California 95050 Phone: (408) 566-2000 Fax: (408) 566-2020 Internet: info@auspex.com World Wide Web: http://www.auspex.com ii ▲ Preliminary and Confidential AUSPEX Protection Against Electrostatic Discharge To prevent damage to the system due to electrostatic discharge, always wear the antistatic wrist strap provided with your network server when you come in contact with the system. Publication Change Record The following table records all revisions to this publication. The first entry is always the publication’s initial release. Each entry indicates the date of the release and the number of the system release to which the revision corresponds. Part Number Date Description 850479-001 March 1998 Release 1.10, first release ▲ iii Preliminary and Confidential AUSPEX Preface About This Guide This guide provides information on how to operate and manage NP (ATM Release 2) software. It assumes you are familiar with the ATM network environment and terminology. Information in this guide was derived in part from the ForeRunner™ SBA-200 ATM SBus Adapter User’s Manual dated March 1996. Applicable Documentation The following is a list of documents you will find useful when installing or operating NP (ATM Release 2): ▲ Software Release Note, Auspex Systems, Inc. ▲ System Manager’s Guide, Auspex Systems, Inc. ▲ Hardware Release Note, Auspex Systems, Inc. ▲ Hardware manual for your server model Typographical Conventions In this guide, different typefaces indicate different kinds of information. The following table explains these typographical conventions. Font Meaning Typewriter Indicates a literal screen message. Bold In a command line, indicates information to be entered exactly as shown. In text, indicates a command name or device name. Italics In a command line, indicates a nonliteral item or variable for which you substitute an appropriate value. In text, indicates a path name or a special term. Hexadecimal values in the text are preceded with “0x,” and leading zeros are not always shown. For example, the notation 0x68 is used to indicate the hexadecimal address 00000068. Preface ▲ v Preliminary and Confidential AUSPEX Special Messages The following special messages are used in this guide: Warning: Warnings alert you to the danger of personal injury and call attention to instructions you must follow for your personal safety. Caution: Cautions call attention to instructions you must follow to prevent damage to system hardware or software or loss of system data. Note: Notes call attention to important information you should be aware of as you follow the procedures described in this guide. Recommendation: Recommendations call attention to an item or procedure that is not required but might help improve performance, ease of use, and ease of installation or configuration. Tools The tools icon identifies the tools you need to complete a task. vi ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Getting Help Customer support is described in this section. North America Telephone Support Customers in North America can reach Auspex customer service at any time by dialing 1800-3-AUSPEX or 1-800-328-7739. International Telephone Support Customers within the countries and territory listed as follows can reach Auspex customer service at any time by dialing the appropriate telephone number. Country or territory Telephone number Country or territory Telephone number Australia 1-800-121-194 Luxembourg 0800-2721 Austria 0-660-7912 Malaysia 800-4509 Belgium 0800-1-0180 Netherlands 06-0222158 Denmark 80-01-03-60 Norway 800-1-1294 France 0800-91-21-32 (0800-26-38-22)* Philippines 1-800-116-0005 Germany 0130-81-8306 Poland 00-800-441-1220 Hong Kong 800-4803 Spain 900-95-4445 Ireland 1800 55 3343 Sweden 020-797326 Israel 177 440 9285 Switzerland 0800-55-1339 Italy 1678-73541 Taiwan 0080-14-9580 Japan 0044-22-12-2414 United Kingdom 0800-28-7739 Korea 0038-13-0374 * France has two toll-free numbers. The number in () is directed to the Paris office during the working day. International customers who purchase Auspex products from an authorized distributor or reseller should contact that distributor or reseller for support Email Support Customer support through email is available to both North America and International customers at the following address: support@corp.auspex.com Preface ▲ vii Preliminary and Confidential AUSPEX Customer Feedback To comment on the content of this publication, send email to Auspex Technical Publications at the following address: techpubs@corp.auspex.com World Wide Web For more information about Auspex Systems, Inc. and its products, use the following resource location on the World Wide Web: http://www.auspex.com viii ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Contents Chapter 1 Overview of NP (ATM Release 2) About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 FORE IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Classical IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Logical IP Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 LANE Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Address Registration and ILMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 ATM Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Operating with ILMI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 ATMARP Server Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 NP (ATM Release 2) Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Chapter 2 Installing NP (ATM Release 2) About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Package Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 NP (ATM Release 2) Network Interface Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Configuring FORE IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Configuring Classical IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Configuring LEC Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Chapter 3 Configuring Network Interfaces About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Maintenance Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ax_adinfo(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ax_atmarp(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ax_atmconfig(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ax_atmlooptest(8C). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ax_atmstat(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ax_elarp(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 ax_elconfig(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 ax_elcreate(8C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 NP (ATM Release 2) and ax_perfmon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Operating Without ILMI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Configuring the NetServer as an ATMARP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Removing NP (ATM Release 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 ▲ ix AUSPEX Preliminary and Confidential Figures Single LANE network 1-6 ATMARP server operation 1-9 Example of an NP (ATM Release 2) entry in an ax_perfmon display 4-4 ▲ xi Preliminary and Confidential AUSPEX xii ▲ Figures Preliminary and Confidential AUSPEX Tables Table 1-1. Table 1-2. NP (ATM Release 2) features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 NP (ATM Release 2) limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Example of NP (ATM Release 2) network interface numbering 3-2 ▲ xiii Preliminary and Confidential AUSPEX xiv ▲ Tables AUSPEX 1 Overview of NP (ATM Release 2) About This Chapter This chapter describes NP (ATM Release 2) software and features. The following topics are covered in this chapter: ▲ Overview ▲ FORE IP Interface ▲ Classical IP Interface ▲ Address Registration and ILMI ▲ ATMARP Server Operation ▲ NP (ATM Release 2) Limitations Overview of NP (ATM Release 2) ▲ 1-1 AUSPEX Overview NP (ATM Release 2) is Auspex’s Network Processor (NP)-resident implementation of Asynchronous Transfer Mode (ATM). The Auspex implementation, with hardware and software supported directly on the NP, results in improved throughput and response time. NP (ATM Release 2) is based on FORE Systems’ SBA-200 Series ATM adapter hardware and software. NP (ATM Release 2) provides connectivity to compatible ATM switches through multi-mode fiber-optic (OC-3) cables with SC and ST-type connectors, or unshielded twisted pair category 5 (UTP5) cables with RJ-45 connectors at 155 megabits per second. Auspex supports up to 3 adapters per NP and up to 15 adapters per system. Each NP supports up to 1024 active virtual connections. Each adapter provides up to 21 IP interfaces (1 FORE IP interface, 4 Classical IP interfaces, and 16 LEC interfaces), allowing you to configure up to 21 IP subnets per adapter. Table 1-1 lists the features available with NP (ATM Release 2). Table 1-1. NP (ATM Release 2) features ▲ LAN Emulation (LANE) over ATM ▲ LAN Emulation Client (LEC) support for Ethernet LANs ▲ SPANS Switched Virtual Circuit (SVC) signalling protocol ▲ Permanent Virtual Circuits (PVC) ▲ Supports up to 1024 Virtual Circuit Identifiers (VCIs) ▲ Supports UNI 3.0 signalling ▲ Supports Interim Local Management Interface (ILMI) ▲ Supports up to 21 virtual Internet Protocol (IP) interfaces per adapter (1 FORE IP, 4 Classical IP, and 16 LEC) 1-2 ▲ NP (ATM Release 2) Manager’s Guide FORE IP Interface The FORE IP interface supports the Single Protocol for ATM Network Signalling (SPANS) protocol and enables communication using ATM Adaptation Layer 4 or 5 (AAL4 or AAL5) without encapsulation. FORE IP uses a broadcast ATMARP server for SPANS signalling and supports direct communication of all hosts on a physical ATM network without the use of IP routers. Since SPANS and UNI 3.0 use different virtual connections to establish network communication, a host can simultaneously support both FORE IP over SPANS and Classical IP over UNI 3.0 on the same ATM adapter. As a result of standard IP routing, all traffic sent through an afa interface will use FORE IP, while all traffic sent through an aqa interface will use Classical IP. Note: Both the afa and aqa interfaces can be configured simultaneously, but they must reside on separate subnets. Classical IP specific configuration changes can only be made with the aqa devices, while SPANS specific configuration changes can only be made with afa devices. FORE IP Interface ▲ 1-3 AUSPEX Classical IP Interface The term classical indicates that the ATM network has the same properties as the existing legacy LANs. That is, even though ATM technology allows for large globally connected networks, for example, it is only used in the LAN environment as a direct replacement of existing LAN technology. The classical model of LANs connected through IP routers is maintained in ATM networks. Classical IP over ATM is different than IP in legacy LANs in that ATM provides a virtual connection environment through the use of permanent virtual circuits (PVCs) and/or switched virtual circuits (SVCs). SVC management is performed via UNI 3.0 signalling. UNI 3.0 is a broadband signalling protocol designed to establish connections dynamically. On an Auspex NetServer, each Classical IP interface name begins with aqa. Once a Classical IP connection has been established, IP datagrams are encapsulated using IEEE 802.3 LLC/SNAP and are segmented into ATM cells using AALS. Note: There is currently no support for IP broadcast or IP multicast datagrams in Classical IP network environments. RFC-1577 is the standard specification for Classical IP over ATM. Logical IP Subnets An important concept in Classical IP networks is that of a Logical IP Subnet (LIS). An LIS is a group of hosts configured to be members of the same IP subnet (that is, they have the same IP network and subnetwork numbers). In this sense, one LIS can be equated to one legacy LAN. In a Classical IP ATM network, placing a host on a specific subnet is a logical choice rather than a physical one. The number of LISs, and the division of hosts into each LIS, is purely an administrative issue. Limitations of IP addressing, IP packet filtering, and administrative boundaries may guide a network manager into establishing several LISs into a single ATM network. Note: Communication between LISs must occur through IP routers. 1-4 ▲ NP (ATM Release 2) Manager’s Guide LANE Services Auspex’s NP (ATM Release 2) software is compliant with the ATM Forum’s LAN Emulation over ATM Version 1.0 specification, and supports LAN Emulation (LANE) of Ethernet (IEEE 802.3) LANs only. LANE allows higher level protocols and LAN applications to interoperate, without modifications, in an ATM network. The components of LANE work together to emulate an emulated LAN (ELAN), resolve MAC to ATM addresses, replace the connectionless operation of legacy LANs with point-to-point connections, and provide broadcast and multicast services. An ELAN has the following components: ▲ LANE Clients (LECs) ▲ LANE Configuration Server (LECS) ▲ LANE Server (LES) ▲ Broadcast and Unknown Server (BUS) Each of these components is described as follows. LEC The LEC runs on each end station in the ELAN. LECs communicate with other ELAN components (LES and BUS) to resolve MAC addresses into ATM addresses. LECS The LECS runs on a SunOS workstation or a FORE Systems ATM switch. It maintains information about all ELANs within the administrative domain. When the LEC successfully communicates with the LECS, the LECS provides a list of ELANs that the LEC can join. LES The LES runs on a SunOS workstation or a FORE Systems ATM switch. It maintains information about the LECs within a single ELAN and performs address resolution. BUS The BUS runs on a SunOS workstation or a FORE Systems switch. It provides services within a single ELAN allowing broadcasts, multicast, and unknown unicasts within a single ELAN. Note: Auspex currently supports Ethernet LECs only. The LECS and LES should be configured either on an ATM switch or an external host. LANE Services ▲ 1-5 AUSPEX Figure 1-1 shows an example of a single LANE network in which the NetServer (workstation A) attempts to initiate data transfers to workstation B. ATM Switch BUS LAN Switch LES A B 1. Address request sent to LES and BUS 2. If LAN Switch knows MAC address the of B, it sends its own ATM address to A 3. Connection Request Connection Indication Connection Received Connection Sent Data Transmission Figure 1-1. Single LANE network 1-6 ▲ NP (ATM Release 2) Manager’s Guide Address Registration and ILMI Before a host can establish connections over a physical interface, the host must know the ATM address for that interface. The primary purpose of the Interim Local Management Interface (ILMI) is to discover and register these ATM addresses dynamically. ATM addresses and ILMI support are discussed in the following sections. ATM Addresses For private ATM networks, addresses uniquely identify ATM endpoints. The UNI 3.0 address format is modeled after that of an OSI Network Service Access Point (NSAP). Since ATM does not have the concept of MAC addresses, ATM uses NSAP addresses, which are 20 bytes long. An ATM address consists of the following: ▲ 13-byte network-side prefix. The prefix is the ATM prefix of the switch to which the host is attached. ▲ 7-byte user-side portion consisting of the following: – 6-byte End System Identifier (ESI). The ESI is the unique IEEE MAC address of the interface. – 1-byte selector. Although each virtual interface for a given physical interface uses the same prefix and ESI, the selector field identifies a specific virtual interface. For example: 0x47.0005.80.ffe100.0000.f21a.1d25.002048062f8b.00 In the example, 0x47.0005.80.ffe100.0000.f21a.1d25. is the ATM switch prefix, 002048062f8b is the MAC portion, and .00 is the selector field that identifies the number of the adapter interface. Operating with ILMI Support If ILMI is supported on all of the switches and hosts in a given network, when a switch boots up, ILMI enables the switch to discover all of the hosts attached to it and to send its ATM prefix associated with the port to those hosts dynamically. In return, the host prepends that prefix to its ESI and selector fields, forming a complete ATM address. If a host changes network ports after an ATM address has been registered for its interface, all existing connections will be closed. If the new port is on a different switch, a new ATM address (with a different network address prefix) will be registered. The host can then establish new connections. Auspex NetServers support ILMI by default. Instructions for using NP (ATM Release 2) without ILMI support are in Chapter 4. There is one instance of the ILMI (ax_ilmid) daemon running per adapter. See the ax_ilmid man page for more information. Address Registration and ILMI ▲ 1-7 AUSPEX ATMARP Server Operation Auspex supports the ATM Address Resolution Protocol (ATMARP) operation for customers who want to obtain the ATM to IP address resolution from the NetServer. In order for a host to establish a connection to another host, it must first determine the other host’s ATM address. ATMARP is the procedure used to resolve an IP address into an ATM address. Since the ATM standards do not currently support broadcast on an ATM/Classical IP interface, address resolution is performed by direct communication with a special ARP server, rather than broadcasting ARP requests as is done in legacy LANs. Each host in an LIS must be configured with the ATM address of the host providing ARP service for its LIS. On a host ATMARP server, the ATM address of the ARP server can be obtained by running ax_atmarp -z (remember to use the interface associated with the given LIS). The ARP server address is normally configured into each host at installation time (the appropriate commands are placed in the script rc.ax_sba200 in the directory /usr/etc/fore or the user specified directory), but it may be done at any time by running ax_atmarp -p. If the ATMARP server address is configured in the firmware download script, it will be persistent across reboots, but if it is configured using ax_atmarp -p, it will not be persistent across reboots. Since only one ATMARP server can function at a time in a given LIS, and since the ATMARP server’s address is manually configured into each host, it is not possible to use multiple, redundant ATMARP servers to improve robustness. If an ATMARP server becomes nonfunctional, a new ATMARP server must be configured, and each host within the LIS must be configured to use the new ATMARP server. A new ATMARP server address can be configured on a host by running the ax_atmarp -p command to set the new address and the ifconfig command to mark the appropriate interface UP or DOWN for the change to take effect. For example: # ax_atmarp -p# ifconfig aqax down; ifconfig aqax up In the example, x represents the number of the interface. 1-8 ▲ NP (ATM Release 2) Manager’s Guide Figure 1-2 shows an Auspex NetServer configured as an ARP server. In the figure, workstation A is attempting to make a connection to workstation B on LIS 1. Workstation A sends an ARP request containing the IP address to be resolved to the ATMARP server. When workstation A receives the ATMARP reply from the ATMARP server, workstation A creates an ATMARP cache to store the IP to ATM address map and begins data transmission to workstation B. ATM Network / LIS 1 A B 1. ARP Request with B’s IP address 2. ARP Reply with B’s ATM address ARP Server 3. Data Transmission Figure 1-2. ATMARP server operation ATMARP Server Operation ▲ 1-9 AUSPEX NP (ATM Release 2) Limitations Table 1-2 lists limitations in the NP (ATM Release 2) software architecture. Table 1-2. NP (ATM Release 2) limitations ▲ Up to 1,024 connections per adapter ▲ Up to 16 LECs supported per adapter (Ethernet only) ▲ No UNI 3.1 support ▲ No support for LES, BUS, or LECS ▲ No Token Ring support ▲ No support for IP multicasting 1-10 ▲ NP (ATM Release 2) Manager’s Guide AUSPEX 2 Installing NP (ATM Release 2) About This Chapter This chapter describes how to install and configure NP (ATM Release 2) software. The procedures described in this chapter assume that your NetServer is already installed at your site. The following topics are covered in this chapter: ▲ Hardware Configuration ▲ Package Tools ▲ Software Installation Installing NP (ATM Release 2) ▲ 2-1 Preliminary and Confidential AUSPEX Hardware Configuration NP (ATM Release 2) uses ForeRunner SBA-200 Series ATM adapters. Each NP can have up to 3 adapters for a maximum of 15 adapters per NetServer. To display your NetServer’s hardware configuration, enter the ax_config command; for example: # ax_config -d Information regarding your NetServer’s hardware configuration is displayed. Here is an example: 60-0028 ? 60-0047 ? 84383FORE ATM/OC3SC Module SBA-200E (4.0.0) 84383FORE ATM/UTP5 Module SBA-200E (4.0.0) Contact your Auspex sales representative to purchase ATM adapters, or your Auspex service representative to install ATM adapters. 2-2 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Package Tools Package tools allow you to install NP (ATM Release 2) from the Auspex Premier Software Series CD-ROM shipped with your system. Package tools are the standard SVR4 package utilities, which are shipped as part of the Auspex system software. The tools allow you to add, check, remove, and display information about NP (ATM Release 2). The basic commands are as follows: ▲ pkgadd(1M) – Transfers the contents of a software package from the distribution medium, and installs it onto a system. Messages from this command display on the console and are written to the file /var/log/pkgadd.log on the target drive and /tmp/pkgadd.log on the current root drive. Note: pkgadd(1M) sets userid to install, if it exists; otherwise, it sets userid to root. If you have a userid of install set up, it must have superuser permission or the pkgadd will fail. Either remove or rename the install userid, or give the install userid superuser permissions. ▲ pkgchk(1M) – Checks the accuracy of installed files or, by using the -l option, displays information about package files. ▲ pkgrm(1M) – Removes a previously or partially installed package from the system. Messages from this command display on the console and are written to the file /var/log/pkgrm.log on the target drive and /tmp/pkgrm.log on the current root drive. ▲ pkginfo(1M) – Displays information about software packages installed on the system. For more information, refer to the UNIX man pages for these commands: pkgadd(1M), pkgchk(1M), pkgrm(1M), and pkginfo(1M). Package Tools ▲ 2-3 Preliminary and Confidential AUSPEX Software Installation This section provides procedures for installing the NP (ATM Release 2) software. Recommendation: After completing the installation, test the new software to verify that the updated root drive is usable (for example, it boots, runs, and the newly added features work). If everything works correctly, clone the entire root disk to an alternate root disk using the ax_sputil(8) command with the copy option. Alternatively, copy each file system on the root disk to an alternate root disk using the ax_clonefs(8) command on each file system. To install NP (ATM Release 2) 1. Mount the Premier Software Series CD. For example: # mount -rt hsfs /dev/acd1 /cdrom This command mounts the CD in drive slot 1 on /cdrom. 2. Mount /usr with read/write privilege: # mount -o remount,rw /usr 3. Add the software package to the server by entering the following command: # pkgadd -d /cdrom The system prompts you to select a software package from a list similar to the following. pkgadd session stated on Mar 2 10:45:05 PST 1998 The following packages are available: 1 AXatm2 2 AXbackup 3 AXdguard 4 AXdocs 5 AXdrvgrd 6 AXftp 7 AXsrvgrd 8 AXEC1 9 AXNeTsrv 10 AXNTadmin 11 AXNTBios ATM 2 (HP-VII,HP-VIII) 1.10 FastBackup (HP-VII,HP-VIII) 1.10 DataGuard (HP-VII,HP-VIII) 1.10 Auspex System Documentation (HP-VII,HP-VIII) 1.10 DriveGuard (HP-VII,HP-VIII) 1.10 NP Resident FTP (HP-VII,HP-VIII) 1.10 ServerGuard (HP-VII,HP-VIII) 1.10 EtherChannel (HP-VII,HP-VIII) 1.10 NeTservices Products (HP-VII,HP-VIII) 1.10 NeTservices Administration (HP-VII,HP-VIII) 1.10 NeTservices Concepts and Planning (HP-VII,HP-VIII) 1.10 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: 2-4 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX where ? is a one-digit entry, and ?? is a two-digit entry. 4. Type 3 for the NP (ATM Release 2) package. The system responds with: Processing package instance from /cdrom ATM 2 (HP-VII,HP-VIII) 1.10 pkgadd installs NP (ATM Release 2) on the NetServer. The system then responds with the following message: Do you want to activate ATM 2 immediately after installation?[y/n] 5. Enter y to activate NP (ATM Release 2) immediately after installation. Enter n if you do not wish to activate NP (ATM Release 2) immediately after installation. Note: If you choose not to activate the NP (ATM Release 2) software immediately after installation, use the ax_enable(8) command to activate the software at a later time. The installation process continues with the following messages: ## Processing package information. ## Processing system information. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with superuser permission during the process of installing this package. Do you want to continue with the installation of this package? [y,n] 6. Enter y to continue with the installation. Installing ATM 2 as ## Executing preinstall script. ## Installing part 1 of 1. [ verifying class ] /usr/etc/fore/ax_adinfo /usr/etc/fore/ax_atmarp /usr/etc/fore/ax_atmconfig /usr/etc/fore/ax_atmlooptest /usr/etc/fore/ax_atmstat /usr/etc/fore/ax_elarp /usr/etc/fore/ax_elconfig /usr/etc/fore/ax_elcreate /usr/etc/fore/ax_ilmid /usr/etc/fore/ax_ncomm /usr/etc/fore/ax_objcopy /usr/etc/fore/ax_sba200.ucode1 /usr/etc/fore/ax_sba200.ucode2 /usr/etc/fore/ax_sba200e.ucode1 /usr/etc/fore/ax_sba200e.ucode2 Software Installation ▲ 2-5 /usr/etc/fore/rc.ax_sba200 /usr/man/man4/afa.4 /usr/man/man4/aqa.4 /usr/man/man8/ax_adinfo.8c /usr/man/man8/ax_atmarp.8c /usr/man/man8/ax_atmconfig.8c /usr/man/man8/ax_atmlooptest.8c /usr/man/man8/ax_atmstat.8c /usr/etc/fore/ax_elarp.8c /usr/etc/fore/configuration.lane /usr/etc/fore/ax_elconfig.8c /usr/etc/fore/ax_elcreate.8c /usr/man/man8/ax_ilmid.8c /usr/man/man8/ax_ncomm.8c Installation of was successful. The following packages are available: 1 AXatm2 2 AXbackup 3 AXdguard 4 AXdocs 5 AXdrvgrd 6 AXftp 7 AXsrvgrd 8 AXEC1 9 AXNeTsrv 10 AXNTadmin 11 AXNTBios ATM 2 (HP-VII,HP-VIII) 1.10 FastBackup (HP-VII,HP-VIII) 1.10 DataGuard (HP-VII,HP-VIII) 1.10 Auspex System Documentation (HP-VII,HP-VIII) 1.10 DriveGuard (HP-VII,HP-VIII) 1.10 NP Resident FTP (HP-VII,HP-VIII) 1.10 ServerGuard (HP-VII,HP-VIII) 1.10 EtherChannel (HP-VII,HP-VIII) 1.10 NeTservices Products (HP-VII,HP-VIII) 1.10 NeTservices Administration (HP-VII,HP-VIII) 1.10 NeTservices Concepts and Planning (HP-VII,HP-VIII) 1.10 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: 7. Enter q to quit the pkgadd routine. pkgadd session finished on Mar 2 17 10:58:50 PST 1998 A log of this session of pkgadd is at /tmp/pkgadd.log on the current root disk, and at /var/log/pkgadd.log on the target disk. 8. Verify the installation using the pkgchk command; for example: # pkgchk -l AXatm2 This completes NP (ATM Release 2) installation. Preliminary and Confidential AUSPEX 3 Configuring Network Interfaces About This Chapter This chapter provides procedures for configuring FORE IP, Classical IP, and LEC interfaces. The following topics are covered in this chapter: ▲ NP (ATM Release 2) Network Interface Numbering ▲ Configuring FORE IP Interfaces ▲ Configuring Classical IP Interfaces ▲ Configuring LEC Interfaces The procedures in this chapter assume that ILMI is running and the NSAP addresses are automatically configured for each interface. See Chapter 4 for procedures on manually configuring NSAP addresses on the Classical IP interfaces. Configuring Network Interfaces ▲ 3-1 Preliminary and Confidential AUSPEX NP (ATM Release 2) Network Interface Numbering This section describes NP (ATM Release 2) network interface numbering. After installing the NP (ATM Release 2) software, you need to configure the network interface s. Each network interface must be configured with a unique IP address that is within the subnet assigned to the ELAN. NP (ATM Release 2) allows you to configure three types of ATM network interfaces: 1 FORE IP primary (afa) interface, 4 Classical IP virtual (aqa) interfaces, and 16 LEC (ael) interfaces. Table 3-1 shows an example of the NP (ATM Release 2) network interface numbering for an Auspex NetServer with two NP boards (NP0 and NP1), each having two ATM adapters (0, 1 and 2, 3). Table 3-1. Example of NP (ATM Release 2) network interface numbering NP board no. ATM adapter no. FORE IP primary interfaces Classical IP virtual interfaces LEC interfaces 0 0 afa0 aqa0, aqa1, aqa2, aqa3 ael0 – ael15 0 1 afa1 aqa4, aqa5, aqa6, aqa7 ael16 – ael31 1 2 afa2 aqa8, aqa9, aqa10, aqa11 ael32 – ael47 1 3 afa3 aqa12, aqa13, aqa14, aqa15 ael48 – ael63 In the example, FORE IP primary interfaces are named afa0 – afa3, depending on the number of ATM adapters installed in the server. Classical IP virtual interfaces are named aqa0 – aqa15, depending on the number of FORE IP primary interfaces configured. Each Classical IP interface has its virtual interface number as a suffix. LEC interfaces are named ael0 – ael63, depending on the number of ELANs configured. 3-2 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Configuring FORE IP Interfaces This section provides the procedures for configuring FORE IP primary interfaces. Each ATM adapter in the NetServer must be configured with a FORE IP address. Auspex system software recognizes FORE IP primary interfaces as afa in commands and displays. To configure the FORE IP primary interface addresses 1. Run NSconfig(8) to edit the network information for each afa interface, then execute NSconfig with Ctrl-F. Note: NSconfig executes ifconfig’s of network interfaces whether you are running in single or multi-user mode. Caution: Do not alter the ifconfig command lines in the file /etc/rc.boot. NSconfig relies on these command lines to function properly. For example, the following NSconfig form shows entries for five ATM adapters installed in an Auspex NetServer: ATM FORE SPANS Intf afa0 . . . afa1 . . . afa2 . . . afa3 . . . afa4 >UP [host-afa0__] afa0 on-net [100.00.00.0_] afa0 off-net [ffffff00_______]>0 >UP [host-afa1__] afa1 on-net [100.00.00.1_] afa1 off-net [ffffff00_______]>0 >UP [host-afa2__] afa2 on-net [100.00.00.2_] afa2 off-net [ffffff00_______]>0 [100.00.00.3_] afa4 off-net [ffffff00_______]>0 >Dwn >UP [host-afa4__] afa4 on-net In this example, interfaces afa0, afa1, afa2, and afa4 are marked UP, and interface afa3 is marked DWN. 2. If you changed the IP address or netmask of a network interface, or if the NIS type is changed to master or slave, reboot the server after running NSconfig. This creates entries in the /etc/rc.boot file. This completes the procedure for configuring the FORE IP primary interface addresses. Configuring FORE IP Interfaces ▲ 3-3 Preliminary and Confidential AUSPEX Configuring Classical IP Interfaces This section provides the procedures for configuring Classical IP virtual interfaces. Each ATM adapter in the NetServer can be configured with a Classical IP virtual interface address. Auspex system software recognizes Classical IP virtual interfaces as aqa in commands and displays. To configure the Classical IP virtual interface addresses 1. Run NSconfig(8) to edit the network information for each aqa interface, and execute NSconfig using Ctrl-F. Note: NSconfig executes the ifconfig’s of network interfaces whether you are running in single or multi-user mode. Caution: Do not alter the ifconfig command lines in the file /etc/rc.boot. NSconfig relies on these command lines to function properly. For example, the following NSconfig form shows entries for five ATM adapters installed in an Auspex NetServer: ATM Classical IP Intf aqa0 . >UP [host-aqa0__] aqa0 on-net [100.00.00.0_] aqa0 off-net [ffffff00_______]>0 >UP [host-aqa4__] aqa4 on-net [100.00.00.1_] aqa4 off-net [ffffff00_______]>0 >UP [host-aqa8__] aqa8 on-net [100.00.00.2_] aqa8 off-net [ffffff00_______]>0 [100.00.00.3_] aqa16 off-net [ffffff00_______]>0 . . aqa4 . . . aqa8 . . . aqa12 >Dwn . . . aqa16 >UP [host-aqa16__] aqa16 on-net In this example, interfaces aqa0, aqa4, aqa8, and aqa16 are marked UP, and interface aqa12 is marked DWN. The NSAP address for each interface is automatically determined by the ILMI daemon (ax_ilmid). 2. If you changed the IP address or netmask of a network interface, or if the NIS type is changed to master or slave, reboot the server after running NSconfig. This completes the procedure for configuring Classical IP virtual interface addresses. 3-4 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Configuring LEC Interfaces This section provides the procedures for configuring LEC interfaces. Note: NP (ATM Release 2) does not support the LAN Emulation Configuration Server (LECS) and LAN Emulation Server (LES) features of LANE. This guide does not provide procedures for these features. Auspex system software recognizes the LEC interfaces as ael in commands and displays. Setting LEC interface addresses requires a few simple steps including, running the NSconfig(8) command. Note: NSconfig executes the ifconfig’s of network interfaces whether you are running in single or multi-user mode. Caution: Do not alter the ifconfig command lines in the file /etc/rc.boot. NSconfig relies on these command lines to function properly. A reboot after running NSconfig is only required if you are running in multi-user mode, changing the IP address or netmask of a network interface, or the NIS type is changed to master or slave. To configure LEC interfaces 1. Using vi(1) or other editor, edit the /usr/etc/fore/configuration.lane file. Using the following examples as guidelines. Note that “UNIT” means ATM adapter. Example 1: # ELAN=Marketing UNIT=0 (which will create ael0) # In the example, the ELAN name is specified as “Marketing”. Since the UNIT number is not set, it defaults to zero, and the LECS defaults to “-well-known”. Example 2: # ELAN=Finance -1 UNIT=1 (which creates ael16) # ELAN=Finance -2 UNIT=2 (which creates ael32) # ELAN=Finance -3 UNIT=3 (which creates ael48) # In the example, three ELAN names are specified as “Finance”. The UNIT numbers are set to 1, 2, and 3. The LECS defaults to “-well-known”. Example 3: # ELAN=Engineering -3 UNIT=3 (which creates ael49) # Configuring LEC Interfaces ▲ 3-5 Preliminary and Confidential AUSPEX In the example, the ELAN name is specified as “Engineering”. Since Engineering is being configured on the same UNIT, the UNIT number is set to 3 and the LECS defaults to “-well-known”. 2. Run NSconfig(8) to edit the network information for each ael interface, then execute NSconfig with Ctrl-F. The following NSconfig form displays the entries for the LEC interface examples described in step 1: ATM LANE Intf ael0 >UP [host-ael0_] ael0 on-net [100.00.00.0_] ael0 off-net [ffffff00_______]>0 ael16 >UP [host-ael16_] ael16 on-net . . . [100.00.00.1_] ael16 off-net [ffffff00_______]>0 ael32>UP [host-ael32_] ael32on-net . . . [100.00.00.2_] ael32 off-net [ffffff00_______]>0 [100.00.00.3_] ael49 off-net [ffffff00_______]>0 . . . ael48 . . . >Dwn ael49 >UP [host-ael49_] ael49 on-net In the example, interfaces ael0, ael16, ael32, and ael49 are marked UP; interface ael48 is marked DWN. NSconfig automatically launches the ax_elcreate command to create the ael entries from the configuration.lane file. The NSAP address for each interface is automatically determined by ILMI daemon (ax_ilmid). 3. Edit the /usr/kvm/sys/aushp/conf/ file to tune “net interfaces” to create more than 60 LEC addresses. 4. Run the ax_elconfig(8C) command to view the configured interfaces. The server displays the ELAN information for each ael interface; for example: # # # # ax_elconfig ax_elconfig ax_elconfig ax_elconfig show show show show -configured -configured -configured -configured -unit -unit -unit -unit 0 1 2 3 This completes the procedure for configuring LEC interfaces. 3-6 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX 4 Maintenance About This Chapter This chapter provides maintenance information for NP (ATM Release 2). The following topics are covered in this chapter: ▲ Maintenance Utilities ▲ NP (ATM Release 2) and ax_perfmon ▲ Operating Without ILMI Support ▲ Configuring the NetServer as an ATMARP Server ▲ Load Balancing ▲ Removing NP (ATM Release 2) Maintenance ▲ 4-1 Preliminary and Confidential AUSPEX Maintenance Utilities This section describes the maintenance utilities available with the NP (ATM Release 2) software. See the man pages for complete information on these utilities. ax_adinfo(8C) This command displays the hardware and firmware versions of the ATM adapter, media type, and slot number. If the firmware release is 0.0.0, the ATM firmware is not downloaded. ax_atmarp(8C) This command is used for MAC/NSAP address mapping. It has the following functions: ▲ Displays translation table entries ▲ Deletes translation table entries ▲ Routes IP traffic to particular destinations over PVCs. Deleting and routing features have numerous options for fine-tuning NP (ATM Release 2) operations. ax_atmconfig(8C) This configuration tool command for NP (ATM Release 2) devices and has the following functions: ▲ Displays an NP (ATM Release 2) device’s current configuration ▲ Sets the MTU on an interface ▲ Enables and disables IP load balancing ▲ Enables and disables SPANS on a device ▲ Enables and disables IP multicasting on an interface ax_atmlooptest(8C) This command is a diagnostic tool that tests an ATM interface for cell reception and transmission functionality. The test uses the FORE ATM user-level Application Programming Interface (API), which requires configuring the FORE IP interface. The ATM interface needs SPANS signalling turned by using the ax_atmconfig(8C) command. ax_atmstat(8C) This command displays numerous FORE ATM device driver statistics. You can choose to display statistics from the physical layer (TAXI, OC-3), ATM layer, ATM adaptation layer, or the NP (ATM Release 2) device drivers. It also allows you to select an interval to use when gathering the statistics. 4-2 ▲ NP (ATM Release 2) Manager’s Guide AUSPEX Preliminary and Confidential ax_elarp(8C) This command removes dynamic table entries for LECs in the router. ax_elconfig(8C) This command allows the user to manually create LANE client (ael) interfaces. ax_elcreate(8C) This command interprets the definitions from the file /usr/etc/fore/configuration.lane, and automatically creates LANE client interfaces. Maintenance Utilities ▲ 4-3 Preliminary and Confidential AUSPEX NP (ATM Release 2) and ax_perfmon The performance monitoring tool ax_perfmon(8) displays specific information for NP (ATM Release 2) connections. Refer to the ax_perfmon man page for more information. Figure 4-1 displays a portion of the ax_perfmon screen. The NP (ATM Release 2) entry is designated as a00. 1.0 System SummarySrvA Sun Mar 1 15:26:20 1998 CPU Util NFS Bytes/sec HP CPU Util NP1:Bytes/sec SP0:OPs/sec NP0 2%[ ] [ 4524] 33% usr a00[ 211] (0~ 80 bar) NP1 1%[ ] [ 11211] 20% sys f00[ 2081] R1[ ] NP2 0%[ ] [ 3365] 66% idle H00[ 0] [ ] Figure 4-1. Example of an NP (ATM Release 2) entry in an ax_perfmon display 4-4 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Operating Without ILMI Support If ILMI is not supported on a particular switch or host in a given network, then the ATM addresses must be manually configured. If a given switch does not support ILMI, it cannot supply an ATM prefix to the hosts. Therefore, the user must assign a unique, valid prefix to the switch. Additionally, the same prefix should be used for all the hosts in the LIS. Once a network interface ATM address is set, it can be changed by running the ax_atmarp(8C) command to set the new address, and then bringing the interface down and back up (ifconfig aqaxx down; ifconfig aqaxx up) for the ATM address change to take effect. To manually configure ATM addresses for systems without ILMI support 1. Get the network prefix from your ATM switch. 2. Get the network address from your ATM adapter. This can be done by logging in as “root” and running the ifconfig command to obtain the “ether” portion of the display. You can add any selector byte you choose. 3. On the NetServer, run the ax_atmarp command to configure the ATM address for each specified interface. For example: # ax_atmarp -n 0x47.0000.00.ffe100.0000.f21a.1d25.002048062f8b.00 aqa16 In the example, 0x47.0000.00.ffe100.0000.f21a.1d25. is the ATM switch prefix, 002048062f8b is the MAC portion, and .00 is any selector byte you choose. The switch directly attached to this interface is then informed of the address through adapter software and the NetServer can then begin signalling. When ILMI is not supported, you need to manually configure the LEC NSAP addresses while creating the LEC interfaces. See the /usr/etc/fore/configuration.lane file for more information. This completes the procedure for manually configuring ATM addresses for systems without ILMI support. Operating Without ILMI Support ▲ 4-5 Preliminary and Confidential AUSPEX Configuring the NetServer as an ATMARP Server With NP (ATM Release 2), the NetServer can be configured as an ATMARP server. The ATMARP server address is configured using the ax_atmarp -p command. Set up the ATMARP to IP address translations by using the ax_atmarp -o command. Use NSconfig to UP the interfaces and ifconfig to set the IP address and netmask. Load Balancing ATM adapters on an NP can be configured for load balancing. Note: FORE IP interfaces on the same NP must be configured with the same IP address for load balancing. See the NSconfig(8C) or ifconfig(8C) man page for more information. Load balancing can be turned off by using the ax_atmconfig -b off afax command, where x represents the number of the interface. This command turns off load balancing for the NP on which the interface resides. 4-6 ▲ NP (ATM Release 2) Manager’s Guide Preliminary and Confidential AUSPEX Removing NP (ATM Release 2) This section describes how to use the pkgrm(1M) command for removing the NP (ATM Release 2) software from the NetServer. Refer to the pkgrm man page for additional information on how to use this command. To remove the NP (ATM Release 2) package 1. Type the pkgrm command at the system prompt as follows: # pkgrm The system lists installed packages and then prompts you for removing a package. pkgrm session started on Sun Mar 1 15:28:47 PST 1998 The following packages are available: . . Select package(s) you wish to process (or ‘all’ to process all packages). (default: all) [?,??,q]: 2. Type the number of the package you want to remove. The system responds with: The following package is currently installed: AXatm2 ATM 2 HP-VII,HP-VIII) 1.10 Do you want to remove this package? 3. Enter y to remove the NP (ATM Release 2) package. The system responds with: ## Removing installed package instance This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] The system responds with: ## Removing installed package instance This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] 4. Enter y to continue removing NP (ATM Release 2). The system responds with: ## Verifying package dependencies. ## Processing package information. ## Executing preremove script. ## Removing pathnames in class /usr/etc/fore/ax_adinfo /usr/etc/fore/ax_atmarp /usr/etc/fore/ax_atmconfig /usr/etc/fore/ax_atmlooptest /usr/etc/fore/ax_atmstat Removing NP (ATM Release 2) ▲ 4-7 /usr/etc/fore/ax_elarp /usr/etc/fore/ax_elconfig /usr/etc/fore/ax_elcreate /usr/etc/fore/ax_ilmid /usr/etc/fore/ax_ncomm /usr/etc/fore/ax_objcopy /usr/etc/fore/ax_sba200.ucode1 /usr/etc/fore/ax_sba200.ucode2 /usr/etc/fore/ax_sba200e.ucode1 /usr/etc/fore/ax_sba200e.ucode2 /usr/etc/fore/rc.ax_sba200 /usr/man/man4/afa.4 /usr/man/man4/aqa.4 /usr/man/man8/ax_adinfo.8c /usr/man/man8/ax_atmarp.8c /usr/man/man8/ax_atmconfig.8c /usr/man/man8/ax_atmlooptest.8c /usr/man/man8/ax_atmstat.8c /usr/etc/fore/ax_elarp.8c /usr/etc/fore/configuration.lane /usr/etc/fore/ax_elconfig.8c /usr/etc/fore/ax_elcreate.8c /usr/man/man8/ax_ilmid.8c /usr/man/man8/ax_ncomm.8c ## Removing pathnames in class ## Updating system information. Removal of was successful. 5. Type q to exit the pkgrm routine. pkgrm session finished on Sun Mar 1 15:28:50 PST 1998 A log of this session of pkgrm is at /tmp/pkgrm.log on the current root disk, and at /var/log/pkgrm.log on the target disk. This completes NP (ATM Release 2) package removal.
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.2 Linearized : Yes Create Date : 1998:03:09 16:46:47 Producer : Acrobat Distiller 3.0 for Power Macintosh Author : Arlene Edwards Title : atm.book Creator : FrameMaker 5.5 Modify Date : 1998:03:10 12:31:21 Page Count : 44 Page Mode : UseOutlines Page Layout : SinglePageEXIF Metadata provided by EXIF.tools