Daniel Rysztak wrote:

>Don't blast me, but I know that Windows HyperTerm, TeraTerm and obviously
>others work.  To rule out a bad port on the Linux box or minicom (which I've
>never tried, but I'm sure works) try a Windows machine running one of those.
>If it doesn't work on that, bad port or bad cable.  It at least cuts the
>problem area in half.

Great suggestion!  Thank you, Daniel!

I booted one of my systems into MS Windows 2000, started HyperTerminal,
created a simple "profile" for COM1 (ttyS0) and pressed return.

I was "greeted" by the Catalyst 1900 Management Console initial screen.
This means that the cable must be OK (I had no doubt about that - I
built it and continuity/short tested it). ;)  This also means that (at
least the serial console part of) the Catalyst 1900 is also working.

Sometimes, it's useful to use MS Windows on a rare occasion (once a
year) for a few minutes before it crashes. :)

I could proceed using MS Windows 2000 and HyperTerminal, but I would
prefer to use GNU/Linux and minicom or another open source terminal
program that runs on GNU/Linux.  Does minicom require special
configuration to run on a serial port?  Is there another open source
program more appropriate to the task?

Sincerely,

Ken Fuchs <kfuchs at winternet.com>

>-----Original Message-----
>From: tclug-list-bounces at mn-linux.org
>[mailto:tclug-list-bounces at mn-linux.org]On Behalf Of Ken Fuchs
>Sent: Monday, March 29, 2004 9:03 PM
>To: TCLUG Mailing List
>Subject: [TCLUG] Serial console access to Cisco Catalyst 1900
>
>
>I'm trying to access my Catalyst 1900 via the serial console.
>
>I built a DB9 to RJ-45 cable by cutting a DB9 cable and RJ-45 cable in
>half and soldering the appropriate ends together as defined here:
>
>http://www.hardwarebook.net/cable/serial/cuscoconsole9.html
>
>It is based on:
>
>http://www.cisco.com/univercd/cc/td/doc/product/lan/28201900/1928v8x/19icg8x
>/19icinst.htm
>
>The cable I built is identical to the cable described in this Cisco
>manual, except it is a single piece cable (doesn't have crossover RJ-45
>and RJ-45 crossover to DB9 adapter and separate modules).
>
>------
>
>I can't seem to establish a serial connection between my Linux PC serial
>port and the Catalyst 1900.  I'm using minicom.  I've tried using
>/dev/ttyS0, /dev/ttyS1, /dev/ttyS2, and /dev/ttyS3 to no avail.  I'm not
>even sure the serial ports on this machine work, since I've never tried
>to use them before.  (I have an internal modem at /dev/ttyS4 that worked
>a few years ago, but is now broken.)  I've set the port to 9600, 8 bits,
>no parity, 1 stop bit, and no flow control just as specified by the 1900
>manual.
>
>I assume the 1900 should send something to the serial console when it
>powers up.  It probably should also send something when it receives
>something from the serial console as well.
>
>Does anyone have any suggestions concerning establishing a serial
>connection with the Cisco Catalyst 1900's serial console?
>
>Sincerely,
>
>Ken Fuchs <kfuchs at winternet.com>
>
>_______________________________________________
>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
>http://www.mn-linux.org tclug-list at mn-linux.org
>https://mailman.real-time.com/mailman/listinfo/tclug-list
>
>
>_______________________________________________
>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
>http://www.mn-linux.org tclug-list at mn-linux.org
>https://mailman.real-time.com/mailman/listinfo/tclug-list
>

_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
http://www.mn-linux.org tclug-list at mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-list