Controllerless Networks

Reply
Contributor I

IAP-345 - Cannot create independent cluster when adjacent to existing VC

I was trying to test and validate the IAP-345 hardware I received as part of various initatives.

 

However, much to my surprise, the IAP-345 decided to "see" my existing corporate IAP VC, tell me that it was pre-empted in the master election by my existing VC, and then lock itself into a slave role with no option for me to intervene.

 

I've also verified that my existing corporate IAP cluster has auto-join turned off.

 

I need to vet this hardware, test migrations to Aruba Central, and numerous other tasks.  How can I get this thing to create it's own independent cluster like I expect it to?

To my knowledge, this wasn't an issue before InstantOS 8.3.

New Contributor

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

Hi,

 

can you put it into a separated VLAN?

Not sure, if truning auto-join soved this in the past.

Seperate VLAN should.

 

Bye,

 

JH

Contributor I

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

Hi Jö,

 

I cannot put these on another vlan due to security requirements.  I have not had this issue prior to 8.3. 

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

If you need to run this as a single entity in the same VLAN, convert the IAP into a standlone mode. standalone.PNG


ACMA, ACMP, ACSA
If my post addresses your query, give kudos:)
Contributor I

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

Hi zalion0,

 

Can this be done pre-boot? 

 

Right now I have to connect this IAP to my network to get it to come up properly, even in a default state (due to requiring internet access).

 

EDIT: This can be done after boot when the IAP is in a slave role. Thats good I guess.

 

I'll give it a shot, but something a bit more programmatic than "Login and convert it" is desirable.  I'm about to have a bunch of these, having to do this each time is going to lengthen my provisioning cycle immensely.  

 

This feels exactly like when Instant was first introduced and I had to "convert" all my "new" APs to campus APs.  Now I'm doing it again, just another direction. 

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

Hey, I saw your edit :) That's good, has it resolved the issue?  Obviously you will have the configuration downloaded from the VC cluster which may or may not be beneficial. 


If you don't have a separate VLAN, I believe the only way you could achieve this would be to assign the IAP a static IP on a local network (such as your laptop/POE external source), convert it to standalone, remove the static IP then plug back into your L2 domain.


ACMA, ACMP, ACSA
If my post addresses your query, give kudos:)
Contributor I

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

So conversion to a "standalone" Instant worked, however now I cannot login.  

 

My SE mentioned that something or another may be blocked during provisioning and the release notes for 8.3 reveal nothing as to what these new credentials might be.

 

I've tried the following:

admin/admin

admin/instant

admin/password

admin/arubanetworks123

admin/aruba123

Contributor I

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

How would I ensure that the existing configs do not sync to this device prior to me being able to convert it to standalone?

 

Also, why is my existing, non-compatible IAP cluster syncing it's config to a device when auto-join is disabled.  Isn't turning off auto-join supposed to prevent another AP from acquiring that config?

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

Have you tried the existing VC password? You advised the new AP successfully joined the existing VC cluster correct? So it would've downloaded the configuration.


ACMA, ACMP, ACSA
If my post addresses your query, give kudos:)
Contributor I

Re: IAP-345 - Cannot create independent cluster when adjacent to existing VC

That's probably my miscommunication.

 

It never actually joined the cluster.  It got far enough to consider itself a slave to my existing 205 VC and that's where it all stopped.  

 

I've seen this behavior before when an IAP with a incompatible firmware version attempts to join a cluster. You'll see it appear in the APs list (though again, why it's doing this while autojoin is disabled is kinda sketchy) but it will never sync firmware or fully sync it's config.

 

I did check the local password I had for my cluster, it didn't function.  I just didn't list it as, well, internal passwords. 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: