Once you have added a cascaded port you may enable Console Server Mode for this port, as you would for a local serial port on the master.
However it is important to be aware that by default SDT Connector uses the Telnet protocol/client to access serial ports on the gateway. It encrypts this Telnet data to secure the connection between the gateway and the SDT Connector client. So in the cascaded scenario the secure connection terminates at the Master (gateway) and the last hop between the Master and the Slave is unencrypted Telnet.
If this is an issue, here is how to secure the last hop of the connection:
- On the Master, click Serial Port -> Edit the cascaded port -> check SSH under Console Server Mode. Click Users & Groups and Add User. Enter a Username and Password, and check the cascaded serial port
- Launch SDT Connector. Select File -> New Gateway and enter the Address of the Master, and the newly created Username and Password
- Click OK, then Retrieve Hosts. A new Service is automatically created called Serial n SSH and added under Local Services for the Master. Use this button to securely connect to the serial port of the Slave.
Note: if the Serial n SSH button is disabled you must nominate an SSH client (e.g. Putty) for SDT Connector to invoke under Edit -> Preferences -> SSH client.