Wireless Access

I use rw7010 and ap205 converted from iap.

but when I assign the ap to controller , it boots as only AM mode despite both of them use default profile.

 

the procedure is below.

1. Set IP address to the factory-default-7010. -----ex.172.16.0.1

2. Enter *convert-aos-ap cap 172.16.0.1* command to the iap205.

3. After AP reboots, 7010 finds the ap205 as AM mode...

4. try purgeenv for the ap, but there is no difference.

 

i want to use normal cap mode.

please give  me any advise.

 

Thanks in advance.

 

Regards

Atsushi Ikeda

Have you checked to see if the AP-205 is supported in your regulatory domain?
#AP205

Please look here:  https://pctools.arubanetworks.com/compliance/ to see if the AP205 (APIN0205) is approved for your country's regulatory domain.

Thank you for quick reply. Yes, it supports my domain. The other ap205s has no problem. one ap205 only... have you got any suggestions ?

On the commandline, type "show ap database long" to see if your access point has any flags that would indicate why.

 

Thank you. There is no flag deisplayed from that command !

Is it in the default ap-group, or in a special ap group?  Does the ap-group that it is in have the radios disabled?

 

It is in default group because it remains default config except ip address. so both radio is enable.

And I connected another 205 to the controller,then it booted up as cap in the same default group...

 

Please tell me if I should get specfy log.

 

Thanks.

Type "show log system 50" and see if anything references your AP.

 

O.K. I atatch its log.

 

I saw AM mode ap in that log..

But I couldn't catch the any information about AM mode boot...

According to the log, you either need to:

- approve that access point

Or

- disable control plane security.

 

 

Please see the chapter on Control Plane Security here:  http://www.arubanetworks.com/techdocs/ArubaOS_64_Web_Help/Web_Help_Index.htm#ArubaFrameStyles/Control_Plane/Configuring_Control_Plan.htm

Though I disabled cpsec, manualy approved and provisioned , the result was same.

Anyway I think ap should not goes to AirMonitor mode without any vap profile setting.

because default profile is ap-mode on each radio.

 

 

 

Is this your access point?

 

Dec 1 01:21:16 :305049:  <WARN> |stm|  Unsecure AP "ac:a3:1e:c2:99:aa" (MAC ac:a3:1e:c2:99:aa, IP 172.16.11.153) has been denied access because Control Plane Security is enabled and the AP is not approved.

 If the answer is "yes", it needs to be approved.  It can take from 8 to 10 minutes for the access point to boot and get a certificate the first time.

Yes, it's my ap , not a customer's.

 

Of course I tried to approve.

[Before]

CPsec : enabled

Auto Cert Provisioning : enabled

White list : approved-ready-for-cert

 

[After] ( few minuts later )

CPsec: enabled

Auto Cert Provisioning : enabled

White list : certified-factory-cert

 

And I did provisioning for ap but nothing changed.

 

Do you mean this as "it needs to be approved" ?

it goes slumming...

Please type "show log system 50" so we can see what the problem is.

 

If this is NOT a production network, I would just disable control plane security, and then reboot your access point with the problem.

 

 

 

 

I disabled cpsec.

Then, already certified ap couldn't connect tunnel to lms.

So I rebooted ap and oprerated purgeenv.

Then ap turned up and became AM mode again.

 

I attach log.

 

Thank you.

What is the output of "show ap database"

I'm so sorry to say that I have to lease this IAP to my customer, so I can't research about this in days... ( this ap acts as IAP correctly ) 

Woud you mind if I resume discussion at a later date ?

No problem

The default AP group is set to air monitor out of the box. You will need to create a new ap group and add a virtual AP and then provision the AP into that group.

have you try with other regularity domain than the default , generaly AM mode is used to unregistred AP type.

 

No I have not. Japan only.

I thought I didn't need to try with other domain  because another IAP205 worked well.

But I will try that.

 

Thank you.

 

any way ,

i got the same probleme with IAP 103 (first i was using algeria reg domain), and to resolve the probeme i change the IAP regularity domain into France.

 

check also the last firmware update.

 Sorry for late.

 

I confirmed that this issue was replicated inspite of the same domain configuration.

And I found a workaround.

This issue occurs in Aruba OS 6.4.1.0, but does not occur in Aruba OS 6.4.2.2.

So this might be a bug.

 

Thanks.

---

@atsushi wrote:

 Sorry for late.

 

I confirmed that this issue was replicated inspite of the same domain configuration.

And I found a workaround.

This issue occurs in Aruba OS 6.4.1.0, but does not occur in Aruba OS 6.4.2.2.

So this might be a bug.

 

Thanks.

---

the versionn 6.4.2.3 is better , they fix many issue , the version 6.4.2.2 was removed from the support site

Hi,

 So you manage to solve this by upgrade the image to 6.4.2.2. or 6.4.3.2 ?

I face the same problem here.

Hi, Mandyvoon

 

Sorry for late.

Yes, I did.