Field | Action |
|
|
New Access | Choose the policy you want to put in effect for adding |
Points | New Access Points to the network. |
| • If you choose are configured automatically, then |
| when a new access points is added to the network it |
| automatically joins the existing cluster. The cluster |
| configuration is copied to the new access point, and no |
| manual configuration is required to deploy it. |
| • If you choose are ignored, new access points will not |
| join the cluster, but will be considered standalone. You |
| need to configure standalone access points manually |
| through KickStart and the Administration Web pages |
| residing on the standalone access points. (To get to the |
| Web page for a standalone access point, use its IP |
| address in a URL as follows: |
| http://IPAddressOfAccessPoint.). |
| Note: If you change the policy so that new access points |
| are ignored, then any new access points you add to the |
| network will not join the cluster. Existing clustered access |
| points will not be aware of these standalone APs. |
| Therefore, if you are viewing the Administration Web |
| pages through the IP address of a clustered access |
| point, the new standalone APs will not show up in the |
| list of access points on the Cluster > Access Points tab. |
| The only way to see a standalone AP is to browse to it |
| directly by using its IP address in the URL. |
| If you later change the policy back to the default so that |
| new access points “are configured automatically,” all |
| subsequent new APs will automatically join the cluster. |
| Standalone APs, however, will stay in standalone mode |
| until you explicitly add them to the cluster. |
| For information on how to add standalone APs to the |
| cluster, see “Adding an access point to a cluster” on |
| |
|
|
www.gateway.com | 35 |