Cyclades ts20br

Cyclades-TS
Installation Manual
Cyclades Corporation
Cyclades-TS Installation Manual
Version 2.0br – June 2001
Copyright (C) Cyclades Corporation, 2001
We believe the information in this manual is accurate and reliable. However, we assume no responsibility,
financial or otherwise, for any consequences of the use of this product or Installation Manual.
This manual is published by Cyclades Corporation, which reserves the right to make improvements or changes
in the products described in this manual as well as to revise this publication at any time and without notice to any
person of such revision or change.
All brand and product names mentioned in this publication are trademarks or registered trademarks of their
respective holders.
FCC Warning Statement:

The Cyclades-TS has been tested and found to comply with the limits for Class A digital devices, pursuant to
Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate
radio frequency energy and, if not installed and used in accordance with the Installation Manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause
harmful interference in which case the user is required to correct the problem at his or her own expense.
Table of Contents
CAPÍTULO 1 - O QUE VOCÊ PRECISA SABER ANTES DE USAR O PRODUTO ........................................ 5
Contrato de Licenciamento de Software .......................................................................................................... 5
How To Use This Manual ................................................................................................................................... 6
Seja um Usuário Registrado.............................................................................................................................. 7
Garantia Lifetime ................................................................................................................................................ 8
CHAPTER 2 WHAT IS IN THE BOX ................................................................................................................. 11
CHAPTER 3 SUMMARY OF THE CONFIGURATION PROCESS.................................................................. 15
CHAPTER 4 CONFIGURATION ....................................................................................................................... 17
CHAPTER 5 UPGRADES AND TROUBLESHOOTING .................................................................................. 36
Upgrades ......................................................................................................................................................... 36
Troubleshooting ............................................................................................................................................... 36
Hardware Test .................................................................................................................................................. 38
Single User Mode ............................................................................................................................................ 40
APPENDIX A INFORMATION FOR USERS NOT FAMILIAR WITH LINUX .................................................. 42
Users and Passwords...................................................................................................................................... 42
Linux File Structure .......................................................................................................................................... 42
Basic File Manipulation Commands ................................................................................................................ 43
The vi Editor ..................................................................................................................................................... 44
The Routing Table............................................................................................................................................ 45
ssh - The Secure Shell Session ...................................................................................................................... 46
The Process Table .......................................................................................................................................... 48
APPENDIX B HARDWARE SPECIFICATIONS .............................................................................................. 49
APPENDIX C SAMPLE PSLAVE.CONF FILES........................................................................................... .... 52
CONSOLE ACCESS SERVER CONFIGURATION FILE ............................................................................. 52
TERMINAL ACCESS SERVER CONFIGURATION FILE ............................................................................ 57
REMOTE ACCESS SERVER CONFIGURATION FILE ............................................................................... 61
COMPLETE CONFIGURATION FILE SHOWING ALL PARAMETERS ...................................................... 66
APPENDIX D CUSTOMIZATION ...................................................................................................................... 82
CAPÍTULO 1 - O QUE VOCÊ PRECISA SABER ANTES DE USAR O PRODUTO

As partes deste capítulo escritas em português foram adicionadas pela Cyclades Brasil. O restante do capítulo
e do manual é do manual publicado pela Cyclades Corporation nos EUA.
Contrato de Licenciamento de Software

Este é um contrato legal entre o usuário final e a Cyclades Brasil, CGC 59.904.466/0001-64 e I.E.
206.069.209.110. Ao utilizar o produto, V.Sa. está concordando irrestritamente com os termos deste contrato.
Caso V.Sa. não concorde com os termos aqui descritos, devolva-o imediatamente a CYCLADES BRASIL para
que possa ser ressarcido prontamente.
1. OBJETIVO DO CONTRATO
Sujeito aos termos e condições estabelecidos neste contrato, o USUÁRIO poderá utilizar o software instalado
no Cyclades-PR2000, suas atualizações disponibilizadas através da Internet e toda a documentação que o
acompanha, somente na consecução de suas atividades comerciais internas.
2. TITULARIDADE
O Software pertence à CYCLADES BRASIL. O Software é protegido pela legislação de direitos autorais da
República Federativa do Brasil e por tratados internacionais. O Software deve ser tratado como qualquer outro
material protegido pelo direito autoral (como por exemplo, um livro ou gravação musical). É vedada a
reprodução dos materiais escritos que seguem anexo ao software sem autorização plena e escrita da
CYCLADES BRASIL.
3. DO USO RESTRITO
É vedado o empréstimo, aluguel, licenciamento ou arrendamento do Software e materiais escritos. Todavia,
poderá cedê-lo em caráter definitivo, desde que o USUÁRIO não retenha nenhuma cópia do mesmo e que o
adquirinte concorde em sujeitar-se aos termos deste Contrato. É vedada a engenharia reversa, bem como
descompilação ou decomposição do Software.
4. GARANTIA LIMITADA - 90 DIAS
Capítulo 1 - O Que Você Precisa Saber 5

A CYCLADES BRASIL garante ao USUÁRIO por um período de 90 (noventa) dias, a contar da data de
emissão da nota fiscal, que o Software estará adequadamente gravado no produto e em condições de operar
conforme descrito na documentação que o acompanha. A CYCLADES BRASIL também garante que o
Software estará de acordo com as especificações funcionais descritas nos manuais técnicos. Na hipótese do
Software estar desconforme com a garantia ora oferecida, a CYCLADES BRASIL, a seu único critério, poderá
consertar, substituir ou reembolsar o preço da compra do Software mediante devolução deste e do Hardware
que o acompanha, desde que se aplique.
5. PRAZO
Este Contrato permanecerá em vigor até sua rescisão mediante aviso prévio ao USUÁRIO, salvo se o mesmo
vier a descumprir qualquer disposição deste Contrato, quando a CYCLADES BRASIL poderá, a seu exclusivo
critério e sem necessidade de notificação prévia, rescindi-lo. Após a rescisão, V.Sa. deverá destruir o Software
e todas as suas cópias ou partes do mesmo.
6. FORO
Fica eleito desde já, com exclusão de qualquer outro, o foro central da cidade de Barueri, estado de São
Paulo, para dirimir toda e qualquer dúvida ou pendência oriunda deste Contrato.
How To Use This Manual

This manual assumes that the reader understands networking basics and is familiar with the terms and
concepts used in Local and Wide Area Networking. The Cyclades-TS is a Linux-based terminal server, which
gives it great flexibility. It runs an embedded version of the Linux operating system and Unix and Linux users
will find the configuration process very familiar. On the other hand, users not familiar with Unix will have a
steeper learning curve, but it is not necessary to be a Unix expert.
Configuration of the equipment is done by editing a few plain-text files (commented sample files for the principal
profiles are provided in appendix C), and then updating the versions of the files in the Cyclades-TS. The files
can be edited in the Cyclades-TS using the vi editor provided, or in another computer with the environment and
text editor of your choice. Unix user or not, we strongly recommend that you follow the steps in this installation
manual before jumping in.
This manual should be read in the order written, with exceptions given in the text.
Chapter 2 - What is in the Box - explains how the Cyclades-TS should be connected and what each cable is
used for.
Chapter 3 - Summary of the Configuration Process - provides a brief roadmap of the Cyclades-TS
configuration
Chapter 4 - Configuration - describes the basic configuration process to get the Cyclades-TS up and running
for the most common uses.
Chapter 5 - Troubleshooting - provides solutions and test procedures for typical problems.
Appendix A - Linux Information - Information for those who are new to Linux/Unix.
Appendix B - Hardware Specifications - Pinout diagrams for cables.
Appendix C - Pslave.conf Sample Files - Example files for 3 profiles and the master file.
Appendix D - Customization - Instructions for those who wish to create their own applications.
Seja um Usuário Registrado

