Service manual

Chapter 6 Configuration 42

Cyclades-TS Installation & Service Manual

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 serial console port with the same parameters. Also make sure that the computer is

configured to route console data to its serial console port (Console Redirection).

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

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.

NOTE: It is possible to access the serial ports from Microsoft stations using some off-the-shelf packages. Although

Cyclades is not liable for those packages, successful tests were done using at least one of them. From the

application’s viewpoint running on a Microsoft station, the remote serial port works like a regular COM port. All the

I/O with the serial device attached to the Cyclades-TS is done through socket connections opened by these

packages and a COM port is emulated to the application.