Wireless Access

Reply
Guru Elite

Re: IAP305 SSID won't showup

What channel is the access point on?


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Occasional Contributor II

Re: IAP305 SSID won't showup

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.

Highlighted
Occasional Contributor II

Re: IAP305 SSID won't showup

Any idea ?

Guru Elite

Re: IAP305 SSID won't showup

What regulatory domain?


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Contributor I

Re: IAP305 SSID won't showup

Any output of "show ap bss-table"?

 

If so, what are the used channels?

Occasional Contributor II

Re: IAP305 SSID won't showup

How do I get the reguratory domain ?

Occasional Contributor II

Re: IAP305 SSID won't showup

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

Guru Elite

Re: IAP305 SSID won't showup

What is the output of "show log system"?


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Occasional Contributor II

Re: IAP305 SSID won't showup

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

Guru Elite

Re: IAP305 SSID won't showup

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.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: