Can anyone help me to fix the issue we've encountered?
We have updated the AP230s to firmware version HiveOS 6.4r1e.2116. After
firmware update, the status LED doesn’t light up anymore (so no indication if it is at fault
or not). It can still use it though and still manageable from Hive Manager.
We had observed that it is rather blinking. Roughly 3 seconds ON (with white light) and 1 minute OFF (no light) and this manifestation is observable in all APs (AP230) they have perform an update.
One thing is for sure, the update was successful for all APs as it displayed in Hive Manager.Prior in updating the firmware all status LED of AP are "ON" and in normal operation.
I think this is a firmware related issue. How can we change it back to normal? Do we need to process RMA for this case?
Thanks in advance for your answer!
This is expected behaviour.
I suggest that you refer to the release notes for HiveOS 6.4r1e where this change is explained:
"Status LED Behavior
Aerohive access points include LEDs that can be used to assist installation, monitoring, and troubleshooting. Prior to this release, the default behavior of the AP130 and AP230 LED was to be on and illuminated at all times during normal AP operation. The new behavior of the AP130 and AP230 LED is to exhibit a long-period blink: The LED illuminates for 4 seconds, and then remains off for about one minute. There are no other changes to the operation of the access point.
This change is in response to a manufacturing defect reported by some customers that might cause the LEDs on the access point to become increasingly dim over time. This defect is largely cosmetic and does not alter or cause any loss of functionality to the product. That is, regardless of the condition of the LED over time, the performance and connectivity provided by your Aerohive network remains unchanged.
Customers who have reported this issue report a significant visual difference between the brightness of the LEDs on their units after nine to twelve months of continuous operation as compared to when the units were originally installed. This issue only exists in AP130s and AP230s, and, to date, has only been reported by AP230 customers, although not all units have been affected. The change in LED behavior allows the LED to continue to provide a visual indicator of the AP's health for those customers who use this feature, while significantly extending the life expectancy of the LEDs, in many cases to beyond the expected service life of the access point.
What You Need to Do
Aerohive recommends that you take steps to extend the life of the LEDs on your access points. Even if you do not typically rely on the LEDs for ongoing operations, taking action now will ensure that the LEDs are available to you if you need them in the future. This requires you to install an updated version of HiveOS. See "Updating Your Devices" on page 2 for instructions on how to update your devices.
By updating HiveOS by September 1, 2015, you ensure the continued, full protection of your Aerohive warranty. For further protection, customers who do not typically use the LEDs as part of ongoing operations can turn the LEDs off completely, then turn them on when needed for troubleshooting."
Thanks for the reply.
So it means it only stay "OFF" to extend LEDs life.
Does the LED will change the status or illuminate automatically if it encounters error on the AP?
I'm just quite worried not seeing the status of LED when it encounters error 'coz I'm not just relying on the HiveManager but also with the physical status of AP.
Yes, if an error condition occurs (such as loss of CAPWAP connectivity to the management platform, loss of backhaul ethernet connectivity, etc) then the orange Alarm LED will illuminate, and once the status returns to a normal condition then the white LED will resume it's slow blink.
We have heard many complaints about this LED Longevity behavior, and we have taken steps in some software under development right now to address many if not all of those complaints about lack of administrative control over this behavior.
Thanks to that! At least now I'm at ease that such error occurred will still be identified physically.
Again, many thanks!
Is it possible to decrease the brightness and keep it on or at least increase the rate of the status updates? Most of our staff identify a problem by looking at the LED. The techs will generally suspect bad cabling and loss of PoE if the AP LED turns off.
Yes. We are changing components and circuitry so that the white LEDs will have the originally expected operational life (many years instead of months) before they begin to dim with age. It will take some time for these newly created devices to percolate thru the retail pipeline.
Sorry, but there is no brightness control available for the AP230 or AP130 LEDs. They are illuminated, or not.
We are in the process of releasing new HiveOS images and the AP230 and AP130 images will incorporate LED behavior changes based on feedback we've received here, via Support tickets, and via late-night calls to my home (well, not that last one, but I suspect some people have been tempted to do so).
By default they will illuminate the white LED for 24 hours after booting up or a reboot. You will have administrative control over this delay as well as the intervals of time they are lit or unlit.
Chris, we did not intentionally use deficient LEDs or poor control circuitry, but there was an error on the datasheet for the LEDs used in these devices that caused us to essentially over-power them, leading to premature aging and therefore dimming of the LEDs. The LEDs still illuminate, but over time they become so dim that you cannot distinguish between lit and unlit. The device will continue to operate just fine, tho, and acknowledging how expensive it is for people to dismount units and send them back for RMA, we added the (original, poor) LED Longevity logic that got people so up in arms. We have changed our manufacturing process and LED circuitry in these devices so that units now being built at the factory won't experience this. The next couple releases of HiveOS for these platforms will auto-detect if they are suspectible to premature aging or not, and will make a local decision after boot-up whether to stay lit steadily if all is good or to go into the LED Longevity behavior. Additionally, the matching network management releases will examine your entire inventory of hardware and make a recommendation for all steadily lit or all in blinking mode, for consistent appearance within your organization. And, of course, you will be able to override this recommendation if you wish.
Dan, I hear you about the multi-color LEDs. I too liked them and wanted to retain them, but the responsible hardware product manager, the industrial design folks, and the user experience folks all had good reasons why white and amber were sufficient. I lost that battle.
When Aerohive introduced the power save feature for the LEDs, our Help Desk started receiving calls that the APs were no longer working. So we had to constantly tell users it was working, and explain the on/off nature.
And what has never been addressed by Aerohive is the fact that the AP370/390 has the same issue. I responded to a thread about this yesterday. Fortunately for us, we only have 10 AP370s. Three of which are at my site, so I can tell you that the white LED on all 3 are so dim you can't see them any more. One is a spare, so its LED is fine. And the other 6 are at other sites, but I'm sure they are in a similar situation.