© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 47 of 70
Figure 15. Configuring Mobility Group on Multiple Mobility Controllers on Cisco Catalyst 3850
Assume that there was an acquisition of the company next door, and now the two networks have to be integrated
in the current network. The network in the acquired company operates in routed access design mode, as shown by
the diagram. The new switch can be configured to operate as a mobility agent under the previously defined mobility
controller switch in the network.
As far as the SPG membership is concerned, there is a choice. If the two user groups are going to be integrated,
OR in terms of keeping the roams simple, the customer can configure just one SPG under a Cisco Catalyst 3850-
based mobility controller. One SPG defined on a Cisco Catalyst 3850 mobility controller switch can contain up to
16 member mobility agents in the SPG.
The other choice is to create a different SPG on the mobility controller switch and insert the new mobility agent
switches in this new SPG. If the user groups from the present company and the acquired company are not going to
roam across the respective workspaces, then a new SPG can be created in such a case. In the example network
preceding, the administrator chooses to create a second SPG, an assumption convenient in order to better explain
the roaming effect on clients.
Relevant configuration that needs to be done on the mobility controller in this case is as in the following:
wireless mobility controller peer-group SPG2
wireless mobility controller peer-group SPG2 member ip 20.1.8.2 public-ip
20.1.8.2
where an SPG, SPG2, is defined on the mobility controller, with 20.1.8.2 as the switch/wireless management IP
addresses of the mobility agent switch configured as member of SPG2.