Aironet 1252 IOS Upgrade Radio Failure

Did anyone else learn this the hard way?  I upgraded a bunch of 1252's using my WLSE to 12.4(21a)JA1 and the radio's crapped out after the upgrade.  I've found references to having to have to shutdown the radios before the IOS upgrade.  What's up with that?
brian

Nope.  I have autonomous and LWAP APs running this IOS version and I have no issues about it.  Can you post the logs during bootup?

Similar Messages

  • Which Aironet 1252 radio module(s)

    I was going to use an Aironet 1252 access point to set up a wireless network and was wondering which radio module (or modules) to get. I have no need for backwards compatibility, so it seems that for best performance I should go with a pure 802.11n network. In order to achieve that goal, is one radio module sufficient? And which band would be best? Or is there any advantage (or disadvantage to getting both the 2.4 GHz radio module (AIR-RM1252G-A-K9) and the 5 GHz one (AIR-RM1252A-A-K9)?
    Any and all suggestions or thoughts are greatly appreciated. Oh, and if you need any other information about my setup please feel free to ask.
    Thanks,
    Paul

    fella5 is right. You've just mentioned the need for backward compatibility therefore both A/B/G modules is OK.
    Are you going to be using a Wireles LAN Controller (WLC)?
    The reason why I'm asking is because the 1252 AP, in order to get both RM to work, you need at least 19.0 watts of power. This can only be achieved using either a enhanced PoE switch (such as the 3560-E/3750-E) or a power injector.
    The latest code of the WLC (firmware 5.2) will upgrade the AVR of both the radio modules of the 1250 to be able to operate at 15.4 watts of power. Here's the catch though: The new WLC code will allow the 1252 to operate both radios BUT the power output (or signal strength) is curtailed.
    However, do you look the 1140 series AP. This model will operate at 15.4 watts of power, full signal strength but the range is not as far as the 1250.
    The 1140 (like it's other brother, 1130) was designed for office use: lots of walls, partitions and corners. The 1250 is designed for industrial use: wide-open space, environmental protection (thus the armoured-tank look-feel-weight).
    Hope this helps.

  • Aironet 1300 AG IOS upgrade

    could somebody give me a doc with the steps to perform an IOS upgrade for the APs
    thank you

    Hi Cris,
    Working with Software Images
    This section describes how to archive (download and upload) software image files, which contain the system software, IOS code, radio firmware, and the web management HTML files.
    Cisco IOS Software Configuration Guide for Cisco Aironet 1300 Series Outdoor Access Point/Bridge 12.3(7)JA
    http://www.cisco.com/en/US/docs/wireless/access_point/1300/12.3_7_JA/configuration/guide/b37mfw.html#wp1035507
    Hope this helps!
    Rob

  • Aironet 1252 firmware update for official N?

    Hi, we currently own several Aironet 1252 WAP with the N draft. Is there a firmware update to the official 802.11N? If so, where can I locate the firmware?
    Our WAP is the "AIR-AP1252G-A-K9" model.

    The 1250, by default, was designed specifically for 802.11N in mind. What you need to do is to get the configurations correct to operate.
    The latest firmwares that updates the APs are the 12.4(10b)JDA3 and 12.4(21a)JA1. The former upgrades the firmwares for both radio modules to version 2.00.22. The latter upgrades the radios further to 2.10.19. Now this is not just number. The upgrades (either one) allows the AP to operate both radios with only 15.4 watts of power. There's a "cost" associated to it and it's lower MCS rates.
    Hope this helps.

  • Wlc 5508 ios upgrade in ha mode

    I am having 2 wlc 5508 in HA mode, and want to upgrade ios from 7.5 to 7.6
    Current IOS file status in primary and secondary.
    Primary  WLC IOS :  AIR-CT5500-K9-7-5-102-0.aes
    Standby WLC IOS :  AIR-CT5500-LDPE-K9-7-5-102-0.aes
    HA WLC ios upgrade procedure is when we  upgrade ios in primary wlc it will push to standby wlc and if earlier ios version match it will accept it.
    ISSUE : If you check in wlc status detail I have given upper both has same ios version but IOS file are different and currently in HA mode and working.
    Now I am trying to upgrade IOS it is not allow me to upgrade it.
    Giving below error :
    TFTP receive complete... extracting components.
    Checking Version Built.
    Image version check passed.
    Informing the standby to start the transfer download process
    Waiting for the Transfer & Validation result from Standby.
    Standby - Standby receive complete... extracting components.
    Standby - Checking Version Built.
    Standby - Image version check passed.
    Standby - Transfer failure : Upgrade from non LDPE to LDPE software is not allowed.
    Please download AIR-CT5500-K9-x-x-x-x.aes image instead.
    Transfer & Validation on Standby failed.
    Transfer download failed both on Active & Standby, Please retry download
    (Cisco Controller) >
    Please suggest how I can upgrade IOS in HA mode.

    Primary WLC IOS : AIR-CT5500-K9-7-5-102-0.aes
    Standby WLC IOS : AIR-CT5500-LDPE-K9-7-5-102-0.aes
    This won't work and you'll see from the error message.  Your standby WLC has a particular firmware loaded with LDPE enabled.  So first, you need to answer if you need LDPE or not.   
    Both firmwares has to match, including LDPE.  If you need LDPE, the your primary has to be loaded with LDPE before you can proceed.  If you don't need LDPE, then you need to downgrade the secondary to non-LDPE version before you can proceed.

  • POE 3560 Issue after IOS upgrade

    Hello,
    I having issue where 6 WLAN AP's not coming back uo after reboot and IOS upgrade of 3560 POE swtiches - . Prior to changes here most if not all ALL the 23 Aps were mainly on one switch, Now after these changes they are now spread over three switches ( 3560's) - with 17 coming back on line
    I am sure its not the power limitation of the switch(s) as the one switch I am TS at present had a fairly large allocation of the aps attached prior to ios upgrade and reload. and the available power value now showing is applicable.for 8 AP's
    I have tried various TS steps to try and bring them back up - A couple of things I would like to try but I am restricted to do so is to check the APS physically or downgrade the ios!
    Any input on this matter would be truly appreciated.- (attached is the log buffer debug)
    res
    Paul

    c3560-ipbase-mz.122-25.SEE2.bin
    You upgraded the IOS to the switch?  I shudder at the thought of what old version did you upgrade FROM.  
    Available:370.0(w) Used:110.4(w) Remaining:259.6(w)
    You've got more than enough PoE left. 
    Only two things comes to my mind:  
    1.   Cable issue - Unfortunately, the 3560 is a non-GigabitEthernet and this particular sub-model does NOT support TDR.
    2.  Hardware failure - Read THIS.

  • Aironet 1252 bridge and 802.11n

    Hi,
    I have two Cisco Aironet 1252  that I want to configure as a point-2-point bridge. Now I want to know if this configuration supports the 802.11n protocol.
    Regards,
    Screech

    Scott,
    I found the following statemen in the release note of IOS 12.4 (25d) (http://www.cisco.com/en/US/docs/wireless/access_point/ios/release/notes/12_4_25d._JArn.html#wp291685)
    802.11n HT Rates Apply Only to No Encryption or WPA2/AES Encryption
    The 802.11n HT rates apply only to no encryption or WPA2/AES encryption. They do not apply to WEP or WPA encryption. If WEP or TKIP encryption is used, the 1250 series access points and any 802.11n Draft 2.0 clients will not transmit at the HT rates. Legacy rates (802.11a/b/g) will be used for any clients using WEP or TKIP encryption
    Given this statement how do I configure AES encryption on the aironets 1252 that are configured in bridge mode as I do not see this option. If possible please provide steps using the web interface.
    Regards,
    Screech

  • Cisco 4500X IOS upgrade through ISSU

    Hi,
    I am having 2 number of cisco 4500x switch and configured with VSS
    so one switch is active and another switch is standby.
    I am panning to upgrade IOS through ISSU
    i read in document that it required auto boot enable in switch.
    My switch current Configuration register = 0x2101
    do i need to change config register or this will ok. If need to change then what will be auto boot and after IOS upgrade do i need to change it again.
    Please help....

    Hello Tarun,
    Please find below the steps to perform the ISSU:
    ISSU Prerequisites
    Before one can perform an ISSU, there are a few prerequisites one must verify for a successful ISSU. The following list explains what is initially required.
    • Must be using a redundant Cisco Catalyst 4500 switch with symmetric hardware (that is, supervisors, memory, rommon, NFL daughter card, and so on).
    • Both new and old Cisco IOS Software images must be preloaded to the file system on both supervisors.
    • SSO must be configured and working properly.
    • Config register must be configured to autoboot (that is, the value should have a "2" in the lowest byte).
    45010R-203# sh bootvar | i register
    Configuration register is 0x2102
    Standby Configuration register is 0x2102
    Several commands are available to verify if SSO is enabled:
    4510R-203# sh module | b Redundancy
    Mod  Redundancy role     Operating mode      Redundancy status
    ----+-------------------+-------------------+-------------------
     1   Standby Supervisor   SSO                  Standby hot        
     2   Active Supervisor    SSO                 Active
    45010R-203# sh redundancy states 
           my state = 13 -ACTIVE 
         peer state = 8   -STANDBY HOT 
               Mode = Duplex
               Unit = Secondary
            Unit ID = 2
    Redundancy Mode (Operational) =  Stateful Switchover
    Redundancy Mode (Configured)  =  Stateful Switchover
    Redundancy State              =  Stateful Switchover
                 <snip>
    4507R-ISSU# sh run | b redundancy
    redundancy
     mode  sso
    As a step prior to the beginning of the ISSU process, the new version of the Cisco IOS Software image needs to be loaded into both the active and standby supervisors' file systems. Both active and standby supervisor need to contain both the new and old images in the file system. In order to store both new and old images, the supervisors should be upgraded to contain sufficient amounts of flash memory prior to the ISSU process.
    The new images can be downloaded into both supervisors using commands such as:
    copy tftp: bootflash:
    copy tftp: slavebootflash: 
    The example below illustrates this verification:
    4510R-203#dir
    Directory of bootflash:/
    1  -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
    2  -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
    4510R-203#dir slavebootflash:
    Directory of slavebootflash:/
    1  -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
    2  -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1 
    Once this check is verified, one can now proceed with the ISSU process.
    The ISSU process is started by typing the "issu loadversion" command on the active supervisor. This command directs the active supervisor to begin the ISSU process. The active supervisor, through intersupervisor communications, checks that the requested image has been downloaded into both the active and standby supervisors' file systems. If the required images are not present, the command is rejected, and an appropriate warning is generated.
    If the "issu loadversion" command is successful, the switch transitions into the "Load Version" ISSU state. The standby supervisor will reset and boot with the new version of the Cisco IOS Software image loaded into the file system.
    The following actions take place when the command is implemented:
    1. The standby supervisor (B) is reset.
    2. The standby supervisor (B) is booted with the new Cisco IOS Software image: Release 12.2(31)SGA1.
    3. If both Cisco IOS Software images are declared as compatible, the standby supervisor moves into SSO mode and is fully stateful for all compatible clients and applications. Compatibility allows for in-service software upgrade or downgrade between two versions to succeed with minimal service effect.
    4. If both Cisco IOS Software images are incompatible, the system moves into RPR mode, and the ISSU process is terminated with an appropriate message to the user. Images are declared incompatible when "required" clients or applications are not interoperable between two Cisco IOS Software releases.
    5. Standby "B" reaches the standby HOT state.
    6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
    7. The "issu loadversion" command also supports a "forced" option that allows the operator to force the system into entering RPR mode when incompatibility is detected.
    Note: When performing an ISSU, disable manual switchovers. Performing manual switchovers during the issu process is strongly discouraged. The current implementation does not prevent it, but it does display a warning to the user.
    An example of the CLI for implementing the issu loadversion command is displayed below.
    On the active supervisor, one would issue the following command:
    4510R-203#issu loadversion 1 bootflash:cat4500-entservices-mz.122-31.SGA1 2 slavebootflash: cat4500-entservices-mz.122-31.SGA1
    Syntax - issu loadversion active-slot active-image-new standby-slot standby-image-new
    The second step of the ISSU process is to perform the issu runversion CLI.
    The user can issue the " issu runversion" command when:
    1. The ISSU state is "Load Version"; this can be verified with the "show issu state detail" CLI.
    2. The standby supervisor is running the new version of the software.
    3. The standby supervisor has moved into the "Standby Hot " state.
    The following actions take place when the " issu runversion" command is executed:
    1. A switchover occurs; that is, the standby (B) becomes the new active, and the old active (A) is rebooted and comes up as a standby.
    2. A timer called "Rollback Timer" is started with a previously configured value.
    3. Move both supervisors to "Run Version" state.
    4. If the command "issu acceptversion" is not issued before the "Rollback timer" fires, then the entire ISSU process is aborted via the automatic rollback.
    5. If the active supervisor console connectivity is established and the "issu acceptversion" command is issued, then the rollback timer is stopped.
    6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
    An example of the CLI for implementing the issu runversion command is displayed below:
    On the active supervisor, one would issue the following command:
    4510R-203#issu runversion 2 slavebootflash:cat4500-entservices-mz.122-31.SGA1
    Syntax - issu runversion standby-slot [standby-image-new]
    Prior to issuing the `issu acceptversion' command the system will be counting down the rollback timer. If `issu acceptversion' is not completed before rollback timer expires an automatic abort will occur. This command stops the "Rollback Timer." This command serves as a feedback mechanism. This is an optional command and can be skipped in the ISSU process with the "issu commitversion" CLI.
    If this command is not issued within 45 minutes (default) from the time the standby supervisor moves into the "Standby Hot" state, it is assumed that the new active supervisor is not reachable and the entire ISSU process is rolled back to the previous version of the software. The acceptversion is not intended for long-term network operation. It is also important to note that none of the features available on the new version will work yet.
    The following actions take place when the command is implemented:
    1. The "Rollback Timer" is terminated. This means that the rollback timer is not looked at anymore. Therefore, the system can run in this state for an extended period.
    2. The user has an option to abort the ISSU process by issuing the command "issu abortversion."
    Aborting the ISSU process now causes the newly active supervisor (B) to fail over to the standby supervisor (A) running the old image and will also cause the rebooting supervisor (B) to load the original image. The issu acceptversion halts the rollback timer and helps ensure the ISSU process is not automatically aborted during the process.
    An example of the CLI for implementing the issu acceptversion command is displayed below:
    On the "New" active supervisor, one would issue the following command:
    4510R-203#issu acceptversion 2
    % Rollback timer stopped. Please issue the commitversion command.
    Syntax - issu acceptversion active-slot-number
    This is the last stage of the ISSU procedure. Once the user is satisfied with the new version of software, this must be committed by issuing the "issu commitversion" command. This command resets the standby supervisor and boots it with a new version of the software (same as the active supervisor). This concludes the ISSU process, and the new version of software is permanently committed on both supervisors. Since this is the conclusion of the ISSU process, the system can not be reverted back to the previous version of the software from this point onward as a part of this upgrade cycle. However, if for any reason users wish to go back to the previous version of the software, they can do so by starting a new upgrade/downgrade process.
    The following actions take place if the command is implemented:
    1. The standby supervisor (A) is reset and booted with the new version of Cisco IOS Software image.
    2. The standby supervisor (A) moves into the "Standby Hot" state in SSO mode and is fully stateful for all clients/applications that are compatible.
    3. Both supervisors are moved into "Final State," which is the same as "Initial State."
    4. Users can initiate switchovers from this point onward.
    An example of the CLI for implementing the issu commitversion command is displayed below:
    4510R-203#issu commitversion 1
    Syntax - issu commitversion standby-slot-number
    ISSU Process: issu abortversion
    One can abort the ISSU process at any stage manually (prior to issuing the issu commitversion command) by issuing the exec-level issu abortversion command. The ISSU process also aborts on its own if the software detects a failure.
    If a user aborts the process after issuing the issu loadversion command, then the standby supervisor engine is reset and reloaded with the original software.
    If the process is aborted after a user enters either the issu runversion or issu acceptversion command, then a second switchover is performed to the new standby supervisor engine that is still running the original software version.
    The supervisor engine that had been running the new software is reset and reloaded with the original software version. The command is accepted only in "Load Version" or "Run Version" states. In "Load Version" state, the active supervisor is running an old image and the standby supervisor is running new image.
    Syntax - issu abortversion active-slot [active-image-new]
    Let me know if you have any questions.

  • Aironet 1131 AG upgrade

    Hi,
    I need to upgrade my APs to c1130-k9w7-tar.123-8.JA2.tar
    Could you please provide me with some documentation on how to do it
    thank you
    Cris

    Hi Cris,
    Here are the methods for 1100 Series AP's;
    Working with Software Images
    This section describes how to archive (download and upload) software image files, which contain the system software, IOS code, radio firmware, and the web management HTML files.
    http://www.cisco.com/en/US/docs/wireless/access_point/12.2_15_JA/configuration/guide/s15mfw.html#wp1035507
    Hope this helps!
    Rob

  • Aironet 1252 doesn't broadcast SSID and VLANs

    Best regards.
    I have an autonomus AP Aironet 1252 (software version: 12.4(18a)JA1)
    I configured 3 SSID and VLANs, but the AP doesn't broadcast SSID, the vlans are working fine because I tested configuring manually the hide SSID on laptops.
    Also the AP broadcasts the SSID whe only one SSID is configured!!!
    How I can do the AP to broadcast all SSIDs?
    Thanks in advance.

    From the command line of your AP.
    Change each SSID as follows.  You want to turn off "guest-mode" and enable "mbssid" at each SSID.  Guest-mode will only broadcast one SSID, you must use mbssid  to allow all SSIDs to broadcast.
    #config t
    #dot11 ssid
    #no guest-mode
    #mbssid
    Now from each radio
    #int d0
    #mbssid
    #int d1
    #mbssid

  • Aironet 1252 Boot Error

    Hi Guys,
    I need a help with an Aironet 1252 which is failing on boot. When power on the access-point shows the error below.
    WARNING: A memory error occurred during the system start-up
    self-test.  The device must be serviced if the error persists.
    The following commands can, optionally, be used to initialize
    the flash file system and the TFTP file transfer system:
    But when this happen, I can start the IOS manually doing flash_init and boot in ROMMON. After do this commands, the access-point starts and works normally.
    How can I check and correct the memory and solve this issue? Anyone had an idea?
    Thanks

    Hi,
    Yes, it looks like you will need to have the unit RMAd, if you like you could try the mode button procedure to reload the IOS to the AP and reset the AP to defaults as a last option.

  • Apple iPad 3. BT email not working. Cannot send emails from btconnect SMTP after iOS upgrade. This is the only difference I am aware of. Can anyone help me please.

    BT email not working. Cannot send emails from btconnect SMTP after iOS upgrade. This is the only difference I am aware of. Apple iPad 3. Can anyone help me please.

    All resolved at last
    Deleted the SMTP setting
    Recreated the SMTP using the same settings
    Able to send emails now
    No logic - as usual - just a bug!

  • Since an ios upgrade on my ipod, my device no longer appears in itunes or my computer

    Since a recent ios upgrade, I can not locate my Ipod touch 5th generation in iTunes nor in My Computer. I am working with Windows 7. I have uninstalled and reinstalled itunes, quicktime and Apple Mobile Device Support software programs. I have also gone through the on line Apple Trouble shooting support for this problem with no success.
    I did have WiFi syncing turned on before the upgrade and now when I go into settings on my iPod, the sync now option is greyed out.
    Any other ideas please...

    OK, never mind. After all that, a restart of the iPhone fixed it. That should have been the first thing I tried, of course, before posting. Sorry about that!

  • I bought a Sandisk Connect Media Drive, downloaded the app from iTunes.  Before iOS 8, movies played fine.  After iOS upgrade I can no longer play movies downloaded from iTunes to the media drive.  Anyone else have a similar issue?

    I bought a Sandisk Connect Media Drive, downloaded the app from iTunes.  Before iOS 8, movies played fine.  After iOS upgrade I can no longer play movies downloaded from iTunes to the media drive.  Anyone else have a similar issue?

    I checked with SanDisk's own online support and they indicate that they have notified Apple of the issue.
    According to SanDisk, the problem lies with Apple not having the iOS 8 version of the Safari browser having DRM decoding enabled that the Media Drive relies upon to decode and play iTunes DRM titles. Non DRM encoded videos will play in the browser.
    DRM audio is not effected as this is handled by the native iOS music app.
    As of the date of this post SanDisk have not been given a timeframe by Apple for this issue to be resolved.
    I hope that Apple resolves this issue quickly as I have a large collection of DRM video titles on a 128Mb memory card installed in the Media Drive that I am unable to view.

  • IPAD Mini Locked after iOS upgrade, tried reset on iPAD did not work, plugged in and device not appearing in iTUNEs for reset/restore

    PAD Mini Locked after iOS upgrade, tried reset on iPAD did not work, plugged in and device not appearing in iTUNEs for reset/restore.  Just get an Apple Logo then a flashing blue screen as if it is caught booting up.   This has happened twice before and iTunes restore fixed it.  But this time device not appearing in iTunes.
    Running iTunes for PC.  But as stated restore has worked before!  Any help greatly appreciated!!

    Place the device in DFU mode and let iTunes restore the device to factory condition.

Maybe you are looking for