Users Guide

assigned to the branch controller in the whitelist entry. To assign a different configuration to an unprovisioned
branch controller, you must delete the whitelist entry and create a new branch controller whitelist entry with
the correct branch config group.
When you remove an entry for an active branch controller from the whitelist on the master controller, that
branch controller no longer receives configuration or license updates from the master controller, but continues
to operate as previously configured. As the license server is the master controller, any operation related to the
licensing does not work after it is detached. If you remove an individual branch controller entry from the
whitelist before that branch controller is connected to the network, that branch controller is not automatically
provisioned as a branch controller, and remains inactive on the network until manually provisioned.
Add branch controllers to the master controller whitelist by navigating to Configuration>Branch>Smart
Config and selecting the Whitelist tab. The settings on the Whitelist tab are described in the table below.
Parameter Description
MAC
address
MAC address of the branch controller
Hostname Hostname of the master controller
Remote
Group
The name of the branch config group whose settings are applied to the branch controller.
Table 64: Branch Config Group Whitelist Settings
PortFast and BPDU Guard
The following section describes some of the Layer-2 Spanning Tree Protocol (STP) features for the branch
controller solution. Currently, PortFast and Bridge Protocol Data Unit (BPDU) Guard features are supported,
which work along with existing L2 STP feature. These two features enhance network reliability, manageability,
and security for the existing L2 STP feature.
Some devices and local stacks running on systems/workstations are capable of generating potential STP
BPDUs that cause Denial of Service (DOS)attacks. PortFast and BPDU Guard features provide stability and
security for network topologies to prevent such attacks.
PortFast
The PortFast feature is introduced to avoid network connectivity issues. These issues are caused by delays in
STP enabled ports moving from blocking-state to forwarding-state after transitioning from the listening and
learning states. STP enabled ports that are connected to devices such as a single switch, workstation, or a
server can access the network only after passing all these STP states. Some applications need to connect to the
network immediately, else they will timeout.
Enabling the PortFast feature causes a switch or a trunk port to enter the STP forwarding-state immediately or
upon a linkup event, thus bypassing the listening and learning states. The PortFast feature is enabled at a port
level, and this port can either be a physical or a logical port. When PortFast feature is enabled on a switch or a
trunk port, the port immediately transitions to the STP forwarding state.
Though PortFast is enabled the port still participates in STP. If the port happens to be part of topology that
could form a loop, the port eventually transitions into STP blocking mode. PortFast is usually configured on an
edge port, which means the port should not receive any STP BPDUs. If the port receives any STP BPDU, it
moves back to normal/regular mode and will participate in the listening and learning states.
Dell Networking W-Series ArubaOS 6.5.x | User Guide BranchController Config for Controllers |
249