Wireless Access

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

ssid not detect ap 103

This thread has been viewed 0 times
  • 1.  ssid not detect ap 103

    Posted Aug 11, 2016 09:46 AM
    I have controller aruba version 7005 and 2 ap 103, ap state is up. But i can't detect ssid from ap 103. Already convert ap 103 to campus wlan, need help? already 3 days for trouble shooting, but yet solved this problem.. hehehhe


  • 2.  RE: ssid not detect ap 103

    Posted Aug 11, 2016 09:53 AM
    Please provide output of

    show AP remote bss-table ap-name <AP name>
    show profile-errors
    show AP active


  • 3.  RE: ssid not detect ap 103

    Posted Aug 11, 2016 09:57 PM

    hi keya_n thanks for respon

     

    (Aruba7005) #show ap remote bss-table ap-name employee
    No AP found with ap_name employee

    (Aruba7005) #show profile-errors

    Invalid Profiles
    ----------------
    Profile                         Error
    -------                         -----
    aaa profile "default-dot1x"     Error: Role 'authenticated' is Unknown
    aaa profile "default-mac-auth"  Error: Role 'authenticated' is Unknown

    (Aruba7005) #show ap active

    Active AP Table
    ---------------
    Name  Group  IP Address  11g Clients  11g Ch/EIRP/MaxEIRP  11a Clients  11a Ch/E                                                                                        IRP/MaxEIRP  AP Type  Flags  Uptime  Outer IP
    ----  -----  ----------  -----------  -------------------  -----------  --------                                                                                        -----------  -------  -----  ------  --------

    Flags: 1 = 802.1x authenticated AP; 2 = Using IKE version 2;
           A = Enet1 in active/standby mode;  B = Battery Boost On; C = Cellular;
           D = Disconn. Extra Calls On; E = Wired AP enabled; F = AP failed 802.1x a                                                                                        uthentication;
           H = Hotspot Enabled; K = 802.11K Enabled; L = Client Balancing Enabled; M                                                                                         = Mesh;
           N = 802.11b protection disabled; P = PPPOE; R = Remote AP;
           S = AP connected as standby; X = Maintenance Mode;
           a = Reduce ARP packets in the air; d = Drop Mcast/Bcast On; u = Custom-Ce                                                                                        rt RAP;
           r = 802.11r Enabled

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0



  • 4.  RE: ssid not detect ap 103

    Posted Aug 11, 2016 10:23 PM

    (Aruba7005) #show ap remote bss-table ap-name Aruba-AP

    Aruba AP BSS Table
    ------------------
    bss  ess  port  ip  phy  type  ch/EIRP/max-EIRP  cur-cl  ap name  in-t(s)  tot-t
    ---  ---  ----  --  ---  ----  ----------------  ------  -------  -------  -----

    Channel followed by "*" indicates channel selected due to unsupported configured channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0
    Num Associations:0



  • 5.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 03:31 AM

    Have you added the necessary licenses to your controller?

     

    Show us "show ap database" aswell please.

     

    Cheers,



  • 6.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 03:53 AM

    Certificate IDs ? ( where i get information for fulfill this question)



  • 7.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 03:54 AM

    It comes with the email when purchasing licenses.

     

    Cheers,



  • 8.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 04:00 AM

    how about trial version, i can try it? i have 1 controller and 2 ap 103 for demo 



  • 9.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 04:02 AM

    Yes, you can generate evaluation licenses on licensing.arubanetworks.com.

     

    Cheers,



  • 10.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 04:13 AM

    Chris,

     

    i can't find trial license menu, ^_^



  • 11.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 04:24 AM

    Certificate management -> Create AOS Eval Certificate :)

     

    Cheers,



  • 12.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 04:34 AM
      |   view attached

    I Still can't find menu (attachment)



  • 13.  RE: ssid not detect ap 103

    Posted Aug 12, 2016 04:48 AM

    Seems like you don´t have the correct permissions on your account. Please contact Aruba support or your Aruba partner.

     

    Cheers,



  • 14.  RE: ssid not detect ap 103

    Posted Aug 14, 2016 10:44 PM
      |   view attached

    Hi Chris and Kenya,

    Thanks you for support me,

    already add license trial for 30 days, but the results same like before AP ssid can't detect..

     

    (Aruba7005) #show ap remote bss-table ap-name Aruba-AP

    Aruba AP BSS Table
    ------------------
    bss  ess  port  ip  phy  type  ch/EIRP/max-EIRP  cur-cl  ap name  in-t(s)  tot-t
    ---  ---  ----  --  ---  ----  ----------------  ------  -------  -------  -----

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0
    Num Associations:0

    (Aruba7005) #show ap remote bss-table ap-name Employee
    No AP found with ap_name Employee

    (Aruba7005) #show ap remote bss-table ap-name Aruba-AP

    Aruba AP BSS Table
    ------------------
    bss  ess  port  ip  phy  type  ch/EIRP/max-EIRP  cur-cl  ap name  in-t(s)  tot-t
    ---  ---  ----  --  ---  ----  ----------------  ------  -------  -------  -----

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0
    Num Associations:0

    (Aruba7005) #show profile-errors

    Invalid Profiles
    ----------------
    Profile  Error
    -------  -----

    (Aruba7005) #show ap active

    Active AP Table
    ---------------
    Name  Group  IP Address  11g Clients  11g Ch/EIRP/MaxEIRP  11a Clients  11a Ch/E                                                                                        IRP/MaxEIRP  AP Type  Flags  Uptime  Outer IP
    ----  -----  ----------  -----------  -------------------  -----------  --------                                                                                        -----------  -------  -----  ------  --------

    Flags: 1 = 802.1x authenticated AP; 2 = Using IKE version 2;
           A = Enet1 in active/standby mode;  B = Battery Boost On; C = Cellular;
           D = Disconn. Extra Calls On; E = Wired AP enabled; F = AP failed 802.1x a                                                                                        uthentication;
           H = Hotspot Enabled; K = 802.11K Enabled; L = Client Balancing Enabled; M                                                                                         = Mesh;
           N = 802.11b protection disabled; P = PPPOE; R = Remote AP;
           S = AP connected as standby; X = Maintenance Mode;
           a = Reduce ARP packets in the air; d = Drop Mcast/Bcast On; u = Custom-Ce                                                                                        rt RAP;
           r = 802.11r Enabled

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0

    (Aruba7005) #(Aruba7005) #show ap remote bss-table ap-name Aruba-AP

    Aruba AP BSS Table
    ------------------
    bss  ess  port  ip  phy  type  ch/EIRP/max-EIRP  cur-cl  ap name  in-t(s)  tot-t
    ---  ---  ----  --  ---  ----  ----------------  ------  -------  -------  -----

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0
    Num Associations:0

    (Aruba7005) #show ap remote bss-table ap-name Employee
    No AP found with ap_name Employee

    (Aruba7005) #show ap remote bss-table ap-name Aruba-AP

    Aruba AP BSS Table
    ------------------
    bss  ess  port  ip  phy  type  ch/EIRP/max-EIRP  cur-cl  ap name  in-t(s)  tot-t
    ---  ---  ----  --  ---  ----  ----------------  ------  -------  -------  -----

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0
    Num Associations:0

    (Aruba7005) #show profile-errors

    Invalid Profiles
    ----------------
    Profile  Error
    -------  -----

    (Aruba7005) #show ap active

    Active AP Table
    ---------------
    Name  Group  IP Address  11g Clients  11g Ch/EIRP/MaxEIRP  11a Clients  11a Ch/E                                                                                        IRP/MaxEIRP  AP Type  Flags  Uptime  Outer IP
    ----  -----  ----------  -----------  -------------------  -----------  --------                                                                                        -----------  -------  -----  ------  --------

    Flags: 1 = 802.1x authenticated AP; 2 = Using IKE version 2;
           A = Enet1 in active/standby mode;  B = Battery Boost On; C = Cellular;
           D = Disconn. Extra Calls On; E = Wired AP enabled; F = AP failed 802.1x a                                                                                        uthentication;
           H = Hotspot Enabled; K = 802.11K Enabled; L = Client Balancing Enabled; M                                                                                         = Mesh;
           N = 802.11b protection disabled; P = PPPOE; R = Remote AP;
           S = AP connected as standby; X = Maintenance Mode;
           a = Reduce ARP packets in the air; d = Drop Mcast/Bcast On; u = Custom-Ce                                                                                        rt RAP;
           r = 802.11r Enabled

    Channel followed by "*" indicates channel selected due to unsupported configured                                                                                         channel.
    "Spectrum" followed by "^" indicates Local Spectrum Override in effect.

    Num APs:0

    (Aruba7005) #



  • 15.  RE: ssid not detect ap 103

    EMPLOYEE
    Posted Aug 14, 2016 11:01 PM

    type "show log system 50" to see if it can tell you why..



  • 16.  RE: ssid not detect ap 103

    Posted Aug 14, 2016 11:30 PM
      |   view attached

    Hi Joseph,

     

    show log system 50 (attachment)

     

    Thank you

     

     

    Attachment(s)

    txt
    log.txt   6 KB 1 version


  • 17.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 02:06 AM

    Reboot all you devices

     

     

     



  • 18.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 02:43 AM
      |   view attached

    reboot done, but the results same like before SSID AP 103 unable to detect ^_^

     

    Topology (attachment)

     



  • 19.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 02:50 AM

    State AP 103 after provisioning, in web gui aruba controller 7005 (attachment)



  • 20.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 02:51 AM
      |   view attached

    Attachment



  • 21.  RE: ssid not detect ap 103

    EMPLOYEE
    Posted Aug 15, 2016 07:21 AM

     

     

    An internal system error has occurred at file sapm_ap_mgmt.c function sapm_proc_hello_req line 11363 error Mismatched Regulatory Domain for AP(Aruba-AP), Ctrl CC(US) AP CC(RW). AP will come up in AM Mode .

    Your problem is that your controller is a US controller model, but you have your regulatory domain for your APs set for CC.  You can only use a controller designated for the US in the US.  You would need a ROW (Rest of the world) controller to use anywhere else.  If you are not in the U.S. you will need a controller that is a ROW model for your aps to work, unfortunately.  Type "show inventory" on the commandline to determine what model controller you have.



  • 22.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 09:54 AM
    Joseph need correction..
    1. Controller (Rest of the world) it mean i have to back to factory default, and setup CC to ID(indonesia) because im in indonesia? Only that?
    2. AP setup i have to back to factory default, after that, i have to convert to wlan campus or not?

    Thanks


  • 23.  RE: ssid not detect ap 103

    EMPLOYEE
    Posted Aug 15, 2016 09:56 AM

    1.  What is the controller model?  What is the SC model in the output of "show inventory?"

     

    After we get that answer, we can decide on your next steps.



  • 24.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 10:26 AM
    Owh. Hehhehehe many thanks. I will give you tomorrow "show-inventory" because im onsite now


  • 25.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 08:36 PM

    (Aruba7005) #show version Aruba Operating System Software. ArubaOS (MODEL: Aruba7005), Version 6.4.2.16 Website: http://www.arubanetworks.com Copyright (c) 2002-2016, Aruba Networks, Inc. Compiled on 2016-02-27 at 14:23:12 PST (build 53988) by p4build ROM: System Bootstrap, Version CPBoot 1.0.3.0 (build 51906) Built: 2015-10-01 03:25:15 Built by: p4build@re_client_51906 Switch uptime is 3 minutes 27 seconds Reboot Cause: POE Power Cycle (Intent:cause:register ee:ee:0:c) Supervisor Card Processor (XLP208 Rev B1 (Secure Boot) , 500 MHz) with 3736M bytes of memory. 32K bytes of non-volatile configuration memory. 1920M bytes of Supervisor Card system flash.

     

    (Aruba7005) #show inventory Supervisor Card slot : 0 System Serial# : CP0011529 (Date:12/23/15) CPU Card Serial# : ANK5CD004D (Date:12/22/15) CPU Card Assembly# : 2010199D CPU Card Revision : (Rev:08.00) SC Model# : Aruba7005 HW MAC Addr : 00:0b:86:be:f5:e0 to 00:0b:86:be:f5:e7 CPLD Version : (Rev: 3.2) Power Source : 802.3af POE Main Board Temperatures : : Remote 1 Temp 31 C (DDR3 temperature) : Local Temp 33 C (Local Thermal) Main Board Voltages : ispPAC_POWR1014A_A : : VCC 5V 5.00V sense 5.118 V : VCC 3V3 3.30V sense 3.324 V : VCC DDR 1V35 1.35V sense 1.372 V : VCC 1V8 1.80V sense 1.832 V : VDD CORE 0.80V sense 0.814 V : VCC 1V2 VRM 1.20V sense 1.188 V : VCC 1V0 1.00V sense 1.012 V : VCC 0V9 0.90V sense 0.918 V : 12V MON 12.0V sense 12.197 V --More-- (q) quit (u) pageup (/) search (n) repeat (Aruba7005) # (Aruba7005) #



  • 26.  RE: ssid not detect ap 103

    EMPLOYEE
    Posted Aug 15, 2016 10:51 PM

    So, it is not clear, but it seems that it has been programmed to the US, when it should be programmed to another country.  You will have to reset it to do that, and then select your country code..

     

    Maintenence> Controller> Clear Config



  • 27.  RE: ssid not detect ap 103

    Posted Aug 15, 2016 11:06 PM

    controller already config in CC ID(indonesia) so how about my ap configuration? convert to wlan campus or let instant AP



  • 28.  RE: ssid not detect ap 103

    Posted Aug 16, 2016 01:22 AM

    controller already config in CC ID(indonesia) AP convert to Wlan campus, the result same like before, AP SSID still can't detect.



  • 29.  RE: ssid not detect ap 103

    Posted Aug 16, 2016 01:48 AM

    (Aruba7005) #show ap database

    AP Database
    -----------
    Name       Group   AP Type  IP Address  Status     Flags  Switch IP     Standby IP
    ----       -----   -------  ----------  ------     -----  ---------     ----------
    Aruba-AP   Banian  103      172.16.0.3  Up 2m:55s  IL     172.16.0.254  0.0.0.0
    Aruba-AP2  Banian  103      172.16.0.5  Up 2m:55s  IL     172.16.0.254  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; 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
           M = Mesh node; Y = Mesh Recovery

    Total APs:2



  • 30.  RE: ssid not detect ap 103

    EMPLOYEE
    Posted Aug 16, 2016 06:08 AM

    The "L" flag means that you need an AP license.  Either a temporary or permanent one should fix your issue.



  • 31.  RE: ssid not detect ap 103

    Posted Aug 16, 2016 06:37 AM

    what i have to do sir for solved this problem? request trial license again for AP or any solution



  • 32.  RE: ssid not detect ap 103

    EMPLOYEE
    Posted Aug 16, 2016 06:46 AM

    Yes, a trial or permanent license would be the solution.