Filter
Top Products
Multiple Controller Layer 2 Deployment
Multiple controllers must all have connectivity to each other via the same Layer 2 broadcast domain. Both
controllers are configured for multicast as shown, using the identical access point multicast groups on each
controller to limit fragmentation. With the assumption that this Layer 2 broadcast domain is connected via a
common switch or a common set of switches, CGMP/IGMP snooping on these switches must be disabled for
this single VLAN or run 4.0.206.0 or later WLC software. With the Vocera Broadcast function and a user
roam from an access point on one controller to an access point on a different controller, there is no mechanism
for IGMP joins to be forwarded to the new Layer 2 port for IGMP snooping to work. Without an IGMP
packet reaching the upstream CGMP or IGMP capable switch, the specified multicast group is not forwarded
to the controller and therefore is not received by the client. In some cases this might work, if a client that is
part of the same Vocera Broadcast group has already sent this IGMP packet before the roaming client roams
onto the new controller With the advantages of version 4.0.206.0, a client who roams to another controller as a
Layer 2 roam receives a general IGMP query immediately after authentication. The client should then respond
with the interested groups and the new controller is then bridged this to the locally connected switch. This
allows the advantages of IGMP and CGMP on your upstream switches.
You can create additional badge SSIDs and Layer 2 domains for separate badge networks as long as your
network is configured to pass multicast traffic appropriately. Also, each Vocera Layer 2 broadcast domain
created must exist everywhere a controller is connected to the network so as not to break multicast.
Figure 6Multiple Controller Layer 2 Deployment
Multiple Controller Layer 3 Deployment
The Layer 3 roaming deployment strategy should only be used with controller−to−controller roaming with
WLC software release 4.0.206.0 or later. If a client that has been connected to the Vocera broadcast group and
receives the appropriate multicast stream and roams to another controller as a Layer 3 roam with the LWAPP
Layer 3 roaming configured, it is queried for interested multicast groups. The client, when sourcing to the
same Vocera broadcast group, has these packets delivered to the anchor controller through the EoIP tunnel