Controller-less WLANs

 View Only
last person joined: one year ago 

Articles relating to existing and legacy HPE Aruba Networking products and solutions including IAP, Central / HPE Aruba Networking Central, MSR, and Outdoor Mesh

APAS provision failed, code: protocol-error-001 error in Instant AP 

Mar 27, 2017 09:41 AM

Q:

APAS provision failed, code: protocol-error-001 in Instant AP



A:

By default, IAPs contact device.arubanetworks.com and when there is no rule configured in Aruba Activate we could see the fail-prov-no-rule. 

 

We would see the below error message in "show log system" of the Instant AP. 

Feb 24 09:40:31  cli[3778]: <341005> <ERRS> |AP 18:64:72:ca:f1:56@10.29.165.250 cli|  APAS provision failed, code: protocol-error-001

Feb 24 11:01:08  cli[3778]: <341005> <ERRS> |AP 18:64:72:ca:f1:56@10.29.165.250 cli|  APAS provision failed, code: protocol-error-001

Feb 24 15:18:08  cli[3778]: <341005> <ERRS> |AP 18:64:72:ca:f1:56@10.29.165.250 cli|  APAS provision failed, code: protocol-error-001

Feb 24 15:33:30  cli[3778]: <341005> <ERRS> |AP 18:64:72:ca:f1:56@10.29.165.250 cli|  APAS provision failed, code: protocol-error-001

 

If the device is not managed by Aruba Central, then we can syslog-level for system as critical which would stop these messages in show log system. 

 

From Cli: 

syslog-level critical system

From Web UI:

We need to navigate to system > show advanced options > Monitoring > Syslog Facility Levels > Set the system to critical. 

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.