LCS60 Network Interface for Ethernet R3.
Copyright 1996 Lucent Technologies All Rights Reserved Printed in USA Federal Communications Commission Statement This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instruction manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pursuant to Subject J or Part 15 of FCC rules.
Table of Contents 1 Trademarks 1 Feature Description Document Organization Reference Documentation Apple References Gateway References PPP References SLIP Reference Other References Overview Benefits LAN Protocols TCP/IP Domain Name Server (DNS) Resolver Simple Network Management Protocol (SNMP) Routing Information Protocol (RIP) AppleTalk Protocol AppleTalk Network Number and Zone Assignment IPX Protocol IPX Virtual Network Assignment Remote Access Protocols TCP/Async Gateway Service TCP Service Por
Table of Contents IP Address Assignment by the LCS60 Hardware Features Enhanced Processor Fiber Interface Network Security Copy Protection Administration Backup/Restore R3.
Table of Contents Dialogues Enter Group Name Define the Local Address for the LCS60 Configure the CPM-HS Module Power and Grounding Power-Up Procedures Power-Down Procedures Verify LCS60 Console Connection Verify Fiber Connection Configure the LCS60 LAN Connections Ethernet 3 General LCS60 Software Configuration Introduction Preliminary Hardware Requirements Preliminary Configuration Requirements Specific Services Initial Setup Configure Protocols and Gateway Services — srvsetup Configure Default Route
Table of Contents Dynamically Assigned IP Address Administration Show Session Examples Call Trace Example Log File Related Commands 5 SLIP – Configuration and Administration LCS60 Configuration and Connection for SLIP Service SLIP Service Connection Dialstrings Privately Administered IP Address Reserved IP Address Dynamically Assigned IP Address Administration Stop Example Call Trace Example Errors Log File Related Commands 6 5-1 5-9 5-10 5-11 5-12 5-13 5-13 5-14 5-14 5-14 5-15 ARAP – Configuration
Table of Contents 7 Gateway Services – Configuration and Administration LCS60 Configuration and Connection for Gateway Service Access to Gateway Services – Dialstrings Telnet Service Inactivity Timeout Option Return to DESTINATION Option User Information Async-to-TCP Gateway Service TCP-to-Async Gateway Service UUCP Feature Data Switch to LCS60 to LAN LAN to LCS60 to Data Switch Example UUCP Service Using SunOS 4.0 Example UUCP Service Using NCR 4.
Table of Contents Typical Administrative Tasks Show Session Example Log Level Example Change the Default Route Example Summary Output Examples System Console Parameters– Autobaud Backup and Restore Operations Generic vs.
Table of Contents LCS60 Application Software Installation Removing the LCS60 Application Software Upgrade Remote Upgrade Installing an Upgrade on a Remote Upgrade Client Processor Board Firmware Update Processor Diagnostics - MVME197 VMEDKHS Diagnostics Connection Verification LCS60 to Data Switch Connected Host Verification (dkcu) LCS60 to Data Switch Verification – Loopback Test (dkcu) LCS60 to Local Ethernet Host Verification (ping) Memory Dump After the Dump is Completed A srvtab 9-29 9-29 9-30 9
Table of Contents C User Error Messages Cable Error Message Outgoing Call Error Messages Incoming Error Messages SLIP Sessions D Software Installation – Fujitsu or Seagate ST5660N Drive Reload System Software UNIX System Software Installation E viii C-1 C-1 C-9 C-10 D-1 D-1 Manual Pages ATLOG ATNETSTAT ATPING DKCU DKMAINT FTP IFCONFIG IFSTAT IFTRACE IPXNETSTAT IPXPING NETSTAT NSLOOKUP PING PULL PUSH ROUTE STATLCS TELNET E-1 E-2 E-4 E-6 E-8 E-9 E-19 E-21 E-24 E-26 E-27 E-28 E-30 E-34 E-35 E-37 E-40
Table of Contents F User Information Introduction Client Software Configuration Client Packages Mac Connection – CCL Script CCL and Modem Hints CCL Modem PPP Service Examples Windows 95 – IPX over PPP PC Configuration PPP Connection WIN PC/TCP 3.0 PC Configuration PPP Connection InterPPP Connection SLIP Service Examples ChameleonNFS 4.
Table of Contents Manager Directory Server Directory I x G-19 G-19 Index Index I-1 Issue 2
Figures Figure 1-1: Figure 1-2: Figure 1-3: Figure 1-4: Figure 1-5: Figure 2-1: Figure 2-2: Figure 2-3: Figure 2-4: Figure 2-5: Figure 2-6: Figure 2-7: Figure 3-1: Figure 3-2: Figure 3-3: Figure 4-1: Figure 4-2: Figure 5-1: Figure 5-2: Figure 6-1: Figure 6-2: Figure 7-1: Figure 7-2: Figure 8-1: Figure 9-1: Figure 9-2: Figure F-1: Figure F-2: Figure F-3: Figure F-4: Figure F-5: Figure F-6: Figure F-7: Issue 2 LCS60 as an AppleTalk Router AppleTalk Virtual Zone IPX Virtual Network IP Routing with the LCS60
Table of Contents Figure F-8: PPP Connection Screen Figure F-9: AppleTalk Status Window Figure F-10: Custom Interface Window Figure F-11: Custom Setup Window Figure F-12: Login Settings Window Figure F-13: ARAP Remote Connection – Example Figure F-14: ARAP Remote Access Setup – Connection Screen Figure F-15: ARAP Remote Access Setup – Modem Example Figure F-16: ARAP Remote Access Status Screen – Example xii F-18 F-18 F-19 F-20 F-20 F-23 F-23 F-24 F-25 Issue 2
Tables Table 1-1: Table 2-1: Table 2-2: Table 2-3: Table 2-4: Table 2-5: Table 2-6: Table 3-1: Table 3-2: Table 3-3: Table 7-1: Table 8-1: Table 8-2: Table 8-3: Table A-1: Table A-2: Table A-3: Issue 2 Online Manual Pages Controls and Indicators Specifications Required Additional Equipment System Console (and Port) Configuration MVME712M Module Optioning RS-232 Interface Protocol and Services Commands Configuration Commands – Config Directory Administrative/Maintenance Commands – Config Directory Gateway
Table of Contents xiv Issue 2
Screens Screen 2-1: TY Configuration Dialogue Screen 2-2: MSM Configuration Dialogue Screen 3-1: LCS60 Top Directory Screen 4-1: Configure IP Network Security Group – Example Screen 4-2: Configure Reserved IP Address – Example Screen 4-3: Configure IPX Parameters – Example Screen 4-4: Configure AppleTalk Virtual Network – Example Screen 4-5: Configure the Ethernet Interface – Example Screen 5-1: Configure IP Network Security Group – Example Screen 5-2: Configure Reserved IP Address – Example Screen 5-3: Co
Table of Contents Screen 9-4: Screen 9-5: Screen 9-6: Screen 9-7: Screen 9-8: Screen D-1: Screen F-1: Screen F-2: Screen F-3: xvi LCS60 Application Software Installation LCS60 Application Software Removal – R2.0 Example set and env Commands Example diag cpm for CPM-HS Module Service Menu How to Enter System Responses CCL Script – Example Sample LCS60 dialup.scr slip.
1 Feature Description Document Organization 1-1 Reference Documentation 1-2 1-3 1-3 1-4 1-4 1-4 Apple References Gateway References PPP References SLIP Reference Other References Overview Benefits LAN Protocols TCP/IP Domain Name Server (DNS) Resolver Simple Network Management Protocol (SNMP) Routing Information Protocol (RIP) AppleTalk Protocol AppleTalk Network Number and Zone Assignment IPX Protocol IPX Virtual Network Assignment Issue 3 1-4 1-5 1-6 1-6 1-6 1-6 1-7 1-7 1-8 1-9 1-9 i
Table of Contents Remote Access Protocols TCP/Async Gateway Service TCP Service Ports Serial Line IP (SLIP) Point-to-Point Protocol (PPP) Van Jacobson TCP/IP Header Compression Compressed IPX Header (CIPX) AppleTalk Remote Access Protocol (ARAP) Multiple IP Subnetworks ii 1-10 1-10 1-11 1-11 1-12 1-12 1-13 1-13 IP Routing Security Groups 1-13 1-13 1-15 IP Address Assignment by the LCS60 1-17 Hardware Features Enhanced Processor Fiber Interface 1-17 1-17 1-18 Network Security 1-18 Copy Protect
Table of Contents Administration Issue 3 Backup/Restore R3.
Table of Contents iv Issue 3
Document Organization Features This installation and administration guide is arranged as follows: Feature Description Chapter 1 describes the LCS60 and its supported services. Hardware Installation Chapter 2 gives all the information needed to install the LCS60. General Software Configuration Chapter 3 details the basic configuration procedures for the LCS60 and gives examples of configuring the supported services (PPP, SLIP, ARAP, Gateway).
Features Document Organization Software Installation This appendix gives instructions for installing UNIX System software on LCS60 machines with Fujitsu Drives and with Seagate 5660N Drives. Man Pages Appendix E includes copies (listed alphabetically) of selected man pages provided on-line with the LCS60. User Information Appendix F provides examples of software packages that may be used with the LCS60.
Reference Documentation CommKit Internal Interface Specification, select code 700-283. Order these manuals from the Customer Information Center, P.O. Box 19901 Indianapolis, IN 46219, 1-800-432-6600 (USA), 1-800-255-1242 (Canada), 1-317-352-8557 (other areas), or contact your Lucent Technologies account executive (AE). Apple References When using the LCS60 with AppleTalk or ARAP, the following references may be useful: Inside AppleTalk, Second Edition, G.S. Sidhu, et.
Features Reference Documentation PPP References RFC 1549, PPP in HDLC Framing RFC 1548, The Point-to-Point Protocol (PPP) RFC 1378, The PPP AppleTalk Control Protocol (ATCP) RFC 1332, The PPP Internet Protocol Control Protocol (IPCP). RFC 1552, The PPP Internetwork Packet Control Protocol (IPXCP). RFC 1553, Compressing IPX Headers over WAN Media (CIPX). SLIP Reference RFC 1055, Nonstandard for Transmission of IP Datagrams over Serial Lines (SLIP).
Overview The LCS60 provides high-speed connectivity between Ethernet networks and the Lucent Technologies family of data switches (Datakit II VCS 2.1 or greater, BNS1000, and BNS-2000). Each LCS60 has the following components: A CPU board to run the LCS60 software and to provide one Ethernet LAN interface A VMEDKHS board to provide a fiber interface to the data switch CPMHS trunk board Communication between boards within the LCS60 is handled over a VME bus.
Features LAN Protocols TCP/IP IP traffic is commonly associated with the Department of Defense (DOD) TCP/IP suite and is often run over Ethernet LANs. The LCS60 allows asynchronous endpoints, such as a terminal or host connected to a data switch, to log onto any Ethernet TCP/IP LAN host by using the LCS60’s async-to-TCP gateway service. The LCS60 provides the terminal user with an interface to the TCP/IP telnet command, which allows the network user to remotely log onto LAN hosts via a virtual terminal.
LAN Protocols The LCS60 supports the standard SNMP management information base (MIB-II). Refer to RFC 1213. Supported Traps and MIBs The generic traps that are supported are: 0 = cold start 2 = link down 3 = link up 4 = authentication failure Routing Information Protocol (RIP) The LCS60 supports RIP processing, i.e., handling IP routing information through the use of routed. routed maintains the route table used by IP to determine the interface through which to send packets.
Features LAN Protocols Figure 1-1: LCS60 as an AppleTalk Router LCS60 (AppleTalk Router) ARAP PPP CommKit Host Interface ELAP* Ethernet * EtherTalk Link Access Protocol. EtherTalk is Apple’s data link protocol that allows Ethernet cables to be used to connect an AppleTalk network. AppleTalk Network Number and Zone Assignment The LCS60 supports dynamic AppleTalk address assignment within a virtual zone of PPP and ARAP clients. (Refer to Figure 1-2.
LAN Protocols It is not necessary to configure the LCS60’s Ethernet interface for AppleTalk. The LCS60 is not a seed router on the Ethernet. It will discover the network range and the zones assigned to the Ethernet by another router and will dynamically acquire a unique AppleTalk node address within the assigned network number range. IPX Protocol The IPX protocol is used to connect hosts in a Novell network.
Features Remote Access Protocols TCP/Async Gateway Service The LCS60 provides a gateway service such that a terminal user connected to the data switch network either directly or through a modem can reach LANconnected hosts/workstations – this is the async-to-TCP gateway service. The LCS60 provides communication in the other direction – from the LAN-host to the data switch – with the TCP-to-async gateway service.
Remote Access Protocols Refer to Chapter 7 for configuration of gateway services. TCP Service Ports A TCP service port is identified by a port number and can be customized to streamline the transition from the TCP/IP network to the data switch network. These ports can be configured with predefined destinations (PDDs), disconnect options, window size changes, time limit options for the DESTINATION: prompt and for data transmission, and customized destination prompts.
Features Remote Access Protocols The total combined number of remote access sessions – when SLIP, PPP, and/or ARAP are configured – available through the LCS60 is 120. Refer to Chapter 5 for configuration of the LCS60 for SLIP service. Point-to-Point Protocol (PPP) PPP provides point-to-point connectivity between a remote PC or Macintosh and a LAN host, and is the industry standard. It is designed to carry multiple protocols such as TCP/IP, XNS, IPX, AppleTalk, and DECnet.
Remote Access Protocols Negotiation of the IPX header compression option is defined in RFC1553. If your client package supports Compressed IPX Headers (CIPX), then configure this feature on your PC. The size of each packet can shrink up to 34 bytes, thereby giving your PPP session a significant performance boost. AppleTalk Remote Access Protocol (ARAP) ARAP is used to obtain direct access to AppleTalk resources at remote locations.
Features Multiple IP Subnetworks Figure 1-4: IP Routing with the LCS60 LAN Segment Security Group: Techs (virtual) 154.12.25 LAN Segment Security Group: Library (virtual) 154.12.24 Ethernet LAN morse-e0 (physical) 154.12.21 Lucent Data Switch Network LCS60 morse LAN Segment Security Group: morse (virtual) 135.12.23 CommKit Host Interface Note: The numbers shown are IP network numbers. The LCS60 reserves host address .1 for each virtual LAN segment (e.g., 154.12.24.1).
Multiple IP Subnetworks The LCS60 provides a mechanism for allocating IP addresses from one or more pools of addresses. Each address pool is associated with a unique IP network security group and is used to limit user access to the LAN. This feature allows the LCS60 administrator to define up to four IP networks that an LCS60 user can select when dialing in for either SLIP service or IP over PPP service. Each IP network is associated one for one with a dkserver service name.
Features Multiple IP Subnetworks Figure 1-5: IP Address Assignment Is this IP address out of range? Incoming Call Error: IP address is not correct Y N IP address privately administered on PC? Is this IP address busy? Y N N Was user ID specified on dialstring? Is this IP address reserved? Y Error: IP address is reserved Y N Grant requested IP address N Set user id to "guest" -D option on dialstring? Error: IP address is not available Y Search for reserved IP address with IP Network se
Multiple IP Subnetworks PPP and SLIP users need to be assigned an IP address when they connect to the LCS60, thereby allowing them to run TCP/IP applications over their serial connection. Figure 1-5 describes IP address assignment; refer to Chapter 4 (PPP) or Chapter 5 (SLIP) for more information. Note: IP address assignment is defined in RFC1332. The LCS60 has three mechanisms for assigning a SLIP or PPP user an IP address: 1 . Privately Administered Static IP Address.
Features Hardware Features Fiber Interface The LCS60 supports a single multiplexed fiber interface to the data switch CPMHS module. This is a distinct advantage in terms of cable management and efficiency over traditional terminal servers which require separate asynchronous connections. Network Security Complete network security is achieved through the Lucent Technologies Network Access Control (NAC) System.
Copy Protection Administration The LCS60 has its own local management software package called lcsadm. This package allows a network administrator to configure services, administer service sessions, and collect performance measurement data. This administration tool can be accessed either through the LCS60 console port or through the multiplexed fiber interface. Note: The remote administration feature is delivered in the disabled state. Instructions for enabling this feature are given in Chapter 8.
Features Administration R3.0 Upgrade Previous releases of the LCS60 can be upgraded to Release 3.0. This requires removing the software and any patches for the earlier release and installing the R3.0 software from tape. Upgrade procedures are given in Chapter 9. The configuration is automatically restored after installing R3.0; the user need only configure new or changed services. Note: When upgrading from R1.0 or R2.0 to R3.0, you must have an R3.0 software key to activate R3.0 features.
Manual Pages Table 1-1: Online Manual Pages ________________________________________________ ________________________________________________ Commands Protocol Path General dkcu /opt/dk/bin/dkcu dkmaint /opt/dk/sbin/dkmaint ifstat /usr/bin/ifstat iftrace /usr/etc/iftrace push /usr/bin/push pull /usr/bin/pull ________________________________________________ statlcs /usr/etc/statlcs TCP/IP ftp /usr/etc/ftp ifconfig /u
Features Manual Pages # man command where command is the name of the command. Customer Assistance Technical support is available for the LCS60 from the Lucent Technologies Customer Technical Support Center at 1-800-WE2CARE.
2 Hardware Installation Introduction Controls and Indicators Site Preparation Space Requirements Cabling EMI Considerations Required Equipment Assembly Unpacking Installing the LCS60 Rack Mounting Wall Mounting Table-Top Mounting Connecting the System Console Serial Port Optioning (DTE/DCE) Direct Connection to the LCS60 Connection through a Data Switch Connection through Modems Connection through StarKeeper II NMS Connecting the Fiber Interface Routing the Optical Fiber Cable Installing the CPM-HS Mo
Table of Contents Configuration of the Lucent Technologies Data Switch – LCS60 Dialogues Enter Group Name Define the Local Address for the LCS60 Configure the CPM-HS Module Power and Grounding Power-Up Procedures Power-Down Procedures Verify LCS60 Console Connection Verify Fiber Connection Configure the LCS60 LAN Connections Ethernet ii 2-21 2-22 2-22 2-22 2-24 2-25 2-25 2-27 2-27 2-28 2-29 2-29 2-29 Issue 3
Introduction The LCS60 is supplied with the operating software already installed; therefore, installation consists mainly of installing hardware and configuring the system. The list below identifies the tasks, in the order that they should be performed, to install and configure the product. These tasks are discussed in detail in the following sections. 1 . Mount the LCS60 Hardware 2 . Attach the console to the LCS60 3 . Connect the fiber between the LCS60 and the CPM-HS 4 .
Hardware Introduction Table 2-1: Controls and Indicators ______________________________________________________________________ Controls ______________________________________________________________________ Location Switch Function ______________________________________________________________________ Rear Panel Power ________________________________________________________ Power ON/OFF SYSTEM RESET Processor and VME bus reset ____________________________________________
Site Preparation Issue 3 Hardware Table 2-2: Specifications ________________________________________________________ ________________________________________________________ LCS60 Network Interface for Ethernet 90 to 132 VAC (47 to 63 Hz), 5 Amps Power Requirements 180 to 250 VAC (47 to 63 Hz), 2.
Site Preparation Space Requirements Hardware The LCS60 can be rack mounted, wall mounted, or installed on a secure surface. The unit is 7 × 17 × 19 inches and weighs 40 lbs. A minimum of 12 inches of clearance is required at the front and rear of the unit for access, and a minimum of two inches of clearance at the sides of the unit to permit proper airflow through the unit. Cabling WARNING: Connect and disconnect cables ONLY when the power is off.
Site Preparation EMI Considerations Required Equipment The LCS60 is shipped in the hardware configuration ordered, the operating software loaded, and user documentation included. Additional equipment required for the initial installation of an LCS60 is listed in Table 2-3.
Assembly Hardware Unpacking The LCS60 hardware comes fully assembled, with the exception of two handles that mount on the front frame of the enclosure. After opening the shipping container, remove the documentation package, system software tapes and diskettes and package of loose parts. Carefully remove the LCS60 unit. Open the front cover of the LCS60 and check that the system is equipped as ordered and that all circuit packs are fully seated in the LCS60 card cage.
Installing the LCS60 2 . With the horizontal support in place, slide the LCS60 into place. Fasten the front frame of the LCS60 to the front uprights with four screws (23- or 25-inch cabinets require extension brackets). Figure 2-1: Mounting the LCS60 Cabinet Hardware WALL Cabinet Rear uprights TOP Disk and tape drives must be on top .. .... .. . . . ....... .. .. .. .. .. .. .. . . .. . . . . LCS60 mounts inside Wall Mount Assembly BOTTOM Front Frame .. .. Wall Mount Assy.
Installing the LCS60 Wall Mounting Wall mounting the LCS60 requires a Wall Mount Assembly to position the unit vertically as shown in Figure 2-1. Hardware Wall mounting requires a surface 45 inches wide by 21 inches high covered by a securely-fastened ¾-inch plywood sheet (or a comparably stable mounting surface). The handles for the LCS60 are shipped in a separate package within the main shipping box.
Installing the LCS60 Connecting the System Console WARNING: Connect and disconnect cables ONLY when the power is off. The LCS60 uses a system console to run diagnostics, receive error messages, and for administration. Configure the console as shown in Table 2-4.
Hardware Installing the LCS60 Table 2-5: MVME712M Module Optioning _____________________________________________________ _____________________________________________________ Default Optioning Ext.
Installing the LCS60 Issue 3 2-11 Hardware Table 2-6: RS-232 Interface ___________________________________________________________________ ___________________________________________________________________ Pin Designation Direction Function BA Port 1 2 TD-Transmit Data To DCE BB 3 RD-Receive Data From DCE CA Async DTE 4 RTS-Request To Send To DCE 5 CTS-Clear To Send From DCE CB Emulation 7 AB Signal Ground CD
Installing the LCS60 Direct Connection to the LCS60 To connect an asynchronous terminal or PC directly to the LCS60 for use as an LCS60 console, refer to Figure 2-3 and follow the steps below: Hardware 1 . Serial Port 1 should be optioned to emulate DCE operation. This is the default; therefore, if you haven’t changed anything there will be no need to change the option. 2 .
Installing the LCS60 1 . Serial Port 1 should be optioned to emulate DCE operation. This is the default; therefore, if you haven’t changed anything there will be no need to change the option. 2 . Connect the LCS60 rear panel connector labeled "Serial Port 1" to an asynchronous port using a straight-through connection (D8AH connector); connect the 25-pin end to the LCS60. a . Configure a group on the data switch network for the asynchronous port connected to the LCS60 b .
Installing the LCS60 Hardware Screen 2-1: continued PORT NUMBER [1-12: +(1-12)]: 11 COMMENT [up to 60 chars double quoted]: "console for lcs60 morse" SERVICE TYPE[console, dialer, host, modem, 2way, or terminal:+(terminal)]: console GROUP [up to 8 chars]: gmorscon BAUD RATE [300, 1200, 9600, ext, auto: +(9600)]: Return EXTERNAL BAUD RATE [2400, 4800, 19200: +(2400)]: Return PARITY [off, even, odd: +(off)]: Return FLOW CONTROL OF TY-12 BY DEVICE [xon_xoff, eia, none: +(none)]: Return FLOW CONTROL OF DEVIC
Installing the LCS60 Screen 2-2: continued Hardware DIRECTION [originate, receive, 2way]: receive DEVICE OR HOST [up to 8 chars: +(standard)]: morscon HOST AUTOBAUD [on, off: +(off)]: off ROUND ROBIN SERVICE [per_port, per_module, none: +(none)]: Return Creating New Host: morscon CC0> enter msm COMPONENT [module, port]]: p MODULE ADDRESS: 18 PORT NUMBER [1-12: +(1-12)]: 11 CC0> enter group GROUP [up to 8 chars]: gmorscon CONNECTED TO 2-WIRE MODEM [yes, no: +(no)]: Return BAUD RATE [75, 110, 150, 300, 120
Installing the LCS60 Note: There are small variations in system prompts and responses depending on the release of the Lucent Technologies data switch (Datakit II VCS or BNS). Hardware 4 . Power-up the system console terminal or PC and set the options as directed in Table 2-4. 5 . Connect an asynchronous terminal or PC to an asynchronous port on the data switch, using a null-modem connection (D8AG connector).
Installing the LCS60 Connection through Modems To connect an asynchronous terminal or PC to the LCS60 for use as a system console by means of modems, refer to Figure 2-5 and follow the steps below: 1 . Option Serial Port 1 to emulate DTE operation. (Refer to the section Serial Port Optioning earlier in this chapter.) 3 . Power up the system console and set options as directed in Table 2-4. 4 . Continue with the Connecting Fiber Interface section.
Installing the LCS60 2 . Connect the LCS60 rear panel connector labeled "Serial Port 1" to an asynchronous port on the data switch using a straight-through connection (D8AH connector); connect the 25-pin end to the LCS60. Hardware 3 . Configure the asynchronous port on the data switch according to Table 2-4 as a receiving group. Conduct the dialogue shown in Screen 2-1 (TY12) or Screen 2-2 (MSM) on the data switch console to: a .
Installing the LCS60 Connecting the Fiber Interface Connection to the data switch network for data communications is by means of a dual optical fiber cable. The network LCS60 fiber connection must be to a CPMHS module in a Datakit II VCS or BNS. For network connection follow the steps below: The optical fiber cable may be run in suspended ceilings, subfloor cable runs, and riser shafts up to 500 feet.
Installing the LCS60 Cables are placed in a single conduit having not less than ¾-inch inner diameter Hardware The pull force on an optical fiber cable does not exceed 50 pounds per cable. Optical fiber cables should not be pulled through more than four 90-degree bends, if more than four such bends are required, provide intermediate help points. The minimum recommended conduit bend radius is 4-½ inches.
Installing the LCS60 Remove the rubber caps from the optical fiber cable that runs from the receiver side of the LCS60, and connect the optical fiber cable to the transmitter side (bottom connector) of the CPM-HS module in the data switch. 5 . Set the MODE toggle switch on the CPM-HS faceplate to ENABLE. 6 . Set the Loopback switch on the CPM-HS paddleboard to NORM.
Installing the LCS60 Dialogues Note: Dialogues differ depending on the data switch and release. Hardware Enter Group Name CC0> enter group GROUP [up to 8 chars]: morse TYPE [local, trunk: +(local)]: local DIRECTION [originate, receive, 2way]: 2way DEVICE OR HOST [up to 8 chars]: morse PASSWORD [up to 8 chars, none: +(none)]:none ROUND ROBIN SERVICE [per_port, per_module, none: +(none)]: none GROUP [up to 8 chars]: Delete CC0> Conduct the appropriate dialogue as shown in screen above.
Installing the LCS60 Hardware CC0> enter address LEVEL [local, area, exchange, local, speedcall: +(local)]: local TYPE [x121, mnemonic, both: +(mnemonic)]: mnemonic MNEMONIC ADDRESS [up to 8 chars]: morse PAD SUPPORT [yes, no: +(no)]: Return DIRECTORY ENTRY [up to 30 chars double quoted, none: +(none)]: "name of the LCS60" GROUP(S) [up to 4 groups separated by commas, none: +(none)]: morse ORIGINATING GROUP NAME SECURITY PATTERN(S) [comma-separated pattern list, same_as, none: +(none)]: Return INITIAL SER
Hardware Installing the LCS60 address This is the IP network security group name. The first address entered must be the the same as the node name that is assigned to the LCS60 when the LCS60, itself, is subsequently configured from the LCS60’s system console. Up to four security groups may be configured for the LCS60, therefore, four corresponding local addresses may be defined. PAD This is not used. directory entry A 30-character description of the LCS60 in double quotes.
Installing the LCS60 A description of the entry. hardware type The fiber interface hardware for the LCS60 always connects to the CPM-HS. connect-time Specifies if billing information is to be logged. number of channels Enter 512. connect time billing This is not used for the LCS60. Single or multiple Enter single. group Enter the group from the previous operation. Endpoint This is not used for the LCS60. restore The CPM-HS module must be restored to service before it can be used.
Installing the LCS60 Figure 2-7: LCS60 Rear Panel AC Connections To Asynchronous Terminal Hardware Coaxial Cable Serial Port 1 (console) System Reset Serial Port 3 See Inset for AC and DC connections TX Serial Port 2 SCSI TTY01 Interface Serial Port 4 Ethernet Printer RX Ethernet Transceiver Cable To Ethernet Transceiver or Multipoint Transceiver Unit Fiber to Data Switch CPM-HS On/Off Switch On/Off Switch Fuse DC Connection AC Connection 110 VAC Power -48 VDC Power Source 2-26 Issue 3
Installing the LCS60 Power-Down Procedures Only a user logged on as root may shut the system down at the system console. When logged on as a user, log off and log back on as root (refer to Chapter 8). (As shipped, the root password is the Return key.) At the root prompt (#), enter: /etc/shutdown -g0 -y -i0 Caution: Use the correct procedure to power down the system.
Installing the LCS60 Through Modems – console and modem optioning and cabling Through StarKeeper II NMS – check the console and LCS60 connections to the data switch network and the related data switch configuration. Hardware 3 . If the STATUS and RUN LEDs on the MVME197 are on solid, contact your service representative. Caution: Use the exit command or ctrl-d to log off the system console, and use a break-break sequence to disconnect.
Installing the LCS60 Configure the LCS60 Configure the LCS60 as directed in Chapters 3 through 7. Hardware LAN Connections Ethernet Connections to an Ethernet LAN are made by a standard DB15 Ethernet transceiver cable. The MVME197 processor board supports a single LAN connection. Refer to Figure 2-7 and follow the steps in the procedure below to connect the LAN to an LCS60. Label all connections. This data is required for correct configuration. 1 .
Hardware LAN Connections 2-30 Issue 3
3 General LCS60 Software Configuration Introduction Preliminary Hardware Requirements Preliminary Configuration Requirements Specific Services 3-1 3-1 3-2 3-3 Initial Setup 3-3 Configure Protocols and Gateway Services — srvsetup 3-10 Configure Default Route, DNS, and SNMP Default Route – dftroute* Domain Name Server – dns SNMP Manager – snmp Starting the LCS60 Base Level Backup Issue 3 3-23 3-24 3-25 3-26 3-27 3-27 i
Table of Contents ii Configuration Changes 3-28 Administrative and Maintenance Commands 3-29 Issue 3
Introduction This chapter describes the steps required for configuring the LCS60 software. An example of a network topology is shown in Figure 3-1. Figure 3-1: Example Network LCS60 Mac Lucent Data Switch Modem Pool Mac LCS60 Software } LCS60 Mac 78:1FC (IPX) Remote Access Clients LAN Note: Refer to Chapters 4, 5, 6, and 7 for examples of PPP, SLIP, ARAP and gateway configurations. LCS200 Router Note: All addresses and names in this figure are examples only.
Introduction Verify that the following procedures have been followed: 1 . The LCS60 is securely mounted as described in Chapter 2. 2 . There is a fiber pair connection between the LCS60 and the CPM-HS module in the data switch node. 3 . A grounded power cord is attached to the power input jack on the rear panel of the LCS60. 4 .
Introduction Specific Services The instructions in this chapter describe the configuration of some of the available services on the LCS60. For details of configuring a specific service, refer to the appropriate chapter: PPP (Chapter 4), SLIP (Chapter 5), ARAP (Chapter 6), gateway services (Chapter 7). Initial Setup Note: Fill-in the "Installer, Administrator, and Hardware Site" information on your LCS60 Network Interface for Ethernet Software Certificate (included in your LCS60 package).
Initial Setup Caution: You have super-user permission and could inadvertently change/delete any and all files, therefore, it is important that you follow these steps verbatim. Step 5 Assign a password to root by using the passwd root command. The password must contain at least six characters. Only the first eight characters are significant; longer passwords can be used but the additional characters are ignored.
Initial Setup WARNING: "lcsadm" configuration is already in progress. cause catastrophic results! Continuing can Do you want to continue? [y/n] The lcsadm interface takes you into a hierarchical system of directories and commands. (For example, Screen 3-1.) Step 7 Screen 3-1: LCS60 Top Directory sysV68:Top> Return Commands may be abbreviated.
Initial Setup Top># config Top>Config># Return Commands may be abbreviated. addhost datetime etherif manager/ quit srvports viewhosts addnet delhost help maxsessions service/ srvsetup viewnets Commands are: atalkas delnet initsetup nodename session/ subnet ^ backup dftroute ipas ports/ snmp top/ ! console dns ipx protocol softwarekey upgrade LCS60 Software Top>Config># init Step 10 Enter init (at Top>Config>) to start the initsetup routine.
Initial Setup *** This step allows the LCS60 Administrator to enter the software key for this *** LCS60 in order to activate the appropriate software features. SOFTWARE KEY CONFIGURATION PARAMETERS 1. Display LCS60 Machine ID 2. Enter Software Certificate and Software Key 3.
Initial Setup Enter 2 on the screen above and continue with initsetup as shown below. Note: If a software key already exists on the LCS60, you will receive a message asking if you want to retain it or delete it and enter a new one. If a software key exists, entry of a new one is not necessary unless you are upgrading to a new release that requires a different key. Answer y to keep the current key or n to discard it and enter a new one.
Initial Setup Note: You must have the appropriate key to activate the features on your LCS60. The R1 key will activate gateway services and the IP protocol feature, R2 activates the R1 features and the AppleTalk protocol feature, and the R3 key will activate all R2 features and the IPX protocol. After completing the steps in initsetup, you must complete the configuration of your LCS60 by adding the protocols and services you will be using.
Configure Protocols and Gateway Services — srvsetup After executing the initial setup procedures above, configure the protocols and gateway services using the srvsetup command (Figure 3-3). Figure 3-3: srvsetup srvsetup configure protocols/services protocol select protocols and services: asytcp, tcpasy, etc.
Configure Protocols and Gateway Services — srvsetup Top>Config># srvset LCS60 Protocols and Services Configuration Procedure The "srvsetup" procedure leads you through the steps to configure the LCS60 protocols and services. Before you run "srvsetup", you should read about LCS60 configuration in the "LCS60 Network Interface Installation and Administration Guide" and assemble the information required for configuration.
Configure Protocols and Gateway Services — srvsetup Enter Menu Selection [? for help, q to quit, RETURN for menu] ==> q *** This step allows the LCS60 Administrator to define the maximum number of *** sessions for each configured service. CAUTION: Please refer to the I&A Guide for instructions about configuring this feature. LCS60 AND SERVICE SESSION PARAMETER CONFIGURATION MENU 1. Add/Change a Session Parameter 2. Delete a Session Parameter 3.
Configure Protocols and Gateway Services — srvsetup Enter Menu Selection [ Type q to QUIT or ? for HELP ] ==> 1 Enter session parameter: "maxsessions", "ppp", "slip", "arap", "asytcp", "tcpasy" [ Type q to QUIT or ? for HELP ] ==> ppp Enter session parameter value [ Type q to QUIT or ? for HELP ] ==> 90 NOTICE: Entering < ppp > service with value of < 90 > Is this correct? Enter y,n ==> y CAUTION: Please refer to the I&A Guide for instructions about configuring this feature.
Configure Protocols and Gateway Services — srvsetup [ Type q to QUIT or ? for HELP ] ==> 1 Enter session parameter: "maxsessions", "ppp", "slip", "arap", "asytcp", "tcpasy" [ Type q to QUIT or ? for HELP ] ==> slip Enter session parameter value [ Type q to QUIT or ? for HELP ] ==> 80 NOTICE: Entering < slip > service with value of < 80 > Is this correct? Enter y,n ==> y CAUTION: Please refer to the I&A Guide for instructions about configuring this feature.
Configure Protocols and Gateway Services — srvsetup The following prompts (ipas) will be displayed only if SLIP or PPP is configured. Note: *** *** *** *** This step allows the LCS60 Administrator to configure the IP address server, which is used by < ppp slip > for both the static and dynamic allocation of IP Addresses. Since one or more of these services is currently configured, IPAS must be configured. CAUTION: Please refer to the I&A Guide for instructions about configuring this feature.
Configure Protocols and Gateway Services — srvsetup IP NETWORK SECURITY GROUP MANAGEMENT FOR SLIP AND PPP SERVICES 1 2 3 4 Add an IP Network Security Group Delete an IP Network Security Group Edit an IP Network Security Group Display all IP Network Security Groups Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 Enter an IP Network Security Group name [q to quit, ? for help] ==> Library Enter an Internet network address [q to quit] ==> 154.12.24 ==> Is [154.12.24.
Configure Protocols and Gateway Services — srvsetup *** *** Class B IP Address: 154.12.25 *** Network Mask: 255.255.255.
Configure Protocols and Gateway Services — srvsetup Added reserved IP address [ 154.12.23.
Configure Protocols and Gateway Services — srvsetup Enter Menu Selection [ Type q to quit or ? for help ] ==> 1 *** The AppleTalk virtual network has not yet been configured. Enter the network number for the LCS60 interface to the AppleTalk network. This must be a number between 1 and 65279, and must NOT be equal to any other network number in use in the AppleTalk network, and must not be contained within any other network number range in use in the AppleTalk network.
Configure Protocols and Gateway Services — srvsetup 1 2 3 Configure an Ethernet Interface Delete an Ethernet Interface Display all Interfaces that are configured Enter Menu Selection [? for help, q to quit, RETURN for menu] ==> 1 WARNING !! This option will automatically delete each interface that was previously configured. It reconstructs the Ethernet interface database from scratch and requires the user to reconfigure each interface again.
Configure Protocols and Gateway Services — srvsetup The following prompts (ipx) will be displayed only if IPX is configured. Note: *** This step allows the LCS60 Administrator to configure the IPX protocol for *** the Ethernet interface and define the virtual IPX network for PPP. Since *** the IPX protocol is selected, it must be configured. CAUTION: Please refer to the I&A Guide for instructions about configuring this feature.
Configure Protocols and Gateway Services — srvsetup 2 Configure/Display Framing Type Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> q CAUTION: Please refer to the I&A Guide for instructions about configuring this feature.
Configure Protocols and Gateway Services — srvsetup ==> 3 The LCS60 IPX Parameters are configured as follows: Ethernet Network Number ..... < 1562 > Virtual Network Number ...... < 57 > Ethernet Frame Type ......... < Ethernet II > CAUTION: Please refer to the I&A Guide for instructions about configuring this feature.
Configure Default Route, DNS, and SNMP Default Route – dftroute* Use the dftroute command to define the default route as shown in the example below. The default route may be entered either as a host name or as a TCP/IP dotted numerical address (e.g., holmes or 154.12.21.3). The host name entered as the default router must exist in the LCS60 configuration database; use the addhost command to add the host as necessary. Top>Config># dftroute CURRENT default route is . . . . . . .
Configure Default Route, DNS, and SNMP Domain Name Server – dns Use dns to define the Domain Name Server as shown in the example below. Top>Config># dns DOMAIN NAME SYSTEM (DNS) CONFIGURATION 1 2 3 Display Current Configuration Modify/Create DNS Resolver Configuration Enable/Disable DNS Enter Menu Selection [? for help, q to quit] ==> 2 Enter Domain Information [?, q] ==> ny.att.com Enter Name Server [?, q] ==> 154.12.21.110 LCS60 Software Enter Name Server [?, q] ==> 154.12.48.
Configure Default Route, DNS, and SNMP [? for help, q to quit] ==> q Top>Config># Be sure to specify routed with the protocol command to start DNS service at boot time. SNMP Manager – snmp LCS60 Software Use the snmp command to define the SNMP manager as shown in the example below.
Configure Default Route, DNS, and SNMP IP address of SNMP manager for community "traps" [?, q] ==> 154.12.21.2 Access right for SNMP manager "154.12.21.2" [r, w, t, ?, q] ==> t Adding the following information to the configuration file: community traps 154.12.21.2 traps Confirm? [y, n] y Enter Community Name [?, q] ==> q Top>Config> # Note: Supported traps are listed in Chapter 1. Refer to RFC1213 for supported MIBs.
Configuration Changes A variety of commands are available to review the configuration. Commands such as viewnets and viewhosts are available from the Config directory. Commands show, types, and summary are also available to check the current configuration before making configuration changes. Refer to Chapter 8 for details of these commands. LCS60 Software The configuration database may be changed at any time by using commands available from the Config directory. Table 3-2 lists the configuration commands.
Configuration Changes Note 2: The addhost and viewhosts commands display only the hosts configured in the local system database. If DNS is used on your system the nslookup command can be used to display host information. Administrative and Maintenance Commands In addition to the commands described in the previous sections, the following administrative/maintenance commands are also available from the Config directory. Refer to the chapter listed in Table 3-3 for details of these commands.
LCS60 Software Administrative and Maintenance Commands 3-30 Issue 3
4 PPP – Configuration and Administration LCS60 Configuration and Connection for PPP Service PPP Service Connection Dialstrings Privately Administered Static IP Address Reserved IP Address Dynamically Assigned IP Address Administration Show Session Examples Call Trace Example Log File Related Commands Issue 3 4-1 4-13 4-15 4-16 4-17 4-18 4-18 4-20 4-21 4-21 i
Table of Contents ii Issue 3
LCS60 Configuration and Connection for PPP Service Figure 4-1 shows an example network using PPP service. Note: PPP service using AppleTalk requires an R2.0 or R3.0 software key. IPX service requires an R3.0 software key. Refer to Chapter 3 for information about the software key.
LCS60 Configuration and Connection for PPP Service Note: The user should familiarize him/herself with all aspects of the LCS60 PPP service. For details, including a description of Multiple IP Subnetworks, refer to Chapter 1. After configuring the LCS60 as described under Initial Setup in Chapter 3, perform the steps shown in Figure 4-2 to configure the LCS60 PPP Service.
LCS60 Configuration and Connection for PPP Service 4 . Enter the lcsadm interface. 5 . Add the PPP service: Enter protocol from Config> or config protocol from Top>. Add tcpip. Add atalk and ipx as required. Add ppp. 6 . Define the PPP service sessions (maxsessions): From the Config directory, enter max, or enter config maxsessions at the Top directory. Assign the number of sessions. The total number of sessions through the LCS60 is 120 when PPP is configured. 7 . Set up IP network security groups (ipas).
LCS60 Configuration and Connection for PPP Service Screen 4-1: Continued 3 4 Edit an IP Network Security Group Display all IP Network Security Groups Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 Enter an IP Network Security Group name [q to quit, ? for help] ==> Library Enter an Internet network address [q to quit] ==> 154.12.24 ==> Is [154.12.24.
LCS60 Configuration and Connection for PPP Service Enter ipas at the Top>Config># prompt or config ipas at Top>. Follow the on-screen instructions for adding a reserved IP address. Reserved IP addresses are useful in cases in which a user’s security privileges are dependent on his/her source IP address. In other computing environments, a reserved IP address could be used to assure that a well known permanent IP address is set aside for server applications residing on a user’s client machine.
LCS60 Configuration and Connection for PPP Service Screen 4-2: Continued Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 Enter User login Id [? for help, RETURN for user ids, q to quit] ==> tbaker Select an IP Network Security Group to add an IP Reserved Address morse Library Techs [q to quit] ==> morse Selected IP Network Security Group [ morse ] Enter an Internet host address allocated from IP network 154.12.23 [q to quit] ==> 154.12.23.7 Added reserved IP address [ 154.12.23.
LCS60 Configuration and Connection for PPP Service Screen 4-2: Continued 1 2 3 4 Add Reserved IP Address Delete Reserved IP Address Edit Reserved IP Address Display Reserved IP Address Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> q Top>Config># 9 . Configure the IPX network number and node address (ipx): Enter ipx at Top>Config># or config ipx from the Top directory. Follow the on-screen instructions for assigning the IPX configuration parameters.
LCS60 Configuration and Connection for PPP Service Screen 4-3: Continued. ETHERNET CONFIGURATION PARAMETERS 1 Configure/Display Network Address 2 Configure/Display Framing Type Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 Current Ethernet Network Number .....
LCS60 Configuration and Connection for PPP Service ==> 2 VIRTUAL (PPP) CONFIGURATION PARAMETERS 1 Configure/Display Network Address Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 Current Virtual Network Number ..... < Undefined > Enter an IPX Network Number [ Type q to quit or ? for help ] ==> 57 Network < 57 > is already configured for your Ethernet Interface.
LCS60 Configuration and Connection for PPP Service [ ? for help, q to quit, RETURN for menu ] ==> q NOTICE: To allow IPX configuration changes to take effect you must first stop and restart the IPX software as follows: lcsadm -c stop ipx lcsadm -c start ipx 10 . Configure the AppleTalk network/zone (atalkas): Enter atalkas at the Top>Config># prompt or enter config atalkas from the Top directory. Follow the on-screen instructions for setting up the AppleTalk network number and zone name.
LCS60 Configuration and Connection for PPP Service Screen 4-4: Continued Enter the zone name to be used by AppleTalk nodes that use the virtual network. The name may contain no more than 32 characters. [ Type q to quit or ? for help ] ==> Research Lab You have entered: VIRTUAL NETWORK NUMBER ..... 2010 VIRTUAL NODE NUMBER ........ 1 VIRTUAL NETWORK ZONE NAME .. Research Lab Confirm? Enter y,n ==> y The LCS60 virtual AppleTalk network is configured as follows: VIRTUAL NETWORK NUMBER .....
LCS60 Configuration and Connection for PPP Service Screen 4-5: Configure the Ethernet Interface – Example Top>Config># etherif TCP/IP ETHERNET INTERFACE CONFIGURATION MENU 1 2 3 Configure an Ethernet Interface Delete an Ethernet Interface Display all Interfaces that are configured Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 WARNING !! This option will automatically delete each interface that was previously configured.
LCS60 Configuration and Connection for PPP Service Screen 4-5: Continued [ ? for help, q to quit, RETURN for menu ] ==> q NOTE: Changes to the configuration will not take effect until you: - enter the lcsadm command and then type "stop tcpip" from the top command directory to stop TCP/IP protocol. - enter the lcsadm command and then type "start tcpip" from the top command directory to start TCP/IP protocol. Top>Config># 12 . From the Top directory, enter start all.
LCS60 Configuration and Connection for PPP Service DESTINATION: mlkway/earth/morse.ppp DESTINATION: mlkway/earth/morse.ppp..-q0:-e6 DESTINATION: mlkway/earth/morse.ppp..-D DESTINATION: mlkway/earth/morse.ppp..-Con The options for the dialstrings are described below. Specifies whether or not priority queueing is enabled (1) or disabled (0). By default, priority queueing is enabled. In priority queueing, IP datagrams are marked as either interactive (e.g., telnet packets) or noninteractive (e.g.
LCS60 Configuration and Connection for PPP Service -u Identifies the user (either user name or numeric ID) for whom the IP address is requested. This is not required when a NAC is used. -C When connecting using IPX, the -C option is used to specify whether CIPX header compression* is to be used. -Con (default) specifies that header compression will be used; -Coff specifies it will not.
LCS60 Configuration and Connection for PPP Service Reserved IP Address The user requests a reserved IP address by omitting the -D option on his/her data switch dialstring and by having a negotiable IP address administered in his/her client software package. The reserved IP address must be centrally administered by the LCS60 administrator prior to the user’s call.
LCS60 Configuration and Connection for PPP Service If your client package does not support entry of a zero IP address (i.e., it is not fully IPCP/PPP conformant) enter the reserved IP address instead of zero. Note: If you are using a reserved address but not authenticating by means of a NAC, then you must also specify your userid on the data switch dialstring as shown below: DESTINATION: area/exch/60name.ppp..
LCS60 Configuration and Connection for PPP Service 1 . Have administered a negotiable IP address in your client software package 2 . Enter this address (e.g., 0.0.0.0 in some packages) on the appropriate screen as documented for your client package 3 . Append the -D option to the data switch dialstring: DESTINATION: area/exch/60name.ppp..-D For example: DESTINATION: mlkway/earth/morse.ppp..
Administration Link information for all PPP sessions Link, IP, IPX, and AppleTalk status for a single PPP session IP information for a single PPP session and display the local address as a numeric value Top>Session># show ppp link LCS60 Point-to-Point Session LINK Configuration: Max Max Timeout Sesid State Config Term Secs S ===== ======== ====== ==== ======= = 1.1 opened 10 2 3 L P 1.10 opened 10 2 3 L P Top>Session># show ppp 1.
Administration PEER Addr: 2010.114 Zone: Research Lab Router: 2010.1 Class: 0 Imp ID: Name: AT Comp: none Route Proto: none Broadcast Supp: none Top>Session># show ppp 1.1 ip LCS60 Point-to-Point Session IP Configuration: Peer Peer Max Sesid State Addr Slot ===== ======== =============== ==== 1.1 opened 154.12.23.9 15 Top>Session># Feb 05 07:56:24 Peer Local Local Comp Local Max Comp Slot Addr Slot Slot ==== =============== ===== ===== 1 154.12.23.
Administration Log File The log file, ppp.log, is written to by the LCS60 PPP server and contains information about incoming PPP call requests. To display the contents of the log file, use the page command as shown in the example below: # pg /usr/adm/lcs/ppp.log Fri Feb 16 11:32:55 13714 [3] ppp1 NEW 1.1 dkserver=morse dk=mlkway/earth/ inbound.54.6 ch=508 uid=tbaker rqst_reserved=1 Fri Feb 16 11:34:22 13714 [3] ppp1 DEL 1.1 Tue Feb 20 13:34:25 13714 [3] ppp1 NEW 1.
PPP Administration 4-22 Issue 3
5 SLIP – Configuration and Administration LCS60 Configuration and Connection for SLIP Service SLIP Service Connection Dialstrings Privately Administered IP Address Reserved IP Address Dynamically Assigned IP Address Administration Stop Example Call Trace Example Errors Log File Related Commands Issue 3 5-1 5-9 5-10 5-11 5-12 5-13 5-13 5-14 5-14 5-14 5-15 i
Table of Contents ii Issue 3
LCS60 Configuration and Connection for SLIP Service Figure 5-1 shows an example network using SLIP service. Figure 5-1: Example Network – SLIP Service Lucent Data Switch Modem Pool Mac Remote Access Clients LCS60 LAN } LCS200 Router You can configure the LCS60 for SLIP service using either the srvsetup command or the individual commands (protocol, maxsessions, ipas, etherif). The examples in this chapter use the individual commands.
LCS60 Configuration and Connection for SLIP Service Figure 5-2: Configuring SLIP Service obtain IP address config protocol tcpip slip maxsessions ipas etherif srvsetup start all configure client side of SLIP service 1 . Obtain the Ethernet IP address for the LCS60 and obtain an IP network address for each IP network security group. At least one IP address, in addition to the Ethernet address, is required for SLIP and PPP service in order to configure the physical connection used for SLIP/PPP.
LCS60 Configuration and Connection for SLIP Service Assign the number of sessions. The total number of sessions through the LCS60 is 120 when SLIP is configured. 5 . Set up IP network security groups (ipas): Enter ipas at the Top>Config># prompt or enter config ipas from the Top directory. Follow the on-screen instructions for configuring IP network security groups for the various workgroups required. Refer to Screen 5-1 for an example.
LCS60 Configuration and Connection for SLIP Service Screen 5-1: Continued ==> Library Enter an Internet network address [q to quit] ==> 154.12.24 ==> Is [154.12.24.0] divided into subnets ? [y, n, ?] y Enter number of mask bits for this subnet [? for help, q for quit] ==> 8 *** New IP Network Security Group "Library" Configuration is: *** *** Class B IP Address: 154.12.24 *** Network Mask: 255.255.255.
LCS60 Configuration and Connection for SLIP Service When a NAC is used, the remote user’s NAC ID is used in the ipas script to reserve an IP address for that user. Therefore, when the script prompts for User login Id, it is referring to the user’s NAC ID. NAC user IDs are alphanumeric symbols up to nine character long. A user NAC ID can be allocated a unique reserved IP address for each of the IP network security groups. A sample session is shown in Screen 5-2.
LCS60 Configuration and Connection for SLIP Service Screen 5-2: Continued Techs quit ==> morse Selected IP Network Security Group [ morse ] Enter an Internet host address allocated from IP network 154.12.23 [q to quit] ==> 154.12.23.7 Added reserved IP address [ 154.12.23.
LCS60 Configuration and Connection for SLIP Service Do not use the IP addresses shown in the example as they should follow your corporate IP address convention. Note: 7 . Configure the Ethernet interface (etherif): Enter etherif at the Top>Config># prompt or enter config etherif from the Top directory. Follow the on-screen instructions for configuring the ethernet interface. (Refer to the example in Screen 5-3.
LCS60 Configuration and Connection for SLIP Service Screen 5-3: Continued Enter aliases for morse Separate each alias with blanks Hit return if there are no aliases [q to quit] ==> ==> Is morse [154.12] divided into subnets ? [y, n, ?] y Enter name of subnet to be added [? for help, q for quit] ==> m-net0 Enter number of mask bits for this subnet [? for help, q for quit] ==> 8 Entering Ethernet interface 0 morse-e0 [154.12.21.5] ==> Is this correct? [y, n] y Ethernet interface 0 morse-e0 [154.12.21.
LCS60 Configuration and Connection for SLIP Service SLIP Service Connection Dialstrings One of the following types of dialstrings (shown with the area/exch/name from the example in Figure 5-1) may be used: DESTINATION: mlkway/earth/morse.slip DESTINATION: mlkway/earth/morse.slip..-m512:-q1:-v16 DESTINATION: mlkway/earth/morse.slip..-D DESTINATION: mlkway/earth/morse.slip..154.12.23.
LCS60 Configuration and Connection for SLIP Service -u Identifies the user (either user name or numeric ID) for whom the IP address is requested. This is not required when a NAC is used. 154.12.23.10 Specifies a privately administered IP address in dotted IP address format. If this option is included on the dialstring, the SLIP server will assign this address only if the address is: Within the IP address range assigned to the LCS60, and Not reserved for any user, and Not currently in use.
LCS60 Configuration and Connection for SLIP Service Reserved IP Address The user requests a reserved IP address by omitting the -D option on his/her data switch dialstring and by having a negotiable IP address administered in his/her client software package. The reserved IP address must be centrally administered by the LCS60 administrator prior to the user’s call.
LCS60 Configuration and Connection for SLIP Service DESTINATION: area/exch/60name.slip..-uuserid This specifies the full address of your LCS60 including the userid entered when the address was reserved. For example, for a userid hartnell on the LCS60 morse: DESTINATION: mlkway/earth/morse.slip..-uhartnell To obtain a privately administered (static) address that has not been reserved by the LCS60, use a dialstring similiar to the following: DESTINATION: mlkway/earth/morse.slip..154.12.23.
LCS60 Configuration and Connection for SLIP Service DESTINATION: area/exch/60name.slip..-D If the -D option is omitted, then the user’s reserved IP address is assigned if it is available (i.e., it exists and is not busy). In the following example, the user ID defaults to a guest user ID. If a reserved IP address has been allocated for the guest user ID, that is the address assigned; if no reserved IP address is set aside for the guest user ID, then a dynamic address is assigned.
Administration Top># stop slip *** Stopping "slip" ... Top># Call Trace Example The following screen shows how to obtain call trace information for SLIP. Top>Session> # trace slip LCS60 Serial Line IP Gateway Tracking Information: Jun 16 10:57:50 Sesid ===== 1.78 1.106 Name ==== s510 s508 Dest. Address ============= 154.12.23.7 154.12.23.18 Remote User ============ cbaker smccoy Chan ==== 510 508 Switch Address ==================== yard/samterm.141.10 yard/samterm.140.
Administration # pg /usr/adm/lcs/slip.log Fri Jun 2 10:59:34 22885 Fri Jun 2 11:00:32 22885 marina/pier/cove.140.9 Fri Jun 2 11:11:12 22885 Fri Jun 2 14:42:04 22885 Fri Jun 2 14:42:35 23342 [3] slip1 started [3] slip1 NEW 1.1 ch=510 uid=tbaker [3] slip1 DEL 1.1 [3] slip1 exited [3] slip1 started • • loglevel = 3 dkserver=morse ip=154.12.23.89 dk=\ ip=153.22.92.
SLIP Administration 5-16 Issue 3
6 ARAP – Configuration and Administration LCS60 Configuration and Connection for ARAP Service ARAP Service Connection Dialstring Administration Show Service Example Show Session Example Call Trace Example Log File Related Commands Issue 3 6-1 6-5 6-5 6-5 6-6 6-6 6-7 6-7 i
Table of Contents ii Issue 3
LCS60 Configuration and Connection for ARAP Service ARAP Figure 6-1 shows an example network using ARAP service. Note: ARAP service requires an R2.0 or R3.0 software key. Refer to Chapter 3 for information about the software key. Figure 6-1: Example Network – ARAP Service Lucent Data Switch Modem Pool Remote Access Clients LCS60 LAN AT&T LCS200 Router You can configure the LCS60 for ARAP service using either the srvsetup command or the individual commands (protocol, maxsessions, atalkas).
ARAP LCS60 Configuration and Connection for ARAP Service Figure 6-2: Configuring ARAP Service config protocol atalk arap obtain virtual Datakit VCS network name maxsessions atalkas etherif* srvsetup start all configure client side of ARAP service * etherif is not required for ARAP service, however, it is required if other services (such as PPP) are being configured as well 1 . Obtain the AppleTalk network number and zone name for the virtual network.
LCS60 Configuration and Connection for ARAP Service ARAP 5 . Configure the AppleTalk network/zone (atalkas): Enter atalkas at the Top>Config># prompt or enter config atalkas from the Top directory. Follow the on-screen instructions for setting up the AppleTalk network number and zone name. (Refer to Screen 6-1.
ARAP LCS60 Configuration and Connection for ARAP Service Screen 6-1: Continued VIRTUAL NETWORK ZONE NAME .. NOTE: Changes to the configuration of the LCS60 virtual AppleTalk network will not take effect until you: - Enter the lcsadm command and then type ’start atalk’ from the top command directory to start AppleTalk protocol.
LCS60 Configuration and Connection for ARAP Service The following type of dialstring (shown with the area/exch/name from the example in Figure 6-1) is used to make the ARAP connection. DESTINATION: mlkway/earth/brown.arap Administration Routine administration of the LCS60 includes ARAP tasks such as starting and stopping ARAP and generating ARAP-specific reports. This section gives some examples of ARAP-specific tasks.
ARAP Administration Show Session Example The screen below shows how to obtain session information for ARAP. Top> session Top>Session> show arap LCS60 AppleTalk Remote Access Protocol Statistics: Sesid Xmit(Bytes) Xmit(Pkts) Recv(Bytes) Recv(Pkts) ===== =========== ========== =========== ========== 1.1 2469 145 2366 137 1.
Administration The log file, arap.log is written to by the LCS60 interface software and contains information about incoming ARAP call requests. To display the contents of the arap.log file, use the page command as shown in the example below: # pg /usr/adm/lcs/arap.log Fri Jun 2 15:41:04 23961 [3] arap1 started loglevel = 3 Fri Jun 2 15:41:04 23961 [3] arap1 nfiles=256 Tue Jun 20 13:15:55 2159 [3] ARAPTOSS dk=mlkway/earth/topper.36.
ARAP Administration 6-8 Issue 3
7 Gateway Services – Configuration and Administration LCS60 Configuration and Connection for Gateway Service Access to Gateway Services – Dialstrings Telnet Service Inactivity Timeout Option Return to DESTINATION Option User Information Async-to-TCP Gateway Service TCP-to-Async Gateway Service UUCP Feature Data Switch to LCS60 to LAN LAN to LCS60 to Data Switch Example UUCP Service Using SunOS 4.0 Example UUCP Service Using NCR 4.
Table of Contents ii Issue 3
LCS60 Configuration and Connection for Gateway Service Figure 7-1 shows an example network using gateway services. Figure 7-1: Example Network – Gateway Services LCS60 Gateway Asynchronous Host NAC Lucent Data Switch Modem Pool Remote Access Clients LCS60 LCS200 You can configure the LCS60 for gateway services using either the srvsetup command or the individual commands (protocol, maxsessions, etherif). The examples in this chapter use the individual commands.
LCS60 Configuration and Connection for Gateway Service Note: The user should familiarize him/herself with all aspects of the LCS60 gateway service. For details, including a description of service ports, refer to Chapter 1. After configuring the LCS60 as described under Initial Setup in Chapter 3, perform the steps shown in Figure 7-2 to configure the LCS60 Gateway Services.
LCS60 Configuration and Connection for Gateway Service From the Config directory, enter max, or enter config maxsessions at the Top directory. Assign the number of sessions of each type for the gateway service: tcpasy and asytcp. The total number of sessions for all services is 120 if PPP, SLIP, or ARAP is configured. If these services are not configured, the total number of sessions is 500. Note: Up to 500 TCP service ports can be configured if the LCS60 is used for gateway service only.
LCS60 Configuration and Connection for Gateway Service Screen 7-1: Gateway Service Configuration – Example TCP-TO-ASYNCHRONOUS GATEWAY SERVICE CONFIGURATION MENU Gateway 1. 2. 3. 4. 5.
LCS60 Configuration and Connection for Gateway Service Screen 7-1: Continued ==> nac Enter Inactivity timeout minutes [ Type q to QUIT, ? for HELP, or press RETURN for default of "n" ] ==> 2 Gateway *** NOTICE *** Entering port < 4419 > to provide < telnet > service as follows: > Pre-Defined call address: > > mlkway/earth/yard - TCP window size .................. 8-bit character mode ............. Inactivity timeout(minutes) ...... Wait-for-Input timeout(minutes) .. NOHUP ............................
LCS60 Configuration and Connection for Gateway Service Screen 7-1: Continued *** NOTICE *** Entering port < 2511 > to provide < directory > service. Gateway Enter this service port? Enter y,n ==> y *** Port < 2511 > has been added. Press RETURN to continue ==> Return TCP-TO-ASYNCHRONOUS GATEWAY SERVICE CONFIGURATION MENU 1. 2. 3. 4. 5.
LCS60 Configuration and Connection for Gateway Service Screen 7-1: Continued Entering port < 1111 > to provide < socket > service as follows: > Pre-Defined call address: > > wimsey TCP window size .................. 8-bit character mode ............. Inactivity timeout(minutes) ...... Wait-for-Input timeout(minutes) .. NOHUP ............................ 2WAY ............................. SID ..............................
Access to Gateway Services – Dialstrings Telnet Service The following dialstring options are available for the telnet service. The usage is: telnet [-e] [-8] [-B] [-D] [-M:rawuucp] [-tterminal] [-w<1-16k>] host-name [port] Gateway When using more than one option, the options must be separated by a colon (:). -e Allows the user to turn the telnet local escape key off or set it to something other than the default of Ctrl-] . -8 Allows 8-bit character mode.
Access to Gateway Services – Dialstrings port Is an optional TCP port number to which the user wants to connect on the remote host. For example, to connect to a remote host’s daytime TCP service, the user would specify port 23. An example is shown in the following screen: DESTINATION: mlkway/earth/brown.telnet..-eoff:-8:-D Ctrl-C :moon Gateway Circuit Open Trying to connect to 154.12.26.1 ... Connected to 154.12.26.1. 8-bit character mode is enabled. Local Escape character ’CTRL ]’ is disabled.
Access to Gateway Services – Dialstrings Return to DESTINATION Option Gateway The LCS60 can be configured to drop the telnet connection if the host to which the user is trying to telnet is unavailable. Without this feature, trying to reach an unavailable host would result in putting the user at the telnet> prompt and could possibly allow unauthorized connection to other LAN hosts. With this feature enabled, the connection is taken down completely if the host is unavailable.
User Information Async-to-TCP Gateway Service A user on a terminal connected to the data switch network directly or through a modem can use the LCS60 connectivity to reach LAN-connected hosts or workstations. DESTINATION: earth/brown.telnet telnet> open 154.12.26.1 Login: For each destination that an async-to-TCP gateway service user may wish to reach: 1 . The LCS60 must be configured to use a DNS server, or 2 .
User Information Gateway DESTINATION: Login: earth/brown.telnet..moon The Lucent Technologies data switch speedcall feature can also be used. In the following screen, the first speedcall is entered such that telnet = brown.telnet; the second speedcall is entered such that the host moon = brown.telnet..moon (refer to the Lucent Technologies data switch documentation for details on setting up speedcall names). DESTINATION: earth/telnet telnet> open 154.12.26.
User Information $ telnet brown Trying 154.12.26.6 ... Connected to 154.12.26.6 Character mode is enabled. Escape character is ’^]’. Notice from LCS60(brown)... Gateway The following editing characters are valid during input at prompts: -- An ASCII "backspace" erases the last character typed, -- An ASCII "@" deletes the entire input line. brown LCS60 DESTINATION: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ telnet brown 2222 Trying 154.12.26.6 (Port 2222)... Connected to brown.
User Information 1 . For telnet, add the following entry to the /usr/lib/uucp/Systems file on the originating CommKit Host Interface connected host. e_host Any DK,g 0 area/exch/60name.telnet..-M:uucp:e_host in:--in: nuucp\012 word: password\012 Gateway Note: -M:raw may be entered instead of -M:uucp in the line above. 2 . Async-to-TCP also offers the TCP socket service (tcpsock) which provides a higher speed transfer pipe for uucp service.
User Information LAN to LCS60 to Data Switch To transfer files, using uucp, from an Ethernet host to the LCS60 to a host attached to a data switch, the system administrator must configure a service port for socket service. Configuration of the service port for socket service requires super user permission. Note: # lcsadm Top> # config srvports TCP-TO-ASYNCHRONOUS GATEWAY SERVICE CONFIGURATION MENU 1. 2. 3. 4. 5.
User Information [ Type q to quit, ? for help, or press RETURN for default of "n" ] Enter y,n ==> n Enter Inactivity timeout minutes [ Type q to QUIT, ? for HELP, or press RETURN for default of "n" ] ==> Return *** NOTICE *** Entering port < 2981 > to provide < socket > service as follows: Gateway > Pre-Defined call address: > > watson - TCP window size .................. 8-bit character mode ............. Inactivity timeout(minutes) ...... Wait-for-Input timeout(minutes) .. NOHUP ......................
User Information If the socket port has not been configured with a PDD, additional fields for the LCS60 call address prompt and data switch call address of the host must be added to the line above. Note: Using port 2981 as configured above (and referring to Figure 7-1), the string would be: watson Any TCP,g 2981 morse in: nuucp word: nuucp123 Gateway Example UUCP Service Using NCR 4.
Administration Routine administration of the LCS60 includes a variety of tasks related to the gateway services. This section gives some examples of these tasks. Refer to Chapter 8 for complete LCS60 administration.
Administration 2222 SOCKET 2048 2511 DIRECTORY 1024 2999 TELNET 1024 4000 TELNET 1024 4419 TELNET 1024 10283 TELNET 512 50000 SOCKET 8192 Top>Ports> summary On On On On On On On On On On On - other nac nac Limit Cfg. ===== ==== 500 6 Top>Ports> Cap.
Administration Log Files Gateway The log files shown in Table 7-1 are written to by the LCS60 interface software and contain information as shown in the table. Table 7-1: Gateway Services – Log Files ______________________________________________________ ______________________________________________________ Information Directory Log File tcpasy#.log TCP-to-Async sessions /usr/adm/lcs/tcpasy asytcp#.
8 Administration Basics 8-1 Logging On 8-1 8-2 8-2 System Console Remote Administration lcsadm Interface Common Commands Initial System Setup (initsetup) Top Directory Commands Session Directory Commands Ports Directory Commands Service Directory Commands Manager Directory Commands Config Directory Commands Typical Administrative Tasks Show Session Example Log Level Example Change the Default Route Example Summary Output Examples System Console Parameters– Autobaud Issue 3 8-3 8-4 8-5 8-5 8-7 8-10
Table of Contents Backup and Restore Operations Generic vs.
Basics The administrator is responsible for operation of the LCS60; this includes verifying connections, maintaining the network, monitoring the operation, collecting data, backing up and restoring files, starting and stopping protocols, and generating reports. All administration is done after the LCS60 is configured (see Chapters 3 – 7). Administration can be performed at the system console or from a remote terminal.
Logging On System Console Log on at the system console and enter lcsadm at the root prompt to obtain access to all LCS60 administrative operations. Remote Administration The LCS60 is provided with a remote access feature which is delivered in the disabled state. The system administrator can enable this feature: Administration 1 . Go to the srvtab directory: # cd /etc/opt/dk/srvtab 2 . Edit the file lcsadm 3 .
Logging On # dkcu mlkway/earth/morse.lcsadm Circuit Open LCS60 Administrative Command Interface. Enter ’RETURN’ key for command list! morse:Top> Note: Remote access is impossible before the system is configured and the dkhost protocol has been started. The lcsadm interface uses a hierarchical system of directories and commands as shown in Figure 8-1. The available directories – Top, Config, Session, Service, Ports, Manager, and Manager Server – and commands are described in the following sections.
lcsadm Interface Figure 8-1: lcsadm Interface Directory Structure start stop Administration Config addhost addnet atalkas backup console datetime delhost delnet dftroute dns etherif initsetup Note: ipas ipx maxsessions nodename protocol snmp softwarekey srvports srvsetup subnet upgrade viewhosts viewnets Session kill show trace types Top Service Ports Manager disable enable flush show summary types disable enable flush show summary update log show start stop update Note: All commands in direct
lcsadm Interface ˆ The ˆ is used to move back to the previous directory. Refer to Figure 8-1. Screen 8-1: Top Directory Top># Return Commands may be abbreviated. config/ service/ ! Top># manager Top>Manager># ^ Top># help session/ Commands are: manager/ start ports/ stop quit ^ Initial System Setup (initsetup) The system must be initialized before it can be used.
Administration lcsadm Interface Name start Synopsis start [? dkhost ipx tcpip atalk slip ppp snmp routed asytcp tcpasy arap all] Description The start service/protocol command starts the named service or protocol. When invoked without options, start will list the services/protocols that are running. Services and protocols can be started individually or all at once using the all option.
lcsadm Interface Administration Table 8-1: Start/stop Command Dependencies ___________________________________________________ ___________________________________________________ Command Entered Protocols/Services Started start arap arap start asytcp tcpip, asytcp start atalk atalk start dkhost dkhost start ipx ipx start ppp tcpip, ppp start routed tcpip, routed start slip tcpip, slip start snmp tcpip, snmp start tcpasy tcpip, tcpa
lcsadm Interface Screen 8-2: Session Directory Top>Manager># session Top>Session># Return Commands may be abbreviated. config/ quit types help service/ ^ Commands are: kill show ! manager/ top/ ports/ trace Administration The following commands are available from the Session directory: Name kill Synopsis kill service-type sesid [sesid ...] Description The kill command terminates a session with the specific service type and session ID (sesid) entered. This command requires root permission.
lcsadm Interface AppleTalk, or IPX configuration information (or all) for the specified session ID. When ppp is specified without a session ID, the ip, atalk, link, and ipx options are available to show IP, AppleTalk, link, or IPX configuration information for all sessions. Example The following shows AppleTalk data for a PPP session. Top>Session># show ppp 1.1 atalk LCS60 Point-to-Point Session ATALK Configuration: PEER Addr: 2010.118 Zone: Research Lab Router: 2010.
Administration lcsadm Interface Name types Synopsis types Description This command lists the available LCS60 service types as shown below. Top>Session># types Help for different types of services. Service types may be abbreviated.
lcsadm Interface disable or enable Synopsis disable port# [port#2 ...] Description These commands are used with a port number to temporarily disable a particular port from service or temporarily enable a particular port. These commands require root permission. More than one port number can be specified on the command line. Name flush Synopsis flush [port# ...] Description This command resets TCP service port statistics for the individual ports. This command requires root permission.
lcsadm Interface Name update Synopsis update Description This command updates the TCP service port configuration table. This command requires root permission. Service Directory Commands The Service directory (Screen 8-4) provides a method for obtaining current status of configured services as well as enable/disable commands. Administration Screen 8-4: Service Directory Top> service Top>Service> Return Commands may be abbreviated.
lcsadm Interface flush Synopsis flush service-type [service-type ...] Description The flush command resets statistics for a service type. This command requires root permission. Name show Synopsis show [service-type ...] Description The show command lists statistics on configured services, capacities, and current states. Entering show without arguments will display statistics for all services.
lcsadm Interface Screen 8-5: Manager Directory Top> manager NOTICE: ’manager’ requires super-user permission Password: xxxx Top>Manager># Return Commands may be abbreviated. Commands are: config/ server/ stop Administration Note: help service/ top/ log session/ update ports/ show ^ quit start ! The Manager directory requires the root password. If you have previously supplied the root password, the system will not ask for it.
lcsadm Interface Name show Synopsis show Description The show command gives information about the LCS60, including details such as process ID, start time, location of log files, log levels, and number of software servers. Name update Synopsis update Description The update command resets the LCS60 manager configuration. Note: The Server directory is a diagnostic tool for checking protocol service information and is not intended for normal administrative purposes.
lcsadm Interface Description This command is used to change the log level of each protocol server for a service. The higher the number given for the log level, the more detailed the log file. Valid log levels are: arap slip atmgr lcm 3, 6, 9 3, 6 3, 9 3, 6, 20 ppp asytcp tcpasy 3, 6, 9, 10 3, 6, 20 3, 6, 20 Administration Default is shown in bold italic typeface. Use the atlog command to set/display the atmgr log level. Use the Manager directory log command to set/display the lcm log level.
lcsadm Interface Screen 8-7: Config Directory Top> config NOTICE: ’config’ requires super-user permission Password: xxxx Top>Config># Return Commands may be abbreviated. Commands are: addhost datetime etherif manager/ quit srvports viewhosts atalkas delnet initsetup nodename session/ subnet ^ backup dftroute ipas ports/ snmp top/ ! console dns ipx protocol softwarekey upgrade The Config directory requires the root password.
Administration lcsadm Interface Name nodename Synopsis nodename Description This command allows the system administrator to set/change the LCS60 node name. Refer to initsetup in Chapter 3. Name subnet Synopsis subnet Description This command allows the system administrator to enter subnetwork information for the LCS60.
lcsadm Interface Description This command generates a menu which allows you to display and configure the software key parameters for your LCS60. softwarekey is invoked by the initsetup program since a key is required to activate any services you configure for the LCS60. You must obtain a software key from 1-800-WE2CARE for your particular LCS60 before you can complete the softwarekey command. An example of the softwarekey command is shown below.
lcsadm Interface [ Type ? for help ] Enter y,n ==> n Are you sure you want to delete the existing software key records? [ Type ? for help ] Enter y,n ==> y A copy of your current keys have been saved in the file /usr/adm/lcs/SoftwareKey.old for future reference. You will now be prompted to enter your Software Certificate Number and Software Key. These values must be properly entered to unlock the copy protected LCS60 Software.
lcsadm Interface upgrade Synopsis upgrade Description This command generates a menu which allows you to perform a remote upgrade of the LCS60. Refer to the Chapter 9 for complete details of the remote upgrade feature.
Typical Administrative Tasks Show Session Example The following screen shows how to check the status of all sessions. Top>Session># show LCS60 TCP to Async Gateway Session Statistics: Sesid Service ===== ========== 2.93 TELNET 2.92 TELNET 2.91 TELNET Administration LCS60 Async to TCP Gateway Session Statistics: Sesid Service ===== ========== 1.9 TELNET 1.8 TELNET 1.
Typical Administrative Tasks Log Level Example The following screen shows the user setting the log level for PPP. Top>Manager>Server># log ppp 3 Top>Manager>Server># Change the Default Route Example Administration Top>Config># dftroute CURRENT default route is ....... 154.12.21.3 DEFAULT ROUTE FUNCTIONS ==================================================== 1 ... Define the default route 2 ...
Typical Administrative Tasks Summary Output Examples The following screen illustrates the summary commands. Top>Service># summary LCS60 Gateway Service Summary: Administration Service Name ============ tcpasy slip ppp -ip -ipx -atalk arap Totals Cfg. ==== 120 120 120 120 Mar Use === 1 08:05:38 Max.
Typical Administrative Tasks *** NOTICE: *** *** The system console "autobaud feature" is currently enabled! *** ==> Do you want to "disable" it? [y, n, ?] y The system console "autobaud feature" is now disabled! You must first log off the system console in order for this change to take effect. SYSTEM CONSOLE CONFIGURATION PARAMETERS 1.
Backup and Restore Operations Screen 8-8: LCS60 Backup and Restore Configuration Menu # lcsadm config backup LCS60 BACKUP AND RESTORE CONFIGURATION MENU 1. Backup(restore) variable files locally or to a remote server 2. Backup-restore server operations and administration Administration Enter Menu Selection [ Type q to quit or ? for HELP ] ==> Generic vs.
Backup and Restore Operations Local and Remote Modes The LCS60 allows the backup and restore of variable files in either local or remote mode. The local mode uses the LCS60’s tape drive to copy variable configuration files from the hard disk to a removable tape, and to restore configuration files to the hard disk from a tape. The LCS60 also provides a centralized backup/restore capability.
Backup and Restore Operations Screen 8-9: Backup/Restore Menu BACKUP/RESTORE MENU 1. Define, delete, and list backup_restore servers 2. Create, delete, and restore backups from a remote server 3. Copy backups to/from tape Administration Enter Menu Selection [ Type q to QUIT, ? for HELP, or ^ to GO BACK ] ==> 3 To copy all variable configuration files to tape, select item 3 on the Backup/Restore menu (Screen 8-9) and then item 3 on the Tape Backup Management menu (Screen 8-10).
Backup and Restore Operations server, itself, was never backed up to tape, then the backups for the entire network would be lost if the server were to suffer a catastrophic accident. When the backup has been completed, the system will redisplay Screen 8-10. To Restore from Tape Note: You cannot use Release 1 or 2 backup tapes for Release 3. To restore variable configuration files from tape: 1 . Enter lcsadm config backup at the root prompt. 2 . Select option 1 from Screen 8-8. 3 .
Backup and Restore Operations There are three types of partial restores, each of which restores predefined sets of related files: Password restores group id, password files, and shadow files, and the time zone setting. Server restores lists of authorized backup/restore servers and clients and, for servers only, restores the archives containing all backups for all clients. The directory /etc/opt/dk is restored as part of a Server restore. Config restores configuration files for the LCS60.
Backup and Restore Operations The centralized backup/restore feature allows: An LCS60 configured as a server to copy to its hard disk variable configuration files from multiple remote LCS60s (and LCS50Es) configured as clients. The remote backup is done disk-to-disk over the data switch network. A backup/restore server may be configured to be its own client.
Backup and Restore Operations 2 . Clients identify which machines (servers) are authorized to copy backups from them and restore backups to them. Centralized backup/restore operations can only proceed when server and client authorizations agree. Access to Backup/Restore Functions – Clients and Servers Administration By default, an LCS60 is configured as a backup/restore client. An LCS60 is automatically configured as a backup/restore server as soon as it defines its first client.
Backup and Restore Operations Defining Backup/Restore Servers on a Client Servers are defined from the Backup/Restore Menu, Screen 8-9. To define which machines (servers) may back up a client, enter option 1 on the Backup/Restore menu (Screen 8-9). This will display the menu shown in Screen 8-12. Screen 8-12: Centralized Backup Server Definition Menu CENTRALIZED BACKUP SERVER DEFINITION MENU 1. 2. 3. 4.
Backup and Restore Operations Defining Backup/Restore Clients on the Server To define which machines may be backed up by a server, select option 1 from Screen 8-11 to obtain the menu shown in Screen 8-13. Screen 8-13: Centralized Backup Client Definition Menu CENTRALIZED BACKUP CLIENT DEFINITION MENU 1. 2. 3. 4.
Backup and Restore Operations Changing a Server to a Client To reconfigure a server as a client, delete all of its clients (option 2 on Screen 813). An LCS60 configured as a backup/restore server will be re-configured as a backup/restore client as soon as it deletes all of its clients. Backup or Restore Functions From a Client To initiate a backup or restore from a client, log onto the client; select option 2 Screen 8-9; see Table 8-2 for the tasks shown on Screen 8-14.
Backup and Restore Operations From a Server To initiate a backup or a restore from a server, log onto the server; select option 2 from Screen 8-11 to obtain Screen 8-15. Screen 8-15: Centralized Backup Operations Menu – Server CENTRALIZED BACKUP OPERATIONS MENU -- SERVER 1. 2. 3. 4.
Backup and Restore Operations A restore from server example follows: Issue 3 8-37 Administration Restore a client’s variable files.
Backup and Restore Operations Creating a Tape If it is necessary to restore a client but it is impossible or inadvisable to do so remotely, a server can copy a client’s backup from disk to tape by selecting option 3 from Screen 8-11 rather than transmit the backup over the data switch network from its disk to the disk of its client. This option displays the menu shown in Screen 8-16. Select option 1 to copy the backup.
Network Access Password Option # useradd -u444 nap # passwd nap New password: password Re-enter new password: password # Note: The password will not echo on the screen. The Network Access Password user ID parameters (e.g., group, uid, etc.) can be modified with the usermod command. An example of the telnet command (with the password option set) is shown in Screen 8-17. Administration Screen 8-17: TCP-to-Async Gateway with Network Access Password $ telnet 154.12.21.5 Trying 154.12.21.5 ...
Network Access Password Option Deleting the Network Access Password Use the userdel at the root prompt to delete the network access password. For example to delete the user id nap, enter: # userdel nap Changing the Network Access Password Administration To change an existing network access password, use the passwd command at the root prompt and enter the new password as directed. Refer to the screen below.
Status LCS60 STATUS REPORT ==================== Ethernet interface status: Interface to en0 is UP. Data Switch status: Fiber Interface to data switch is UP. Note: is is is is is is is is is is is is UP. UP. UP. UP. UP. UP. UP. UP. UP (IP Network Security Group). UP (IP Network Security Group). UP (IP Network Security Group). UP. If dkdaemon is DOWN, you must stop dkhost and then start dkhost. Error Messages Note: For alarms to StarKeeper II NMS, refer to Appendix B.
Error Messages Error Messages from the LCS60 Fiber Interface The following sections identify error messages you may see when executing the commands that make outgoing calls over the Host Interface. Console Error Messages The error messages that may appear on the console as a result of errors detected in the CommKit Host Interface software and hardware are included below.
Error Messages switch. Try manually restarting the interface. The optical connection between the receiver on the VMEDKHS board in the LCS60 and the transmitter on the CPM-HS paddle board at the data switch has been broken. Verify that the CPMHS is properly installed in the data switch slot and that there is optical connectivity between the LCS60 and the CPM-HS. The interface will recover automatically when the condition has been cleared.
Error Messages Server Error Messages When communications between the LCS60 and the data switch are interrupted, the server detects the problem and prints the following error message on the host console: * * * * * * * * * * * * * * * * * * * * * * * * * The Server for servername is having problems Please get someone to attend to it. The last error was: date dkmgr: Unable to contact CommKit for Server servername * * * * * * * Administration servername is the name of the server reporting the problem.
Error Messages Lucent Technologies Data Switch Server Log File The log file, dksrvlog, is written to by LCS60 interface software and contains information about incoming call requests. The default log file name is /var/opt/dk/log/dksrvlog.network_security_group_name. There will be as many dksrvlog files as there are multiple subnetworks configured. For the example in Figure 3-1, the three dksrvlog files are: dksrvlog.morse, dksrvlog.Library, and dksrvlog.Techs.
Administration Error Messages Log Level 2 This will log the reasons incoming calls are rejected. The token used is either ERROR or DENIED. Log Level 3 This will enter information when a call exits, including the device, process id, and exit code. The exit code is passed from the process which was spawned by the dkserver for the call. The token used is EXIT. Log Level 4 Arguments that are passed with the incoming call are logged. The token is ARGS. Log Level 5 Same as log level 4.
Error Messages Table 8-3: Log Files ____________________________________________ ____________________________________________ Information Log File adial.log Dialer information arap.log1 ARAP sessions asytcp# .log Async-to-TCP sessions atmgr.log AppleTalk information lcm.log Manager software lcsstatD.log StarKeeper II NMS information ppp.log PPP sessions slip.log SLIP sessions slipdial.log SLIP calls tcpasy#1.
Administration Error Messages 8-48 Issue 3
9 Maintenance Reload System Software Issue 3 UNIX System Software Installation UFS Utility Fixes Tape Installation inet Package Removal LCS60 Application Software Installation 9-1 9-1 9-7 9-8 9-9 Removing the LCS60 Application Software 9-13 Upgrade 9-15 Remote Upgrade Installing an Upgrade on a Remote Upgrade Client 9-16 9-16 Processor Board Firmware Update 9-19 Processor Diagnostics - MVME197 9-23 i
Table of Contents VMEDKHS Diagnostics 9-25 Connection Verification 9-28 LCS60 to Data Switch Connected Host Verification (dkcu) LCS60 to Data Switch Verification – Loopback Test (dkcu) LCS60 to Local Ethernet Host Verification (ping) Memory Dump After the Dump is Completed ii 9-28 9-29 9-29 9-30 9-32 Issue 3
Reload System Software If the system crashes, you may need to reload the system software: 1 . Install the UNIX System software 2 . Install the UFS Utility Fixes tape 3 . Remove the inet package 4 . Install the LCS60 application software. UNIX System Software Installation Caution: Once the UNIX Software has been loaded, do not reset or power off the LCS60 without first shutting down the system (/etc/shutdown -y -g0 -i0) as file damage may result.
Reload System Software 6 . Enter bo 0 40 COREunix at the 197-Bug> prompt. This will generate installation screens ending with the Screen 9-1. This information will not be repeated; use Screen 9-1 as you proceed with installation for instructions on entering responses.
Reload System Software Set Display Options The display options currently assume your terminal has: 24 lines unknown cursor addressing 1) 2) 3) 4) 5) No change, proceed with installation or upgrade Change the number of lines and return to this screen Select vt100 cursor addressing Select wyse50 cursor addressing Select unknown cursor addressing Enter option number of choice: [ 1-5 ] ( 1 ) 1 UNIX SYSTEM V/88 Release 4 Upgrade/Installation You have the following options: 1) 2) 3) 4) Full installation Upgra
Reload System Software 1) 2) 3) 4) Automatic 1-disk installation All automatic disk configuration options Manual disk configuration Read the disk configuration from the disk(s) Enter option number of choice: [ 1-4 ] ( 1 ) Return Final Verification of 1-disk installation Device Disk description m197_c0d0 1GB SCSI (SEAGATE) BOOT COMMAND: "bo 0 0" Format? Space Left No 1073402 Partition / swap /stand /usr /var /home /tftpboot FS ufs bfs ufs ufs ufs s5 1) 2) 3) 4) Slice m197_c0d0s0 m197_c0d0s1 m197_c0
Reload System Software Motif Package Query #1 Install the Motif clients? [ y n ] ( y ) Return NCD Package Query #6 Install the NCD 19 server? [ y n ] ( n ) Return X11 Package Query #2 Install the X11 software development files? [ y n ] ( y ) Return 9 .
Reload System Software Ready to begin Formatting The following disks will now be formatted: m197_c0d0 You can safely ignore error messages such as: Non-Motorola volume id read on unit xx or Invalid VTOC read on unit xx Press to continue with formatting or interrupt (CTRL-c) to abort: Return Slicing Installation Disk(s) Activating Swapping To Disk Making File Systems Installing Boot Block Mounting Installation Partitions Switching to Installation Partitions Installing Package(s) Installation in p
Reload System Software UFS Utility Fixes Tape Installation Install the UFS Utility Fixes tape (tape 2 of 3) by inserting the UFS Utility tape in the tape drive and conducting the dialogue shown in Screen 9-2. Note: In the pkgadd -d /dev/rmt/ctape1 command, the last character is a one not the letter L. Screen 9-2: UFS Utility Fixes Maintenance Tape Installation # pkgadd -d /dev/rmt/ctape1 Installation in progress.
Reload System Software inet Package Removal The LCS60 Application tape will initialize its own version of the inet package, therefore it is essential that you remove the existing inet package. Remove the inet package by conducting the dialogue shown Screen 9-3. Screen 9-3: inet Package Removal # pkgrm inet The following package is currently installed: inet Internet Utilities (m88k) FH40.42 IR03.
Reload System Software LCS60 Application Software Installation To install the LCS60 Application: 1 . Be sure the /var file system has enough space (approximately 60,000 blocks required); then: 2 . Insert the LCS60 Application tape (tape 3 of 3) in the tape drive and conduct the dialogue (as root; from the Console login) shown in Screen 9-4.
Reload System Software Screen 9-4: continued. Processing package instance from LCS60 Network Interface Version R3.0 Bldxx (m88k) Copyright (c) 1996 Lucent Technologies Inc. All Rights Reserved Copyright (c) 1994, 1995 AT&T All Rights Reserved Copyright Motorola Inc. 1988 - 1994 All Rights Reserved Copyright (c) 1985, 1986, 1987, 1988, 1989, 1990 The Wollongong Group, Inc. All Rights Reserved Copyright (c) 1990, 1991, 1992, 1993, 1994 Novell Inc.
Reload System Software 3 . Remove the cartridge tape from the tape drive. 4 . Reboot the LCS60 as shown below: # /etc/shutdown -g0 -y -i6 Shutdown started. Mon Apr 10 16:43:19 EDT 1996 Broadcast Message from root (console) on morse Mon Apr THE SYSTEM IS BEING SHUT DOWN NOW ! ! ! 10 16:43:21... Log off now or risk your files being damaged. Changing to init state 6 - please wait # INIT: New run level: 6 The system is coming down. Please wait. System services are now being stopped.
Reload System Software Multiprocessor Kernel Debugger Release 4 Version 4 Copyright (c) 1988 UNISYS. Copyright (c) 1991, 1992, 1993 Motorola, Inc. All rights reserved. Found 1 CPU(s) NOTICE: MP Locking disabled STREAMS threshold = 13738550 Max STREAMS memory = 26103245 UNIX(R) MP System V Release 4.0 Motorola m88k Version R40V4.2 Total real memory = 33554432 Available memory = 27648000 Copyright (c) 1984, 1986, 1987, 1988, 1990 AT&T Copyright (c) 1991 UNIX System Laboratories, Inc.
Reload System Software the LCS60 and the individual protocols and/or services you want to be up whenever the system is rebooted. Before you run "lcsadm" you should read about LCS60 configuration in the "LCS60 Network Interface Installation and Administration Guide" and assemble the information required for configuration. The system is ready. morse Console Login: After the screen above is displayed, complete the installation by: 1 . Logging on as root Note: As shipped, the root password is the Return key.
Removing the LCS60 Application Software Screen 9-5: LCS60 Application Software Removal – R2.0 Example # pkgrm lcs60 The following package is currently installed: lcs60 LCS60 Network Interface (m88k) R2.0 Bldxx Do you want to remove this package [y,n,?,q] y ## ## ## ## Removing installed package instance Verifying package dependencies. Processing package information. Executing preremove script. Updating /etc/ttysrch Maintenance Saving: /usr/etc/default.route /usr/etc/inetinit.cf /usr/etc/snmpd.
Removing the LCS60 Application Software Although the file /usr/etc/pppd.conf is saved when an R1.0 or R2.0 package is removed, it is not needed for R3.0 and will not be reloaded when you load R3.0. Note: Upgrade To upgrade an existing R1.0 or R2.0 LCS60 to R3.0, you will need an LCS60 R3.0 Application Tape (tape 3 of 3). To perform the upgrade: 1 . As root from the Console login, stop all services (lcsadm stop all). 2 . Determine if you have any patches on R1.0 or R2.
Upgrade 4 . Remove the R1.0 or R2.0 LCS60 software as described in the section Removing the LCS60 Application Software earlier in this chapter (page 9-13). Note: The removal screen for the different releases will be similar but not identical to the screen shown in Figure 9-5. 5 . Install the R3.0 LCS60 application software as described in the section LCS60 Application Software Installation earlier in this chapter (page 9-9). Note: In order to activate R3.0 features, you must have an R3.0 software key.
Remote Upgrade 2 . Access the Remote Upgrade Installation Menu using lcsadm -c config upgrade or: # lcsadm Top># config Top>Config># upgrade REMOTE UPGRADE INSTALLATION MENU CLIENT Procedures: 1. Enable a client to receive a generic download 2. Remove from client the previously installed generic 3. Install on a client the downloaded generic 4. Disable a client from receiving a generic download .............................................................. SERVER Procedures: 5.
Remote Upgrade 7 . On the server, select item 6 to transfer the software generic from the server to the client. Before the copy is initiated, the client is checked to ensure it has sufficient disk space to receive and store the copy. The software is downloaded in the client’s save area. Do not continue with step 8 until this transfer has completed. 8 . After the transfer from the server is complete, on the client, select menu item 2.
Processor Board Firmware Update If the MVME197E processor board has been replaced, the set and env must be executed to reset the time and date and autoboot functions. After replacing the board, attach a console to the console port on the rear of the LCS60 as described in Chapter 2. Then turn the LCS60 rear power switch on. Within a few seconds, boot messages will begin to appear on the console screen.
Maintenance Processor Board Firmware Update ____________________________________________________________________ ____________________________________________________________________ N Network Auto Boot at power-up only [Y/N]= N? Network Auto Boot Controller LUN = 00? ____________________________________________________________________ 0 ____________________________________________________________________ Network Auto Boot Device LUN = 00? 0 Network Auto Boot Abort Delay = 15? 15 _
Processor Board Firmware Update 1 Maintenance _____________________________________________ _____________________________________________ N Master Enable #2 [Y/N]=N? Master Starting Address #2 = 00000000? _____________________________________________ 0 _____________________________________________ Master Ending Address #2 = 00000000? 0 Master Control #2 = 00? 0 _____________________________________________ Master Enable #3 [Y/N]=N? ____________________________________________
Processor Board Firmware Update Screen 9-6: set and env Commands Maintenance Copyright Motorola Inc. 1988 - 1994 All Rights Reserved MVME197 Debugger/Diagnostics Release Version 1.1 - 06/17/94 (06_17.94) Local Memory Found = 02000000 (&33554432) MPU Clock Speed =50Mhz Initializing Local Memory...
Processor Diagnostics - MVME197 The MVME197 automatically runs its processor diagnostics on start up, after power is applied, and after a reset has occurred. If an error is found, it will be displayed on the console, if possible, and the FAIL LED will be turned on (refer to Figure 9-1).
Processor Diagnostics - MVME197 Maintenance DP ECDM HE HEX LA LANC LC LE LF LN MASK NCR NV PCC2 RAM RAMCD RAMCDI RTC SE ST ST2401 VME2 ZE ZP Display Pass Count ECDM Tests (DIR) Help on Tests/Commands Help Extended Loop Always Mode LAN Coprocessor (Intel 82596) Tests (DIR) Loop Continuous Mode Loop on Error Mode Line Feed Mode Loop Non-Verbose Mode Self Test Mask NCR 53C710 SCSI I/O Processor Test (DIR) Non-Verbose Mode PCCchip2 Tests (DIR) Random Access Memory Tests (DIR) Generic Memory Tests with Data C
Processor Diagnostics - MVME197 197-Diag> sd 197-Bug> bo 0 0 VMEDKHS Diagnostics After configuring the CPM-HS module, if a connection problem is encountered, the screen below will be displayed. NOTICE: DKHS0:Interface is down: TX-HANG . . . ********** ** The CommKit Server for morse is having problems ** Please get someone to attend to it. ** The last error was:May 16 07:49:20(273)[0]dkmgr:Can’t open /dev/dk/dial0 ********** 1 .
VMEDKHS Diagnostics 2 . Check the VMEDKHS board: Log into the system console and enter stop dkhost from the lcsadm interface Quit the lcsadm interface and enter dkdiag -a -n5 -i0 from the root prompt Verify that the diagnostic is completed successfully If a failure occurs, reboot the system; if the error message occurs again, check the CPM-HS board in the data switch node. 3 . Check the CPM-HS board: On the data switch console, conduct the dialogue shown in Screen 9-7.
VMEDKHS Diagnostics This task must be performed within 60 seconds! Type yes To Continue, no To Stop Command: CONTINUE TESTING [ yes, no: +(yes) ]: yes 90-08-18 13:47:57 NODE=NODENAME M diagnose cpm 11 local_loop DIAGNOSTIC EXITS CC0> diag cpm 11 TEST TYPE [command_logic, module_reset, local_loop, remote_loop]: remote_loop Ask the host computer administrator to replace the fiber optic link connection on the FIB paddle board with a loop-around connector.
Connection Verification Verify the validity of all connections before considering the LCS60 ready to assume its role in the network. Figure 9-2: Verifying Connections, Example Network LCS60 Remote Access Clients Lucent Data Switch Modem Pool LCS60 Asynchronous Host LCS200 Maintenance Router LCS60 to Data Switch Connected Host Verification (dkcu) Use the dkcu command to verify the connectivity between the local LCS60 and a data switch connected host.
Connection Verification dkcu mlkway/earth/watson You should get a login prompt from watson. LCS60 to Data Switch Verification – Loopback Test (dkcu) Use the dkcu command to verify the connectivity between the local LCS60 and a data switch. From the LCS60 system console, use the following format: dkcu where is the name of the LCS60, itself. As an example, refer to the network in Figure 9-2.
Memory Dump If the LCS60 hangs and a memory dump is required, do the following: 1 . Log the console session on a PC, if possible. Information must be recorded to evaluate the dump, and logging the session is, therefore, required. 2 . Display the debugger prompt by pressing the 197 board Abort button. (Refer to Figure 9-1). Caution: Do not use the Reset button, this will clear the current memory status ( Abort leaves the current status intact).
Memory Dump Screen 9-8: Service Menu 1) Continue System Start Up 2) Select Alternate Boot Device 3) Go to System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape Enter Menu #: 6 . At the Service Menu, enter 6 to dump memory to tape. 7 . Continue with the dialogue below; use Return to select defaults: Maintenance Do you wish to dump memory (N/Y)? y Controller LUN = 04, Device LUN = 00.
Memory Dump Rewind command executing Erase tape (Y/N)? n Retension tape (Y/N)? n Writing file #0 Writing file #1 Done with tape you may remove it. followed by the Service Menu (Screen 9-8). 10 . Reboot the LCS60 using the Reset button on the LCS60. After the Dump is Completed After dumping the memory and rebooting the LCS60, follow the procedures below to capture the information needed to understand the dump.
A Originating Group Security srvtab Server Table System Field Service Field Flags Field User Field Program Field Initial Parms Field Server Table Scanning Rules Modifications to the Server Table Server Table Validation and Matching Issue 3 A-1 A-1 A-2 A-3 A-4 A-5 A-6 A-7 A-8 A-9 A-9 i
Table of Contents ii Issue 3
srvtab The granting and denial of access privileges by the CommKit Host Interface on a called LCS60 is controlled entirely by the server table on the called LCS60. An incorrect or incomplete server table can cause serious security problems by allowing unauthorized access to system files and resources. This section describes the facilities available through the /etc/opt/dk/srvtab server table and provides the user with several suggestions to make the network connections more secure.
srvtab system Note: service flags user program initial-parameters Delimit fields by tabs only. Do not use blanks. These fields are described below. System Field The system field (originating-group) contains a pattern against which originating groups are matched. The format of the pattern is area/exchange/group[!][.user], where the suffixes ! and .user are optional.
srvtab Service Field The service field contains the name of the service the caller may request. This field consists of a single word or abbreviation and is used to match the service string that appears after the first period in the requester’s dialstring. A single asterisk may be used to match any requested service and the special entry "-" is used to match the case where no specific service was requested by the dialstring.
srvtab Flags Field Appendix A The flags field of a server table mapping line contains one or more flags that may be used to control or modify the actions the server takes when processing a call request that has been mapped to that line. Flags specify options that are unique to the mapped line. A brief description of each flag is provided in Table A-1.
srvtab Table A-1: Continued ______________________________________________________________________ the invoked program (e.g., login) will overwrite this entry in the system utmpx file with valid user information. This style of accounting does not make an entry in the system wtmpx file; it assumes that the invoked program will make the initial entry, ______________________________________________________________________ thus avoiding multiple entries.
srvtab Table A-2: User ID Mapping Options _______________________________________________________________________ _______________________________________________________________________ Option Description *n, *o Use the numeric user ID supplied in the call request information. The *o means the user ID should be interpreted as an octal number. The *n indicates the user ID should be treated as a self-determining number.
srvtab Initial Parms Field The initial parms field (fixed program arguments field) of a server table entry specifies the initial (fixed) arguments for the invoked program. The colon-separated arguments from the server table will be passed to the invoked program starting as the zero argument. If the flag is present in the server table entry, additional arguments obtained from the incoming remote execution channel will follow the initial arguments when the program is invoked.
srvtab Table A-3: Continued _________________________________________________________________________ _________________________________________________________________________ Specification Description %h _________________________________________________________________________ The local server name. _________________________________________________________________________ %l The originator, as known to the local node. The originating module number of the call being serviced.
srvtab Modifications to the Server Table The server table is opened each time a call request is received from the data switch node. Opening the server table for each incoming call allows the administrator to make modifications that will take effect on the next incoming call. There is no need to restart the server after modifications to the table. Server Table Validation and Matching Since /etc/opt/dk/srvtab is a directory, the file corresponding to the requested service is examined.
Appendix A srvtab A-10 Issue 3
B StarKeeper II NMS Configuration of the StarKeeper II NMS Issue 3 Diskette or Tape Installation StarKeeper II NMS – Configuration Commands B-1 B-1 B-4 Alarms to StarKeeper II NMS B-6 i
Table of Contents ii Issue 3
The LCS60 for Ethernet is compatible with the StarKeeper II NMS Releases 3.0 through 8.0 on the HP 720/730 platform and Release 3.0 and 4.2 on the 6386 platform. Note: To verify the version of StarKeeper II NMS that you are running, log on to the StarKeeper II NMS as cnmsadm. To verify the version, the output of help version should contain the following line: StarKeeper (R) II NMS RX.Y where X.Y is the Release number.
StarKeeper II NMS Configuration of the StarKeeper II NMS b . Choose SYSADM ; this displays the Sysadm menu c. Choose SHUTSK; select y to continue with shutdown. Enter Return when you see the shutdown completed message. d . Exit the SKsh program by pressing Return and then y at the Exit the Menu Program? prompt. 3 . At the SK: prompt, enter the su command with no arguments to change your user id to root. 4 .
Configuration of the StarKeeper II NMS c. cd /tmp mt rew cpio -ivdumB ./UNINSTALL < StarKeeper II NMS # # # # /dev/rmt/0mn Enter i Return when you see the following: Connections for L60 must either be removed or made inactive. If you are upgrading L60 you should make the connections inactive, otherwise connection information will have to be re-entered. Enter "r" to remove, or "i" to make inactive: i d . Remove the diskette or tape from the drive. 5 .
StarKeeper II NMS Configuration of the StarKeeper II NMS 6 . Remove the floppy diskette or tape from the drive when installation is complete. 7 . Enter exit Return to restore the user id to cnmsadm. 8 . Re-start the StarKeeper II NMS: a . At the SK: prompt, enter SKsh; this displays the main menu b . Choose SYSADM ; this displays the sysadm menu c. Choose STARTSK; select y to continue with startup. Enter Return when you see the startup completed message. d .
Configuration of the StarKeeper II NMS Return . 9 . At Time zone enter the applicable time zone for the LCS60 entered in Step 5 followed by a Return (refer to the StarKeeper II NMS documentation for format details). 10 . The next field is optional. At Comment enter a comment (or nothing) and press Ctrl-g . 11 . At Console press Return . 12 . At Alarms enter y Ctrl-t to indicate that the LCS60 uses an Alarms-type connection. 13 .
StarKeeper II NMS Configuration of the StarKeeper II NMS 20 . To exit the selection menu, press Return and enter yes at the Exit the Menu program? prompt. 21 . At the SK: prompt, enter conn_sync. Alarms to StarKeeper II NMS Once you have configured the StarKeeper II NMS to monitor the LCS60, the alarms listed in this section will be sent from the LCS60 to the StarKeeper II NMS. If the condition that generated an alarm corrects itself, StarKeeper II NMS will automatically clear the alarm.
Alarms to StarKeeper II NMS Interface to is down. (reason: n) Description: The LCS60 is not able to transmit data over the specified interface. Reason code 1: Loss of carrier detected for the physical Ethernet interface. Action: The recommended action for reason code 1 is as follows. Verify the connection of the Ethernet interface to the LCS60 and verify the physical state of the Ethernet network. The LCS60 does not need to be rebooted when the physical connection is reestablished.
StarKeeper II NMS Alarms to StarKeeper II NMS L600640 Process tlid is down. Description: The tlid process is not executing. Action: Restart the tlid process by entering lcsadm -c stop tcpip and then lcsadm -c start all from the LCS60 system console. If the problem occurs again, reboot the system (cd / ; /etc/shutdown -y -g0 -i6). Refer to the start all command in Chapter 8. Call your LCS60 support personnel if the problem persists. L600645 An IP Network Security Group process is down.
Alarms to StarKeeper II NMS StarKeeper II NMS L600730 Process ipxd is down. Description: The ipxd process is not executing. Action: Restart the ipxd process by executing lcsadm -c stop ipx, followed by lcsadm -c start ipx from the LCS60 system console. Call your LCS60 support personnel if the problem persists. L600735 Process sapd is down. Description: The sapd process is not executing.
StarKeeper II NMS Alarms to StarKeeper II NMS B-10 Issue 3
C User Error Messages Cable Error Message C-1 Outgoing Call Error Messages C-1 Incoming Error Messages C-9 C-10 SLIP Sessions Issue 3 i
Table of Contents ii Issue 3
Cable Error Message If the cable is disconnected the following error message will be displayed: WARNING:e1x7=transmit packet dropped carrier sense loss on controller 0 TDR problem at 405 3 meters. Error Messages WARNING:e1x7=transmit problem found by TDR for on-board ethernet controller 0. Outgoing Call Error Messages The following are error messages that may appear when placing an outgoing call through the CommKit Host Interface.
Outgoing Call Error Messages host. This can be caused by: 1 . The server name is not defined in the data switch control computer database 2 . The name is not assigned to a group Error Messages 3 . The group is not assigned to the host-connected CPM-HS module. Address too long The call was denied because the length of the dialstring was larger than the network maximum. All channels busy All assigned ports/channels are in use or are marked as not available by the remote endpoint.
Outgoing Call Error Messages Could not complete your call. Try again The call could not be completed because: — The autodialer failed to complete the dialing sequence, or — The port connected to the autodialer was removed from service during the call. Some part of the requested destination is not defined in the network. The network does not allow this host to have access to the requested destination. The requested destination is not well formed (too many slashes).
Outgoing Call Error Messages Error Messages Note: If you try to contact a remote host from the DESTINATION: prompt, any one of the errors 130– 136 may occur. The error message will be identified by its appropriate error code in the following error message where xxx is the code number. ERROR DURING CALL SETUP. CALL SYSTEM ADMINISTRATOR. CODE: xxx Dkserver: Can’t push your streams module. The call could not be completed because the configured STREAMS modules could not be pushed onto the open channel.
Outgoing Call Error Messages Dkserver: Can’t set/get circuit parameters: Call System Administrator. The call could not be accepted because the dkserver process could not communicate with the host device. Either the incoming initialization or buffer size could not be set or the the receiving buffer size could not be returned in the answer. Dkserver: Call on a busy device or call collision, try again.
Outgoing Call Error Messages Insufficient CIR at module The call could not be completed because the module receiving the call does not have sufficient resources to support the requested committed information rate (CIR). Error Messages Invalid or missing phone number The user has neglected to type the phone number required to make a phone call as in dkcu dialer_name.phone_number. The phone_number is synonymous with the dialstring.
Outgoing Call Error Messages Network hung up The network hung up the call. Network routing error Due to a network configuration error, the call is being sent and received over the same trunk. The call was dialed successfully but the autodialer did not get an answer. No carrier tone was detected The call was dialed successfully and answered; however, no carrier tone was detected by the autodialer. No diagnostic channel The call could not be completed because a diagnostic channel is not available.
Outgoing Call Error Messages Receive window too small The call could not be completed because the receive window size is too small. Remote node not answering Error Messages A connection cannot be completed because a data switch trunk or common data switch control computer database somewhere in the network path is inoperable. Server already exists This host attempted to set up a CommKit Host Interface server, but the data switch control computer database already knows a server by that name.
Outgoing Call Error Messages Splice failed The connection endpoints could not be successfully spliced together. Transmit window too big The call could not be completed because the transmit window size is too big. The call could not be completed because a trunk in the call path is busy. Trunk configuration mismatch. Call Network Administrator The call was rejected because a trunk in the call path is not properly configured. Contact the data switch Network Administrator.
Incoming Error Messages SLIP Sessions The LCS60 may send the following messages to the SLIP user: is out of range Error Messages The IP/SLIP client requested an on his/her data switch dialstring that was not within the range of the IP network and subnetwork mask associated with the called IP Network Security Group (i.e., the dkserver service name).
Incoming Error Messages ipaserrno= An internal error occurred with the IP Address Server software logic. slip is temporarily disabled may have only one -s option, got and The IP/SLIP client attempted to bypass NAC security by entering a -s option on his/her data switch dialstring even though he/she had been authorized to call . The call is refused and a message logged in the /usr/adm/lcs/slip.log file.
Incoming Error Messages mtu=, must satisfy 296 <= mtu <= 1006 The IP/SLIP client specified an out of bounds number on the data switch dialstring for the SLIP Maximum Transmission Unit (MTU) size. can not request both dynamic IP address and IP address Error Messages The user specified both the -D option and a privately administered IP address in his/her dialstring. Only one of these may be entered.
D Issue 3 Software Installation – Fujitsu or Seagate ST5660N Drive Reload System Software D-1 UNIX System Software Installation D-1 i
Table of Contents ii Issue 3
Reload System Software Note: This appendix applies to the Fujitsu and Seagate ST5660N disk drives which were used in Release 1.0 and 2.0 of the LCS60. Release 3.0 is equipped with a Seagate ST11200N disk drive; procedures for the R3.0 drive are given in Chapter 9. If the system crashes, it may be necessary to reload the system software by: 1 . Installing the UNIX System software 2 . Installing the UFS Utility Fixes tape (Chapter 9) 3 . Removing the inet package (Chapter 9) 4 .
UNIX System Software Installation 5 . Determine which type of drive you have by typing ioi at the 197-Bug> prompt.
UNIX System Software Installation Note: If you have not inserted the tape the following will be displayed. Booting from: VM197, Controller 0, Drive 40 Loading: COREunix Boot logic error Packet status: 0000 Additional Error Status: 0002 7 . If you have a Fujitsu Drive, go to step 12. 8 . For the Seagate ST5660N drive only, continue with steps 9 through 11.
UNIX System Software Installation Add the following line to the file: "SEAGATE" Note: "ST5660N" mfuj2624 7 "SEAGATE ST5660N" Separate the fields above using tabs only; spaces are not allowed. Write and quit the file. 10 .
UNIX System Software Installation Set Display Options The display options currently assume your terminal has: 24 lines unknown cursor addressing 1) No change, proceed with installation or upgrade 2) Change the number of lines and return to this screen 3) Select vt100 cursor addressing 4) Select wyse50 cursor addressing 5) Select unknown cursor addressing Enter option number of choice: [ 1-5 ] ( 1 ) 1 UNIX SYSTEM V/88 Release 4 Upgrade/Installation You have the following options: 1) 2) 3) 4) Full installat
UNIX System Software Installation Appendix D 2) All automatic disk configuration options 3) Manual disk configuration 4) Read the disk configuration from the disk(s) Enter option number of choice: [ 1-4 ] ( 1 ) Return Final Verification of 1-disk installation Device Disk description m197_c0d0 see note below BOOT COMMAND: "bo 0 0" Format? Space Left No 29520 Partition / swap /stand /usr /var /home /tftpboot FS ufs bfs ufs ufs ufs s5 Slice m197_c0d0s0 m197_c0d0s1 m197_c0d0s2 m197_c0d0s3 m197_c0d0s4 m197
UNIX System Software Installation 14 . For the both Fujitsu and Seagate ST5660N drives: Continue with the dialogue as shown in the screen below: bnu Package Query #1 Please enter the ‘node name‘ to call this machine, it must be 8 or less alphanumeric characters: ( unix ) morse inet Package Query #1 You can enter the value of the IP address now if you know it, otherwise you can just press RETURN to continue.
UNIX System Software Installation Making File Systems Installing Boot Block Mounting Installation Partitions Switching to Installation Partitions Installing Package(s) Installation in progress. 15 . For both the Fujitsu and Seagate ST5660N drives: Installation messages will continue to scroll as the UNIX System software is installed. This procedure will continue for approximately 49-60 minutes. Appendix D 16 .
E Manual Pages ATLOG E-1 ATNETSTAT E-2 ATPING E-4 DKCU E-6 DKMAINT E-8 FTP E-9 IFCONFIG E-19 IFSTAT E-21 Table of Contents i
Table of Contents ii IFTRACE E-24 IPXNETSTAT E-26 IPXPING E-27 NETSTAT E-28 NSLOOKUP E-30 PING E-34 PULL E-35 PUSH E-37 ROUTE E-40 Issue 3
Table of Contents STATLCS E-42 TELNET E-43 Table of Contents iii
Table of Contents iv Issue 3
ATLOG ATLOG ( 1M ) NAME atlog - AppleTalk manager log file SYNOPSIS atlog [-d loglevel] [-t enprz0] DESCRIPTION This command is used to display or set the logging level (-d) and the protocols for which the log information will be displayed (-t). For the -d option, the larger numbers provide more detailed logging information. The valid entries for the -t option are: e Specify e to trace ECHO. n Specify n to trace NBP. p Specify p to trace atping sessions. r Specify r to trace RTMP.
ATNETSTAT ( 1M ) ATNETSTAT NAME atnetstat - show AppleTalk network status SYNOPSIS atnetstat - [-nv] one of -i, -r, or -z is required DESCRIPTION The atnetstat command displays the contents of AppleTalk network-related data structures to show the status of configured interfaces and routing tables known to the kernel-level Datagram Delivery Protocol (DDP) routing module, and of zone lists known to the atmgr process.
ATNETSTAT ATNETSTAT ( 1M ) Gateway the address of the next router to which packets intended for this Destination will be sent or local if the Destination is directly connected to the router. Distance the number of router hops from the router to the Destination network. The -v (verbose) option may be requested with both the -i and -r options. If the -v option is requested, then the unique KEY associated with each interface and route is displayed. The VIRTUAL interface is always assigned a zero KEY.
ATPING ( 1M ) ATPING NAME atping - send AppleTalk Echo Protocol (AEP) Request packets SYNOPSIS atping [ -d sec ] net.node [packetsize [count]] DESCRIPTION atping is intended for use in network testing, measurement, and management, primarily for manual fault isolation. Tracking a single-point hardware or software failure in an AppleTalk network can often be difficult.
ATPING ATPING ( 1M ) DIAGNOSTICS Exit status is zero for normal terminations; a positive number for error terminations. FILES /usr/etc/atping /usr/etc/atlog /usr/etc/atnetstat SEE ALSO Inside AppleTalk, Second Edition, Chapter 6.
DKCU ( 1C ) DKCU NAME dkcu – call another host SYNOPSIS dkcu [ – s ] [ – f ] [ – d ] [ – v ] [ – x ] destination DESCRIPTION dkcu dials another UNIX System, a terminal, or possibly a non-UNIX System. It manages an interactive conversation with possible transfers of ASCII files. It places a call to the destination host or terminal on the data switch network. Several options are supported by dkcu: –s Suppresses the "Circuit Open" and other non-error messages.
DKCU DKCU ( 1C ) ˜ %put from [ to ] Copy file from (on local system) to file to on remote system. If to is omitted, the from argument is used in both places. Permission to create or overwrite the to file must be allowed. ˜ %break Transmit a BREAK to the remote system. ˜ ˜. . . Send the line ’˜ . . .’ to the remote system. The use of ’˜ %put’ requires stty(1) and cat(1) on the remote side.
DKMAINT ( 1M ) DKMAINT NAME dkmaint – host interface maintenance SYNOPSIS dkmaint – r – i interface [ – c channel ] [ – v ] DESCRIPTION dkmaint is a program used to reset and perform other maintenance operations on host interfaces or channels. When the ’– r’ option is specified, dkmaint sends an ioctl(2) to the host interface driver which eventually causes M_HANGUP messages to be issued to each process using the specified channel.
FTP FTP ( 1 ) NAME ftp – file transfer protocol SYNOPSIS ftp [-d] [-g] [-i] [-n] [-t] [-v] [-wwsize] [host [port]] DESCRIPTION Ftp is the user interface to the ARPANET standard File Transfer Protocol (FTP). This protocol allows a user to transfer files to and from a remote network site. The ftp client includes a command interpreter which interactively executes file transfer commands. The command interpreter prompt is ftp>. Ftp can also be run from a shell script, taking its input from a file.
FTP ( 1 ) FTP 2) If the first character of the file name is , the remainder of the argument is interpreted as a shell command. Ftp will fork a shell with the supplied argument, and pipe the output of the ftp command to the shell in the usual manner. If the shell command includes spaces, the entire argument must be enclosed in quotation marks (for example, "ls -lt"). Note that there can be no space between the pipe symbol and the shell command.
FTP FTP ( 1 ) ascii Set the data representation type to ascii. This is the default type. bell Toggle a bell that sounds after each file transfer command is completed. By default the bell is turned off. binary Set the data representation type to binary. bye Terminate the FTP session with the remote server and exit the ftp program. case Toggle case-mapping of remote file names during an mget command.
FTP ( 1 ) FTP form format Set the vertical format control for ASCII and EBCDIC file transfers to format. Valid formats are carriage-control, non-print (default), and telnet. Only the non-print format is currently supported. get remote-file [local-file] Retrieve the specified remote-file and store it on the local host. If local-file is not specified, the local file will be named remote-file. File transfer uses the current settings for type, format, mode, and structure.
FTP FTP ( 1 ) macdel mname Delete the macro mname. macls [mname] List the names of defined macros or the definition of the macro named mname. mdelete remote-file ... Delete the specified files on the remote host. If globbing is enabled, each remote-file will first be expanded. mdir remote-file ... local-file Obtain an extended directory listing of multiple files on the remote host and place the result in local-file. Globbing must be turned off when using this command.
FTP ( 1 ) FTP nmap [inpattern outpattern] Unset (no arguments) or set the file name mapping mechanism. File name mapping is used to automatically derive a destination file name from the source file name during get, mget, mput, and put commands. This is of particular interest when connecting to a non-UNIX remote host with different file naming conventions or practices.
FTP FTP ( 1 ) proxy ftp-cmd Execute an FTP command on a secondary control connection. This command enables you to open simultaneous connections to two FTP servers and transfer files between them instead of between the local client and a server. The original FTP connection is called the primary control connection; the connection made through the proxy command is called the secondary control connection. The server on the secondary connection must support the FTP protocol command PASV.
FTP ( 1 ) FTP rhelp [command] Request a list of the FTP protocol commands implemented by the remote server (no arguments) or an explanation of the specified protocol command. rmdir directory-name Delete a directory on the remote host. rstatus [file] Show the status of the remote host or of the specified file on the remote host. runique Toggle the creation of unique local file names for retrieval using get and mget.
FTP FTP ( 1 ) ‘fortune’ and that file already exists, the target name ‘fortune.1’ will be used. If fortune.1 already exists, the target name ‘fortune.2’ will be tried. This will continue with extensions 1 through 99; if all versions of the file already exist, the transfer will fail. The unique file name will be displayed if the transfer succeeds. By default, sunique is off. system Show the type of operating system running on the remote host. tenex Set the data representation type to tenex.
FTP ( 1 ) FTP FILES .netrc(4), services(4) NOTES Note that a command works only if the FTP server on the remote host supports it. Use rhelp to see which requests the remote server recognizes. The mget and mdelete commands should be used with caution. Specifying a directory where a plain file name is expected could produce unexpected results.
IFCONFIG IFCONFIG ( 1M ) NAME ifconfig – configure interface parameters SYNOPSIS ifconfig interface [address_family] [address [dest_address]] [parameters] DESCRIPTION The ifconfig command is used to display and modify the configuration of a network interface. Only the superuser can modify an interface configuration. Interface is the name assigned to the interface in the network configuration file inetinit.cf(4).
IFCONFIG ( 1M ) IFCONFIG metric n Set the routing metric of the interface to n; the default metric is zero. Higher metrics have the effect of making a route less favorable; metrics are counted as additional hops to the destination network or host. The routing metric is used by the routing protocol routed(1M). mtu mtu Set the Maximum Transmission Unit of the interface to mtu; the default metric is the value that was returned by the interface when the network was started.
IFSTAT IFSTAT ( 1M ) NAME ifstat - displays interface statistics SYNOPSIS ifstat [-adfstz] [-l interval] [config file [cntrlr num]] DESCRIPTION ifstat provides a common, configurable platform for the display of driver-specific interface statistics gathered by the supported drivers. ifstat displays statistics to stdout in the format dictated by the configuration file, config file [see ifstat.conf(4)]. The user may specify config file on the command line or let ifstat choose the configuration file.
IFSTAT ( 1M ) IFSTAT -s Show interfaces. Display the ip interfaces that ifstat supports. ifstat does not display interfaces not currently configured under ip. For example, for the two MVME376 boards in a system, if only the first board is configured under ip, ifstat displays the first board and not the second. Examine the configuration files under /etc/ifstat.conf to learn all the possible interfaces ifstat can support. -t Terminfo unsupported.
IFSTAT Issue 3 IFSTAT ( 1M ) 5 No ifstat-supporting driver found via ip 6 Failed to open config file 7 Device line format bad in config file 8 Action in device line of config file bad 9 Code format bad in config file 10 Failed to initialize terminal for curses 11 Failed to open device specified in config file 12 MACIOC GETSTATS (get statistics) ioctl to driver failed E-23
IFTRACE ( 1M ) IFTRACE NAME iftrace – trace host network packets SYNOPSIS iftrace [– gdpbhrtn] [– f diskfile] [– i count] [keywords] DESCRIPTION iftrace allows the super-user to trace packets at the interface level. The traced packets may be those received, sent, or both. A filtering facility is provided to discard broadcast packets (-b), to select received (-r) and/or transmitted (-t) packets, as well as to filter packets based upon keywords.
IFTRACE –d IFTRACE ( 1M ) Allows internal debug tracing to be enabled. keywords Allows packets to be filtered based upon specific fields within a packet. The keywords ip, ipx, and apple are required to filter packets for either DOD IP Internet or Novell IPX or AppleTalk datagrams, repectively. Only one datagram type can be specified at a time.
IPXNETSTAT ( 1M ) IPXNETSTAT NAME ipxnetstat - show IPX network status SYNOPSIS ipxnetstat [-ir [dv] ] [-p rip ipx] [interval] DESCRIPTION The ipxnetstat command symbolically displays the contents of network-related data structures to show the status of configured interfaces, routing tables, and network statistics related to IPX packet traffic. The -i option shows the status of both the ethernet and virtual configured network interfaces.
IPXPING IPXPING ( 1M ) NAME ipxping - send NetWare Link Services Protocol (NLSP) Ping Request packets SYNOPSIS ipxping network:node [packetsize ] [count] [ interval] DESCRIPTION ipxping is intended for use in network testing, measurement, and management, primarily for manual fault isolation. Tracking a single-point hardware or software failure in an Internetwork Packet Exchange (IPX) network can often be difficult.
NETSTAT ( 1 ) NETSTAT NAME netstat – show network status SYNOPSIS netstat [-AainrsSv] [-p protocol] [interval] DESCRIPTION The netstat command symbolically displays the contents of network-related data structures to show the status of active connections (default), configured interfaces, routing tables, network statistics, STREAMS buffer allocation failures, and packet traffic. The effect of pertinent options will be described in the discussion of each type of status display.
NETSTAT NETSTAT ( 1 ) the destination of the route is a host. The D flag indicates that the route is dynamic. The U flag indicates that the route is up. The -n option disables the symbolic translation of the network and interface addresses, causing both to be displayed in their Internet dot notation. Note that the reference count will always be zero since the kernel routing functions do not yet track this statistic.
NSLOOKUP ( 1 ) NSLOOKUP NAME nslookup – query name servers SYNOPSIS nslookup host [server] nslookup [- server] DESCRIPTION Nslookup is a program that queries DARPA Internet domain name servers. If called with a host name or address as the first argument, nslookup will print the name and Internet address of that host.
NSLOOKUP NSLOOKUP ( 1 ) quit Terminate interactive mode and return to the shell. Quit is an alias for exit. root Change the default server to the server for the root of the domain name space. The default root server is nic.ddn.mil. (Root is a synonym for the command lserver nic.ddn.mil.) The name of the root server can be changed with the set root command. server host lserver host Change the default server to host.
NSLOOKUP ( 1 ) NSLOOKUP type=qtype query=qtype Specify the type of information requested from the name server. The NS and SOA records apply to a domain, the PTR records apply to a reverse Internet address, the remaining records apply to a host.
NSLOOKUP NSLOOKUP ( 1 ) DIAGNOSTICS Exit status is zero for normal termination, a positive number for error termination. The diagnostic messages displayed for an unsuccessful search are: Time-out The server did not respond to a request after a certain amount of time (changed with set timeout=x) and a certain number of retries (changed with set retry=x). No information Depending on the query type set with the set query command, no information about the host was available, though the host name is valid.
PING ( 1M ) PING NAME ping – send ICMP ECHO_REQUEST packets SYNOPSIS ping [-r] [-v] host [packetsize [count]] DESCRIPTION Ping is intended for use in network testing, measurement, and management, primarily for manual fault isolation. The DARPA Internet is a large and complex aggregation of network hardware connected by gateways. Tracking a single-point hardware or software failure can often be difficult.
PULL PULL ( 1C ) NAME pull – transfer files from another system SYNOPSIS pull [ - L ] destination filename ... directory DESCRIPTION pull establishes a data switch circuit to a source (remote) host named in destination and transfers files from that host. The filenames are files or directories on the source machine and are interpreted relative to the user’s HOME directory on the source destination if they do not begin with a ´/´. The filenames are placed in the directory on the target (local) machine.
PULL ( 1C ) PULL The push(1C) and pull commands invoke the pupu program (/opt/dk/bin/pupu) on the remote system to handle the remote end of all file transfers. If the srvtab(4) file on the remote system invokes the pupu program with the ´– r´ option, file transfers will be restricted to/from the home directory tree on the remote system by disallowing all paths that begin with a leading ´/´ or that contain an embedded ´..´ specification.
PUSH PUSH ( 1C ) NAME push – transfer files to another system SYNOPSIS push [ – L ] destination filename ... directory push [ – L ] destination – directory < file_list DESCRIPTION push establishes a data switch circuit to the target (remote) host named in destination and transfers files to that host. The filenames are files or directories on the source (local) machine. The filenames are placed in the directory on the target machine.
PUSH ( 1C ) PUSH Long Names If the target machine is not a SVR4 implementation and the source machine transfers a file with a name greater then 14 characters, the name will usually be truncated to 14 characters. Note: A few preSVR4 implementations support long file names but the push command has no way of knowing if these systems do or do not. The local side will warn the user for each file name that may be truncated.
PUSH PUSH ( 1C ) local machine will be used as the file modification time. FILES /opt/dk/bin /etc/opt/dk/dkhosts directory in which this command resides host control file for destination mapping SEE ALSO pull(1C), authorize(1M), dkdial(3X), maphost(3X), dkhosts(4), srvtab(4). time(2) in the UNIX System V Programmer’s Reference Manual. find(1) in the UNIX System V User’s Reference Manual.
ROUTE ( 1M ) ROUTE NAME route – manipulate the routing tables SYNOPSIS route flush [] route add [] destination gateway metric [netmask value] [mtu value] route delete [] destination gateway DESCRIPTION Route is used to manipulate the network routing tables used by ip to determine which local network interface should be used to transmit a packet. The flush command will remove all gateway routes (see netstat(1)) from the tables.
ROUTE ROUTE ( 1M ) DIAGNOSTICS Exit status is zero for normal termination, a positive number for error termination. add host destination: gateway gateway add network destination: gateway gateway The specified route was successfully added to the route table. del host destination: gateway gateway del network destination: gateway gateway The specified route was successfully deleted from the route table. destination gateway done This message is displayed for each route deleted by the flush command.
STATLCS ( 1M ) STATLCS NAME statlcs - check the interfaces and core processes status of the LCS60 SYNOPSIS statlcs [-t] DESCRIPTION statlcs with -t displays the status to the terminal; without the -t option, statlcs outputs the status into the file /tmp/statlcs.log EXAMPLES An example of statlcs -t is shown: LCS60 STATUS REPORT ==================== Ethernet interface status: Interface to en0 is UP. Data Switch status: Fiber Interface to data switch is UP.
TELNET TELNET ( 1 ) NAME telnet – log in to remote host SYNOPSIS telnet [-ec] [-8] [host [port]] DESCRIPTION Telnet is used to communicate with another host using the TELNET protocol. When invoked without the host and port arguments, telnet enters command mode, as indicated by its prompt (telnet>). In this mode, it accepts and executes the commands discussed below. When invoked with a host [and port], telnet performs an open command with those arguments.
TELNET ( 1 ) TELNET eight Toggle eight-bit mode. When disabled (default), the high order bit is stripped on each byte to ensure transmission of valid seven-bit characters. When enabled, telnet will not strip the high-order bit, facilitating communication with hosts using an 8-bit character set such as the European or Asian character set. The -8 command line option also enables 8-bit mode. escape c Change the telnet escape character to the given c. The default escape character is the tilde (˜).
TELNET TELNET ( 1 ) WONT inform the remote server that you will stop performing the option The following options can be negotiated: binary transmit in binary (raw) mode echo remote echo (input is echoed by the remote server) exopl extended options list (negotiate from the extended options list) status display option status (display options currently in effect) tm timing mark (send a timing mark) Options can be abbreviated to the shortest unique sequence.
TELNET ( 1 ) TELNET The valid NVT commands are: z ao send an abort output request ayt send a message (are you there?) to remote server brk send a break request ec send an erase character request el send an erase line request dm send a data mark to signify end of urgent data ip send an interrupt request nop send a null operation ? display a list of transnvt commands. Suspend the telnet session. True job suspension is implemented if supported by the original shell (csh or ksh).
F User Information Introduction F-1 Client Software Configuration F-1 F-2 F-2 F-5 F-5 F-6 Client Packages Mac Connection – CCL Script CCL and Modem Hints CCL Modem PPP Service Examples Windows 95 – IPX over PPP PC Configuration PPP Connection WIN PC/TCP 3.0 PC Configuration PPP Connection InterPPP Connection SLIP Service Examples ChameleonNFS 4.
Table of Contents ARAP Service Example Connection (via Modem) ii F-22 F-22 Issue 3
Introduction This Appendix provides examples of software packages that may be used with the LCS60. This Appendix is by no means comprehensive. In order to configure your client software for use with the LCS60 for ARAP, PPP, and/or SLIP service, you must refer to the documentation provided with that software. This Appendix offers examples only. Inclusion of various software packages in this Appendix is not an endorsement of any of these products.
Client Software Configuration Users with a NAC security server: — Destination (as described above for All Users) — NAC User ID — NAC Password. Enter any options directed by your package (refer to the documentation for the package you are using). Specify parameters (e.g., host name, domain name, etc.) as required. Client Packages A variety of ARAP, PPP, and SLIP software packages are available. Some examples are shown in this section.
Client Software Configuration Screen F-1: CCL Script – Example ! ! @ORIGINATE @ANSWER ! (xxxxx) note "Communicating at 38400 bps.
Client Software Configuration Screen F-1: Continued ! @LABEL 59 exit -6019 ! ! Attempt to hang up the modem ! @HANGUP exit 0 User Information Edit this script with the information appropriate for your modem and configuration. The entries in the above script are described below: ! Indicates a comment. @ORIGINATE @ANSWER Labels to begin execution of originate and answer mode. xxxxx Anything specific to your modem should go here. Refer to your modem documentation. 38400 Baud rate.
Client Software Configuration USERID, Password, DESTINATION Your user ID, password, and DESTINATION. nj/exch/system.ppp Your LCS60 dialstring for PPP; use the ARAP dialstring, nj/exch/system.arap, for ARAP. exit 0 Terminates execution of the script (in this example, 0 is defined as a good return). exit -6019 Terminates execution of the script (in this example, -6019 is defined as a bad return). @HANGUP Marks the point in the script where execution begins to hang up.
Client Software Configuration @LABEL 21 note "Got Password:" ask 1 "Enter Password" write "^*\13" matchstr 1 22 "DESTINATION:" jump 59 matchread 400 jump 59 @LABEL 22 write "nj/exch/system.ppp/arap" note "Sent nj/exch/system.ppp/arap" Be sure you don’t have conflicts with existing label numbers. Modem The great majority of modems will work correctly right out of the box using the default settings.
PPP Service Examples PC Configuration Before you can make a PPP connection using IPX with Windows 95, you must configure your PC as follows: Install the following Client, Adapter, and Protocol software (included with Windows 95): — Client Software for NetWare Networks (currently R3.X only) — Protocol Software for IPX (and IP if desired) — Dial-up Adapter Software. To install the software, select Control Panel, then click on Network.
PPP Service Examples Figure F-1: Windows 95 IPX Over PPP – Example Screens User Information Figure F-2: Windows 95 IPX Over PPP – Connect To Example Screen F-8 Issue 3
PPP Service Examples In the previous screen, Password is not used. Note: PPP Connection After completing the client configuration procedures described above, establish the PPP connection as follows: Enter the connection dialstring in the Terminal Window as shown in the example below. Be sure to enter F7 after entering the dialstring. DESTINATION: mlkway/earth/morse.ppp Windows 95 can also use a customized dial-up script. Refer to the Windows 95 on-line help for details on scripts. Note: WIN PC/TCP 3.
PPP Service Examples Screen F-2: Sample LCS60 dialup.scr (comment, {}) (comment, {You must change the phone number, username, and password.}) (comment, {If you change a modem command prefix, use uppercase characters.}) (comment, {}) (comment, {To operate a modem which supports the Hayes Command Set with }) (comment, { command extensions:}) (send, {}) (send, {AT&F&C0}(cr){}) (comment, {}) (comment, {Leave first pause time at 1 second (minimum time possible).
PPP Service Examples Screen F-2: Continued (pause, 2000) (comment, {}) (comment, {Send \r to get DESTINATION prompt}) (send, {}) (pause, 1000) (comment, {}) (comment, {Send dialstring for morse}) (send, {mlkway/earth/morse.ppp}(cr){}) (pause, 4000) (comment, {}) (comment, {Switch the packet driver from character mode to packet mode.}) (comment, {}) (changemode, packet) (comment, {}) (comment, {Send a request to open the LCP layer}) (comment, {Pause to confirm that the lcp and ipcp layers are open.
PPP Service Examples You can configure the PPP connection options, as described in the PC/TCP Software documentation by selecting Configure... . You may specify the PPP LINK and IP negotiation values that will be used during negotiation with the LCS60 when you make the connection. The Dialer screen allows you to specify the PPP server to which you would like to connect and the connection script to use. Figure F-3: PC/TCP Example Screens mt60 User Information dialup (c:\pctcp\dialmt.
PPP Service Examples Figure F-4: PC/TCP Session Configuration Screen Example COM2 14400 154.12.22.81 Set the port and baud rate to the ones you are using with your modem. Enable hardware flow control. Note: Negotiation of the TCP/IP header compression option is defined in RFC1332. If your client package supports Van Jacobson Header Compression, then configure this feature on your Mac or PC.
PPP Service Examples Note: Be aware that baud rates are dictated by the application, serial drivers installed, and the version of the PC UART. InterPPP Note: InterPPP II is different from InterPPP. Refer to the user documentation for specific details. The InterPPP software requires minimal Mac configuration for AppleTalk or IP over PPP. Note: Make sure MacTCP is installed in the Control Panels folder. MacTCP should come with the InterPPP package.
PPP Service Examples 6 . To set the IP address, under Configure, select TCP/IP (Figure F-7) and enter the IP address in "Local IP Address." Note: If you are using a privately administered IP address, enter it in the Local IP Address field, otherwise the LCS60 will dynamically assign an IP address (if a negotiable IP address has been administered in the client software package). 7 . From the Main Screen, Figure F-8: — Enter the phone number or the dialstring.
PPP Service Examples Figure F-5: Network Control Panel User Information Figure F-6: Modem Port and PPP Screens F-16 Issue 3
PPP Service Examples Notes: US Robotics Sportster in the preceding figure is the dialing script (CCL) which contains the necessary instructions to set up the modem and log on to the LCS60. Modem Port selects which device the modem is connected to; the modem port is usually designated. When setting your physical link parameters (LCP) you can take the defaults as shown on the right. Make sure PAP/CHAP authentication are not selected. Authentication is handled by the NAC.
PPP Service Examples Figure F-8: PPP Connection Screen User Information Figure F-9: AppleTalk Status Window 2010.
SLIP Service Examples ChameleonNFS 4.0 Note: ChameleonNFS 4.5 is different from ChameleonNFS 4.0. Refer to the user documentation for specific details. Before you can make a SLIP connection using ChameleonNFS, you must configure the SLIP interface through Windows; Figures F-10 - F12 show an example configuration for dynamic IP address acquisition. 1 . Under the Custom window, select Interface and add a SLIP interface. Figure F-10: Custom Interface Window • IP address (1.1.1.
SLIP Service Examples Note: NEWT will display the dynamic IP address your PC has been assigned.
SLIP Service Examples slip.ini file); refer to Screen F-3 for an example. 3 . After configuring slip.ini, select "Connect" for the SLIP connection. Screen F-3: slip.
ARAP Service Example Note: In order to edit the CCL script, you should have the AppleTalk Remote Access Modem Script Workshop software (contact your modem or client software vendor). The CCL documentation will indicate the supported baud rates. Connection (via Modem) To establish the ARAP connection, perform the following steps: 1 . From the Network Control Panel of the Control Panels folder select Remote Only. (Refer to Figure F-13.) 2 . Launch the Remote Access Client program and select Guest.
ARAP Service Example Figure F-13: ARAP Remote Connection – Example Figure F-14: ARAP Remote Access Setup – Connection Screen User Information UNTITLED Issue 3 F-23
ARAP Service Example Caution: You must connect as Guest. You will receive the following error message if you attempt to connect as Registered User. User Information Figure F-15: ARAP Remote Access Setup – Modem Example Note: F-24 Hayes Optima 14.4 in the figure above is the dialing script (CCL) which contains the necessary instructions to set up the modem and log on to the LCS60. Modem Port is used to select which device the modem is connected to; the modem port is usually designated.
ARAP Service Example Figure F-16: ARAP Remote Access Status Screen – Example User Information Issue 3 F-25
User Information ARAP Service Example F-26 Issue 3
G Glossary Glossary General Parameters AppleTalk Network/Zone (atalkas) Ethernet Interface (etherif) DNS Resolver (dns) Define Service Sessions (maxsessions) SLIP/PPP Service (ipas/ipx) TCP-to-Asynchronous Gateway Services (srvports) Subnetwork Configuration (subnet) Report Fields Session Directory Ports Directory Service Directory Manager Directory Server Directory Issue 3 G-1 G-1 G-3 G-3 G-4 G-5 G-5 G-5 G-6 G-7 G-8 G-8 G-16 G-17 G-19 G-19 i
Table of Contents ii Issue 3
Glossary This glossary is provided as an easy reference for terms and parameters used throughout this document. General The following terms are used throughout this document. A link independent protocol developed by Apple. ARA Apple Remote Access. An ARAP client package from Apple Computer Co. ARAP AppleTalk Remote Access Protocol. A set of protocols that allows a client computer to connect to an AppleTalk network via a serial connection.
Glossary Glossary HDLC High-level data link control. A link level protocol used by PPP. IETF Internal Engineering Task Force. interface The connection between a host and a network. internet A network of networks. IP Network Security Group A symbolic name assigned to a virtual subnet IP address. This name matches the group ID assigned on the NAC. Four such IP Network Security groups are supported in LCS60 R2.0; the first IP Network Security group name assigned is the uname.
Glossary RIP Routing information protocol. A configurable lcsadm process for routing IP packets. RFC Request for comments document of the IETF. routed A service which uses RIP to maintain the IP route table. A configurable lcsadm process for routing IP packets. router A device that routes information between networks. SLIP Serial Line IP Protocol. An internet protocol. SNMP Simple Network Management Protocol.
Glossary zone name The name of the virtual AppleTalk network. Although an AppleTalk zone name may contain any 8-bit character listed in Table D-1 of Inside AppleTalk, Second Edition, the only characters that may be entered as the zone name for the LCS60 virtual AppleTalk network are the printable 7-bit ASCII characters. The valid characters are the SPACE character, all punctuation marks, digits, and upper-case and lower-case letters. SPACE characters that precede the first non-space character are ignored.
Glossary DNS Resolver (dns) domain The domain this machine and its name server(s) belong to. nameserver The nameserver is identified by its internet address using dotted decimal notation. Multiple servers may be defined in your configuration file; they will be accessed in the order listed until a connection to a server is made.
Glossary User login id Enter the remote user’s ID. If a NAC is used, this is the NAC ID. Network Address To configure the network address in ipx’s Ethernet Configuration Parameters, enter the actual IPX network number (1– 8 digits in hexadecimal) of the LCS60. To configure the network address in ipx’s Virtual (PPP) Interface Configuration Parameters, enter the virtual IPX network number. For example, in Figure 3-1, morse’s actual IPX network number is 1562 and its virtual IPX network is 57.
Glossary Enable, 8-bit character mode This prompt will be displayed for telnet ports only; enter y to allow the administrator to configure the service port with 8-bit character mode enabled. The default (n) is 7-bit character mode. inactivity timeout Enter the time in minutes in which the session will terminate if there is no input or output. The default is n which is a two minute wait. PDD To associate a call address with this TCP-to-async port, enter a PDD in the form area/exchange/local address (e.
Glossary interface address Specify the internet address for the network named in the previous prompt. mask bits The subnetwork mask identifies the subnetwork field of a network address. The length of the subnetwork field is chosen by specifying the number of subnetwork bits that will be used to formulate the network mask for a subnetted network. Enter only the number of bits in the host portion of the IP address. The default number is set to zero. The number of bits specified represents contiguous bits.
Glossary Xmit(Pkts) Number of packets transmitted. Recv(Bytes) Number of bytes received. Recv(Pkts) Number of packets received. Recv Errs CRC Indicates a checksum error for the received PPP frame. BadF Indicates the number of invalid frames received. Rej Indicates the number of duplicate or out of sequence frames rejected. ReXmts Number of re-transmissions (this is seen with the -v option).
Glossary Recv(Bytes) Number of bytes received. Recv(Pkts) Number of packets received. Show Async/TCP Top>Session> show asy Top>Session> show tcp Sesid Session ID number. Service The service type (e.g., telnet) for TCP and ASYNC sessions. Char Mode Indicates the mode enabled for the port (8-bit, 7-bit, or binary). Xmit(Bytes) Number of bytes transmitted. Recv(Bytes) Number of bytes received. Connect Time The time the TCP or ASYNC session was connected.
Glossary Recv(Pkts) Number of packets received. Receive Errors Len Indicates the length of the PPP frame received was not valid. CRC Indicates a checksum error for the PPP frame received. State Indicates that the state of the PPP frame received was invalid for HDLC framing. Alloc Indicates that the system was unable to allocate a buffer for the received frame.
Glossary Glossary ACCM Asynchronous control character mapping (refer to the documentation for the PPP package you are using). Magic The option that detects if there is a loopback situation in the connection (refer to the documentation for the PPP package you are using). Proto Comp Protocol compression (refer to the documentation for the PPP package you are using). Addr Comp Address field compression (refer to the documentation for the PPP package you are using).
Glossary Class Equals 1; dial-in server. Imp ID Implementation ID: V.. Name Name of the server (LCS60). AT Comp AppleTalk compression type. (Not supported.) Route Proto Routing protocol. (Not supported.) Broadcast Supp Broadcast packet suppression. (Not supported, therefore, no packets are suppressed.) Address (ipx) IPX network number and node number. Router Name (ipx) The IPX router (the LCS60) for the virtual network.
Glossary Remote User The user ID (or numeric equivalent if the -n option is used) of the remote user’s IP address. Chan The data switch channel number used for the gateway. Switch Address The originating group information. Trace Async/TCP Top>Session> trace asy Top>Session> trace tcp Session ID number. State The state of the TCP-to-Async or Async-to-TCP connection (IDLE, CONN, or FLOW). Local Address The LCS60 address. This is displayed when using the -v option in the form address.port# (e.g.
Glossary Trace PPP Top>Session> trace ppp Sesid Session ID number. Name The name of the PPP session. This name will be the letter p followed by the data switch channel number. Remote User The symbolic name (or numeric equivalent if the -n option is used) of the remote user’s IP address. Chan The data switch channel number used for the gateway. Switch Address The originating group information. Trace SLIP Top>Session> trace slip Session ID number. Name The name of the SLIP session.
Glossary Ports Directory Show Statistics Top>Ports> show Port # The number of the configured port. Service The service configured on the specified port (i.e., directory, telnet, socket). State The state of the port service (up or down). Total The number of times the port has been accessed. Busy The number of times the port has been busy when access has been attempted. Fail The number of times port access has been tried and failed. Reset The number of times the port has been reset.
Glossary Nohup Indicates whether the no hangup feature has been enabled. 2way Indicates whether the 2way feature has been enabled. SID-Type The security server type (e.g., NAC). Idle The inactivity timeout in minutes. Wait Indicates whether the wait-for-input timeout feature is disabled or the number of minutes configured if it has been enabled. Pre-Defined Address The PDD call address associated with the specified port.
Glossary Cfg. The total number of sessions that have been configured for the service listed (determined from maxsessions). Use The number of sessions currently in use. Cap. The percent of the maximum number of sessions currently in use. Max. The maximum number of sessions in use at one time. Total The number of times the session has been accessed. Busy The number of times the session has been busy when access has been attempted. Fail The number of times access has been tried and has failed.
Glossary Manager Directory Show Top>Manager># show Name The server name. Pid # Process ID number. Total Ses. Cfg The maximum number of sessions that can be configured. Total Ses. Used The maximum number of sessions in use. Total Servers The number of servers. Start Time The starting time of the session with the Pid # shown. Verbosity The verbosity level. Log File Name The session log file.
Glossary The number of sessions in use. Startup Time The starting time of the service shown. Server Name (#) The name and number of the server running the specified process.
I Index Index Issue 2 I-1 i
Index ii Issue 2
Index A Access remote, 1-12, 8-2 ACCM, G-12 Add default route, 3-24 DNS information, 3-25 hosts, 3-28 networks, 3-28 protocols, 3-28 service ports, 7-3 SNMP information, 3-26 Addhost/delhost, 8-17 Adding a user, 8-38 Addnet/delnet, 8-17 Addr, G-12 Addr comp, G-12 Address (ipx), G-13 Addressing dynamic, 4-17, 5-12 Reserved IP, 4-16 static, 4-16 adial.
Index Index Async-to-TCP gateway service, 1-6, 7-11 asytcp.log, 7-20, 8-47 AT Comp, G-13 Atalkas, 3-18, 4-10, 6-3 example, 6-3 Atlog, E-1 atmgr.
Index Issue 2 Configuration, 3-1 AppleTalk network/zone, 4-10, 6-3 AppleTalk virtual network, 4-10, 6-3 ARAP, 6-1 changes, 3-28 dialogues, 2-24 ethernet interface, 4-11, 5-7 files, 8-28 gateway services, 3-10, 7-1 initial, 3-3 IP address, 5-4 IPX network, 4-7 LCS60, 2-29 Mac, F-1 network security group, 4-3, 5-3 PC, F-1 port, 2-9 PPP, 4-1 protocols, 3-10 requirements, 3-2 reserved IP addresses, 4-4 service ports, 7-3 SLIP, 5-1 SLIP information, 5-3 StarKeeper II NMS, B-1 system console, 2-9 TY, 2-14 Confi
Index Index fiber interface, 2-19 power, 2-26 system console, 2-9 through modems, 2-17 through StarKeeper II NMS, 2-17 through the Lucent Technologies data switch, 2-12 verify, 2-27, 9-28 Console, 8-18 connection, 2-12 Controls, 2-1 Copy all, 8-28 Copy protection, 1-19, (see also Software key) CPM-HS module, 2-24, 2-28, 9-27 installation, 2-20 CRC, G-9, G-11 Creating a tape, 8-38 Customer Assistance, 1-22 Customer Assistance Center, (see CAC) D D8AG cord, 2-16 D8AH connector, 2-13, 2-18 Data switch, G-1
Index E Echo request, 4-14 EMI considerations, 2-5 Enable, 8-10, 8-12 2WAY, G-6 SID, G-6 Enable 8-bit character mode, G-7 Env, 9-21 Env command responses, 9-19 Error messages, 8-41 cable, C-1 call, 8-44 console, 8-42 fiber connection, 9-25 fiber interface, 8-42 gateway services, 7-19 hardware, 8-42 incoming, C-9 log files, 8-47 outgoing call, C-1 Issue 2 server, 8-44 server log file, 8-45 SLIP session, C-10 Errors, 5-14 Etc/hosts, 8-26 Etherif, 4-11, 5-7 Ethernet interface configuration parameters, G-4 c
Index Index F Fail, G-16, G-18 FCC regulations, 2-5 Features, 1-6 Fiber access, 8-2 Fiber cable connection, 2-4, 2-19 to 2-20 routing, 2-19 Fiber connection error messages, 9-25 Fiber interface, 1-18, 2-19 diagnostics, 9-26 Files, 8-26 damage, 8-25 generic, 8-26 transfer, 1-10 variable, 8-26 Firmware update processor board, 9-19 First-time authentication, 1-18 Flags field, A-4 Flush, 8-11, 8-13 Foreign address, G-14 frame type, G-1 Ftp, E-9 G Gateway async-to-TCP, 7-11 references, 1-3 Gateway service ses
Index Issue 2 IPX, 4-7, G-2 IPX address, 4-7 IPX example screens, F-9 IPX header compression, 4-15 IPX network configuration, 4-7 IPX over PPP, F-6 IPX parameters, 4-7 IPX protocol, 1-9 IPX virtual network assignment, 1-9 Ipxas, 3-23 Ipxnetstat, E-26 Ipxping, E-27 Index Initial parms field, A-7 Initial setup, 3-3 Initsetup, 3-6, 8-5 example, 3-6 Installation, 2-6 application software, 9-9 CPM-HS module, 2-20 hardware, 2-1 StarKeeper II NMS, B-1 UFS Utility Fixes tape, 9-7 Interface, G-2 address, G-4, G-
Index Index lcsstatD.log, 8-47 Len, G-11 Limit, G-17 Local addr, G-12 Local address, G-14 to G-15 Local backup/restore, 8-27 Local comp slot, G-12 Local max slot, G-12 Log, 8-14 to 8-15 Log file arap.log, 6-7 asytcp.log, 7-20 ftslisten.log, 7-20 gateway services, 7-20 ppp.log, 4-21 server, 8-45 slip.log, 5-14 tcpasy.
Index O Online manual pages, 1-21 Operation, 2-1 Originating group, G-2 name, 8-33 P Parameters, G-3 Passwd, 8-38, 8-40 Password option, 8-38 restore, 8-30 Patches software, 9-15 Issue 2 PC configuration, F-1, F-7, F-9 user information, F-1 PC/TCP example screens, F-12 PC/TCP PPP, F-9 PC/TCP Session Configuration Screen example, F-13 PDD, 1-11, 7-3, 7-12, G-2, G-7 Peer addr, G-12 Peer comp slot, G-12 Peer max slot, G-12 Pid #, G-19 Ping, 9-29, E-34 pkginfo, 9-9, 9-15 pkgrm, 9-15 Point-to-Point Protocol,
Index Index PPP, 1-12, G-2 administration, 4-18 client software, F-2 configuration, 4-1 dialstrings, 4-13 ready, 4-15 references, 1-4 screen, F-16 service examples, F-6 user information, F-1 PPP connection, 4-13, F-2, F-9, F-11 keepalive, 4-14 screen, F-17 PPP service configuration parameters, G-5 miscellaneous administrative commands, 4-21 PPP (service field), A-3 PPP service sessions define, 4-3 ppp.
Index Issue 2 Routing IP packets, 1-7 RS-232 connections, 2-4, 2-9 to 2-10, 2-12, 2-16 rx, A-3 Index Remote Addr Address, G-13 Remote Addr Zone, G-13 Remote Upgrade Installation Menu, 9-17 Remote user, G-14 to G-15 Removal application software, 9-13 inet package, 9-8 Report fields, G-8 Requirements configuration, 3-2 hardware, 3-1 Res, 9-27 Reserved IP addresses, 4-4 Reserved IP addressing, 4-16, 5-11 Reset, G-16 Restore complete, 8-29 from a server, 8-37 from tape, 8-29 password, 8-30 server, 8-30 type
Index Index Server name (#), G-20 Server table, A-1 flags, A-4 modifications to, A-9 scanning rules, A-8 validation and matching, A-9 Servers define, 8-33 Service, G-10, G-16 field, A-3 menu, 9-30 name, G-19 type, G-7 Service directory, 8-12 commands, 8-12 disable, 8-12 enable, 8-12 flush, 8-13 report fields, G-17 show, 6-5, 8-13, G-17 summary, 8-13, G-18 types, 8-13, 8-16 Service port, 1-11 configure, 7-3 directory, 7-3 example, 7-18 socket, 7-3, 7-15 telnet, 7-3 Services commands, 3-9 Sesid, G-8 to G-11
Index Issue 2 configuration, B-1 configuration commands, B-4 connection, 2-17 determining release of, B-1 installation, B-1 Start all, 3-27, 8-6 dependencies, 8-6 protocols, 8-6, 8-14 Start the LCS60, 3-27 Start time, G-19 Startup time, G-20 State, G-11, G-14 State (port), G-16 State (service), G-18 Static address, 4-16 Static IP address, 5-11 Statlcs, 8-40 to 8-41, E-42 Status, 8-40 Stop all, 8-6 dependencies, 8-6 protocols, 8-6, 8-14 SLIP example, 5-13 Subnet, 3-28, 8-18, G-5, G-7 Subnetwork, G-3 to G-4
Index Index System console, 8-2 configuration, 2-9 connection, 2-9 System console parameters, 8-24 System Field, A-2 System responses how to enter, 9-2, D-2 System software reload, 9-1, D-1 T Table-top mounting, 2-8 Tape backup to, 8-27 list contents, 8-30 restore from, 8-29 Tape Backup Management menu, 8-28 server, 8-38 TCP gateway sessions, 1-11 TCP service ports, 1-11 TCP window size, G-7 tcpasy.log, 7-20, 8-47 TCP/IP configuration commands, 3-28 TCP/IP protocol, 1-6 tcplisten.
Index UFS Utility Fixes tape installation, 9-7 UNIX commands, 1-21 UNIX System software installation, 9-1, D-1 Update, 8-12, 8-15 Upgrade, 1-20, 8-21 R1.0 to R3.0, 9-15 R2.0 to R3.
Index Index I-16 Issue 2
