Cisco WLC (AIR-WLC2006-K9) Serial Cable
in [Cisco]
|
From: Hamzah Khan on 12 Feb 2010 07:29 On Wed, 10 Feb 2010 15:37:13 -0700, Aaron Leonard wrote: > Before you give up, you might want to consider the possibility that the > WLC's console has been set to some speed other than 9600 bps. I.e. you > might try setting one of the other speeds: > > > (tucson-wlc2006) >config serial baudrate ? > > [1200/2400/4800/9600/19200/38400/57600/115200] Enter serial speed. > > Good luck, > > Aaron Just went through all the speeds.... none of them worked. :( It must be dead. :'(
From: Hamzah Khan on 12 Feb 2010 07:31 On Tue, 09 Feb 2010 16:03:56 -0600, Hamzah Khan wrote: > I've been trying to get access to the CLI on a AIR-WLC2006-K9 WLC I > bought a few weeks ago as part of a lab kit, but have been very > unsuccessful. > > I've tried a straight-through serial cable, a null modem serial cable, > and two DB-9 to RJ45 serial cables (the type used with most Cisco > equipment) with an RJ45 coupler between them, but none of them seem to > work (no output on my terminal emulator). > > I've checked my terminal emulator (minicom) settings multiple times > (9600 baud, 8 data bits, 1 stop bit, no parity and no flow control), and > I'm sure they are correct anyway since these settings are the same for > all other Cisco routers, and it works fine on my 1841 and other routers. > I'm just having issues with this WLC. :( > > Is there a special type of cable I need to use for this WLC? > > Any clarification truly appreciated! > > Regards > > Hamzah Is there a way to perform a "restore to factory defaults" through hardware rather than through the CLI? :S (ie maybe change a jumper or something).
From: bod43 on 12 Feb 2010 08:07 On 12 Feb, 12:31, Hamzah Khan <ham...(a)removethis.hamzahkhan.com> wrote: > On Tue, 09 Feb 2010 16:03:56 -0600, Hamzah Khan wrote: > > I've been trying to get access to the CLI on a AIR-WLC2006-K9 WLC I > > bought a few weeks ago as part of a lab kit, but have been very > > unsuccessful. > Have you tried booting it with the console attached? You might get some messsages that indicate failure to complete startup? Maybe:-) As I think someone already mentioned maybe worth connecting a network analyser to it when it boots to see if it is sending out anything. You might be able to get an IP address for it that way. e.g. Wireshark which is free and very fine too.
From: Hamzah Khan on 12 Feb 2010 08:26 On Fri, 12 Feb 2010 05:07:43 -0800, bod43 wrote: > Have you tried booting it with the console attached? Yep, I have tried this. Nothing at all appears. > You might get some messsages that indicate failure to complete startup? > Maybe:-) > > As I think someone already mentioned maybe worth connecting a network > analyser to it when it boots to see if it is sending out anything. You > might be able to get an IP address for it that way. > > e.g. Wireshark which is free and very fine too. I have also tried using Wireshark to sniff any packets, but it doesn't seem to be sending anything out. :( The only thing I can think of is that it either has some bad setting which is stopping the console from working, and the ethernet ports are shutdown, or the WLC is dead. :( Regards Hamzah
From: Gary on 13 Feb 2010 01:30
Hamzah Khan wrote: > I have also tried using Wireshark to sniff any packets, but it doesn't > seem to be sending anything out. :( Did you plug everything in to a hub or a switch? For best results with dumb hardware and Wireshark, tcpdump, etc. always use a hub. I keep a couple of four ports hubs lying around for just such rare occasions. -Gary |