(this hidden command prevents the AP from reloading when it can't join a controller)Īnd create a DHCP scope with a fixed lease for the AP - you can do this on an IOS DHCP server with: If not, then the AP is going to cycle through DHCP release/renewal, and will possibly reboot, defeating your efforts to load in the autonomous IOS, unless you take the following steps: If the AP is now joined to a WLC, then proceed to the Archive Command step below. The above command is necessary in order to permit you to enter the archive command. 12.4(18a)JA (5.2) or above - enter this hidden command: If the AP is running a CAPWAP image - i.e. one prior to 12.4(18a)JA (5.2) - then first enter the following hidden command. If the AP is running a pre-CAPWAP image - i.e.
You may also use a TELNET/SSH session to the AP, if and only if it is running a lightweight IOS version of 12.4(21a)JA2 (6.0.188.0), 12.4(10b)JDE (4.2.209.0), or above. Next, set up a terminal session to the AP's CLI (exec.) This can be done with an asynchronous serial connection to the AP console, from a terminal emulator program such as PuTTY. In this case, we will use 1, the aIOS image for the 1260 series AP. Put the desired aIOS (k9w7) image on the TFTP server. Put the TFTP server somewhere on the network where the AP can reach it via IP. the k9w7 feature set) on an access point running lightweight IOS.Īs the first step, set up a TFTP server as needed. This tip shows how to install an autonomous IOS image (i.e. Installing Autonomous IOS (aIOS) on a Lightweight AP from the CLI
0 kommentar(er)
