A Console tip

Unanswered Question
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
scottmac Tue, 03/06/2007 - 10:23
User Badges:
  • Green, 3000 points or more

Verify that you have no handshake enabled (no hardware, no software).


Good Luck


Scott


Thanks for your answer Scott,


but my console configuration is working fine in another Cisco devices, I have the console problem only with brand new AP?s, in fact, I have installed some of them, and all they have the same problem, I thing it is a new condition in them but...I do not know.


Can somebody help me ???


Martin



spanlink Wed, 06/27/2007 - 13:00
User Badges:

I have the same problem here. We have some 1231Gs and console doesn't work. If I'm consoled into it while I turn it on I can see it boot up, but it doesn't seem to respond to any commands I send it.


It's very frustrating.

Rob Huffman Thu, 06/28/2007 - 11:25
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Nick,


It sounds like you might have ended up with a Lightweight AP (LAP1231 Part#) instead of an IOS AP. This can be fixed;


Reverting the Access Point Back to Autonomous Mode


http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp161272


You can convert an access point from lightweight mode back to autonomous mode by loading a Cisco IOS Release that supports autonomous mode (Cisco IOS release 12.3(7)JA or earlier). If the access point is associated to a controller, you can use the controller to load the Cisco IOS release. If the access point is not associated to a controller, you can load the Cisco IOS release using TFTP.


Using a TFTP Server to Return to a Previous Release


Follow these steps to revert from LWAPP mode to autonomous mode by loading a Cisco IOS release using a TFTP server:



--------------------------------------------------------------------------------


Step 1 The static IP address of the PC on which your TFTP server software runs should be between 10.0.0.2 and 10.0.0.30.


Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point) in the TFTP server folder and that the TFTP server is activated.


Step 3 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point, c1130-k9w7-tar.default for an 1130 series access point, and c1240-k9w7-tar.default for a 1240 series access point.


Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.


Step 5 Disconnect power from the access point.


Step 6 Press and hold MODE while you reconnect power to the access point.


Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds) and then release.


Step 8 Wait until the access point reboots, as indicated by all LEDs turning green followed by the Status LED blinking green.


Step 9 After the access point reboots, reconfigure it using the GUI or the CLI.


From this doc;


http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp161272


Hope this helps!

Rob



spanlink Thu, 06/28/2007 - 12:51
User Badges:

Eh... Make sure that Flow control is set to "none", not "hardware". It was working on all other Cisco devices I tried, but I'm still quite embarrassed.


Thanks for your help. : )

Actions

This Discussion