Cisco USB-USB console and umodem driver

A

AndHag

More and more equipment (switches and router) only have an USB port as the console port.
As an example, the new C9200CX do not have a RS232 port but only USB.

FreeBSD uses the umodem driver in combination with the ucom driver to connect the hardware chip
to a /dev/cuaUX device file.

All this works as it should and I can do "cu -l cuaU0 -s 9600" and get a connect.
But no text at all.

Windows, MacOS and Linux have working drivers.
The umodem driver from NetBSD hasn´t been touched in a long time.


How can we fix this?
 
AndHag said:
FreeBSD uses the umodem driver in combination with the ucom driver to connect the hardware chip
Click to expand...
Depends on the hardware, there's also a uftdi(4) driver for FTDI specific chips. Or umoscom(4), uplcom(4), uslcom(4), uvscom(4), and probably a couple more I forgot.

AndHag said:
All this works as it should and I can do "cu -l cuaU0 -s 9600" and get a connect.
Click to expand...
Try 115200 speed. Modern equipment tends to set the serial speed a lot faster by default.
 
Sometimes that USB port fronts a serial device, like an FTDI chip.
I've got some NetGate devices running pfSense. Console is a serial device port is USB-C.
I connect doing something like:
tip ucom1 -115200

So however you are connecting, baud rate and "bits per character" are the most important to get characters.
You may need to actually be root before doing cu or tip commands
 
Thank you for all advices, but the question is not how to use the cu command. It is how to connect to Cisco USB console. They use Silicon Labs chip CP210x or Cisco chip and 9600, 8N. They have downloadable drivers for Windows and on mac it just works.

I use Freebsd every day. I use Cisco every dag. But this USB console forces me to use windows.
 
You must log in or register to reply here.
Back
Top