Brocade Communications Systems RFS6000 System Reference Manual page 322

5
Layer 3 mobility
•
•
•
•
•
•
•
•
•
NOTE
When using Layer 3 Mobility ensure that TCP traffic on port 58788 is allowed on the network(s)
where wireless clients will be roaming from and to.
To configure Layer 3 Mobility for the controller:
1. Select Services > Layer 3 Mobility from the main menu tree.
308
Seamless Client roaming between controllers on different Layer 3 subnets, while retaining the
same IP address.
Static configuration of mobility peer controllers.
Layer 3 support does not require any changes to the Client. In comparison, other solutions
require special functionality and software on the Client. This creates numerous inter-working
problems with working with Clients from different legacy devices which do not support Layer 2
controllering.
Support for a maximum of 20 peers, each handling up to a maximum of 500 Clients.
A full mesh of GRE tunnels can be established between mobility peers. Each tunnel is between
a pair of controllers and can handle data traffic for all Clients (for all VLANs) associated directly
or indirectly with the Client.
Data traffic for roamed Clients is tunneled between controllers by encapsulating the entire
Layer 2 packet inside GRE with a proprietary code-point.
When Clients roam within the same VLAN (Layer 2 Roaming), the behavior is retained by
re-homing the Client to the new controller so extra hops are avoided while forwarding data
traffic.
Clients can be assigned IP addresses statically or dynamically.
Forward and reverse data paths for traffic originating from and destined to Clients that have
roamed from one Layer 3 subnet to another are symmetric.
The Layer 3 Mobility screen appears with the Configuration tab displayed.
Brocade Mobility RFS6000 and RFS7000 System Reference Guide
53-1001858-01