BaudBuddy

A serial terminal for Cisco switches on a Mac

Console settings that actually work, why pasting a config drops characters, and what to do when the terminal type matters more than you expected.

Cisco console ports have been 9600 8N1 with no flow control for about as long as Cisco has made them, and that is most of what you need. The rest of this is the handful of things that turn a working console into a frustrating one.

The settings

9600, 8 data bits, no parity, 1 stop bit, no flow control.

Newer platforms sometimes ship at 115200, and some let you change it in software, so if 9600 gives you rubbish rather than silence, try 115200 before anything else.

Flow control is the one that catches people. Set it to hardware, on a console cable with three wires and no handshake lines, and the terminal waits forever for a clear to send that will never arrive. You get perfect silence in both directions and no clue why.

The connection sheet with baud rate 9,600, data bits 8, parity none, stop bits 1 and flow control none, summarised as 9600 8-N-1

Give the connection a name and it comes back in one click, matched by the adapter’s serial number rather than a device path that changes when you move USB ports.

Nothing appears when you connect

Normal. A switch that is already running says nothing until you give it a reason. Press Enter twice.

If you get a login prompt, good. If you get nothing at all, the checks are: another program holding the port, the wrong device, flow control, or the wrong baud rate. Those are covered properly in the silent console guide.

Two commands worth typing first

terminal length 0

Turns off the pager. Without it, every long output stops at --More-- and waits for a space, which is fine when you are reading and infuriating when you are capturing.

show running-config

With the pager off and session logging on, that is your backup taken.

Why pasting a config drops characters

This is the single most useful thing on this page.

A console port has no flow control. When you paste two hundred lines into it, your Mac sends them at the full line rate and the switch processes them at whatever speed its CPU manages while also doing its actual job. When its input buffer fills, the extra characters do not queue. They are gone.

The result is a configuration that looks like it applied, with three lines mangled somewhere in the middle. Sometimes it is a missing character in an access list, which is worse than a syntax error because it parses.

Two fixes:

  • Pace the paste. Send it with a small delay between lines. Ten to twenty milliseconds is usually plenty, more on an old switch under load. BaudBuddy has this built in for exactly this reason.
  • Or do not paste at all. Put the config on a TFTP or SFTP server and have the switch fetch it. Slower to set up, impossible to corrupt.

If you have ever wondered why a config you pasted behaved differently from the one you copied, this was almost certainly it.

Terminal type actually matters here

Most of the time you can ignore terminal emulation. Cisco’s menu driven setup screens and a few diagnostic tools are the exception: they draw with escape sequences and expect the terminal to answer honestly about what it is.

If a screen draws as garbage or the arrow keys insert ^[[A instead of recalling a command, the terminal identity is wrong. vt100 and xterm both work for most Cisco work.

The related annoyance: if a terminal claims to be xterm-256color and then sends the function keys of something else, applications get confused in ways that are hard to attribute. Answering a device attributes request as exactly what you claimed to be is not a feature anyone notices until it is missing.

Logging, and why timestamps belong in the margin

Turn session logging on before you start, not after something interesting happens.

Two things are worth having. Byte exact raw output for anything you might need to prove later, and readable text for the version you will actually read. And timestamps drawn beside the output rather than inserted into it, because a timestamp in the middle of the stream corrupts the very thing you captured.

That distinction matters the first time you try to diff two captures and find your own timestamps in the way.

Rollover cables, and the port on the front

Console on older Catalyst gear is an RJ45 socket that is not Ethernet. It needs a rollover cable, the light blue one, which reverses the pin order. A straight patch lead will not work and will not tell you why.

Newer switches often have a USB mini-B or USB-C console port alongside it. That one appears on your Mac as a serial device directly, no adapter needed. Where both exist, plugging into USB usually disables the RJ45 port, which is occasionally a surprise when someone else is already connected.

Saved connections

The small thing that adds up: name a connection once, with its rate, its framing, its terminal type and its logging preference, and it comes back identically next time. Console settings differ between the Catalyst in the rack, the Fortigate next to it and the PDU below, and re-entering them each time is how you end up at 9600 on a device that wanted 115200, staring at silence and starting the whole diagnostic dance again.