02-24-2007 07:28 PM - edited 03-05-2019 02:33 PM
I have two 5505's with one Sup. III module each. I can't get either 5505 to communicate via the console port at all. The PC shows the Com port is connnected, but no matter what, I get no communication with the switches.
Is there something different about doing this on a 5505 than. say, a 1924? Also, how do you do a factory reset? Does the reset button come into play? Could that help me get console communication with the switches?
Thanks!!
02-24-2007 10:29 PM
Are you using the correct console cable?
Are your com: parameters set correctly? The default for cisco equipment is 9600:8:N:1:None.
02-25-2007 02:45 AM
Hi,
I do have the com port settings set to 9600:8:N:1:None as I would for other Cisco routers/switches. No go.
I am using a standard Cisco console cable, but when the link you sent says to use a "straight-through" cable, are they talking about something different? Would using a "straight-through" cable
The prob is too, if these switches have been altered from the default com port settings, then I can't tell and might be fighting a losing battle. If I can find out how to do a factory reset of the switch
Thoughts?
Appreciate the response!
02-25-2007 09:16 AM
The 5500 do no use the "standard" rolled console cable (which is wired pin 1 to pin 8, pin 2 to pin 7, etc.)they need a cable wired straight through (i.e. pin 1 to pin 1, pin 2 to pin2, etc)
I typically use a plain old CAT5 ethernet cable to connect to a conslole port on the 5500's
02-25-2007 11:10 AM
Then that's probably my issue. I need to find a local shop in KC that sells RJ45 to DB9 adapters so that, instead of using the Cisco console cable, I would use a true cat5 cable. I'll give that a shot. Thanks all!!
02-25-2007 10:52 AM
I suggest you sort out the cable problem first. Usually, if the cable is correct but the line settings are not, you'll see some garbled output. When that happens, you can change settings (baud rate first) until you see something legible.
02-25-2007 02:30 PM
Understood. Like I'd said, I'm comfortable with console connections and port settings, as I've configured other models successfully. But I also know that the settings can be majorly changed on the switch, making it appear you can't get a connection. I'm sure it's just me using the wrong cable.
Thanks!
02-26-2007 07:19 PM
Ok, I bought the DB9 to RJ45 adapter. Wired it the way the diagram online shows for a straight through cable. Still no connection to the console on two different 5505 switches. I'm thinking now that either I have the adapter pinouts wrong, or else I still need to reset the switches
Help help!
Carl
02-26-2007 09:38 PM
Here is another document for the 5500 recovery. There is no mention of a "factory reset" procedure.
What happens when you try to telnet into the switch?
02-27-2007 07:44 AM
I don't get any response trying to connect to the switch. As far as telnet specifically, I am not sure what the config is set to and it doesn't seem to allow a telnet connection
I reviewed the link you gave, and again the core issue is not even being able to get a CLI prompt period. So, no way to issue commands.
When I bought the DB9 to RJ45 adapter, I pinned it to match the pinout diagram that would be for a standard Cat5 network cable to DB9 connection. So, that should be good. Yet, from two different PCs, nothing. Hyperterminal shows the Com port is connected
It's got to be a communication prob, because of the inability to get a CLI.
07-03-2016 05:58 PM
I too had the same problem, I resolve it by using a straight through ethernet cable and adapter to usb serial interface and under console interface, the console listing came up after using putty com3 and xon/xoff setting. Hope this helps... you.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide