MSM7xx Controllers Configuration Guide v6.4.0

Licensing
• MSM720 and MSM760 controllers must have the Premium Mobility License installed to support
teaming. (Licenses must be installed individually on each controller that is part of the team.)
MSM765 zl and MSM775 zl controllers are shipped with this license pre-installed.
• You must install enough AP licenses to support all the APs you intend to manage with the team.
When teaming is enabled, AP licenses are pooled across all controllers. See “Failover”
(page 271) for more information on how AP licenses are managed.
Networking
• The connectivity settings you define on the team manager must be the same on all team
members for all ports, VLANs, etc. For example, if the LAN port on the team manager (Access
network on the MSM720) is on subnet 192.168.5.0, then all team members must also have
their LAN port (Access network) on the same subnet. As a result, any ports on a switch to
which the controllers are connected must also be configured identically.
IMPORTANT: All team members must have an IP address assigned to their LAN port (Access
network on the MSM720). This must be done even if the LAN port (Access network on the
MSM720) is not connected or not used in your setup.
• To avoid creating loops in your network, always configure teaming setting before
interconnecting the controllers.
• On the MSM720, the port used for the teaming control channel (configured under Control
channel on the Controller > Management > Teaming page) cannot be part of a trunk. HP
recommends that you use a dedicated port for teaming.
• The IP address used for the teaming control channel (configured under Control channel on the
Controller > Management > Teaming page) cannot be on the same subnet as the LAN port or
Internet port (Access network or Internet network on the MSM720).
• The DHCP server feature is not supported when controller teaming is active, therefore an
external DHCP server needs to be installed to support dynamic address assignment to controlled
APs and their users.
• APs do not have to be located on the same subnet as the team, and can be connected to the
team via an L3 network (using either DNS, DHCP option 43, or by having provisioning the
AP). However, all APs must reach the team on the same interface (either LAN port or VLAN).
This means that you cannot connect one AP to the team via the LAN port and another via a
VLAN.
• If the APs are provisioned for controller discovery, then the APs must be provisioned to discover
all controllers in the team, not just the team manager, otherwise failover is not supported.
• Multiple teams can be installed on the same subnet. If this is done, make sure that APs are
properly provisioned so that they can only associate with controllers from the correct team.
• To successfully support controller teaming, the network that connects the controllers must not
block TCP port 4999 and UDP ports 4999, 38215, and 51936.
Public access
(For more information, see “Guest access and teaming” (page 276).)
• Customization of the public access interface web content should be done via attributes retrieved
from a third-party RADIUS server. If RADIUS is not available, you must manually configure
each controller in the team with matching settings.
• Payment services are not supported.
248 Controller teaming