AP-6532 Virtual Controller Behavior against the configured standalone AP

Y Yoshihiro Sato 3 years ago
3 0 0

Our partner is checking the virtual controller and found out one symptom.
1) AP-6532-NO1 was configured as Standalone AP and worked correctly.(SSID:TEST1)

2) AP-6532-NO2 was configured as Virtual Controller and put into the same network, where AP-6532-NO1 was running.

   SSID was configured with "SSID:TEST2".

3) AP-6532-NO1 SSID was changed into "TEST2".

#AP-6532-NO1 and AP-6532-NO2 are on the same subnet.(same broadcast domain)

 

Based on the above, VC's configuration was distributed to Standalone AP, although that was not configured as "Adopt to VC"...

 

Is this the expected behavior?

It does not seem to be, based on the initial wizard and standalone AP system reference guide...

 

==

Standalone AP -Select this option to deploy this access point as an autonomous fat access point. A standalone AP isn't managed by a Virtual Controller AP, or adopted by a RFS series controller.

==

 

Your input would be greatly appreciated.

CONTACT
Can’t find what you’re looking for?