Cyclades TS1000 configuration
Although we will only work on CAS mode, the device supports different modes of operation which drastically change the behaviour and features offered. these modes are:
CAS Console Access Server
This a the common 'console server' where various device consoles (switches, servers and equipment) have their serial console connection connected to the device and the device allows you to manage them remotely in a secure way.
In this mode we can understand the the CAS client (you) connect from the network to the device and the device provide you access to the serial consoles.
RAS Remote Access Server
This works as a multiplexed modem, where multiple modems (lines) are connected to the serial ports of the device. Each line (i.e. a dialin phone line) is able to access the device which provide network access to the remote users connected through the lines.
In this mode we can see the clients as the remote folks who dialed one of the serial modems connected to the device and the device provides them access to the network.
TS Terminal Server
In this mode there are standard (old) physcial serial terminals (screen+keyboard) connected to the serial ports of the device. The device provide shell access to the servers on the networks from the serial terminals connected to it.
In this mode the clients would be the users using the serial terminals connected to the device which redirects their console to server connected to the network.
Making changes
The main configuration file for the service provided (either CAS, RAS or TS) is the /etc/portslave/pslave.conf
file.
/etc/portslave/pslave.conf
file.
After modifying you need to signal the daemon to reload the configuration:
signal_ras hup
To save the configuration (we recommend both locally for reboots and remotely for backup):
saveconf saveconf tftp bin <tftp-ip> <filename>
Data buffering
If correctly configured, the device logs or records the data which pass through the serial ports.
This data by default is save locally under /var/run/DB/ directory, but due the hardware limitations of the device and storage space this may not be enough.
To enable data buffer set this higher than 0 (the number is the local filesize limit)
all.data_buffering 4194304
Please check documentation to store it into a NFS exported volume or even forward them to a remote syslog server. Below some quick hints on how to do it:
NFS configuraiton
conf.nfs_data_buffering nas:/srv/console/
SysLog forwarding
all.DB_user_logs on all.syslog_buffering 4096 all.syslog_sess 0 all.DB_timestamp 1 conf.DB_facility 6 (syslog local facility num)
Then you need to edit and tune the /etc/syslog-ng.conf
file to properly configure syslog