PDF(452.8 KB) View with Adobe Reader on a variety of devices
ePub(472.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(498.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 29, 2020
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document lists 2 methods to successfully setup the 1532's with daisy chaining and allow ethernet bridging of a remote switch's traffic to flow through to the core network.
Controller running 126.96.36.199 and up.
Minimum of 2 1532 outdoor AP's(Access Point). You can use any other model of AP as the wired root, but for daisy chaining you have to use 2 1532's, of course.
Before starting any of this configuration, please make sure that the remote switch is not connected to the Subordinate RAP(Root Access Point) until the configuration on the mesh network is complete and verified to be correct. If you do not do this, there is a high probability that spanning tree will take down the entire mesh network that is connected to the RAP. It will block the root ap switch port and drop all the children connected to it. This can create a whole new set of issues due to the re-convergence of the mesh network. Potentially causing an extended outage and a lot of frustration.
2504 Wireless LAN Controller
2702 as the wired RAP
2 1532's to daisy chain
2 switches (3750's in my lab), one core, one remote.
1107 is native and what the AP's connect to the controller on.
12 is remote wired client vlan.
Easiest method first.
Enable Vlan transparent on the controller. With this enabled it will pass the native and also pass the tagged vlan's from the remote side without having to define them on the Rap/Map gig interfaces. More on this in the next example.
Wired Root AP mesh configuration
Mesh Access Point(MAP) configuration
First Mesh AP of the daisy chain. This is considered the Primary of the chain. It uses its 5Ghz radio to connect to the wired Rap. Note that daisy chaining is enabled on this AP.
Subordinate AP-- Daisy Chain Configuration
Subordinate AP of the daisy chain. Notice that it is configured as a Rap and not a Map. This AP will use its POEin port to connect to the Lan port on the primary Map AP. Note that daisy chain is enabled on this AP. The traffic from this AP's lan port as well as it's 2.4Ghz and 5Ghz radio will be sent to the primary AP via the ethernet cable and then transmitted out the Primary AP's 5Ghz radio to the Rap at the core. you then connect the Lan port on this AP to the remote switch.
Since this AP is configured as a Rap you can also change it's 5Ghz radio to a different channel than the core root AP. This way you can have channel separation to additional downstream Map's from this subordinate AP.
More complex, but gives a bit more flexibility with allowing or not allowing vlans at the gig interfaces of the mesh ap's.
Vlan transparent is disabled for this configuration.
Please note that for this configuration to work you have to have vlan support enabled on all the ap's that are part of this bridge group or that will be connecting to each other over the mesh.
You also have to define the native vlan as well as the allowed vlan's on all the interfaces of the AP's along the mesh path.
Screen shots to hopefully make this point clear.
Wired Root AP configuration
Primary MAP AP configuration
Subordinate RAP connected to the Primary AP and the remote switch.