Mobility agent, benefits? or am i doing it wrong.

[Dallas Brown]

Hello,

I am just at the point of labing a wireless setup. I have configured a 3850 as a wireless controller. I have another stack of 3850's that will be going in the same building that I was thinking of making a Mobility agent that points at the controller. What is the actual benefit of a mobility agent, it doesn't seem to get any of the configs i made on the Controller, it seems like i have to configure all WLANS and AP groups on both anyway, so why would I even bother with a mobility agent? It seems like it would be easier to to just make both stacks controllers.  Am I doing it wrong or should they  replicate configs?  One thing I am not sure about is the DHCP pool on the agent i set it as the controller for that pool, but that maybe wrong, I attached configs as well.

Thank you

Mobility Controller Summary:

Mobility Role                                   : Mobility Controller
Mobility Protocol Port                          : 16666
Mobility Group Name                             : **********
Mobility Oracle IP Address                      : 0.0.0.0
DTLS Mode                                       : Enabled
Mobility Domain ID for 802.11r                  : 0x89f
Mobility Keepalive Interval                     : 10
Mobility Keepalive Count                        : 3
Mobility Control Message DSCP Value             : 48
Mobility Domain Member Count                    : 1

Link Status is Control Link Status : Data Link Status

Controllers configured in the Mobility Domain:

IP               Public IP        Group Name       Multicast IP     Link Status
-------------------------------------------------------------------------------
192.168.100.1    -                **********    0.0.0.0          UP   : UP

Switch Peer Group Name            : **********
Switch Peer Group Member Count    : 1
Bridge Domain ID                  : 100
Multicast IP Address              : 0.0.0.0

IP               Public IP             Link Status
--------------------------------------------------
192.168.100.129  192.168.100.129       UP   : UP

Mobility Agent Summary:

Mobility Role                                   : Mobility Agent
Mobility Protocol Port                          : 16666
Mobility Switch Peer Group Name                 : **********
Multicast IP Address                            : 0.0.0.0
DTLS Mode                                       : Enabled
Mobility Domain ID for 802.11r                  : 0x89f
Mobility Keepalive Interval                     : 10
Mobility Keepalive Count                        : 3
Mobility Control Message DSCP Value             : 48
Switch Peer Group Members Configured            : 1

Link Status is Control Link Status : Data Link Status

The status of Mobility Controller:

IP              Public IP            Link Status
------------------------------------------------
192.168.100.1   192.168.100.1        UP   : UP

Switch Peer Group members:

IP              Public IP            Data Link Status
-----------------------------------------------------
192.168.100.129 192.168.100.129      UP

[Rasika Nayanajith · Accepted solution]

If you configure those two as MC, then roaming between those two won't be optimum. Best way to configure is given building switches in a single SPG as MA (obviously in your case one stack has to be MC if there is no centralized MC).

If these switch stacks are separated in L3 (unlikely if it is in a single building), & you put them as MC, then those two should be in different mobility group. (as 1MC per one mobility sub domain). 

This gives some idea how this CA setup works. In that case 5760 acting as MC, but you can think of as a 3850 stack in your case.

http://mrncciew.com/2013/12/14/3850ma-with-5760mc/

HTH

Rasika

**** Pls rate all useful responses ****

[Dallas Brown]

Thank you. Appreciate the answer