Search results

  1. P

    Aruba AP to IAP

    With your S/N, the hash for RW should be 64ffc0b716789ee9665c2986732c7665dd9ed9b4 You need to include country code when generate the hash, which is in this case "RW-CNDFHN7235"
  2. P

    Aruba AP to IAP

    It does not matter which os you are using as this process is under apboot. Yes (as answered in 1) Correct
  3. P

    Aruba AP to IAP

    Update for the hashcode, if you would like to change between US-RW do the following: Using SHA1 encode the string "US-AP S/N" or "RW-AP S/N" respectively (for exp: US-ABC12345) After that replace the hashcode accordingly from the converting command.
  4. P

    Aruba AP to IAP

    AP315 was released later after 324/325 so all of them have 512mb ram. Just be careful with the apboot version of batch that manufactured 2016 as it could not able to upgrade to os8 due to image size was limited to 14mb. Otherwise it can run on os6 perfectly fine.
  5. P

    Aruba AP to IAP

    The best way is asking for apboot cli screenshot. Otherwise try to avoid the DOM 2016 as these are first batch with lots of mixed up issue with ram and apboot(315 & 335 cannot upgrade to OS8) limitation.
  6. P

    Aruba AP to IAP

    There were 2 version of 325: One running with physical controller has only 256mb ram Others IAP or later AP version has full 512mb ram The 256mb ram version does not have enough ram to run os8, so better off with os6 or maximum can run os8.3.
  7. P

    Aruba AP to IAP

    The process below is converting AP to IAP only with console cable and no controller needed. Setup TFTP server with firmware ready and connect to the AP with Putty/Serial (Console cable) Stop the apboot by any key when see this message "Hit <Enter> to stop autoboot:3" proginv system ccode...