Converting 1131 series AP to Lightweight

Unanswered Question
Apr 29th, 2009

I am trying to convert an AP in Thailand from autonomous to lightweight through WCS. I was able to add the AP as autonomous in WCS, but when I try to convert it to lightweight it always fails on loading recovery image. I have turned on tftp debugging on the access point.

TFTP Event debugging is on

TFTP Packet debugging is on

DIEBOLDAIR1#

Apr 28 19:52:05.719: TFTP: Sending read request

Apr 28 19:52:06.073: TFTP: Received block 1, socket_id 0x10EE384

Apr 28 19:52:06.074: TFTP: Sending ACK for block 1, socket_id 0x10EE384

Apr 28 19:52:06.423: TFTP: Received block 2, socket_id 0x10EE384

Apr 28 19:52:06.423: TFTP: Sending ACK for block 2, socket_id 0x10EE384

Apr 28 19:52:06.775: TFTP: Received block 3, socket_id 0x10EE384

Apr 28 19:52:06.775: TFTP: Sending ACK for block 3, socket_id 0x10EE384

Apr 28 19:52:07.125: TFTP: Received block 4, socket_id 0x10EE384

Apr 28 19:52:07.125: TFTP: Sending ACK for block 4, socket_id 0x10EE384

Apr 28 19:52:07.475: TFTP: Received block 5, socket_id 0x10EE384

Apr 28 19:52:07.475: TFTP: Sending ACK for block 5, socket_id 0x10EE384

Apr 28 19:52:07.826: TFTP: Received block 6, socket_id 0x10EE384

Apr 28 19:52:07.826: TFTP: Sending ACK for block 6, socket_id 0x10EE384

Apr 28 19:52:08.176: TFTP: Received block 7, socket_id 0x10EE384

Apr 28 19:52:08.176: TFTP: Sending ACK for block 7, socket_id 0x10EE384

Apr 28 19:52:08.527: TFTP: Received block 8, socket_id 0x10EE384

Apr 28 19:52:08.527: TFTP: Sending ACK for block 8, socket_id 0x10EE384

Apr 28 19:52:08.527: TFTP: Sending error 0 Session terminated

Apr 28 19:52:08.529: TFTP: Sending read request

Apr 28 19:52:08.882: TFTP: Received block 1, socket_id 0x10F1D88

Apr 28 19:52:08.883: TFTP: Sending ACK for block 1, socket_id 0x10F1D88

Apr 28 19:52:09.233: TFTP: Received block 2, socket_id 0x10F1D88

Apr 28 19:52:09.233: TFTP: Sending ACK for block 2, socket_id 0x10F1D88

Apr 28 19:52:09.241: TFTP: Sending error 0 Session terminated

I am using a Cisco tftp server loaded on one of our servers. I can seeing the tftp session open, but it quickly fails giving me this error:

Wed Apr 29 19:56:03 2009: Sending 'c1100-rcvk9w8-tar.123-11JX1.tar' file to 10.175.86.61 in binary mode

#########

What I also do not understand is that I am trying to load this recovery image:

c1130-rcvk9w8-tar.124-10b.JA3.tar

yet the tftp server shows 'c1100-rcvk9w8-tar.123-11JX1.tar'

I have tried tftp'ing the file directly from the router to eliminate any latency issues and it still fails.

I'm running out of ideas.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
vancamt76 Wed, 04/29/2009 - 16:12

Okay nevermind on this. I tried creating a new migration template with the recovery image linked and it is working now. I think that because I was using an 1100 template and just changing the recovery image it was defaulting back to the 1100 image since I was not saving the template before selecting the AP. It all makes sense to me now.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode