Wireless Access

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

IAP305 SSID won't showup

This thread has been viewed 3 times

  • 1.  IAP305 SSID won't showup

    Posted Aug 01, 2017 12:34 PM

    Hi.

     

    I have bought IAP305 lately and started to setup.

    First, I connected to my router with a cable.

     

    In many docs I see, "instant" SSID should show up in my PC, which it doesn't currently.

     

    I could access to console with both ssh and browser.(it aquires and IP address from router's DHCP server)

     

    And I could see the default "instant" network configured in the web.

     

    Is there anything I should do ? Or anything I've missed ?

    If I create another Network with new SSID, it won't showup either.

     

    Thank you guys in advance.



  • 2.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 01, 2017 04:38 PM

    What version of Instant?

    What regulatory domain?



  • 3.  RE: IAP305 SSID won't showup

    Posted Aug 02, 2017 02:25 AM

     Thanks for the reply.

     

    Will this do ?(How do I get the regulatory domain?)

     

    # show about

    Name :Aruba Operating System Software
    Type :305
    Build Time :2016-12-15 01:54:43 PST
    Version :6.5.1.0-4.3.1.0_57768
    Website :http://www.arubanetworks.com
    Legal :(c) Copyright 2016 Hewlett Packard Enterprise Development LP.
    Cloud Activation Key:



  • 4.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 02, 2017 04:53 AM
    Are these new IAPs or used?
    Did you try factory resetting it using the button?


  • 5.  RE: IAP305 SSID won't showup

    Posted Aug 02, 2017 04:56 AM

    It's new one.

    I bought three of them, and tried the same thing in two which turned out to be the same result.

    And also tried factory reset several times which turned out to also fail.



  • 6.  RE: IAP305 SSID won't showup

    Posted Aug 02, 2017 04:57 AM

    Is there anything I can provide ?

    % show run

    % show tech-support



  • 7.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 02, 2017 05:20 AM

    Are you using DHCP?  If you setup a new SSID, the Instant SSID should disappear.



  • 8.  RE: IAP305 SSID won't showup

    Posted Aug 02, 2017 06:30 AM

    > Are you using DHCP? If you setup a new SSID, the Instant SSID should disappear.

    For uplink, I use  DHCP.

    And for the Instant SSID, I didn't touch anything so it should be default.
    If I setup new SSID, Instant SSID disappears, and new SSID appears.

    But the problem is that I can't see it on my PC or on my smartphone.

    (can't see both Instant and original SSID on PC/smartphone)



  • 9.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 02, 2017 06:54 AM
    Which smartphone are you using?


  • 10.  RE: IAP305 SSID won't showup

    Posted Aug 02, 2017 12:17 PM

    I've tried

     

    MacBookPro

    iPhone5, iPhone6S, OnePlus2
    Windows10



  • 11.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 02, 2017 01:23 PM

    What channel is the access point on?



  • 12.  RE: IAP305 SSID won't showup

    Posted Aug 04, 2017 07:06 AM

    I tried 2 patterns.

    1. with default instant SSID

    I don't know which channel the default instant SSID use

     

    2. with customized channel, I set the following

    For 5GHz: 36, 40, 44, 48
    For 2.4GHz: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13

    Used wifi analyzer to see if there's any signal, but couldn't find one.



  • 13.  RE: IAP305 SSID won't showup

    Posted Aug 15, 2017 10:25 PM

    Any idea ?



  • 14.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 16, 2017 06:44 AM

    What regulatory domain?



  • 15.  RE: IAP305 SSID won't showup

    Posted Aug 18, 2017 11:39 PM

    How do I get the reguratory domain ?



  • 16.  RE: IAP305 SSID won't showup

    Posted Aug 16, 2017 10:08 AM

    Any output of "show ap bss-table"?

     

    If so, what are the used channels?



  • 17.  RE: IAP305 SSID won't showup

    Posted Aug 18, 2017 11:40 PM

    This is what it shows.

    Looks like no bss or channels ...

     

    # show ap bss-table

    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



  • 18.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 19, 2017 04:11 AM

    What is the output of "show log system"?



  • 19.  RE: IAP305 SSID won't showup

    Posted Aug 19, 2017 05:50 AM

    There are many logs complaining about activation of provision failed...

     

    c8:b5:ad:c4:9b:f4# show log system

    Aug 19 03:28:54 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 03:33:56 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 03:38:58 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 03:40:46 cli[14131]: <341101> <WARN> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Execute command-exit.
    Aug 19 03:44:00 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 03:49:02 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 03:54:04 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 03:59:10 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: protocol-error-001
    Aug 19 04:04:08 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:09:11 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:14:12 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:19:15 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:24:17 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:29:19 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:34:21 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:39:23 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:44:25 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:49:27 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:54:29 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 04:59:31 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:04:34 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:09:36 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:14:38 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:19:43 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:24:42 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:29:44 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:34:46 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:39:50 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: protocol-error-001
    Aug 19 05:44:50 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:49:52 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule

    Aug 19 05:54:54 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 05:59:56 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:04:58 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:10:00 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:15:02 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:20:05 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:25:07 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:30:09 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:35:11 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:40:13 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:45:15 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:50:17 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 06:55:19 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:00:21 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:05:23 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:10:25 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:15:27 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:20:30 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:25:32 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:30:35 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:35:37 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: protocol-error-001
    Aug 19 07:40:39 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: protocol-error-001
    Aug 19 07:45:40 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 07:50:43 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: protocol-error-001
    Aug 19 07:55:44 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:00:46 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:05:48 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:10:50 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:15:52 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule

    Aug 19 08:25:56 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:30:58 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:36:02 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:41:02 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:46:05 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:51:07 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 08:56:09 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:01:11 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:06:13 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:11:15 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:16:17 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:21:19 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:26:21 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:31:23 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:36:26 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: protocol-error-001
    Aug 19 09:41:27 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule
    Aug 19 09:46:29 cli[2115]: <341005> <ERRS> |AP c8:b5:ad:c4:9b:f4@192.168.1.251 cli| Activate provision failed, code: fail-prov-no-rule



  • 20.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted Aug 19, 2017 08:08 AM
    It seems like you should contact TAC. Your access point seems to be in activate (the cloud) but if you just purchased them, they should not be.


  • 21.  RE: IAP305 SSID won't showup

    Posted Aug 19, 2017 08:15 AM

    Thanks Colin for all the help.

    I'll contanct the TAC.

     

    Let me just summarize my current situation.

    - my IAP305 seems to be activated on cloud

    - it should not be activated if it's right after the purchase

    - and that seems to be causing a problem

     

    Is that correct ?



  • 22.  RE: IAP305 SSID won't showup
    Best Answer

    EMPLOYEE
    Posted Aug 19, 2017 12:34 PM

    That is what it might be, based on the logs.  They could find more things in the logs to indicate otherwise.



  • 23.  RE: IAP305 SSID won't showup

    Posted Aug 20, 2017 10:38 AM

    Thanks Colin for your patient support.

    Really appreciate it.



  • 24.  RE: IAP305 SSID won't showup

    Posted May 04, 2018 07:33 PM

    Hl, i have the same situation but with an IAP375, i enter the instant and then i create the SSID and dont show up, i try several times but dont work, did the TAC solve this, thanks a lot 



  • 25.  RE: IAP305 SSID won't showup

    EMPLOYEE
    Posted May 16, 2018 12:29 PM
    @jppdiaz wrote:

    Hl, i have the same situation but with an IAP375, i enter the instant and then i create the SSID and dont show up, i try several times but dont work, did the TAC solve this, thanks a lot 

    The IAP375 requires newer firmware than the IAP305, so this is likely a different issue. Please start a new thread if you're still needing assistance with this.