Wireless Access

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

AC3600 AP flag S

This thread has been viewed 2 times

  • 1.  AC3600 AP flag S

    Posted Feb 26, 2019 02:45 AM

    Hi everyone,

     

    We are encounting a strange problem.

     

    Some Aps' flags suddenly have an "S" , then the SSID suddenly gone.

    After a while , flag "S" disappear and the SSID recover

     

     

    here are some output:

     

    AP Database
    -----------
    Name Group AP Type IP Address Status Flags Switch IP Standby IP
    ---- ----- ------- ---------- ------ ----- --------- ----------

    AP-003 AFW7 RAP-108 10.80.99.122 Up 16d:5h:36m:2s  S 10.80.99.231 10.80.99.232
    AP-004 AFW7 RAP-108 10.80.99.142 Up 16d:4h:49m:53s S 10.80.99.232 10.80.99.231

     

     

    Flags: U = Unprovisioned; N = Duplicate name; G = No such group; L = Unlicensed
    I = Inactive; D = Dirty or no config; E = Regulatory Domain Mismatch
    X = Maintenance Mode; P = PPPoE AP; B = Built-in AP; s = LACP striping
    R = Remote AP; R- = Remote AP requires Auth; C = Cellular RAP;
    c = CERT-based RAP; 1 = 802.1x authenticated AP; 2 = Using IKE version 2
    u = Custom-Cert RAP; S = Standby-mode AP; J = USB cert at AP
    i = Indoor; o = Outdoor
    M = Mesh node; Y = Mesh Recovery

     

    How can I fix this problem?

     

     

    Thank you for any answers

     

     



  • 2.  RE: AC3600 AP flag S

    Posted Feb 26, 2019 03:16 AM

    Have you turned on and checked the ap debug log already?

     

    Does the ssid disapear from "show ap bss-table" ?



  • 3.  RE: AC3600 AP flag S

    MVP EXPERT
    Posted Feb 26, 2019 08:54 AM

    The "S" flag will appear when an AP has made a standby GRE connection to another controller. Have you got HA failover enabled and do you have a BLMS IP specified in the AP System Profile?

     

    The AP is potentially failing over to a standby controller which does not have the correct configuration for the SSID/VAP (check it with #show profile-errors) so the SSID may not be broadcast.