Com o objetivo de atender às expectativas dos clientes e de melhorar sempre a qualidade de nossos produtos
e serviços, gostaríamos de receber suas críticas e sugestões através do preenchimento do Registro on-line,
localizado em nosso Web site (http://www.cyclades.com.br, área “suporte técnico”). Ser um cliente registrado
Cyclades significa ter acesso aos seguintes serviços:
• Suporte Técnico Gratuito

• Upgrades de Software
• Garantia Lifetime
Importante: A Cyclades se reserva o direito de não oferecer suporte técnico e atualizações de

software, além de limitar a garantia para apenas um ano a clientes não cadastrados.
Garantia Lifetime
O Que é Garantia Lifetime Cyclades?
É uma política de garantia para os produtos Cyclades que significa garantia por toda a vida do produto contra
defeitos de fabricação ou defeitos não causados por agressões do ambiente onde o produto está instalado,
desde que todas as recomendações e especificações constantes dos manuais Cyclades tenham sido
observadas.
Como Obter a Garantia Lifetime

Para que um produto Cyclades possa ter a Garantia Lifetime Cyclades, o cliente deve preencher, no Web site
da Cyclades Brasil, o formulário de Usuário Registrado. Caso o cliente não possua acesso à Internet, deverá
contatar a Cyclades para que o registro seja feito por telefone/fax. Sem este procedimento, o período da
garantia estará limitada a um ano, contado da data de emissão da nota fiscal que acompanha o produto.
O Que a Garantia Lifetime Cyclades Cobre

Software: A Garantia Lifetime Cyclades cobre atualizações e upgrades de software (inclusão de novas
funções pela troca de versão de software), aperfeiçoando o produto e beneficiando o usuário.
Hardware: A Garantia Lifetime Cyclades cobre falhas do produto decorrentes de defeito de fabricação, ou não
causadas por agressões ao produto, impostos pelo ambiente onde o produto está instalado.
O Que a Garantia Lifetime Cyclades Não Cobre

1. Efeitos causados por agressões ao produto, impostos pelo ambiente onde o produto está instalado, ou por
falha em seguir todas as recomendações e especificações constantes dos manuais Cyclades. Portanto
não estão cobertos pela Garantia Lifetime Cyclades:
• Os componentes e/ou a própria placa quando danificados pela queima de canais seriais, e a
respectiva mão de obra para conserto.
• A fonte de alimentação, após 90 dias da data de compra.
• Os componentes e/ou a própria placa quando danificados pela queima da interface com o bus do
micro onde uma placa multisserial foi instalada, e a respectiva mão de obra para conserto.
NOTA: Tipicamente estes danos são causados por:

a.erro na instalação da placa,
b. descargas elétricas nas linhas de comunicação (raios),
c. conexão de outro produto ao da Cyclades sem que estes estejam desligados no instante da conexão,
d. conexão a outros equipamentos não adequados,
e. sobretensões causadas pelo aterramento inadequado das instalações elétricas e/ou erros de
instalação elétrica.
2. Abuso, displicência ou imperícia no transporte, armazenagem, instalação ou uso do produto.
3. Produtos que tenham sido alterados e/ou reparados pelo cliente sem a autorização por escrito da
Cyclades; produtos cujo número de série da Cyclades Brasil tenha sido removido, ou que não tenham
sido vendidos pela Cyclades Brasil ou representante autorizado.
4. Qualquer perda ou dano resultante do uso ou da incapacidade de usar o produto, nem o custo de reparar
ou substituir qualquer outro bem que seja danificado, nem lucros cessantes quando este produto não
funcionar adequadamente.
Suporte Técnico Gratuito

Após efetuar o registro, tire todas as sua dúvidas de instalação, configuração e gerenciamento com os
profissionais do Suporte Técnico da Cyclades, gratuitamente via telefone ou e-mail. Ligue para (11) 5033-
3366 de segunda a sexta, das 8:30 às 17:30 horas ou mande e-mail para suporte@cyclades.com.br. Você
será atendido por analistas treinados para sanar sua dúvida em relação ao hardware, software, instalação e
configuração do produto adquirido.
Caso seu produto, adquirido há menos de 30 dias, apresente problemas no funcionamento, entre em contato
com o Suporte Técnico. Eles irão avaliar a necessidade da troca do produto por outro produto novo, caso haja
problema de fabricação.
Como Entrar em Contato com a Assisência Técnica

Se houver um problema relacionado ao hardware que o Suporte Técnico não consiga resolver, envie o produto
para Cyclades com uma Nota Fiscal de remessa para conserto.

Caso seja um caso urgente, entre em contato primeiro com a Assistência Técnica da Cyclades no telefone
(11) 5033-3311. Na nota fiscal, coloque os seguintes dados:
Razão Social: Net Conectividade Ltda.
Endereço: Av. Santa Catarina, 155 - Aeroporto
São Paulo - SP 04635-000
CGC: 59.904.466/0002-45
I.E.: 112.350.633.116
CFO = 5.99 Remessa para conserto (se for do estado de São Paulo)
CFO = 6.99 Remessa para conserto (fora de S. Paulo)
Se sua empresa não for emitente de nota fiscal, envie junto com o produto uma carta fiscal incluindo seu
nome, R.G., endereço, telefone para contato declarando o motivo pelo qual você está enviando o produto para
a Cyclades, assinando-a em seguida.
O Que é o Cyclades Premium Partner (CPP)?

O CPP é uma revenda Cyclades que está capacitada a configurar, vender e dar suporte técnico dos produtos
Cyclades, localmente nas regiões em que atuam. Os funcionários de um CPP recebem um treinamento inicial
com duração de 3 dias sobre os produtos e tecnologia Cyclades e são continuamente reciclados técnica e
comercialmente nos novos produtos e serviços Cyclades.
O suporte técnico da Cyclades é composto de dois níveis. O primeiro é um suporte técnico telefônico (ou por
e-mail) gratuito fornecido pela própria Cyclades e o segundo é um suporte técnico local (on-site) fornecido pelo
CPP. Este segundo suporte não é gratuito.
Veja a relação dos CPPs cadastrados no Web site da Cyclades Brasil (www.cyclades.com.br). Na área de
“Revendas”, clique no sub-menu “CPPs”.

CHAPTER 2 WHAT IS IN THE BOX

The Cyclades-TS is a line of console access and terminal servers. There are several models with differing
numbers of serial ports. The following figures show the main units and accessories included in each package
and how cables should be connected. The loop-back connector is provided for convenience in case
hardware tests are necessary.
Cyclades-TS2000
Back View
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 90-240VAC
Ethernet
10/100Base-T Console
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
On/Off Wall Outlet

Switch
Cross Cable Power Cable
(Same as
Console Cable) Console Cable
Modem
Cable Connect to a
Connect to COM Serial Port
a DTE Device
Connect to a modem or
to a null-modem adaptor
//////////
Installation Manual Loop-Back Mounting Kit

Connector
FIGURE 2.1 CYCLADES-TS2000 AND CABLES

Chapter 2 - What is in the Box 11
Cyclades-TS1000
Back View
90-240VAC
CYCLADES TS1000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Ethernet
10/100Base-T Console
On/Off Wall Outlet

Switch
Cross Cable Power Cable
(Same as
Console Cable) Console Cable
Modem
Cable Connect to a
Connect to COM Serial Port
a DTE Device
//////////
Installation Manual Loop-Back Mounting Kit

Connector

Back View Cyclades-TS800

On/Off Ethernet Console
On/Off
DC IN
1
0
Switch
Power Cable
Modem
Cable Console Cable
To Wall Outlet
Cross Cable
(Same as Console Cable)
Connect to a DTE Device
//////////
Installation Manual Loop-Back

Connector

Back View Cyclades-TS400

On/Off Ethernet Console
On/Off
DC IN
1
0
Switch
Power Cable
Modem Console Cable

Cable
To Wall Outlet
Cross Cable
(Same as Console Cable)
Connect to a DTE Device
//////////
Loop-Back
Installation Manual Connector

CHAPTER 3 SUMMARY OF THE CONFIGURATION PROCESS

The Cyclades-TS can be used as a:
• console access server,

• terminal server,
• remote access server.
A detailed description of each of these profiles is provided in the next chapter. The Cyclades-TS’s operating
system is embedded Linux. Even if you are a Unix user and find the tools and files familiar, do not configure this
product as you would configure a regular Linux server.
You do not need to be a Unix user to configure the Cyclades-TS. Additional information about the files and tools
needed for configuration is provided in appendix A.
The basic configuration steps are:
A.Connecting the Cyclades-TS to the network and other devices. Consult Chapter 2, What is in the Box, for
questions on which cable should be used for which device.
B.Connect a PC or terminal to the Cyclades-TS via the console port and login.
C.Modify the Linux files

/etc/hostname
/etc/hosts
/etc/resolv.conf
/etc/network/st_routes
to let the Cyclades-TS know about its local environment
D.Edit the pslave.conf file. This is the main configuration file that concentrates most product parameters and
defines the functionality of the Cyclades-TS. The modifications made to this file will depend on the profile.
Chapter 3 - Summary of the Configuration Process 15

E.Activate the changes.
F. Test the configuration to make sure the ports have been set up properly.
G.Save the changes and restart the server application.
Full details on each step listed above and how to perform them are provided in the next chapter. Make sure to
always complete ALL the steps for your application before testing or switching to another profile.
Chapter 3 - Summary of the Configuration Process 16

CHAPTER 4 CONFIGURATION
This chapter guides you step by step through the configuration of the Cyclades-TS for the three principal
applications:
1. Console Server,
2. Terminal Server, and
3. Remote Access Server.
Many steps are common to both, so please read the entire chapter before beginning.
STEP ONE
Connect a PC or terminal to the Cyclades-TS using the console cable. If using a PC, HyperTerminal can be
used in the Windows operating system or Kermit in the Unix operating system. The terminal parameters should
be set as follows:
• Serial Speed: 9600 bps
• Data Length: 8 bits
• Parity: None
• Stop Bits: 1 stop bit
• Flow Control: Hardware flow control or none
• Ansi emulation (Note: if your terminal does not have ansi emulation, select vt100; then, on the TS, log in as
root and switch to vt100 by typing “TERM=vt100;export TERM”)
When the Cyclades-TS boots properly, a login banner will appear.
Log in as root (there is no password). A password should be created as soon as possible. The Cyclades-TS
runs Linux, a Unix-like operating system, and those familiar with the Unix operating system will feel quite at
home. A description of the Linux file system and basic commands is given in the Linux appendix at the end of
this manual.
Chapter 4 Configuration 17
STEP TWO
A console server application is shown in Figure 4.1. It will be used in this step to demonstrate the configuration
of variables common to all applications.
Radius Authentication Server,

Syslog Server, Name Server
IP Address: 200.200.200.2
Internet Workstation
TS1000 Ethernet Interface
IP Address: 200.200.200.1 Cyclades-PR1000
Ethernet Interface:
200.200.200.5
TS1000
Socket
Port 7008
Socket
192.168.1.108 Workstation
Socket Port 7001
Port 7002 192.168.1.101
192.168.1.102
Serial Connections
Speed: 9.6 K
FIGURE 4.1 CONSOLE SERVER APPLICATION

This application allows a user to access a server connected to the Cyclades-TS through its COM port from a
workstation on the LAN or WAN. A server console is opened on the workstation. The authentication is usually
performed by a Radius server and either telnet or ssh (a secure shell session) can be used. See the Linux
appendix for more infomation about ssh.
Four Linux files must be modified to identify the TS1000 and its neighbors. The operating system provides the vi
editor, which is described in the Linux appendix for the uninitiated. The first file is /etc/hostname. The only entry
should be the hostname of the Cyclades-TS. An example is shown in Figure 4.2.
TS1000
FIGURE 4.2 CONTENTS OF THE /ETC/HOSTNAME FILE

The second file is /etc/hosts. It should contain the IP address for the Ethernet interface and the same
hostname entered in the /etc/hostname file. It may also contain IP addresses and host names for other hosts
in the network.
200.200.200.1 TS1000
200.200.200.2 RadiusServer
127.0.0.1 localhost
FIGURE 4.3 CONTENTS OF THE /ETC/HOSTS FILE
The third file that must be modified is /etc/resolv.conf. It must contain the domain name and nameserver information
for the network.
domain mycompany.com
nameserver 200.200.200.2
FIGURE 4.4 CONTENTS OF THE /ETC/RESOLV.CONF FILE

The fourth file defines static routes and is called /etc/network/st_routes. In the console server example in
Figure 4.1, the PR1000 is the gateway router and thus its IP address is configured in this file to be the default
gateway. Other static routes are also configured in this file.
route add default gw 200.200.200.5
FIGURE 4.5 CONTENTS OF THE /ETC/NETWORK/ST_ROUTES FILE
STEP THREE
This is where the configuration for the three profiles - Console Server, Terminal Server and Remote Access
Server diverge. Follow step three for the appropriate profile.
STEP THREE - CONSOLE SERVER

The fifth file is specific to the Cyclades-TS and a sample file with comments is supplied in the Linux file system. It
is called /etc/portslave/pslave.conf. A listing of the pslave.conf file with all possible parameters, as well as the
files used to create the three applications in this chapter, is provided in Appendix C. There are three basic types
of parameters: conf.* parameters are global or apply to the Ethernet interface; all.* parameters are used to set
default parameters for all ports, and s#.* parameters change the default port parameters for individual ports. An
all.* parameter can be overriden by a s#.* parameter appearing later in the pslave.conf file (or vice-versa). A brief
description of each parameter used for the console server profile is given in Figures 4.6-4.7.
Parameter Description Value for
This Example
conf.eth_ip The IP address of the Ethernet interface. This parameter, along with the 200.200.200.1
next two, is used by the cy_ras program to OVERWRITE the file
/etc/network/ifcfg_eth0 as soon as the command "signal_ras HUP" is
executed. The file /etc/network/ifcfg_eth0 should not be edited by the user
unless the cy_ras application is not going to be used.
conf.eth_mask The mask for the Ethernet network. 255.255.255.0
conf.eth_mtu The Maximum Transmission Unit size, which determines whether or not 1500
packets should be broken up.
conf.syslog The IP address of a remote syslog daemon can be provided here, if 200.200.200.2
desired.
conf.facility This value (0-7) is sent to the syslog server (the TS is a syslog client) to 7
indicate in which file the syslog messages should be stored. The file
/etc/syslog.conf on the syslog server contains a mapping between facility
numbers and server log files.
FIGURE 4.6 CONSOLE SERVER PSLAVE.CONF GLOBAL PARAMETERS

This Example
all.syslog_level This variable determines which syslog messages will be sent to the 4
syslog server configured in the conf.syslog parameter. A value of 0
suppresses all but emergency messages while values between 1 and 7
send progressively more types of messages for each increment. This
value (as for all "all." parameters) can later be overridden for
individual ports using the s<port number>.syslog_level parameter.
all.console_level This variable determines which syslog messages will be sent to the 4
Cyclades-TS console connected through the console interface. See the
previous parameter for a description of possible values
all.speed The speed for all ports. 9600
all.datasize The data size for all ports. 8
all.stopbits The number of stop bits for all ports 1
all.parity The parity for all ports. none
all.authtype There are several authentication type options: local (authentication is radius
performed using the /etc/passwd file), radius (authentication is performed
using a Radius authentication server), none, local/radius (authentication
is performed locally first, switching to Radius if unsuccessful), and
radius/local (the opposite of the previous option). Note that this
parameter controls the authentication required by the Cyclades-TS. The
authentication required by the device to which the user is connecting is
controlled separately.
all.authhost1 This address indicates the location of the Radius authentication server 200.200.200.2
and is only necessary if this option is chosen in the previous parameter.
A second Radius authentication server can be configured with the
parameter all.authhost2.
all.accthost1 This address indicates the location of the Radius accounting server, 200.200.200.2
which can be used to track how long users are connected after being
authorized by the authentication server. Its use is optional.
FIGURE 4.7 CONSOLE SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS

This Example
all.radtimeout This is the timeout (in seconds) for a radius authentication query. The 3
first server (authhost1) is tried three times, and then the second (if
configured) is contacted. If the second also fails to respond, the first is
contacted again, repeating the cycle up to 10 times.
all.secret This is the shared secret necessary for communication between the cyclades
Cyclades-TS and the Radius servers.
all.ipno This is the default IP address of the Cyclades-TS's serial ports. The 192.168.1.101+
"+" indicates that the first port should be addressed as 192.168.1.101
and the following ports should have consecutive values. Any host can
access a port using its IP address as long as a path to the address
exists in the host's routing table.
all.issue This text determines the format of \r\n\ TSLINUX - Portslave Internet Services\n\
the login banner that is issued when \r\n\ Welcome to terminal server %h port S%p \n\
a connection is made to the \r\n\ Customer Support: 510-770-9727
Cyclades-TS. \n represents a new www.cyclades.com/\n\
line and \r represents a carriage \r\n
return.
all.prompt This text defines the format of the login prompt. Expansion characters, %h login:
listed in Appendix C, can be used here.
all.term This parameter defines the terminal type assumed when performing vt100
rlogin or telnet to other hosts.
all.flow This sets the flow control to hardware, software, or none. hard
all.poll_interval When not set to zero, this parameter sets the wait for a TCP connection 0
keep-alive timer. If no traffic passes through the Cyclades-TS for this
period of time, the Cyclades-TS will send a modem status message to
the remote device to see if the connection is still up.
FIGURE 4.7 CONSOLE SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS (CONTINUED)

This Example
all.socket_port This defines an alternative labeling system for the Cyclades-TS ports. 7001+
The '+' after the numerical value causes the interfaces to be numbered
consecutively. In this example, interface 1 is assigned the port value
7001, interface 2 is assigned the port value 7002, etc.
all.protocol For the console server profile, the possible protocols are socket_server socket_server
(when telnet is used) and socket_ssh (when ssh version one or two is
used).
all.data_buffering A non-zero value activates data buffering. A file (/var/run/ttyS#.data) is 0
created on the Cyclades-TS and all data received from the port is
captured. The file contains a maximum size equal to this parameter,
which is overwritten each time the maximum is reached. This file can be
viewed using the normal Unix tools (cat, vi, more, etc.).
all.syslog_buffering When non-zero, the contents of the data buffer are sent to the syslog 0
server every time a quantity of data equal to this parameter is collected.
s1.tty The device name for the port is set to the value given in this parameter. ttyS1
If a device name is not provided for a port, it will not function.
s2.tty See the s1.tty entry in this table. ttyS2
FIGURE 4.7 CONSOLE SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS (CONTINUED)
Execute the command signal_ras hup to activate the changes. At this point, the configuration should be
tested. A step-by-step check list follows.
1. Since Radius authentication was chosen, create a new user on the Radius authentication server called test
and provide him with the password test.
2. From the console, ping 200.200.200.2 to make sure the Radius authentication server is reachable.
3. Make sure that the physical connection between the Cyclades-TS and the servers is correct. A cross cable
(not the modem cable provided with the product) should be used. Please see the hardware specifications
appendix for pin-out diagrams.

4. The Cyclades-TS has been set for communication at 9600 bps, 8N1. The server must also be configured to
communicate on the COM port with the same parameters. Also make sure that the computer is configured
to route console data to the COM port.
5. From a server on the LAN (not from the console), try to telnet to the server connected to the first port of the
Cyclades-TS using the following command:
telnet 200.200.200.1 7001
For both telnet and ssh sessions, the servers can be reached by either:
1. Ethernet IP of the Cyclades-TS and assigned socket port
or
2. Individual IP assigned to each port.
If everything is configured correctly, a telnet session should open on the server connected to port 1. If not, check
the configuration, follow the steps above again, and check the troubleshooting appendix. Now continue on to
step four later in this chapter.
STEP THREE - TERMINAL SERVER

The terminal server profile allows a terminal user to access a server on the LAN. The terminal can be either a
dumb terminal or a terminal emulation program on a PC. No authentication is used in this example and rlogin is
chosen as the protocol.
LAN
Linux Server
IP: 200.200.200.3
ETH0 TS1000
IP: 200.200.200.1
Speed: 9600 Port 16 VT100 Terminal
Port 1
PC Running
Terminal Application (VT100)
FIGURE 4.8 TERMINAL SERVER APPLICATION

The fifth configuration file (the first four were described in step two) is specific to the Cyclades-TS and a sample
file with comments is supplied in the Linux file system. It is called /etc/portslave/pslave.conf. A listing of the
pslave.conf file with all possible parameters, as well as the files used to create the three applications in this
chapter, is provided in Appendix C. There are three basic types of parameters: conf.* parameters are global or
apply to the Ethernet interface; all.* parameters are used to set default parameters for all ports, and s#.* parameters
change the default port parameters for individual ports. An all.* parameter can be overriden by a s#.* parameter
appearing later in the pslave.conf file (or vice-versa). A brief description of each parameter used for the terminal
server profile is given in Figures 4.9-4.10.

This Example
conf.rlogin Location of the rlogin binary that accepts the -i flag. /usr/local/bin/
rlogin-radius
conf.telnet Location of the telnet utility. /bin/telnet
conf.ssh Location of the ssh utility. /bin/ssh
conf.locallogins This parameter is only necessary when authentication is being performed 0
for a port. When set to one, it is possible to log in to the Cyclades-TS
directly by placing a "!" before your login name, then using your normal
password. This is useful if the Radius authentication server is down.
FIGURE 4.9 TERMINAL SERVER PSLAVE.CONF GLOBAL PARAMETERS

This Example
all.speed The speed for all ports. This value (as for all "all." parameters) can 9600
later be overridden for individual ports using the s<port
number>.speed parameter.
all.authtype There are several authentication type options: local (authentication is none
using a Radius authentication server), none, local/radius (authentication
is performed locally first, switching to Radius if unsuccessful), and
radius/local (the opposite of the previous option). Note that this
parameter controls the authentication required by the Cyclades-TS. The
authentication required by the device to which the user is connecting is
controlled separately.
all.protocol For the terminal server profile, the possible protocols are login (which telnet
requests username and password) and rlogin (which receives the
username from the TS and requests a password), telnet, ssh and ssh2.
all.host The IP address of the host to which the terminals will connect. 200.200.200.3
FIGURE 4.10 TERMINAL SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS

This Example
all.issue This text determines the format of \r\n\ TSLINUX - Portslave Internet Services\n\
the login banner that is issued when \r\n\ Welcome to terminal server %h port S%p \n\
a connection is made to the \r\n\ Customer Support: 510-770-9727
Cyclades-TS. \n represents a new www.cyclades.com/\n\
line and \r represents a carriage \r\n
return.
all.prompt This text defines the format of the login prompt. Expansion characters, %h login:
listed in Appendix C, can be used here.
all.term This parameter defines the terminal type assumed when performing vt100
rlogin or telnet to other hosts.
s1.tty The device name for the port is set to the value given in this parameter. ttyS1
If a device name is not provided for a port, it will not function.
FIGURE 4.10 TERMINAL SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS (CONTINUED)
1. Since authentication was set to none, the Cyclades-TS will not authenticate the user. However, the Linux
Server receiving the connection will. Create a new user on the server called test and provide him with the
password test.
2. From the console, ping 200.200.200.3 to make sure the server is reachable.
3. Make sure that the physical connection between the Cyclades-TS and the terminals is correct. A cross cable
(not the modem cable provided with the product) should be used. Please see the hardware specifications
appendix for pin-out diagrams.
4. The Cyclades-TS has been set for communication at 9600 bps, 8N1. The terminals must also be configured
with the same parameters.
5. From a terminal connected to the Cyclades-TS, try to log in to the server using the username and password
configured in item one.
Now continue on to step four later in this chapter.
STEP THREE - REMOTE ACCESS SERVER

The remote access server profile allows a modem user to access the LAN. Radius authentication is used in this
example and ppp is chosen as the protocol.
Syslog Server
IP: 200.200.200.3
Radius Authentication LAN

Server
IP: 200.200.200.2 ETH0
IP:200.200.200.1
Port 32 Modem
TS2000 IP: 200.200.200.42
Port 1 Modem PC
Speed: 57600 Modem
PC
Modem IP: 200.200.200.11
FIGURE 4.11 REMOTE ACCESS SERVER APPLICATION
The fifth configuration file (the first four were described in step two) is specific to the Cyclades-TS and a sample
file with comments is supplied in the Linux file system. It is called /etc/portslave/pslave.conf. A listing of the
pslave.conf file with all possible parameters, as well as the files used to create the three applications in this
chapter, is provided in Appendix C. There are three basic types of parameters: conf.* parameters are global or
apply to the Ethernet interface; all.* parameters are used to set default parameters for all ports, and s#.* parameters
change the default port parameters for individual ports. An all.* parameter can be overriden by a s#.* parameter
appearing later in the pslave.conf file (or vice-versa). A brief description of each parameter used for the remote
access server profile is given in Figures 4.12-4.13.

This Example
conf.pppd Location of the ppp daemon with Radius. /usr/local/sbin/
pppd-radius
conf.syslog The IP address of a remote syslog daemon can be provided here, if 200.200.200.3
desired.
conf.facility This value (0-7) is sent to the syslog server (the TS is a syslog client) to 7
indicate in which file the syslog messages should be stored. The file
/etc/syslog.conf on the syslog server contains a mapping between facility
numbers and server log files.
FIGURE 4.12 REMOTE ACCESS SERVER PSLAVE.CONF GLOBAL PARAMETERS

This
Example
all.speed The speed for all ports. This value (as for all "all." parameters) can later 57600
be overridden for individual ports using the s<port number>.speed
parameter.
all.syslog_level This variable determines which syslog messages will be sent to the syslog 4
server configured in the conf.syslog parameter. A value of 0 suppresses all
but emergency messages while values between 1 and 7 send progressively
more types of messages for each increment.
all.console_level This variable determines which syslog messages will be sent to the Cyclades- 4
TS console connected through the console interface. See the previous
parameter for a description of possible values
all.authtype There are several authentication type options: local (authentication is radius
using a Radius authentication server), none, local/radius (authentication is
performed locally first, switching to Radius if unsuccessful), and radius/local
(the opposite of the previous option). Note that this parameter controls the
authentication required by the Cyclades-TS. The authentication required by
the device to which the user is connecting is controlled separately.
FIGURE 4.13 REMOTE ACCESS SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS
Parameter Description Value for This

Example
all.authhost1 This address indicates the location of the Radius authentication server 200.200.200.2
and is only necessary if this option is chosen in the previous parameter. A
second Radius authentication server can be configured with the
parameter all.authhost2.
all.accthost1 This address indicates the location of the Radius accounting server, which 200.200.200.2
can be used to track how long users are connected after being authorized
by the authentication server. Its use is optional.
all.radtimeout This is the timeout (in seconds) for a radius authentication query. The first 5
server (authhost1) is tried three times, and then the second (if configured)
is contacted. If the second also fails to respond, the first is contacted
again, repeating the cycle up to 10 times.
all.secret This is the shared secret necessary for communication between the cocomero
Cyclades-TS and the Radius servers.
all.protocol For the remote access server profile, the available protocols are PPP, ppp
SLIP and CSLIP.
all.ipno The IP address to be assigned to the dial-in users. 200.200.200.11+
all.netmask The netmask corresponding to the IP number provided in the previous 255.255.255.255
parameter.
all.mtu The maximum transmission unit (MTU) that can be transmitted in a PPP 1500
packet.
all.mru The maximum reception unit (MRU) that can be received in a PPP packet. 1500
all.initchat Modem initialization string. TIMEOUT 10 "" \d\l\dATZ \
OK\r\n-ATZ-OK\r\n "" \
TIMEOUT 3600 RING "" \
STATUS Incoming %p:I.HANDSHAKE "" ATA \
TIMEOUT 60 CONNECT@ "" \
STATUS Connected %p:I.HANDSHAKE
FIGURE 4.13 REMOTE ACCESS SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS (CONTINUED)
Parameter Description Value for This

Example
all.dcd In a socket session, if dcd=0, a connection request (telnet or ssh) will 1
be accepted regardless of the DCD signal and the connection will not
be closed if the DCD signal is set to DOWN. In a socket connection,
if dcd=1 a connection request will be accepted only if the DCD signal
is UP and the connection will be closed if the DCD signal is set to
DOWN.
all.autoppp PPP options to auto-detect a ppp %i:%j novj \
session. proxyarp modem asyncmap 0 \
noipx noccp login auth require-pap refuse-chap \
mtu %t mru %t \
plugin /usr/lib/libpsr.so
all.pppopt PPP options when user has already %i:%j novj \
been authenticated. proxyarp modem asyncmap 0 \
noipx noccp mtu %t mru %t netmask %m \
idle %I maxconnect %T \
s1.tty The device name for the port is set to the value given in this ttyS1
parameter. If a device name is not provided for a port, it will not
function.
FIGURE 4.13 REMOTE ACCESS SERVER PSLAVE.CONF PORT-SPECIFIC PARAMETERS (CONTINUED)

1. Since Radius authentication was chosen, create a new user on the Radius authentication server called test
and provide him with the password test.
2. From the console, ping 200.200.200.2 to make sure the Radius authentication server is reachable.
3. Make sure that the physical connection between the Cyclades-TS and the modems is correct. The modem
cable provided with the product should be used. Please see the hardware specifications appendix for pin-
out diagrams.
4. The Cyclades-TS has been set for communication at 57600 bps, 8N1. The modems should be programmed
to operate at the same speed on the DTE interface. Also make sure that the computer is configured to route
console data to the COM port.
5. Try to dial in to the Cyclades-TS from a remote computer using the username and password configured in
item one. The computer dialing in must be configured to receive its IP address from the remote access
server (the Cyclades-TS in this case) and to use PAP authentication.
Now continue on to step four.
STEP FOUR - FOR ALL PROFILES

The next step is to update the system with the modified data in the files above. Make sure the file named /etc/
config_files contains the names of all files that should be saved to flash.
Next, the command saveconf, which reads the /etc/config_files file, should then be run. saveconf copies all the
files listed in the file /etc/config_files from the ramdisk to /proc/flash/script. The previous contents of the file /
proc/flash/script will be lost.
Restart the cy_ras process using its process ID. This can be done by executing the command:
signal_ras hup
This executes the ps command, searches for the cy_ras process id, then sends the signal HUP to the process,
all in one step.
Now the configuration is complete.
saveconf is equivalent to tar -czf /proc/flash/script -T /etc/config_files in

standard Linux (this command is emulated by busybox on the TS and does not support the z flag).
restoreconf does the opposite of saveconf, copying the contents of the /proc/flash/script
file to the corresponding files in the ramdisk. The files on the ramdisk are overwritten.
restoreconf is run automatically each time the Cyclades-TS is booted.
CHAPTER 5 UPGRADES AND TROUBLESHOOTING

Upgrades
All 6 files added by Cyclades to the standard Linux files are in the /proc/flash directory. They are:
boot_ori - original boot code
boot_alt - alternate boot code
syslog - event logs (not used by Linux)
config - configuration parameters, only the boot parameters are used by the boot code
zImage - Linux kernel image
script - file where all Cyclades-TS configuration information is stored
To upgrade the Linux kernel provided in the Cyclades-TS, ftp the new zImage file on top of the zImage file in
the /proc/flash directory. Then, reboot, and the new Linux kernel will take over. This can be confirmed by
typing
cat /proc/version
to see the Linux kernel version.
Troubleshooting
If the Cyclades-TS booted properly, the interfaces can be verified using ifconfig and ping. If ping does not
work, check the routing table using the command route. Of course, all this should be tried after checking that
the cables are connected correctly.
As mentioned in Chapter 4, the file /etc/config_files contains a list of files acted upon by saveconf and
restoreconf. If a file is missing, it will not be loaded onto the ramdisk on boot. The following table lists files
that should be included in the /etc/config_files file and which programs use each.
Chapter 5 Upgrades and Troubleshooting 36

File Program
/etc/securetty telnet, login, su
/etc/issue getty
/etc/getty_ttyS0 login (via console)
/etc/hostname tcp
/etc/hosts tcp
/etc/host.conf tcp
/etc/nsswitch.conf dns
/etc/resolv.conf dns
/etc/config_files saveconf
/etc/passwd login, passwd, adduser...
/etc/group login, passwd, adduser...
/etc/ssh/ssh_host_key.pub sshd
/etc/ssh/sshd_config sshd
/etc/ssh/ssh_config ssh client
/etc/ssh/ssh_host_key sshd (ssh1)
/etc/ssh/ssh_host_key.pub sshd (ssh1)
/etc/ssh/ssh_host_dsa_key sshd (ssh2)
/etc/ssh/ssh_host_dsa_key.pub sshd (ssh2)
/etc/snmp/snmpd.conf snmpd
/etc/portslave/pslave.conf cy_ras, portslave, TS configuration information
/etc/network/ifcfg_eth0 ifconfig eth0, cy_ras, rc.sysconf
/etc/network/ifcfg* ifconfig, cy_ras, rc.sysinit
/etc/network/ifcfg_lo ifconfig lo, cy_ras, rc.sysinit
/var/run/radsession.id radinit, radius authentication process
/home adduser, passwd
/etc/network/st_routes ifconfig, cy_ras, rc.sysconf
If any of the files listed in /etc/config_files is modified, the Cyclades-TS administrator must execute the
command saveconf before rebooting the Cyclades-TS or the changes will be lost. If a file is created (or a file

name altered), its name must be added to this file before executing saveconf and reboot.
Cyclades Technical Support is always ready to help with any configuration problems. Before calling,
execute the command
cat /proc/version
and note the Linux version and Cyclades-TS version written to the screen. This will speed resolution
of most problems.
Hardware Test
A hardware test called tstest is included with the Cyclades-TS firmware. It is a menu-driven program, run by
typing tstest at the command prompt, and the various options are described below. Note that the Cyclades-TS
should not be tested while in use as the test will inactivate all ports.
Port Test
Either a cross cable or a loop-back connector is necessary for this test. The pinout diagrams are supplied in
appendix B. Connect the loop-back connector to the modem cable and then connect the modem cable to the
port to be tested (or connect a cross cable between two ports to be tested). When tstest senses the presence
of the cable or connector, the test will be automatically run and the result shown on the screen.
Each line of data correponds to a port in test. The last 4 columns (DATA, CTS, DCD, and DSR) indicate errors.
The values in these columns should be zero. The figure below is an example of the output screen.
<- Packets -> <- Errors ->
From To Sent Received Passes Data CTS DCD DSR
2 <-> 2 35 35 35 0 0 0 0
4 <-> 5 35 35 35 0 0 0 0
5 <-> 4 35 35 35 0 0 0 0
When this test is run with a cable or connector without the DSR signal (see the pinout diagram for the cable or
connector being used), errors will appear in the DSR column. This does not indicate a problem with the port. In
the example above, tstest perceived that a loop-back connector was attached to port 2 and that a cross cable

was used to connect ports 4 and 5.
Port Conversation
This test sends and receives data on the selected port. One way to run this test is to place a loop-back
connector on the port to be tested and begin. Enter the number of the port and a baud rate (9600 is a typical
value). Type some letters, and if the letters appear on the screen, the port is working. If the letters do not appear
on the screen (which also occurs if the loop-back connector is removed), the port is not functioning correctly.
A second method that can be used to test the port is to connect it to a modem with a straight cable. Begin the
test and type “at”. The modem should respond with “OK”, which will appear on the screen. Other commands
can be sent to the modem or to any other serial device.
Test Signals Manually

This test confirms that signals are being sent and received on the selected port. Neither the loop-back connector
nor the cross cable are necessary. Enter the number of the port to be tested and begin the test.
State DTR DCD DSR RTS CTS

ON X X
↓ ↓
OFF X X X
First, type Ctrl-D to see the X in the DTR column move position, then type Ctrl-R to see the X in the RTS column
change position. If each of the Xs moves in response to its command, the signals are being sent.
Another method to test the signals is to use a loop-back connector. Enter the number of the port with the loop-
back connector and start the test. In this case, when Ctrl-D is typed, the Xs in the first three columns will move
as shown below.

State DTR DCD DSR RTS CTS

ON X X X X
↓ ↓ ↓
OFF X
This is because the test is receiving the DTR signal sent through the DCD and DSR channels. When Ctrl-R is
typed, the Xs in the RTS and CTS columns should move together. If the Xs change position as described, the
signals are being sent and received correctly.
Single User Mode
The Cyclades-TS has a single user mode used when:
• The name or password of the user with root privileges is lost or forgotten,
• After an upgrade or downgrade which leaves the Cyclades-TS unstable,
• After a configuration change which leaves the Cyclades-TS inoperative or unstable.
Type the word “single” during the boot using a console connection. This cannot be done using a telnet or other
remote connection.
The initial output of the boot process is shown below.
Entry Point = 0x00002120

loaded at: 00002120 0000D370
relocated to: 00300020 0030B270
board data at: 003052C8 0030537C
relocated to: 002FF120 002FF1D4
zimage at: 00008100 0006827E
relocated to: 00DB7000 00E1717E
initrd at: 0006827E 0024F814
relocated to: 00E18000 00FFF596
avail ram: 0030B270 00E18000
Linux/PPC load: root=/dev/ram

After printing “Linux/PPC load: root=/dev/ram”, the Cyclades-TS waits approximately 10 seconds for user input.
This is where the user should type “single”. When the boot process is complete, the Linux prompt will appear
on the console:
[root@(none) /]#
If the password or username was forgotten, execute the following commands:

passwd
saveconf
reboot
For configuration problems, the user has two options:
1. Edit the file(s) causing the problem with vi, then execute the commands
saveconf
reboot
2. Reset the configuration by executing the commands:

echo 0 > /proc/flash/script
reboot
If the problem is due to an upgrade/downgrade, a second downgrade/upgrade will be necessary to reverse the
process. First, the Ethernet interface must be initialized in order to reach a ftp server. Execute the following
script (replacing the IP number with your Ethernet interface IP number):
config_eth0 200.200.200.1
At this point, the DNS configuration (in the file /etc/resolv/conf) should be checked and a default route should be
created if one no longer exists. Then, download the kernel image using the ftp command.

APPENDIX A INFORMATION FOR USERS NOT FAMILIAR WITH LINUX
Users and Passwords

A username and password are necessary to log in to the Cyclades-TS. The user “root” is predefined, without a
password. A password should be configured as soon as possible to avoid unauthorized access.
Type the command:
passwd
to create a password for the root user.
To create a regular user (without root priveleges), use the commands:
useradd user_name
password user_password
To log out, type “logout” at the command prompt.
Linux File Structure

The Linux file system is organized hierarchically, with the base (or root) directory represented by the symbol “/”.
All folders and files are nested within each other below this base directory. The directories located just below
the base directory are:
Appendix A - Linux 42
/home Contains the work directories of system users.

/bin Contains applications and utilities used during system initialization.
/dev Contains files for devices and ports.
/etc Contains configuration files specific to the operating system.
/lib Contains shared libraries.
/proc Contains process information
/mnt Contains information about mounted disks.
/opt Location where packages not supplied with the operating system are stored.
/tmp Location where temporary files are stored.
/usr Contains most of the operating system files.
/var Contains operating system data files.
Basic File Manipulation Commands

The basic file manipulation commands allow the user to copy, delete and move files and create and delete
directories.
cp file_name destination Copies the file indicated by file_name to the path indicated by
a) cp text.txt /tmp destination. a) copies the file text.txt in the current directory to the tmp
b) cp /chap/robo.php ./excess.php directory. b) copies the file robo.php in the chap directory to the
current directory and renames the copy excess.php.
rm file_name Removes the file indicated by file_name.
mv file_name destination Moves the file indicated by file_name to the path indicated by
destination.
mkdir directory_name Creates a directory named directory_name. a) creates the directory
a) mkdir spot spot in the current directory. b) creates the directory snuggles in the
b) mkdir /tmp/snuggles directory tmp.
rmdir directory_name Removes the directory indicated by directory_name.
Other commands allow the user to change directories and see the contents of a directory.
pwd Supplies the name of the current directory. While logged in, the user is always
"in" a directory. The default initial directory is the user's home directory,
/home/<username>
ls [options] directory_name Lists the files and directories within directory_name. Some useful options are -l
for more detailed output and -a which shows hidden system files.
cd directory_name Changes the directory to the one specified
cat file_name Prints the contents of file_name to the screen.
Shortcuts:
. (a dot) represents the current directory
.. (two dots) represents one directory above the current directory (i.e. one directory closer to the base
directory).
The vi Editor
To edit a file using the vi editor, type
vi file_name
vi is a three-state line editor: it has a command mode, a line mode and an editing mode. If in doubt as to which
mode you are in, press the <ESC> key which will bring you to the command mode.
Mode What is done there How to Get There
command mode navigation within the open file Press the <ESC> key.
editing mode text editing See list of editing commands below.
line mode file saving, opening, etc. exiting From the command mode, type ":" (the
from vi colon).
Entering the program, the user is automatically in the command mode. To navigate to the part of the file to be
edited, use the following keys:
h moves the cursor to the left (left arrow)
j moves the cursor to the next line (down arrow)
k moves the cursor to the previous line (up arrow)
l moves the cursor to the right (right arrow)
Having arrived at the location where text should be changed, use these commands to modify the text (note
commands “i” and “o” will move you into the editing mode and everything typed will be taken literally until you
press the <ESC> key to return to the command mode)
i insert text before the cursor position (everything to
the right of the cursor is shifted right)
o create a new line below the current line and insert
text (all lines are shifted down)
dd remove the entire current line
u undo the last modification
x delete the letter at the cursor position
Now that the file has been modified, enter the line mode (by typing “:” from the command mode) and use one of
the following commands:
w save the file (w is for write)
wq save and close the file (q is for quit)
q! close the file without saving
w file save the file with the name file
e file opens the file named file
The Routing Table
The Cyclades-TS has a static routing table that can be seen using the commands
route -n
or
netstat -rn
The file /etc/network/st_routes shown in Figure 4.5 is the Cyclades-TS’s method for configuring static routes.
Routes should be added to the file (which is a script run when the Cyclades-TS is initialized) or at the prompt (for
temporary routes) using the following syntax:
route [add|del] [-net|-host] target netmask nt_msk [gw gt_way] interf
[add|del] one of these tags must be present -- routes can be either added or deleted.
[-net|-host] -net is for routes to a network and -host is for routes to a single host.
target target is the IP address of the destination host or network
netmask the tag netmask and a mask are necessary only when subnetting is used. Otherwise, a
nt_msk mask appropriate to the target is assumed. nt_msk must be specified in dot notation.
gw gt_way specifies a gateway, when applicable. gt_way is the IP address or hostname of the
gateway.
interf the interface to use for this route. Must be specified if a gateway is not. When a gateway
is specified, the operating system determines which interface is to be used.
ssh - The Secure Shell Session

