mrncciew https://mrncciew.com/2012/10/20/lightweight-to-autonomous-conversion/
efore converting LWAP to Autonomous need to understand the type of OS image running on these platforms. I found following blog post is very useful to summarize the type of IOS & understanding its naming convention.
http://www.my80211.com/cisco-auton-labs/2011/11/19/understanding-cisco-access-point-ios-images.html
Following are the three type of IOS available & need to download the correct type before starting the conversion process.
- k9w7 – autonomous IOS
- k9w8 – full lightweight IOS (this is what is bundled in the WLC .aes image, and is factory installed on “mesh” APs)
- rcvk9w8 – lightweight recovery image – this is factory installed on lightweight APs, unless a “mesh” image is specified; it lacks radio firmware
In our case we require k9w7 for Autonomous conversion. More specifically c1140-k9w7-tar.124-25d.JA.tar as my AP is 1142.
To convert Lightweight AP to Autonomous AP, need to have PC directly connected to AP’s ethernet port. If you are powering AP from the switch (i.e use PoE) then PC & AP needs to be in two switch ports in the same vlan. In my example PC is 10.10.10.1/24 & AP is 10.10.10.102/24.
Console into the access point & do the following configurations.
AP5475.d0f5.2ee7#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Dot11Radio0 unassigned NO unset up up
Dot11Radio1 unassigned NO unset up up
GigabitEthernet0 unassigned YES DHCP up up
AP5475.d0f5.2ee7#debug capwap console cli <- without this line LWAP not accepting the conf t
AP5475.d0f5.2ee7#conf t
AP5475.d0f5.2ee7(config)#ip default-gateway 10.10.10.1
AP5475.d0f5.2ee7(config)#int g0
AP5475.d0f5.2ee7(config-if)#ip address 10.10.10.102 255.255.255.0
AP5475.d0f5.2ee7(config-if)#no sh
AP5475.d0f5.2ee7#ping 10.10.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.1, timeout is 2 seconds: !!!!!
AP5475.d0f5.2ee7#archive download-sw /force-reload /overwrite tftp://10.10.10.1/c1140-k9w7-tar.124-25d.JA.tar
"examining image...
Loading c1140-k9w7-tar.124-25d.JA.tar from 10.10.10.1 (via GigabitEthernet0): !
extracting info (283 bytes)
Image info:
Version Suffix: k9w7-.124-25d.JA ...................."
Once conversion process is over, you can verify the right image is on your access point.
ap>en
Password: <-- default password is Cisco
ap#
ap#sh version
Cisco IOS Software, C1140 Software (C1140-K9W7-M), Version 12.4(25d)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Thu 09-Dec-10 15:24 by prod_rel_team
ROM: Bootstrap program is C1140 boot loader
BOOTLDR: C1140 Boot Loader (C1140-BOOT-M) Version 12.4(18a)JA3, RELEASE SOFTWARE (fc1)
ap uptime is 0 minutes
System returned to ROM by reload
System image file is "flash:/c1140-k9w7-mx.124-25d.JA/c1140-k9w7-mx.124-25d.JA"
For the LWAP conversion, use the recovery image ( e.g c1140-rcvk9w8-tar.124-25d.JAL.tar). We can use the same command on the autonomous AP priviledge mode.
AP5475.d0f5.2ee7#archive download-sw /force-reload /overwrite tftp://10.10.10.1/c1140-rcvk9w8-tar.124-25d.JA.tar
Following Cisco Support Community forum video demonstrate teh above process.
https://supportforums.cisco.com/videos/
If you have WLC managed AP (currently registered to a WLC), then you can use WLC CLI command to convert that to Autonomous. In below example I have IW3702 AP on my WLC
(8540-TEST) >show ap summary
AP Name Slots AP Model Ethernet MAC Location Country IP Address
IW3702 2 IW3702-2E-Z-K9 2c:d0:2d:81:a6:5c default location AU 10.15.6.90
(WLC) >config ap tftp-downgrade ?
<TFTP Server IP addr> Enter the TFTP server's IP address
(WLC) >config ap tftp-downgrade x.x.x.x ?
<filename> Image file name on the TFTP server
(WLC) >config ap tftp-downgrade x.x.x.x ap3g2-k9w7-tar.153-3.JE.tar ?
<Cisco AP> Enter the name of the Cisco AP.
(WLC) >config ap tftp-downgrade x.x.x.x ap3g2-k9w7-tar.153-3.JE.tar IW3702
Once issue that command given AP should download new image from your TFTP server.efore converting LWAP to Autonomous need to understand the type of OS image running on these platforms. I found following blog post is very useful to summarize the type of IOS & understanding its naming convention.
http://www.my80211.com/cisco-auton-labs/2011/11/19/understanding-cisco-access-point-ios-images.html
Following are the three type of IOS available & need to download the correct type before starting the conversion process.
- k9w7 – autonomous IOS
- k9w8 – full lightweight IOS (this is what is bundled in the WLC .aes image, and is factory installed on “mesh” APs)
- rcvk9w8 – lightweight recovery image – this is factory installed on lightweight APs, unless a “mesh” image is specified; it lacks radio firmware
In our case we require k9w7 for Autonomous conversion. More specifically c1140-k9w7-tar.124-25d.JA.tar as my AP is 1142.
To convert Lightweight AP to Autonomous AP, need to have PC directly connected to AP’s ethernet port. If you are powering AP from the switch (i.e use PoE) then PC & AP needs to be in two switch ports in the same vlan. In my example PC is 10.10.10.1/24 & AP is 10.10.10.102/24.
Console into the access point & do the following configurations.
AP5475.d0f5.2ee7#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Dot11Radio0 unassigned NO unset up up
Dot11Radio1 unassigned NO unset up up
GigabitEthernet0 unassigned YES DHCP up up
AP5475.d0f5.2ee7#debug capwap console cli <- without this line LWAP not accepting the conf t
AP5475.d0f5.2ee7#conf t
AP5475.d0f5.2ee7(config)#ip default-gateway 10.10.10.1
AP5475.d0f5.2ee7(config)#int g0
AP5475.d0f5.2ee7(config-if)#ip address 10.10.10.102 255.255.255.0
AP5475.d0f5.2ee7(config-if)#no sh
AP5475.d0f5.2ee7#ping 10.10.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.1, timeout is 2 seconds: !!!!!
AP5475.d0f5.2ee7#archive download-sw /force-reload /overwrite tftp://10.10.10.1/c1140-k9w7-tar.124-25d.JA.tar
"examining image...
Loading c1140-k9w7-tar.124-25d.JA.tar from 10.10.10.1 (via GigabitEthernet0): !
extracting info (283 bytes)
Image info:
Version Suffix: k9w7-.124-25d.JA ...................."
Once conversion process is over, you can verify the right image is on your access point.
ap>en
Password: <-- default password is Cisco
ap#
ap#sh version
Cisco IOS Software, C1140 Software (C1140-K9W7-M), Version 12.4(25d)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Thu 09-Dec-10 15:24 by prod_rel_team
ROM: Bootstrap program is C1140 boot loader
BOOTLDR: C1140 Boot Loader (C1140-BOOT-M) Version 12.4(18a)JA3, RELEASE SOFTWARE (fc1)
ap uptime is 0 minutes
System returned to ROM by reload
System image file is "flash:/c1140-k9w7-mx.124-25d.JA/c1140-k9w7-mx.124-25d.JA"
For the LWAP conversion, use the recovery image ( e.g c1140-rcvk9w8-tar.124-25d.JAL.tar). We can use the same command on the autonomous AP priviledge mode.
AP5475.d0f5.2ee7#archive download-sw /force-reload /overwrite tftp://10.10.10.1/c1140-rcvk9w8-tar.124-25d.JA.tar
Following Cisco Support Community forum video demonstrate teh above process.
https://supportforums.cisco.com/videos/
If you have WLC managed AP (currently registered to a WLC), then you can use WLC CLI command to convert that to Autonomous. In below example I have IW3702 AP on my WLC
(8540-TEST) >show ap summary
AP Name Slots AP Model Ethernet MAC Location Country IP Address
IW3702 2 IW3702-2E-Z-K9 2c:d0:2d:81:a6:5c default location AU 10.15.6.90
(WLC) >config ap tftp-downgrade ?
<TFTP Server IP addr> Enter the TFTP server's IP address
(WLC) >config ap tftp-downgrade x.x.x.x ?
<filename> Image file name on the TFTP server
(WLC) >config ap tftp-downgrade x.x.x.x ap3g2-k9w7-tar.153-3.JE.tar ?
<Cisco AP> Enter the name of the Cisco AP.
(WLC) >config ap tftp-downgrade x.x.x.x ap3g2-k9w7-tar.153-3.JE.tar IW3702
Once issue that command given AP should download new image from your TFTP server.
PCMCIA ATA Flash PC Card imaging using OmniDrive 留言
The best source of information for utilizing the OmniDrive and the PC Card Manager software it comes with is the documentation that the device comes with — starting with the comprehensive help system contained in PC Card Manager’
"Help"menu.A copy of this document is available online.
I. Checking the OmniDrive
A quick way to determine if the OmniDrive, its drivers, and PC Card Manager are working is to
Menu: "Tools -> Analyze Card"Here, we used a 64MB ATA Flash PC Card, so the values populating the fields in the “ATA Card” section will likely look different than those you are deploying. What’s important is that the fields are filled in with values. If there are issues, see the begining of this document for instructions on checking the OmniControl utility to ensure that all the drivers and software packages are installed correctly.
II. Creating an image of a card
To create a byte-for-byte image (binary image) of the ATA Flash PC Card:
Menu: "Actions -> Copy -> Card to File(s)""New"in the"Copy Jobs"section"Source; File"click the ellipse"…"character"Save As"dialog perform the following:"Save in:"pop-up"File name:"field"Files of type"pop-up to"BIN files""Save""Source"the following attributes will be preset:"Copy"in the bottom of the"Copy: Card to File(s)"dialog. A progress indicator will appear."Copy Jobs; Address"III. Writing images to cards
The process for writing images to cards is very similar to the process above.
To write a byte-for-byte copy of a binary image to the ATA Flash PC Card:
Menu: "Actions -> Copy -> File(s) to Card""New"in the"Copy Jobs"sectionUnder
"Source; File"click the ellipse"…"characterChange
"Files of type"to"BIN files"and locate the file created in step II.5 above.Click
"Open". Like step II.6 above, there is no need to change the default values. Here, the attributes will be under"Target".They should read the same as discussed above:"Options"select"Write with verify"and click"Copy". A progress dialog appears."Source file"under"Copy Jobs". You may now eject the current PC Card and insert a new card."Copy"for all subsequent cards, and"Cancel"when you are done.Compares
A compare function, much like
cmpin Unix, is available to check cards to binary images. The process described in the document OmniDrive: Comparing .bin files to Linear Flash images would be the same for ATA Flash as it is for Linear Flash.