cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
924
Views
0
Helpful
0
Replies

WAP371 creates new cluster instead of joining the existing one

ciscoheidi
Level 1
Level 1

Hello,

I noticed today that probably after a firmware update ( to 1.3.0.7) in the cluster of three WAP371, one WAP created a second cluster with the same name. The firmware update did not work for this WAP either.
I made up for the firmware update, but the WAP continued to create its own cluster of the same name.
Downgrading all WAP to 1.3.0.6 did not help either. Also the order of the cluster accession does not change anything.
Starting with factory default did not help either.
Before the error, the WAP creating its own cluster was cluster master.

In the log you can find:
err mDNSResponder _csco-sb._tcp. service renamed from "cluster0" to "cluster0 (2)".

Does anyone have a tip or can help me please?

 

Kind regards
Ciscoheidi

0 Replies 0