ssh is a command interface and protocol often used by network administrators to connect securely to a remote
computer. ssh is actually three utilities—slogin, ssh and scp—that replace their non-secure counterparts rlogin,
rsh and rcp. There are two versions, ssh and ssh2. The Cyclades-TS offers both.
The command to start an ssh client session from a Unix workstation is

ssh -t <user>@<hostname>
where
<user> = <username>:ttySnn or
<username>:socket_port or
<username>:ip_addr or
<username>:serverfarm
Note: “serverfarm” is a physical port alias. It can be configured in the file pslave.conf.
An example:
username: cyclades
TS1000 IP address: 192.168.160.1
host name: ts1000
servername for port 1: file_server
ttyS1 addressed by IP 10.0.0.1 or socket port 7001. The various ways to access the server connected to the
port are:
ssh -t cyclades:ttyS1@ts1000
ssh -t cyclades:7001@ts1000
ssh -t cyclades:10.0.0.1@ts1000
ssh -t cyclades:file_server@ts1000
ssh -t -l cyclades:10.0.0.1
Note that either -l or @ are used, but not both. For ssh2, the -2 flag is used:
ssh -t -2 cyclades:7001@ts1000
To log in to a port that does not require authentication, the username is not necessary:
ssh -t -2 ttyS1@ts1000
The Process Table

The process table shows which processes are running. Type ps -a to see a table similar to that below.
PID Uid Gid State Command

1 root root S /sbin/inetd
31 root root S /sbin/sshd
32 root root S /sbin/cy_ras
36 root root S /sbin/cy_wdt_led wdt led
154 root root R /ps -a
To restart the cy_ras process use its process ID or execute the command:
signal_ras hup
This executes the ps command, searches for the cy_ras process id, then sends the signal HUP to the process,
all in one step. Never kill cy_ras with the signals -9 or SIGKILL.
APPENDIX B HARDWARE SPECIFICATIONS

The Cyclades-TS has RJ-45 female interfaces.
Modular Jack
Modular Plug Cable

Modular Plug
Pin 1
Pin 1
Pin 1
Cable
.
FIGURE B.1 RJ-45 FEMALE CONNECTOR - 8 PINS

Buy cables directly from Cyclades or make them using the information provided in the diagrams on the next
pages.
Appendix B - Hardware Specifications 49

How to Connect the Cyclades-TS to Modems

Use a straight cable to connect a modem to a Cyclades-TS port, which connects the signals on the two sides pin
to pin. If the modem has a DB-25 connector, create a convertor following the pinout diagram in Figure B.2.
To the
Cyclades-TS
Cyclades-TS Modem
RJ-45 Female/DB-25 (RJ-45 - 8 pins ) (DB-25)
Male Converter
Pin Signal Signal Pin
RJ-45
Connector Modem 3 TxD TxD 2
3
6 6 RxD RxD 3
1
5 4 Gnd Gnd 7
8
4 7 DCD DCD 8
pin 8
2
7 pin 1 5 CTS CTS 5
pin 1 pin 8 2 DTR DTR 20
2 34567 8 1 RTS RTS 4
1 13
Front View 8 DSR DSR 6
14 25
20
FIGURE B.2 STRAIGHT CABLE FOR MODEM WITH DB-25 INTERFACE

This is a straight cable and all signals on one side should be connected to the same signals on the other side.

How to Connect the Cyclades-TS to Terminals, Printers and Servers

Terminals and printers often have DB-25 serial interfaces. They can be connected to the Cyclades-TS with a
null-modem cable, which is a cable used to connect two DTE devices. They connect the Gnd signals and
connect the TxD signal on one side with the RxD on the other. If the modem has a DB-25 connector, create a
convertor following the pinout diagram in Figure B.3. If hardware flow control is not needed, the other signals do
not need to be passed and can remain unconnected.
Straight
To the Cable With
Cyclades-TS Terminal / Printer
8 Wires
RJ-45 Female/DB-25 Cyclades-TS Without Hardware
Male Converter (RJ-45 -8 pin) Flow Control (DB-25)
Pin Signal Signal Pin

RJ-45
Connector 3 TxD RxD 3
Terminal or Printer
6 RxD TxD 2
6
3 4 Gnd Gnd 7
4 8 DSR DTR 20
2 7 DCD DSR 6
Pin 8 7 2 DTR DCD 8
8 Pin 1
Pin 1 1 RTS RTS 4
Front View 1 Pin 8 5 CTS CTS 5
5
2 3 7
1 13
14 25
6 8
Front View
4 5 20
FIGURE B.3 NULL MODEM CABLE (CROSS CABLE)

APPENDIX C SAMPLE PSLAVE.CONF FILES

The pslave.conf files for the three examples configured in chapter 4 are presented first. Then, the pslave.conf
file with all possible parameters and their descriptions follows.
CONSOLE ACCESS SERVER CONFIGURATION FILE

#
# pslave.conf Sample server configuration file.
#
# Console Access Server Profile
#
#
# The Cyclades-TS uses a virtual terminal concept. Virtual terminals are
# named s1, s2, etc. Every virtual terminal should have a related
# physical device tty (without the "/dev/"). The tty parameter
# must be configured and must be unique for each virtual terminal.
#
#
# There two types of parameters:
#
# 1) Global parameters
# These parameters have the prefix "conf." Example of global parameters
# are ethernet ip address, etc.
#
# 2) Terminal Parameters.
# These parameters have prefixes "all.", "s1.", "s2.", etc.
#
#
# The "all." entries are used as a template for all virtual terminals.
# Setting all.speed to 9600 will set all virtual terminal (s1, s2,
# s3, etc.) speeds to 9600.
#
# Note that you can change the "all." settings one by one.
# If the parameter "s4.speed 19200" appears later in the file, all
terminals
# except s4 will have speed 9600 bps and "s4" will have speed 19200 bps.
#
#
# Ethernet configuration.
Appendix C - Sample pslave.conf files 52

#
# These parameters should only be configured in the file /etc/network/
ifcfg_eth0
# _IF_ the customer will not be using the cy_ras/portslave aplications. If the
# the cy_ras/portslave aplications are _NOT_ used put all ifconfig commands
# for the ethernet directly in the /etc/network/ifcfg_eth0.
# The cy_ras application OVERWRITES the ifcfg_eth0 file with the values
configured
# here.
#
#
conf.eth_ip 200.200.200.1
conf.eth_mask 255.255.255.0
conf.eth_mtu1500
#
# Syslog server: syslog is the IP address of a remote syslog daemon.
facility
# is a value from 0 to 7 which is sent to the syslog server to
# indicate in which file the syslog messages should be stored.
# The file /etc/syslog.conf on the syslog server contains a mapping
# between facility numbers and server log files.
#
conf.syslog 200.200.200.2
conf.facility 7
#
# Syslog server message level. An integer between 0 and 7. Zero: does not send
# syslog messages to the syslog server.
#
all.syslog_level 4
#
# Syslog Console message level. An integer between 0 and 7. Zero: does not
send
# syslog messages to the console.
#
all.console_level 4
#
# Speed. All ports are set to 9600 baud rate, 8 bits, No parity, 1 stop bit.

# These values can be changed port by port later in the file.
#
all.speed 9600
all.datasize 8
all.stopbit 1
all.parity none
#
# Authentication type - either "local", "radius", "none", "remote"
# local/radius, or radius/local.
#
# If the authentication type is configured as "local/radius" the portslave
# first tries to authenticate locally. If it fails, portslave will try to
# authenticate using the radius server.
#
all.authtype radius
# Authentication host and accounting host. Two of each can be configured
# per port. The first is always tried three times before switching to the
# second. Then are tried alternately, up to a maximum of 10 times total.
# radtimeout sets the number of seconds per query.
#
all.authhost1 200.200.200.2
all.accthost1 200.200.200.2
all.radtimeout 3
#
# The shared secret used by RADIUS.
#
all.secret cyclades
#
# IP. If you end the "ipno" with a "+", the port number will
# be added to the IP number to give the IP number for that port.
# The IP number of a port is used when the RADIUS
# server does not send an IP number, or if it tells us to use a dynamic IP no.
#
all.ipno 192.168.1.101+
#

# Standard message issued on connect.
#
all.issue \r\n\
TSLINUX - Portslave Internet Services\n\
\r\n\
Welcome to terminal server %h port S%p \n\
\r\n\
Customer Support: 510-770-9727 http://www.cyclades.com/\n\
\r\n
#
# Login prompt.
#
all.prompt %h login:
#
# Terminal type, for rlogin/telnet sessions.
#
all.term vt100
#
# Serial port flow control:
# hard - hardware, rts/cts
# soft - software, CTRL-S / CTRL-Q
# none.
#
all.flow hard
#
# When not set to zero, this parameter sets the wait for a TCP connection
# keep-alive timer. If no traffic passes through the Cyclades-TS for
# this period of time, the Cyclades-TS will send a modem status message
# to the remote device to see if the connection is still up.
#
all.poll_interval 0
#
# This defines an alternative labeling system for the Cyclades-TS ports.
# The '+' after the numerical value causes the interfaces to be numbered
# consecutively.
#
all.socket_port 7001+

#
# Default protocol
#
# Valid values are "login", "rlogin", "telnet",
# "ssh", "ssh2", "slip", "cslip", "ppp", "socket_client",
# "socket_server" and "socket_ssh".
all.protocol socket_server
#
# Data buffering configuration
#
# A non-zero value activates data buffering. A file (/var/run/ttyS#.data)
# is created on the Cyclades-TS and all data received from the port is
# captured. The file contains a maximum of 1024k, which is overwritten each
# time the maximum is reached. This file can be viewed using the normal Unix
# tools (cat, vi, more, etc.).
#
all.data_buffering 0
#
# When non-zero, the contents of the data buffer are sent to the syslog
# server every time a quantity of data equal to this parameter is collected.
# [40 to 255 recomended]
#
all.syslog_buffering 0
# Port-specific parameters
#-----------------
# PORT 1
#-----------------
# this port can be accessed by typing: ssh -t <username>:ttyS1@200.200.200.1
or
# ssh -t <username>:200.200.200.11@200.200.200.1
or
# ssh -t -l <username>:7001 200.200.200.1 or
s1.tty ttyS1
#
#
s1.protocol socket_server

s1.authtype local
#-----------------
# PORT 2
#-----------------
or
# ssh -t <username>:200.200.200.12@200.200.200.1
or
s2.tty ttyS2
#-----------------
# PORT 8
#-----------------
or
# ssh -t <username>:200.200.200.18@200.200.200.1
or
# see the installation manual for other possible syntaxes.
s8.tty ttyS8
TERMINAL ACCESS SERVER CONFIGURATION FILE

#
#
# Terminal Server Profile
#
#
#
#
#
#
#
#
#
terminals
#
#
ifcfg_eth0
configured
# here.
#
conf.eth_ip 200.200.200.1
conf.eth_mtu1500
#
# Location of the rlogin binary that accepts the "-i" flag.
#
conf.rlogin /usr/local/bin/rlogin-radius
#
# Location of the telnet utility. This can be the system telnet. (Optional)
#
conf.telnet /bin/telnet

#
# Location of ssh utility. This can be the system SSH. (Optional)
#
conf.ssh /bin/ssh
#
# This parameter is only necessary when authentication is being
# performed for a port. When set to one, it is possible to log
# in to the Cyclades-TS directly
# by placing a "!" before your login name, then using your normal
# password. This is useful if the Radius authentication server is down.
#
conf.locallogins 0
#
#
all.speed 9600
all.datasize 8
all.stopbit 1
all.parity none
#
# Authentication type - either "local", "radius", "none"
#
#
all.authtype none
#
#
all.protocoltelnet

#
# Default ip address of linux host to which the terminals will connect.
# Used by the protocols rlogin, ssh, socket_client, etc.
#
all.host 200.200.200.3
#
#
all.issue \r\n\
\r\n\
\r\n\
\r\n
#
# Login prompt.
#
#
#
all.term vt100
#
# none.
#
all.flow hard
# Activation of individual ports

s1.tty ttyS1
#s2.tty ttyS2

#s3.tty ttyS3
#s4.tty ttyS4
#s5.tty ttyS5
#s6.tty ttyS6
#s7.tty ttyS7
#s8.tty ttyS8
#s9.tty ttyS9
#s10.tty ttyS10
#s11.tty ttyS11
#s12.tty ttyS12
#s13.tty ttyS13
#s14.tty ttyS14
#s15.tty ttyS15
s16.tty ttyS16
REMOTE ACCESS SERVER CONFIGURATION FILE

#
#
# Remote Access Server Profile
#
#
#
#
#
#
#
#
#
terminals
#
#
#
#
ifcfg_eth0
configured
# here.
#
conf.eth_ip 200.200.200.1
conf.eth_mtu1500
#
# Location of our patched pppd with Radius linked in.
#
conf.pppd /usr/local/sbin/pppd-radius
#
facility
#
#
conf.facility 7

#
#
all.speed 57600
all.datasize 8
all.stopbit 1
all.parity none
#
#
all.syslog_level 4
#
send
#
all.console_level 4
#
# Authentication type - either "local", "radius", "none"
#
#
all.authtype radius
#
#
all.radtimeout 5
#

#
all.secret cocomero
#
#
all.protocolppp
#
all.ipno 200.200.200.11+
all.netmask 255.255.255.255
#
# Maximum reception/transmission unit size for the port
#
all.mtu 1500
all.mru 1500
#
# Use this to initialize the modem.
#
# d == delay (1 sec), p == pause (0.1 sec), l == toggle DTR
# r == <CR>, l == <LF>
#
all.initchat TIMEOUT 10 \
"" \d\l\dATZ \
OK\r\n-ATZ-OK\r\n "" \
TIMEOUT 3600 \
RING "" \
STATUS Incoming %p:I.HANDSHAKE \
"" ATA \

TIMEOUT 60 \
CONNECT@ "" \
STATUS Connected %p:I.HANDSHAKE
#
# none.
#
all.flow hard
#
# DCD signal (sets the tty parameter CLOCAL). Valid values are 0 or 1.
# In a socket session, if all.dcd=0, a connection request (telnet or
# ssh) will be accepted regardless of the DCD signal and the connection
# will not be closed if the DCD signal is set to DOWN.
# In a socket connection, if all.dcd=1 a connection request will be
# accepted only if the DCD signal is UP and the connection (telnet or
# ssh) will be closed if the DCD signal is set to DOWN.
#
all.dcd 1
#
# PPP options - used if a PPP session is autodetected.
# Note that mru and mtu are both set to the MTU setting.
all.autoppp %i:%j novj \
proxyarp modem asyncmap 0 \
noipx noccp login auth require-pap refuse-chap \
mtu %t mru %t \
# PPP options - User already authenticated and service type is PPP.
#
all.pppopt %i:%j novj \
proxyarp modem asyncmap 0 \
noipx noccp mtu %t mru %t netmask %m \
idle %I maxconnect %T \

