Quick Answer / Summary: Classic console cable: RJ45 to DB9, rolled pinout (1-8, 2-7, 3-6, 4-5), connecting a PC’s serial port to the device’s console port. Modern Cisco gear adds USB Mini-B/Type-B console ports – one USB cable, no adapter. Terminal settings: 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control. A straight-through or crossover cable will not work – the rollover wiring is the product.
The Cisco console cable is the administrator’s last-resort link – the connection that works when the network does not. Its wiring is a rollover (pin 1 to 8, throughout), its legacy form ends in DB9 serial, its modern form ends in USB, and its terminal settings have not changed since the nineties. The page is the cable’s whole story.
The Rollover Wiring
The console cable’s eight conductors roll over: pin 1 lands on pin 8, pin 2 on pin 7, and so through the middle. The reversal distinguishes it from every ethernet patch in the drawer – and the wrong cable plugged into a console port connects nothing, silently. The DB9 end carries the RS-232 levels the PC’s serial port (or USB adapter) speaks; the RJ45 end keys into the console port the switch or router has carried since the first Catalyst.
The USB Console Generation
Modern Cisco devices add a USB Mini-B or Type-B console port that emulates the serial link over USB – one cable, no DB9, no adapter, and a driver that appears as a COM port. The USB console coexists with the RJ45 console; both speak the same protocol, and the management laptop that owns a Type-B port retires the serial adapter entirely. The USB cable is pinned as console – a generic charge cable without data lines connects nothing.
Terminal Settings: The Eternal 9600 8N1
The console’s serial parameters – 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control – have been constant across Cisco’s line for decades. The emulator (PuTTY, screen, minicom) takes those five values, opens the COM port, and the device’s banner answers. Garbled output means a baud mismatch; silence means the wrong cable, the wrong port, or a driver missing on USB.
The Kit and the Field Reality
The working console kit is short: the rollover cable, a USB-serial adapter for laptops without DB9 ports (FTDI-chipset adapters behave; the cheapest CH340 clones fight their drivers), and the terminal emulator preconfigured. Field reality adds two: the console port’s RJ45 is not ethernet – the label matters when both ports sit side by side – and the kit lives in the bag that travels, because the console session is by definition needed when everything else is broken.
Beyond Cisco: The Console Family
The rollover pinout is Cisco’s habit; other vendors rolled their own – some rollover, some straight, some with different DB9 pinouts – and the multi-vendor kit carries an adapter set rather than one cable. The honest bag labels each cable by vendor and pinout, because the drawer’s identical-looking cables differ by exactly the wiring that matters.
Beyond Cisco: The Console Family
The rollover pinout is Cisco habit; other vendors rolled their own – some rollover, some straight, some with different DB9 pinouts – and the multi-vendor kit carries an adapter set rather than one cable. The honest bag labels each cable by vendor and pinout, because the drawer identical-looking cables differ by exactly the wiring that matters.
Console Cable Reference
| Item | Classic | Modern |
|---|---|---|
| Cable | RJ45 to DB9, rollover | USB Mini-B / Type-B |
| PC side | Serial port or USB adapter | Direct USB, driver as COM port |
| Wiring | 1-8, 2-7, 3-6, 4-5 | USB console pins |
| Settings | 9600 8N1, no flow | Same |
| Failure mode | Straight/crossover used by mistake | Charge-only USB cable |
Real-World Application Scenarios
Recovering misconfigured switches when the network is down, initial-configuration of new routers, lab benches for certification study, and the management bag that travels to every site.
Recommended Internal Resources
Editorial Note: Internal linking recommendation: (1) Product cluster – https://zh-zong.com/productlist/ (anchor: Cisco console cables, USB console leads and FTDI USB-serial adapters); (2) Technical guide – https://zh-zong.com/ethernet-cable-guide/ (anchor: console and rollover cable guide); (3) Reference – https://zh-zong.com/faq/ (anchor: console cable questions answered).
Frequently Asked Questions (FAQ)
Q: Can I use a normal ethernet cable as a console cable?
A: No – console ports need the rollover wiring (pin 1 to 8 and so on), which a straight-through or crossover patch does not carry. The cable looks identical and connects nothing.
Q: Why is my console session showing garbled characters?
A: Baud mismatch – the console expects 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control. Reset the emulator’s serial settings and the banner becomes readable.
Q: Do modern Cisco devices still need the rollover cable?
A: They keep the RJ45 console port alongside a USB console port – the USB cable with data lines works alone. The rollover remains the fallback for gear whose USB console is disabled or unmanaged.