Controllerless Networks

Reply
MVP Guru

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

I've had a quick think and you maybe able to complete the following if you cannot gain access to the CLI for whatever reason.

 

- Remove IAP from network.

- Power with POE source

- Factory Reset IAP

- Set a static IP

- Access SetMeUp SSID

- Convert into Standalone Mode

- Reboot

- Remove static IP.

- Plug back into original VLAN.


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Contributor II

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

Update.

 

I went with the work-around mentioned above and set up what amounts to be a local network with internet access.

 

I was able to successfully default the AP and gain access.

 

However, as soon as I set the region code it kicked me out and now I can't login...again.

 

The 8.3 guide didn't reveal much either. 

MVP Guru

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

Try using a different management VLAN for the new cluster/IAP345 and reset the new AP



Thank you

Victor Fabian

Pardon typos sent from Mobile
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
MVP Guru

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

That is odd. Can you remove the Internet access for the IAP? I am wondering if it is attempting to connect to Activate/Central.


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Contributor II

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

<macaddy># swarm-mode standalone
CLI's management authentication settings have been changed. Your login credentials are now being re-checked...
Your credentials are no longer valid, you are being logged out. Please login again with the up-to-date username and password.

Contributor II

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

Hi Victor,

 

That's what I tried originally only to be told I should put the IAP on a network apart from my existin cluster.  I did this and was able to get the IAP to act as I would expect an out-of-box IAP to act.

 

However, regardless of what vlan it's on, I still have no idea what the "updated" credentials are when moving it into a standalone mode.

Contributor II

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

It might be, I'm digging around in my Central instance presently.

Will update if I find anything.
MVP Guru

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

Good idea! Keep us posted.


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Contributor II

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

Ok, 

 

So ultimately it's not reporting into central or managed by central at the present time.  

 

I'm still googling like mad trying to find out what changed my default credentials so I can get into this IAP, give it a config, attach it to central, import said config, and validate what I'm trying to validate.

I'm in the process of peeling out anything I can find of this AP from Central just in case.

 

Educated Guess: Do you think it was just coincidence that the credentials changed just as I set a region code?  I suspect there was a background process that was, in all liklihood, trying to talk with Central.

MVP Guru

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

Have you tried resetting the AP back to factory default via console?



Thank you

Victor Fabian

Pardon typos sent from Mobile
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: