Technical data

ICR Limitations

 Each controller is identified by one IP address and this must be the virtual IP

address in the Meru interface. No controller IP interface address that participates

in a roaming domain can reside in VLAN interface. This address is used as the

end-point of inter-controller tunnels. Stations can use VLAN-connected ESSIDs.

 Each controller maintains a list of roaming group members as IP addresses. All

member controller configurations must have the same list of IP addresses and

they must be in the same order.

 If a member is added after the group has been created, all controllers must add

the member and restart the service. The restart will cause stations to be dropped

in all member controllers until the feature is back online.

 Each member controller should have the exact same shared ESSID configuration

to ensure predictable/desired roaming.

 To activate fixed mode, one of the controllers needs to be acknowledged as the

DHCP home (a question asked after entering each peer IP address).

 A roaming group can contain up to five controllers.

 Clients using inter-controller roaming can be identified using the command show

roaming-domain all (my interface addresses, peer controllers, my roaming

stations, stations at home here, stations onlink now).

 Tunnels are per-controller.

 For N+1, failover is not seamless but IP layer mobility is retained.

 Ongoing IP sessions such as TCP/IP or UDP/IP continue across inter-controller

roaming. Ongoing voice calls also continue but the QoS is not preserved on the

subsequent controller; Captive Portal users have to re-authenticate as well.

 Only one roaming domain is supported and the assumption is that all members

support the same ESSID among the controllers. An ESSID can be bound to untagged

(Meru Networks) or tagged (VLAN) interface.

 No fast roaming is supported, with the switchover time in the order of seconds.

 For this release, dual Ethernet operation, active-active or active-redundant, is

not supported.

 After changing VLAN configuration, inter-controller roaming must be restarted.

Caution!

The above operation is service-disrupting, and should only be performed when

absolutely necessary.