Wireless Access

last person joined: yesterday 

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

Move RAPS from controller on 6.5 to new controller deployment on 8.3

This thread has been viewed 3 times

  • 1.  Move RAPS from controller on 6.5 to new controller deployment on 8.3

    Posted Jul 06, 2018 11:48 AM

    Hi. 

    What is required to move a RAP from a controller on 6.5 to a controller on 8.3.0.1. I want to change the external NATed IP address from the 6.5 to the 8.3 controller.  Initial concern is what IP to map the NAT to on 8.3 ( VMM cluster with 7210 controller cluster), and will RAPs update firmware?

     

    old version 6.5.3.1

    new version 8.3.0.1

    RAP 203RP 

     



  • 2.  RE: Move RAPS from controller on 6.5 to new controller deployment on 8.3

    EMPLOYEE
    Posted Jul 06, 2018 12:11 PM

    You may want to start here if you haven't already:

    https://community.arubanetworks.com/t5/Wireless-Access/AOS-8-Fundamentals-Guide/td-p/433747

     

    The initial concern would be the 7210s. You mentioned the controllers are clustered. Currently, cluster configurations with RAP do not support NAT. Because of how the nodelist is used for controller discovery with cluster configurations, the controllers would need to have public IPs in order for a cluster to work. If the controllers are not clustered, the NAT deployment similar to what was deployed in 6.5 would still work.



  • 3.  RE: Move RAPS from controller on 6.5 to new controller deployment on 8.3

    Posted Jul 06, 2018 05:16 PM

    Dear 

     

    We upgrade our 7010 from 6.5 to 8.2 in cpboot by the command upgrade 

    Why when it reboot, we can not get into cpboot again, the Mad watchdos reboot one by one!

     

    Secure Boot Enabled on the Processor

    Bank: Secondary Watchdog
    CPLD: rev: 3.0 (30:8008|32:0004|33:0000|34:0000|35:0000)
    PRID: 000C1203
    POWER ON RESET CFG:30CC0FF2
    Initialized I2C0 Controller.
    Initialized I2C1 Controller.
    SPD Rev:0x11 DIMM:0 Type:2 Speed:666MHz #Rank:1
    DDR3: Node 0 Channel 0 Mem size = 4096 MB UDIMM
    set freq:666666
    DDR3: Node 0 DRAM frequency 666 MHz
    DDR3: Node 0 CPU frequency 800 MHz
    mtb_ps:125 clock:1500 trc:33 trcd:9 trp:9
    AP3:A0CFFF0 ODTP1:10000
    Board DDR VDD set to 1.5V.
    N:0 CH:0 additional rdlvl rdly:1
    N:0 Ch:0 m:32 s:32 R OK.
    Rank:0 HW WLVL Passed Mask:1FF
    AP3:A0CFFF0 ODTP1:10000
    n:0 ch:0 RTT WR:0200
    ===N:0 Ch:0 m:32 s:32 RW OK.
    Node:0 Ch:0 TGE Set Memory:4096 MB value:FF FF -- PASS
    Node:0 Ch:0 TGE Set Memory:4096 MB value:FF 00 -- PASS
    Node:0 Ch:0 TGE Set Memory:4096 MB value:AA 55 -- PASS
    Node:0 Ch:0 TGE Set Memory:4096 MB value:00 00 -- PASS

    DDR3 Initialization Passed.
    NBU0 DRAM BAR0 base: 00000000 limit: 0013f000 xlate: 00000001 node: 00000000 ( 0 MB -> 320 MB, size: 320 MB)
    NBU0 DRAM BAR1 base: 001d0000 limit: 00bff000 xlate: 00090001 node: 00000000 ( 464 MB -> 3072 MB, size: 2608 MB)
    NBU0 DRAM BAR2 base: 00e00000 limit: 0128f000 xlate: 00290001 node: 00000000 ( 3584 MB -> 4752 MB, size: 1168 MB)
    Hit Ctrl + X keys to stop autoboot: 0

    CPBoot image is signed
    Verifying CPBoot checksum...
    CPBoot check passed
    Signer Cert OK
    Policy Cert OK
    RSA signature verified.
    ## Starting application at 0x8C100000 ...


    CPBoot 1.0.7.0 (build 56553)
    Built: 2016-09-22 at 04:52:12

    DRAM: 4 GB
    Detected [XLP208 Rev B1 (Secure Boot) ] (6a|6a)
    CPLD: rev: 3.0 (30:8008|32:0004|33:0000|34:0000|35:0000)
    Flash: 16 MB
    Watchdog caused the previous reset. So Running Watchdog Framework
    Watchdog reset caused in cpboot context
    -----------------------------------------------------------------
    System will be rebooted in about 1 seconds...

     

    Mad Watchdog reboot one by one ! 



  • 4.  RE: Move RAPS from controller on 6.5 to new controller deployment on 8.3

    EMPLOYEE
    Posted Jul 06, 2018 05:28 PM

    cloudq ... I recommend contacting Aruba TAC to open a case on your issue. I have not encountered the problem you describe when upgrading to 8.3, but have also not had to upgrade a controller via cpboot to do so. It may be that there's a fault with the controller that requires an RMA.

     

    http://www.arubanetworks.com/support-services/contact-support/