Wireless Access

last person joined: 18 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Regulatory Domain Mismatch on APs, Flag E

This thread has been viewed 4 times
  • 1.  Regulatory Domain Mismatch on APs, Flag E

    Posted Aug 27, 2014 12:12 AM

    (OAW-6000) #show ap database local flags E

    AP Database
    -----------
    Name               Group  AP Type    IP Address   Status      Flags  Switch IP     Standby IP
    ----               -----  -------    ----------   ------      -----  ---------     ----------
    d8:c7:c8:c9:b0:0f  poc    OAW-AP105  10.88.88.36  Up 20m:4s   M2E    10.88.88.250  0.0.0.0
    d8:c7:c8:c9:b1:98  poc    OAW-AP105  10.88.88.41  Up 24m:35s  M2E    10.88.88.250  0.0.0.0

    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
           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
           M = Mesh node; Y = Mesh Recovery

    Total APs:2

     

    (OAW-6000) #show country trail

    2014-08-21_00-30-04: Upgrade: domain ID
    2014-08-21_23-02-46: Upgrade: domain US
    2014-08-21_23-22-01: Upgrade: domain US
    2014-08-22_17-12-58: Upgrade: domain US
    2014-08-25_19-20-49: Upgrade: domain US
    2014-08-26_17-37-03: Upgrade: domain US
    2014-08-26_19-57-44: Upgrade: domain US
    2014-08-26_20-18-05: Upgrade: domain US
    2014-08-26_20-48-37: Upgrade: domain US
    2014-08-26_22-16-04: Upgrade: domain US
    2014-08-26_22-37-26: Upgrade: domain US

     

    (OAW-6000) #show ap regulatory-domain-profile default

    Regulatory Domain profile "default"
    -----------------------------------
    Parameter                          Value
    ---------                          -----
    Country Code                       US
    Valid 802.11g channel              1
    Valid 802.11g channel              6
    Valid 802.11g channel              11
    Valid 802.11a channel              36
    Valid 802.11a channel              40
    Valid 802.11a channel              44
    Valid 802.11a channel              48
    Valid 802.11a channel              149
    Valid 802.11a channel              153
    Valid 802.11a channel              157
    Valid 802.11a channel              161
    Valid 802.11a channel              165
    Valid 802.11g 40MHz channel pair   1-5
    Valid 802.11g 40MHz channel pair   7-11
    Valid 802.11a 40MHz channel pair   36-40
    Valid 802.11a 40MHz channel pair   44-48
    Valid 802.11a 40MHz channel pair   149-153
    Valid 802.11a 40MHz channel pair   157-161
    Valid 802.11a 80MHz channel group  36-48          
    Valid 802.11a 80MHz channel group  149-161

     

    And there is no Ap Specific Configuration in Configuration> Wireless> AP Configuration> AP Specific Tab.  Just delete the AP specific configuration for that AP name.

     

     

     

    any advice about this ?

     

    Thanks,

    Yanto

     
     



  • 2.  RE: Regulatory Domain Mismatch on APs, Flag E

    EMPLOYEE
    Posted Aug 27, 2014 07:47 AM

    Yanto,

     

    What model of access point is this?

    Did you convert it from an IAP?

    What version of ArubaOS are you running?



  • 3.  RE: Regulatory Domain Mismatch on APs, Flag E

    Posted Aug 28, 2014 03:56 AM
    hi joseph Model AP is OAW AP105, AIP105 and AIP225, Yes i was convert the Instans AP to AP before. in this case i use AOS version 6.3.1.9 Thanks, yanto


  • 4.  RE: Regulatory Domain Mismatch on APs, Flag E

    Posted Sep 02, 2014 03:34 AM

    hi colin,

     

    any update about this issue?

     

    Thanks,

    yanto
     



  • 5.  RE: Regulatory Domain Mismatch on APs, Flag E

    EMPLOYEE
    Posted Sep 02, 2014 07:33 AM
    Yanto,

    Please open up a support case. Your description does not match the details of the fixed bug.