AMP does not officially support the Vx-to-IOS upgrade function; that is, it is not well tested (the process is irreversable, so extremely difficult to test). It is theoretically possible to do the conversion Using_AMP, by using it to push the IOS conversion image to the APs under the right conditions.
There are very specific parameters for how the APs should be set beforehand, and how they will wind up afterwards. Aside from that one specific step in the process, there are several other ways in which AMP can help:
1. WLAN inventory: discover all the APs on your network, determine which ones are running VxWorks and which ones have been upgraded to IOS; snapshot the current configuration of those VxWorks APs that you are targetting for upgrade to IOS.
2. Prepare APs for upgrade: the image used to do the VxWorks-to-IOS conversion only works from certain versions of VxWorks. specifically, you can use AMP to upgrade your VxWorks APs to version 12.02T1, the last version for which the conversion works; additionally, there are specific requirements for available memory on the AP for the conversion to succeed; you could use AMP to restore most of the configurable settings to factory defaults and free up additonal memory if needed.
After these two steps you can attempt to push the IOS conversion image either from AMP, or upload it manually to the AP. After this, the AP will have a factory default configuration, and will attempt to get an address via DHCP.
3. Rediscover converted APs: after conversion to IOS, they will appear as "New Devices" on the network - with the generic name of 'ap'; AMP would rediscover them and allow you to correlate with the old version of the AP by matching the LAN MAC addresses.
4. Configure SNMP - AMP can enable and configure SNMP so that the newly converted devices are managable
5. Reapply configuration: you can use AMP to re-apply the configuration according to your desired policy, referencing the settings as the device was configured before it was upgraded.
The upgrade process is tedious no matter what, and it will wind up taking a longer amount of time than for the usual firmware update. But AMP can take a bite out of that time and make the process easier.
Referenced documents:
http://www.cisco.com/warp/public/102/wlan/AP1200upgrade.pdf
http://www.cisco.com/univercd/cc/td/doc/product/wireless/airo1200/accsspts/tool3ios/mt_ap_a.htm
AMP does not officially support the Vx-to-IOS upgrade function; that is, it is not well tested (the process is irreversable, so extremely difficult to test). It is theoretically possible to do the conversion Using_AMP, by using it to push the IOS conversion image to the APs under the right conditions.
There are very specific parameters for how the APs should be set beforehand, and how they will wind up afterwards. Aside from that one specific step in the process, there are several other ways in which AMP can help:
1. WLAN inventory: discover all the APs on your network, determine which ones are running VxWorks and which ones have been upgraded to IOS; snapshot the current configuration of those VxWorks APs that you are targetting for upgrade to IOS.
2. Prepare APs for upgrade: the image used to do the VxWorks-to-IOS conversion only works from certain versions of VxWorks. specifically, you can use AMP to upgrade your VxWorks APs to version 12.02T1, the last version for which the conversion works; additionally, there are specific requirements for available memory on the AP for the conversion to succeed; you could use AMP to restore most of the configurable settings to factory defaults and free up additonal memory if needed.
After these two steps you can attempt to push the IOS conversion image either from AMP, or upload it manually to the AP. After this, the AP will have a factory default configuration, and will attempt to get an address via DHCP.
3. Rediscover converted APs: after conversion to IOS, they will appear as "New Devices" on the network - with the generic name of 'ap'; AMP would rediscover them and allow you to correlate with the old version of the AP by matching the LAN MAC addresses.
4. Configure SNMP - AMP can enable and configure SNMP so that the newly converted devices are managable
5. Reapply configuration: you can use AMP to re-apply the configuration according to your desired policy, referencing the settings as the device was configured before it was upgraded.
The upgrade process is tedious no matter what, and it will wind up taking a longer amount of time than for the usual firmware update. But AMP can take a bite out of that time and make the process easier.
Referenced documents:
http://www.cisco.com/warp/public/102/wlan/AP1200upgrade.pdf
http://www.cisco.com/univercd/cc/td/doc/product/wireless/airo1200/accsspts/tool3ios/mt_ap_a.htm