Which console cable for accessing Cisco switch from a Mac?

[OMGponies]

I've acquired a Cisco WS-C3560CG-8PC-S that didn't come with a console cable. I've downloaded the hardware installation guide and getting started guide, and have able to reset the switch to factory defaults, and am attempting to run the express setup. I've had limited success with using the web gui available at 10.0.0.1. I've not been able to telnet to the switch, or connect with GNU screen.

My questions:
1. I'm connected to one of the RJ45 ports. Connecting to the console port doesn't get me anywhere. Do I need to use the USB (mini B) console port for configuration instead of RJ45? Do I need both kinds of console connections?
2. I'm using a Mac (with Safari and Firefox), and the product manual says I need to use a PC with Windows 2000, XP, Vista, or Windows Server 2003 to complete express set up. Is Windows really a requirement?

I've installed telnet, know how to ssh, and also how to use GNU screen, and if there's a way to interact with the hardware through the terminal I'd prefer that. I'd appreciate if someone could point me in the right direction. My initial goal is to get this set up as a dumb switch.

 

[ColinTaylor]

I've had limited success with using the web gui available at 10.0.0.1.

What is the problem?

If you don't have a Cisco RJ45 to DB9 serial cable, or a PC with a serial port, I suggest you get a USB A (or USB-C depending on what your Mac has) to USB Mini-B cable and see if the connection shows up on your Mac as a serial port.

 

[tgl]

I googled this question and found out that the "USB" console port has a doubtless-intentionally-nonstandard 5-pin connector, so it's unlikely to work with a normal USB Mini-B cable. I think you will need (a) an RJ45 to DB9 serial cable, and (b) a USB-to-serial adapter. Both are fairly easy to come by and not that expensive. I bought one of these a few years ago and had success driving some serial device or other with a Mac, the one time I used it.

 

[ColinTaylor]

I googled this question and found out that the "USB" console port has a doubtless-intentionally-nonstandard 5-pin connector, so it's unlikely to work with a normal USB Mini-B cable.

The 5-pin connector is the USB standard connector, as used by old digital cameras, PS3 controllers, etc. I've never seen any mention of a 4-pin version other than the warning in those Cisco instructions.

 

[tgl]

The 5-pin connector is the USB standard connector, as used by old digital cameras, PS3 controllers, etc. I've never seen any mention of a 4-pin version other than the warning in those Cisco instructions.

Oh, interesting. I wonder why they would bother to write that if 4-pin weren't a thing?

 

[OMGponies]

I’ve been able to get here by resetting the switch to default and plugging an ethernet cable into port 1 on the front panel:

The web console link gives me a 404 error, and I’m unable to open telnet from the menu, which is odd, because I did install it:

[Command not found: telnet]

[Could not create a new process and open a pseudo-tty.]

The other links do all work for me, although I thought there is an express setup program that is supposed to run at this stage.

My ethernet cable does nothing when I plug it into the console port. My understanding is that ethernet is not the same as USB when referring to a console port but I still don’t understand why a user might need two kinds of console cables. Why does the rj45 port exist?

It appears I need a usb cable like this. The documentation I'm looking at also mentions installing a driver (on Windows).

 

[ColinTaylor]

My ethernet cable does nothing when I plug it into the console port.

That's because that is not an ethernet port. As it explains in the manual, it is a serial port (e.g. RS232) for which you need the appropriate cable and a PC also with a serial port.

It appears I need a usb cable like this.

That appears to be the case. Although I'd wager that any USB Mini-B cable would work, so check your "old cables" bin.

 

[sfx2000]

The web console link gives me a 404 error, and I’m unable to open telnet from the menu, which is odd, because I did install it:

[Command not found: telnet]

[Could not create a new process and open a pseudo-tty.]

MacOS has removed telnet in more recent versions...

Telnet is available via HomeBrew - https://formulae.brew.sh/formula/telnet

Regarding the HTTP 404 error - just means that a resource wasn't found - could be anything, but with all the mitigations around web access, your browser might be blocking things proactively since the switch is not configured...

 

[tgl]

I found this relevant discussion about getting the "web console" to work:
https://community.cisco.com/t5/swit...possible-to-manage-a-2960-switch/td-p/1795219

 

[sfx2000]

I found this relevant discussion about getting the "web console" to work:
https://community.cisco.com/t5/swit...possible-to-manage-a-2960-switch/td-p/1795219

Gosh, this reminds me of all the work-arounds that had to be done with older gear - from IE6 dependencies to Java and deprecated API's...

Older gear to moved to End of Support for various reasons... and that's where OP's switch is.

 

[OMGponies]

I found this relevant discussion about getting the "web console" to work:
https://community.cisco.com/t5/swit...possible-to-manage-a-2960-switch/td-p/1795219

Thanks for this link. It was helpful to know others had the same issues as me.

In case it helps anyone in the future, I had an initial error with telnet:

Switch#Kerberos: No default realm defined for Kerberos!

but after I set default unset autologin in my .telnetrc, I was able connect to the switch from the terminal with telnet 10.0.0.1:

I will still need to get a console cable to access the console port.