Technical data

How Inter-Controller Roaming Works

After 802.11 re-authentication takes place on a subsequent AP and controller, the

station’s original IP address and connectivity are preserved. (Note that the QoS flows

are not handed off across the roaming domain.)

Note that intercontroller roaming does not support the dynamic addition or deletion

of peers or anchored ESSIDs to/from the roaming domain. Before adding/deleting any

peers to/from the existing list, stop the roaming-domain using the command stop.

And after adding the peers start the roaming domain again using the command start.

GRE is not supported in a roaming domain. Captive Portal reauthenticates when it

roams to a new ICR controller.

Configuring Intercontroller Roaming with the Web UI

Intercontroller roaming is one of the Global Controller Parameters that you set when

you configure a controller at Configuration > Devices > Controller. The value for

Roaming Domain Sate can be either Enable or Disable.

Configuring Intercontroller Roaming with the CLI

ICR can only be configured with the CLI. There is no Web UI interface at this time.

The following commands are used to configure ICR:

 roaming-domain essid

 roaming-domain peer-controller

 roaming-domain start

 show roaming-domain

 roaming-domain stop

 show roaming-domain

These commands are described in detail in the System Director Command Reference

Guide.

Intercontroller Roaming Configuration Example

This example lists the three roaming domain commands. The controller 172.19.2.20

is added to the ICR, and then roaming is started.

default# configure terminal

default (config)# roaming-domain ?

peer-controller Add the peer controller into roaming domain.

start start roaming domain.

stop stop roaming domain.

default (config)# peer-controller 172.19.2.20

default (config)# roaming-domain start

default (config)# exit

default#