Deployment Guide

Define Client Bridge from the Radios tab within the configuration Profile. Only one radio can be
configured as a Client Bridge. This can be either radio. Regardless of which radio is configured as the
Client Bridge, both radios will continue to provide service. All ExtremeWireless 11ax APs are supported,
provided that the AP operational mode is configured for a Centralized site. Both the Client Bridge AP
and the infrastructure AP must be an 11ax AP model: AP3xx, AP4xx, and AP5xx or the AP410C or
AP460C.
Note
AP39xx access points are not supported.
Note
For Extreme Campus Controller deployments with network policy assignment for proper end-
system visibility, the Client Bridge AP must be in a Centralized Site (Campus mode) and must
be managed by Extreme Campus Controller.
Wired and wireless clients can be managed by Client Bridge. Client trac can be forwarded on any of
the following supported topologies: Bridged@AP, Bridged@AC, Fabric Attach, and VxLAN. A wired
client refers to a device that has direct wired connectivity to the client port (GE2) of the AP. This can be
a direct connection into the AP's port or connected through a small-port switch. The wired client port
supports up to 128 simultaneous client sessions.
Note
• ExtremeWireless Wi-Fi 6 access points do not provide POE to connected clients.
• Ports on the Universal APs are labeled with the prefix ETH.
• When Client Bridge is configured on a single interface AP, the single interface is used as
the client port, not as an uplink, and you will not see the GE2 Port Function.
Network policy is applied to both wired and wireless clients in the same way. The network policy is
enforced on the Client Bridge AP before the network trac is forwarded. All configuration updates are
pushed to the Client Bridge AP before being applied to the infrastructure AP.
The role assignment for each AP is defined in its unique configuration Profile. When using Bridged@AP
and Fabric Attach topologies, ensure that the Client Bridge role assignment is synchronized with the
infrastructure AP role assignment.
Note
For a Client Bridge path, policy enforcement for clients is handled at the Client Bridged AP,
including any adjustments to topology assignment (VLAN Tagging). The infrastructure AP
operates purely as a transparent bridge for the trac that is received from the Client Bridge
AP. The same applies to management network access. If the infrastructure is configured to
require management trac on a specific VLAN, and is tagged by the infrastructure AP, the
same configuration needs to be applied to each Client Bridge AP, ensuring that the VLAN
tags match the infrastructure requirement. It behaves essentially as if the Client Bridge access
point was directly connected to the same infrastructure switch port as the infrastructure AP
that provides the path for wireless connectivity.
Related Topics
Configure Client Bridge on page 178
Deploying Client Bridge
AP Client Bridge
Extreme Campus Controller Deployment Guide for version 5.46.03 177