Bootable files

[matthogue]

So I have done it. AP1200 series Access Point is Dead.

When attempting to upgrade the firmware, a few problems arose and the set BOOT command could not locate the file properly. So the JA3 file was deleted. And now there are no bootable files on the AP. Is there a fix for this, since there is no way to tftp a new firmware version into the AP. When trying to copy tftp sys, it says I have no permission. Does this require a return to Cisco, or is there a way for me to enable tftp to update the firmware correctly?

Thanks for any help, and I hope everyone is not laughing to hard at the fact that I have killed an Access Point.

[matthogue]

Rob,

Thanks for your help with my wireless issues in the past. I have a similar issue now.

When trying to reload the IOS image to a defective 1200 series AP through the steps above I am getting the following

ERROR: Failed to open archive file tftp://255.255.255.255/c1200-k9w7-tar.default

I have changed the IP of the connected laptop to 10.0.0.25 with 255.255.255.0. The tftp server is setup and pointing to the respective folder. Shouldnt the AP be looking for tftp://10.0.0.25/c1200.....?

Any help?

Also, on a separate issue, have you noticed any issues with

(C1240-K9W7-M), Version 12.4(3g)JA ?

I have a scenario with two AP's, one (C1240-K9W7-M), Version 12.3(8)JA2, and one with the 12.4(3g)JA. The 12.3 works fine and the 12.4 is having issues. I think someone on the network has a static IP and they are connecting to the network periodically, possibly causing the issues the users are experiencing.

Thanks,

Matt

[Rob Huffman]

Hey Matt,

Nice to hear from you again :)Sounds like a TFTP problem for sure :( The AP shouldn't be looking for the 255 address. Are you using the same machine for TFTP that you were succcessful with last time? Same TFTP Server?

Try these settings as well;

IP_ADDR 10.0.0.5

NETMASK 255.255.255.0

DEFAULT_ROUTER 10.0.0.1

Have a look at the details in the following threads that all have to do with TFTP. There are some great hints for troubleshooting TFTP problems from some of my favourite NetPros like ScottMac,Stephen from Cisco and Jack Young. The likely culprit may be that you need to uncheck "hide extensions for known file types" on your TFTP server;

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=WLAN%20Radio%20Standards&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddc042b/8#selected_message

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddc03c4/2#selected_message

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddbf271

Maybe try this (highly recommended version)

Solar Winds tftp

http://www.solarwinds.net/Tools/Free_tools/TFTP_Server/

The problem could be that the Laptop (used for TFTP) Operating System is hiding the known file type. From Internet Explorer, go into Tools > Folder Options > View, scroll down until you find the parameter Hide extensions for known file types, and uncheck the box.

As far as the 12.4(3) IOS we have switched to LWAPP so I can't give you much info but I have read about some issues with it here on the Forums.

Hope this helps! Good Luck!

Rob

[matthogue]

Rob,

I was using the same tftp server and laptop as previously had worked. I changed up and used the solarwinds server this time, which began the download... Igot part of it completed, then it states

the system is unable to boot automatically because there are no bootable files to boot.

It goes right back to the ap:

Even when part of the image file loaded it was still going to tftp://255.255.255.255/c1200-k9w7-tar.default

I am going to check the links you provided to see if that helps.

Thanks,

Matt

[matthogue]

BTW, the hide extensions for known file types was already unchecked but it still searches for 255.

:-(

[matthogue]

How's it going Rob? Hope all is well for the Holidays in your world.

I'll start easy with the question and then get into it.

Can you upgrade a Cisco AP350 from VxWorks to IOS using the conversion tool over a VPN connection?

I ask this knowing that our customer should be swapping out the APs for 1200 series units, but you know how it goes with customers. :)

When using the conversion tool, I am trying to connect to an AP on our enterprise network, pull its config file, and add it to the helper image i have on my laptop for the conversion tool to upgrade the 350 AP. I am able to telnet into the AP using both the CLI and the browser interfaces from this location as well.

The error I get when trying to gather Security Information from the source device is

Unable to detect source AP. Check:

1. Network Connectivity

2. User's capability

3. whether SNMP is enabled in the source AP.

The info below is from the browser interface of the AP:

Simple Network Management Protocol (SNMP): Enabled

System Description: Cisco 350 Series AP 12.02T1

Knowing all possible connections are valid, including the username/password are correct, network connectivity is active, SNMP is enabled, I am getting a tad baffled.

The only other thing outside of the VPN instance is that when logging in to the CLI of a 350 VxWorks, you have to enter the command :login before entering the username/pw. I am not exactly sure how the conversion tool is connecting to the AP, through TFTP or http, so how else would it not be able to connect to the device.

let me know if I can provide more info on this or if it is possible while on VPN.

thanks,

Matt

[Rob Huffman]

Hey Matt,

I almost missed your post here (I am glad I didn't) Hope all is well with you, I am only 8 hours away from a nice Holiday break!!

To be honest, I have never done this conversion so I'm afraid that I can't offer much help :( (you may want to open a new thread on this one).

There are a couple of RED Flags for me in this process which would certainly lead me to want to be on site for this work. If you run into any problems it sure looks like Console access plus the use of the Mode button would be a good thing!

Process Failure

If you do not have sufficient system DRAM resources, the upgrade process fails. Unless you make a console connection during the upgrade process, such a failure may not be readily visible. The only clear failure symptom is an unfamiliar blink pattern in the LEDs on the top of the unit.

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a008019fea0.shtml

If User Manager is disabled in your VxWorks access point and if you bypass the conversion tool's Security Configuration window, you can only log in on the upgraded access point using the console port.

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

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

Caution If User Manager is enabled in your VxWorks access point and if you bypass the conversion tool's Security Configuration window, you may not be able to log in on the upgraded access point. All access to the access point may be blocked (Telnet, browser, and the console port). If this occurs, you must reset the access point to defaults using the mode button.

http://www.cisco.com/en/US/docs/wireless/access_point/conversion/ios/administration/guide/MT_C4.html

Hope this helps and the best of the Holidays to you and yours!

Rob