Wireless Access

last person joined: 17 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

Problem with AP-105 Checksum bad

This thread has been viewed 5 times

  • 1.  Problem with AP-105 Checksum bad

    Posted Aug 16, 2012 01:56 PM

    I have and AP-105 that is registering a checksum bad.

     

    I plugged it into so I could provision it and it never showed up on my list of ap's

     

    so I hooked up a console cable to it and this is the output.  I have tried to purge the ap and that hasnt worked either.  All it does is what is shown in the putty output.  I let the unit just set their and just keeps saying checksum bad...

     

     

    any help would be appericated

     

     


    APBoot 1.2.4.4 (build 26618)
    Built: 2011-01-07 at 13:42:04

    Model: AP-10x
    CPU: AR7161 revision: A2
    Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
    DRAM: 128 MB
    POST1: passed
    Copy: done
    Flash: 16 MB
    PCI: scanning bus 0 ...
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 168c 0029 00002 01 10000000 00000000 00000000 00000000
    01 00 168c 0029 00002 01 10010000 00000000 00000000 00000000
    Net: eth0
    Radio: ar922x#0, ar922x#1

    Hit <Enter> to stop autoboot: 0
    Checking image @ 0xbf100000
    Invalid image format version: 0xffffffff
    Checking image @ 0xbf800000
    Invalid image format version: 0xffffffff
    eth0 up: 100 Mb/s full duplex
    DHCP broadcast 1
    invalid RARP header
    DHCP broadcast 2
    DHCP IP address: 170.117.132.49
    DHCP subnet mask: 255.255.240.0
    DHCP def gateway: 170.117.128.1
    DHCP DNS server: 170.117.137.2
    DHCP DNS domain: cmc-nh.org
    ADP multicast 1
    ADP broadcast 1
    ADP multicast 2
    invalid RARP header
    ADP broadcast 2
    checksum bad
    ADP multicast 3

    Retry count exceeded
    DNS request 1 for aruba-master.cmc-nh.org to 170.117.137.2
    T Using eth0 device
    TFTP from server 170.117.137.162; our IP address is 170.117.132.49
    Filename 'mips32.ari'.
    Load address: 0x2000000
    Loading: invalid RARP header
    T T T T T T T T invalid RARP header
    T T
    Retry count exceeded; starting again
    eth0 up: 100 Mb/s full duplex
    checksum bad
    checksum bad
    checksum bad
    invalid RARP header
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad
    checksum bad

     



  • 2.  RE: Problem with AP-105 Checksum bad

    Posted Aug 16, 2012 02:01 PM
    Does this IP 170.117.137.162 belong to your controller?
    It looks like the mips32.ari AP image that you are downloading from the TFTP server is corrupt and you would have to get a clean image.


  • 3.  RE: Problem with AP-105 Checksum bad

    Posted Aug 16, 2012 02:34 PM

    Yes the 170.117.137.162 belongs to the controller.   However I have been able to provision more access points after this one in questions.  We have 50 ap's I am provisioning and the AP in question is number 20 and I have already configured 12 more since then with no problem.



  • 4.  RE: Problem with AP-105 Checksum bad

    Posted Aug 16, 2012 04:44 PM
    snewell,

    Can you try connecting the AP directly to the controller port ? If that is not possible then try changing the switch port to which the AP is connected to.

    If the above two does not help then please open a case with support.

    Thanks,


  • 5.  RE: Problem with AP-105 Checksum bad

    Posted Aug 17, 2012 08:19 AM

    Thanks HT I will have to call in and open a support ticket as I already have it plugged into a port on the controller to configure the aps.  that is where the message came from

     



  • 6.  RE: Problem with AP-105 Checksum bad

    Posted Oct 17, 2012 05:58 AM

    Hi there,

     

    have some similar issue here, got some AP124 with old APboot 1.0.8.3  which came up with invalid_image 0xFFFFFFFF , i tested on some ArubaOS 6.1.3.4 controller, then i reminded that once there were issues with APs with older APboot, so i plugged into some controller with 5.0.4.7 and it came properly up and was able to be provisioned.

     

    i dont get the clue again to put the latest Apboot on it so it comes also up on OS 6.x , anyone ?

     



  • 7.  RE: Problem with AP-105 Checksum bad

    Posted Oct 17, 2012 06:01 AM

    i think its in the apboot menu with "upgrade" , but dont have the command , i will check again KB and guide and will post later i think i can fix this by myself

     

    @cjoseph , give me 20minutes before you post ;-)