Wireless Access

last person joined: 15 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Dead AP, don't know if by natural death or radiation induced.

This thread has been viewed 0 times

  • 1.  Dead AP, don't know if by natural death or radiation induced.

    Posted Sep 02, 2013 11:36 AM

    Hello,

    We have an Aruba networks installation deployed inside of a synchrotron. Suddenly one of the access points, an AP61, died after 4 years of service. Is the first one on this installation that dies.

    The dead one was installed on a place where it is exposed to radiation. The nearest radiation sensor accounts for an acumulated dose of 1172 mSv caused by photons and 100 mSv by neutrons.

     

    I've tried to connect to it using the serial adapter. I get a responsive console, but after some seconds it hangs and stop responding. At the end of the post I pasted the log.

     

    I would like to know the cause of the death. Because i have 10 access points on this kind of places where they are exposed and i would like to know if I have to start to dig 10 more graves.

     

    Regards

     

    APBoot 1.5.5 (build taylor@harpua-ENG.0000)
    Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

    CPU: AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
    Board: Merlot, Local Bus at 90 MHz
    DRAM: 32 MB
    POST: passed
    FLASH: 4 MB
    Net: en0 lo0

    Hit <Enter> to stop autoboot: 1

    APBoot 1.5.5 (build taylor@harpua-ENG.0000)
    Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

    CPU: AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
    Board: Merlot, Local Bus at 90 MHz
    DRAM: 32 MB
    POST: mem 0 (Mismatch at a0018a3c: Expected f554df69 got f554df49) FAILED!
    FLASH: 4 MB
    Net: en0 lo0

    Hit <Enter> to stop autoboot: 2

    APBoot 1.5.5 (build taylor@harpua-ENG.0000)
    Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

    CPU: AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
    Board: Merlot, Local Bus at 90 MHz
    DRAM: 32 MB
    POST: passed
    FLASH: 4 MB
    Net: en0 lo0

    Hit <Enter> to stop autoboot: 0
    apboot>
    apboot>
    apboot>
    apboot> purge
    Erasing....
    Programming....
    Verifying....
    apboot>

     

    APBoot 1.5.5 (build taylor@harpua-ENG.0000)
    Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

    CPU: AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
    Board: Merlot, Local Bus at 90 MHz
    DRAM: 32 MB
    POST: passed
    FLASH: 4 MB
    Net: en0 lo0

    Hit <Enter> to stop autoboot: 0
    Loading FLASH image @ 0xbfc40000... not present
    Loading FLASH image @ 0xbfc80000...
    Verifying checksum...

     

    As you can see I was trying to factory reset the AP but it doesn't help.

     



  • 2.  RE: Dead AP, don't know if by natural death or radiation induced.

    EMPLOYEE
    Posted Sep 03, 2013 08:18 AM

    For issues like this (quite interesteing by the way), I would definitely open a case and request a failure analysis.



  • 3.  RE: Dead AP, don't know if by natural death or radiation induced.

    Posted Sep 04, 2013 05:11 PM

    The only way to get to the root cause of a failure like this would be to have the ap in hand. I'd follow Seth's recomendations, open a tac case.

    When you get a root cause please post back and let us know. I have some customers where radiation might be an issue. 

     

    What is your radiation from? 



  • 4.  RE: Dead AP, don't know if by natural death or radiation induced.

    Posted Sep 05, 2013 03:53 AM

    Hello, thanks for the advice. I will try to do that.

    Our radiation cames from a synchrotron, a particle accelerator. Is not from a radioactive material.

    http://en.wikipedia.org/wiki/Synchrotron

     

    Regards