Cloud Managed Networks

 View Only
  • 1.  AP505 unable to join existing AP515 cluster

    Posted Dec 08, 2022 04:58 AM
    Edited by jrwhitehead Dec 08, 2022 04:58 AM

    Hi,

    I've got a Central Managed AP515 cluster running 8.10.0.2_84367. I'm attempting to add an AP505 which is currently on 8.7.1.6_81786 but it's failing to upgrade and join the cluster.

    Cluster security is off. All the AP are on the same VLAN on a layer 2 switch. I've been informed that nothing is being blocked outbound by a firewall.

    I'm seeing the following messages in the system log on the VC. Any ideas?

    Dec 8 09:35:17 cli[4846]: <341097> <WARN> |AP-NAME@10.10.10.10 cli| recv_image_check: mac-48:2f:6b:aa:bb:cc, version-8.7.1.6-8.7.1.6_81786, ccode_idx-255.
    Dec 8 09:35:17 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| ccode_index_to_ccode_array_idx_vc, return i = 6
    Dec 8 09:35:17 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| is_reg_domain_match my_arr_idx = 6, other_arr_idx= 6
    Dec 8 09:35:17 cli[4846]: <341052> <ERRS> |AP-NAME@10.10.10.10 cli| recv_image_check, 2996: AP class not match, Conductor-55, Member-64.
    Dec 8 09:35:17 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| Image_sync_via_isc
    Dec 8 09:35:18 cli[4846]: <341002> <INFO> |AP-NAME@10.10.10.10 cli| recv_sta_update: 7b:bb:db:cb:cb:bb client acl is 153
    Dec 8 09:35:18 cli[4846]: <341002> <INFO> |AP-NAME@10.10.10.10 cli| recv_sta_update: Received user role info TLV
    Dec 8 09:35:18 cli[4846]: <341002> <INFO> |AP-NAME@10.10.10.10 cli| Updated client acl to 153
    Dec 8 09:35:22 cli[4846]: <341097> <WARN> |AP-NAME@10.10.10.10 cli| recv_image_check: mac-48:2f:6b:aa:bb:cc, version-8.7.1.6-8.7.1.6_81786, ccode_idx-255.
    Dec 8 09:35:22 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| ccode_index_to_ccode_array_idx_vc, return i = 6
    Dec 8 09:35:22 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| is_reg_domain_match my_arr_idx = 6, other_arr_idx= 6
    Dec 8 09:35:22 cli[4846]: <341052> <ERRS> |AP-NAME@10.10.10.10 cli| recv_image_check, 2996: AP class not match, Conductor-55, Member-64.
    Dec 8 09:35:22 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| Image_sync_via_isc
    Dec 8 09:35:22 cli[4846]: <341004> <WARN> |AP-NAME@10.10.10.10 cli| isc_image_url_request: Gemini,8.10.0.2-8.10.0.2_84367
    Dec 8 09:35:22 cli[4846]: <341002> <INFO> |AP-NAME@10.10.10.10 cli| ap_info_body length 507
    Dec 8 09:35:23 cli[4846]: <341140> <INFO> |AP-NAME@10.10.10.10 cli| build_activate_url_cache, 6243: payload is X-Status-Code: success.
    Dec 8 09:35:23 cli[4846]: <341092> <ERRS> |AP-NAME@10.10.10.10 cli| build_activate_url_cache: 6257: Parse error in payload.
    Dec 8 09:35:23 cli[4846]: <341140> <INFO> |AP-NAME@10.10.10.10 cli| get_version_and_url_for_multi_class_image_upgrade, 6755: payload is X-Status-Code:.
    Dec 8 09:35:23 cli[4846]: <341143> <ERRS> |AP-NAME@10.10.10.10 cli| get_version_and_url_for_multi_class_image_upgrade,6794: could not get class-55 in payload.
    Dec 8 09:35:23 cli[4846]: <341002> <INFO> |AP-NAME@10.10.10.10 cli| Clear isc_sync_ap in isc_disconnect


  • 2.  RE: AP505 unable to join existing AP515 cluster

    Posted Dec 08, 2022 08:41 AM
    Make sure that the APs run the same firmware version (example 8.10.0.2_84367) before joining them in the same network. Only if they run the same firmware version they will form a cluster. These log messages tell that there is no firmware image in the (515) cluster for the AP505.

    Best is to bring the 505 up in a separate network from the AP 515, then upgrade firmware, then move it back and it should work and form a cluster.

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: AP505 unable to join existing AP515 cluster

    Posted Dec 08, 2022 09:01 AM
    Really? Is that still the case after all these years?

    If so, I'm disappointed that the AP cannot upgrade via Central.


  • 4.  RE: AP505 unable to join existing AP515 cluster

    Posted Dec 08, 2022 09:40 AM
    If you add+subscriber the AP to Central, then you should be able to upgrade from Central through the firmware update function. Sorry, missed the 'Central Managed'.

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 5.  RE: AP505 unable to join existing AP515 cluster

    Posted Dec 08, 2022 09:52 AM
    Ah great. The AP is already added and subscribed in greenlake. Also added to the correct group in Central.

    I'll get TAC to have a look I think.


  • 6.  RE: AP505 unable to join existing AP515 cluster

    Posted Dec 09, 2022 03:37 AM
    Activate can help with that. 

    Without Activate there is still some nuisance to add a different type of AP to the cluster. Fastest way for me is to upgrade one AP to the same version of FW as it is in a cluster (in separate vlan via Central or manually), and move it into the cluster. Then other APs can join without a problem.

    Best, Gorazd

    ------------------------------
    Gorazd Kikelj
    ------------------------------