Tsunami MP.11 Installation and Management Model 5012-SUR ...
Tsunami MP.11 Installation and Management Model 5012-SUR ...
Tsunami MP.11 Installation and Management Model 5012-SUR ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
System Overview <strong>Tsunami</strong> <strong>MP.11</strong> <strong>5012</strong>-<strong>SUR</strong> <strong>Installation</strong> <strong>and</strong> <strong>Management</strong><br />
Virtual Local Area Networks (VLANs)<br />
For example, consider the above diagram which has a Radius Server at its back-end with two different BSU’s: BSU1 <strong>and</strong><br />
BSU2 <strong>and</strong> one SU in roaming. Let's assume that user has pre-configured SU VLAN configuration on Radius Server as:<br />
SU in Access Mode & its Access VLAN ID as 100 <strong>and</strong> Access VLAN Priority as 5.<br />
During the registration of SU with BSU1, BSU1 sends SU information in the form of Access-Request frame to the Radius<br />
Server. The Radius Server validates SU’s MAC address <strong>and</strong> if the SU is authorised, it sends an Access-Accept frame<br />
with Vendor Specific Attributes to BSU1 which has VLAN configuration on it. Thus, BSU1 receives VLAN configuration for<br />
SU with the SU’s Access VLAN ID as 100 <strong>and</strong> access VLAN priority as 5.<br />
When SU moves from the range of BSU1 to BSU2, a similar process takes place <strong>and</strong> the Radius Server provides the<br />
same VLAN ID to the SU through BSU2. Thus the SU has same VLAN ID <strong>and</strong> Priority throughout its roaming. This<br />
ensures a centralized management of SU’s VLAN configuration via the Radius Server.<br />
When there is no VLAN configuration via Radius Server, BSU-SU follows the normal procedure of working.<br />
NOTE: When SU VLAN Status is enabled, SU ignores the VLAN configuration from the Radius Server <strong>and</strong> BSU as SU<br />
VLAN status has the highest priority.<br />
41