AP Behavior When Moved from an SZ to Another SZ
Moving from an SZ to a different SZ
affects AP behavior. The "Move AP" functionality can only help to provision AP data
to the
target SZ but it cannot guarantee AP connection to the target SZ.
AP Behavior When AP Is Moved to Another Cluster
| Scenario | System Behavior and Connection Status | AP Behavior When Moved from an SZ to Another SZ |
|---|---|---|
| AP Onboarding | Refer to Workflow | NA |
| AP belongs to specific SZ and zone | After RND proxies the AP request to a specific SZ and zone based on the AP Registration Rules, AP gets disconnected from RND and remains connected with SZ. Once the AP is onboarded to SZ, AP will not send discovery requests to RND. | At this stage, if you move AP to another SZ, the AP will be moved to the staging zone of the original SZ. Though an AP record will be created in the target SZ, the AP status will be displayed as offline. |
| AP in staging zone | If the AP is forwarded to staging zone, AP remains connected to RND and SZ and the AP continues to send discovery requests to RND. | At this stage, if you move AP to another SZ, the AP will be redirected to the target SZ. |
| If the AP is redirected to a specific SZ and zone, AP gets disconnected from RND and remains connected with SZ and AP will not send discovery requests to RND. | At this stage, if you move AP to another SZ, an AP record will be created in the target SZ but the AP status will be displayed as offline. | |
| Later, if the AP is moved back to the staging zone, AP will not send discovery requests to RND. | At this stage, if you move AP to another SZ, an AP record will be created in the target SZ but the AP status will be displayed as offline. | |
| AP is unmanaged | If the default cluster is not configured, the AP keeps communicating with RND sending the discovery requests to RND. AP will not connect to any SZ. | NA |