ETS Reference Manual
For the Lantronix ETS Family of Multiport Device Servers
The information in this guide may change without notice. The manufacturer assumes no responsibility for any errors
which may appear in this guide.
UNIX is a registered trademark of The Open Group. Ethern et is a tra demark of XEROX Corpo ration. DE C and LAT
are trademarks of Digital Equipment Corporation. Centronics is a registered tra demark of Centronics Data Compu t er
Corp. PostScript is a trademark of Adobe Systems, Inc. NetWare is a trademark of Novell Corp. AppleTalk, Chooser,
and Macintosh are trademarks of Apple Computer Corp. LaserJet and Bitronics are trademarks of Hewlett Packard.
Windows is a trademark of Microsoft.
Copyright 2000, Lantronix. All rights reserved. No part of the contents of this book may be transmitted or reproduced
in any form or by any means without the written permission of Lantron ix. Printed in the United States of America.
The revision date for this manual is October 23, 2000.
Part Number: 900-065
Rev. A
WARNING
This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of
FCC Rules. These limits are designed to provide reasonable protection against such interference when operating in a
commercial environment. Th is equipment g enerates, us es, and can r adiate radio fr equency energy, and if not installed
and used in accordance with this guide, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause interference in which case the user, at his or her own
expense, will be required to take whatever measures may be required to correct the interference.
Changes or modifications to this device not explicitly approved by Lantronix will void the user’s authority to operate
this device.
Cet appareil doit se soumettre avec la section 15 des statuts et règlemen ts de FCC. Le fonctionn ement est subjecté aux
conditions suiv ant es :
(1) Cet appareil ne doit pas causer une interférence malfaisante.
(2) Cet appareil doît accepter n'importé quelle interférence reìue qui peut causer uneopération indésirable.
i
Contents
1: Introduction............................................................................................................. 1-1
1.1 Product Overview.......................................................................................................................1-1
1.2 Protocol Support.........................................................................................................................1-1
1.3 Terms..........................................................................................................................................1-2
1.4 Server Features ...........................................................................................................................1-2
1.5 How To Use This Manual...........................................................................................................1-5
2: Concepts .................................................................................................................2-1
2.1 Services................................................................................................................... ....................2-1
2.2 Serial Protocols...........................................................................................................................2-1
2.2.1 RS-232........................................................................................................................2-1
2.2.2 RS-423........................................................................................................................2-1
2.2.3 RS-422........................................................................................................................2-2
2.3 Network Protocols......................................................................................................................2-2
2.4 AppleTalk ...................................................................................................................................2-3
2.4.1 Addressing..................................................................................................................2-3
2.4.2 Zones...........................................................................................................................2-3
2.4.3 Name Binding Protocol (NBP)...................................................................................2-4
2.5 LAN Manager.............................................................................................................................2-4
2.5.1 Networking.................................................................................................................2-4
2.6 LAT.............................................................................................................................................2-5
2.7 TCP/IP ........................................................................................................................................2-7
2.7.1 IP Addresses ...............................................................................................................2-7
2.7.2 Telnet..........................................................................................................................2-8
2.7.3 Name Resolution ........................................................................................................2-9
2.7.4 Local Host Table.......................................................................................................2-10
2.7.5 Dynamic Host Control Protocol (DHCP).................................................................2-10
2.7.6 Serial Line Internet Protocol (SLIP).........................................................................2-12
2.7.7 Simple Network Management Protocol (SNMP).....................................................2-13
2.7.8 Reverse Telnet (RTEL).............................................................................................2-13
2.7.9 LPR Support .............................................................................................................2-14
2.7.10 UUCP Support........................................................................................................2-14
2.7.11 TCP/IP Utilities and Commands............................................................................2-14
2.8 LAT and TCP/IP Connectivity.................................................................................................2-15
2.8.1 Connection Methods ................................................................................................. 2-15
2.8.2 Environment Strings.................................................................................................2-15
2.9 NetWare ...................................................................................................................................2-16
2.9.1 Networking...............................................................................................................2-16
2.9.2 Access Lists..............................................................................................................2-16
2.10 Sessions...................................................................................................................................2-17
2.11 PostScript................................................................................................................................2-18
2.12 Modem Features .....................................................................................................................2-18
2.12.1 Remote Configuration ............................................................................................2-19
2.13 Security...................................................................................................................................2-19
Contents
ii
2.13.1 Menu Mode.............................................................................................................2-20
2.13.2 Event Reporting/Logging .......................................................................................2-21
3: Getting Started........................................................................................................ 3-1
3.1 Configuration Methods...............................................................................................................3-1
3.1.1 EZWebCon.................................................................................................................3-1
3.1.2 Using a Web Browser.................................................................................................3-2
3.1.3 Command Line Interface............................................................................................ 3-2
3.2 Entering and Editing Commands................................................................................................3-3
3.3 Restricted Commands.................................................................................................................3-4
3.4 Command Types.........................................................................................................................3-4
3.4.1 Set and Define.............................................................................................................3-4
3.4.2 Show, Monitor, and List.............................................................................................3-4
3.4.3 Clear and Purge...........................................................................................................3-5
3.5 Abbreviating Keywords..............................................................................................................3-5
3.6 Maintenance Issues.....................................................................................................................3-5
3.6.1 Changing the Server Name.........................................................................................3-5
3.6.2 Changing the Server Prompt.......................................................................................3-6
3.6.3 Rebooting the Server..................................................................................................3-6
3.6.4 Restoring Factory Defaults.........................................................................................3-7
3.6.5 Reloading Operational Software.................................................................................3-7
3.7 Editing the Boot Parameters.......................................................................................................3-7
3.8 System Passwords.......................................................................................................................3-8
3.8.1 Privileged Password....................................................................................................3-8
3.8.2 Login Password .......................................................................................................... 3-9
3.8.3 Maintenance Password...............................................................................................3-9
3.9 Configuration Files.....................................................................................................................3-9
3.9.1 Using EZWebCon.....................................................................................................3-10
3.9.2 Without EZWebCon.................................................................................................3-10
4: Server Configuration..............................................................................................4-1
4.1 General Server Parameters..........................................................................................................4-1
4.1.1 Enabling Incoming Connections.................................................................................4-1
4.1.2 Enabling Server-Wide Port Characteristics................................................................4-1
4.1.3 Enabling Announcements...........................................................................................4-2
4.2 AppleTalk Server Parameters.....................................................................................................4-2
4.3 LAT Server Parameters .............................................................................................................. 4-3
4.3.1 Server Identification ................................................................................................... 4-3
4.3.2 Network Timers..........................................................................................................4-3
4.3.3 Node Limit..................................................................................................................4-3
4.4 NetWare Server Parameters........................................................................................................4-4
4.4.1 Routing and Encapsulation.........................................................................................4-4
4.4.2 NetWare Access Lists.................................................................................................4-4
4.5 TCP/IP Server Parameters..........................................................................................................4-5
4.5.1 IP Address...................................................................................................................4-5
4.5.2 Other TCP/IP Parameters ...........................................................................................4-5
4.5.3 Local Host Table.........................................................................................................4-6
4.5.4 Host Limit...................................................................................................................4-6
4.5.5 SLIP............................................................................................................................4-6
4.6 Creating Services......................................................................................................................4-12
Contents
iii
4.6.1 Creating a Simple Service (A Line Printer)..............................................................4-12
4.6.2 Setting Up a Service With Group Codes..................................................................4-13
4.6.3 TCP/Telnet Service Sockets .....................................................................................4-14
4.6.4 Enabling Other Service Options...............................................................................4-14
4.6.5 Setting Up a Modem Service....................................................................................4-15
4.7 Security.....................................................................................................................................4-16
4.7.1 Controlling Incoming Sessions.................................................................................4-16
4.7.2 IP Security Table......................................................................................................4-16
4.7.3 SNMP Security.........................................................................................................4-18
4.8 Event Logging...........................................................................................................................4-18
4.8.1 Configuring Host Types ...........................................................................................4-18
4.8.2 Host Name Formats..................................................................................................4-19
4.8.3 Event Classes............................................................................................................4-19
5: Ports.........................................................................................................................5-1
5.1 Port Commands...........................................................................................................................5-1
5.1.1 Port Access.................................................................................................................5-1
5.1.2 Serial Configuration.................................................................................................... 5-2
5.1.3 Virtual Ports................................................................................................................5-5
5.2 Modems ......................................................................................................................................5-6
5.2.1 Modem Basics ............................................................................................................ 5-6
5.2.2 Modem Wiring............................................................................................................5-7
5.2.3 Baud Rates..................................................................................................................5-8
5.2.4 Modem Configuration ................................................................................................5-9
5.2.5 Modem Result Codes..................................................................................................5-9
5.2.6 Modems with SLIP..................................................................................................... 5-9
5.2.7 Modem Configuration Checklist ..............................................................................5-10
5.2.8 Testing the Modem Configuration............................................................................5-10
5.3 Other Port Characteristics.........................................................................................................5-11
5.3.1 Dialback....................................................................................................................5-11
5.3.2 Dialup .......................................................................................................................5-11
5.3.3 Device Type..............................................................................................................5-12
5.3.4 DTRwait ...................................................................................................................5-12
5.3.5 Group Numbers ........................................................................................................5-12
5.3.6 Interrupts...................................................................................................................5-12
5.3.7 Port Messages...........................................................................................................5-13
5.3.8 Port Names................................................................................................................5-13
5.3.9 Terminal Type ..........................................................................................................5-13
5.4 Security.....................................................................................................................................5-14
5.4.1 Password Restrictions............................................................................................... 5-14
5.4.2 Menu Mode...............................................................................................................5-14
5.4.3 Locking a Port...........................................................................................................5-15
5.4.4 Preventing Access Until DSR Is Asserted................................................................5-15
5.4.5 Automatic Logouts...................................................................................................5-16
5.4.6 Dialback Security......................................................................................................5-16
6: Using the ETS .........................................................................................................6-1
6.1 Logging In and Out.....................................................................................................................6-1
6.1.1 Logging In ..................................................................................................................6-1
6.1.2 Logging Out................................................................................................................6-1
Contents
iv
6.2 Configuring Your Port................................................................................................................6-2
6.2.1 Unsecure Port Commands..........................................................................................6-2
6.3 Connecting to Services...............................................................................................................6-3
6.3.1 Connecting to LAT Services ......................................................................................6-3
6.3.2 Connecting to Telnet Hosts ........................................................................................6-4
6.3.3 Connecting to Local Ports ..........................................................................................6-5
6.3.4 Connecting to Remote Hosts Via Rlogin.................................................................... 6-5
6.3.5 Connecting to the Server from UNIX Hosts...............................................................6-6
6.4 Default Services ..........................................................................................................................6-6
6.5 Session Management..................................................................................................................6-7
6.5.1 Break...........................................................................................................................6-7
6.5.2 Backwards and Forwards............................................................................................6-7
6.5.3 Backward and Forward Switch Keys .........................................................................6-7
6.5.4 Disconnect and Resume..............................................................................................6-8
6.6 Local Server Commands.............................................................................................................6-8
6.6.1 Broadcast ....................................................................................................................6-8
6.6.2 Lock............................................................................................................................6-9
6.6.3 Logout.........................................................................................................................6-9
6.6.4 Test Port......................................................................................................................6-9
6.7 Status Displays............................................................................................................................6-9
7: TCP/IP Host Setup..................................................................................................7-1
7.1 Selecting A Printing Method......................................................................................................7-1
7.2 LPR Printing...............................................................................................................................7-2
7.2.1 LPR Basics..................................................................................................................7-3
7.2.2 LPR on Windows NT 3.5.1 (and later).......................................................................7-4
7.2.3 LPR on AIX Hosts......................................................................................................7-6
7.2.4 LPR on HP Hosts........................................................................................................7-8
7.2.5 LPR on SCO UNIX Hosts..........................................................................................7-8
7.2.6 LPR on Sun Solaris Hosts...........................................................................................7-9
7.3 Reverse Telnet (RTEL).............................................................................................................7-10
7.3.1 Components of RTEL...............................................................................................7-10
7.3.2 Installing Reverse Telnet Software...........................................................................7-10
7.3.3 Queueing with the RTEL Software..........................................................................7-11
7.3.4 Setting up the RTEL Backend Filter ........................................................................7-12
7.3.5 Setting up the RTEL Named Pipe Daemon..............................................................7-14
7.3.6 Creating a BSD Print Queue Using RTELPD..........................................................7-17
7.3.7 Creating a SYSV Print Queue Using RTELPD........................................................7-17
7.3.8 RTEL Troubleshooting............................................................................................. 7-18
7.4 TCP Socket Connections..........................................................................................................7-18
7.5 PostScript Configuration...........................................................................................................7-19
8: NetWare Host Setup............................................................................................... 8-1
8.1 Access Lists ................................................................................................................................8-1
8.2 Licensing NDS............................................................................................................................8-1
8.3 Printing .......................................................................................................................................8-2
8.3.1 Creating NDS Print Queues with PCONSOLE..........................................................8-3
8.3.2 Creating Print Queues with NetWare Administrator..................................................8-4
8.3.3 Creating Bindery Print Queues with QINST..............................................................8-6
8.3.4 Installing a Print Queue Using PCONSOLE..............................................................8-7
Contents
v
8.3.5 Configuring Rprinter ..................................................................................................8-9
8.4 PCL...........................................................................................................................................8-15
8.5 PostScript..................................................................................................................................8-15
8.6 Troubleshooting........................................................................................................................8-15
8.6.1 QINST Print Queue Troubleshooting.......................................................................8-15
8.6.2 NDS Print Queue Troubleshooting...........................................................................8-16
8.6.3 NetWare Host Troubleshooting................................................................................8-18
9: LAT Host Setup.......................................................................................................9-1
9.1 Printing from LAT......................................................................................................................9-1
9.1.1 Printing to an Application Port...................................................................................9-1
9.1.2 Printing to a Service....................................................................................................9-2
9.1.3 Printing PostScript......................................................................................................9-3
9.1.4 Printing Using DCPS Software ..................................................................................9-4
9.1.5 Translating RLAT Jobs to RTEL ...............................................................................9-4
9.2 The ets$configd Download Server .............................................................................................9-5
9.3 Troubleshooting..........................................................................................................................9-6
9.3.1 VMS Printer Troubleshooting ....................................................................................9-6
9.3.2 VMS Host Troubleshooting........................................................................................9-8
10: AppleTalk Host Setup......................... ..... ..... .... ................................. ..... ............ 10-1
10.1 Configuration..........................................................................................................................10-1
10.1.1 Bitronics Interface ..................................................................................................10-1
10.1.2 Macintosh Service Configuration...........................................................................10-2
10.2 Printing from a Macintosh......................................................................................................10-2
10.2.1 Using AppleTalk on UNIX or VMS.......................................................................10-2
10.2.2 Using LaserPrep...................................................................................................... 10-2
10.2.3 Printing Bitmap Graphics.......................................................................................10-2
10.3 Troubleshooting Macintosh Printing......................................................................................10-3
10.3.1 General Troubleshooting........................................................................................ 10-3
10.3.2 Host Troubleshooting.............................................................................................10-5
11: LAN Manager Host Setup...................................................................................11-1
11.1 Printing Methods.....................................................................................................................11-1
11.1.1 DLC .......................................................................................................................11-1
11.1.2 NetBIOS .................................................................................................................11-3
11.2 Windows NT Troubleshooting...............................................................................................11-4
12: Command Reference..........................................................................................12-1
12.1 Overview.................................................................................................................................12-1
12.2 Command Line Interface........................................................................................................12-1
12.2.1 Command Completion............................................................................................12-1
12.2.2 Command Line Editing...........................................................................................12-2
12.3 Attach Port..............................................................................................................................12-2
12.4 Backwards...............................................................................................................................12-4
12.5 Bg............................................................................................................................................12-4
12.6 Broadcast ................................................................................................................................12-4
12.7 Clear/Purge Commands..........................................................................................................12-5
12.7.1 Clear/Purge Dialback..............................................................................................12-5
12.7.2 Clear/Purge Hosts...................................................................................................12-5
Contents
vi
12.7.3 Clear/Purge IPsecurity............................................................................................12-6
12.7.4 Clear/Purge Menu................................................................................................... 12-6
12.7.5 Clear/Purge Protocol NetWare Access...................................................................12-7
12.7.6 Clear/Purge Service................................................................................................12-7
12.7.7 Clear/Purge SLIP ...................................................................................................12-8
12.7.8 Clear/Purge SNMP .................................................................................................12-8
12.7.9 Clear/Purge Telnet Hosts........................................................................................ 12-8
12.8 Close .......................................................................................................................................12-9
12.9 Cls...........................................................................................................................................12-9
12.10 Connect.................................................................................................................................12-9
12.11 Crash 451............................................................................................................................12-11
12.12 Define..................................................................................................................................12-11
12.13 Disconnect ..........................................................................................................................12-12
12.14 Fg........................................................................................................................................12-12
12.15 Finger..................................................................................................................................12-12
12.16 Forwards .............................................................................................................................12-13
12.17 Help.....................................................................................................................................12-13
12.18 Initialize..............................................................................................................................12-14
12.19 Jobs .....................................................................................................................................12-15
12.20 Kill......................................................................................................................................12-15
12.21 LAT.....................................................................................................................................12-15
12.22 List......................................................................................................................................12-15
12.23 Lock....................................................................................................................................12-16
12.24 Logout.................................................................................................................................12-16
12.25 Man.....................................................................................................................................12-16
12.26 Mode...................................................................................................................................12-17
12.27 Monitor ...............................................................................................................................12-17
12.28 Netstat.................................................................................................................................12-17
12.29 Open ....................................................................................................................................12-18
12.30 Ping.....................................................................................................................................12-18
12.31 Purge...................................................................................................................................12-18
12.31.1 Purge SLIP..........................................................................................................12-18
12.32 Remove Queue....................................................................................................................12-19
12.33 Resolve................................................................................................................................12-20
12.34 Resume................................................................................................................................12-20
12.35 Rlogin..................................................................................................................................12-20
12.36 Save.....................................................................................................................................12-21
12.37 Send ....................................................................................................................................12-22
12.38 Set/Define Dialback ............................................................................................................12-23
12.39 Set/Define IPsecurity..........................................................................................................12-23
12.40 Set/Define Logging.............................................................................................................12-25
12.41 Set/Define Menu.................................................................................................................12-26
12.42 Set Noprivileged................................................................................................................. 12-26
12.43 Set/Define Port Commands ................................................................................................12-27
12.43.1 Define Port Access .............................................................................................12-27
12.43.2 Set/Define Port Authorized Groups....................................................................12-28
12.43.3 Set/Define Port Autobaud...................................................................................12-28
12.43.4 Set/Define Port Autoconnect..............................................................................12-29
12.43.5 Set/Define Port Autoprompt...............................................................................12-30
12.43.6 Set/Define Port Autostart....................................................................................12-30
Contents
vii
12.43.7 Set/Define Port Backward..................................................................................12-31
12.43.8 Set/Define Port Break.........................................................................................12-31
12.43.9 Set/Define Port Broadcast...................................................................................12-32
12.43.10 Set/Define Port Character Size.........................................................................12-33
12.43.11 Set/Define Port Command Completion............................................................12-33
12.43.12 Set/Define Port Dedicated ................................................................................12-34
12.43.13 Set/Define Port Dialback..................................................................................12-36
12.43.14 Set/Define Port Dialup......................................................................................12-37
12.43.15 Set/Define Port DSRlogout...............................................................................12-37
12.43.16 Set/Define Port DTRwait..................................................................................12-38
12.43.17 Set/Define Port Flow Control...........................................................................12-39
12.43.18 Set/Define Port Forward ...................................................................................12-40
12.43.19 Set Port Groups................................................................................................. 12-40
12.43.20 Set/Define Port Inactivity Logout.....................................................................12-41
12.43.21 Set/Define Port Local .......................................................................................12-41
12.43.22 Set/Define Port Loss Notification.....................................................................12-42
12.43.23 Set/Define Port Menu.......................................................................................12-43
12.43.24 Define Port Modem Control.............................................................................12-43
12.43.25 Set/Define Port Name.......................................................................................12-44
12.43.26 Set/Define Port Parity.......................................................................................12-44
12.43.27 Set/Define Port Passflow..................................................................................12-45
12.43.28 Set/Define Port Password .................................................................................12-45
12.43.29 Set/Define Port Preferred..................................................................................12-46
12.43.30 Set/Define Port Printer......................................................................................12-48
12.43.31 Set/Define Port Queue......................................................................................12-48
12.43.32 Set/Define Port Remote Configure...................................................................12-49
12.43.33 Set/Define Port Security ...................................................................................12-49
12.43.34 Set/Define Port Session Limit ..........................................................................12-50
12.43.35 Set/Define Port Signal Check...........................................................................12-50
12.43.36 Set/Define Port SLIP........................................................................................12-51
12.43.37 Set/Define Port Speed.......................................................................................12-51
12.43.38 Set/Define Port Stop......................................................................................... 12-52
12.43.39 Set/Define Port Telnet Pad ...............................................................................12-53
12.43.40 Set/Define Port Termtype.................................................................................12-53
12.43.41 Set/Define Port Type........................................................................................12-54
12.43.42 Set/Define Port Username ................................................................................12-54
12.43.43 Set/Define Port Verification .............................................................................12-55
12.44 Set Privileged/Noprivileged................................................................................................12-56
12.45 Set/Define Protocols Commands........................................................................................12-56
12.45.1 Define Protocols AppleTalk ............................................................................... 12-56
12.45.2 Define Protocols IP.............................................................................................12-57
12.45.3 Define Protocols LAN Manager.........................................................................12-58
12.45.4 Set/Define Protocols LAT..................................................................................12-58
12.45.5 Set/Define Protocols NetWare ............................................................................12-59
12.46 Set/Define Server Commands.............................................................................................12-62
12.46.1 Set/Define Server Announcements.....................................................................12-62
12.46.2 Set/Define Server Bootgateway..........................................................................12-63
12.46.3 Set/Define Server BOOTP..................................................................................12-63
12.46.4 Set/Define Server Broadcast...............................................................................12-63
12.46.5 Set/Define Server Buffering...............................................................................12-64
Contents
viii
12.46.6 Set/Define Server Circuit Timer.........................................................................12-64
12.46.7 Set/Define Server Console..................................................................................12-65
12.46.8 Set/Define Server Domain..................................................................................12-65
12.46.9 Set/Define Server DHCP....................................................................................12-65
12.46.10 Set/Define Server Gateway...............................................................................12-66
12.46.11 Set/Define Server Groups ................................................................................12-66
12.46.12 Set/Define Server Host Limit ...........................................................................12-67
12.46.13 Set/Define Server Identification.......................................................................12-67
12.46.14 Set/Define Server Inactivity Timer...................................................................12-68
12.46.15 Set/Define Server Incoming .............................................................................12-68
12.46.16 Set/Define Server IPaddress .............................................................................12-69
12.46.17 Set/Define Server Keepalive Timer..................................................................12-70
12.46.18 Set/Define Server Loadhost..............................................................................12-70
12.46.19 Set/Define Server Lock.....................................................................................12-71
12.46.20 Set/Define Server Login Password...................................................................12-71
12.46.21 Set/Define Server Maintenance Password........................................................12-72
12.46.22 Set/Define Server Multicast Timer...................................................................12-72
12.46.23 Set/Define Server Name ...................................................................................12-73
12.46.24 Set/Define Server Nameserver .........................................................................12-73
12.46.25 Set/Define Server NetWare Loadhost ..............................................................12-74
12.46.26 Set/Define Server NetWare Printserver............................................................12-74
12.46.27 Set Server NetWare Reset ................................................................................12-75
12.46.28 Set/Define Server Node Limit ..........................................................................12-75
12.46.29 Set/Define Server Password Limit....................................................................12-75
12.46.30 Set/Define Server Privileged Password............................................................12-76
12.46.31 Set/Define Server Prompt.................................................................................12-76
12.46.32 Set/Define Server Queue Limit ........................................................................12-77
12.46.33 Set/Define Server RARP ..................................................................................12-78
12.46.34 Set/Define Server Reload .................................................................................12-78
12.46.35 Set/Define Server Retransmit Limit .................................................................12-78
12.46.36 Set/Define Server Rlogin..................................................................................12-79
12.46.37 Set/Define Server Secondary............................................................................12-79
12.46.38 Set/Define Server Serial Delay.........................................................................12-79
12.46.39 Set/Define Server Service Groups....................................................................12-80
12.46.40 Set/Define Server Session Limit.......................................................................12-80
12.46.41 Define Server Silentboot...................................................................................12-81
12.46.42 Set/Define Server SLIP Password.................................................................... 12-81
12.46.43 Set/Define Server Software ..............................................................................12-82
12.46.44 Set/Define Server Startupfile............................................................................12-82
12.46.45 Set/Define Server Subnet Mask........................................................................12-83
12.46.46 Set/Define Server UUCP..................................................................................12-84
12.47 Set/Define Service Commands...........................................................................................12-84
12.47.1 Set/Define Service..............................................................................................12-84
12.47.2 Set/Define Service AppleTalk............................................................................12-85
12.47.3 Set/Define Service Banner..................................................................................12-85
12.47.4 Set/Define Service Binary..................................................................................12-86
12.47.5 Set/Define Service DLC.....................................................................................12-86
12.47.6 Set/Define Service EOJ ......................................................................................12-86
12.47.7 Set/Define Service Formfeed..............................................................................12-87
12.47.8 Set/Define Service Identification........................................................................12-87
Contents
ix
12.47.9 Set/Define Service LAN Manager...................................................................... 12-88
12.47.10 Set/Define Service LAT ...................................................................................12-88
12.47.11 Set/Define Service NetWare.............................................................................12-88
12.47.12 Set/Define Service Password............................................................................12-89
12.47.13 Set/Define Service Ports...................................................................................12-89
12.47.14 Set/Define Service PostScript ...........................................................................12-90
12.47.15 Set/Define Service PSConvert..........................................................................12-90
12.47.16 Set/Define Service RTEL.................................................................................12-90
12.47.17 Set/Define Service SOJ.....................................................................................12-91
12.47.18 Set/Define Service TCPport .............................................................................12-91
12.47.19 Set/Define Service Telnetport...........................................................................12-92
12.47.20 Set/Define Service Virtual................................................................................12-92
12.48 Set Session Commands.......................................................................................................12-93
12.48.1 Set Session Delete...............................................................................................12-93
12.48.2 Set Session Echo.................................................................................................12-93
12.48.3 Set Session Interactive........................................................................................12-94
12.48.4 Set Session Newline ...........................................................................................12-94
12.48.5 Set Session Passall..............................................................................................12-95
12.48.6 Set Session Passthru ...........................................................................................12-95
12.49 Set/Define SLIP..................................................................................................................12-95
12.49.1 Set SLIP..............................................................................................................12-96
12.49.2 Define SLIP........................................................................................................12-97
12.50 Set/Define SNMP ...............................................................................................................12-98
12.51 Set/Define Telnet Hosts......................................................................................................12-99
12.52 Show/Monitor/List Commands.........................................................................................12-100
12.52.1 Show/Monitor/List Dialback ............................................................................12-100
12.52.2 Show/Monitor/List Hosts..................................................................................12-100
12.52.3 Show/Monitor/List IPsecurity ..........................................................................12-100
12.52.4 Show/Monitor/List Logging.............................................................................12-101
12.52.5 Show/Monitor/List Menu.................................................................................12-101
12.52.6 Show/Monitor Nodes........................................................................................12-101
12.52.7 Show/Monitor/List Ports..................................................................................12-102
12.52.8 Show/Monitor/List Protocols............................................................................12-104
12.52.9 Show/Monitor Queue........................................................................................12-107
12.52.10 Show/Monitor/List Server..............................................................................12-108
12.52.11 Show/Monitor/List Services...........................................................................12-111
12.52.12 Show/Monitor Sessions..................................................................................12-111
12.52.13 Show/List SLIP...............................................................................................12-112
12.52.14 Show/Monitor/List SNMP..............................................................................12-112
12.52.15 Show/Monitor/List [Telnet] Hosts..................................................................12-113
12.52.16 Show/Monitor Users.......................................................................................12-113
12.52.17 Show Version..................................................................................................12-114
12.53 Source ...............................................................................................................................12-114
12.54 Stty....................................................................................................................................12-115
12.55 Su......................................................................................................................................12-115
12.56 Telnet................................................................................................................................12-115
12.57 Test Loop..........................................................................................................................12-116
12.58 Test Port............................................................................................................................ 12-116
12.59 Test Service.......................................................................................................................12-117
12.60 Unattach Port ....................................................................................................................12-118
Contents
x
12.61 Unlock Port.......................................................................................................................12-119
12.62 Who...................................................................................................................................12-119
12.63 Zero Counters ...................................................................................................................12-119
A: Contact Information...............................................................................................A-1
A.1 Problem Report Procedure........................................................................................................A-1
A.2 Full Contact Information...........................................................................................................A-1
B: Troubleshooting.....................................................................................................B-1
B.1 Power-up Troubleshooting........................................................................................................B-1
B.2 DHCP Troubleshooting.............................................................................................................B-1
B.3 BOOTP Troubleshooting..........................................................................................................B-2
B.4 RARP Troubleshooting.............................................................................................................B-2
B.5 Modem Configuration Checklist...............................................................................................B-2
C: Updating Software .................................................................................................C-1
C.1 Obtaining Software ...................................................................................................................C-1
C.2 Reloading Software ...................................................................................................................C-2
C.3 Troubleshooting Flash ROM Updates......................................................................................C-4
Glossary
Index
1-1
1: Introduction
1.1 Product Overview
The Lantronix ETSs (ETS4P, ETS8P, ETS16P, ETS16PR, ETS32PR, and ETS422PR) are Multiport
Device Servers that provide shared network access to terminals, devices, console ports, and printers for a
variety of network protocols and operating systems. The ETS supports the TCP/IP, IPX (NetWare), Local
Area Transport (LAT), AppleTalk (EtherTalk), and Microsoft LAN Manager protocols.
Lantronix server s store thei r executabl e software i n Flash (rewri table) ROM, mea ning that they do not hav e
to download software from a host each time they boot. Software must only be downloaded when a new
software version becomes available. See Appendix D for more information.
Note: In this manual, all servers will be referred to as “the ETS” unless a distinction
needs to be made between models.
1.2 Protocol Support
The ETS supports five industry-standard network protocols:
TCP/IP
TCP/IP is a widely-used protocol that can be run on networks with Macintoshes, PCs, and Unix
workstations. Server support includes Telnet, Rlogin, DNS, and the LPR and RTEL printing systems.
NetWare (IPX/SPX )
NetWare allows devices attached to the ETS to act as networked printers. The ETS s upports all NetWare frame types: Ethernet v2, Native Mode (802.3), 802.2, and 802.2 SNAP. In addition, it supports both Bindery mode and NetWare Directory Services (NDS).
Local Area Transport (LAT)
LAT is a protocol developed by Digital Equip ment Corporati on for local netwo rk terminal connec tions and is supported on almost all Digital operating systems. It provides both logins to remote
hosts and host-initiated print spooling.
AppleTalk
AppleTalk allows networked Apple Macintosh computers to see devices attached to the ETS and
access them as they would any networked printer.
LAN Manager
The ETS allows devices on LAN Manager ne tworks to access networke d printers. Systems runni ng
Windows NT can access the devices using the Digital Network Port for Windows NT or the NetBIOS protocol.
Terms Introduction
1-2
1.3 Terms
In this manual, the following terms are used to describe parts of a network. See the Glossary for more
detailed explanations of these terms.
host A computer, sometimes referred to as a CPU, attached to the network. The
term host
node Any intelligent device directly connected to the Ethernet network and having
its own Ethernet addre sses, such a s a host, an Ethernet p rinter, or a t erminal o r
print server. Devices connected to the ETS are not nodes.
service A resource that can be acc essed local ly or via the net work. For example, a host
is a service to which terminals can connect. The ETS can offer its attached
printers and modems to the network as services.
session A logical connectio n to a ser vi ce. A t ypi cal session is a terminal connect ed to
a host through the terminal server.
Local mode The ETS user interface, which is used to issue configuration and session
management commands and establish sessions with services.
1.4 Server Features
AppleTalk Support
The ETS provides Ethernet a cce ss to attached laser pri nte rs ; ETS p ri nt s er vic es a ppe ar i n t he Mac intosh Chooser window li ke any other pr inter on the ne twork. Bi-directi onal communication (either
a serial or IEEE 1284 parallel interface) is required.
LAN Manager Support
The ETS can be configured to appear as a print node to other LAN Manag er nodes. Suppo rted systems include Windows NT and Windows 95.
LAT and Digital Compatibility
The ETS supports LAT and TSM/NCP, making it fully compatible with most Digital Equipment
Corporation operating environments.
NetWare Support
The ETS is used primar il y f or pr int serving. The ETS c an als o be c onf igured and logged int o fr om
a NetWare fileserver, and can function as a print node for other NetWare fileservers.
TCP/IP and UNIX Compatibility
Almost all UNIX systems support Telnet, an established industry standard. Telnet can be used for
interactive se ssions, or fo r logging int o the server to issu e configurat ion commands. UNIX system s
generally implement Rlogin as well, unless security considerations dictate that it be disabled at a
particular site. Support for domain name servers, network gateways, SLIP access, and a local domain name are all provided. In addition, IP security can be enabled to control access to the server.
Introduction Server Features
1-3
Connectivity
The Server connects ter mina ls dir ectl y to the net work , which conse rv es physi cal port s on th e host,
allows the terminal to acc ess more than one host, and simplifies terminal cabling .
Multiple Session Support
Users can open multiple out goi ng LAT, Rlo gin , and Telnet sessions, and can eas il y swit ch among
active sessions. Up to eight s essions are supported p er connected terminal. Each session can be connected to any host and can use any supported protocol.
Load Balancing
If a LAT service is provided by more than one node, the server chooses the least busy service for
the connection. This helps balance CPU usage and provides better user response times.
Small Size
The small, attract ive case is des igned to fit int o any office env ironment. Becaus e there is no int ernal
fan, the ETS operates silently.
Ease of Use
The server’s Local mode su pports command li ne editing, command line recal l, and command completion. An extensive Help facility is also provided.
Easy Configuration
The EZWebCon utility (p rovide d on CD-ROM) allows users to c onfigu re th e ET S from a any h ost
machine running the Java Vir tual Machine (JVM). It also al lows remote host logins into the Server,
which are similar to Telnet and LAT logins.
Note: You must be Supervisor to run the EZWebCon utility on a NetWare client.
Dialback ports, which allow manag ers to improve secur ity for dial-in mode m users. A menu mode,
which enables managers to tailor which individual commands users are allowed to use.
Remote Configu ration
The ETS can be logged into and remotely configured using one of the following methods:
❍ Digital’s NCP and TSM facilities
❍ The Telnet c onsole port, similar to the N CP remote console
❍ The network login feature, which allows managers to log into the ETS via TCP/IP, LAT, and
NetWare.
❍ EZWebCon, a configuration applic ation that ru ns on any host computer running the Java Virt ual
Machine (JVM).
Server Features Introduction
1-4
Command Line Interface
A simple but powerful command interface is provided for both users and system managers. The
ETS operating code is downloaded automatically at power-up, making software upgrades as easy
as copying a file.
The ETS stores its ope rati ng sof tware permane ntly on- board, so i t doe s not need to downloa d code
unless new versions bec ome available. Servers ca n also be configured to requ est a downloaded configuration file at boot time.
The Command Reference chapter o f this r eference manual desc ribes the commands a vailable in the
ETS’s local command line mode. These commands control port and server configuration, session
management, and other tasks. Ports can be se t to secur e to allow onl y a subset of the commands. In
addition, a menu mode i s prov ided so that users will n ot have to le arn th e Se rver c ommand set , but
can instead choose from a table of commands.
Note: See the Command Reference for more information on the command line,
command recall, and command completion features.
Context-Sensitive Help
Context-sensiti ve on-line help is ava ilable at any poin t. You may type “HELP” b y itself for over all
help, “HELP command” for help on a specific command, or a partial command li ne f oll owed by a
question mark for help on what is appropriate at that particular point.
Note: See Help on page 12-13 for more information.
Host-Initiated Connections
The ETS may be configured to provide its attached devices as services to other nodes, allowing
hosts to share pr int er s and modems. AppleTalk, LAN Mana ger , LAT, Net Wa re, and TCP/IP hosts
can queue jobs to ETS services simultaneously. The optional RTEL host software provides both
printer backend access and a named pipe interface to the ETS from TCP/IP hosts.
IPX Redirector
The IPX Redirector i s an a pplica tion that allows PCs on an IPX net work to share mode ms conne cted to the server using Micros oft Windows or DOS communi cations sof tware that sup ports the INT
14 or NASI redirector interface. With the help of the Redirector, PC users can dial out, connect to
a modem available as an ETS service, and connect to a remote host.
Security
The ETS includes several configurable security features. They include:
❍ Group codes, which allow the ETS to act as a filter to limit the user’s knowledge of, and access
to, specific services.
❍ Automatic session logouts when a port is disconnected or a device is turned off.
❍ Password protection for privileges, ports, services, maintenance commands, and the remote
console.
❍ The ability to secure certain ports, which prevents them from issuing privileged commands and
giving them a limited view of the network.
❍ The ability of an individual user to lock his or her port, as well as specify the password that will
unlock it.
Introduction How To Use This Manual
1-5
❍ An IP security table, which allows the server manager to restrict incoming and outgoing TCP/IP
connections to certain ports and hosts. This allows managers to restrict Server access to a
particular local network segment or host. It also allows restrictions for SLIP access to the
network.
DHCP Support
The Server can obtain an IP address from a DHCP server at boot time.
SNMP Support
The ETS supports the Simple Network Management Protocol (SNMP), which can be used by network managers to monitor net work load and e rror condi tions. No enter prise-s pecific MIBs ar e supplied by Lantronix.
Diagnostics
Power-up and interactive diagnostics help system managers troubleshoot network and serial line
problems.
1.5 How To Use This Manual
The rest of the chapters in this manual describe the features and commands of the ETS. Information is
broken down as follows:
◆ Chapters 2 through 6 cover general functionality:
◆ Chapter 2, Concepts, explains the basic ideas behind ETS operation.
◆ Chapter 3, Getting Started, explains available configuration methods, as well as steps needed for
reconfiguration and maintenance operation.
◆ Chapter 4, Server Configuration, explains server-wide configuration options, including protocol-
specific configuration and security issues.
◆ Chapter 5, Ports, details the port- specific confi gurat ion opt io ns, inc luding seri al por t par ameters and
modem-related commands.
◆ Chapter 6, Using the ETS, introduces end-users to the Server. It also explains how to use the Server
interactively.
◆ Chapters 7 through 11 cover protocol-specific issues and troubleshooting:
❍ Chapter 7 covers TCP/IP Host Setup.
❍ Chapter 8 covers NetWare Host Setup.
❍ Chapter 9 covers LAT Host Setup for VMS.
❍ Chapter 10 covers AppleTalk Host Setup.
❍ Chapter 11 covers LAN Manager Host Setup.
How To Use This Manual Introduction
1-6
◆ Chapter 12, Command Reference, lists the ETS command set in detail, including syntax, options,
errors, examples, and where to find related information.
◆ Appendices provide supplementary information, including Technical Support contact information,
troubleshooting tips, and pinout information.
Note: Installation and cabling are covered in your Server’s Installation Guide.
2-1
2: Concepts
The ETS provides two major functions: outgoing sessions, which are basically interactive connections to
other nodes, and incoming connections to services, such as printer and modem support.
2.1 Services
Services are the basic method of co nnecting to t he ETS from any hos t or another server. In ge neral, a service
is required on th e ETS before any job or connect ion queuei ng will t ake pla ce. See the Ser ver Config uration
chapter for details on creating and using services.
2.2 Serial Protocols
The ETS models support RS-423 and RS-422 se rial protocols. I n addition, the y are compatible wi th RS-232
devices.
2.2.1 RS-232
The RS-232 line interface standard is a single-ended peer-to-peer interface. Today’s personal computers
typically have at least one RS-232 serial port. It is the most common serial protocol used today.
RS-232 is used for connecting devices across short distances, at speeds up to 230.4 kb/s. Faster speeds
require shorter cabli ng to ensure error-fr ee communicati ons. The maximum cable lengt h at a given speed is
determined by many factors, i ncludi ng the immedi ate el ectrica l env ironment and t he quali ty of cab le used,
but is usually less than 10 meters at high speeds.
Lantronix MSS models have RS-232 ports. RS-232 devices are interoperable with RS-423 devices.
2.2.2 RS-423
All of the ETS models support the RS-423 line interface standard. RS-423 devices are interoperable with
RS-232 devices. That is, RS-232 ports can receive data reliably from RS-423 ports and vice-versa.
The main difference between RS-423 and RS-232 is that RS-423 employs lower voltage signaling and
differential receivers. RS-423 still uses single-ended transmitters for compatibility with RS-232 receivers.
RS-423 is generally rated at higher speeds over longer cabling runs than RS-232. Maximum data rates of
230.4 kb/s are possible on ETS-PR models, and 115.2 kb/s is the maximum on ETS-P models.
Network Protocols Concepts
2-2
2.2.3 RS-422
The ETS422PR supports RS -422 on all of it s p orts. RS-422 i s dif ferent fr om RS-232 or RS-42 3 in t hat i t is
a differential or balanced line interface standard. It is designed for longer cabling distances (approaching
4,000 feet) in noisie r electrical environments , and it can be used in mult i-drop networks with one drive r and
up to ten receivers.
The maximum speed of the RS-42 2 port s on t he E TS422PR is 230.4 k b/s, as with RS-4 23, but this rate can
be sustained over longer cable runs than possible on RS-232 or RS-423 connections.
RS-422 ports are interoperable with RS-423 ports, but not with RS-232. When connecting an RS-422 port
to an RS-423 port, you must be sure that your connector cable is properly configured. Please consult the
connector pinout drawings in Appendix C before making a connector cable.
2.3 Network Protocols
A network protocol describes the data contained in Ethernet packets. The network protocols provided by
the ETS are completely separa te , other than the use of the Ethernet data lay er. The following figure shows
the protocol stacks supported by the ETS.
Figure 2-1: Supported Network Protocols
There are three different Ethernet frame formats, one of which is subdivided:
◆ What is typically called Ethernet is technically referred to as Ethernet v2. This is the default frame
type for most TCP/IP, LAT, and MOP/NCP protocol stacks. It can also be used for NetWare.
◆ The IEEE 802.2 frame format comes with either a regular or a SNAP SAP (Service Access Point).
AppleTalk uses the SNAP format by default. Both types can be used by NetWare.
◆ NetWare 2.x and 3.x stations, by def ault, do not use any of these fr ame types. They use a native mode
format that is being phased out.
AppleTalk LAN Manager LAT NetWare TCP/IP
Printer
Access Protocol
SMB LAT NCP Telnet/ Rlo-
gin/ RTEL/
lpd
ATP NetBEUI SPX TCP
DDP IPX IP
Ethernet/IEEE 802.3 Data Layer
Concepts AppleTalk
2-3
2.4 AppleTalk
AppleTalk is a protocol used primarily by Apple Macintoshes to access network resources such as file
servers and printers. AppleTalk is also available for UNIX, NetWare, and other operating systems. The
AppleTalk protocol c an be run over Etherne t (EtherTalk), Token Ring (TokenTa lk), or LocalTal k, which is
a medium speed network type built into every Macintosh. These various network media can be connected
with AppleTalk routers to allow all nodes to communicate with one another. The AppleTalk protocol
supports features such as file sharing and security in addition to printing.
The ETS supports only the Printe r Access Protocol (PAP) and th erefo re canno t creat e outgoi ng AppleTa lk
sessions—only incoming pri nt requests are accepted. Any services on the ETS with AppleTalk enabled will
show up as LaserWriters in Macintosh Chooser windows and are associated with an available zone
(explained in Section 2. 4.2) . User s who s el ect a ETS service as their LaserWrit er wil l ha ve th ei r pr int jobs
forwarded to the ETS for printing, or for queueing if the print port on the ETS is in use or otherwise
unavailable.
AppleTalk printing is different from printing in other protocols. There are standard Macintosh drivers
provided for specific Apple printer types, such as LaserWriters and ImageWriters, but there are no plain
ASCII line print ers by default. ASCII jobs are converted into PostScript (for la se r p rinters) or bitmaps (for
ImageWriters) when printed. Only laser printer devices are supported by the ETS under AppleTalk.
The Macintosh client will need to query the printer about status, so only laser printers that reply to these
interactive PostScript requests can be used. The ETS parallel ports support Bitronics mode, provided the
attached laser printer also implements it.
2.4.1 Addressing
AppleTalk provides for dynamic node addressing, a llowing a node to choose its ad dress at boot time. It will
send network packets to the other nodes to avoid choosing a node ID already in use. A node can also
discover its network number by listening for AppleTalk router broadcasts; if none are heard, a default
network number is chos en. The ETS will save zon e/net work/nod e ID t ripl ets in pe rman ent memor y, which
reduces traffic at rebo ot time, alt hough the ETS Appl eTalk addre ss may change ac ross boots in response to
any network changes.
Network numbers are conf igure d in the r outer s, so the o nly Appl eTalk confi gurat ion s uppo rted by the ETS
is the specification of a zone name other than the default. D ue to the generally non-configu rable natur e of
AppleTalk, most AppleTa lk devices are t ruly “plug-a nd-play”— they c an be powered up and used right out
of the box.
2.4.2 Zones
Zones are arbitra ry groupin gs of AppleTal k nodes used to orga nize reso urces int o groups that are e asier fo r
users to understand. For example, a college may organize zones around departments, like Math
Department and Physics Department. Zones allow users to sift through large numbers of nodes by
choosing those groups they are fami liar with regar dless of the o rganization of t he network. In ge neral, zones
need not have a correlation to physical or network location, thus any node can declare itself a member of
any single zone.
LAN Manager Concepts
2-4
Zones, like nodes, origin ate from and are confi gured on AppleTal k routers. One zone on each network wil l
be chosen by the router as the defaul t zone. If ther e are no Apple Talk rou ters on the network, th ere wil l be
only one zone (the default zone) of which all nodes are members. If no zone name has been previously
defined on the ETS, or if the de fined zone is no longe r valid, the ETS wil l join the defa ult zone and no other
configuration is needed. The ETS can be placed in a different zone with the Define Protocols AppleTalk
command. Each time the ETS is booted, or when its zone is changed, it will verify the zone name with a
router.
2.4.3 Name Binding Protocol (NBP)
NBP is used by AppleTalk to advertise resources, such as printers and fileservers, to the network. Any
resource that othe r user s can access will have NBP i nformat ion t hat must be co mmunic ated t o othe r nodes .
The items in the Chooser window reflect the NBP resources on the network.
NBP and the Chooser organize re sources by t hree level s: name, type , and zone. Names ar e arbitrary strings
assigned by users , such as Kathy or MyPrinter. T ypes are generi c classes o f resources , such as Ma cintos h
IIci and LaserWriter. Zones, mentioned previously, are collections of nodes on the network. Typical
Macintosh NBP information might be [Kathy, Macintosh IIci, Accounting] for the name, type, and zone,
respectively. A serv ice offered by the E TS called MyPrinter that has AppleTalk enable d and that is located
in the Engineering zone would have an NBP description of [MyPrinter, LaserWriter, Engineering]. If the
LaserWriter resource in the Engineering zone were selected in the Chooser, one of the resources shown
would be the MyPrinter service offered by the ETS.
The NBP type LaserWriter designates a PostScript printer, so nodes printing to printers of type
LaserWrite r assume that th e printer sup ports PostSc ript. Care must be taken to attach only PostScript
printers to ETS ser vices with AppleTalk e nabl ed , an d t o d isa ble AppleTalk on servi ce s t hat do not support
PostScript printers. It is not possible to print to non-PostScript printers (for example, ImageWriters and
StyleWriters) from a Macintosh via the ETS.
2.5 LAN Manager
LAN Manager is based on the NetBIOS pr otocol. It is use d by several PC-b ased operatin g systems, notabl y
OS/2, Windows NT, and Windows for Workgroups , althou gh LAN Manage r serv ers have been written f or
HP and Sun workstations. The ETS i mplements only en ough of the NetBIOS protoc ol stack to provi de print
services to nodes; no interactive logins are allowed.
The ETS also implements the straightforward and easy to use DLC printer protocol typically used by HP
laser printers. You must se lect the hardware addre ss of the ETS as the target for t he print job. DLC operation
is only supported under Windows NT. DLC does not provide queueing on the ETS, nor does it allow
printing to more than one service on the ETS.
2.5.1 Networking
NetBIOS is not a routable protocol, so the ETS can only communicate with local nodes or nodes that are
accessible via a gateway capable of bridging the NetBIOS data.
Concepts LAT
2-5
LAN Manager node lookups take a text resource name and resolve it into a hardware address. For this
reason, node and resource names must be unique on the network, and the ETS will print an error message
if any configuration that violates this rule is attempted.
Note: NetBIOS can be run over TCP/IP, but the ETS does not support this mode of
operation.
2.6 LAT
Digital Equipment Corpor ation’s LAT ( Loca l Area Trans port) netw orkin g software is d esigne d to eas e the
process of accessing and managing local area networks.
LAT is significantly different from other protocols in two important ways. First, LAT is not routable. There
is no way to divide LAT networks into smaller subnet works and use routers to reduce tra ffic between nodes.
Second, LAT is a timer-driven protocol. Packets are expected at certain intervals, and the protocol cannot
adapt to slow network lin ks dynamically. Fo r these reaso ns, LAT traffic over wide areas is ty pically carri ed
inside (or encapsulated in) TCP/IP or IPX/SPX packets. The latter two protocols are fully routable, and
can handle wide-area, slow network links.
Note: If LAT is bridged across slow links, session time-outs and errors are likely.
LAT software is built around the concept of services. A service may be provided by a dedicated device,
such as a printer, or by a ne twork host. A device t hat offers one or more se rvices, such as your ETS, is called
a node.
Services have names, and there can be more than one service on a network with the same name. For
example, you could attach eight modems to a server and set up the service modem to use ports 1-8; a user
who typed Connect Modem wo uld not nece ssarily know which port would be used fo r the connec tion. Note
that if a service is provided by the lo cal ETS and a lso a by r emote node, there i s no guaran tee that a connect
command issued locally would result in a connection to the local service (although this can be explicitly
requested).
LAT Concepts
2-6
In general, all ser vices offered by the ETS are ass ociated with one or more ports; exceptions t o this rule will
be noted later. Figure 2-2 shows an example of services offered on a network.
Figure 2-2: Example of Network Services
Nodes advertise their services to the network by broadcasting occasional messages about them. These
messages, referred to as multicasts, contain the node’s name and its list of services. By monitoring
multicast messages, all hosts on the network know what nodes and services are available and can provide
this information to their interactive users. The Show Services and Show Nodes commands display this
information.
LAT multicast messages contain a rating for each service offered. Ratings range from 0 to 255; 0 means
the service is unavailable, while 255 means the service is available and has no current users. Ratings for a
given service may cha nge over t ime. For ex ample, t he ratin g for a c omputer accept ing logi ns will g enerall y
change as its workload cha nges. Conv ersel y, rati ngs for a modem are t ypical ly eit her 0 ( in use) or 255 (no t
in use). In the example above, the server with eight modems attached will continue to advertise that the
service “modem” is available (a 255 rating) until all eight modems are in use (a 0 rating).
Service ratings may concern even casual users, since they are used to determine which service a user will
be connected to whenever there is a choice. For example, if a user types Connect Hub and five nodes
offer service hub, the user will be connected to the least busy node automatically. In the case mentioned
above, where both the local ETS and a remote node offered the same service, the ratings determine which
node will service the connection attempt.
Another major netwo rk management featur e of LAT is the concept of service groups. Eac h port on the ETS
and each service on the network can be thought of as belonging to one or more groups. When a user or
device requests a service connection, the LAT host will check to see if the groups to which the requester
belongs match those of the r equested s ervice. If any group number is common to both the request er and the
service, the connection attempt continues. If there are no common group numbers, the connection attempt
fails.
Note: There may be additional access restrictions on the service, such as password
protection.
Node Vax2, with
service Vax2
(logins to other
users)
Node Phred, a computer
offering services
"LaserPrinter" (for
printing) and "Phred"
(for logins)
Node Server_1, offering
service "modem"
01
PWR OK NET RCV XMT
EPS4
LANtronix
Concepts TCP/IP
2-7
Suppose Bob is logged into port 4 on his ETS and the server manager has given port 4 access to groups 1,
7, 13, and 105. Bob, or anyone else using port 4, can only access services that have one of those group
numbers. Suppose Bob wishes to access a modem on a different server. If the server to which the modem
is attached allows access to groups 8, 12, 16, 42, and 105; Bob will be allowed to use the modem because
he and the modem service have group 105 in common.
Note: See Set/Define Port Authorized Groups on page 12-28 and Set/Define Server
Service Groups on page 12-80 for more information.
Group numbers also are useful to nodes because each node only needs to pay attention to multicasts that
involve its users’ groups. As a result, groups can hide services that would otherwise be visible. The server
manager can also hide se rvices from a set of port s. Setting up and managi ng services and groups i s discussed
in more detail in the Server Configuration chapter, n ext.
ETS units used in the LAT environment support remote configuration of server ports by VMS hosts. This
feature of the LAT softwar e allows the serve r to implement VMS commands that chang e a user’s “termin al
line.” For instance, if user Bob con nects to a VMS host and ty pes the command Set Term inal/Spe ed=2400,
the speed will be changed on the host and the host will ask the ETS to change the “real” terminal line (in
this case, Bob’s ser ia l port on the server). Thi s feature supports chan ges to parity and flow control as well.
Note: Remote control can b e disa bled; see Set /Defi ne Port Remote Co nfigur e on pag e
12-49.
2.7 TCP/IP
2.7.1 IP Addresses
Every TCP/IP node on a network has an IP address, which is unique to that network and an Ethernet
Address, which is unique across all hardware in the world. The IP address provides information needed to
forward packets across multiple networks, if necessary.
The address is of the form n .n.n.n, where each n is a number from zero to 254, as in 192.0.0.1 . The exception
is that there cannot be a zero in the last segment of the address.
Note: The number 255 is strictly reserved for broadcast packets.
A unique IP address must be specif ied on the ETS before any of the TCP/IP funct io nal it y is available. See
your Installation Guide for more information on configuring the IP address.
A DHCP server can be used to tempora rily assign a leased IP ad dress to the ETS. See Dynamic Host Control
Protocol (DHCP) on page 12-10 for more information.
TCP/IP Concepts
2-8
2.7.2 Telnet
Telnet is an industry-standard network protocol. Networks that support Telnet can (and do) stretch for
thousands of miles a nd cont ain t housands of ho sts. Th e theo ry behi nd Tel net i s that a use r anywhe re on the
network can access a for ei gn host and start a ter mina l session. The user does not hav e t o wor ry ab out what
kind of computer or operati ng system he is dealing wit h, and the remote host does not need to know the type
of terminal the user is using. Telnet accomplishes this compatibility with the virtual terminal: any Telnet
connection looks the same from both sides of the network. Figure 2-3 illustrates this concept.
Figure 2-3: ETS Network Telnet Example
2.7.2.1 Telnet Connections
All terminals on the network can access all hosts, but do not need to know (nor can they know) the host’s
exact hardware type. Theoretically, terminal 4 in the example above could establish a Telnet session with
host Phred, and would see t he same type of sessi on as it would with a direct terminal connection to terminal
5. Phred, the CPU, will also treat terminal 4 as if it were directly connected.
A Telnet connection begin s with both par ties in the c onnection assuming t hat the other termina l is “dumb,”
that it knows littl e ab out cha rac ters, fonts, cursor movement, a nd so on. The two sides negoti at e opt io ns t o
determine the capabi lities of the other. For example, a t erminal might su pport full curso r-control char acters.
Once the connection is established, the terminal and host may agree to support the extra characters. This all
happens transparently to the user, who sees only a login screen and none of the negotiation process.
By default, Teln et connects to a pre-set po rt number to access a remote host’s Telnet server. The ETS allows
the specificati on of a port number other tha n the default to be used for the connectio n. For example, if a host
is set up to listen to Telnet requests on port number 1034, that port number can be specified in the Telnet
command entered into the ETS.
Note: The Telnet command is explained in the Command Reference chapter.
Concepts TCP/IP
2-9
2.7.2.2 Rlogin
In addition to Telnet, ETS users can use the Rlogin application to connect to remote TCP/IP hosts. Rlogin
is similar to Telnet, but it can be configured to allow trusted users to log into a host without password
verification. For this reason, Rl ogin can be a s ecurity problem, a nd is not enabl ed on all sit es. TCP/IP Server
Parameters on page 4-5 explains how to set up Rlogin access and di scusses the methods of user verifi cation.
Like the UNIX version of the command, the ETS Rlogin command allows the user to specify a different
username for logging in to remote devic es. Both Telnet a nd Rlogin suppor t the port’s Termtype fiel d, which
allows hosts to discover the type of terminal device automatical ly.
Note: Rlogin is explained in the Command Reference.
TCP/IP implementations generally have no knowledge of remote hosts until a connection is attempted.
There is no searching for a host until the actual connection request is made. The UNIX operating system
supports the rwho faci lity to allo w hosts to see e ach ot her withou t an a ctive co nnecti on, but it i s not always
implemented, enabl ed, or supported. Host s running rwho send out oc casional broadcast s containing the host
name, address, and user informati on. The ETS will listen for rwho broadcas ts and keep track of which UNIX
hosts are available. See Show/Monitor/List [Telnet] Hosts on page 12-113 or your local host
documentation for more information.
2.7.2.3 Subnetworks
TCP/IP Internets are usually broken down into networks, where a host is able to see only the hosts on its
own network or sub-unit. TCP/IP networks then rely on routers (or gateways) to transfer network traffic
to hosts on other networks.
Routers are typically connected to two or more networks, and will pass, or route, TCP/IP messages across
network boundaries. The ETS can be told explicitly which hosts are the gateways for the local network. If
no gateways are currently specified, the ETS will listen to routing protocol packets (for example, RIP) to
decide which hosts are acting as gateways. See Set/Define Server Gateway on page 12-66 for more
information.
The ETS decides at connecti on time whet her th e desir ed TCP/IP host is on the loc al net work segmen t with
the help of the subnet mask on the server. This mask tells how much of the IP address is the network
address, and is applied to the IP addresses of both the ETS and the remote host. If the resulting addresses
are identical, the conne ction is deemed local and the host is contacted directly. I f not, the connection attempt
and all subsequent messages to this host will be directed to the ETS’s gateway host for forwarding. The
subnet mask, if not set expl icitly , will be automati cally con figured f or the given IP address. Se e Set /Define
Server Subnet Mask on page 12-83 for more information.
2.7.3 Name Resolution
TCP/IP hosts generall y have an alphanumeri c host name, such as Phred, in addition t o a numeric IP addr ess,
such as 192.0.1.99. For this reason, the ETS supports the use of a local host table and domain name
servers— hosts that can translate text host names into the numeric addresses that are needed for a
connection.
TCP/IP Concepts
2-10
Text names make it unnecessar y to r emembe r lo ng strings of address numbers . For exampl e, suppose user
Bob wishes to log into a host named “alex.weasel.ctcorp.com.” The other hosts on the network have no
knowledge of which pi ece of hardware is associated wit h this name, so the ET S must translate the name into
a numeric address, such as 199.25.172.6. After the name is translated (or resolved), the connection can be
attempted.
See Set/Define Se rver Domai n on page 12-65 for more information.If the re i s n o local host table or na me
server to provide text name tr anslation, or if the name server(s) can not translate the name, the host’s numer ic
IP address would have to be used for the co nnec ti on. Also, if the ETS has not been told which local ho st is
acting as the name server (see the Set/Define Server Nameserver command), it assumes that none is
available and the connect request will likely fail.
The ETS also allows the s etting o f a default domain name t o be appende d to any hos t name for which name
resolution is performed. In the example above, if Bob’s server had a default domain name of
weasel.ctcorp.com, then Bob could type telnet alex and the ETS would attempt to resolve
alex.weasel.ctcorp.com. This name checking occurs for all ETS commands that require text name
resolution, such as Tel net, Rlogin, and Ping. If the con nect destina tion name ends with a period, the domai n
name is not added to the hostname for resolution.
2.7.4 Local Host Table
The ETS enhances name resolution by providing a simple host table, which is a list of node names and
corresponding IP addresses. Using the Set/ Def ine Telnet Hosts command, the server manager can add
hosts to this table. Thi s allows the user to ente r a text na me desc ribed i n the tabl e in place of an IP addre ss,
which in turn eliminates the need to remember IP addresses. The local host table is especially useful for
sites that do not have a domain name server, or in cases where a few hosts are accessed frequently.
The Show Hosts command displays all curre ntly- known IP node s and how they were learn ed: via the l ocal
host table, a local name server, rwho broadcasts, or name resolution during a connection attempt.
If name serving is enabled, the name server will be asked for the node’s IP address only if the local host
table does not contain the informat io n. This mean s that inc orrec t infor mati on in the loc al host ta ble will be
used, even if it is contrary to what a nameserver might report. The local host table does not have to be
consistent with the name server, but consiste ncy will avoid c onfusion. To mai ntain consi stency, remove the
old hosts from the host table with the Clear/Purge Telnet Hosts command.
Host table aliases should b e easy to type , remember , and re cog nize. Th ey are limit ed to 64 charac ters , with
a maximum length of 16 characters per segment. For example, alex.weasel.ctcorp is legal, while
alex.communicationsserver.ctcorp is not.
The ETS can also get host names and IP add resses from nod e rwho bro adcasts and at tempt t o add entries t o
the host table b ased on thi s infor mation. If the r who addr esses are clea red from t he table, they wi ll reapp ear
the next time the host sends out an r who message. Addres ses will also r eappear if a user attempts to connect
to one of them.
2.7.5 Dynamic Host Control Protocol (DHCP)
DHCP, an extension to BOOTP, allows network administrators to lease IP addresses to network nodes as
needed. ETS servers offer two levels of DHCP support: boot and runtime.
Concepts TCP/IP
2-11
If your ETS has boot mode DHCP support, t he ETS will a ttempt to a cquire an IP address via DHCP at boot
time. If it succeeds, the ETS will save the IP address into NVR and continue with the boot process. Once
running, the ETS’s operational code will attempt to acquire the same IP address from the DHCP server. If
for some reason the runtime DHCP request fails (for example, if there is no response for 15 seconds), the
ETS will use the address saved in NVR.
If your ETS does not support DHCP at the boot level, you can still use DHCP at the operational level. To
enable DHCP in the runtime code, enter the Set/Define Server DHCP Enabled command and reboot the
server.
Note: Enabling DHCP will remove the IP address saved in NVRAM, if there is one.
The ETS will use BOOTP or RARP to acquire an IP address at boot time, and then it will request an IP
address via DHCP once it is running. If the runtime DHCP request fails, the server will use the IP address
stored in NVRAM. If t he DHCP request succeeds, the ETS will use the result ing IP addre ss. It will not save
the IP address to NVRAM or overwrite the saved address (the one acquired by BOOTP or RARP).
If you enter a new IP address with the Set/Define Server IPaddress command, the ETS will assume that
you want to use that address in the future, and will disable DHCP.
Note: When DHCP is used, the IP address saved in NVRAM will change e ach time the
ETS boots, and the List Server Bootparams command (which shows the
characteristics that will be in effect the next time the ETS boots) may show a
different IP address than the one that is currently in use.
TCP/IP Concepts
2-12
2.7.6 Serial Line Internet Protocol (SLIP)
The SLIP protocol allows hosts to communicate via TCP/IP over a serial line instead of Ethernet. Due to
the point-to-point nature of serial lines, only two hosts can communicate over a single line. SLIP is most
frequently used for dialup modem lines, where a SLIP-equipped TCP/IP host can dial into the ETS, begin
a SLIP session, and thus ga in acc ess to the ne twork a ttach ed to t he ETS. The remote host c an sta rt se ssion s
to the ETS or any other hos t on the networ k, subject to security and oth er login res trictions. If multiple TCP /
IP hosts are connected to the ETS via SLIP connections, each SLIP host can also access any of the other
SLIP hosts, with the ETS routing pac kets be tween the serial lines . An example SLIP s etup is s hown below.
Figure 2-4: SLIP Example
Note: See Set/Define SLIP on page 12-95 for more details.
In the example above, assume all host s hav e a subnet mask of 255.255.255.0. All four host s will appear to
be on the same network segment, and all four will be able to start TCP/IP connections with each other.
The ETS in this case “rout es” pac ket s betwe en the seria l lines and the Ether net withou t help from th e ho sts
involved. Note that since all the hosts are on the same network, the ETS is not routing in the true sense of
the word, and any “real” IP routers on the network will not be affected by the SLIP sessions. The ETS is
only directing network traffic to the proper serial port.
The ETS checks each packet it receives to see if it is destined for the ETS, or if it should send it to one of
the SLIP hosts or out to the Ethernet. If an Ethernet packet is sent to the ETS and there is no SLIP connecti on
for it, or if a packet is received from a SLIP port but is not from the host that is supposed to be there, the
packet is discarded. This prevents other hosts from connecting to an active SLIP line and accessing the
ETS’s Ethernet. The ETS also provides ARP replies for its SLIP hosts so that hosts on the Ethernet can
resolve their IP addresses.
There are two restrict ions on ETS SLIP support . First, there can be onl y one host at the end of the serial line.
The ETS will only fo rward packets to and from the host regist ered on the SLIP line, it will not rout e packets
to and from a SLIP network (m ult i ple host s) . Sec ond, a ll of t he hosts connected via seri al li nes mus t be on
the same network and subnet as the server.
ETS
Server
Ethernet Backbone
Modems
Host 192.73.100.11
Host 192.73.100.23
Host 192.73.100.78
Host 192.73.100.172
Serial Lines
AUI Cable
Concepts TCP/IP
2-13
The SLIP section of the Server Configuration chapter covers SLIP setup and other restrictions.
2.7.7 Simple Network Management Protocol (SNMP)
The ETS supports the SNMP network protocol, which allows hosts on the network to query nodes for
counters and network statistics and change some parameters on those nodes. The form of these requests is
documented by RFC 1098. The list of items that can be queried and/or set and the type of data used, such
as integer and str ing, a re bot h docu mented i n v arious Mana gement Inf ormati on Base s (MIBs) . MIBs co ver
a variety of things, such as parallel port status, counters, and IP address resolution tables.
The ETS supports the following MIBs:
MIB-II (RFC 1213) System, Interface, Address Transl ation, IP, ICM P, TCP, and UDP, but not the
EGP group.
Parallel MIB (RFC 1660)All parallel devices.
Serial MIB (RFC 1659)All Serial devices.
Character MIB (RFC 1318)All character-oriented devices.
The ETS will respond to querie s for unkno wn MIBs with a “not in MIB” error t o the requ esting host . RFC’s
1065, 1066, and 1098 offer add itional informat ion on SNMP queries and t he structure of the MIBs. See Set/
Define SNMP on page 12-98 for more information about configuring MIB usage.
Traps are sent to a host when an abnormal event occurs on the ETS. The ETS can generate limited forms
of three SNMP traps. It will gene rate a Coldstart trap when it first boots, and a Linkup trap when the
startupfile (if any) has been read from a host and normal operation commences. If a startupfile has been
configured but t he download f ails, the ETS will send an Authentication trap. In all three cases, the trap wil l
be directed to the IP address of the ETS’s loadhost. The ETS will not generate traps for any other cases.
Note: To disable traps, define t he Loadhost as “0.0.0.0” and re boot the server. See Set/
Define Server Loadhost on page 12-70 for syntax.
The ETS has a local SNMP security table to restrict or prevent unauthorized SNMP configuration.
2.7.8 Reverse Telnet (RTEL)
When a server provides a servi ce to a LAT host, the connection is of ten referred to as Reverse LAT. Reverse
Telnet allows a UNIX host to initiate connections to the ETS in much the same way. It is called Reverse
Telnet because “normal” connections are logins from a server to a host.
Your ETS comes with special software to add RTEL functionality to your UNIX host. RTEL connections
can be made through a back- end program for a printer, o r through a named pi pe. For example, yo u can print
files from your UNIX h ost t o a printer attached to the ETS through your hos t’s lp or lpr print system. ETS
services do not care what hosts are using them. Multiple jobs from any of the supported protocols can be
queued simultaneously on any service.
TCP/IP Concepts
2-14
2.7.9 LPR Support
The ETS and many UNIX systems implement the lpr (Berkeley remote printing) protocol, a protocol that
makes it very easy to add pri nt ho sts to a system. To add the ETS as a print hos t, add the ETS’s IP address
to a host table and add the ETS’s service name as a print queue. No special host software or other
configuration is needed. ETS services can be accessed via the normal lpr commands on the host.
Print jobs can be forwarded multiple “hops” in the network. If you only want one host to know about ETS
print queues, configure the other hosts to forward their print jobs to that host which will forward them to the
ETS for printing.
Note: See Chapter 7, TCP/IP Host Setup, for more information.
2.7.10 UUCP Support
The UUCP (UNIX-UNIX Copy Protocol) utility allows UNIX hosts to transfer files between machines. It
is most commonly used for electronic mail transfers and can be run over Ethernet, typically via TCP/IP or
serial links. When run via TCP/IP, a handler for UUCP typically listens on port 540 of the host; when a
connection to this port is ma de, a UUCP connect ion is ass umed and the UUCP negotiation begins. The E TS
provides support for incoming and outgoing UUCP connections.
Incoming UUCP can be accomplished with the server handling the serial line and creating a network
connection to the UUCP machine. Since UUCP typically does not provide Telnet interpretation, the ETS
Connect TCP command would be used to pr ovide a raw TCP data stream to t he UUCP host, and specifically
to UUCP port (540).
Dedicated connections t o the UUCP port can be made by adding the appropriate TCP parameter s to the Port
Dedicated command, or by adding an environment string to TCP/IP connection settings.
Outgoing UUCP connections can be made in a similar manner. The UUCP host must be configured such
that outgoing UUCP network connectio ns are made t o the ETS UUCP por t. If the ETS has been configure d
with the Set/Define Server UUCP co mmand on page 12 -84, it will at tempt to co nnect to a speci fic servi ce
named UUCP. This service must ma p to one or more ETS ser ial ports, poss ibly ones with mode ms attached.
A chat script (L.sys or Systems files) on the UUCP machine provides the commands needed to dial the
modem and log into the remote UUCP machine. Th e ch at scr ipt needs no kno wledge of the ETS c ommand
set or service connection sequence.
2.7.11 TCP/IP Utilities and Commands
The following commands have been added to help TCP/IP usability:
Finger Displays users on local and remote hosts. The f inger command by its elf shows
all users on the ETS. If given with a parameter, such as user@host, it shows
information regardi ng the named user on the specifi ed host. The user name can
be omitted, in which case all the users on the remote host will be displayed. If
the host cannot be reached or accessed, the finger command fails.
Note: To see a list of ETS processes, enter the command “finger finger.”
Netstat Displays the status of the routing tables and current network sessions.
Concepts LAT and TCP/IP Connectivity
2-15
Ping Sends a TCP/IP request for an echo packet to another network host to test
network connections.
Send Ena bles users on Telnet session to send explicit Telnet control characters, suc h
as Abort Output (AO), Are You There (AYT), and more.
2.8 LAT and TCP/IP Connectivity
The service capabili ties of the ET S also all ow transla tion betwe en LAT and Telnet protocols. Fo r example,
a user on a LAT host might see and connect to an ETS offering service ernie as a LAT connection. This
“service” might actual ly be a Tel ne t con nec tion to host ernie. In the other direction, a TCP/IP user can use
the UNIX Telnet or Rlogin command to connect to a LAT host through the ETS.
Both cases can take place transparently to the user. This implies that the TCP/IP host does not need LAT
software, nor does the LAT host need additional TCP/IP software. The only difference between the
connection types is thei r setup. One should kee p in mind that each su ch connection con sumes ETS memory
and processing resou rces because eac h is treated as a connected “port ” and user on the ETS. Chapter 7, TCP/
IP Host Setup, explains how to set up Telnet to LAT and LAT to Telnet translations.
2.8.1 Connection Methods
The mechanics of the protocol translator add the ability to actually connect to the ETS from either a TCP/
IP host (using Telnet or Rlogin ) or a LAT hos t. For example, if the ETS’s IP address is 192.0.1. 92, a Telnet
connection from an IP host t o this addr ess wil l retur n the local pr ompt just as if the us er had logg ed in on a
hardwired port. Also, the ETS ca n advertise itself as a “service” to LAT hosts. That is to sa y, LAT hosts can
connect to the server and obtain the local prompt.
Once an incoming (LAT or Telnet) connection has been started, users can use the server as if they were
connected on a local port. They can start outgoing connections, connect to local services, configure the
server, and so on. TCP/ IP users th en have a con venient way t o remotely “ma nage” the se rver: managers can
simply log in and become the privileged user, change server parameters, and log out again.
2.8.2 Environment Strings
The ETS can be configured to set up sessions according to the host to which it is connected. These
environment settings can be supplied via the Connect command, or can be saved either as part of the
preferred or dedicat ed host name or as part of a vi rtua l tra nslation servi ce. Most of the environment optio ns
mimic the Set Session command options.
The environment str ing is a se quence of key letter s, sometimes pr efixed by a pl us (+) or minus (-). The keys
are added after the hostname and a colon for Telnet or Rlogin connections, and are specified via the
EnvString paramete r for LAT connections. The available key lett ers are explained in the Connect co mmand
on page 12-9.
Key letters are not case-sensitive, and no white space is allowed in the environment string. In addition,
commands that oppose previously-configured settings will overwrite the previous setting, even if they
appear on the same command line.
NetWare Concepts
2-16
2.9 NetWare
Novell’s NetWare software allo ws you to link compu ters together and provide fi le and printer sh aring. It is
typically used to network DOS-based PCs, but is starting to appear under UNIX and other operating
systems. NetWare is built around file servers, which handle user logins, provide network resources, and
control security. At least one file server, such as a PC or UNIX host, is required in any NetWare
environment. Net Ware users ty pically have to log i nto a file server to e njoy the net worked (sh ared) benefi ts.
The ETS supports a sig nificant subset of t he NetWare functionalit y, most notably print sp ooling. Fileserver s
can be configured to send queued pr int jobs to print ers attac hed to the ETS. No special sof tware is req uired
on the fileserver; configuration uses the EZWebCon Configuration software or the standard PCONSOLE
utility. Any user or application that can use NetWare print queues can spool jobs to the ETS.
The ETS must periodical ly query the fi le servers for pending jobs. To do s o, it logs into a f ile server to acc ess
the print sp ooler, and will try to connect to al l file server s on the local network (subject to a ccess lists,
explained later) to check for such j obs. See Set/Define Server Net Ware Loadhost on page 1 2-74 for more
information.
NetWare support includes an IPX COM port redirector that allows users on IPX networks to share modems.
For more information, see the Redirector Quick Installation Template that came with your ETS. NetWare
support also allows logins from fileservers to the ETS (for configuration) and file downloading (to
download the system software at boot time).
2.9.1 Networking
Each NetWare node uses its hardware address as its node ID. In addition, the ETS gets all the networking
information it ne eds f rom per iodic broa dcasts sent by Ne tWare r outer s on the n etwork. It wil l le arn i ts own
network number as well as routes to non-local file servers. No further configuration is needed.
The NetWare protocol can use all fo ur Ether net fr ame format s. It wi ll li sten f or all fr ame fo rmats, a nd then
use the correct o ne for the con nec tion. Th e diff erent fr ame type s are treat ed as d iffer en t networ ks, and thu s
each frame type has a different network number. If there is only one frame format in use on the LAN, the
ETS will use the network number for that frame type. If there are multiple frame types, limitations to the
NetWare protocol require that the ETS use a different network nu mber for each frame type on which it wants
to advertise itself.
The ETS can use multip le frame types b y creating a ne w, unique “inte rnal network number” and advert ising
itself as a router to the internal network. Any nodes or fileservers that need to communicate with the ETS
use this new network number, and treat the ETS as a router to that network. If this behavior is not desired,
the ETS can be forced to use only one frame type (and thus not need an internal network number).
2.9.2 Access Lists
Since NetWare networks can have hundreds of fileservers, the network needs a way to reduce the number
of ETS queries, both to reduce network traffic and to prevent long delays in servicing active queues. By
using access lists (created with the Set/Define Protocols NetWare Access command on page 12-59) you
can control w hich file servers the ETS w ill and won’ t poll for prin t jobs.
The file servers have no co ntrol over the ETS access lists , so they wi ll neve r know if a misco nfigur atio n of
the access list prevents them from spooling print jobs to the ETS.
Concepts Sessions
2-17
2.10 Sessions
When a user connects to a service on the network (LAT, Telnet, or Rlogin), he or she creates a session. A
non-networked terminal with a dedicated line fro m the termina l to the CPU is ty pically limited to a single
session—users must log out of the current session before they can connect to new host or service.
With the ETS, however, this restriction is eliminated. A user can have several open sessions at a time,
although only one is displayed on the screen. Four important topics accompany our discussion of multiple
session support:
◆ Leaving an active session and returning to the Local prompt.
This is accomplished with the Break key. Pressing it will retur n the server to Local mode, leaving any
sessions connected. In Local mode, users can issue server commands to perform various ETS
functions.
If your terminal device has no Break key, you can configure a local switch key with the Set/Define
Port Local command.
◆ Moving between active sessions without returning to the Local prompt, or moving from the Local
prompt to an active session.
The Backwards and Forwards commands, entered in Local mode, move users backwards and
forwards through sessions. In addition, the Set/Define Port Backward and Set/Define Port
Forward commands allow users to define switch keys to move forwards and backwards through
sessions without returning to Local mode.
◆ Setting session characteristics.
The Set Session commands allow you to configure each session to perform various amounts of
processing on the input character stream. For example, it is possible to configure the session so that
it does not interpret and strip out flow control characters.
It is also possible to redefine the Delete and Return keys for Telnet connections, depending on the
host to which you ar e connectin g. This is e specially useful for TCP/ IP hosts tha t expect bo th Carriage
Return and Line Feed, for example, or only Line Feed. Note that you can only set the current
session—you must move through the session list if you wish to change a non-current session.
◆ Disconnecting sessions from Local mode and Resuming them.
If a session on a remot e host freezes u p or gets stuc k executing co de, you can Break o ut of the ses sion
and close it with the Disconnect command. You can also resume work on a session after you’ve
returned to L ocal mode wit h the Resume command. Both commands can affect any of the active
sessions, not just the current one. Logging out of the server closes all active connections.
For an example of how th ese functi ons work, se e the Using the ETS chapter,
The number of active sessions a user can have on the server is limited by two factors: available server
memory resources and software limits (including a server-wide session limit and a port-specific session
limit). The absolute maximum number of sessions per port is eight.
PostScript Concepts
2-18
See Set/Define Server Session Limit on page 12-80 and Set/ Define Port Session Limit on page 12 -50 for
more information.
2.11 PostScript
Many printers (including all LaserWriters and other AppleTalk compatible laser printers) use a printing
language called PostScript. Unlike other printer protocols, which typically accept ASCII characters and
print them verbatim, PostScript is also a programming language. Shapes and fonts can be defined as
routines and re-used on successive pages, multiple fonts and copies can be printed, and text and diagrams
can be rotated and shifted on pages.
PostScript is also an interactive language, where the printing host can query the printer for its knowledge
about fonts and software versions. If the host expects to receive data from the printer (as is the case for all
AppleTalk printing ), the pr in ter must suppor t Bitr onics mode and b e connec ted to a bidi rect ional port su ch
as one on the ETS. PostScript printing from UNIX, LAT, and NetWare host s, where bidirect ional data f low
is not a requirement, can generally use any parallel port.
PostScript is a verbose la nguage; it is recommen ded that th e printer and ETS use a baud rate of at leas t 9600
to communicate over serial lines. A baud rate of 38400 or better is strongly recommended for high-output
duty; see the printer’s documentation for information on changing the serial speed. Also, many PostScript
jobs contain 8- bit char acters. The ETS is conf igured f or 8- bit char acters, but if the pri nter is not (the def ault
on many laser printers is 7-bit), some characters will be printed incorrectly. See your printer’s
documentation for details on how to change the character size setting.
Due to the interactive nature of PostScript, it is possible for the printer and host to get out of synch in their
communication. Since the printer “interprets” the entire PostScript job and then prints the pages, it is
possible for the ETS to compl ete the transfe r and ac cept a new j ob while t he print er is still digestin g the la st
job. For this reason, an end-of-job character (ASCII 0x4 or Ctrl-D) is used to end all PostScript jobs.
Typically the host will send one at the end of the job and the printer will reply with one when it is done
processing the job. For information on end-of-job characters, see Set/Define Service EOJ command on
page 12-86.
The ETS will force a Ctrl-D character when PostScript is enabled on the appropriate service and wait for
one in return. Therefore, enabling PostScript is strongly recommended for all PostScript printer
applications. It gua ra nte es that the printer is rea dy to accept new data when the j ob a ct ually starts. Job loss
and printer hangs are the usual result if Post Script is no t enable d on the ser vice and the pr inte r cannot keep
up with the job rate. High-speed printers may happen to work if the PostScript attribute is not enabled,
simply because they finish the current job in the time it takes for the ETS to accept the next one.
2.12 Modem Features
The ETS supports both incoming and outgoing modem connections. The ETS can be conf ig ured to offer a
modem service to both LAT and Telnet users . Using the DSR and DTR s ignals from the s erial line s (see the
Serial Pinouts appe ndix in you r Install ation Guid e) th e ETS ports can both l og out an attached modem after
a connection exit s and be logged out if the modem hangs up. Ports ca n a lso be configured to a uto ma ti cally
detect the baud rate at login time allowing multi-speed modems to connect easily.
Concepts Security
2-19
The ETS allows port s to be configur ed with t he Dialup and/or DTRwait charact eristi cs. Dial up will t ell any
LAT service that a port is connected to a modem; the remote node may decide to disallow the connection
based on that flag for securi ty re asons. The DTRwait ch aract erist ic wil l force t he ETS to de-asse rt DTR on
a port until a user actually connects to the port. This connection can be either an interactive login from a
device on the network or a LAT or Telnet service connection. For some modems, de-asserting DTR will
prevent the modem from answering an incoming call unless someone is already connected to the port.
The ETS also provides Dialback support, which requires port users to enter a trusted username and then
allow the ETS to close the connection and attempt to reconnec t via a specified mode m command string. This
ensures that only trusted usernames are used, and that the usernames only log in from a particular phone
number. If an invalid username is entered or the reconnect attempt fails, the connection is assumed to be
non-secure and th e port is logged out. Po rts configured fo r Dialback have a 30-se cond time limit for ent ering
a username at login time to prevent unauthorized users from denying access to others. Dialback does not
interfere with ou tgoing modem connecti ons, so a modem can be restricted fo r incoming logins but still allow
network users full outgoing access.
2.12.1 Remote Configuration
There are three ways to remotely configure the ETS: the Telnet console port, the NCP and TSM utilities,
and SNMP.
TCP/IP users connecting to the Telnet console port (port 7000) will be prompted for the ETS’s login
password. After entering the login password, the user can issue normal configuration commands, but will
still have to enter the privileged password to issue privileged commands. Connections to this port are not
subject to the Set/Define Server Incoming command, and thus managers can log into this port regardless
of whether regular TCP logins are enabled.
VMS users can use the NCP utility to si gnal remo te hosts to perfor m specific opera tions acro ss the network
or form connections to the ETS. Thi s is e specially useful for Flas h-ROM ETS’s, which mig ht not b e placed
in easily accessibl e locations. The TSM uti lity uses NCP to start logi n sessions with the ETS and allows files
of ETS commands to be sent to the ETS. Access to remote control of the ETS can be protected by the
maintenance password.
The Telnet console, NCP, and TSM all require the correct login password to be entered. The default
password is access. It can be changed via the Set/Define Server Login Password command. See Set/
Define Server Maintenance Password on page 12-72 for information on remote access control.
SNMP allows network hosts to query other hosts for counters and network statistics. In general, one host
on a network will run an SNMP application that queries the other hosts on the network to collect statistics
and other inform ation and signal err or co nditi ons. The ET S will not genera te qu eries of its own; i t ca n only
respond to queries from other hosts. See the discussion of Simple Network Management Protocol (SNMP)
on page 2-13 for more information.
2.13 Security
Several methods can be used to control access to the ETS and restrict user behavior once logged in. For
example:
Security Concepts
2-20
◆ Incoming logins can be selectively disabled and/or password protected via the Set/Define Server
Incoming command.
◆ The IP security table can be used to restrict logins to the ETS.
◆ Ports used for network logins can be “preconfigured” with a standard set of characteristics for each
login.
For more information a bout security me asures and re striction options, inc luding some ETS f eatures th at are
used for more than security reasons, see the Server Configuration and Ports chapters.
2.13.1 Menu Mode
For added security or a uniform command interface, system managers can set some or all ports for Menu
Mode. Users logging into a port in menu mode will have the following text displayed on their terminals
instead of the local prompt:
Menu Mode Display
The users will not be able to enter text commands; they will only be allowed to enter a numeric choice from
the menu. Up to 36 commands can be provided for the user s, incl uding a command to exit menu mode and
return to the interac ti ve Loc al > pr ompt. Menu mode frees users from having to r emember ETS syn tax and
generally prevents t hem from entering p rivileged configu ration commands, alt hough it can be con figured to
allow them privileged access.
Configuring the menu is a two step process:
1 The port is configured to use menu mode with the Set/Define Port Menu command.
2 The command entries themselves are configured with the Set/Define Menu command.
A menu command of Exit can be specified, in which case the user will be allowed to exit menu mode and
return to the command line to en ter normal ETS command lines. This mig ht be useful , for users who pref er
the ease of use of a menu but need to return to the command line occasionally. Menu mode can then be reentered via the Set/Define Port Menu command, or by logging out and logging back in to a port that has
menu mode enabled.
The current or saved menu t ables can be displayed via th e Show/Monitor/List Menu commands. Individual
menu entries or entire menu tables can be cleared via the Clear/Purge Menu commands.
<Menu Name>
1. command1
2. command2
...
10. command 10
Enter Selection:
11. command11
12. command12
...
20. command 20
Concepts Security
2-21
2.13.2 Event Reporting/Logging
The ETS can be configured to report various errors and events either to the serial console port or to a
network host via TCP/IP (usi ng the syslogd facility), LAT, or Net Ware . Events that can be logged include
user logins, modem events, printer state changes, system boots, system resets, and a full record of
commands issued on the ETS. See Set/Define Logging on page 12-25 for more information.
3-1
3: Getting Started
This chapter provides background information to get you started using the ETS. Topics include methods
used to initially set up the ETS as well as ongoing maintenance issues, such as rebooting and restoring
factory default settings.
This chapter assumes the following:
◆ The ETS has booted properly and is running its operational code
◆ The ETS is connected to the Ethernet
◆ For IP network users, the ETS has been assigned a valid IP address.
If any of these conditions have not been me t, re fe r to y our Installatio n G uide for information on installing
the ETS.
3.1 Configuration Methods
The ETS may be configured using one of two methods: the EZWebCon configuration software, or
commands issued at the command line (Local> prompt).
Note: To configure the ETS when a pro blem has occurred, refer to the Troubleshooti ng
appendix.
3.1.1 EZWebCon
The EZWebCon software is the recommended way to configure the unit. EZWebCon guides you through
configuration using a graphical interface. Its configurations take effect immediately, like Set commands,
and are permanent, like Define commands.
EZWebCon is shipped with the ETS on CD- ROM. It can b e in stalled and used on any computer for which
there is a Java Virtual Machi ne. To install EZWebCon, re fer to the README file locat ed in the EZWebCon
directory. For assistance once EZWebCon is running, refer to the EZWebCon on-line help.
Note: There are problems with some implementat ions of the Java Virtual Machine. See
the EZWebCon README file for more information.
Configuration Methods Getting Started
3-2
3.1.2 Using a Web Browser
The ThinWeb Manager web browser interface allows you to log into and configure your ETS using a
standard web browser with JavaScript enabl ed. Simply type the ETS IP add ress or resolvab le text name into
the browser’s URL/Lo cation field .
Figure 3-1: Sample Web Browser Login
Once you have connected to the ETS, you will see th e Lantron ix ThinWeb Man ager int erface. Use the left hand menu to navigate t o subpages where y ou can configure impo rtant settin gs as well as vi ew statistics an d
other server information.
Figure 3-2: ThinWeb Manager Interface
3.1.3 Command Line Interface
To configure the ETS without using th e EZWe bCon graphical user interface, you must ent er configuration
commands at the command line when a port is in character mode. In character mode, the Local> prompt
is displayed.
There are four ways to enter character mode:
◆ Connect a terminal to the serial console port and press the Return key until the Local> prompt is
displayed.
◆ Establish a Telnet or Rlogin connection to the ETS from a TCP/IP host.
◆ In EZWebCon, click the Terminal icon. The Local> prompt will be di splayed in a t erminal emulati on
window.
◆ Establish a TCP/IP remote console connection by Telnetting to port 7000:
Figure 3-3: Remote Console Connection
Note: Remote console logins are password protected via the server login password.
See Login Password on page 3-9 for more information.
% Telnet 192.0.1.166 7000
MENU
Getting Started Entering and Editing Commands
3-3
3.2 Entering and Editing Commands
In examples throughout the manual, ETS commands and keywords are displayed in uppercase for clarity.
They may be entered in upper, lower, or mixed case.
The Command Reference chapter displays the syntax of each command, and includes restrictions, known
errors, and r eferences to related comma nds. Optional parameters are enclosed in straight brackets [ ].
Multiple options in a set of brackets may be ent ered, or options ca n be omitted entirely. Re quired parameters
are enclosed in curly braces { }. One and only one of the parameters enclosed i n each set of braces must be
used. User-supplied parameters, such as a particular host name, are shown in italics or all lower case.
When entering a string, such as a username or filename, it is important to remember to enclose the string
in quotes to preserve case and spac ing. If a s tring is not encl osed in quot es, it wi ll be aut omatically changed
to all uppercase characters.
Note: The privileged and login pas swords are case-ind ependent, even when entered in
quotes.
The ETS command completion feature, when enabled, will complete partially-typed commands for you.
This can save time and reduce errors if you’re entering a number of commands. To use command
completion, type part of a command, then press the space bar; the ETS will automatically “type” the
remainder of the command . I f t he partial command is am big uous , the terminal will beep to prompt you for
more information. See Set/Define Port Command Completion on page 12-33 for more information.
All keys used for entering and editing commands are listed in Table 3-1.
Table 3-1: Command Line Editing Keys
Key Purpose
Return Executes the current command line
Delete Deletes the character before the cursor
Ctrl-A Toggles insert mode (insert or overstrike;
overstrike is the default).
Ctrl-D Logs the port out
Ctrl-E Moves the cursor to the end of the line
Ctrl-H or Backspace Moves the cursor to the beginning of the line
Ctrl-R Redisplays the current command
Ctrl-U Deletes the entire current line
Ctrl-Z Logs out of the server
Left Arrow Moves the cursor left
Right Arrow Moves the cursor right
Restricted Commands Getting Started
3-4
Note: Line editing is disabled on hardcopy (printer) ports.
3.3 Restricted Commands
To prevent unauthorized users from changing server-wide characteristics, some commands require
privileged (superuse r) status. To obtain privileged st atus, enter the privile ged password. See Privile ged
Password on page 3-8 for more information about passwords, including the default passwords.
3.4 Command Types
The following commands appear frequently throughout this manual. There are subtle differences between
each group of commands, as explained below.
3.4.1 Set and Define
Set Makes an immediate but not permanent change. To make the change
permanent, use the Save command after configuration is complete.
Save Makes a group of commands entered with the Set command permanent. For
example, users can enter several Set commands to configure a service, then
Save the service.
Note: Settings that are made with bot h Set and Sav e behav e as if the y were config ure d
using Define commands. See Save on page 12-21 for more information.
Define Makes a permanent change that generally doesn’t take effect until the unit is
rebooted. Define Port will take effect as soon as the port is logged out and
Define SLIP will take effect once a new SLIP session is started.
3.4.2 Show, Monitor, and List
Show Displays the curr ent settings. Current setti ngs include those made usin g the Set
command but not yet Saved as permanent changes.
Monitor Displays the cur rent sett ings at regul ar i nterv als ; in form ation is u pdated ev ery
three seconds.
Up Arrow or Ctrl-P Recalls the previous command
Down Arrow or Ctrl-N Recalls the next command
!text Recalls the last command starting with text
!! Recalls the last command
Table 3-1: Command Line Editing Keys, cont.
Key Purpose
Getting Started Abbreviating Keywords
3-5
List Displays the unit’s per manent s etti ngs. Note t hat some settings that ar e List ed
will not take effect until the unit is rebooted.
3.4.3 Clear and Purge
Clear Removes an item immediately, but not permanently. When the unit is
rebooted, the old setting will again be in effect.
Purge Removes an item permanently, but ge nerally does no t take effect unt il the unit
is rebooted. Purge Port will take effect as soon as the port is logged out and
Purge SLIP will take effect as soon as the current SLIP session (if any) ends.
3.5 Abbreviating Keywords
When configuring the ETS via the command line, it is only necessary to type as many characters as are
needed to distinguish the keywords from one another. For example, the following two commands are
equivalent:
Figure 3-4: Full and Abbreviated Commands
Note: Extra white space (more than one consecutive space between keywords) is
ignored.
3.6 Maintenance Issues
The following sections detail configuration that is required on a sporadic or ongoing basis.
3.6.1 Changing the Server Name
The ETS is initially configured with a server name. However, you can give the ETS a custom name of up
to 16 alphanumeric characters using the following command:
Figure 3-5: Changing the Server Name
The ETS name string must be enclosed in quotes if lowercase letters are used.
Local>> DEFINE PORT 2 BROADCAST ENABLED AUTOCONNECT ENABLED PARITY EVEN
SPEED 4800
Local>> DEF PO 2 BRO EN AUTOC EN PAR E SP 4800
Local>> DEFINE SERVER NAME “PrintServer”
Maintenance Issues Getting Started
3-6
3.6.2 Changing the Server Prompt
The prompt each user r eceives (t he Local> pr ompt) is config urable in a variety of ways. For a basic prompt,
enter a command similar to the following. The resulting prompt is shown on the next line.
Figure 3-6: Configuring User Prompt
Note: The remote console port prompt cannot be changed.
For a customized prompt, the options listed under Set/Define Server Prompt on page 12-76 can be
included in the prompt string. Placing a space after the end of the prompt is recommended, as it makes
reading and editing the command line much easier.
Figure 3-7 displays a few examples of commands used to change prompts. In the examples, the first
command line results in the prompt used in the second command line, and so on.
Figure 3-7: Prompt Examples
3.6.3 Rebooting the Server
There are two ways to reboot the ETS: pressing the Reset button while using EZWebCon, or entering the
Initialize command at the Local> prompt.
Options to the Initialize command include rebooting the server, reloading the Flash-ROM code, and
restoring the unit’s factory default settings. The example below shows a simple, immediate reboot. See
Initialize on page 12-14 for more information.
Figure 3-8: Rebooting the Server
If possible, any current use r sessions should be logged out before rebooting the ETS. Disconnecting sessi ons
may prevent connection problems after the ETS is rebooted.
It is courteous to warn users that the server will be “going down;” this can be done using the Broadcast
command. The complete syntax of Broadcast is listed on page 12-4 in the Command Reference.
Figure 3-9: Broadcast Command
Local> SET SERVER PROMPT “Server>”
Server>
Local> SET SERVER PROMPT “Port %n: “
Port 5: SET SERVER PROMPT “%D:%s! “
ETS-8:LabServ! SET SERVER PROMPT “%p%S_%n%P%% “
Port_5[NoSession]_5>%
Local>> INITIALIZE SERVER DELAY 0
Local>> BROADCAST ALL “Server shutdown in 5 minutes.”
Getting Started Editing the Boot Parameters
3-7
3.6.4 Restoring Factory Defaults
Should it become necessary, the ETS can be restored to the defaul t settings install ed at the factory. This will
restore everything—the ETS will functi on as th ough it j ust came o ut of the box. Be c ertai n you wish t o do
this before you start. As ment ioned in Section 3.6.3, you can use the Initialize command to reboot the server
to its factory default settings.
Figure 3-10: Restoring Factory Defaults
3.6.5 Reloading Operational Software
The ETS stores softwar e in Flash ROM that con trols initializa tion, operation, and c ommand processing. The
contents of Flash ROM can be updated by downloading a new version of the operational software.
Reloading the code into the Fla sh ROMs is a strai ghtf orward pr ocess. The operati onal cod e is downloa ded
from a network host vi a TFTP or MOP and then programmed i nt o t he Flash ROMs. To force the uni t to redownload and reprogram its stored code, enter the Initialize Reload command from the command line.
Compressing the code and loading it into the Flash-ROM takes approximately 30 secondst, during which
time the console port is unusable. However, the ETS LEDs will indicate continuing activity. If the ETS is
powered off or otherwise interrupted during the ROM programming phase, the code in the ROMs will be
invalid and the ETS will have to be reloaded again from the network host the next time it is turned on.
3.7 Editing the Boot Parameters
If the information that the ETS uses at boot time changes, you must edit the ETS boot parameters,
including:
◆ Loadhost (TCP/IP or NetWare)
The loadhost is the host from which the ETS operational software is downloaded at boot time.
◆ Backup loadhost (optional)
Software is downloaded from a backup loadhost when the primary loadhost is unavailable.
◆ Software filename
◆ DHCP (may be enabled or disabled)
◆ BOOTP (may be enabled or disabled)
◆ RARP (may be enabled or disabled)
◆ Boot Gateway
At boot time, packets are addressed to the loadhos t but are sent to a boot ga teway host. This elimina tes
the need for proxy-arp on the router.
Local>> INITIALIZE FACTORY
System Passwords Getting Started
3-8
◆ NetWare fileserver name
Boot parameters are edited with Set/Define Server commands.
Figure 3-11: Editing Boot Parameters
Note: The loadfile name must be placed in quotes to preserve case.
3.8 System Passwords
There are three important passwords for the ETS: the privileged password, the login password, and the
maintenance password. All three are discussed in the following sections.
3.8.1 Privileged Password
Changing any server or port setting (and issuing certain other commands) requires privileged user status.
When using EZWebCon, you will be prompted for the privileged password when it is needed. If you are not
using EZWebCon, you must enter the Set Privileged command at the Local> prompt to become the
privileged user.
Figure 3-12: Set Privileged Command
Note: The prompt may change to reflect privileged user status, if configured to do so.
If another user is currently logged into the ETS as the privileged user, you can use the Set Privileged
Override command to forcibly become the privileged user.
The default privileged password for the ETS is system. To change the privileged password, use the Set/
Define Server Privileged Password command on page 12-76 to enter a new password of up to six
alphanumeric characters. It is not necessary to enclose the password string in quotes; the privileged
password is not case-sensiti ve.
Figure 3-13: Changing Privileged Password
If you do not provide the password on the command line, you will be prompted to enter it and then verify
your entry. The password will not be displayed on the terminal.
Note: You can abort the pas sword-entering proc ess by pressing Ctrl-Z at the pas sword
prompt.
Local>> DEFINE SERVER LOADHOST 192.0.1.8 SOFTWARE “newload”
Local> SET PRIVILEGED
Password> system (not echoed)
Local>>
Local> SET PRIVILEGED
Password> system (not echoed)
Local>> SET SERVER PRIVILEGED PASSWORD hippo
Local>> SAVE SERVER PRIVILEGED PASSWORD hippo
Getting Started Configuration Files
3-9
When you are finishe d enterin g the priv ilege d commands, i t is a go od idea to t urn of f privil eged sta tus with
the Set Noprivileged command so that you do not inadvertently change settings.
3.8.2 Login Password
Each port can be configured to require a login password when in character mode. Users will be prompted
for this password when attempting to log into the port.The Local> prompt will not be displayed until the
correct password is entered.
The default login pa ssword is acc ess. To change thi s password, use t he Set/Define Server Login Password
command on page 12-71. You may enter a new password of up to six alphanumeric characters. It is not
necessary to enclose the password string in quotes; the login password is not case-sensitive.
Figure 3-14: Defining Login Password
If you do not provide the password on the command line, you will be prompted to enter it and then verify
your entry. The password will not be displayed on the terminal.
To enable the use of the login password on the appropriate port(s), enter the following command.
Figure 3-15: Enabling Login Password
The ETS uses the login password to log into NetWare file servers. If the login password is changed,
NetWare print queue setups must also be changed to reflect the new password.
3.8.3 Maintenance Password
The maintenance password is used for MOP/TSM access to the server. Unlike the other passwords, the
maintenance password is a string of up to 16 hexadecimal digits (0-9,A-F).
The default server maintenance password is a string of 16 zeroes. To change the password, become the
privileged user and enter the following command.
Figure 3-16: Defining a Maintenance Password
3.9 Configuration Files
A configuration fi le is a series of ETS commands used for automatic configuration of one or more servers.
It may be used by the system administrator when necessary or downloaded automatically from a TCP/IP
host (via TFTP), from a VMS host (via LAT), or from a NetWare fileserver when the ETS boots.
Using a configuration fil e can reduce the time re quired to config ure the ETS. Options that woul d need to be
manually set using EZWebCon or the command line can be automatically executed.
Local>> DEFINE SERVER LOGIN PASSWORD badger
Local>> DEFINE PORT num PASSWORD ENABLED
Local> DEFINE SERVER MAINTENANCE PASSWORD newpass
Configuration Files Getting Started
3-10
3.9.1 Using EZWebCon
EZWebCon will examine the current configuration of your ETS, translate this information into a series of
commands, and save the commands in a file. This file can be downloaded to configure the ETS. Refer to
EZWebCon’s on-line help for more information.
3.9.2 Without EZWebCon
To use a configuration file without EZWebCon, first create a configuration file, then configure the host so
that you can download the file, then configure the ETS to use the configuration file.
3.9.2.1 Creating the File
The configuration fi le conta ins ETS comma nds, one per line, tha t will be executed b y the ETS in s equence.
Privileged commands can be used because the startupfile is run in privileged mode on the server.
Capitalization of commands is optional. If a string (such as a password or filename) is entered, it must be
enclosed in quotes to preserve case or non-alphabetic characters. To include a comment, preface each line
of text with a pound character (#); these lines will be ignored.
If Define Server commands ar e included in the f ile, they will not take effect until the next reboot. Similarl y,
Define Port commands will not take effec t until t he port(s) ar e logged out. All other Def ine commands wil l
take effect for the current boot.
The download file is re-r ead at e very b oot unles s it i s re-conf igured, s o do no t put co mmands like Initialize
or Crash 451 in the file. Unless the startup filename has been changed, an Initialize c ommand will cause
the ETS to boot perpetually, and recovery will require that you flush the unit’s NVR.
Managers can use the So urce command to test the file , in effect causing the ETS to at tempt t o downl oad a
configuration fil e befo re maki ng it a part of t he ser ver’s boot routi ne. This test is s trongly r ecomme nded as
it helps eliminate errors that might prevent the ETS from booting.
Figure 3-17: Configuration File
It is assumed that the console port executes the configuration file; if you use a command without a port
designation, like Set Port Speed 9600, it wil l affect the conso le port’s set tings. Use the Show Serv er Status
command to see which port is currently the console (the default is port 1).
#setting up the ports
DEFINE PORT ALL BITRONICS ENABLED
DEFINE PORT ALL DSRLOGOUT ENABLED
#setting up a print service
DEFINE SERVICE print1 IDENT “Printer on lab ETS port 1”
Getting Started Configuration Files
3-11
3.9.2.2 Configuring the Host
The configuration file can be downloa ded from a TCP/I P host (vi a TFTP), fro m a VMS host (via LAT), or
from a NetWare fileserver. In any case, some host configuration will be necessary.
◆ For TFTP loading, enable TFTP lo adi ng on your host and place the con fi gur ati on file in a download
directory.
◆ For LAT downloading, install the ets$configd service handler on your VMS hosts. The service
handler code is included on the distribution CD-ROM.
◆ For NetWare, put the configura tion file in th e fileserve r’s login directory.
3.9.2.3 Configuring the Server
To configure the ETS to use the commands in the configuration file, use the Source command. If the
configuration file must be downloaded each time the ETS boots, the filename must be specified using the
Set/Define Server Startupfile command.
The configuration fil ename is generally of the form “host*f ilename”, where host ca n be a TCP/IP, VMS, or
NetWare node name. The asterisk should be replaced wit h col ons or a ba cks la sh as follows: use one colon
(:) for a TCP/IP host, two colons (::) for a LAT host, or one backslash (\) for a NetWare host.
For example, to download the file config.cmd from TCP/IP host TROUT at IP address 192.0.1.5, the
following command would be used.
Figure 3-18: Downloading from a TCP/IP Host
Note: You must define a nameserver if you wish to use a text TCP/IP hostname. The
ETS will attempt t o resolve the name at boot time; if it can not resolve the name,
the download will fail.
Figure 3-19 displays the command needed to download the same startup file from NetWare host BASS.
Notice that the host name is now Bass\Sys, and the filename i s now \Login\conf ig.cmd to reflect that the file
resides in the login directory.
Figure 3-19: Downloading from a NetWare Fileserver
Figure 3-20 displays the command needed to download the same startup file from VMS host PIKE.
Figure 3-20: Downloading from a VMS Host
Local> DEFINE SERVER STARTUP “192.0.1.5:config.cmd”
Local> DEFINE SERVER STARTUP “BASS\SYS:\LOGIN\config.cmd”
Local> DEFINE SERVER STARTUP “PIKE::config.cmd”
Configuration Files Getting Started
3-12
3.9.2.4 Download Sequence
If the configurati on file cannot be do wnloaded at boot time, the serve r will retr y the download if con figured
to do so. This behav ior i s gove rned b y t he St artupf ile Ret ry li mit. A Ret ry li mit of z ero mea ns the ET S will
retry forever until it can download the file. Otherwise it will try a specific number of times, then continue
booting.
Figure 3-21: Defining the Startupfile
Note: The ETS is not usable while retrying a download.
If the startupfile i s not readabl e, or if ther e is a problem with t he file and the ETS cann ot boot full y, you will
still be able to access the ETS via the NCP/TSM and Telnet console ports.
Scripts written for TSM should work unchanged, with the possible exception of privileged mode. Set
Privileged cannot b e used in eithe r a Sou rce or St artup file file , so t he command must be re moved fr om any
TSM scripts that are to be used with Startupfile.
Local> DEFINE SERVER STARTUPFILE “filename” RETRY 10
4-1
4: Server Configuration
After powering up the ETS for the first time, you will want to configure it for everyday use. Most of the
parameters discussed in this chapter only need to be set once and can be left alone until a major change is
needed. Please refer to the Glossary for more information about unfamiliar terms.
Note: IP parameters must be specified before Telnet can be used, and an IP address
must be configured bef ore EZWebCon can be used. See your In st all at ion Guide
or the Set/Define Server IPaddress command on page 12-69 for instructions.
After configuring server-wide parameters for your ETS, proceed to Chapter 5 for port-specific
configuration. In addition, be sure to read the appropriate host setup chapter(s) to configure your host
machine(s) to take advantage of available ETS features.
4.1 General Server Parameters
4.1.1 Enabling Incoming Connections
By default, incoming LAT connections ar e disabled and incoming Telnet connections are enabled. To all ow
LAT users to log into the ETS, you must enable incoming connections using the Set/Define Server
Incoming command. The following command allows both LAT and Telnet users to log into the ETS.
Figure 4-1: Allowing Incoming Conn ections
Note: For full command syntax and options, see Set/Define Server Incoming on page
12-68.
4.1.2 Enabling Server-Wide Port Characteristics
You can set up se rver-wide po rt char acteristi cs, such as enabling locking and broadcastin g and setti ng users
session limits. The following commands allows port users to lock their ports, send broadcast messages to
other ports, and set the maximum number of sessions per port to three.
Figure 4-2: Defining Server Characteristics
Individual port users can then lock their own ports as desired, send and receive broadcasts, and start up to
three simultaneous sessions. For more information about port characteristics, see Chapter 5, Ports.
Local> DEFINE SERVER INCOMING BOTH
Local> DEFINE SERVER LOCK ENABLED BROADCAST ENABLED
Local> DEFINE SERVER SESSION LIMIT 3
AppleTalk Server Parameters Server Configuration
4-2
4.1.2.1 Preconfiguring Virtual Ports
Incoming LAT or Telnet/Rlogin logins to the ETS do not have a physical port associated with them, since
they can appear and disappear at random. Therefore, each such connection receives a virtual port at the
time of connection which disappears after logout. These virtual ports are created from a template port,
which is the set of characteristics that every network login receives. Each user can use the Set Port
commands to customize his or her own port during that connection, but cannot save the individual port
settings. A recommended use for the template port is to provide local switches to network logins, as they
typically do not have any Break key to use after they connect.
The ETS provides a way to preconfigure virtual ports. If a parameter is Defined on port zero, it will set up
default parameters to be provided for all of the network logins. If, for example,
Define Port 0
Preferred “Albert”
is entered, the preferred service for all network logins becomes service Albert.
Users can change or clear these characteristics on their own ports with their own Set Port command after
login.
NCP and Telnet remote cons oles ar e consi dered virtual logins , so they will al so rec eive t he template port’ s
setup. They will, however, ignore many of the co nfiguration options, s uch as Dedicated and Acc ess settings.
Otherwise, the console could be rendered useless.
4.1.3 Enabling Announcements
The Announcements flag tells the ETS whether to broadcast local servic e advertisements and MOP remote
console announcements to the network. Normally enabled, Announcements can be disabled if you don’t
want network users to see or connect to the local services. If no services are defined, the ETS does not
broadcast announcements.
Note: For command syntax, see Set/Define Server Announcements on page 12-62.
4.2 AppleTalk Server Parameters
The only configurable AppleTalk parameter is the zone to which the ETS will belong. If there is no
AppleTalk router on the network, all devices will pick the same zone (“*”). If a router is present, the ETS
will use the network’ s d ef aul t zone unless Define Pro toc ols Appl eTal k is used to specify a different zone
name.
Figure 4-3: Specifying AppleTalk Zone
The above command places the ETS in an AppleTalk zone called “AcctZone.” An error will be returned
(and the default zone used) if the specified zone cannot be confirmed with a router.
Note: Zone names are case-sensitive; if lowercase letters are used in the name, the
string must be enclosed in quotation marks.
The current zone name can be viewed on the Show Protocols display. The Show Protocols AppleTalk
screen and its subscreens give even more detail, including the current network range and packet counts. A
node will only show up in the display if it is a router or is in direct contact with the ETS for printing or
configuration.
Local> SET PROTOCOL APPLETALK ZONE “AcctZone”
Server Configuration LAT Server Parameters
4-3
4.3 LAT Server Parameters
Two groups of LAT parameters can be specified in order for the ETS to communicate on the network: the
ETS’s identificatio n information (its ide ntification str ing and name) and network timer s. In addition, a node
limit can be set if desire d.
4.3.1 Server Identification
Select a short, unique and descriptive name for the ETS, as well as a more descriptive string to be used as
the identificat ion string. The na me may contain up to 1 6 characters and t he identifi cation string ma y contain
up to 40 characters.
Figure 4-4: Defining Server Name
Note: If you change the ETS name, be sure to ec ho the change in any ex isting NetWare
print setups.
4.3.2 Network Timers
The LAT network timers (Circuit, Keepalive, and Multicast) as well as the Retransmit Limit are set to
default values at the f actory and are correct for most networks . They sho uld be c hanged onl y if yo u are su re
the change is necessary.
Figure 4-5: Changing LAT Parameters
4.3.3 Node Limit
The Set/Define Server Node Limit command is used to set the number of remote LAT service nodes for
which the ETS will store information. This limit can be set in large network environments to keep ETS
network overhead down.
Figure 4-6: Setting a Node Limit
Local> DEFINE SERVER NAME “Server_1”
Local> DEFINE SERVER IDENT “Biolab Server: Modem Available”
Local> DEFINE SERVER CIRCUIT 60
Local> DEFINE SERVER RETRANSMIT LIMIT 100
Local> DEFINE SERVER NODE LIMIT 5
NetWare Server Parameters Server Configuration
4-4
4.4 NetWare Server Parameters
Several NetWare parameters can be configured to ensure that your ETS functions properly on an IPX
network. First, Set/ Defin e Se rver NetWare Loadhost can be used to spec ify the fileserver fr om wh ic h to
download operational code.
Figure 4-7: Defining a NetWare Loadhost
Other configurable parameters are discussed in the following sections.
4.4.1 Routing and Encapsulation
The ETS will listen to all NetWare frame type s by creating an internal network number and advert ising itself
as a router to this network . In g eneral , th is wil l allo w all nodes an d file serve rs t o acces s the ETS r egardl es s
of frame type. If this behavior is not desired, the ETS can be restricted to only one frame format (and thus
will not need the internal network and routing support). Three commands control this behavior:
◆ Set/Define Protocols NetWare Routing enables or disables the creation and use of an internal
network number.
◆ Set/Define Protocols NetWare Internal Network Number allows you to set the internal network
number if the preconfigured internal network number does not meet your requirements.
◆ Set/Define Protocols NetWare Encapsulation controls which frame type to use when routing is
disabled. The choices are ETHER_II, NATIVE, 802_2, and SNAP, which provide for Ethernet v2,
Native mode, 802.2, and 802.2 SNAP, respectively.
Figure 4-8: Setting Frame Types
By default, Routing is e nabled and all ap plicable enc apsulation t ypes are support ed. See Network Proto cols
on page 2-2 for more information on the various frame types.
4.4.2 NetWare Access Lists
The NetWare access lists are used to control which fileservers the ETS will query for print requests. By
default, the ETS will query all fileservers on the local network.
The access list contains the names of the fileservers to query, and/or the keywords All (no restriction) and
Local (restricts que ries to f ilese rv ers t hat a re on the same n etwo rk as the E TS). For exa mple , the foll owing
commands allow the ETS to query all fileservers on the local network, as well as a single non-local server
named RFS2.
Figure 4-9: Setting NetWare Access
Local> DEFINE PROTOCOLS NETWARE LOADHOST “loadserv”
Local> DEFINE PROTOCOL NETWARE ENCAPSULATION SNAP
Local> DEFINE PROTOCOL NETWARE ACCESS LOCAL
Local> DEFINE PROTOCOL NETWARE ACCESS RFS2
Server Configuration TCP/IP Server Parameters
4-5
By default, the ETS will only q uery l ocal f iles erver s, but this may st ill be too many in a lar ge net work . The
Clear/Purge Protocol NetWare Access command allows you to remove items from the access list.
The Se t/Define Protocols NetWare Reset command can be use d if necessar y to force the ETS to re scan all
fileservers for pending j obs. This is useful after rebooting or after confi guring new queues on the file servers
to ensure that the ETS recognizes queues directed to it.
Keep in mind that fi leserver s cannot tell i f the ETS is not poll ing them du e to access restri ctions. Th ere will
be no error messages if a valid fileserver cannot print to the ETS due to the access list.
4.5 TCP/IP Server Parameters
If you want TCP/IP connectivity (Telnet, Rlogin, LPR, and RTEL support), you must configure IP
parameters on the ETS. First and foremost, the ETS must have a unique IP address. If this was set at boot
time (by BOOTP, DHCP, or RARP), it does not need to be reset. Other parameters are explained in this
section.
Note: An IP address is also required for EZWebCon use.
4.5.1 IP Address
To configure the ETS’s IP address, use a command of the following form.
Figure 4-10: Setting the IP address
One of the most common problems is that of duplicate IP addresses on the network. Signs of this problem
are Telnet/Rlogin connections that fail soon after connecting and ARP requests that do not find a known
host. If the server either loses its IP address when booting or will not allow a new IP address to be
configured, another hos t might be using the same address. I f any of these problems occur, doubl e check to
make sure that your ETS has a unique IP address on the network.
Note: See your Installat ion Guid e fo r more in form ation o n confi guring t he IP addres s.
4.5.2 Other TCP/IP Parameters
Users can define a names erver host if you wan t text TCP/IP host names to be resolved, a nd a default domai n
name to use in case a domain is not specified. You can also set a gateway host, which allows TCP/IP
connections to other connected network segments. Finally, you can set a loadhost (if not done already) so
that TCP/IP boots will be attempted.
Figure 4-11: Setting TCP/IP Parameters
Local> DEFINE SERVER IPADDRESS 192.0.1.228
Local> DEFINE SERVER NAMESERVER 192.0.1.29
Local> DEFINE SERVER DOMAIN “weasel.ctcorp.com”
Local> DEFINE SERVER GATEWAY 192.0.1.188
Local> DEFINE SERVER LOADHOST 192.0.1.33
TCP/IP Server Parameters Server Configuration
4-6
You can also configure a backup host in case the primary one fails.
Figure 4-12: Configuring Backup Hosts
4.5.3 Local Host Table
If your environment uses a few TCP/IP hosts regularl y, you may wish to ad d hosts to th e local host table so
that nameserving text names is not necessary (and numeric addresses do not have to be used). The Set/
Define Telnet Hosts command adds entries to the local host table.
Figure 4-13: Define Telnet Hosts Command
TCP/IP host names are ca se-independent, whet her used with the hos t table or with a names erving host.Users
who Telnet or Rlogin to host beeny will be connected to address 192.0.1.23 without needing network
nameserving support.
In addition to the Local Host table, t he ETS has a TCP/IP security tabl e that can be used to restrict incoming
or outgoing TCP/IP con nections. Manage rs can restric t connection s by address or net work on a port by port
basis. See IP Security Table on page 4-16 for more information on using the security table.
4.5.4 Host Limit
The Set/Define Server Host Limit command is used to set the number of remote TCP/IP hosts for which
the ETS will store information . In large network envir onments, thi s will keep ETS network ov erhead down.
The host limit applies only to hosts that were not explicitly set in the host table (for example, hosts seen
using rwho).
Figure 4-14: Setting a Host Limit
4.5.5 SLIP
SLIP allows hosts to establish TCP/IP connections over serial lines to the ETS, and then onto the network
attached to the ETS. The ETS will route packets among the serial and Ethernet lines transparently to the
user. This allows hosts to dial in vi a modems and run TCP/IP ses sions di rect ly to the net without having to
go through the ETS co mmand line. SLIP sess ions can be conf igured to Autostar t, or can be manual ly started
with the Set/Define SLIP command.
Although SLIP configuration involves setting specific port characteristics, it is covered in this chapter
instead of the Ports chapter due to its complexity. Configuring a serial line for SLIP access involves two
steps: the manager must enable SLIP access on the port (see the Set/Define Port SLIP command) and a
user must explicitly start a SLIP session after logging into the serial port (see Set/Define SLIP).
There are a few things to note about SLIP access:
Local> DEFINE SERVER SECONDARY NAMESERVER 192.0.1.193
Local> DEFINE SERVER SECONDARY GATEWAY 192.0.1.195
Local> DEFINE TELNET HOST beeny 192.0.1.23
Local> DEFINE SERVER HOST LIMIT NONE
Server Configuration TCP/IP Server Parameters
4-7
◆ Until the port is actively running SLIP, it can be used normally as a service port or a login port. If a
modem is attached to the port, users can connect to the port and dial out. The port changes to SLIP
interpretation only after receiving the Set SLIP command.
◆ After the SLIP session is started, the Local mode of the ETS is not reachable again until the port is
logged out, thus terminating the SLIP session. The port can be logged out via the Logout Port
command or via de-assertion of DSR on the serial line.
◆ A SLIP session’s characteristics, such as IP address and MTU, cannot be modified once SLIP is
started.
◆ Modem control has to be enabled (see Define Port Modem Control) for SLIP connections running
across a modem. Otherwise the SLIP session wil l not be terminate d even though the user might have
hung up the phone line. When modem control is enabled, the SLIP session will be terminated when
the locally-attached modem hangs up.
◆ SLIP data is “binary” in the s ense tha t any 8-bit charact er can occur in the SLIP d ata str eam. Because
of this, attached modems cannot be set to use XON/XOFF or any other cha ra cte r- bas ed fl ow control
method. If they do, the session will hang and/or lose data.
◆ All devices between the SLIP host and the ETS must pass characters unchanged, including XON/
XOFF flow control characters. Many devices can be configured turn flow control off, but will still
strip XON/XOFF characters out of the data stream. This is not acceptable.
◆ The ETS will force the serial port’s flow control to None for the duration of the SLIP session, and
will restore it when the SLIP session ends.
◆ Hardwa re flow control is unaff ected by SLIP operation.
◆ Seven-bit characters cannot be used; the SLIP session will force 8-bit mode.
◆ MTU is the size of the largest packet that can be sent unfragmented on a particular media. Packets
larger than that si ze must be fragmented in to two or more packet s and then reasse mbled by the remote
host. The MTU value and IP fragmentation can have a large effect on both the interoperability and
performance of SLIP connections.
In general, the ETS MTU for SLIP sho uld be as high as possibl e without exceedi ng the r emote host’s
MTU values. If the remote SLIP device does not support IP packet reassembly, the MTU should be
set as high as possible to prevent any fragmentation.
◆ The Ethernet MTU is 1536 bytes. The SLIP guidelines (RFC 1055) suggest an MTU of 1006 bytes
for SLIP connections. Some SLIP implementations, however, have a lower MTU. In thos e ca ses the
SLIP MTU on the ETS must be se t lo wer, which increase s IP fr agmentat ion, wh ich i n tur n decr eases
performance and can increase network traffic as more packet headers are needed for the fragmented
packets.
◆ Maximum packet size (MTU) and whether or not to pass IP broadcast packets to the SLIP lines can
be configured via the Set/Define SLIP commands.
TCP/IP Server Parameters Server Configuration
4-8
◆ The remote SLIP hosts should n ot need extr a routing c onfiguration. Th e only possi ble change ne eded
is to make the default route point to the ETS as shown below. You may also wish to configure
gateway hosts on the ETS if non-local TCP/IP sessions will be started.
Figure 4-15: Specifying Default Route
◆ SLIP connections can be restricted via the Set/Define Server SLIP Password and Set/Define
IPsecurity commands.
4.5.5.1 Configuring Necessary SLIP Parameters
No SLIP session can be st arted unti l the ETS knows t he IP address of the remote SLI P host, the MTU t o use
for the SLIP connection, and whether to forward Broadcast IP packets onto the SLIP line. Each of these
parameters can be set in one of three places: as a default for the entire server, as a default for a particular
port, or when the SLIP session is initiated. The command below specifies a server-wide default MTU.
Figure 4-16: Specifying Defaults
Defaults for a sp eci fi c port always take pre cedence over server-wi de defaults. A configur ati on that applies
to one port in particular might look like the following:
Figure 4-17: Configuration of One Port
An IP address can also be specified for a particular p ort if only on e IP address will e ver connect to th at serial
port.
Figure 4-18: Specifying an IP Address
Default entries can be for ced on ne w sessi ons so that u sers ca nnot ove rr ide one or more of the por t sett in gs
or server defaults. Options enabled in the Define SLIP Port or Define SLIP Default commands, such as
Force, will take precedence over the user’s options entered on the Set/Define SLIP command line.
If Force is enabled, the port’s options will take first precedence, then the server default settings, then the
user-entered options. If Force is disabled, the user-entered options take first precedence, then the port’s
settings, then the default set tings. For exampl e, the foll owing series of commands res ult in an MTU of 100 0
because the Force option takes precedence over the user’s request.
Figure 4-19: Forced MTU Value Taking Precedence
% su
# route add default ETSname metric
Local> DEFINE SLIP DEFAULT MTU 512 BROADCAST DISABLED
Local> DEFINE SLIP PORT 5 MTU 640 BROADCAST ENABLED
Local> DEFINE SLIP PORT 5 IPADDRESS 192.0.1.100
Local> DEFINE SLIP DEFAULT MTU 1000 FORCE ENABLED
Local> SET SLIP ADDRESS 192.0.1.20 MTU 500
Server Configuration TCP/IP Server Parameters
4-9
Conversely, the command sequence below will result in a SLIP session that uses the user’s MTU value of
500.
Figure 4-20: User’s Settings Taking Precedence
The Force option applies onl y to the IPaddress , MTU, and Broadcast opti ons. If no IP address is configured
(either as a port setting or server default) or specified by the user, the connection will fail. If no MTU is
configured or specified by the user, the connection will use the RFC value of 1006 bytes. If no Broadcast
value is configured or specified by the user, Broadcast will remain disabled.
4.5.5.2 Starting a SLIP Session
Three things are needed to start a SLIP session:
◆ SLIP must be enabled on any ports that might want to star t a SLIP session in the fut ure. Define SLIP
Port n
enables SLIP on the port automatically.
Figure 4-21: Enabling SLIP
◆ Values for the IPaddress, MTU, and Broadcast options must be set. They can be specified on the
command line or configured as server-wide or per-port defaults.
As discussed in Configuring Necessary SLIP Parameters on page 4-8, port settings and server
defaults can be forced on any SLIP session started. If Force is disabled, the user can enter desired
SLIP parameters on the command line provided the port is not dedicated to SLIP or configured for
Autostart SLIP (see below).
◆ A SLIP session must be started.The f irst command in the exampl e below is used when a de fault SLIP
address has been configured for the port. If no default address has been configured for the port, the
target IP address must be entered on the command line.
Figure 4-22: Starting a SLIP Session
After entering the Set SLIP command, the user wil l be logged out and the ETS wil l beg in tr eat ing all input
from the serial line as SLIP packets. The Local> prompt cannot be reached again unless the SLIP session
is terminated (via the Logout Port command) and the user logs back into the ETS.
If you want a partic ular port to always run S LIP, use the Autostart option, in which case i t is not necessary
for the user to enter a command to start the SLIP session.
Figure 4-23: Enabling Autostart
Local> DEFINE SLIP DEFAULT MTU 1000 FORCE DISABLED
Local> SET SLIP ADDRESS 192.0.1.20 MTU 500
Local> DEFINE PORT 5 SLIP ENABLED
Local> SET SLIP
OR
Local> SET SLIP IPADDRESS 192.0.1.50
Local> DEFINE SLIP PORT 4 MTU 1000 AUTOSTART ENABLED
TCP/IP Server Parameters Server Configuration
4-10
Port 4 will treat all serial data as SLIP packets until the Autostart option is removed and the port is logged
out. The exception to this case is if the port also has Modem Control enabled. If so, a drop in the DSR sig nal
will terminate the SLIP session, and the session will not restart until DSR is re-asserted.
A password can be configured to restrict access to SLIP sessions.
Figure 4-24: Setting SLIP Password
If a SLIP password has been set on the ETS, the server will prompt for it after the Set SLIP com mand has
been entered. If the password is not entered correctly, SLIP will not be started on that port; the user will
remain at the Local> prompt.
Ports with SLIP Auto start enabl ed wil l not have t o ent er the passwo rd—they wi ll al ways be in SLI P mode.
If you are concerned about SLIP security, disable Autostart and require that all SLIP users enter the SLIP
password before starti ng.
4.5.5.3 Tips for Increasing SLIP Performance
◆ Disable broadcasts; the extra packet traffic can be surprisingly heavy.
◆ Set the MTU as high as possib le on t he ETS and on the remote SLIP device. This lowers the ra ti o of
header information to useful data and reduces time-consuming IP fragmentation.
◆ Be sure that characters aren’t being lost or altered by any communications equipment between the
SLIP hosts. Flow control between modems is particularly troublesome.
◆ When Telnetting with SLIP, Telnet directly to the desired host, not to the ETS and then to the final
destination.
◆ Be sure that all IP hosts that send and receive packe ts over the SLIP line use UDP checksumming and
don’t blindly set the checksums to zero. Hosts that do not check UDP checksums may send and
receive corrupted packets, but may accept the corrupted data as valid. At least one major UNIX
implementation does not check or set the UDP checksum by default.
◆ See your host documentation for information on enabling UDP checksumming.
4.5.5.4 Tips for Increasing SLIP Network Security
◆ If possible, restrict the IP addresses that the user can select, either via the Force option or the IP
security tables. This will help prevent the remote SLIP host from “impersonating” a legitimate host
on your network.
◆ Be very careful with .rhosts and /etc/hosts.equiv files on UNIX machines. Improper setup of these
files may allow unauthorized users to access the host.
◆ Disable broadcasts; it is possible that the remote user can learn important information from packets
being broadcast from your network onto the SLIP line.
◆ Counters are available for each SLIP session via the Show SLIP Port command. The displays will
show both forwarded and di scarded packets for b oth dir ec ti ons of the session, and may be useful for
debugging SLIP connections.
Local> SET SERVER SLIP PASSWORD slpass
Server Configuration TCP/IP Server Parameters
4-11
◆ The display also shows counters for fragmentation, reassembly, and packets dropped due to
congestion on the SLIP line. The IP errors field shows incoming packets that were discarded due to
protocol problems inclu ding checksums errors, hea der problems, and incorrect source hosts. The ETS
will discard any packets from the SLIP session that are not from the initially-configured host.
4.5.5.5 SLIP Setup Example
Figure 4-25 shows a po ssible setup to u se SLIP with modems. The e xample shows many of th e options; your
situation may not require them all.
Figure 4-25: SLIP Setup Examp le
1
In order, these commands:
2 Allow ports 4 and 5 to run SLIP, and set th em for modem control with out fl ow c ontrol. XON/XOFF
flow control cannot be used for SLIP.
3 Set a SLIP password that must be entered by ports issuing a Set SLIP command.
4 Set the server-wide SLIP defaults to disable broadcast IP packets across SLIP sessions, and set an
MTU based on the SLIP specification.
5 Configure port 4 to autostart SLIP to one IP address. Whenever port 4’s serial connection is active
(DSR asserted), it will interpret SLIP packets. The Local> prompt will not be available in this case
until Autostart is disabled.
6 Give port 5 a diff erent MTU t han the serve r de fau lt; since no I P addres s is sp ecif ied f or po rt 5, i t wil l
have to be specified in the Set SLIP command.
7 Logout both ports so that the Define Port and SLIP commands take effect.
4.5.5.6 Modems with SLIP
If Modem Control is defined on a port set for SLIP Autostart, SLIP is handled slightly differently. In this
case, SLIP will not be started until the port sees assertion of the DSR signal, which generally occurs when
the attached local modem has formed a connection with a remote modem.
Until DSR is asserted, the port will remain idle in non-SLIP mode. It is usable as a service port in this state
until SLIP is st arted. Aft er SLIP is s tarted, t he SLIP ses sion will be clos ed if the at tached mode m device deasserts the DSR signal.
Local> DEFINE PORT 4,5 SLIP ENABLED MODEM ENABLED FLOW NONE
Local> DEFINE SERVER SLIP PASSWORD “slipag”
Local> DEFINE SLIP PORT 4 IPADDRESS 192.0.1.1 AUTOSTART ENABLED
Local> DEFINE SLIP PORT 5 MTU 512
Local> LOGOUT PORT 4
Local> LOGOUT PORT 5
Creating Services Server Configuration
4-12
4.6 Creating Services
A service is any resource that can be accessed locally or via the network. For example, a host is a service
to which terminals can connect. The ETS can offer its attached devices to the network as services.A
Lantronix service is also known as a remote pr inter name or remot e queue name on many operati ng systems.
Autobaud should not be enabled for any port that offers a service. Also, recall that a port’s access must be
set to Dynamic or Remote to allow service connections.
When you try to modify a service that already exists, the command will simply change its characteristics.
If the service does not exi st yet, the se rver assume s you want to crea te that servi ce. The ETS will only print
an error message if you try to remove a service that does not exist. Connections and queueing are enabled
by default whenever you create a service.
If you are new to set ti ng u p se rvi ces, you might want to try using the simple servic e i n Fi gur e 4-26 using a
terminal as the print device. You can then connect locally to the service and see if typed characters are
displayed on the terminal . Characte rs typ ed on the servi ce termin al should also be sent to the origi nal port .
If it seems to be working proper ly , you can try us in g a rea l pri nt devi ce and con figur e the p ort accor dingl y.
Recall that you will need to use the <Break> key or your port’s local key (see the Set/Define Port Loc al
command) to return to the command line from a service connection.
If you are new to set ti ng u p se rvi ces, you might want to try using the simple servic e i n Fi gur e 4-26 using a
terminal as the print device.
4.6.1 Creating a Simple Service (A Line Printer)
Connections, queueing, banner, and formfeed options are enabled by default when you enter a Set Service
command, so it is not necessary to configure them explicitly. NetWare, and RTEL access are provided by
default, but LAT and AppleTalk access have to be explicitly enabled. The port providing the service must
also allow remote access, so it must have access set to Dynamic or Remote.
Figure 4-26 shows the command needed to create a service called dump_port on port 2.
Figure 4-26: Set Service Command
If the device connected to port 2 is a physical print device, the port’s baud rate should be set to reflect the
highest speed at which the printer is capable o f printing. Par ity, chara cter size, an d flow contro l might have
to be adjusted to match the printer’s settings.
Enter a Show Servic es command to verify that the service was created and usable.
Figure 4-27: Show Service Command
Local> SET SERVICE dump_port PORT 2 LAT ENABLED
Local> LOGOUT PORT 2
Local> SHOW SERVICE LOCAL CHARACTERISTICS
Service: DUMP_PORT
Rating: 255
Characteristics:
Enabled Groups: 0
Ident:
Ports: 2
Queuing Banner RTEL Formfeed NetWare
LAT Connections
Server Configuration Creating Services
4-13
In Figure 4-27, the se rvi ce rating is non-zer o, i ndi cating that the servi ce is available for con nections. If the
service rating were zero, the service would not be available. This can happen if the port is not configured
for Dynamic or Remote access, if conne ctions are disa bled, or if the service/port is in use. The Show Ports
All command is useful for finding out why a service is unavailable; it shows port access modes, login
statuses, and the services currently being offered.
After setting up a service, you should be able to connect to it locally or from other protocol-compatible
nodes. To connect to service dump_port, use the following command:
Figure 4-28: Connecting to a Service
Note: Output will be dis played on port 4. If t her e is a terminal device on port 4, it will
echo keystrokes to the port.
To disconnect from the service, press the Break key to return to the Local> prompt, then type Disconnect.
Your session will be closed and the dump_port service will again be available for connections. Enter the
Show Services command to make sure.
4.6.2 Setting Up a Service With Group Codes
Local ports can be given a list of LAT service groups that they are authorized to use. The access list will
deny the ports access to services that do not belong to any matching authorized groups. For example, you
may wish to limit connections to a printer or to a certain set of ports on a server.
Figure 4-29: Service Configuration Example
In order, the commands in Figure 4-29:
◆ Enable group 1 and groups 2 through 5 on the server and assign them to any local services.
◆ Define all local ports so they can access gr oups 1 , 4, and 7. When a por t lo gs in, all of its aut hori zed
groups are usable. Since groups 1 and 4 are common to both the ports and lo cal servic es, all the loc al
ports will be able to connect to any local service.
Note: Group codes only apply to LAT connections. They have no effect on the other
protocols supported by the ETS (Apple Tal k, LAN Manage r, NetWar e, and TCP /
IP).
◆ Set up port 2 to which the printer will be connected, reset the speed to 2400 baud, and disable
broadcasts to the port. For more information on port settings, see Chapter 5.
◆ Define remote access for port 2 (since the printer will not need to log in, and set the port’s name, and
disable any Break key processing.
Local> connect dump_port
%Info: connecting to service dump_port at node...
Local> DEFINE SERVER GROUPS 1,2-5 ENABLED
Local> DEFINE PORT 2 AUTHORIZED 1,4,7 ENABLED
Local> DEFINE PORT 2 SPEED 2400 BROADCAST DISABLED
Local> DEFINE PORT 2 ACCESS REMOTE NAME “printer” BREAK DISABLED
Local> LOGOUT PORT 2
Local> SET SERVICE “printer” PORT 2 IDENTIFICATION “LocalPrint”
Local> SAVE SERVICE “printer”
Creating Services Server Configuration
4-14
◆ Log the port out so that the Define commands take effect.
◆ Create a print service on the port that allows connections and queueing by default, and enable the
server send out an identification string in network multicasts.Create a print service on port 2, and
enable the ETS to send out an identification string in network multicasts.
◆ Save the service so that it will be enabled after the next server reboot.
4.6.3 TCP/Telnet Service Sockets
The TCPport and Telnetport servi ce options allow you to con figure a TCP socket associa ted with a service.
Connections to that s ocket numb er are mapped t o the serv ice. This a llows you t o create a TCP “rotary” t hat
can apply to multiple physical ports. As long as the service rating is non-zero, TCP connections to the socket
are accepted (provided a port is available to handle the TCP connection).
The Telnetport and TCPpor t options are simi lar, with the one ex ception t hat Telne tport will perform Tel net
IAC interpretation on the data stream while TCPport treats the connection as a raw data pipe. Neither
provides for queueing—if the service is unavailable, the TCP connection is rejected.
4.6.4 Enabling Other Service Options
In addition to TCPport and Telnetport, several other service options can be enabled on a service:
Table 4-1: Service Options
Option Function
AppleTalk Enables or disables AppleTalk access to the service. Macintosh computers,
for example, will see the service name in their Choosers if they are on the
same zone/network as the ETS. Note that all AppleTalk enabled services on
the ETS are assumed to be LaserWriter printers running PostScript. There is
no way to support non-PostScript devices (such as ImageWriters and
modems).
Banner If enabled, provides a banner page before servi ce data is se nt t o the por t. The
host software may still provide its own banner page regardless of the ETS
service setting. This option should not be used with PostScript.
Binary If enabled, prevents the ETS from processing the data stream. Disabling this
feature (the default), allows the ETS to convert <LF> to <CR><LF> and possibly perform tab expans ion. Post Scrip t (below) imp lies binary mod e. Binary
should be enabled for PCL jobs.
DLC If enabled, handles NT DLC print connections.
EOJ If enabled, appends a user-configurable end-of-job string to every job.
Formfeed If enabled, appends a Formfeed to print jobs.
LANManager Enables or disables LAN Manager access to the service.
LAT Enables or disables LAT access to the service.
NetWare Enables or disables NetWare access to the service. If NetWare is not enabled
on any ETS services, the ETS will not poll the fileservers.
Server Configuration Creating Services
4-15
4.6.5 Setting Up a Modem Service
The example displayed in Figure 4-30 is rather detailed, but once you have created a service or two, the
process should become largely intuitive. Remember that the Show/Monitor/List Services commands are
available to show you exactly what has been set up s o f ar. I f you are unsure or think you may have made a
mistake, dele te the service (using Clear/Purge Service) and start from scratch. Refer to the upcoming
section for modem-specific configuration issues.
Figure 4-30: Modem Service Setup
Because many of the commands sh own are similar to the ones in the previous exa mple, only those that d iffer
will be explained:
The port is configured in much the same way as in the simple service example. XON/XOFF flow control
has been enabled for t he modem. Acce ss to the p ort is now dy namic so tha t both remot e and loca l users ca n
access the modem to dial in or out. Modem control and password protection are both enabled.
Users who dial into the modem and connect to the ETS’s serial port will have to enter the login password
due to the Define Port Password Enabled entry. This option can be omitted if not desired.
The service is set up as with the previ ous example, but a password has been ena bled for both the service and
the port. Users who connect to t he service local ly or from anoth er host on the netwo rk will have to enter the
service password (lo co) to use the servi ce to conne ct to the modem and dial out. This op tion can be omitted
if not desired.
Note: For more information on port settings, see Chapter 5.
Postscript If enabled, queries the printer (via Ctrl-D exchanges) to make sure it is ready
for a new job before starting any job. Any service supporting only a Post-
Script printer should also have this flag enabled.
PSConvert If enabled, encapsulates text sent to the service in a PostScript wrapper. This
allows text-only queues to print to PostScript devices.
RTEL Enables or disables RTEL access to the service.
SOJ If enabled, sends a user-configurable start-of-job string to the attached device
at the beginning of every access.
Local> DEFINE PORT 2 PARITY NONE FLOW XON SPEED 19200
Local> DEFINE PORT 2 BROADCAST DISABLED
Local> DEFINE PORT 2 ACCESS DYNAMIC
Local> DEFINE PORT 2 NAME “modem” BREAK DISABLED
Local> DEFINE PORT 2 MODEM ENABLED PASSWORD ENABLED
Local> LOGOUT PORT 2
Local> SET SERVICE MODEM PORT 2 IDENTIFICATION “19200 BPS Modem”
Local> SET SERVICE MODEM PASSWORD “loco”
Local> SAVE SERVICE MODEM
Table 4-1: Service Options, cont.
Option Function
Security Server Configuration
4-16
Since modems do not log the user out when a connection is finished, you will probably want to have the
Break or Local key available so you can return to the ETS command line; see Set/Define Port Local for
more information. If you wish to disconnect from the modem session, use the Disconnect or Logout
command.
If a port and modem are to be used to allow dial in connections, you may wish to make the port Secure.
Secure status prevent s d ial -i n us er s f rom ch angi ng t he p ort ch ara ct er ist i cs a nd pr eve nti ng o the r us er s f rom
being able to dial in properly.
4.7 Security
Security measures a re a vai lable to monitor users and to restrict user s f rom unwanted activity. S ecur i ty can
be implemented server-wide, or it can be configured for individual ports as desired. The following section
discusses server-wide security measures; for port security measures, see Chapter 5, Ports.
4.7.1 Controlling Incoming Sessions
The Set/Define Server Incoming command allows or denies incoming LAT or Telnet connections. It can
also require incoming users to enter the ETS login password to log in from the network. The following
commands allow LAT and Telnet users to log into the ETS without having to enter a password.
Figure 4-31: Allowing Unrestricted Incoming Connections
For security-conscious systems, the following commands can be used to only allow authenticated logins.
That is, lo gin attempts are subject to password verification.
Figure 4-32: Configuring Password for Incoming Connections
Connection Methods on page 2-15 explains in detail the mechanics of setting up incoming sessions. Note
that users loggi ng in from the ne twork are much har der to trace and monitor than those on attached ph ysical
ports.
Make sure your ETS and network environment are reasonably secure if you allow network logins. Also,
refer to Enabling Server-Wide Port Charact eristics on pa ge 4-1 for details on con figuring ports for network
logins. Note that you can c onfigure the TCP/I P security table to enable or disable network connectio ns from
certain hosts—see IP Security Table on page 4-16 for more information.
4.7.2 IP Security Table
The ETS provides an IP Security Table as a mechanism for restricting incoming and outgoing TCP/IP
sessions (including Telnet, Rlogin, SLIP, and RTEL). The security table allows the manager to enable or
disable access to and from the ETS based on port number as well as IP address. The IP security table does
not apply to print connections via RTEL.
Local> SET SERVER INCOMING BOTH
Local> SET SERVER INCOMING NOPASSWORD
Local> SET SERVER INCOMING PASSWORD
Local> SET SERVER LOGIN PASSWORD “8ball”
Server Configuration Security
4-17
Like other configurat ions, s ecuri ty tab le ent ries can be Set or Define d. To add an entry t o the t able, s pecif y
an IP address (or range), which direction(s) to restrict, and a list of affected ports.
Figure 4-33: Setting Server Access
In order, the command in Figure 4-33:
1 Affects addresses f rom 192.0. 1.1 through 192.0.1.254 us ing the 2 55 “wildcar d” networ k address seg-
ment.
2 Prevents ports 4, 5, 6, and 7 from beginning sessi ons to hosts wi th these addresses using the Out going
Disabled keywords.
The IP address must be four segments of 0-255 each. A 255 in any segment applies to all numbers in that
range such that 192.0.1.255 includes all addresses of 192.0.1.n. A trailing zero in any address is shorthand
for “all addresses in this range are disabled, for both directions and for all ports.” The following two
commands a re equal.
Figure 4-34: Set IPsecurity Command
Parameters can be added aft er the addr ess term to change th e defaults. Incoming a nd Outgoing Dis abled are
the default settings for any Set/Define IPsecurity command. Incoming refers to users on other hosts
attempting to log into the ETS. Outgoing refers to local users connecting to other TCP/IP hosts.
Port number 0 corresponds to t he virt ual por ts (tha t is, users who log int o the ETS fro m the networ k). If no
ports are specified on the command line, all ports, both physical and virtual, are included by default.
Note: SLIP is disabled by default for Set/Define IPsecurity commands.
Individual entries can be removed by entering Clear/Purge IPsecurity with no parameters other t han the
address. This command form is not valid for any addresses with zeros in any segment.
Figure 4-35: Clear IPsecurity Command
The entire security table can be cleared with one command:
Figure 4-36: Clearing Secur i ty Tabl e
Local> SET IPSECURITY 192.0.1.255 OUTGOING DISABLED PORT 4-7
Local> SET IPSECURITY 192.0.1.0
Local> SET IPSECURITY 192.0.1.255 OUT DISABLED IN DISABLED
Local> CLEAR IPSECURITY 192.1.1.102
Local> CLEAR IPSECURITY ALL
Event Logging Server Configuration
4-18
4.7.2.1 Using the Security Table
There are two basic rul es for check ing a TCP/IP connection for legali ty. First, a more specific rule take s
precedence over a less specific one. For example, if connections to 192.0.1.255. are disabled but
connections to 192.0.1.78 are enabled, a connection to 192.0.1.78 will succeed. Second, in the absence of
any rule that r estri cts a conne ction , ac cess i s allowe d. If t his b ehavio r i s not desir ed, incl ude an e ntry of the
following fo rm:
Figure 4-37: Setting IPsecurity
This is the le ast specific rul e i n the table, and will e nsure that connecti ons fail unless ot her w is e allowed by
another en try (recall that all por ts are included in the rule by default).
If no entries are defined in the table, all connection attempts will succeed. Also, if the connecting user has
privileged status, the connection will be allowed regardless of the entries in the table.
Note: Managers should try enabling and disabling certain addresses on their local
network to see what the y can and c annot do if they are unclear a s to the r ules on
the use of the security table.
4.7.3 SNMP Security
Since SNMP can be used to cha nge ETS se tt ings, a way to prevent unaut hor iz ed Se t commands is needed.
The ETS provides a security mecha nism for restr icting SNMP acce ss to the unit that is linked to the SNMP
community name used. To prevent eas y access to the allowed community names, the Show SNMP and List
SNMP commands are restricted to privileged users.
SNMP configuration requires a community name and an access type: Readonly, Both (read and write), or
None. Clearing an SNMP entry requires that you enter either a community name to remove or the All
parameter to clear the entire table. SNMP queries or Set requests that are not permitted are sent an error
reply specifying the problem. See Set/Define SNMP on page 12-98 for more information.
4.8 Event Logging
The ETS can be configured to report various events either to a serial port on the ETS or to a remote host.
The latter can be done with in the TCP/IP, LAT, or NetWare prot ocols. TCP/I P messages will be s ent to the
syslogd daemon on the host, while LAT and NetWare messages will be echoed to the console of the host/
fileserver. LAT logging requires installing the Lantronix-supplied logging program on the LAT host.
Configuring event logging requires three steps—configuring the host types, setting the host to which the
information will be reported, and configuring which class(es) of events will be logged.
Note: Classes can be individuall y enabled and disab led, and multiple cla sses of events
can be logged.
4.8.1 Configuring Host Types
Host types must be configured as follows:
Local> SET IPSECURITY 255.255.255.255 IN DISABLED OUT DISABLED
Server Configuration Event Logging
4-19
VMS Ensure that the ets$configd process is running. Ensure that the priority level
*.notice is defined in the syslog.conf file.
UNIX Set up the logging facility on the host. See the syslog man pages for more
information.
Novell Using the PCONSOLE utility, add the ETS name as a printserver.
Note: See Chapter 8 for more information on NetWare and PCONSOLE.
4.8.2 Host Name Formats
The following formats distinguish the host to which logging information is sent:
hostname:: Indicates a LAT host.
hostname: Indicates a TCP/IP host, specified as either an IP address or text host name.
hostname\ Indicates a NetWare fileserver.
CONSOLE Indicat es events should be logg ed to the ETS serial c onsole port (designa ted as
port 1).
4.8.3 Event Classes
The event classes that can be logged are:
Commands All commands issued on the ETS will be reported (verbose output).
Network All users logging in from or out to the network will be reported.
Printer Changes in printer status lines will be reported.
Security All logins and Set Privileged events are reported, as well as any password
failures.
System Booting and Initialize events are reported.
Modem All modem activity is reported, including incoming and outgoing jobs.
The following example sends login and security events to a TCP/IP host.
Figure 4-38: Set Logging Command
To clear logging, specify None in place of the host designation and event class.
Figure 4-39: None Option
To display current logging status, use the Show Logging command.
Local> SET LOGGING HOST 192.1.2.0: NETWORK ENABLED SECURITY ENABLE D
Local> SET LOGGING NONE
5-1
5: Ports
All Lantronix products have two types of ports: physical and virtual.
◆ There is one physical port for every serial or parallel connector on the ETS. Physical ports are
numbered starting with 1 . Devices c onnected t o the physical ports a re governe d by ch aracteri stics set
up for the individual ports with the Set/Define Ports commands explained in this chapter.
◆ There is one virtual port on every ETS. Referred to as port 0, it governs all incoming Telnet and
Rlogin connections (those that are not associated with a physical port). Virtual ports are configured
the same way as physical ports , the only differenc e being t hat all inc oming conn ectio ns get the same
set of port characteristics.
Note: Virtual ports are explained further in Section 5.1.3 on page 5-5.
5.1 Port Commands
Initial port c onfigurati on should be st raightfor ward; the majority of t he ports wil l probabl y be used for local
terminal connections. If so, commands in the following format should be sufficient.
Figure 5-1: Configuration Command
Most port commands require you to be the privileged user. Also, many port commands require that the
Define command be used rather than the Set command. For a comparison of the Set, Save, and Define
commands, see Command Types on page 3-4.
If you’re entering a number of commands at once, you may wish to enable the Command Completion
characteristic. When command completion is enabled, the ETS will complete partially-typed commands
when either the Space or Tab key is pressed. This can save time and reduce errors if you’re entering several
commands at a time. To enable command completion, use the following command:
Figure 5-2: Enabling Command Completion
5.1.1 Port Access
A port’s access may be set to one of the following: Dynamic, Local, Remote, or None. Dynamic permits
both local and remote logins . Loc al permits only local logins and all ows t he por t to ini ti at e conne ct ions to
services, while Remote permits only network connection requests. None prevents all incoming and
outgoing connections, rendering the port unusable. The default setting is Local access for all ports.
Local>> DEFINE PORT ALL AUTOSTART ENABLED
Local>> DEFINE PORT 2 COMMAND COMPLETION ENABLED
Port Commands Ports
5-2
Before a user can Telnet from the network to a ETS port and dial out using an attached modem, the port
must be set for dynamic or remote a ccess. To log into a port locally and Telnet t o a remote ho st, set t he port
for local or dynamic access. To configure port access, use the Define Port Access c ommand. Access must
be configured with Defi ne c omma nds s in ce t he c onf iguration is reset to th e sa ved values every time a user
logs in or connects to a service on that port.
Figure 5-3: Configuring Connection Type
If a connection to a service is failing, check the port’s access mode first.
5.1.2 Serial Configuration
5.1.2.1 Baud Rate
The ETS and attached serial device, such as a modem, must agree on a speed or baud rate to use for th e serial
connection. The default speed is 9600 baud. Other baud rates can be set with the Set/Define Port Speed
command followed by a baud rate number.
Figure 5-4: Changing the Baud Rate
The ETS also supports Autoba ud, which a ttempt s to conf igure the por t’s sp eed and p arity by an alyzing t he
first <Return> keys typed at login. To enable this feature, type the following command.
Figure 5-5: Enabling Autobaud
Autobaud will not wor k for devic es that do no t “log i n” (such as printers an d modems) and wi ll not fun ction
for baud rates l ess than 1200 or for cert ain pari ty and char acter s ize sett ings (8 -bit, no parity a nd 8-bit, even
parity are acceptable). If the attached devices will be using one speed permanently, Autobaud can remain
disabled. See the Set/Define Port Autobaud command on page 12-28.
Terminal devices that will be running at 9600 baud will not need the autobau d feature, and can ge nerally be
used with the factory-set configuration. Ports that will be used for non-terminals (for example, printers) will
probably have to be configure d separately, as will terminals that won’t work with autobaud. Other than the se
cases, terminal-dedicated ports should need no special configuration.
The ETS’s parity, character size, and stop bits should be configured as shown in the following sections.
5.1.2.2 Flow Control
Flow control enables two con nected device s to control th e amount of data trans mitted between t hem. When
flow control is enabled on a ETS por t and a conne cte d devi ce (for example, a modem), it ensures tha t da ta
sent from the sending device will not overflow the receiving device’s buffers.
The ETS supports both hardware (RTS/CTS) and software (XON/XOFF) flow control. Hardware flow
control is recommended. The two methods are described in the following sections.
Local>> DEFINE PORT 2 ACCESS DYNAMIC
Local>> DEFINE PORT 4 SPEED 2400
Local> DEFINE PORT ALL AUTOBAUD ENABLED
Ports Port Commands
5-3
Note: The ETS and the device with which it is communicating must agree on the type
of flow control used.
5.1.2.2.1 Hardware Flow Control (RTS/CTS)
When hardware flow cont rol is used, the flow of da ta is c ontrolled b y two s erial port signals (typic ally RTS
and CTS). Two connected devices will assert and de-assert RTS and CTS to indicate when they are ready
to accept data.
For example, the ETS will assert RTS when it is ready to accept data. When it can no longe r accept data (its
buffers are full) it will de-assert RTS. A connec ted device will monitor the assertion and de- assertion of this
signal and will only send data when RTS is asserted. Along the same lines, a device will assert CTS when
it is ready to accept data. When its buffers are full, it will de-assert CTS to tell the ETS to stop sending.
Note: Modem control only works with CTS/RTS flow control on the ETS8P, ETS16P,
and MSS. If you wish to use modem con trol o n other mod els, yo u must use XON/
XOFF flow control.
5.1.2.2.2 Software Flow Control (XON/XOFF)
XON/XOFF controls the flow of data by sending particular characters through the data stream. The
characters sent to signify the ability or inability to accept data are Ctrl-Q (XON) and Ctrl-S (XOFF). To
enable XON/XOFF flow control, enter the following command:
Figure 5-6: Enabling Software Flow Control
Applications that use the Ctrl-Q and Ctrl-S characters (for example, certain text editors) will conflict with
XON/XOFF flow control and there fore an alternative met hod of flow control should be used. If a user enters
a Ctrl-Q or Ctrl-S, these characters will be interpreted as flow control characters and removed from the data
stream. In addition, protocols that require an 8-bit clean data path (such as SLIP and UUCP) cannot use
XON/XOFF flow control.
Note: An 8-bit clean data path is one th at data pas ses thr ough comple tely un chan ged.
5.1.2.2.3 Setting up Flow Control
To configure flow control on a port, complete the following steps.
1 Set the Appropriate Line/Serial Speeds
Consider the line spee d and the serial speed of th e modem; if data is to be compre ssed, the serial speed
should be slightly hi gher t han the line speed. When c onnecting a terminal to the port, ensure tha t the
speed of the terminal matches the port speed.
2 Disable Autobaud
To ensure that the set speeds are always used, disable any automatic speed selection or autobaud
options on your modem. In addition, disable Autobaud on the ETS port you’re configuring. Use the
Set/Define Port Autobaud command.
Figure 5-7: Disabling Autobaud
3
Determine the Appropriate Flow Control Method
Local> DEFINE PORTS ALL FLOW CONTROL XON
Local>> DEFINE PORT 2 AUTOBAUD DISABLED
Port Commands Ports
5-4
Refer to Flow Control on page 5-2 fo r a descrip tion of the di fferent fl ow control meth ods. Choos e the
method that’s most compatible with the serial device and applications you’ll be using.
4 Configure Flow Control
Configure your serial device to use the selected method of flow control. Refer tothe device’s
documentation for instru ctions.
Configure flow control on the ETS using the Set/Define Port Flow Control command. Figure 5-8
displays an example.
Figure 5-8: Configuring RTS/CTS Flow Control
For more information about flow control command syntax, see Set/Define Port Flow Control on
page 12-39.
5.1.2.3 Parity, Character Size, and Stop Bits
The default character size of 8 data bits can be changed to 7 data bits. Similarly, the default stop bit count
of 1 bit can be changed to 2 bits. Parity is normally None, but can also be Even, Mark, Odd, or Space.
Figure 5-9: Configuring Parity, Character Size, and Stop Bits
5.1.2.4 Preferred and Dedicated Connections
A preferred servic e or host is t he default service ( Telnet o r Rlogin) or Telnet host used for a particular port.
If you enter the Connect, Telnet, or Rlogin command without specifying a service or host, you are
connected to the pr eferr ed ser vi ce or ho st. A dedica ted ser vi ce or ho st is the one a por t will al ways con nect
to when logged in. A port can also be configured for dedicated SLIP; no other protocol can be run on the
port. The following sections show how to configure preferred and dedicated connections.
When a port is dedicated, the local prompt cannot be accessed. Therefore, commands cannot be entered to
disable the dedicated characteristic. If you plan to dedicate all of the ETS’s ports, be sure that you have
another way to log into the ETS (for example, via Telnet), or else you will have to initialize the ETS to its
factory default settings.
5.1.2.4.1 Preferred Services and Hosts
To specify a preferred service, use the Set/Define Port Preferred command.
Figure 5-10: Specifying a Preferred Service
To automatically connect to the preferred service upon login, the Autoconnect characteristic must be
enabled for the service.
Figure 5-11: Enabling Autoconnect
Local>> DEFINE PORT 2 FLOW CONTROL CTS
Local>> DEFINE PORT 4 PARITY EVEN
Local>> DEFINE PORT 4 CHARSIZE 7 STOP 2
Local>> DEFINE PORT 2 PREFERRED SERVICE ets_modem
Local>> DEFINE PORT 2 AUTOCONNECT ENABLED
Ports Port Commands
5-5
To specify a preferred Telnet host, use the Set/Define Port Preferred Telnet command.
Figure 5-12: Specifying a Preferred Telnet Host
Environment strings can be added to the commands to specify additional connection information for a
preferred connection. The following example tells the ETS to use the remote host’s FTP port (port 21) for
the connection, and to use Passall mode.
Figure 5-13: Specifying Environment
Environment for LAT and TCP/ IP connections is descr ibe d in Environment Str ings o n page 2-15. The key
letters are described in Set/Define Port Preferred on page 12-46.
5.1.2.4.2 Dedicated Services and Hosts
To specify a dedicated service, use the Set/Define Port Dedicated command.
Figure 5-14: Specifying a Dedicated Service
To specify a dedicated Telnet host, use the Set/Define Port Dedicated Telnet command.
Figure 5-15: Specifying a Preferred Telnet Host
When the user logs off the service or out of the Telnet host, or when the service or host cannot be reached
for some reason, the user will be logged out of the ETS.
As with preferred connections, environment strings can be added to the commands to specify additional
connection information.
5.1.2.4.3 Dedicated SLIP
A port can be configured to automatically run SLIP when the port is started. No other protocol can run on
the port; it w ill continu e to run SLIP until it is logged out. To dedicate a port to SLIP, use the fo llowing
command:
Figure 5-16: Dedicating a Port to SLIP
5.1.3 Virtual Ports
Incoming Telnet and Rlogin connec tions are not associated wit h a physical port. Instead, they are associated
with a virtual port, port 0, which serves for the duration of the connection.
Local>> DEFINE PORT 2 PREFERRED TELNET 192.75.1.0
Local>> DEFINE PORT 5 PREFERRED “billvax” ENVIRONMENT 21+P
Local>> DEFINE PORT 2 DEDICATED lrs_modem
Local>> DEFINE PORT 3 DEDICATED TELNET 192.0.1.221
Local>> DEFINE PORT 3 SLIP DEDICATED
Modems Ports
5-6
Each virtual port is created with a default set of characteristics. The Set/Define Port commands (starting
with Define Port Access on page 12-27) can be used to customize a virtual port during the Telnet/Rlogin
session; however, thes e customizations ca nnot be saved. The port reve rts to the default se t of characteris tics
once the session is closed.
To make configuration s that apply to all virtu al ports (all future Telnet/Rlo gin connections ), use Define Po rt
commands and speci fy ze ro as the port number . Al l port settings can be conf igured for virtual ports except
those that don’t make sen se for vir tual port s, (i.e., Autobaud, Dedicat ed, Dialbac k, DSRLogout, DTRWai t,
Modem Control, and SLIP).
For example, the comma nd in Figure 5-17 ma kes all ports pr ocess the Break ke y locally rath er than passing
it on to the remote service.
Figure 5-17: Configuring Virtual Ports
Note: Virtual ports cannot be configured with Set commands, they can only be
configured with Define commands.
Because NCP and Telnet remote console sessions are considered virtual logins, configurations made with
Define Port 0 commands will apply to them as well. Virtual port settings are often used to provide local
switches to network logins, as they typically do not have a Break key to use after the connection is made.
Note: Use the List Port command to view virtual port characteristics.
5.2 Modems
Modems are usually connected to data equipment (such as terminals or servers) with a 25 pin DB-25
connector that allo ws t he equipment to see all the s ign al s the modem provides. These si gna ls include Ring
(RI), Carrier Detect (CD), and Data Set Ready (DSR).
Although modems are sometimes difficult to set up, the following points should help you connect one to
your ETS. Refer to the cable pinouts in your Installation Guide for more details as you read these
instructions. Keep in mind two things:
The special handling for modem connections is only done if the port in question has Modem Control
enabled. See the Define Port Modem Control command for details.
The way the ETS handles modem ports is rather simple and straightforward. Most modem problems are
caused by cabling mistakes or by an incorrect modem configuration.
5.2.1 Modem Basics
When Modem Control is enabled on a port, the ETS uses the DSR input signal on the serial port to decide
when there is a valid modem connection and the Data Transmit Ready (DTR) output line to signal the
modem that a connection is pos si bl e or a cce ptable. The attached modem may not be using t hese signals as
the ETS expects, however.
For a sample incoming call, the signal sequence might be:
Local>> DEFINE PORT 0 LOCAL SWITCH ^F
Ports Modems
5-7
1 The modem and ETS wait for a connection. The ETS provides DTR to the modem so that the modem
will accept any inc oming calls. The modem does not pr ovide DSR to the ETS si nce it is not co nnected
via the phone line.
2 The modem receives a call, asserts the Ring signal, and then asserts Carrier Detect (CD) to signal it
accepted the connection.
3 The ETS sees its DSR input signal go high when the modem asserts DSR and/or CD.
4 The ETS logs the port in, after which the remote caller presses Return and gets a login prompt or au-
toconnect from the ETS.
5 The user works for a while, then decides to log out and exit.
6 If the user logs of f the ETS locally, t he ETS dr ops the DTR line long eno ugh to signal the mode m to
hang up the remote connection (roughly 3 seconds).
7 If instead the remote modem hangs up before the user logs out, CD (the ETS’s DSR) is de-asserted,
and the ETS closes the local session.
For outgoing calls, the sequence might be:
1 A local user connects to the modem service. The ETS keeps DTR high for the modem and pays no
attention to incoming DSR yet.
2 The user dials out and connects to a remote service.
3 The modem now raises CD (and therefore the DSR signal on the ETS) as a sign that it is connected.
The ETS now begins monitoring the DSR line while the session progresses.
4 If the user logs out of the remote connection, the remote modem hangs up and the local modem de-
asserts DSR. The ETS then logs the user off the service and makes the service available again.
5 If the local connection i s closed (for examp le, by a Disconnect), the ETS drops DTR to signal the mo-
dem to hang up the remote end and closes the session.
5.2.2 Modem Wiring
There are two fundamental wiring issues to address: Data Terminal Ready (DTR), and Data Set Ready
(DSR). Both issues, along with Carrier Detect (CD), are discussed in this section.
The ETS normally asserts DTR. When Modem Control is enable d, the ETS will drop DTR for three seconds
each time the port is logged out and each time a network user disconnects from a modem service. The
modem must be configured to hang u p and r ecycle when DTR is dropped. Security prob lems may result if
the modem is not configured in this way.
The ETS must know when a connection is lost so it can log out the port and close any sessions. Otherwise
security problems will res ult when the next user logs into the por t. The ETS also needs to know when a valid
connection does not exist so it can ignore spurious characters from the modem. Otherwise the ETS may
interpret the characters from the modem as a user logging in, causing the port to be unavailable.
Modems Ports
5-8
5.2.2.1 DSR (Data Set Ready) for Automatic Logouts
An ETS port can be configured to automatically log itself out when DSR is no longer asserted; in other
words, the port log s out whe n the mode m is dis connec ted. Thi s can he lp ens ure por t sec urity becaus e user s
are prevented from unplugging terminal lines and using sessions that are still active.
5.2.2.2 DSR for Controlling Remote Logins
The DSR signal can also be used to determine whether or not a remote login to a port will be permitted.
DSRlogout can be used to automatically log a port out when the DSR signal is deasserted. See DSRlogout
on page 5-16 for more information.
The Signal Check charact eris tic r equir es the asser tion of the DSR s ignal before a remot e login is perm itte d
on a particular port . Signal Check is genera lly e nabled fo r use with prin ters; if the pr inter do esn’t asser t the
DSR signal, it’s assumed to be disconnected or powered off. In this case, the remote login isn’t permitted,
and print jobs are not sent from the ETS to the pr inter. See Preventing Access Unt il DSR Is Asserted on page
5-15 for more information.
5.2.2.3 DCD (Data Carrier Detect)
The DCD signal is asserted by the local modem when it detects a connection from a remote modem. If
you’re using a DB25 port, no wiring is required in order to use the DCD signal.
RJ45 ports have one pin that can be used for either DSR or DCD. If you are using modems, this pin must
be wired to the modem’s DCD pin. If you are using another type of device (such as a terminal or printer),
this pin should be wired to t he device’s DSR pin. Refer to the Pin outs appendix of your Installation Guide
for instructions.
5.2.2.4 DTR (Data Terminal Ready)
The ETS asserts DTR when it is ready t o accept inc oming data or connections. It also use s DTR to cycle the
modem when modem control is enabled by temporarily dropping the signal.
ETS ports can be configured to assert DTR only when a user logs into the port by enabling the DTRWait
characteristic. See DTRwait on page 5-12 for more information.
5.2.3 Baud Rates
The ETS and modem must a gree on the baud r ate used for the serial interfac e. However, the modem at tached
to the ETS may be communi cating with the remote modem at a di fferent speed due to the use of c ompression
and error correction techniques. The ETS and modem can be configured in one of three basic ways:
1 Set the baud rate of the ETS and the mode m to the highest expected rat e, disable autobaud on the ETS
and on the modem, and use flow control to handle connections at all slower rates.
On some modems disabling Autobaud is known as “locking the serial speed” or “locking the DTE
speed.” This method allows nonstandard transmission rates such as those found in V.32bis (14,400
baud), error correction, and data compression. This method is generally the most reliable as the
modem and the ETS always use the same baud rate.
Ports Modems
5-9
Ports that support V.32bis should be set to 19200 baud. Also, ports that use compression should be
set one or two speeds higher than the modem’s speed. For example, a port supporting a 2400 baud
modem with compression should be set to 4800 or 9600 baud.
2 Use the autobaud feature of the ETS; the ETS will adjust its speed to that of the modem.
Flow control isn’t strictly requir ed in this configur ation. Applications that cannot use f low control due
to limitations listed in the Parity, Character Size, and Stop Bits section on page 5-4 may still func tion
correctly, but if at all possible, flow control is still recommended.
Nonstandard transmiss ion rates such as V.32bis (14,400 baud), error correc tion, and data compression
cannot be supported with this method. During a long data transfer, eventually either the ETS or the
modem will run out of buffer space and overflow the other, resulting in data loss.
3 If only one standard baud rate is to be suppo rted, se t the ETS to that rate and disab le autoba ud. Flo w
control may be disabled, subject to the same caveats discussed above.
5.2.4 Modem Configuration
In dialout situat ions, it is po ssible for users to r econfigure the modem with no rmal “at” co mmands. It is a lso
possible for a user to misconfigure a modem such that it will be unavailable, unusable, or cause security
problems. Fortunately, many modems can reload their saved configuration each time DTR is dropped by
the ETS. The modem will always be configured correctly after each use provided the user doesn’t modify
the saved settings.
5.2.5 Modem Result Codes
If the modem is configured to return result codes or status messages, the ETS and the modem may start to
“babble.” A message from the mode m will be int er pre te d as a use r l oggi ng into the ETS, and the ETS will
send a prompt to the modem. The modem will inter pret this prompt as a command and send an error message
to the ETS. This process causes the por t and modem to become unavail able, and can be cleared te mporarily
by logging the port out.
The best solution to this potential problem is to configure the mo dem so that it never returns result codes.
Unfortunately, the lack of status messages may make outgoing connections inconvenient. If the modem
supports displaying messages only during outbound connections, babbling can usually be avoided.
5.2.6 Modems with SLIP
If Modem Control is defined on a port set for SLIP autostart, SLIP is handled slightly differently. In this
case, SLIP does not start until the port sees assertion of the DSR signal, which generally occurs when the
attached local modem has formed a connection with a remote modem.
Until DSR is asserted , the po rt re mains i dle ( in non- SLIP mode) . It c an be u sed as a s ervic e port until SLIP
is started. After SLIP is started, the SLIP session closes if the attached modem device de-asserts the DSR
signal. For more information on SLIP configuration, see SLIP on page 4-6.
Modems Ports
5-10
5.2.7 Modem Configuration Checklist
These items should be verified after any modem configuration. Note that some options might not be
provided on the modem in question.
◆ The modem must disconnect immediately when DTR is dropped.
◆ The modem must assert CD (or DSR, if connected) when connec ted to an other mode m and must not
assert CD when disconnected. The modem may optionally assert CD during outbound dialing.
◆ The modem and ETS must agree on the flow control method and baud rate scheme.
◆ The modem must not send result codes or messages to the ETS except optionally during outgoing
calls.
◆ Configuration information should be saved in non-volatile memory (NVRAM) so that it will be
retained du ring power outages.
◆ The modem should restore its configuration from non-volatile memory when DTR is dropped.
◆ The modem should be configured to answer the phone if incoming connections are to be supported.
Generally this is done with the ats0=1 command.
◆ The modem should not answer the phone unless DTR is asserted by the ETS.
These items should also be verified after any ETS port configuration:
◆ Modem Control must be enabled . Using modems on po rt s with out Modem Co ntrol enabl ed will l ead
to security problems. See the Define Port Modem Control command on page 12-43 for synta x and
details
◆ Baud, parity, and flow control settings should be verified with the modem setup.
◆ Autobaud should only be enabled if required.
5.2.8 Testing the Modem Configuration
The example tests in this section assume that the modem is attached to port 4 and the modem and ETS
checklists have been followed.
Dial into the ETS and issue the Test Port command. A regular cascading pattern should be printed. If
characters are lost after a few dozen lines, there is a flow control problem.
On another port, issu e the Logout Port 4 comman d. The modem sho uld immediat ely hang up and be r eady
for the next call i n a f ew se conds. If not, the modem is ignoring DTR, or there is a wiri ng problem. Repeat
this procedure with all expected modem speeds and options.
Dial into the ETS, connect to a network host, and log in. Hang up the remote modem without logging out
of the ETS. After the ETS’s modem hangs up, issue the Show Port 4 co mmand f rom anot her p ort. Th e po rt
should be in the Idle state.
Ports Other Port Characteristics
5-11
Dial into the ETS a gain. The port s hould hav e been r eset, a nd should no lon ger be connected to the netwo rk
host. If not, the modem is incorrectly asserting DSR/CD, or there is a wiring problem.
If outbound calls are to be suppor ted, connec t to the modem’ s service with the Conn ect command. In many
cases the Connect Local command is a quick shortcut: dial a remote modem. After the modem connects,
log into the remote system.
In some configurations, it may not be possible to see the dial commands or the modem’s status messages.
If a modem fails to pick up the phone, DTR may not be wired correctly, or the modem may be configured
to ignore incoming calls. If modems fail to connect to each other, there could be a modem compatibility
problem. For example one modem’s configuration might require a special feature such as error correction
to complete connections. Verify both modem configurations, or try swapping one or both modems with
different models or different brands.
5.3 Other Port Characteristics
5.3.1 Dialback
Dialback allows a system manager to set up a dialback list of authorized users for incoming modem
connections. When a username matching one in the list is entered, the port will be logged out and the user
will be called back at the predefined number.
The Dialback syste m may be u sed for s ecuri ty purpose s as we ll, but does not a bsolutel y guara ntee sec urity.
See Dialback Security on page 5-16 for more information.
5.3.2 Dialup
It is frequent ly us eful (or ess entia l) f or a LAT host to know whet her a c onnect ion at tempt is coming from a
modem or not. The LAT host will inquire about modem status when any connect is made, but you can
explicitly inform the host about modem status with the Dialup flag. When Dialup is enabled on a port, the
port will report that it is used for a dial-in modem if the LAT host asks. If you have any ports that will be
used exclusively for modem access, define this parameter.
Note: The Dialup characteri stic has no effect on non-LAT connect ions (Telne t, Rlogin,
and so on).
Some services or nodes may reject a connection because of its Dialup status due to the inherent security
concerns with modem connections. While this may seem like an annoyance, it is a security feature and
should be implemented if possible via the Dialup flag.
Figure 5-18: Setting the Dialup Flag
Local>> DEFINE PORT 4 DIALUP ENABLED
Other Port Characteristics Ports
5-12
5.3.3 Device Type
The Type characteristi c specifi es the devi ce types compa tible wit h a part icular por t. Type can be one of the
following: ANSI, Hardcopy, or Softcopy. To set a type, use the following command:
Figure 5-19: Configuring the Device Type
The command above specifies th at the port is compatible wit h VT100-type devices. For fu rther explanation,
see Set/Define Port Type on page 12-54.
5.3.4 DTRwait
The DTRwait flag governs whether a port provides DTR when idle. [[[Normally DTR is always asserted.
In general, this allows modems to answer an incoming call, as many mode ms wil l not ans wer a cal l unless
DTR is asserted.]]] If you enable DTRWait, t he ETS will de assert DTR unt il the po rt recei ves a connec tion
request. When such a connection begi ns, the ETS will assert DTR; when the conn ection is closed, DTR will
be de-asserted.
Figure 5-20: Enabling Dtrwait
5.3.5 Group Numbers
Each port can be given one or more authorized LAT group numbers. By default, only group zero is
authorized, which restricts a port ’s ac ces s to only those n odes t hat offer services i n g rou p zero. The ETS is
also configured for group zero, so by default, all ports can access any services local to this ETS. To allow
port access to specific groups, enter the Set/Define Port Authorized Gr oups command.
Figure 5-21: Defining Port Authorized Group
For information on server-wide enabling of LAT groups, see Set/Define Server Service Groups on page
12-80.
5.3.6 Interrupts
When a port is being used for a net work connection, the port will be busy; in ot her words, local user s cannot
use the port at that time. To permit local logins when a network connection is running, the port must have
dynamic access configured and the Interrupts characteristic must be enabled.
Figure 5-22: Enabling Interrupts
Local> SET PORT 3 TYPE ANSI
Local> SET PORT 2 DTRWAIT ENABLED
Local>> DEFINE PORT 2 AUTHORIZED GROUPS 0,77,122-178
Local>> DEFINE PORT 2 ACCESS DYNAMIC
Local>> DEFINE PORT 2 INTERRUPTS ENABLED
Ports Other Port Characteristics
5-13
5.3.7 Port Messages
Various degrees of “verb osity ” are ava ilabl e for po rts re ceivi ng ETS message s. Message s from ot her user s
on the ETS can be enabled or disabled wit h the Broadcast flag. If the serial line connec ting a terminal to the
ETS is an unsure connection, setting Loss Notification will cause an audible beep if a character is lost.
Finally, Verification wi ll allow or prohibit the prin ting of informational messages as session connec tions
are started, exited, or switched.
These parameters are all e nabl ed by default. If you would l i ke to disable them (for exa m ple , if you wish to
decrease packet traffic), enter the following commands:
Figure 5-23: Disabling Port Messages
5.3.8 Port Names
The default name for each port is Port_n, where n denotes the port number. To assign a new name to a p ort,
use the Set/Define Port Name command.
Figure 5-24: Assigning Port Name
A default username can also be specif ied fo r a p ort usi ng the Set/Define Port Username command. When
the username is specified with the this command, users will not be prompted for a username upon login.
Figure 5-25 displays an example.
Figure 5-25: Specifying a Username
5.3.9 Terminal Type
Termtype informati on is used for outg oing Telne t and Rlogin sess ions. For exam ple, it can be used to te ll a
remote host how to configur e your t ermina l to ru n a part icula r appli cati on. The te rmtype s hould be enter ed
as a string, as shown in the command below:
Figure 5-26: Configuring the Terminal Type
No terminal type is specified by default.
DEFINE PORT 3 BROADCAST DISABLED
DEFINE PORT 3 LOSS NOTIFICATION DISABLED
DEFINE PORT 3 VERIFICATION DISABLED
Local>> DEFINE PORT 3 NAME “highspeed_modem”
Local>> DEFINE PORT 2 USERNAME “fred”
Local> SET PORT 3 TERMTYPE VT100
Security Ports
5-14
5.4 Security
Between the various password protections on the ETS and the access control provided by service groups,
security should n ot be a problem; a lmost any acce ss restricti on can be enfo rced. For port s that need a higher
level of security, the Set/Define Port Security command allows the ETS manager to restrict a port user’s
actions on the ETS. Ports set this way are called secure ports. If a port is set secure, it cannot see or affect
other ports on the system, nor can it use the Set Privileged comman d. The secure option is useful for te rminal
connections that need to be restricted but still have access to the command line.
Due to the sequence of security checks (see Table 5-1), multiple security features can be enabled on any
port. For example, a port can be configured to requ ire a login password, ent er a dialback username, and then
be placed in menu mode.
5.4.1 Password Restrictions
Users can be required t o enter the ETS l ogin pa ssword be fore t hey ar e allo wed t o connec t to spe cific po rts.
By default, incoming Telnet and Rlogin connections are not required to enter the login password. To
configure the ETS to require the login password, enter the Set/Define Port Password command.
Figure 5-27: Requiring the Login Password
5.4.2 Menu Mode
Ports that don’t need (or due to secur ity concer ns, should not hav e) access t o the ETS command line can be
put into menu mode. In menu mode, users are given a preset menu of up to 36 commands to choose from
when they log in, but are not given automatic access to the command line. Individual ports are configured
for menu mode with the Set/Define Port Menu command. The commands that users see i n the menu system
are configured via the Set/Define Menu command.
Table 5-1: Security Checks
Server Area to Check Determines
Access is set to None User cannot obtain any prompt or log in.
Port password is enabled User must enter login password.
Port Dedicated is enabled Port is forcibly autoconnected; user cannot access
command line.
Port Dialback is enabled Username must be an authorized name; reconnect
attempt must succeed.
Port Security is enabled Command set is restricted.
Port Menu is enabled Port is forced into menu command mode.
Local>> DEFINE PORT 2 PASSWORD ENABLED
Ports Security
5-15
Each Set Menu command takes three parameters: an entry number to d etermine its place in the menu, an
option name that the user will see in th at command slot, and the command string that will be executed if the
user selects that entry. For example, the command displayed in Figure 5-28 will put an entry in menu
position five.
Figure 5-28: Set Menu Command
Menu users will see the str ing Show net work TCP hosts; if they sel ect thi s entry, the command S how Hosts
will be executed for them.
The Exit command can be assigned to on e of the menu slots to return user s to the command line. The Logout
command can be added to log the user out and reset the port. Typing Ctrl-D or Ctrl-Z at the menu prompt
will also log out a menu mode user.
Menu commands ar e subject to the curr ent user ’s priv ilege l evel. Enab ling S ecurity on the port may restri ct
the user from selecting some of the menu entries.
5.4.3 Locking a Port
The Lock command may be used to secure a port without disconnecting sessions. When Lock is entered,
the user will be prompte d to enter a pass word. The port will then be lock ed until thi s password is us ed again
to unlock it. Figure 5-29 displays an example.
Figure 5-29: Locking and Unlocking a Port
For information on enabling t he ETS Lock feature, see Enabling Server -Wide Port Characte ristics on page
4-1.
To unlock a port without the Lock pas sword, a pri vileged us er must use the Unlo ck Port command, or log
out the port using the Logout command. Logout will disco nnect all sessions. Unlo ck Port and Log out are
discussed in the Command Reference.
5.4.4 Preventing Access Until DSR Is Asserted
The Signal Check charac teristic can be used t o prevent re mote connecti ons to a port unless DSR is asserted.
This is often used to prevent Telnet logins to a port until the device attached to the port (for example, a
terminal) asserts the DSR signal, indicating that it is connected and powered on.
Figure 5-30: Enabling Signal Check
Local> SET MENU 5 “Show net TCP hosts” “SHOW HOSTS”
Local> LOCK
Password> donut (not echoed)
Verification> donut (not echoed)
Unlock password> donut (not echoed)
Local>
Local>> DEFINE PORT 3 SIGNAL CHECK ENABLED
Security Ports
5-16
5.4.5 Automatic Logouts
Ports can be configured to log out automatically when the DSR signal is dropped to prevent users from
accessing other sessions by switching physical terminal lines. Ports can also be configured to log out
automatically or when they’ve been inactive for a specified period of time.
5.4.5.1 DSRlogout
When a device connected to the ETS is disconnected or powered off, the DSR signal is dropped. To
configure a port to log out when this happens, use the Set/Define Port DSRlogout command.
Figure 5-31: Enabling Dsrlogout
Normally, DSR must be enabled on a port for it to automatically log out when the device it is attached to is
turned off or disconnected. When DSRlogout is enabled, the ETS will log out the port’s user if either of
these cases occurs to prevent unauthorized users from unplugging physical terminal cables and gaining
access through other users’ still-active sessions.
DSRlogout is also useful with incoming modems. When the modem hangs up, it will log the user out and
thus force the host to prompt subsequent users to log in. For this reason, Modem Control implicitly enables
DSRlogout (although it will not show up as enabled), as well as other features. DSRlogout does not
implicitly enable Modem Control, however. DSRlogout and Modem Control are mutually exclusive
features; the same physical serial line signals are used for both features.
5.4.5.2 Inactivity Logout
To configure a port to log out after a specified period of inactivity, use the Set/Define Port Inactivity
Logout command. This command works in conjunction with the Set/Define Server Inactivity Timer
command, which defines an inactivity limit as a particular number of minutes. After the timer period has
elapsed, a port with Inactivity Logout enabled will be considered inactive and automatically logged out.
Figure 5-32: Enabling Inactivity Logout
5.4.6 Dialback Security
Depending upon the modem an d its confi guratio n, it may be po ssible fo r a determi ned attacke r to penetr ate
the system. There are two windows of vulnerabi lity where an attacker coul d gain unauthorized access to the
ETS: the first exists after the ETS hangs up the modem but before the modem dials the user back, and the
second exists after a dialback attempt fails but before the ETS reaches the end of its 80-second timeout
period. Careful confi gur ati on a nd testing of the system duri ng t hese short vulnerable peri ods is req uir ed t o
ensure a hig h level of se curity.
To minimize potential security problems when using Dialback, configure your modem carefully. The
modem should not answer the line unt il the second or third rin g, and never unti l the DTR signal is a sserted.
The modem should also be configured to dial only after detecting a dial tone, and hang up otherwise.
Local>> DEFINE PORT 1 DSRLOGOUT ENABLED
Local>> DEFINE PORT 1 INACTIVITY LOGOUT ENABLED
Local>> DEFINE SERVER INACTIVITY TIMER 500
Ports Security
5-17
If the Dialback c all should fail for any other r eason before the 80 -second timeout ( for example, if the number
dialed is busy), a s econd c alle r may be a ble to log in to th e ETS. This possi bilit y can be vi rtual ly e limina ted
by two steps:
1 In the Dialback strin g itself, is sue a command to ign ore incomin g calls. An example of this command
is ats0=0dt555-1234.
2 Re-enable incoming cal l answering a fter the DTR sign al is droppe d (that is, after the dia lback sessio n
has ended). To accomplish this, the modem should be configured to reload its normal configuration
each time DTR is dropped.
When dialback is used, the ETS will ver ify the identity of incomin g users by logging the port out and di aling
the user back at a specified number. Dialback may be configured to
1 Permit connections without dialback,
2 Log out a port and call the user back,
3 Terminate the connection when unauthorized users attempt to connect,
4 Any combina tion of the firs t three.
To use dialback for character logins, you must configure a list of authorized users. First enable Modem
Control using the Define Port Modem Control Enabled command. Then enable dialback using the Set/
Define Port Dialback Enabled command.
Figure 5-33: Define Dialback Enabled
Local>> DEFINE PORT 3 DIALBACK ENABLED
6-1
6: Using the ETS
A connection to a servi ce or host i s called a se ssion on t hat host. One of the most u seful fe atures of the ETS
is that it allows you to have multiple sessions on different hosts, and gives you easy access to all of them.
Active sessions can include LAT, Telnet, or Rlogin connections, or any combination of the three.
This chapter explains int er ac ti ve se ssi ons on the ETS. After reading this chapter, you should know how to
log into the ETS, confi gure the ETS for sess ion activity, form conne ctions to service s, and manipulate activ e
sessions. In addition, you will be able to view and interpret various ETS status displays.
6.1 Logging In and Out
6.1.1 Logging In
Each port on the ETS can support an interactive user or other device such as a printer. If you are using the
ETS from a terminal, you will generall y log into t he ETS freque ntly. Use t he followi ng steps to log into t he
ETS:
1 Press the Return key on your t er minal u nti l th e ETS re sponds. If you s ee gar bled c har acte rs or get n o
response after four or five returns, check cable connections and the terminal’s baud rate, parity, and
character size settings. Both the terminal and the ETS port must agree on these settings. If the ETS
manager has enabled passwor d protection you wi ll see the words
Login Password>. Type the login
password and press the Return key.
2 If this port has no permanent username associated with it, the ETS will respond with Username>.
You can enter up to 16 characters as a username, or type Ctrl-Z to use the port name as your user
name.
The ETS will respond in one of three ways:
◆ If you see the Local_x> prompt, where x is your port number, you ar e now in the ETS’s Loca l mode.
When in Local mode, you can enter only t he ETS commands for which you are priv ileged. Type Help
if you need information about the ETS’s command set.
◆ If you receive a menu screen, you ar e i n menu mo de, an d you can only enter the commands list ed i n
the menu screen.
◆ If the ETS logs you out and attempts to reconnect, your port is in dialback mode and the ETS is
attempting to verify your username and connection location.
6.1.2 Logging Out
When you’re through using the ETS, type Logout at the Local> pr ompt. You can also type ei ther Ctrl- D or
Ctrl-Z at the local prompt t o log out. If you have connected se ssions, they will be closed before you log out.
The ETS will then await another login.
Configuring Your Port Using the ETS
6-2
You may remain logged into the ETS (with or without active sessions) perpetually, with a few possible
exceptions.
◆ If you leave connected sessions for long periods of time, a host may log you out. Many hosts are set
to log off users af te r a set period of i nact ivity; this will not af fect your login to t he ETS, but you will
have to log in to the remote h ost again.
◆ The ETS supports an inactivity logout ti mer of it s own. If the ETS manag er has enabl ed this fe at ure,
you will be logged out of the ETS after a preset period of inactivity, usually ranging from 15 to 120
minutes.
◆ If the DSRLogout option is enabled , you may be l ogged out aut omatically whe never your t erminal i s
turned off or your connection is disrupted.
6.2 Configuring Your Port
6.2.1 Unsecure Port Commands
A variety of options can be set to customize your port. Refer to the Command Reference chapter for a full
description of the following Set Port and Define Port command options:
◆ Autoconnect and Preferred Services cause your port to try to connect to any configured Preferred
service as soon as you log in.
◆ Autoprompt determines whether a login prompt is sent back immediately when your port connects
to a LAT service. No Autoprompt means that you will have to pr ess Return to obtain the login prompt.
Telnet and Rlogin sessions always return a login prompt upon connection.
◆ Groups controls which of the port’s Authorized Groups are enabled. Authorized Groups are set by
the ETS mana ger.
◆ Loss Notification causes your te rmin al t o beep i f cha rac ters are dropped on the connection wit h the
ETS.
◆ Username sets up a default username for your port. Note that if you configure a username, you will
not be prompted for it at login time.
◆ Verification enables status messages when you connect, disconnect, or switch sessions.
◆ Newline Character controls whether a carriage return, line feed, or both are sent as the newline
character.
6.2.1.1 Privileged Port Commands
There are several Set Port options that the manager (or privileged user) can set. These usually are used
when configuring the por t for the first time, and are rarely changed.
◆ Access controls whether the port is a ccessible to l ocal equipment (Local), remote users such as a local
printer or dial-ou t modem (Re mo te) , or both (Dynamic). Dynamic access is used for dial-in/d ial -out
modems, or for devices such as teletypes that can be used both interactively and as print devices.
Using the ETS Connecting to Services
6-3
◆ Authorized Groups configures all the service groups the port can possibly use. Use the Set/Define
Port Authorized Groups command to specify which of the Aut hor i zed g roups are actually enable d.
◆ Autobaud lets the ET S attempt to automatically set the port’s speed and parity based on the first
characters typed at login (they must be Returns). Aut obaud works if the port is at lea st 1200 baud and
is using eight bit characters, or seven bit characters with even parity.
◆ Autostart forces the ETS to log it self in immediate ly upon bootin g rathe r than wait f or the input of a
carriage return. I f modem contro l is enabled , the co nnection will be establ ished when the DSR signal
is asserted. If there is a dedicat ed host or service, the ETSwill connect to it ; if not, it wil l dis pla y the
Local> prompt.
Note: Autostart should remain disabled (the default) if network connections are
desired.
◆ Dedicated sets up the por t so that it can onl y c onnect to one specifi c ser vi ce and nothing else . When
a user logs in on t he por t, he wil l be connec te d to the s ervic e; when he logs ou t of the r emote servi ce,
he will be logged out of the ETS.
◆ Name sets the port’s name for identification purposes (not to be confused with the username, which
identifies who is using the port).
◆ Password, governs whether the ETS password is required for logins.
◆ Security controls whether the port can execute restricted commands.
◆ Session Limit sets the maximum nu mber of ope n sessi ons the p ort can have at a g iven time . The port
session limit must be less than or equal to the ETS’s session limit.
6.3 Connecting to Services
After configuring and usin g the ETS in Local mode, you wil l pr obably want to connect to remote hosts. A
remote host is any host bey ond your ETS, whether it is in an oth er country or in the same office as you are.
In addition to conne ctin g to r emote ho sts, y ou can a ccess the ETS fr om withi n your UNIX or VMS s essio n
using LAT, Telnet, or Rlogin. This means that you can remotely connect to the ETS to access its services
just as if you had logged in locally. You can also access remote printers that are not directly connected to
your system. The following section explains how to make these connections.
6.3.1 Connecting to LAT Services
To connect to a LAT service, use the Connect command and give the service name, for example:
Figure 6-1: Connecting to a LAT Service
This will connect you with the highest rated service named Harvey on the network (see the discussion of
ratings in the Concepts chapter for more information about ratings).
Local> CONNECT HARVEY
Connecting to Services Using the ETS
6-4
You can also force a con nection to an explicit ho st and specify exactly which po rt (i f applicable) to use on
that host. This may be necessary because more than one host on a local network can provide a s ervice. For
example, the following command will at tempt to connect to the prin ter service on a specific port of host
vax8.
Figure 6-2: Connecting to a Specific Host
This may or may not be possible, and you will be told if the ETS cannot locate or connect to the specified
service.
If your ETS has been configured to allow incoming logins (see Set/Define Server Incoming on page 12-
68), the ETS will show up as a servi ce on the n etwork. You can then connect to t he ETS from an other LATbased ETS. After connecti ng to the ETS, yo u will see e ither the ETS Loc al> prompt o r a prompt fo r a login
password. You can then use the ETS as if you had logged in to the host direct ly. To exit the ETS and return
to your local session, type
logout or Ctrl-Z.
Keep in mind that many LAT-supporting terminals and hosts do not have provisions for a Break key that
can be used by the ETS. If you plan to connect to a remote host from the ETS and will need to return to
Local mode, be sure to set a Local Switch character (see Break on page 6-7).
Once the ETS has been defined a s a service by yo ur system manager, yo u can connect to i t from a VMS host
using one of the following VMS commands.
Figure 6-3: Connecting From a VMS Host
In the example above, LTAnnnn is a LAT application port that your system manager has assigned for the
ETS service.
6.3.2 Connecting to Telnet Hosts
To connect to Telnet hosts, type either of the following commands:
Figure 6-4: Connecting to a Telnet Host
In both cases, you can use a “text” host name (such as labsun) or the numeric IP address of the host (such
as 192.0.1.88). See the IP Addresses and Name Resolution sections of the Concepts chapter for more
information on using text host names.
Local> CONNECT PRINTER NODE vax8 DESTINATION port_5
$ set host/lat ETSname
OR
$ Kermit
Kermit-32> set line LTAnnnn
Kermit-32> connect
Local> CONNECT TELNET LABSUN
Local> TELNET LABSUN
Using the ETS Connecting to Services
6-5
If necessary, you c an specify a login to an explici t port on the re mote host by adding : xxxx to the e nd of the
hostname or IP address. For example, the following command attempts a Telnet connection to TCP port
2005 on the specified host, rather than the default Telnet port.
Figure 6-5: Specifying a Port Number
On some Telnet connections, padding of Newline characters may be a problem. By default, the ETS will
pad newlines with a Null character (ASCII 0x0) as part of the Telnet specification. Two commands are
provided to overri de this default: Set/Define Port Telnet Pad and Set Session Newline. Set Port Telnet Pad
controls whether a null character is sent after the newlines in an interactive session; Set Session controls
which character is actually sent as the newline character (usually a carriage return).
6.3.3 Connecting to Local Ports
Users can connect to local ETS ports. This is useful, for example, when configuring the unit from a serial
port. To connect to a local p ort fr om an ETS login , use t he Conne ct Lo cal command at the Local> prompt.
Figure 6-6: Connecting Locally
The connection will be made to the specified port provided that the port is available. Once the connection
is established, commands may be issued to the device attached to the serial port (such as a modem or
printer).
6.3.4 Connecting to Remote Hosts Via Rlogin
If Rlogin connections are enabled on both the ETS and the remote UNIX or VMS hosts, you can use the
Rlogin command to connect fr om the ETS to t hese hos ts. Beca use Rlog in can by pass th e nor mal pass word/
login sequence, it is a potential security problem and might not be enabled. The format of the Rlogin
command is identical to the Telnet command.
Figure 6-7: Rlogin Command
If Rlogin is enabled, your ETS username is used for the remote login. If the username is unknown or is
password protected, you will still be prompted for a login password on the UNIX host. If password
protection is turned off for the username entered, you will be logged in normally.
You can optionally specify a username to be used instead of the current one for your port.
Figure 6-8: Specifying an Alternate Username
Local> TELNET 192.0.1.90:2005
Local> CONNECT LOCAL port_2
Local> CONNECT RLOGIN HARVEY
Local> RLOGIN HARVEY
Local> RLOGIN HARVEY ROBERT
Default Services Using the ETS
6-6
6.3.5 Connecting to the Server from UNIX Hosts
If incoming TCP/IP logins are enabled (again, see the Set/Define Server Incoming command), users can
log into the ETS from anot her UNIX host. They can also use Rlogi n to connect to a LAT or TCP/ IP servic e
offered by the ETS. To log int o t he ETS us ing Tel net , typ e ei th er of the following commands at th e UNIX
prompt where IP_address is the address of the ETS and etsname is the name of your ETS.
Figure 6-9: Logging in Using Telnet
The previous example as sumes your sys tem manager has set up t he host’s /etc /hosts fil e to include t he ETS.
After you enter the command, you wil l be connected t o the ETS and will either see the ETS Local> pro mpt,
see the ETS menu (if menu mode is configur ed), or be prompted fo r a login password. You can then use the
ETS as if you had logged in direct ly t o the ma chi ne. Typ e
logout or Ctrl-D to exit the ETS and retur n to
your UNIX session.
You can use Rlogin instead of Telnet to connect to remote services that the ETS can see. The following
command should be used for a normal login:
Figure 6-10: Rlogin Command
The command displayed below will attempt a connection through the ETS to service etsname. The service
can be local to the ETS or on another host on the network. Either a LAT or a Telnet service can be used;
LAT will be tried first.
Figure 6-11: Connecting to a Service
6.4 Default Services
You can set a default service to be used for connections rather than having to specify the remote host or
service in the Connect command. This is useful if you usually use one host or service regularly. You can
specify this default service using the Set/Define Port Preferred command.
Figure 6-12: Define Port Preferred Command
The example above defi nes vax8 a s the serv ice to which the con necti on attempt wi ll be made when ever the
basic Connect command is entered. For a Telnet service, the command might look like the following
example.
Figure 6-13: Set Port Preferred Command
% telnet etsname
% telnet IP_address
% rlogin etsname
% rlogin etsname -l serv_name
Local> DEFINE PORT PREFERRED vax8
Local> DEFINE PORT PREFERRED TELNET vax8.divc.mgmt.com
Using the ETS Session Management
6-7
You can specify Telnet services as either text names or numeric IP addresses. TCP/IP hosts on a network
are unique across the network, so there is no need to differentiate Telnet nodes with the Node and
Destination parameters.
A default Telnet service is different from a default LAT service. If you have only a default Telnet service
set up but type Connect, you will get an error because there is no default LAT host set up (the ETS will
attempt a connection to a LAT host first, but will not find one).
6.5 Session Management
While in Local mode, you can switch to a differ ent sessi on, list which sessi ons you have open, change your
port characterist ics, and more. To list your act ive sessio ns, enter the Show Sessions c ommand. You will se e
the type of connection, the host name, and any Node or Destination information. The current service will
be labeled. You can use the Set Session command to change the characteristics of your connections, and
other commands to manipulate sessions.
6.5.1 Break
It is necessary to have a way to leave an active session and return to the ETS Local> prompt. This is
accomplished w ith the Break key. Pressing it will return the ETS to Local mode, leaving any sessions
connected.
In Local mode, users can issue ETS commands to perform various ETS functions. If your terminal device
has no Break key, you can configure a local switch key with the Set/Define Port Local command. You can
also enter the Set/Define Port Break command to change where the Break key is ac tually process ed: by the
ETS, the remote host, or neither. By default, the ETS handles the Break key and does not pass it to the
remote service.
Not all keyboard Break key s functio n alike; s ome dedicat ed keyboard Break keys wil l not be r ecognized a s
such by the ETS.
The ETS Break setting only affects Break s comin g i nto a port, it does not affect network or Connect Local
attempts to send a Break out of the port.
6.5.2 Backwards and Forwards
You can think of all of the user’s open sessions as a list from the first created to the most recently created.
The Backwards and Forwards commands, entered in Local mode, move users backwards and forwards
through sessions. Backwards refers to a session started earlier, and Forwards refers to a more recent
session. The sessi on list is ci rc ular, so go ing for ward fr om th e most r ecent s essio n ta kes you t o the e arli est,
and going backward from the first session resumes the most recent session.
6.5.3 Backward and Forward Switch Keys
As with the Break key, Backwards and Forwards can be bound to specific keys (see the Set/Define Port
Backward and Set/Define Port Forward commands), so long as the spe cified keys are no t typed in normal
use. The switch keys are interpreted by the ETS and the current session is changed appropriately.
Local Server Commands Using the ETS
6-8
Pressing the Backward or Forward switch key is identical to going back to Local mode and typing the
command explicitly. However, the switch keys also function in Local mode—if you press the defined
Forward key from the loca l prompt, i t is the same a s typing For wards as a command. Unlike t he Break ke y,
Forwards and Backwards are not assigned to any particular key by default. They must be explicitly
configured.
At this point, an example may help to clarify working with sessions. Suppose user Bob connects to host
Irvine. He works for a while, then presses the Break key to return to Local mode and forms a new
connection to host Dayton. He works some more, then he decides to break and connect to host Sanfran.
If he presses Break and types
Show Sessions, his session list will look like this:
◆ Irvine
◆ Dayton
◆ Sanfran (where Sanfran is the current session)
If Bob presses his Backward key or enter s the Backward command, he will resume the sessio n on Dayton.
Pressing it again put s him in the Irvine ses sion. Pressing t he Forward key twice from the Irvine sess ion will
move him forward in the list to the Dayton session and then to the Sanfran session. Pressing the Forward
Key once more from Sanfran moves him to the other end of the list, to Irvine.
6.5.4 Disconnect and Resume
Two other useful sessi on manage ment commands ar e Disconnec t a nd Resume. The Disconn ect co mmand
terminates the curre nt sessi on, a specif ied session, o r all of yo ur sessio ns. In our ex ample above, Bob could
type Disconnect 1 to terminate the Irvine session.
From the local prompt, Resume returns you to a specified session or the current session. If you do not
specify a valid ses si on number, Resume will put you ba ck in the last active s es sion. In our example above,
Bob could type Resume 2 to go back to Dayton.
6.6 Local Server Commands
Each local port can use the following Local mode commands: Broadcast, Lock, Logout, and Test Port.
6.6.1 Broadcast
When the Broadcast feature is enabled by your system manager, you can use the Broadcast command to
send messages to other users on your ETS by specifying either a port number or a username. If a user is
specified, the message will go the user with that name. If there are multiple users with the same name, the
message will go to t he one with the lowest port number. Typical broadcast commands are s hown in Figure
6-14.
Figure 6-14: Broadcast Comm and Exam pl es
Note: The message must be enclosed in quotation marks.
Local> BROADCAST 8 “Host Vax5 is down - use vax9”
Local> BROADCAST Bob “This server will reboot in 5 minutes”
Using the ETS Status Displays
6-9
If you do not want t o receiv e broadcas t mess ages, you c an enter Set Port Bro adcast Di sabled t o refuse them
on your own port.
6.6.2 Lock
The Lock command can be used to disable access to your port without actually logging out. If you Lock
your port, you will be asked for a password and a verification of the password; the latter is used to ensure
that you typed the password correctly. Once a port is locked, it is unusable until the password is again
entered or until your ETS manager unlocks the port (which is useful when you forget the password). Like
Broadcast, locking can be disabled server-wide by the manager.
6.6.3 Logout
Obviously, Logout logs out the current port. Any connections to session or services will be disconnected.
6.6.4 Test Port
This command may be used to verify wiring and flow control setup problems with your serial port. The
command sends an identical stream of characters to the terminal, either continuously or for a specified
number of lines. If your connection is regularly dropping characters, you may be able to identify the
problem.
Note: If multisessions are enabled on a port, only that port can issue a Test Port for
itself.
6.7 Status Displays
Three sets of commands can be used to view ETS status displays. The Show commands show the current
availability of hosts and services as well as the state of the ETS, its ports, and the local services. Monitor
commands provide a continuous dis play ra ther th an a one-t ime look. Lis t commands are provide d to show
the current setup in permanent memory (that is, the settings that will take effect after the next reboot or
logout).
The List command is a special case, as some displays make no sense to list. Sessions and Users, for
example, have no meaning in the per manent con figur ation da ta. List Nodes als o has no meani ng, as it on ly
refers to the remote nodes.
Note: Additional keywords app ly to some command s; see th e Command Ref erence for
full syntax.
Netstat Shows currently active UDP/TCP/IP and LAT sessions.
Show Dialback Shows the currently configured dialback strings, if any.
Status Displays Using the ETS
6-10
Show Hosts Displays the TCP/IP hosts known to the ETS. These are hosts that were
resolved with a connec t attempt, seen with rwho broadcasts, or explicit ly added
to the host table with th e Set/Define Telnet Hosts command.
The Host, Node, and Service displays allow you to use “wildc ards” in place of
host names. Wildcards are characters that can be substituted for a single
character or a series of characters.
Show IPsecurity Shows any restricti on on incoming or outgoing TCP/IP s essions and the ports
to which those restrictions apply.
Show Logging Shows the device to wh ich logging information is di re ct ed for output, such as
a console or a specific host.
Show Menu Shows the currently configured menu strings, if any.
Show Nodes Shows the LAT nodes on the network offering services, and their LAT
protocol version. The Status sub-option shows hardware addresses and any
services offered by the node.
Show Ports Shows the current setup of your port. Settings such as flow control, parity,
default preferred hosts, and username are shown, as well as enabled settings
such as Broadcast, Lock, and Messages. The display will also show printer
status: either on-line and ready to accept jobs, or in a non-ready state such as
ACK, Busy, or Error.
Show Protocols Shows an overall view of the networ k protocol counters, unles s a parameter is
added to the command. Specifying one of the following protocols shows
detailed information on that protocol: AppleTalk, LAN Manager, LAT,
NetWare, or TCP/IP. Users can also display which protocols are currently
enabled using the Enabled ke yword. In addition, us ers can request infor mation
on Counters and Queues.
Show Queue Shows the jobs currently waiting in the ETS’s print queue(s).
Show Server Shows the state of the ETS, incl udi ng ha rdwa re and software addresses, LAT
timers, session and queue limits, and so on. There are also available counters
(network events) , status (a ctive use rs, ports, a nd services ), and boot (reloadin g
information) displays.
Show Services Shows the loca l and re m ote services that are availabl e to you r port, subject to
any group restri ctions that are in place (that is, you cannot see ser vices that you
are not eligible to connect to). Using the Local option instead of a s ervice name
shows only the services provided by this ETS.
The Characteristics opti on displays more detailed inform ation on the servi ce,
such as its rating and groups. The Status option shows availability as well as
the offering node.
Show Sessions Displays you r active sessions (if any) . The command di splays the ho st/serv ice
you are connected to as well as the session number and type of connection.
Loading...