s1.tty ttyS1
s32.tty ttyS32
COMPLETE CONFIGURATION FILE SHOWING ALL PARAMETERS
#
# pslave.conf Here is the sample server configuration file.
#
# Generic SAMPLE:
# all async ports at 9600 bps, 8N1
# Eth IP address 192.169.160.10/24 (MTU=1500)
# protocol socket_server
# host IP 192.168.160.8/24
# syslogd IP 192.168.160.1
# Radius Server IP 192.168.160.3 (authentication and accounting)
# authentication radius
#
#
# The Terminal Server uses a virtual terminal concept. Virtual terminals are
#
#
#
#
#
#
terminals
#
#
# Expansion Variables
#
# A list of format strings used by some parameters is provided here
# for reference.
#
# %l: login name
# %L: stripped login name
# %p: NAS port number
# %P: protocol
# %b: port speed
# %i: local IP
# %j: remote IP
# %1: first byte (MSB) of remote IP
# %2: second byte of remote IP
# %3: third byte of remote IP
# %4: fourth (LSB) byte of remote IP
# %c: connect-info
# %m: netmask
# %t: MTU
# %r: MRU
# %I: idle timeout
# %T: session timeout
# %h: hostname
# %%: %
#
# These parameters should only be configured in the file
# /etc/network/ifcfg_eth0 if the customer will not be using the
# cy_ras/portslave aplications. If the cy_ras/portslave aplications are not
# used put all ifconfig commands for the ethernet directly in the
# /etc/network/ifcfg_eth0.
#
configured
# here.
#

conf.eth_ip 192.168.160.10
conf.eth_mtu1500
#
# Lock directory - /var/lock on FSSTND compliant systems.
#
conf.lockdir/var/lock
#
# Location of the rlogin binary that accepts the "-i" flag.
#
conf.rlogin /usr/local/bin/rlogin-radius
#
# Location of our patched pppd with Radius linked in.
#
conf.pppd /usr/local/sbin/pppd-radius
#
# Location of the telnet utility. This can be the system telnet. (Optional)
#
conf.telnet /bin/telnet
#
# Location of ssh utility. This can be the system SSH. (Optional)
#
conf.ssh /bin/ssh
#
# This parameter is only necessary when authentication is being
# performed for a port. When set to one, it is possible to log
# in to the Terminal Server directly
# by placing a "!" before your login name, then using your normal
# password. This is useful if the Radius authentication server is down.
#
conf.locallogins 1
#
facility
#
conf.facility 7

#
#
all.speed 9600
all.datasize 8
all.stopbits 1
all.parity none
#
#
all.syslog_level 4
#
send
#
all.console_level 4
#
# Authentication type - either "local", "radius", "none", "remote"
# "local/radius", or "radius/local".
#
#
all.authtype radius
#
#
all.radtimeout 3
#all.authhost2 192.168.160.4

#all.accthost2 192.168.160.4
#
#
all.secret cyclades
#
# Default protocol.
#
#
all.protocolsocket_server
#
# Default ip address of linux host to which the terminals will connect.
# Used by the protocols rlogin, ssh, socket_client, etc.
#
all.host 192.168.160.8
#
#
all.ipno 192.168.1.101+
all.netmask 255.255.255.255
#
# Maximum reception/transmission unit size for the port
#
all.mtu 1500
all.mru 1500
#
#
all.issue \r\n\
\r\n\

\r\n\
\r\n
#
# Login prompt.
#
#
#
all.term vt100
#
# If you want the Terminal Server to update the
# login records (written to the /var/run/utmp and/or /var/log/wtmp
# files), set sysutmp/syswtmp to 1. This is useful for tracking
# who has accessed the Terminal Server and what they did.
#
all.sysutmp 1
all.syswtmp 0
all.utmpfrom "%p:%P.%3.%4"
#
# Use initchat to initialize the modem.
#
# d == delay (1 sec), p == pause (0.1 sec), l == toggle DTR
# r == <CR>, l == <LF>
#
#all.initchat TIMEOUT 10 \
# "" \d\l\dATZ \
# OK\r\n-ATZ-OK\r\n "" \
# TIMEOUT 10 \
# "" ATM0 \
# OK\r\n "" \
# TIMEOUT 3600 \
# RING "" \
# STATUS Incoming %p:I.HANDSHAKE \
# "" ATA \
# TIMEOUT 60 \

# CONNECT@ "" \
# STATUS Connected %p:I.HANDSHAKE
#
# none.
#
all.flow hard
#
# DCD signal (sets the tty parameter CLOCAL). Valid values are 0 or 1.
# In a socket session, if all.dcd=0, a connection request (telnet or
# ssh) will be accepted regardless of the DCD signal and the connection
# will not be closed if the DCD signal is set to DOWN.
# In a socket connection, if all.dcd=1 a connection request will be
# accepted only if the DCD signal is UP and the connection (telnet or
# ssh) will be closed if the DCD signal is set to DOWN.
#
all.dcd 1
#
# PPP options - used if a PPP session is autodetected.
# Note that mru and mtu are both set to the MTU setting.
#
#all.autoppp%i:%j novj \
# proxyarp modem asyncmap 0 \
# noipx noccp login auth require-pap refuse-chap \
# mtu %t mru %t \
# ms-dns 192.168.160.5 ms-dns 0.0.0.0 \
# plugin /usr/lib/libpsr.so
#
# PPP options - User already authenticated and service type is PPP.
#
#all.pppopt %i:%j novj \
# noipx noccp mtu %t mru %t netmask %m \
# idle %I maxconnect %T \
# ms-dns 192.168.160.5 ms-dns 0.0.0.0 \

#
#
# When not set to zero, this parameter sets the wait for a TCP connection
# keep-alive timer. If no traffic passes through the Terminal Server for
# this period of time, the Terminal Server will send a modem status message
# to the remote device to see if the connection is still up.
#
all.poll_interval 0
#
# This defines an alternative labeling system for the Terminal Server ports.
# The '+' after the numerical value causes the interfaces to be numbered
# consecutively.
#
all.socket_port 7001+
#
# Data buffering configuration
#
# A non-zero value activates data buffering. A file (/var/run/ttyS#.data)
# is created on the Terminal server and all data received from the port is
# captured. The file contains a maximum of 1024k, which is overwritten each
# time the maximum is reached. This file can be viewed using the normal Unix
# tools (cat, vi, more, etc.).
#
all.data_buffering 0
#
# When non-zero, the contents of the data buffer are sent to the syslog
# server every time a quantity of data equal to this parameter is collected.
# [40 to 255 recomended]
#
all.syslog_buffering 0
#
# Send Break to the TTY when this string is received (ssh only).
#
all.break_sequence ~break
#
# Authentication of Radius users registered without passwords

#
# When enabled (value 1) and a user registered in
# the Radius database with a blank password tries to log in, the user
# is authenticated. This is a very weak level of security since
# a user would only need to know that a particular username exists.
# This does not affect Radius users registered with passwords.
#
all.radnullpass 0
#
# SAMPLES
#
# To activate one of the samples below, comment all other samples
############################################################################
# SAMPLE #0: Console Server profile
# all ports with protocol socket_server
# all ports with radius authentication
# all ports at 9600 bps 8N1
# syslogd IP 192.168.160.1
#
# SAMPLE #0 Begin
#
s1.tty ttyS1
s2.tty ttyS2
s3.tty ttyS3
s4.tty ttyS4
s5.tty ttyS5
s6.tty ttyS6
s7.tty ttyS7
s8.tty ttyS8
s9.tty ttyS9
s10.tty ttyS10
s11.tty ttyS11
s12.tty ttyS12
s13.tty ttyS13
s14.tty ttyS14
s15.tty ttyS15
s16.tty ttyS16

# for TS2000 uncomment s17 through s32
#s17.tty ttyS17
#s18.tty ttyS18
#s19.tty ttyS19
#s20.tty ttyS20
#s21.tty ttyS21
#s22.tty ttyS22
#s23.tty ttyS23
#s24.tty ttyS24
#s25.tty ttyS25
#s26.tty ttyS26
#s27.tty ttyS27
#s28.tty ttyS28
#s29.tty ttyS29
#s30.tty ttyS30
#s31.tty ttyS31
#s32.tty ttyS32
############################################################################
# SAMPLE #1: Console Server profile with data buffering enabled
# all ports with protocol socket_server
# all ports with radius authentication
# syslogd IP 192.168.160.1
#
# for ssh sessions:
# ssh -t <username>:<serverfarm>@<tsname>
# ssh -t <username>:<ttySn>@<tsname>
# ssh -t <username>:<IP address of the async port>@<tsname>
# ssh -t <username>:<socket TCP port of the async port>@<tsname>
#
# or:
# ssh -t -l <username>:<serverfarm> <tsname>
# ssh -t -l <username>:<ttySn> <tsname>
# ssh -t -l <username>:<IP address of the async port> <tsname>
# ssh -t -l <username>:<socket TCP port of the async port> <tsname>
# ssh -t -l <username> <IP address of the async port>
#
# serverfarm is an alias name for a server connected to the Terminal
# Server through one of its ports. Only used by the ssh command.

#
#
# for telnet sessions: telnet <tsname> <TCP socket port> or telnet <IP
address>
#
# uncomment the right "all.protocol" below according to use of SSH or TELNET
#
# SAMPLE #1 Begin
#
# all.protocol socket_ssh
# all.protocol socket_server
#
#all.data_buffering 1000 # maximum file size
#all.syslog_buffering 50 # minimum syslog data size
#
#s1.tty ttyS1
#s1.serverfarm server_snoopy
#s2.tty ttyS2
#s2.serverfarm server_patty
#s3.tty ttyS3
#s3.serverfarm server_woodstock
#s4.tty ttyS4
#s5.tty ttyS5
#s6.tty ttyS6
#s7.tty ttyS7
#s8.tty ttyS8
#s9.tty ttyS9
#s10.tty ttyS10
#s11.tty ttyS11
#s12.tty ttyS12
#s13.tty ttyS13
#s14.tty ttyS14
#s15.tty ttyS15
#s16.tty ttyS16
#s17.tty ttyS17
#s18.tty ttyS18
#s19.tty ttyS19
#s20.tty ttyS20
#s21.tty ttyS21
#s22.tty ttyS22

