MSM7xx Controllers Configuration Guide v6.4.0

Unprovisioned APs
Once an unprovisioned AP has received its IP address from a DHCP server, it attempts to discover
a controller using the following methods, in order:
• UDP broadcast
• DHCP
• DNS
These discovery methods are applied on the following interfaces, in order:
• Last interface on which a controller was discovered. (Only applies to APs that have previously
discovered a controller)
• Untagged on Port 1
• All detected VLANs (in sequence) on Port 1
Provisioned APs
If connectivity settings are provisioned on the AP, then the AP uses only the provisioned settings
(see “Provisioning connectivity” (page 173). The following connectivity settings are available on
provisioned APs:
• Interface: Wireless port or local mesh link.
• VLAN support: Allows a VLAN to be designated. Discovery will then take place on the VLAN.
NOTE: If discovery is configured to take place on a VLAN over a local mesh link, a second
VLAN must be defined to send traffic over the local mesh link. The same VLAN cannot be used
to carry the control channel and local mesh traffic.
If discovery settings are provisioned on the AP, then the AP uses only the provisioned settings (see
“Provisioning discovery” (page 175)). The following discovery settings are available on provisioned
APs:
• DNS discovery: Enables custom controller names and domains to be used for discovery.
• Discovery using specific IP addresses: Enables the AP to find controllers operating at specific
IP addresses.
Discovery recommendations
NOTE: When controller teaming is active, controlled APs discover a team in the same way that
they discover non-teaming controllers.
• If the AP is on the same subnet as the controller, then UDP discovery will work with no
configuration required on either the AP or controller. This applies whether the controller is
operating as the DHCP server for the network or if a third-party DHCP server is used.
If VLANs are being used, then UDP discovery will also work with no configuration. However,
to speed up the discovery process you can provision the AP with a specific VLAN ID. This will
eliminate the need for the AP to find and attempt discovery on all available VLANs.
• If the AP is on a different subnet than the controller, UDP discovery will not work. Instead,
DHCP or DNS discovery must be used, or direct IP address discovery must be provisioned.
• DHCP discovery: If you have control of the DHCP server, enable support for the Colubris Vendor
Class as explained in “DHCP discovery” (page 149).
◦ DNS discovery: If you have control of the DNS server, you can configure it to resolve the
default controller names that an AP will search for. To use custom names, you must
Discovery of controllers by controlled APs 151