HP LCS60 Installation Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Recording Equipment
  5. LCS60
  6. Installation manual
HP LCS60 Installation Manual

HP LCS60 Installation Manual

Network interface for ethernet r3.0
Hide thumbs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
Table of Contents

Advertisement

Quick Links

Download this manual
LCS60 Network Interface
for Ethernet R3.0
Installation and Administration
Guide
255-111-107
Issue 3
July 1996

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the LCS60 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for HP LCS60

Summary of Contents for HP LCS60

  • Page 1 LCS60 Network Interface for Ethernet R3.0 Installation and Administration Guide 255-111-107 Issue 3 July 1996...

  • Page 2: Issue

    ChameleonNFS® is a registered trademark of IBM Corp. DECnet is a trademark of Digital Equipment Company. HP® is a registered trademark of Hewlett-Packard Co. Hydralube Blue® is a registered trademark of Arnco Equipment Co. InterPPP is a trademark of InterCon Systems Corp.
  • Page 3 Table of Contents Trademarks 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...

  • Page 4: Table Of Contents

    Table of Contents IP Address Assignment by the LCS60 Hardware Features Enhanced Processor Fiber Interface Network Security Copy Protection Administration Backup/Restore R3.0 Upgrade Remote Upgrade Centralized Network Management Manual Pages Customer Assistance Hardware Installation Introduction Controls and Indicators Site Preparation...
  • Page 5 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 General LCS60 Software Configuration Introduction...
  • Page 6 Show Session Examples Call Trace Example Log File Related Commands 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...
  • Page 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...
  • Page 8 Network Access Password Option Deleting the Network Access Password Changing the Network Access Password Status Error Messages Error Messages from the LCS60 Fiber Interface Console Error Messages Hardware Error Messages Server Error Messages Call Error Messages Lucent Technologies Data Switch Server Log File...
  • Page 9 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 Originating Group Security...
  • Page 10 Table of Contents User Error Messages Cable Error Message Outgoing Call Error Messages Incoming Error Messages SLIP Sessions Software Installation – Fujitsu or Seagate ST5660N Drive Reload System Software UNIX System Software Installation Manual Pages ATLOG ATNETSTAT ATPING DKCU DKMAINT IFCONFIG IFSTAT IFTRACE...
  • Page 11 User Information Introduction Client Software Configuration Client Packages Mac Connection – CCL Script CCL and Modem Hints 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.0 ARAP Service Example...
  • Page 12 Table of Contents Manager Directory Server Directory Index Index G-19 G-19 Issue 2...
  • Page 13 Figures Figure 1-1: LCS60 as an AppleTalk Router Figure 1-2: AppleTalk Virtual Zone Figure 1-3: IPX Virtual Network Figure 1-4: IP Routing with the LCS60 Figure 1-5: IP Address Assignment Figure 2-1: Mounting the LCS60 Cabinet Figure 2-2: MVME712M Header Locations and Factory Jumper Placements Figure 2-3: System Console Connections –...
  • Page 14 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 –...
  • Page 15 Tables Table 1-1: Online Manual Pages Table 2-1: Controls and Indicators Table 2-2: Specifications Table 2-3: Required Additional Equipment Table 2-4: System Console (and Port) Configuration Table 2-5: MVME712M Module Optioning Table 2-6: RS-232 Interface Table 3-1: Protocol and Services Commands Table 3-2: Configuration Commands –...
  • Page 16 Table of Contents Issue 2...
  • Page 17 Screen 8-4: Service Directory Screen 8-5: Manager Directory Screen 8-6: Server Directory Screen 8-7: Config Directory Screen 8-8: LCS60 Backup and Restore Configuration Menu Screen 8-9: Backup/Restore Menu Screen 8-10: Tape Backup Management Menu Screen 8-11: Centralized Backup/Restore Menu – Server...
  • Page 18 Table of Contents Screen 9-4: LCS60 Application Software Installation Screen 9-5: LCS60 Application Software Removal – R2.0 Example Screen 9-6: set and env Commands Screen 9-7: Example diag cpm for CPM-HS Module Screen 9-8: Service Menu Screen D-1: How to Enter System Responses Screen F-1: CCL Script –...
  • Page 19 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 Issue 3...
  • Page 20 Point-to-Point Protocol (PPP) Van Jacobson TCP/IP Header Compression Compressed IPX Header (CIPX) AppleTalk Remote Access Protocol (ARAP) Multiple IP Subnetworks IP Routing Security Groups IP Address Assignment by the LCS60 Hardware Features Enhanced Processor Fiber Interface Network Security Copy Protection 1-10...
  • Page 21 Administration Backup/Restore R3.0 Upgrade Remote Upgrade Centralized Network Management Manual Pages Customer Assistance Issue 3 Table of Contents 1-19 1-19 1-20 1-20 1-20 1-21 1-22...
  • Page 22 Table of Contents Issue 3...

  • Page 23: Document Organization

    Document Organization This installation and administration guide is arranged as follows: Chapter 1 describes the LCS60 and its supported ser- Feature Description vices. Hardware Installa- Chapter 2 gives all the information needed to install the tion LCS60. General Software Chapter 3 details the basic configuration procedures for...

  • Page 24: Reference Documentation

    Customer Assistance Center (CAC) HOTLINE: 1-800-WE2CARE. Because it may be necessary to integrate the LCS60 with data switch and Star- Keeper II NMS products, the following manuals are useful references: StarKeeper II NMS User Guide, select code 255-114-707...

  • Page 25: Apple References

    1-317-352-8557 (other areas), or contact your Lucent Technologies account execu- tive (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.al, Addison-Wesley Pub- lishing (ISBN 0-201-55021-0).

  • Page 26: Ppp References

    AppleTalk Remote Access Protocol (ARAP) Point to Point (PPP) LAN to data switch connectivity between the resources of Ethernet LANs and the data switch network is accomplished using the LCS60 (refer to Figure 3-1 for an example of a data switch network). Issue 3...

  • Page 27: Benefits

    Lucent Technologies family of data switches (Datakit II VCS 2.1 or greater, BNS- 1000, 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 CPM- HS trunk board Communication between boards within the LCS60 is handled over a VME bus.

  • Page 28: Lan Protocols

    Domain Name Server (DNS) Resolver The LCS60 can be configured as a Resolver in the DNS; this allows the LCS60 to access a DNS Server for the translation of symbolic names into IP addresses.

  • Page 29: Appletalk Protocol

    AppleTalk software. The LCS60 can be used as an AppleTalk router connecting the Ethernet LAN to a virtual AppleTalk network. The virtual AppleTalk network created by the LCS60 permits as many as 120 remote AppleTalk devices to dial in over the data switch and connect to the AppleTalk internet.

  • Page 30: Appletalk Network Number And Zone Assignment

    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.) Upon dialing into the LCS60, the PPP client is assigned an available network and node number automatically. The client then becomes part of the virtual zone configured on the LCS60;...

  • Page 31: Ipx Protocol

    The IPX protocol is used to connect hosts in a Novell network. The LCS60 can be used as an IPX router connecting the Ethernet LAN to a virtual IPX network via PPP. The virtual IPX network created by the LCS60 permits as many as 120 remote end hosts to dial in over the data switch and connect to the Novell network.

  • Page 32: Remote Access Protocols

    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 LAN- connected hosts/workstations – this is the async-to-TCP gateway service. The LCS60 provides communication in the other direction –...

  • Page 33: Tcp Service Ports

    SLIP allows a remote PC or Macintosh to logically reside on the TCP/IP LAN. In a SLIP session, a remote user can dial into an LCS60, request SLIP service, and receive an IP address automatically. This remote user is then logically connected to the LAN and can execute such TCP/IP commands as ftp, telnet, and ping.

  • Page 34: Van Jacobson Tcp/Ip Header Compression

    The remote PC or Macintosh negotiates the PPP protocol options with the LCS60 through the client software package residing on the PC or Mac. A remote user can dial into the LCS60 through the data switch, request PPP service, and receive an IP address, IPX address, and/or AppleTalk network and node number automatically.

  • Page 35: Multiple Ip Subnetworks

    The LCS60 uses ARAP to provide connection between the CommKit Host Inter- face and Ethernet-connected AppleTalk devices. A remote user can dial into the LCS60 through the data switch, request ARAP service, and receive the AppleTalk network and node number automatically.

  • Page 36: Figure 1-4: Ip Routing With The Lcs60

    135.12.23 Security Group:Eng The LCS60 has a physical IP network number for its Ethernet interface (e.g., 154.12.21) and can have a virtual IP network number for each defined security group (e.g., Library, morse, Techs, Eng), up to a maximum of four such groups as shown in Figure 1-4.

  • Page 37: Security Groups

    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.

  • Page 38: Figure 1-5: Ip Address Assignment

    Multiple IP Subnetworks Figure 1-5: IP Address Assignment Incoming Call IP address privately administered on PC? Was user ID specified on dialstring? Set user id to "guest" -D option on dialstring? Assign dynamic IP address 1-16 Is this Error: IP address IP address out is not correct of range?

  • Page 39: Ip Address Assignment By The Lcs60

    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. The user’s IP address is locally administered by the user on his/her PC software package. The LCS60 will use the IP address requested by the PC package if it is valid and unused.

  • Page 40: Fiber Interface

    NAC. Once authenticated, the user can request a TCP gateway session or a remote access session (such as ARAP, PPP, or SLIP) with an LCS60 by means of a simple dialstring. From the LAN, all sessions bound for the data switch net- work can be forced to be authenticated by means of the TCP service port feature.

  • Page 41: Copy Protection

    This number is assigned during the initial setup of the LCS60 using the lcsadm interface (refer to Chapter 3 for complete details). The copy-protection feature uses a release-specific software key; that is, Release 3 ser- vices can only be activated using the Release 3 key.

  • Page 42: R3.0 Upgrade

    Centralized Network Management StarKeeper II NMS provides complete network management from one central- ized location for both the data switch and the LCS60. The StarKeeper II NMS can be located anywhere on the data switch network and can contact many LCS60 gateways.

  • Page 43: Manual Pages

    Manual Pages The LCS60 is provided with a set of online manual pages. Some commands that may be of particular help to the system administrator are listed in Table 1-1 and are included in Appendix E. Table 1-1: Online Manual Pages...

  • Page 44: Customer Assistance

    Customer Assistance Technical support is available for the LCS60 from the Lucent Technologies Cus- tomer Technical Support Center at 1-800-WE2CARE. For more information on these service offerings, or to establish a service account, contact your Lucent Technologies account representative, or call 1-800-WE2- CARE during our standard business hours (8AM –...
  • Page 45 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...
  • Page 46 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...

  • Page 47: Introduction

    7 . Verify the LCS60 fiber connection 8 . Configure the LCS60 using the lcsadm interface (Chapters 3– 7) 9 . Verify connections between the LCS60 and LAN hosts and between the LCS60 and data switch connected endpoints (Chapter 9).

  • Page 48: Site Preparation

    PWR STATUS* *Can be seen by means of the rear panel cutout labeled SCSI INTERFACE. Site Preparation LCS60 specifications for the power, interface, and operating requirements, as well as the other pertinent interface specifications, are listed in Table 2-2. Controls...

  • Page 49: Table 2-2: Specifications

    Table 2-2: Specifications LCS60 Network Interface for Ethernet Power Requirements Operating Temperature Storage Temperature Operating Humidity Storage Humidity Fiber Interface Fiber Core Size Mode Fiber Optic Cable Connector Ethernet Interface Interface Connector Console/Terminal Interfaces Port 1 (console) Ports 2,3,4 (terminal)

  • Page 50: Space Requirements

    Site Preparation Space Requirements 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.

  • Page 51: Emi Considerations

    EMI Considerations The LCS60 can radiate radio frequency energy, and if not installed in accordance with instructions, may cause interference to radio communications. This equip- ment has been tested and found to comply with the limits for a Class A comput-...

  • Page 52: Assembly

    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.

  • Page 53: Figure 2-1: Mounting The Lcs60 Cabinet

    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...

  • Page 54: Wall Mounting

    2 . Attach the Wall Mounting Assembly to the plywood surface, using four ¼ x ¾-inch lag screws. 3 . Locate the LCS60 in the mounting assembly by aligning the front flange of the LCS60 with the four threaded holes on the flange at the left end (facing the assembly).

  • Page 55: Connecting The System Console

    The LCS60 has four serial RS-232 ports which can emulate asynchronous DTE or DCE. Serial Port 1 is used for the LCS60 system console and operates at 9600 bps. Ports 2, 3, and 4 can be used to interface asynchronous terminals to the LCS60 UNIX System with Ports 2 and 3 providing 9600 bps operation and Port 4 providing 1200 bps operation.

  • Page 56: Figure 2-2: Mvme712M Header Locations And Factory Jumper Placements

    Installing the LCS60 Table 2-5: MVME712M Module Optioning Default Optioning Ext.Interface Port Emulation Non-Default Optioning Figure 2-2: MVME712M Header Locations and Factory Jumper Placements 2-10 Port Jumper Bridged Pins no jumpers no jumpers J21 6 DS1 DS2 Issue 3...

  • Page 57: Table 2-6: Rs-232 Interface

    Ports 2, 3, and 4 Async DTE Emulation Designation Ports 2, 3, and 4 Async DCE Emulation Issue 3 Installing the LCS60 Function Direction TD-Transmit Data To DCE RD-Receive Data From DCE RTS-Request To Send To DCE CTS-Clear To Send...

  • Page 58: Direct Connection To The Lcs60

    Figure 2-3: System Console Connections – Direct Asynchronous Terminal Connection through a Data Switch To connect an asynchronous terminal or PC to the LCS60 for use as a system con- sole through a data switch network, refer to Figure 2-4 and follow the steps below: Note: Connections to the data switch network must be to an asynchronous port (e.g., a TY-12 port).
  • Page 59 2 . Connect the LCS60 rear panel connector labeled "Serial Port 1" to an asyn- chronous port using a straight-through connection (D8AH connector); connect the 25-pin end to the LCS60.

  • Page 60: Screen 2-2: Msm Configuration Dialogue

    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)]:...
  • Page 61 INITIAL SERVICE STATE [in, out: +(out)]: in LEVEL [network, area, exchange, local, speedcall: +(local)]: CC0> restore msm COMPONENT [module, port]]: p MODULE ADDRESS: 18 PORT NUMBER [1-12: +(1-12)]: 11 CC0> Issue 3 Installing the LCS60 Return Return Return Return Return Return Return...

  • Page 62: Figure 2-4: System Console Connections - Through A Data Switch

    6 . Restore both asynchronous ports and name to service. 7 . In response to the DESTINATION prompt on the terminal device, enter the name created for the LCS60 console. This step can be done from any ter- minal displaying a DESTINATION prompt. Maintain proper security pre- cautions to guard against unauthorized or accidental usage.

  • Page 63: Connection Through Modems

    Connection through Modems To connect an asynchronous terminal or PC to the LCS60 for use as a system con- sole 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.)

  • Page 64: Figure 2-6: System Console Connections - Through Starkeeper Ii Nms

    Installing the LCS60 2 . Connect the LCS60 rear panel connector labeled "Serial Port 1" to an asyn- chronous port on the data switch using a straight-through connection (D8AH connector); connect the 25-pin end to the LCS60. 3 . Configure the asynchronous port on the data switch according to Table 2-4 as a receiving group.

  • Page 65: Connecting The Fiber Interface

    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 CPM- HS module in a Datakit II VCS or BNS.

  • Page 66: Installing The Cpm-Hs Module And Optical Fiber Cable

    LCS60 should not exceed 2.9 km. Remove the rubber caps from the optical fiber cable that runs from the transmitter side of the LCS60 and connect the optical fiber cable to the receiver side (top connector) of the CPM-HS module in the data switch.

  • Page 67: Configuration Of The Lucent Technologies Data Switch Lcs60

    Configuration of the CPM-HS module in the data switch is done in the same way as a CPM-HS module connected to a UNIX System host. The number of chan- nels should be the same as the number of channels with which the LCS60 is con- figured, 512.

  • Page 68: Dialogues

    The entries are described below: group Defines the group name by which the data switch knows the LCS60. This is morse in the example. This must be the same as the LCS60 node name. type The LCS60 is a local connection to the data switch (the CPM-HS module resides in this data switch).
  • Page 69 MNEMONIC ADDRESS [up to 8 chars]: morse PAD SUPPORT [yes, no: +(no)]: 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)

  • Page 70: Configure The Cpm-Hs Module

    Appendix A) may also be used to restrict incoming calls, is used to disable this feature. Return service state The local address must be in service for the LCS60 to originate and receive calls. Configure the CPM-HS Module CC0> enter cpm...

  • Page 71: Power And Grounding

    Power-Up Procedures Follow the steps below for LCS60 power up only after reading this section. 1 . Connect the LCS60 to the power source. For the AC power unit, the outlet should be on a dedicated circuit for the LCS60.

  • Page 72: Figure 2-7: Lcs60 Rear Panel Ac Connections

    Installing the LCS60 Figure 2-7: LCS60 Rear Panel AC Connections System Reset See Inset for AC and DC connections On/Off Switch AC Connection 110 VAC Power 2-26 To Asynchronous Terminal Coaxial Cable Serial Por t 1 Serial Por t 2...

  • Page 73: Power-Down Procedures

    Console Login: prompt. Verify LCS60 Console Connection To verify the console connection, perform the following: 1 . Power-up the LCS60 and verify that communication with the console has been established. The console should display diagnostic text followed by the Console Login: prompt.

  • Page 74: Verify Fiber Connection

    ** The last error was:May 16 07:49:20(273)[0]dkmgr:Can’t open /dev/dk/dial0 ********** reverse the fiber cable connection on either the LCS60 or CPM-HS (whichever is more convenient); if the machine doesn’t recover after a few minutes stop and start dkhost from the lcsadm interface. If the error message appears again, per- form a diagnostic check as described in Chapter 9.

  • Page 75: Configure The Lcs60

    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 confi- guration.
  • Page 76 LAN Connections 2-30 Issue 3...
  • Page 77 General LCS60 Software Configuration Introduction Preliminary Hardware Requirements Preliminary Configuration Requirements Specific Services Initial Setup Configure Protocols and Gateway Services — srvsetup Configure Default Route, DNS, and SNMP Default Route – dftroute* Domain Name Server – dns SNMP Manager – snmp...
  • Page 78 Table of Contents Configuration Changes Administrative and Maintenance Commands 3-28 3-29 Issue 3...

  • Page 79: Preliminary Hardware Requirements

    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 Lucent Data Switch Modem Pool LCS60 78:1FC (IPX) Remote Access Clients Note: Refer to Chapters 4, 5, 6, and 7 for examples of PPP, SLIP, ARAP and gateway configurations.

  • Page 80: Preliminary Configuration Requirements

    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.

  • Page 81: Specific Services

    Specific Services The instructions in this chapter describe the configuration of some of the avail- able 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).

  • Page 82: Figure 3-2: Initsetup

    Caution: Only one system administrator at a time should be using lcsadm to configure the LCS60. Use the lcsadm interface for all system administration; do not attempt to adjust individual configuration database files in any other way. If you attempt to execute any of...
  • Page 83 The machine name (shown in Screen 3-1 as sysV68) appears at the beginning of the Top prompt. The sysV68 will be replaced by the node name you configure for your LCS60 after you exit and then re-enter the lcsadm interface (in the example that follows the prompt would become morse:Top ).
  • Page 84 LCS60 Initial Setup and Configuration Procedure The "initsetup" procedure leads you through the steps to initially set up this LCS60 by entering the node name, time and date, and the software key. *** This step allows the LCS60 Administrator to set the node name.
  • Page 85 *** 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.
  • Page 86 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.

  • Page 87: Table 3-1: Protocol And Services Commands

    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. Refer to the sections (Configure Protocols and Gateway Services– srvsetup and Configure Default Route, DNS, and SNMP ) below to complete the configuration of your LCS60.

  • Page 88: Configure Protocols And Gateway Services Srvsetup

    Refer to Chapters 4, 5, 6, and 7 for examples of individual commands. Perform the following steps to configure the protocols and gateway services for your LCS60. (You should have already done an initsetup as described previously.) Step 1 Enter srvsetup at the Top Config # prompt to start the protocol/service setup routine.
  • Page 89 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"...
  • Page 90 Enter Menu Selection [? for help, q to quit, RETURN for menu] ==> *** 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.
  • Page 91 Is this correct? Enter y,n ==> y 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. Display all Session Parameters...
  • Page 92 Is this correct? Enter y,n ==> y 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. Display all Session Parameters...
  • Page 93 The following prompts (ipas) will be displayed only if SLIP or PPP is configured. *** 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.
  • Page 94 Configure Protocols and Gateway Services — srvsetup IP NETWORK SECURITY GROUP MANAGEMENT FOR SLIP AND PPP SERVICES 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 ] ==>...
  • Page 95 *** Class B IP Address: 154.12.25 *** Network Mask: 255.255.255.0 Is this correct? Enter y,n ==> y IP NETWORK SECURITY GROUP MANAGEMENT FOR SLIP AND PPP SERVICES 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 ]...
  • Page 96 Note: 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 dis- cover 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.
  • Page 97 [ Type q to quit or ? for help ] ==> q *** This step allows the LCS60 Administrator to configure the Ethernet *** interface for TCP/IP on this LCS60. This must be configured for TCP *** Gateway, PPP and SLIP services. TCP/IP ETHERNET INTERFACE CONFIGURATION MENU Issue 3 Configure Protocols and Gateway Services —...
  • Page 98 Configure Protocols and Gateway Services — srvsetup 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.
  • Page 99 Note: The following prompts (ipx) will be displayed only if IPX is configured. *** 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.
  • Page 100 Configure Protocols and Gateway Services — srvsetup 2 Configure/Display Framing Type Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> CAUTION: Please refer to the I&A Guide for instructions about configuring this feature. IPX CONFIGURATION MANAGEMENT Ethernet interface configuration parameters Virtual (PPP) interface configuration parameters Display all Parameters...

  • Page 101: Configure Default Route, Dns, And Snmp

    [ ? for help, q to quit, RETURN for menu ] ==> This completes your configuration of protocols and services on this LCS60. To start ALL configured protocols and services, enter the command "lcsadm" and then from the top command directory type "start all".

  • Page 102: Default Route – Dftroute

    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.

  • Page 103: Domain Name Server – Dns

    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 Display Current Configuration Modify/Create DNS Resolver Configuration Enable/Disable DNS Enter Menu Selection [? for help, q to quit] ==>...

  • Page 104: Snmp Manager – Snmp

    Configure Default Route, DNS, and SNMP [? for help, q to quit] ==> Top>Config># Be sure to specify routed with the protocol command to start DNS service at boot time. SNMP Manager – snmp Use the snmp command to define the SNMP manager as shown in the example below.

  • Page 105: Starting The Lcs60

    LCS60 variable files to preserve the confi- guration information. These tapes can be labeled "day 0 backups" and can be used to restore the LCS60 quickly to a working state if necessary. Use the com- mand lcsadm -c config backup as described in Chapter 8.

  • Page 106: Configuration Changes

    Table 3-2: Configuration Commands – Config Directory Configuration Set the date and time Change the node name Choose the protocols to start when the LCS60 is rebooted Change the default route Set the software key Set the DNS resolver Change the SNMP configuration...

  • Page 107: Administrative And Maintenance Commands

    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 direc- tory.
  • Page 108 Administrative and Maintenance Commands 3-30 Issue 3...
  • Page 109 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...
  • Page 110 Table of Contents Issue 3...

  • Page 111: Lcs60 Configuration And Connection For Ppp Service

    Apple Printer Novell File Server Workstation You can configure the LCS60 for PPP service using either the srvsetup command or the individual commands (protocol, maxsessions, ipas, ipx, atalkas, etherif). The examples in this chapter use the individual commands. If previous configuration (for example, for SLIP service) was performed, some of the steps required for configuring the LCS60 for PPP service may have already been completed (e.g., etherif, ipas).

  • Page 112: Figure 4-2: Configuring Ppp Service For Ip, Ipx, And Appletalk

    Zone name 1 . Obtain the Ethernet IP address for the LCS60 and 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.
  • Page 113 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). Enter ipas at the Top Config # prompt or config ipas at Top and follow the on-screen instructions for configuring IP network security groups for the various workgroups required.
  • Page 114 LCS60 Configuration and Connection for PPP Service Screen 4-1: Continued Edit an IP Network Security Group Display all IP Network Security Groups Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> Enter an IP Network Security Group name [q to quit, ? for help] ==>...
  • Page 115 IP address for each of the IP network security groups. A sample session is shown in Screen 4-2. (Refer also to the IP Address Assignment by the LCS60 section in Chapter 1.) Screen 4-2: Configure Reserved IP Address – Example Top>Config># ipas CAUTION: Please refer to the I&A Guide for instructions...
  • Page 116 LCS60 Configuration and Connection for PPP Service Screen 4-2: Continued Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> Enter User login Id [? for help, RETURN for user ids, q to quit] ==>...

  • Page 117: Screen 4-3: Configure Ipx Parameters – Example

    IPX CONFIGURATION MANAGEMENT Ethernet interface configuration parameters Virtual (PPP) interface configuration parameters Display all Parameters Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> 1 Issue 3 LCS60 Configuration and Connection for PPP Service...
  • Page 118 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 ] ==> Current Ethernet Network Number ... < Undefined >...
  • Page 119 Enter Menu Selection [ ? for help, q to quit, RETURN for menu ] ==> The LCS60 IPX Parameters are configured as follows: Ethernet Network Number ... < 1562 > Virtual Network Number ... < 57 > Ethernet Frame Type ... < Ethernet II >...

  • Page 120: Screen 4-4: Configure Appletalk Virtual Network – Example

    ==> 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...
  • Page 121 VIRTUAL NODE NUMBER ... <1> VIRTUAL NETWORK ZONE NAME .. <Research Lab> 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.

  • Page 122: Screen 4-5: Configure The Ethernet Interface – Example

    LCS60 Configuration and Connection for PPP Service Screen 4-5: Configure the Ethernet Interface – Example Top>Config># etherif TCP/IP ETHERNET INTERFACE CONFIGURATION MENU 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 ] ==>...

  • Page 123: Ppp Service Connection Dialstrings

    PPP Service Connection Dialstrings One of the following types of dialstrings (shown with the area/exch/name from the example in Figure 4-1) may be used to connect to the LCS60 for PPP service. Issue 3 LCS60 Configuration and Connection for PPP Service...
  • Page 124 Specifies whether echo requests are disabled (0) and the time to discon- nect (N, where N is a number greater than 3). By default, the LCS60 will send out an echo request every 60 seconds over each PPP connection to check that each link is up.

  • Page 125: Privately Administered Static Ip Address

    IP address on the PPP client package. This IP address will be negotiated with the LCS60. If that address is available, your session will acquire that IP address. If the requested IP address is reserved or busy, then the connection will not be successful.

  • Page 126: Reserved Ip Address

    NAC. In the absence of a NAC or an explicit -u option, the user ID defaults to the value guest. If the LCS60 does not find a reserved IP address for the given combination of the IP network and user ID, then the session start up request is assigned a dynamic IP address.

  • Page 127: Dynamically Assigned Ip Address

    The -D option has been omitted from the dialstring and the user does not have a reserved IP address administered in the LCS60 configuration data- base. To obtain a dynamic address from the LCS60 for your Mac or PC you must: Issue 3 LCS60 Configuration and Connection for PPP Service...

  • Page 128: Administration

    DESTINATION: mlkway/earth/morse.ppp..-D Administration Routine administration of the LCS60 includes PPP tasks such as starting or stop- ping PPP and generating PPP-specific reports. Refer to Chapter 8 for complete LCS60 administration and the Glossary for a description of the report fields gen- erated by the administrative commands.
  • Page 129 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 Timeout Sesid State...

  • Page 130: Call Trace Example

    Administration PEER Addr: 2010.114 Zone: Research Lab Router: 2010.1 Top>Session># show ppp 1.1 ip LCS60 Point-to-Point Session IP Configuration: Peer Peer Peer Max Comp Sesid State Addr Slot Slot ===== ======== =============== ==== ==== =============== ===== ===== opened 154.12.23.9 Top>Session># Call Trace Example The following screen shows how to obtain call trace information for PPP.

  • Page 131: Log File

    Log File The log file, ppp.log, is written to by the LCS60 PPP server and contains informa- tion 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...
  • Page 132 Administration 4-22 Issue 3...
  • Page 133 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...
  • Page 134 Table of Contents Issue 3...

  • Page 135: Lcs60 Configuration And Connection For Slip Service

    LCS60 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. If previous configuration (for example, for PPP service) has been performed, some of the steps required for configuring LCS60 for SLIP service may have already been completed (e.g., etherif, ipas).

  • Page 136: Figure 5-2: Configuring 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.
  • Page 137 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.
  • Page 138 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 ? Enter number of mask bits for this subnet [? for help, q for quit] ==>...

  • Page 139: Screen 5-2: Configure Reserved Ip Address – Example

    IP network security groups. A sample session is shown in Screen 5-2. (Refer to the IP Address Assignment by the LCS60 section in Chapter 1 for more information.) Screen 5-2: Configure Reserved IP Address – Example Top>Config># ipas CAUTION: Please refer to the I&A Guide for instructions...
  • Page 140 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.7 ] for [ tbaker ]...

  • Page 141: Screen 5-3: Configure The Ethernet Interface – Example

    Hit return if there are no aliases [q to quit] ==> Enter morse-e0 internet address (e.g. 154.11.21.1) [q to quit] ==> 154.12.21.5 Enter official name of network [154.12] or q to quit ==> dock-net Issue 3 LCS60 Configuration and Connection for SLIP Service Screen 5-3: continued on next page...
  • Page 142 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 ? Enter name of subnet to be added [? for help, q for quit] ==>...

  • Page 143: Slip Service Connection Dialstrings

    The queue is located between the IP protocol and the data switch, therefore, priority queueing only affects datagrams flowing from the LCS60 to the data switch. Specifies the number of Van Jacobson TCP/IP header compres- sion slots to use. The default is 16; the number of slots must satisfy: 3 N 64.

  • Page 144: Privately Administered Ip Address

    In this case, the user’s IP address is locally administered by the user on his/her PC software package. When calling into the LCS60 SLIP service, this requested IP address is presented as part of the data switch dialstring. The LCS60 grants the user’s request for the proposed IP address if the IP address is: A valid IP address allocated from within the IP network range associated with the IP network security group name that he/she has called.

  • Page 145: Reserved Ip Address

    NAC. In the absence of a NAC or an explicit -u option, the user ID defaults to the value guest. If the LCS60 does not find a reserved IP address for the given combination of the IP network and user ID, then the session start up request is assigned a dynamic IP address.

  • Page 146: Dynamically Assigned Ip Address

    LCS60, use a dialstring similiar to the following: DESTINATION: mlkway/earth/morse.slip..154.12.23.11 This specifies the full address of the LCS60 and a specific IP address. The IP address specified in the above dialstring cannot be one of the IP addresses that has been reserved for other users or is in use.

  • Page 147: Stop Example

    Routine administration of the LCS60 includes SLIP tasks such as starting or stop- ping SLIP and generating SLIP-specific reports. This section gives some exam- ples of SLIP-specific tasks. Refer to Chapter 8 for complete LCS60 administration and to the Glossary for the report fields generated by the administrative commands. Stop Example...

  • Page 148: Errors

    For SLIP connection errors, refer to Appendix C. Log File The log file, slip.log is written to by the LCS60 interface software and contains information about incoming SLIP call requests. To display the contents of the log file, use the page command as shown in the example below:...

  • Page 149: Related Commands

    [3] slip1 started loglevel = 3 Related Commands The following commands may be of particular interest when administering the LCS60’s SLIP service: ping The manual pages for these commands are contained in Appendix E of this docu- ment; they are also available online.
  • Page 150 Administration 5-16 Issue 3...
  • Page 151 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...
  • Page 152 Table of Contents Issue 3...

  • Page 153: Lcs60 Configuration And Connection For Arap Service

    If previous configuration (for example, for PPP service) has been performed, some of the steps required for configuring the LCS60 for ARAP service may have already been completed (e.g., atalkas). Skip the steps that have been completed previously.

  • Page 154: Figure 6-2: Configuring Arap Service

    LCS60 Configuration and Connection for ARAP Service Figure 6-2: Configuring ARAP Service config protocol atalk obtain virtual Datakit VCS network name srvsetup configure client side of ARAP service 1 . Obtain the AppleTalk network number and zone name for the virtual network.

  • Page 155: Screen 6-1: Configure Appletalk Virtual Network – Example

    ==> 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...
  • Page 156 Screen 6-1: Continued VIRTUAL NETWORK ZONE NAME .. <Research Lab> 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.

  • Page 157: Arap Service Connection Dialstring

    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. Refer to Chapter 8 for complete LCS60 administration and to the Glossary for a description of the report fields gen- erated by the administrative commands.

  • Page 158: Show Session Example

    Call Trace Example The following screen shows how to obtain call trace information for ARAP. Top>Session> trace arap LCS60 AppleTalk Remote Access Protocol Tracking Information: - - - - - Remote Addr - - - - - Sesid Name Zone...

  • Page 159: Log File

    Log File 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...
  • Page 160 Administration Issue 3...
  • Page 161 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.0 Administration Service Ports...
  • Page 162 Table of Contents Issue 3...

  • Page 163: Service

    LCS60 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. If previous configuration (for example, for TCP/IP service) has been done, some of the steps required for configuring LCS60 for gateway services may have already been completed (e.g., protocol, etherif).

  • Page 164: Figure 7-2: Gateway Services Configuration

    For details, including a description of service ports, refer to Chapter 1. After configuring the LCS60 as described under Initial Setup in Chapter 3, per- form the steps shown in Figure 7-2 to configure the LCS60 Gateway Services.
  • Page 165 500. 4 . Configure TCP-to-asynchronous gateway service ports (srvports): Up to 500 TCP service ports can be configured if the LCS60 is used Note: for gateway service only. The ports are identified by a number and can be customized with pre-defined destinations (PDDs), disconnect options, inactivity timers, and other options.

  • Page 166: Screen 7-1: Gateway Service Configuration – Example

    [ Type q to quit, ? for help, or press RETURN for default of "n" ] Enter y,n ==> y Enable the LCS60 NOHUP (no hangup) feature for this port? [ Type q to quit, ? for help, or press RETURN for default of "n" ] Enter y,n ==>...
  • Page 167 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 *** NOTICE *** Entering port < 4419 > to provide < telnet > service as follows: >...
  • Page 168 [ Type q to QUIT, ? for HELP, or press RETURN for default of "1024" ] ==> 8192 Enable the LCS60 NOHUP (no hangup) feature for this port? [ Type q to quit, ? for help, or press RETURN for default of "n" ] Enter y,n ==>...
  • Page 169 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 ... 8192 - 8-bit character mode ... Enabled - Inactivity timeout(minutes) ...

  • Page 170: Access To Gateway Services – Dialstrings

    Access to Gateway Services – Dialstrings Telnet Service The following dialstring options are available for the telnet service. The usage is: telnet [-e off char ] [-8] [-B] [-D off char ] [-M:raw uucp] [-tterminal] [-w 1-16k ] host-name [port] When using more than one option, the options must be separated by a colon (:).

  • Page 171: Inactivity Timeout Option

    port Is an optional TCP port number to which the user wants to con- nect 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 Circuit Open Trying to connect to 154.12.26.1 ...

  • Page 172: Return To Destination Option

    Access to Gateway Services – Dialstrings Return to DESTINATION Option 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>...

  • Page 173: Async-To-Tcp Gateway Service

    1 . The LCS60 must be configured to use a DNS server, or 2 . The name of that destination must be properly entered into the LCS60’s configuration database (e.g., through the addhost command), or 3 . The user must request the destination from the telnet prompt by opening a dotted IP numerical address (e.g., open 123.45.6.78).

  • Page 174: Tcp-To-Async Gateway Service

    To use the TCP-to-async gateway service, the user can issue a telnet command to the LCS60’s IP address with or without the use of a service port. If no service port is configured, enter the call address of the data-switch connected host. Log on in the usual manner.

  • Page 175: Uucp Feature

    CommKit Host Interface connected hosts by means of the LCS60, configure CommKit Host Interface connected hosts to regularly poll Ethernet-connected hosts for uucp traffic. There are two ways to set up the uucp feature for data switch to LCS60 to LAN file transfer: Issue 3...
  • Page 176 DNS server. area and exch represent the area and exchange of the data switch to which the LCS60 is connected, and 60name is the name of the LCS60 performing the telnet. For tcpsock, 540 is the service type.

  • Page 177: Lan To Lcs60 To Data Switch

    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. Note: Configuration of the service port for socket service requires super user permission.

  • Page 178: Example Uucp Service Using Sunos 4.0

    LCS60 database to provide socket service and 60name is the name of the LCS60 that is used as the TCP-to-Async gateway. Note:...

  • Page 179: Example Uucp Service Using Ncr 4.0

    Note: 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. Using port 2981 as configured above (and referring to Figure 7-1), the string...

  • Page 180: Service Ports

    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. Service Ports The following screens show a variety of port commands: Top>...

  • Page 181: Trace Tcp/Async

    Cap. Directory ===== ==== ==== ========= Top>Ports> Trace TCP/Async The following screen shows a typical trace: Top> session Top>Session> trace tcp LCS60 TCP to Async Gateway Tracking Information Sesid State Port Foreign Address ===== ===== ===== ==================== CONN 154.12.24.44.1188 CONN 154.12.24.47.2331...

  • Page 182: Table 7-1: Gateway Services - Log Files

    Administration Log Files 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 Log File Information tcpasy#.log TCP-to-Async sessions asytcp#.log Async-to-TCP sessions tcplisten.log...
  • Page 183 Administration Basics Logging On 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...
  • Page 184 Network Access Password Option Deleting the Network Access Password Changing the Network Access Password Status Error Messages Error Messages from the LCS60 Fiber Interface Console Error Messages Hardware Error Messages Server Error Messages Call Error Messages Lucent Technologies Data Switch Server Log File...

  • Page 185: Basics

    Only the superuser has the freedom to do all of the tasks needed to administer an LCS60. To restrict the users with superuser privileges give the root password only to approved users.

  • Page 186: 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 dis- abled state. The system administrator can enable this feature: 1 . Go to the srvtab directory: # cd /etc/opt/dk/srvtab 2 .

  • Page 187: Lcsadm Interface

    # dkcu mlkway/earth/morse.lcsadm Circuit Open LCS60 Administrative Command Interface. morse:Top> Remote access is impossible before the system is configured and the Note: dkhost protocol has been started. lcsadm Interface The lcsadm interface uses a hierarchical system of directories and commands as shown in Figure 8-1.

  • Page 188: Common Commands

    lcsadm Interface Figure 8-1: lcsadm Interface Directory Structure start stop Config Session kill addhost ipas show addnet trace maxsessions atalkas types nodename backup protocol console snmp datetime softwarekey delhost srvports delnet srvsetup dftroute Note: All commands in directories shown subnet bold-italic typeface upgrade shown in...

  • Page 189: Top Directory Commands

    Chapter 3. Top Directory Commands Once you log onto the LCS60, the Top prompt is displayed. This indicates you are in the LCS60 Top Directory. To display the options available from this direc- tory, use the key as shown in Screen 8-1.
  • Page 190 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 pro- tocols can be started individually or all at once using the all option.

  • Page 191: Session Directory Commands

    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 start ppp tcpip, ppp start routed tcpip, routed start slip tcpip, slip start snmp tcpip, snmp start tcpasy tcpip, tcpasy start tcpip...
  • Page 192 lcsadm Interface Screen 8-2: Session Directory Top>Manager># session Top> Session ># Return Commands may be abbreviated. Commands are: config/ help quit service/ types The following commands are available from the Session directory: Name kill kill service-type sesid [sesid ...] Synopsis Description The kill command terminates a session with the specific service type and session ID (sesid) entered.
  • Page 193 ID, the ip, atalk, link, and ipx options are available to show IP, AppleTalk, link, or IPX configuration informa- tion 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: Sesid State ===== ======== opened LOCAL Addr: 2010.1...

  • Page 194: Ports Directory Commands

    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. They are: Types Description ===== =========== tcpasy TCP/Async Service...
  • Page 195 Name disable or enable disable port# [port#2 ...] Synopsis 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.

  • Page 196: Service Directory Commands

    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. Screen 8-4: Service Directory Top>...

  • Page 197: Manager Directory Commands

    The types command lists the available service types. Manager Directory Commands The Manager directory (Screen 8-5) provides utilities to obtain information about the LCS60 management (LCM) subsystem components. This directory is not used for standard administration but should only be used for diagnostic admin- istrative purposes.
  • Page 198 Description The log command is used to obtain and change the verbosity of the log level of the LCS60 manager (lcm.log). The higher the number given for the log level, the more detailed the log file; valid values are 3, 6 (default), and 20.
  • Page 199 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.

  • Page 200: Config Directory Commands

    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 3, 6, 9 slip 3, 6 atmgr...
  • Page 201 The addhost/delhost commands allow the system adminis- trator to add or delete hosts (names and addresses) in the network by adjusting the LCS60 database file. The addnet/ delnet commands allow the system administrator to add or delete the network by adjusting the LCS60 database file.
  • Page 202 Synopsis backup Description This command generates a menu which allows you to per- form the full range of LCS60 backup and restore opera- tions. Refer to the section Backup and Restore Operations later in this chapter. Name console Synopsis...
  • Page 203 1-800-WE2CARE for your particular LCS60 before you can complete the softwarekey command. An example of the softwarekey command is shown below. The software key is specific to the release of the LCS60 and will not grant access to features introduced in later releases.
  • Page 204 /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. Please refer to the Software Certificate for details on obtaining a Software Key from the WECARE Support Center (1-800-WE2-CARE).

  • Page 205: Typical Administrative Tasks

    (as found in the /etc/networks file). Typical Administrative Tasks This section gives a few examples of tasks the LCS60 Administrator may per- form. For LCS60 service-specific tasks refer to the appropriate chapter: PPP (Chapter 4), SLIP (Chapter 5), ARAP (Chapter 6), gateway (Chapter 7).

  • Page 206: Show Session Example

    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: Char Total Sesid Service Mode Xmit(Bytes) Recv(Bytes) Connect Time ===== ========== ==== =========== =========== ============ ========= 2.93...

  • Page 207: Log Level Example

    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 Top>Config># dftroute CURRENT default route is ... 154.12.21.3 DEFAULT ROUTE FUNCTIONS ==================================================== 1 ... Define the default route 2 ...

  • Page 208: Summary Output Examples

    Cfg. ============ ==== tcpasy slip -ipx -atalk arap Totals Top>Service># port Top>Ports># summary LCS60 TCP/Async Service Port Summary Information: Limit Cfg. Cap. Directory ===== ==== ==== ========= 2001 System Console Parameters– Autobaud The following screen shows an example of the autobaud feature being disabled.

  • Page 209: Backup And Restore Operations

    Top>Config># Backup and Restore Operations The LCS60 backup and restore capabilities have been provided to help protect the substantial investment in time and effort that may have been required to work out the necessary networking definitions, administer them using LCS60 commands and functions, and then verify that they are correct.

  • Page 210: Generic Vs. Variable Files

    The hard disk of each LCS60 stores both kinds of files. Generic files are the same on every LCS60, and never change. For example, executable programs such as lcsadm are generic files, whereas the TCP/IP configuration file /etc/hosts is a variable file.

  • Page 211: Local And Remote Modes

    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 confi- guration files from the hard disk to a removable tape, and to restore configura- tion files to the hard disk from a tape.
  • Page 212 Insert a blank tape – which is not write-protected – into the tape drive when instructed to do so. If the LCS60 has been configured as a backup/restore server, the tape that is created will also contain the backups of all of the server’s clients.

  • Page 213: To Restore From Tape

    server, itself, was never backed up to tape, then the backups for the entire net- work 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.

  • Page 214: To List The Contents Of A Tape

    The directory /etc/opt/dk is restored as part of a Server restore. Config restores configuration files for the LCS60. The Config restore will fail unless TCP/IP has been stopped. Caution: When performing a Server or COMPLETE restore, the restored database will be the database of the last backup.

  • Page 215: Security — Authorizing Clients And Servers

    The centralized backup/restore feature allows: An LCS60 configured as a server to copy to its hard disk variable confi- guration files from multiple remote LCS60s (and LCS50Es) configured as clients. The remote backup is done disk-to-disk over the data switch net- work.

  • Page 216: Access To Backup/Restore Functions – Clients And Servers

    Access to Backup/Restore Functions – Clients and Servers 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. To access the centralized backup/restore functions needed by a backup/restore client, use the Backup/Restore menu (Screen 8-9 obtained by selecting option 1 from Screen 8-8).

  • Page 217: Defining Backup/Restore Servers On A Client

    In the case in which you are reconfiguring a client to be a server, you must first delete all servers previously defined for the LCS60. Select option 2 on Screen 8-12 to delete the servers. This is required because a backup/restore server may not define other servers.

  • Page 218: Defining Backup/Restore Clients On The Server

    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.

  • Page 219: Backup Or Restore Functions

    To reconfigure a server as a client, delete all of its clients (option 2 on Screen 8- 13). 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.
  • Page 220 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.
  • Page 221 A restore from server example follows: Restore a client’s variable files. Clients known by this server ======================================== brown Enter client name [ Type q to quit or ? for help ] ==> brown Backups for client "brown" ======================================== wednesday -- Dec 19 10:48 monday -- Dec 17 09:55 Type name of backup or press RETURN for default of "wednesday"...

  • Page 222: Creating A Tape

    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.

  • Page 223: Screen 8-17: Tcp-To-Async Gateway With Network Access Password

    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. morse LCS60 DESTINATION: mlkway/earth/watson login: Note: The Network Access Password prompt appears only if the password option is set.

  • Page 224: Deleting The Network Access Password

    The password will not echo on the screen. The new password will become effective immediately. Status The system administrator can query the LCS60 to obtain process, fiber, and Eth- ernet interface status at any time using the command statlcs -t. An example is shown below:...

  • Page 225: Error Messages

    UP. Note: 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 are displayed on the LCS60 system console. Issue 3 Status 8-41...

  • Page 226: Error Messages From The Lcs60 Fiber Interface

    CPM-HS is removed from service during operation, or if a power failure occurs on the data switch node, the following error message will appear on the LCS60 system console indicating the loss in communication with the data switch.
  • Page 227 RX-MUTE 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 CPM- HS is properly installed in the data switch slot and that there is optical connectivity between the LCS60 and the CPM-HS.

  • Page 228: Server Error Messages

    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.

  • Page 229: Lucent Technologies Data Switch Server Log File

    Lucent Technologies Data Switch Server Log File The log file, dksrvlog, is written to by LCS60 interface software and contains infor- mation 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.

  • Page 230: Additional Log Files

    A number of other log files that can be examined for troubleshooting and diag- nostic purposes are contained in the directory /usr/adm/lcs. These files are writ- ten to by the LCS60 application software and contain information as shown in Table 8-3.

  • Page 231: Table 8-3: Log Files

    Table 8-3: Log Files Log File Information adial.log Dialer information arap.log 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# .log TCP-to-Async sessions tcplisten.log TCP-to-Async service The tcpasy#.log file is located in the directory /usr/adm/lcs/tcpasy.
  • Page 232 Error Messages 8-48 Issue 3...
  • Page 233 Maintenance Reload System Software UNIX System Software Installation UFS Utility Fixes Tape Installation inet Package Removal LCS60 Application Software Installation Removing the LCS60 Application Software Upgrade Remote Upgrade Installing an Upgrade on a Remote Upgrade Client Processor Board Firmware Update...
  • Page 234 Table of Contents 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 9-25 9-28...

  • Page 235: Reload System Software

    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. A new installation of the UNIX System will destroy all files currently on disks used for the installation.

  • Page 236: Screen 9-1: How To Enter System Responses

    Reload System Software 6 . Enter bo 0 40 COREunix at the 197-Bug> prompt. This will generate ins- tallation 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.
  • Page 237 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...
  • Page 238 Reload System Software 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 ) Final Verification of 1-disk installation Device Disk description m197_c0d0 1GB SCSI (SEAGATE) Partition...
  • Page 239 Should the disable/enable commands be available to ALL users?[ y n ]( n ) lp Package Query #3 Will you be attaching a PostScript printer to this system? [ y n ] ( y ) nsu Package Query #1 Enter the number of pseudo-terminal devices...
  • Page 240 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 Invalid VTOC read on unit xx Press <RETURN> to continue with formatting or interrupt (CTRL-c) to abort: Slicing Installation Disk(s) Activating Swapping To Disk Making File Systems...

  • Page 241: Ufs Utility Fixes Tape Installation

    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.

  • Page 242: Inet Package Removal

    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.

  • Page 243: Lcs60 Application Software Installation

    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 con- duct the dialogue (as root; from the Console login) shown in Screen 9-4.
  • Page 244 Reload System Software Screen 9-4: continued. Processing package instance <lcs60> from </dev/rmt/ctape1> 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...
  • Page 245 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 ! ! ! Log off now or risk your files being damaged.
  • Page 246 Building symbols in /tmp/sa.adrfl for /stand/unix Starting process accounting Print services started. Your LCS60 Network Interface must be set up by you. When you see the "login" prompt you must login as "root" and then type: lcsadm config initsetup followed by the RETURN key.

  • Page 247: Removing The Lcs60 Application Software

    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.

  • Page 248: Screen 9-5: Lcs60 Application Software Removal – R2.0 Example

    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 <lcs60>...

  • Page 249: Upgrade

    R3.0. 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).

  • Page 250: Remote Upgrade

    To upgrade many R2.0 or later LCS60s to release 3.0 or later, the local tape drive need only be used to install the upgrade release on a single R2.0 or R3.0 LCS60, the remote upgrade server. All other LCS60s in a network are remote upgrade clients and can be upgraded remotely over the data switch from the server.
  • Page 251 5 . On the server; select item 5 under the SERVER Procedures and answer the prompts accordingly. Note: A server can only maintain (i.e., spool) one copy of an LCS60 software generic and an LCS60 patch. Therefore, if a copy already resides on the server, this procedure will automatically remove it before copying the newer generic from tape onto disk.
  • Page 252 # pkgadd -d /var/spool/pkg Continue with step 10 below. 9 . On the client, select menu item 3. This will install the downloaded LCS60 software generic. After this step has been completed successfully you may exit or quit from the lcsadm command.

  • Page 253: Processor Board Firmware Update

    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.
  • Page 254 Processor Board Firmware Update Network Auto Boot at power-up only [Y/N]= N? Network Auto Boot Controller LUN = 00? Network Auto Boot Device LUN = 00? Network Auto Boot Abort Delay = 15? Network Auto Boot Configuration Parameters Pointer (NVRAM) = 00000000? Memory Search Starting Address = 00000000? Memory Search Ending Address = 02000000? Memory Search Increment Size = 00010000?
  • Page 255 Master Enable #2 [Y/N]=N? Master Starting Address #2 = 00000000? Master Ending Address #2 = 00000000? Master Control #2 = 00? Master Enable #3 [Y/N]=N? Master Starting Address #3 = 00000000? Master Ending Address #3 = 00000000? Master Control #3 = 00? Master Enable #4 [Y/N]=N? Master Starting Address #4 = 00000000? Master Ending Address #4 = 00000000?

  • Page 256: Screen 9-6: Set And Env Commands

    Processor Board Firmware Update Screen 9-6: set and env Commands Copyright Motorola Inc. 1988 - 1994 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... 02000000 Done Idle MPU(s) : NONE 197-Bug>...

  • Page 257: Processor Diagnostics - Mvme197

    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).
  • Page 258 Processor Diagnostics - MVME197 Display Pass Count ECDM ECDM Tests (DIR) Help on Tests/Commands Help Extended Loop Always Mode LANC LAN Coprocessor (Intel 82596) Tests (DIR) Loop Continuous Mode Loop on Error Mode Line Feed Mode Loop Non-Verbose Mode MASK Self Test Mask NCR 53C710 SCSI I/O Processor Test (DIR) Non-Verbose Mode...

  • Page 259: Vmedkhs Diagnostics

    If this LED is lit, check the cable connection. If the connection is complete, reverse the fiber cable connection on either the LCS60 or the CPM- HS (whichever is more convenient).

  • Page 260: Screen 9-7: Example Diag Cpm For Cpm-Hs Module

    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;...
  • Page 261 Restore the CPM-HS to service as shown in Screen 9-7 (res cpm #). Verify that the CPM-HS is active as shown in Screen 9-7 (display conn mod #). 4 . Restart the LCS60 software using the start dkhost command from the lcsadm interface. Issue 3...

  • Page 262: Connection Verification

    LCS200 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. From the LCS60 system console, use the following format: dkcu call address where call address is the call address of a fiber-connected host.

  • Page 263: Lcs60 To Local Ethernet Host Verification (Ping)

    LCS60 to Local Ethernet Host Verification (ping) Use the ping command to verify the connectivity between a LCS60 and an Ether- net host on the LAN attached to the LCS60. Log onto the LCS60 system console as user root. Enter the following command:...

  • Page 264: Memory Dump

    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.

  • Page 265: Screen 9-8: Service Menu

    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 .

  • Page 266: After The Dump Is Completed

    Service Menu (Screen 9-8). 10 . Reboot the LCS60 using the 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. Login as root...
  • Page 267 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...
  • Page 268 Table of Contents Issue 3...

  • Page 269: 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.

  • Page 270: System Field

    srvtab system service flags Delimit fields by tabs only. Do not use blanks. Note: 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.

  • Page 271: Service Field

    (generally login) arap ARAP asterisk wild card (matches any requested service) authorize authorize (see also the section User Field) LCS60 backup and restore do (invoke commands on remote hosts) lcsadm LCS60 administrative interface login login pupu file transfer...

  • Page 272: Flags Field

    srvtab Flags Field 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.

  • Page 273: User Field

    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.

  • Page 274: Program Field

    srvtab Table A-2: User ID Mapping Options Option *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. For example, an initial 0x or 0X indicates hexadecimal, and an initial 0 indicates octal.

  • Page 275: Initial Parms Field

    Initial Parms Field The initial parms field (fixed program arguments field) of a server table entry speci- fies 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.

  • Page 276: Server Table Scanning Rules

    srvtab Table A-3: Continued Specification The local server name. The originator, as known to the local node. The originating module number of the call being serviced. The originating data switch node name. The type of originating device. Parameters from the dialstring. The parameters are reparsed so that colons may be used to produce separate arguments.

  • Page 277: Modifications To The Server Table

    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 adminis- trator 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.
  • Page 278 srvtab A-10 Issue 3...

  • Page 279: Configuration Of The Starkeeper Ii Nms

    StarKeeper II NMS Configuration of the StarKeeper II Diskette or Tape Installation StarKeeper II NMS – Configuration Commands Alarms to StarKeeper II NMS Issue 3...
  • Page 280 Table of Contents Issue 3...

  • Page 281: Configuration Of The Starkeeper Ii Nms

    Configuration of the StarKeeper II NMS 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 plat- form. Note: To verify the version of StarKeeper II NMS that you are running, log on to the StarKeeper II NMS as cnmsadm.
  • Page 282 3 . At the SK: prompt, enter the su command with no arguments to change your user id to root. 4 . Confirm that the StarKeeper II NMS Support for LCS60 for Ethernet package has not been previously installed on this StarKeeper II NMS. At the # prompt enter the /usr/bin/displaypkg command (6386) or the cat -s $INPUT/L60.name command (HP 720/730).
  • Page 283 Network Interface for Ethernet R3.0 StarKeeper® NMS RX.Y Support for AT&T 6386 into the disk drive when instructed to do so. Insert the tape labeled LCS60 Network Interface for Ethernet For HP Hardware R3.0 StarKeeper® NMS RX.Y Support for Hewlett-Packard into the tape drive and wait until the light stops blinking.
  • Page 284 3 . Select menu item System/Node by pressing "Configure a System/Node" menu. 4 . Select menu item Add by pressing 5 . At System/Node name enter the name of the LCS60 (e.g., morse the example in Figure 3-1). 6 . At Type enter L60 Return .
  • Page 285 Step 5 (e.g., room number) followed by a Return . 9 . At Time zone enter the applicable time zone for the LCS60 entered in Step 5 followed by a (refer to the StarKeeper II NMS documentation for Return format details).

  • Page 286: 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.
  • Page 287 Action: The recommended action for reason code 1 is as follows. Verify the con- nection 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.
  • Page 288 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.
  • Page 289 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.
  • Page 290 Alarms to StarKeeper II NMS B-10 Issue 3...

  • Page 291: User Error Messages

    User Error Messages Cable Error Message Outgoing Call Error Messages Incoming Error Messages SLIP Sessions Issue 3 C-10...
  • Page 292 Table of Contents Issue 3...

  • Page 293: Cable Error Message

    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. 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.
  • Page 294 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 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.

  • Page 295: Outgoing Call Error Messages C

    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. Destination not recognized Some part of the requested destination is not defined in the network.
  • Page 296 Outgoing Call 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 identi- fied by its appropriate error code in the following error message where xxx is the code number.
  • Page 297 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.
  • Page 298 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). 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.
  • Page 299 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. No answer from dialed number 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;...
  • Page 300 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 A connection cannot be completed because a data switch trunk or com- mon data switch control computer database somewhere in the network path is inoperable.

  • Page 301: Incoming 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. Trunk busy The call could not be completed because a trunk in the call path is busy. Trunk configuration mismatch.
  • Page 302 IP address is reserved The IP/SLIP client requested an IP address on his/her data switch dial- string that has been reserved by the LCS60 administrator. If a user wishes to request his/her own reserved IP address, then he/she should omit the IP address from his/her data switch dialstring.
  • Page 303 Either insufficient resources are available to allocate another SLIP session or one of the required system processes cannot be contacted to set up the user’s session. Try again later; if the problem persists contact the LCS60 administrator. may have only one -s option, got dkserver name and name from...
  • Page 304 Incoming Error Messages mtu= MTU size , 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 IP address The user specified both the -D option and a privately administered IP address in his/her dialstring.
  • Page 305 Software Installation – Fujitsu or Seagate ST5660N Drive Reload System Software UNIX System Software Installation Issue 3...
  • Page 306 Table of Contents Issue 3...
  • Page 307 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.

  • Page 308: Screen D-1: How To Enter System Responses

    UNIX System Software Installation 5 . Determine which type of drive you have by typing ioi at the 197-Bug> prompt. The response to the ioi command is shown below for each of the three types of drives: Seagate ST5660N VME197 Seagate ST11200N VME197 Fujitsu...
  • Page 309 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 .
  • Page 310 UNIX System Software Installation Add the following line to the file: "SEAGATE" "ST5660N" Note: Separate the fields above using tabs only; spaces are not allowed. Write and quit the file. 10 . For the Seagate ST5660N drive only: Enter installation menu and continue as shown below: Ctrl-D Leaving maintenance shell: UNIX SYSTEM V/88 Release 4 Upgrade/Installation...
  • Page 311 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...
  • Page 312 UNIX System Software 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 ) Final Verification of 1-disk installation Device Disk description see note below m197_c0d0 Partition Slice...
  • Page 313 Should the disable/enable commands be available to ALL users?[ y n ]( n ) lp Package Query #3 Will you be attaching a PostScript printer to this system? [ y n ] ( y ) nsu Package Query #1 Enter the number of pseudo-terminal devices...
  • Page 314 18 . For both the Fujitsu and Seagate ST5660N drives: Continue with the pro- cedures described in Chapter 9 to install the UFS Utility Fixes Tape, remove the inet package, and install the LCS60 application software. key to continue the shutdown and...
  • Page 315 Manual Pages ATLOG ATNETSTAT ATPING DKCU DKMAINT IFCONFIG IFSTAT Table of Contents E-19 E-21...
  • Page 316 Table of Contents IFTRACE IPXNETSTAT IPXPING NETSTAT NSLOOKUP PING PULL PUSH ROUTE E-24 E-26 E-27 E-28 E-30 E-34 E-35 E-37 E-40 Issue 3...
  • Page 317 STATLCS TELNET Table of Contents Table of Contents E-42 E-43...
  • Page 318 Table of Contents Issue 3...
  • Page 319 ATLOG 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: Specify e to trace ECHO.
  • Page 320 ATNETSTAT ( 1M ) NAME atnetstat - show AppleTalk network status SYNOPSIS atnetstat - i r z [-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.
  • Page 321 ATNETSTAT Gateway the address of the next router to which packets intended for this Destination will be sent or local if the Destination is directly con- nected to the router. Distance the number of router hops from the router to the Destination net- work.
  • Page 322 It is also possible to contact routers on networks OTHER THAN that to which the LCS60 is attached by specifying a zero node, as in net.0 (Refer to Inside AppleTalk, p. 4-7). It is not possible to contact the AppleTalk addresses that correspond to the LCS60’s virtual network port or to its...
  • Page 323 ATPING DIAGNOSTICS Exit status is zero for normal terminations; a positive number for error termina- tions. FILES /usr/etc/atping /usr/etc/atlog /usr/etc/atnetstat SEE ALSO Inside AppleTalk, Second Edition, Chapter 6. Issue 3 ATPING ( 1M )
  • Page 324 DKCU ( 1C ) 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 It places a call to the destination host or terminal on the data switch network.
  • Page 325 DKCU ˜ %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.
  • Page 326 DKMAINT ( 1M ) 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.
  • Page 327 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.
  • Page 328 FTP ( 1 ) 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 argu- ment, and pipe the output of the ftp command to the shell in the usual manner.
  • Page 329 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. Terminate the FTP session with the remote server and exit the ftp program.
  • Page 330 FTP ( 1 ) form format Set the vertical format control for ASCII and EBCDIC file transfers to for- mat. 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.
  • Page 331 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 ...
  • Page 332 FTP ( 1 ) 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 dif- ferent file naming conventions or practices.
  • Page 333 proxy ftp-cmd Execute an FTP command on a secondary control connection. This com- mand 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 connec- tion;...
  • Page 334 FTP ( 1 ) 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.
  • Page 335 ‘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.
  • Page 336 FTP ( 1 ) 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 unex- pected results.
  • Page 337 IFCONFIG 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 net- work 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).
  • Page 338 IFCONFIG ( 1M ) 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 rout- ing metric is used by the routing protocol routed(1M).
  • Page 339 IFSTAT 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 confi- guration file.
  • Page 340 IFSTAT ( 1M ) 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.
  • Page 341 IFSTAT No ifstat-supporting driver found via ip Failed to open config file Device line format bad in config file Action in device line of config file bad Code format bad in config file Failed to initialize terminal for curses Failed to open device specified in config file MACIOC GETSTATS (get statistics) ioctl to driver failed Issue 3 IFSTAT ( 1M )
  • Page 342 IFTRACE ( 1M ) 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 dis- card broadcast packets (-b), to select received (-r) and/or transmitted (-t) packets, as well as to filter packets based upon keywords.
  • Page 343 IFTRACE – d 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.
  • Page 344 IPXNETSTAT ( 1M ) 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 net- work statistics related to IPX packet traffic.
  • Page 345 To use ipxping for fault isolation, the hexidecimal IPX address of the target node must be specified in network:node format. While it is possible to contact the IPX address of the LCS60’s Ethernet port, it is not possible to contact the addresses that correspond to the LCS60’s virtual IPX network port.
  • Page 346 NETSTAT ( 1 ) 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.
  • Page 347 NETSTAT 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.
  • Page 348 NSLOOKUP ( 1 ) 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.
  • Page 349 NSLOOKUP 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.
  • Page 350 NSLOOKUP ( 1 ) 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. Internet address (the default) of the host CNAME canonical (official) name for an alias...
  • Page 351 NSLOOKUP 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).
  • Page 352 PING ( 1M ) 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, pri- marily for manual fault isolation. The DARPA Internet is a large and complex aggregation of network hardware connected by gateways.
  • Page 353 PULL 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 ´/´.
  • Page 354 PULL ( 1C ) 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 ´/´...
  • Page 355 PUSH NAME push – transfer files to another system SYNOPSIS push [ – L ] destination filename ... directory push [ – L ] destination – directory DESCRIPTION push establishes a data switch circuit to the target (remote) host named in destina- tion and transfers files to that host.
  • Page 356 PUSH ( 1C ) 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 pre- SVR4 implementations support long file names but the push com- mand has no way of knowing if these systems do or do not.
  • Page 357 PUSH local machine will be used as the file modification time. FILES /opt/dk/bin /etc/opt/dk/dkhosts 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. Issue 3 PUSH ( 1C ) directory in which this command resides...
  • Page 358 ROUTE ( 1M ) NAME route – manipulate the routing tables SYNOPSIS route flush [ net host ] route add [ net host ] destination gateway metric [netmask value] [mtu value] route delete [ net host ] 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.
  • Page 359 ROUTE 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.

  • Page 360: Statlcs E

    STATLCS ( 1M ) 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 out- puts the status into the file /tmp/statlcs.log...
  • Page 361 TELNET 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 ).
  • Page 362 TELNET ( 1 ) 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 communi- cation with hosts using an 8-bit character set such as the European or Asian character set.
  • Page 363 TELNET 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) timing mark (send a timing mark)
  • Page 364 TELNET ( 1 ) The valid NVT commands are: send an abort output request send a message (are you there?) to remote server send a break request send an erase character request send an erase line request send a data mark to signify end of urgent data send an interrupt request send a null operation display a list of transnvt commands.
  • Page 365 User Information Introduction Client Software Configuration Client Packages Mac Connection – CCL Script CCL and Modem Hints 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.0 Issue 3...
  • Page 366 Table of Contents ARAP Service Example Connection (via Modem) F-22 F-22 Issue 3...

  • Page 367: Client Software Configuration

    LCS60 side of the configuration only. Client Software Configuration To use the LCS60 as a server for ARAP, PPP, or SLIP service, the remote user must have client software loaded on his or her PC or Macintosh that conforms to the ARAP, PPP, or SLIP protocol specifications.

  • Page 368: Client Packages

    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.

  • Page 369: Screen F-1: Ccl Script – Example

    Screen F-1: CCL Script – Example @ORIGINATE @ANSWER ! (xxxxx) note "Communicating at 38400 bps." 2 CommunicatingAt 38400 serreset 38400, 3, 8, 1 note "Dialing ^1" 3 write "ATDT^1/38400\13" @LABEL 19 write "\13" matchstr 1 20 "USERID" matchread 400 jump 59 @LABEL 20 note "Got USERID"...
  • Page 370 Client Software Configuration Screen F-1: Continued @LABEL 59 exit -6019 ! Attempt to hang up the modem @HANGUP exit 0 Edit this script with the information appropriate for your modem and configuration. The entries in the above script are described below: Indicates a comment.

  • Page 371: Ccl And Modem Hints

    USERID, Password, Your user ID, password, and DESTINATION. DESTINATION nj/exch/system.ppp Your LCS60 dialstring for PPP; use the ARAP dialstring, nj/exch/system.arap, for ARAP. Terminates execution of the script (in this exit 0 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).

  • Page 372: Modem

    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.

  • Page 373: Pc Configuration

    3 . Once you have entered the connection parameters, a Connect to window will be displayed. Enter the appropriate information. This will open a Terminal Window in which you can authenticate and enter the data switch dialstring for the LCS60. Issue 3 PPP Service Examples...

  • Page 374: Figure F-1: Windows 95 Ipx Over Ppp – Example Screens

    PPP Service Examples Figure F-1: Windows 95 IPX Over PPP – Example Screens Figure F-2: Windows 95 IPX Over PPP – Connect To Example Screen Issue 3...

  • Page 375: Ppp Connection

    PC/TCP software. The dialup script initializes and dials the modem, handles login authentication (such as login/password prompts from the NAC) and sends the LCS60 dialstring in response to the Lucent Technologies data switch DESTINATION prompt. The hangup script will terminate the PPP connection and hang up the modem. Tem- plates for these scripts are supplied with the package;...

  • Page 376: Screen F-2: Sample Lcs60 Dialup.scr

    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 })

  • Page 377: Ppp Connection

    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, {})

  • Page 378: Figure F-3: Pc/Tcp Example Screens

    (c:\pctcp\dialmt.scr) The choices for servers and scripts are read from the pctcp.ini file. Make sure you have added a session for the LCS60 server and created the dialup and hangup scripts for it. Select to set up your connection configuration for the Configure...

  • Page 379: Figure F-4: Pc/Tcp Session Configuration Screen Example

    Set the port and baud rate to the ones you are using with your modem. Enable hardware flow control. To have the LCS60 assign your client software an IP address dynamically, leave the IP address as zeroes and add the -D option to your data switch dialstring. For a privately administered address, enter the IP address your LCS60 administrator assigned to your client software.

  • Page 380: Interppp

    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 InterPPP II is different from InterPPP. Refer to the user documentation Note: for specific details. The InterPPP software requires minimal Mac configuration for AppleTalk or IP over PPP.
  • Page 381 — Under File, select Save As to save the setup to a file name (for — example, lcs60). This will allow you to launch lcs60 the next time you want to establish the PPP connection, rather than repeating this procedure.

  • Page 382: Figure F-5: Network Control Panel

    PPP Service Examples Figure F-5: Network Control Panel Figure F-6: Modem Port and PPP Screens F-16 Issue 3...

  • Page 383: Figure F-7: Ip Address Screen

    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.

  • Page 384: Figure F-9: Appletalk Status Window F

    PPP Service Examples Figure F-8: PPP Connection Screen Figure F-9: AppleTalk Status Window 2010.122 Research Lab morse F-18 Issue 3...

  • Page 385: Slip Service Examples

    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 config- ure the SLIP interface through Windows; Figures F-10 - F12 show an example configuration for dynamic IP address acquisition.
  • Page 386 SLIP Service Examples Note: NEWT will display the dynamic IP address your PC has been assigned. Figure F-11: Custom Setup Window Figure F-12: Login Settings Window The ID, password and dialstring information provided in the Setup Window (Figure F-12) is called in by the scripting language file (in this example, the F-20 Issue 3...
  • Page 387 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.ini File Fragment [DEFAULT] SCRIPT=name: $u$r word: $p$r -n $6$c$r -i TYPE=SLIP [SLIP0] SCRIPT=DESTINATION: $c$r -n $5 TYPE=SLIP [SLIP1] SCRIPT=USERID: $u$r Password: $p$r DESTINATION: $c$r -n $6 -i TYPE=SLIP...

  • Page 388: Arap Service Example

    Use the defaults for all other fields. Under File, select Save As to save the setup to a file name (for — example, lcs60). This will allow you to launch lcs60 the next time you want to establish the ARAP connection, rather than repeating this procedure.
  • Page 389 ARAP Service Example Figure F-13: ARAP Remote Connection – Example Figure F-14: ARAP Remote Access Setup – Connection Screen UNTITLED Issue 3 F-23...
  • Page 390 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.
  • Page 391 ARAP Service Example Figure F-16: ARAP Remote Access Status Screen – Example Issue 3 F-25...
  • Page 392 ARAP Service Example F-26 Issue 3...
  • Page 393 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-16 G-17 G-19...
  • Page 394 Table of Contents Issue 3...

  • Page 395: Glossary

    Datakit II VCS, BNS-1000, or BNS-2000. data switch directory This service allows LAN hosts to query the LCS60 to obtain a service listing of all TCP-to-async port numbers, associated PDDs, and the service type of each port number. Only one port may act as a directory port at a time.
  • Page 396 The point where switching between computers and terminals takes place. node name The name given to a LCS60. This is the hostname and is independent of host interface names. This becomes the uname for this machine (e.g., morse in Figure 3-1).

  • Page 397: Parameters

    Zones allow users to find devices easily. Parameters The following parameters are used in configuring the LCS60. The parameters are listed alphabetically according to the service being configured. AppleTalk Network/Zone (atalkas) network This is a number between 1 and 65279.

  • Page 398: Ethernet Interface (Etherif)

    D-1 of Inside AppleTalk, Second Edition, the only characters that may be entered as the zone name for the LCS60 virtual AppleTalk net- work 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.

  • Page 399: Dns Resolver (Dns)

    This parameter defines the session type: async-to-TCP (asytcp), session parameter TCP-to-async (tcpasy), PPP (ppp), SLIP (slip), and ARAP (arap). maxsessions defines the maximum number of supported LCS60 sessions for all services. session The number of sessions you want to configure for a specific ser- parameter vice.

  • Page 400: Tcp-To-Asynchronous Gateway Services (Srvports)

    Enter y if you want the LCS60 to wait for the user to press the key before it attempts to re-establish the connection.

  • Page 401: Subnetwork Configuration (Subnet)

    Enable, 8-bit 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 character mode enabled. The default (n) is 7-bit character mode. inactivity Enter the time in minutes in which the session will terminate if timeout there is no input or output.

  • Page 402: Report Fields

    31 characters. They may contain letters, numbers, dashes, and underscores. Report Fields The following report fields are found in the LCS60 reports generated by the status commands (e.g, show, trace, etc.). The report fields are listed according to the directory in which they are generated.
  • Page 403 Xmit(Pkts) Number of packets transmitted. Recv(Bytes) Number of bytes received. Recv(Pkts) Number of packets received. Recv Errs Indicates a checksum error for the received PPP frame. BadF Indicates the number of invalid frames received. Indicates the number of duplicate or out of sequence frames rejected.
  • Page 404 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.
  • Page 405 Max Config The number of times the LCS60 will try to configure a connec- tion before quitting. The number of times the LCS60 will try to terminate the link to Max Term the PPP host gracefully before dropping the connection.
  • Page 406 Local Addr The IP address of the LCS60. Local Max Indicates whether Van Jacobson header compression is being used by the LCS60 or not (0). If used, the number is the max- Slot imum number of slots. Local Comp The LCS60’s identifier field compression setting (refer to the Slot documentation for the PPP package you are using).
  • Page 407 Supp packets are suppressed.) Address (ipx) IPX network number and node number. Router The IPX router (the LCS60) for the virtual network. Name (ipx) CIPX Max Indicates whether CIPX compression is being used or not (0). If Slot (ipx) used, the number is the maximum number of slots.
  • Page 408 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., morse-e0.23). The port number of the gateway. The port number is shown Port as part of the Local Address field when using the -v option.
  • Page 409 The name of the SLIP session. This name will be the letter s followed by the data switch channel number. Local Address The LCS60 IP address, displayed using the -v option. Dest Address The IP address of the user. Remote User The user ID of the remote user.

  • Page 410: Ports Directory

    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. The number of times the port has been busy when access has been Busy attempted.

  • Page 411: Service Directory

    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.
  • Page 412 Glossary Cfg. The total number of sessions that have been configured for the ser- vice listed (determined from maxsessions). 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.
  • Page 413 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.
  • Page 414 Glossary Inuse 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. G-20 Issue 3...
  • Page 415 Index Index Issue 2...
  • Page 416 Index Issue 2...
  • Page 417 Index 2WAY, G-17 enable, G-6 8-bit, G-16 8-bit character mode enable, G-7 Access remote, 1-12, 8-2 ACCM, G-12 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...
  • Page 418 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.log, 8-47 Atnetstat, E-2 Atping, E-4 Authentication first-time, 1-18 Authorize, A-3 Autobaud, 8-24 Autoboot reset, 9-21 Backup, 8-18, (see Backup/restore) base level, 3-27 from a server, 8-36 to tape, 8-27...
  • Page 419 StarKeeper II NMS, B-1 system console, 2-9 TY, 2-14 Configuration commands, 3-28 StarKeeper II NMS, B-4 Connect time, G-10 Connection console, 2-12 direct to LCS60, 2-12 fiber - error messages, 9-25 fiber - verify, 2-28 fiber cable, 2-19 to 2-20 Index...
  • Page 420 Customer Assistance Center, (see CAC) D8AG cord, 2-16 D8AH connector, 2-13, 2-18 Data switch, G-1 Data switch dialstrings, 4-13, 5-10 Data switch to LCS60 to LAN, 7-13 Datetime, 8-17 DB15 connections, 2-29 Default route, 3-24 Ethernet-connected host, 3-24 example, 8-23...
  • Page 421 6-6 CCL script, F-2 default route, 8-23 define a client, 8-34 dftroute, 8-23 initsetup, 3-6 IPX, F-9 LCS60 dialup.scr, F-9 log level, 8-23 network, 3-1 PC/TCP, F-12 PPP service, F-6 service ports, 7-18 show, 6-6 show ppp, 8-9...
  • Page 422 Index 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...
  • Page 423 Ipxnetstat, E-26 Ipxping, E-27 Keepalive PPP connection, 4-14 Kill, 8-8 LAN, G-2 LAN protocols, 1-6 LAN to LCS60 to data switch, 7-15 LCM, 8-13, G-2 start, 8-14 stop, 8-14 lcm.log, 8-14, 8-47 LCS, G-2 LCS50, B-1 LCS60 Backup and Restore Configura-...
  • Page 424 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...
  • Page 425 Network example, 3-1 management, 1-20 name, G-2, G-4, G-8 security, 1-18 Network Access Controller, (see NAC) Network access password, 8-38 Network address, G-6 Network control panel, F-15 Network number, G-3 Network security group, G-5 configure, 4-3, 5-3 No hangup, G-6 Node, G-2 name, G-2 Nodename, 3-3, 3-6, 8-18...
  • Page 426 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...
  • Page 427 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...
  • Page 428 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...
  • Page 429 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...
  • Page 430 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 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...
  • Page 431 Van Jacobson header compression, 1-12, F-13 Variable files, 8-26 Verbosity, G-19 Verify connections, 9-28 fiber connection, 2-28 Issue 2 LCS60 console connection, 2-27 Version determining, 9-9 Viewhosts, 8-21 Viewnets, 8-21 Virtual terminal, 1-6 Vjslots, G-9 VMEDKHS diagnostics, 9-25 Wait, G-17...
  • Page 432 Index I-16 Issue 2...

Table of Contents