#s23.tty ttyS23
#s24.tty ttyS24
#s25.tty ttyS25
#s26.tty ttyS26
#s27.tty ttyS27
#s28.tty ttyS28
#s29.tty ttyS29
#s30.tty ttyS30
#s31.tty ttyS31
#s32.tty ttyS32
#
# SAMPLE #1 End
############################################################################
############################################################################
# SAMPLE #2:Terminal Server profile
# all ports with local authentication
# syslogd IP 192.168.160.1
#
# comment (all.authtype radius) and (all.protocol socket_server) above and
# replace them with the parameters given below.
#
# SAMPLE #2 Begin
#
# all.protocol login
# all.authtype local
#s1.tty ttyS1
#s2.tty ttyS2
#s3.tty ttyS3
#s4.tty ttyS4
#s5.tty ttyS5
#s6.tty ttyS6
#s7.tty ttyS7
#s8.tty ttyS8
#s9.tty ttyS9
#s10.tty ttyS10
#s11.tty ttyS11
#s12.tty ttyS12
#s13.tty ttyS13

#s14.tty ttyS14
#s15.tty ttyS15
#s16.tty ttyS16
#s17.tty ttyS17
#s18.tty ttyS18
#s19.tty ttyS19
#s20.tty ttyS20
#s21.tty ttyS21
#s22.tty ttyS22
#s23.tty ttyS23
#s24.tty ttyS24
#s25.tty ttyS25
#s26.tty ttyS26
#s27.tty ttyS27
#s28.tty ttyS28
#s29.tty ttyS29
#s30.tty ttyS30
#s31.tty ttyS31
#s32.tty ttyS32
#
# SAMPLE #2 End
############################################################################
############################################################################
# SAMPLE #3:RAS (PPP dial-in) profile
# all ports at 57600 bps, 8N1
# all ports with local authentication
# syslogd IP 192.168.160.1
# DNS Server 192.168.160.5
# remote IP addresses assigned 192.168.160.101-116 (TS1000) 101-132 (TS2000)
#
# comment (all.protocol ppp), (all.ipno 192.168.1.101+),
# (all.speed 9600), (all.autoppp ""), (all.pppopt ""), and
# (all.initchat "") above and replace them with the
# parameters given below.
#
# SAMPLE #3 Begin
#

# all.speed 57600
# all.ipno 192.168.160.101+
# all.protocol ppp
# all.autoppp %i:%j novj \
# noipx noccp login auth require-pap refuse-chap \
# mtu %t mru %t \
# ms-dns 192.168.160.5 ms-dns 0.0.0.0 \
#
# all.pppopt%i:%j novj \
# noipx noccp mtu %t mru %t netmask %m \
# idle %I maxconnect %T \
# ms-dns 192.168.160.5 ms-dns 0.0.0.0 \
#all.initchat TIMEOUT 10 \
# "" \d\l\dATZ \
# OK\r\n-ATZ-OK\r\n "" \
# TIMEOUT 3600 \
# RING "" \
# STATUS Incoming %p:I.HANDSHAKE \
# "" ATA \
# TIMEOUT 60 \
# CONNECT@ "" \
# STATUS Connected %p:I.HANDSHAKE
#s1.tty ttyS1
#s2.tty ttyS2
#s3.tty ttyS3
#s4.tty ttyS4
#s5.tty ttyS5
#s6.tty ttyS6
#s7.tty ttyS7
#s8.tty ttyS8
#s9.tty ttyS9
#s10.tty ttyS10
#s11.tty ttyS11
#s12.tty ttyS12
#s13.tty ttyS13
#s14.tty ttyS14
#s15.tty ttyS15

#s16.tty ttyS16
#s17.tty ttyS17
#s18.tty ttyS18
#s19.tty ttyS19
#s20.tty ttyS20
#s21.tty ttyS21
#s22.tty ttyS22
#s23.tty ttyS23
#s24.tty ttyS24
#s25.tty ttyS25
#s26.tty ttyS26
#s27.tty ttyS27
#s28.tty ttyS28
#s29.tty ttyS29
#s30.tty ttyS30
#s31.tty ttyS31
#s32.tty ttyS32
#
# SAMPLE #3 End
#########################################################################
############################################################################
# SAMPLE #4: Terminal Server profile
# all ports at 38400 bps, 8N1
# syslogd IP 192.168.160.1
#
# remote authentication: performed by the host
# local authentication: performed first by the TSx000 and then by the host
# radius authentication: performed by the Radius Server and then by the host
#
# comment (all.authtype radius) and (all.speed 9600) above and replace
# them with the parameters below. According to the type of authentication
# wanted, uncomment the right "all.authtype" below.
#
# SAMPLE #4 Begin
#
# all.speed 38400
# all.authtype remote

# all.authtype local
# all.authtype radius
#
#s1.tty ttyS1
#s2.tty ttyS2
#s3.tty ttyS3
#s4.tty ttyS4
#s5.tty ttyS5
#s6.tty ttyS6
#s7.tty ttyS7
#s8.tty ttyS8
#s9.tty ttyS9
#s10.tty ttyS10
#s11.tty ttyS11
#s12.tty ttyS12
#s13.tty ttyS13
#s14.tty ttyS14
#s15.tty ttyS15
#s16.tty ttyS16
#s17.tty ttyS17
#s18.tty ttyS18
#s19.tty ttyS19
#s20.tty ttyS20
#s21.tty ttyS21
#s22.tty ttyS22
#s23.tty ttyS23
#s24.tty ttyS24
#s25.tty ttyS25
#s26.tty ttyS26
#s27.tty ttyS27
#s28.tty ttyS28
#s29.tty ttyS29
#s30.tty ttyS30
#s31.tty ttyS31
#s32.tty ttyS32
# SAMPLE #4 End
############################################################################

APPENDIX D CUSTOMIZATION
Everything related to the Cyclades-TS can be traced back to two files: /etc/rc.sysinit and /etc/
inittab. All Cyclades-TS application programs are started during boot by the init process. The related lines
in the /etc/inittab file are listed below:
# System initialization.
::sysinit:/etc/rc.sysinit
# Single user shell
ttyS0::respawn:/sbin/getty ttyS0 ansi
::respawn:/sbin/cy_wdt_led wdt led
# Cyclades RAS
::once:/sbin/snmpd
::once:/sbin/cy_buffering
::once:/sbin/cy_ras
::once:/sbin/sshd -f /etc/ssh/sshd_config
::once:/sbin/ex_ntpclient
To customize the Cyclades-TS, change these lines or add others. If the /etc/inittab file is changed, edit the /
etc/config_files file and add a line containing only “/etc/inittab”. Save the file and exit the editor. Save the new
configuration by executing saveconf. Then, the Cyclades-TS should be turned off and then turned on again.
This is necessary because the init program provided by Busybox, a tool that emulates rm, cp, etc., but uses
much less space, does not support the option ‘q’.
Cyclades provides a development kit which allows changes to be made to the Cyclades-TS’s software. However,
Cyclades does not provide free technical support for systems modified in this way. Any changes are the
responsability of the user.
Appendix D - Customization 82
Cyclades Corporation Cyclades South America
41829 Albrae Street Av. Santa Catarina, 155
Fremont, CA 94538 - USA 04635-000 São Paulo, SP, Brazil
Phone: (510) 770-9727 Phone: 55-11-5033-3333
Fax: (510) 770-0355 Fax: 55-11-5033-3388
www.cyclades.com www.cyclades.com.br
Cyclades Philippines Cyclades Germany

Unit 804, LTA Bldg. 118 Perea St. Klenzestrasse 9
Legaspi Village D-85737 Ismaning - Germany
Makati City Phillipines 1200 Phone: +49 (0)89 96 99 74-40
Phone: (632) 813-0353 Cyclades UK Fax: +49 (0)89 96 99 74-55
Fax: (632) 655-2610 Unit 6 Moorwell Road Business Park www.cyclades.de
www.ph.cyclades.com Scunthorpe, North Lincolnhire DN17 2RU - UK
Phone: +44 1724 277179
Fax: +44 1724 279981
www.uk.cyclades.com

Cyclades ts20br

Enviado por

Direitos autorais:

Formatos disponíveis

Cyclades ts20br

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Cyclades ts20br

Enviado por

Direitos autorais:

Formatos disponíveis

Cyclades-TS

FCC Warning Statement:

CAPÍTULO 1 - O QUE VOCÊ PRECISA SABER ANTES DE USAR O PRODUTO

Contrato de Licenciamento de Software

4. GARANTIA LIMITADA - 90 DIAS

Capítulo 1 - O Que Você Precisa Saber 5

How To Use This Manual

Seja um Usuário Registrado

• Suporte Técnico Gratuito

Importante: A Cyclades se reserva o direito de não oferecer suporte técnico e atualizações de

Como Obter a Garantia Lifetime

O Que a Garantia Lifetime Cyclades Cobre

O Que a Garantia Lifetime Cyclades Não Cobre

NOTA: Tipicamente estes danos são causados por:

2. Abuso, displicência ou imperícia no transporte, armazenagem, instalação ou uso do produto.

Suporte Técnico Gratuito

Como Entrar em Contato com a Assisência Técnica

Capítulo 1 - O Que Você Precisa Saber 9

O Que é o Cyclades Premium Partner (CPP)?

Capítulo 1 - O Que Você Precisa Saber 10

CHAPTER 2 WHAT IS IN THE BOX

On/Off Wall Outlet

Installation Manual Loop-Back Mounting Kit

FIGURE 2.1 CYCLADES-TS2000 AND CABLES

On/Off Wall Outlet

Installation Manual Loop-Back Mounting Kit

FIGURE 2.2 CYCLADES-TS1000 AND CABLES

Chapter 2 - What is in the Box 12

Back View Cyclades-TS800

Installation Manual Loop-Back

FIGURE 2.3 CYCLADES-TS800 AND CABLES

Chapter 2 - What is in the Box 13

Back View Cyclades-TS400

Modem Console Cable

FIGURE 2.4 CYCLADES-TS400 AND CABLES

Chapter 2 - What is in the Box 14

CHAPTER 3 SUMMARY OF THE CONFIGURATION PROCESS

• console access server,

The basic configuration steps are:

C.Modify the Linux files

Chapter 3 - Summary of the Configuration Process 15

E.Activate the changes.

G.Save the changes and restart the server application.

Chapter 3 - Summary of the Configuration Process 16

When the Cyclades-TS boots properly, a login banner will appear.

Radius Authentication Server,

FIGURE 4.1 CONSOLE SERVER APPLICATION

FIGURE 4.2 CONTENTS OF THE /ETC/HOSTNAME FILE

FIGURE 4.3 CONTENTS OF THE /ETC/HOSTS FILE

FIGURE 4.4 CONTENTS OF THE /ETC/RESOLV.CONF FILE

STEP THREE - CONSOLE SERVER

FIGURE 4.6 CONSOLE SERVER PSLAVE.CONF GLOBAL PARAMETERS

Parameter Description Value for

Parameter Description Value for

Parameter Description Value for

appendix for pin-out diagrams.

telnet 200.200.200.1 7001

STEP THREE - TERMINAL SERVER

FIGURE 4.8 TERMINAL SERVER APPLICATION