Just wanted to update this thread with another known working config and known working USB-A cables.
I've been testing this with a customer in the USA.
Terminal Server: Lantronix SLC 8024
Terminal Server sw/fw version: 7.4.0.0R13
Cables tested as working:
https://www.amazon.com/dp/B07BK6P67K/ AND
https://www.amazon.com/dp/B075V1RGQKNo rollover adapter used.
Please note that to get this to work with terminal servers, you need to use the USB-A port which does not have an internal RS-232 chip. When connecting to a terminal server, one end of the connection is supported by an RS-232 chip inside the cable and the other end is supported by a RS-232 chip inside the terminal server. The USB-C port on the CX switches already has an internal RS-232 chip attached to it for console purposes. Any USB C or A to RJ45 serial cable will have an onboard RS-232 chip. If you attach such a cable to the USB-C port on the CX switch which has an internal RS-232 chip, it simply will not work because the cable ALSO has an RS-232 chip. I am not aware of any USB-C to RJ45 serial adapter cable which does not have an RS-232 chip on the cable. The reason there is an internal RS-232 chip on the USB-C console port on the CX switch is so any simple USB-C to USB-A cable can provide serial console access from a modern Mac, Linux, or Windows based PC without requiring special cables or drivers.
@ktakodra or
@Yash can PLM please confirm the updated version of the chipsets in this thread are officially supported? The cables I tested both have the FTDI FT232R chipset. What is stated in the thread is FT231X and PL3202. I haven't found any PL cables to work in my testing.
Screenshot of relevant Lantronix config:
Original Message:
Sent: Apr 30, 2021 09:52 AM
From: Chris B
Subject: Aruba CX and Console
Anyone have any solutions for CX console access? USB-C isn't ideal for customers like myself that have a large OOBM system that only uses RJ45 rollover cables. I've seen there are RJ45 to USB-C cables but I purchased one and it didn't seem to work so trying to find a solution here other than rip and replace all our console devices.