minicom and Cisco equipment issues

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Fri Jan 26 14:39:12 UTC 2007


On Fri, Jan 26, 2007 at 02:42:18PM +0300, Kihara Muriithi wrote:
> Hi pals,
> I wonder if someone have seen this problem before. I have not been able to
> use a usb-serial cable to get access to Cisco equipment. I am sure minicom
> is properly configured as I have used the same setting that I used on
> another box that works well with Ciscos. The main difference is the serial
> port. One has a real serial port while the other one emulate a serial port
> through a USB port.
>  The connection seems solid as I can see some Cisco CDP error message
> mixed up with a lot of gibberish on the console. I however can not interact
> with the console, and the only way out of it seem to kill the console. The
> device node is properly created, the kernel notice the interface insertion
> well -as inferred from the dmesg. I am at a loss at where else I can look
> for likely issue with this setup. Have someone encountered it and what was
> the solution? Advice
> 
> Thanks
> William
> 
> 
> Port Scan<*1>: S0   S1   S2   S3
> WvModem<*1>: Cannot get information for serial port.
> ttyUSB0<*1>: ATQ0 V1 E1 --
> AjQAjQAj/???+[???Aj/x;???[12][0f]???#[1b]WE???[1a]?[1f][1f];C??????E???{???^Z{[0b]??????j/???[12]???[??????z[???[07][12][0f]???#[1f]E????[1f][1f][1f];?????????E???{=[1f]???j[=???Q[??????x[Q'??????E???{[0f]^Z{[0b]+???[???'?????????E???{???^Z{[0b]??????j/???[12]???[??????
> ttyUSB0<*1>: failed with 2400 baud, next try: 9600 baud
> ttyUSB0<*1>: ATQ0 V1 E1 -- Backup-Switch>
> ttyUSB0<*1>: failed with 9600 baud, next try: 115200 baud
> ttyUSB0<*1>: ATQ0 V1 E1 --
> ttyUSB0<*1>: and failed too at 115200, giving up.
> 
> 
> atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
> atkbd.c: Unknown key released (translated set 2, code 0xd9 on
> isa0060/serio0).
> atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
> usb 2-1: new full speed USB device using uhci_hcd and address 2
> usb 2-1: configuration #1 chosen from 1 choice
> usbcore: registered new interface driver usbserial
> drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
> usbcore: registered new interface driver usbserial_generic
> drivers/usb/serial/usb-serial.c: USB Serial Driver core
> drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
> pl2303 2-1:1.0: pl2303 converter detected
> usb 2-1: pl2303 converter now attached to ttyUSB0
> usbcore: registered new interface driver pl2303
> drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver

I have used a pl2303 adapter recently, and was using it to talk to a USR
modem which worked perfectly.  No idea why it wouldn't work with a cisco
unless the cisco was broken.  Of course it could be the usb adapter is
defective, or maybe the cable you are using is defective.

Certainly the line '> ttyUSB0<*1>: ATQ0 V1 E1 -- Backup-Switch>' looks
like at 9600 (as expected) the cisco did send readable text.

--
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list