Cloud Managed Networks

 View Only

  • 1.  All radios disabled

    Posted 2 days ago
    Edited by ascott 2 days ago

    Hi,

    I could use some help.  I have been working on getting my gateways and APs moved to New Central (CNX).  Currently in a non-production lab environment that's connected off my production core.  I have a case open on this issue and have had several SEs look at it.  Thought I would ask here as I need to get this issue resolved.

    My issue is we cannot get an AP to work.  The radios are disabled with a reason of "Disabled by SAPD Msg".  Before I bore you, I attached some log entries below. The AP and Gateway are on AOS 10.8.0.2 (was .1 until yesterday).  Both up and licensed in CNX.  They are in the same Device Group and site.  The site is in the US and the devices show US country code.  The gateway has a GW Cluster profile configured in the Device Group.  The AP has a WLAN profile set for "TUNNELED" mode, and the gateway cluster is selected.  The wireless vlan is set.  

    The network is AP connected to a NAC port on a 6200 CX SW then uplinked to a Cisco core switch.  The Gateway is a 7010 and is also connected to the same core switch.  No Restrictions between these devices besides the AP which is on a NAC role but currently has an IP any any any on the role ACL.  The wireless VLAN SVI is on the Cisco core.  The VLANs are all setup on the core correctly and trunked to the controller, trusted.

    I am seeing errors like the below on the logs I collected from the AP about SAPD.

    SSID Action Request History
    ---------------------------
    Timestamp             Action   Essid                            Reason       Current Cluster Primary/Backup Cluster
    ---------             ------   -----                            ------       --------------- ----------------------
    2026-06-01 16:54:59   DOWN_REQ NLAW101                          No Mapping   Primary         /
    2026-06-01 16:54:59   DOWN_REQ Guest-SSID                       No Mapping   Primary         /
    2026-06-01 16:55:00   DOWN_REQ NLAW101                          No Mapping   Primary         /
    2026-06-01 16:55:00   DOWN_REQ Guest-SSID                       No Mapping   Primary         /
    2026-06-01 16:55:02   DOWN_REQ NLAW101                          No Mapping   Primary         /
    2026-06-01 16:55:02   DOWN_REQ Guest-SSID                       No Mapping   Primary         /

    [9022]2026-06-01 16:54:27 VAP: 0 adv_health_ie: 0 health_ie: 0x0
    [9022]2026-06-01 16:54:27 sapd_proc_apcli_msg: ssid NLAW101, lci-cap 0, civic-cap 0
    [9022]2026-06-01 16:54:27 sapd_c2c_check_ssid_need_disable_by_oos(3414): No cluster mapping found, disable essid: NLAW101
    [9022]2026-06-01 16:54:27 vap not present, vnum: 0, rnum:0
    [9022]2026-06-01 16:54:27 vap not present, vnum: 0, rnum:1
    [9022]2026-06-01 16:54:27 vap not present, vnum: 255, rnum:2
    [9022]2026-06-01 16:54:27 c2c_gw_profile_name=Guest-SSID_1772655916832472404_, preemption=0, oos_def 0, oos_op 1, essid  Guest-SSID o_twin_essid , forward_mode 2
    [9022]2026-06-01 16:54:27     ESSID_CONFIG received for VAP(1/255/255<-1/255/255), ESSID(Guest-SSID/), radio_bmap: 0x3/0x7 mbssid_btm: 0x4 eht_enable: 1 eht_mcs_map: 0x924/13,13,13,13 mlo: 0 scs: 0 opmode: 0x1/opensystem configred_opmode: 0x1/opensystem 
    [9022]2026-06-01 16:54:27 VAP: 1 adv_health_ie: 0 health_ie: 0x0
    [9022]2026-06-01 16:54:27 sapd_proc_apcli_msg: ssid Guest-SSID, lci-cap 0, civic-cap 0
    [9022]2026-06-01 16:54:27 sapd_c2c_check_ssid_need_disable_by_oos(3414): No cluster mapping found, disable essid: Guest-SSID
    [9022]2026-06-01 16:54:27 vap not present, vnum: 1, rnum:0
    [9022]2026-06-01 16:54:27 vap not present, vnum: 1, rnum:1
    [9022]2026-06-01 16:54:27 vap not present, vnum: 255, rnum:2
    [9022]2026-06-01 16:54:27 Recv NO_ESSID for o_vnum 0 mbssid_vnum 255 mbg_number 0
    [9022]2026-06-01 16:54:27 Recv NO_ESSID for o_vnum 1 mbssid_vnum 255 mbg_number 0
    [9022]2026-06-01 16:54:28 c2c_gw_profile_name=NLAW101_1779453457818662186_, preemption=0, oos_def 0, oos_op 1, essid  NLAW101 o_twin_essid , forward_mode 2
    [9022]2026-06-01 16:54:28     ESSID_CONFIG received for VAP(0/255/255<-0/255/255), ESSID(NLAW101/), radio_bmap: 0x3/0x7 mbssid_btm: 0x4 eht_enable: 0 eht_mcs_map: 0x924/13,13,13,13 mlo: 0 scs: 0 opmode: 0x40/wpa2-aes configred_opmode: 0x40/wpa2-aes 
    [9022]2026-06-0

    Any ideas on what I could be missing. 



  • 2.  RE: All radios disabled

    Posted 2 days ago

    Well I just got the radios up.  Had a typo in the gateway cluster IP.  Currently up with manual gateway cluster selection.  Now need to get it working with auto gateway.  See how that goes but when playing with it earlier it looked like it could only apply to a site collection or a device group which means I still need to recreate the profile several times.   I was trying to avoid having to recreate my WLAN profile 600 times.




  • 3.  RE: All radios disabled

    Posted yesterday

    It's is possible to have auto-site clustering in CNX. However, this is currently limited to specific customers. Please reach out to your SE to check if the account can be enabled for this. It's called PE mode migration.



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------

    Original Message


  • 4.  RE: All radios disabled

    Posted yesterday

    Thank you for the reply William.  I have Auto Cluster.  Are you using it already?  Any you running into any issues with it?   I plan to lab it out again today but I believe the last time I tried it I had to assign it to a site collection or device group.  And because of that it drives a requirement for me to recreate my WLAN profiles several times.  What I am after is ONE WLAN profile per SSID that I can use globally so I have consistent settings globally and do not have to edit multiple profiles each time we resolve an issue for a site.


    Original Message


  • 5.  RE: All radios disabled

    Posted yesterday

    I'm refering to the "Gateway Clustering Orchestration" feature. Do you have this available?

    Without this feature you need to create a WLAN profile per site. With this feature you can use auto site clustering and have a single WLAN profile. I have customers that are using this. 



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------

    Original Message


  • 6.  RE: All radios disabled

    Posted yesterday

    Yes I have it.  But I am seeing still a requirement to recreate my WLANs multiple times.  Instead of per site with Auto Cluster it will be per Site Collection group or Device Group.  Unless I am wrong the Auto cluster has to be applied to one of these.


    Original Message


  • 7.  RE: All radios disabled

    Posted yesterday

    There are a few steps to take.

    1. Create a Gateway Clustering Orchestration profile with Auto-Site enabled
    2. Assign the create profile to global or a lower level scope
    3. Create a WLAN profile in the Library and under VLAN > Tunnel > Gateway Cluster select "AUTO-SITE-CLUSTER-MGW".
    4. Now assign the WLAN profile to a site or site collection. I believe Global should also work.



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------

    Original Message


  • 8.  RE: All radios disabled

    Posted 14 hours ago

    @willembargeman - Again thank you for the help.   

    I created a new auto cluster profile set to auto and pushed to the global folder.  I built new wireless WLANs and applied them to the site collection  level because it does not allow me to apply it to the global level.  My radios are up.  See the error I get below if I try to apply the WLAN to the global folder when Auto Cluster is selected in the WLAN.  Not a big deal just pointing out its not supported at the global level

    I also think I am going to run into another issue with auto cluster.  My clusters are single gateways at a site.  I have a remote gateway (backup LMS) in another location.  One for US, one for EMEA, APAC, ect..)So lets say I have a WLAN called Corp.  Corp needs to be at all site collections/global.  ButSome site collections need APAC some need EMEA, some need US.  How can I do this.   From what my SE is telling me I need to name the WLAN profile the same name as the SSID so I can only set the backup cluster to one hard coded device and can not create a duplicate WLAN name.  


    Original Message


  • 9.  RE: All radios disabled

    Posted 10 hours ago

    The use-case you describe is not going to work with auto-site cluster. Yes, for this you need to use the Secondary Gateway Cluster option. 

    I'm not sure about the SSID and profile name. For some scenarios at this moment it needs to be the same, yes. 

    Currently I can't test this. I think best is to discuss this with your SE and maybe TME/PLM to check what is possible at this and what is planned to be enhanced in the future. 



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------

    Original Message


  • 10.  RE: All radios disabled

    Posted 4 hours ago

    It looks like the error is stating it wants the config applied on a per site collection or device collection. If you setup your devices in sites, you can then put the sites in a site collection where those configs are applied. My interpretations of site collection would be grouping devices in geographical regions or by mgmt domains from operations. I have used the approach to apply general configs on site collections and then if i need to override a named vlan I can do that at a site level for the whole group of AP's. The same would go for radio profile. Maybe a new site has issues with UNII-1 and I want to enable UNII-2 instead. Those overrides are now made fairly easy as long as you keep some structure in the hierarchy.

    As to setting regulatory domain info. It depends on how you want to structure everything. You can create a basic profile and just leave it at automatic for country. It will pick the country for the address populated in the site. I think it would be to much work to create multiple ap system profile configs for different countries. 

     I didn't see a country code option under the system area for gateways. Im not sure what an RW device would default to, although I dont see why a country is needed on gateways. Since the wlan is no longer being managed by gateway,  there is no need for it to match the AP. I still would need to test what an RW device does and where does it default. I would assume you can change this via api, and maybe it will be added in the workflow changes that are coming. 


    Original Message


Related Content