Cisco Catalyst IW9167E Heavy Duty Access Point Configuration Guide, Release 26.1.x

RAP Ethernet Daisy Chain

Updated: April 10, 2026

Want to summarize with AI?

Enhances the existing Ethernet bridging functionality by forcing the bridge access point to use the Ethernet link as the uplink backhaul.

This feature enhances the existing Ethernet bridging functionality by forcing the bridge access point to use the Ethernet link for uplink backhaul instead of using a wireless link. If the Ethernet link fails, the access point continues to avoid selecting a parent over wireless backhaul.

This figure shows an example of RAP Ethernet Daisy Chain topology. Each RAP receives a standalone DC power source

Figure 1. RAP Ethernet Daisy Chain topology

Table 1. Port mapping
Panel Label	SW Interface
mGig POE-IN port	wired 0
SFP	wired 1

All APs in the daisy chain operate in mesh bridge mode or Flex+Bridge mode with the Root AP role. The PoE-IN (wired0) and SFP (wired1) ports can serve as uplink ports, and the PoE-IN (wired0) port has higher priority than the SFP (wired1) port.
Disable VLAN transparency on all daisy-chained RAPs.
To enable VLAN support on each root AP:
- For bridge mode APs, use the ap name name-of-rap mesh vlan-trunking [native] vlan-id command to configure a trunk VLAN on the corresponding RAP.
- For Flex+Bridge APs, you must configure the native VLAN ID under the corresponding flex profile.

Limitations in Cisco IOS XE Cupertino 17.9.3

The feature has these limitations in Cisco IOS XE Cupertino 17.9.3:

You must use the primary Ethernet port (mGig port) as the uplink. SFP port-to-SFP port connections are not supported. This limitation impacts network throughput, since 2.5Gbps or 5Gbps copper SFP modules are unavailable for SFP port to mGig port connections.
Do not use the existing persistant-ssid command to enable the RAP Ethernet Daisy Chain feature.

Updates in Cisco IOS XE Dublin 17.11.1

This feature is enhanced to support the following functions in Cisco IOS XE Dublin 17.11.1:

When Wireless Spanning Tree Protocol (WSTP) hello is enabled, the system supports automatic root port detection. This feature allows the RAP to use any port as its uplink. The subsequent topology diagram illustrates this feature.

Figure 2. RAP Ethernet Daisy Chain With WSTP Topology
A new command neamed rap-eth-daisychain is introduced to enable the feature.

Wireless LAN Spanning Tree Protocol

Wireless LAN spanning tree protocol (WSTP) organizes a Cisco mesh network into a loop-free spanning tree topology. It quickly configures a mesh network into a stable, loop-free, optimal spanning tree topology. An optimal topology provides least-cost paths to the primary Ethernet LAN. WSTP Hello messages are used to build the WSTP topology.

The WSTP super root is a single RAP that is elected as the highest level “super” root for the entire WSTP spanning tree. The super root is directly attached to the primary LAN and transmits zero-cost WSTP SR Hello messages on its Ethernet root port to advertise the primary LAN to RAPs.

Comparison with previous releases

The following table compares the daisy chain features in current release and prior to 17.11:


	Prior to Release 17.11.1	Release 17.11.1
Topology	Fixed topology RAP must use its mGig port as uplink in daisy chain topology	Flexible topology RAP can use either the mGig port or the SFP port as an uplink in the daisy chain topology. To enable this, use WSTP on the AP.
Feature enablement	Persistant-ssid in AP profile ¹	rap-eth-daisychain in Mesh profile
Ring Topology	Not supported ²	Not supported

¹ Persistant-ssid is still supported in 17.11. This ensures the daisy chain function is not impacted after upgrading from a previous release to 17.11 with the old configuration. However, persistant-ssid is not recommended in 17.11. The new rap-eth-daisychain command is recommended.

² Supported only on IW6300 access point, by enabling daisychain-stp-redundancy. For more information, see the RAP Ethernet Daisy Chain Redundancy for STP Ring Topology section in Cisco Catalyst IW6300 Heavy Duty Series and 6300 Series Embedded Services Access Point Software Configuration Guide.

RAP Ethernet Daisy Chain configuration

This section provides procedures for the RAP Ethernet daisy chain configuration.

Preconfigure RAP Ethernet Daisy Chain before field deployment

This procedure describes how to complete the preconfiguration steps in the lab before setting up for field deployment.

Procedure

	1.	Unpack, connect, and power on the AP.
	2.	Join each AP to controller with mGig port. Refer to the figure for details.
	3.	Configure the AP to bridge mode. Then, set the AP role to Root AP. For detailed configuration procedures, see https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-11/config-guide/b_wl_17_eleven_cg/m_mesh_ewlc.html#task_pnb_bwy_mlb .
	4.	Configure the RAP Ethernet Daisy Chain. Create a mesh profile and enable the RAP Ethernet Daisy Chain feature. See Enabling RAP Ethernet Daisy Chain . Attach the profile to all RAPs. Configure one AP as the Super Root. This AP should be the first hop to the wireless controller. See Configure Super Root . Configure the primary Ethernet port on the Super Root AP if you use the SFP port as the uplink. See Configure primary Ethernet port .
	5.	Enable Ethernet Bridging and Configure Ethernet port. See Configuring Ethernet Bridging and Ethernet Port . Enable Ethernet Bridging. Configure the Ethernet port on both Port 0 and Port 1, including port mode and VLAN. Configuring the port as trunk mode is recommended.
	6.	Verify the behavior in daisy chain topology. Connect the RAPs using the wired port, one at a time. Note The RAP which is the first hop from wireless controller should be configured as Super Root, as shown in the figure. Ensure that each RAP at every hop can join the controller. Note In field deployment, just repeat Step 6 of this procedure. Make sure you configure the first hop as Super Root.

Enable RAP Ethernet Daisy Chain from CLI

This procedure describes how to enable RAP Ethernet Daisy Chain feature.

Procedure

	1.	Use the configure terminal command to enter into configuration mode. Example: `Device# configure terminal`
	2.	Use the wireless profile mesh profile command to configure a mesh profile and enter mesh profile configuration mode. Example: `Device(config)# wireless profile mesh default-mesh-profile`
	3.	Use the ethernet-bridging command to connect remote wired networks to each other. Example: `Device(config-wireless-mesh-profile)# ethernet-bridging`
	4.	Use the rap-ethernet-daisychain command to enable the RAP Ethernet Daisy Chain feature on a Remote Access Point (RAP). Example: `Device(config-wireless-mesh-profile)# rap-ethernet-daisychain`
	5.	(Optional) Use the show wireless profile mesh detailed command or show wireless mesh ethernet daisy-chain summary command to verify the configuration on the wireless controller. Example: `Device# show wireless profile mesh detailed <profile name> … RAP ethernet daisychain : ENABLED` `Device# show wireless mesh ethernet daisy-chain summary AP Name BVI MAC BGN Backhaul Ethernet STP Red Super Root ---------------------------------------------------------------------------------------------------- APxxxxxx xxxxxxx xxxxx Ethernet0 Up Up NA Enabled` Or use the show mesh config command on AP, as shown in the following example: `Device#show mesh config … RAP Ethernet Daisy Chain: Enabled Daisy Chain Root: Disabled`

Enable RAP Ethernet Daisy Chain from GUI

This procedure describes how to Enable RAP Ethernet Daisy Chain from GUI.

Before you begin

Procedure

	1.	Choose Configuration > Wireless > Mesh > Profiles.
	2.	Click the mesh profile. The Edit Mesh Profile page is displayed.
	3.	Check the RAP Ethernet Daisy Chain check box.

Click Update & Apply to Device.

Configure Super Root

This procedure ensures that the first RAP connected to the upstream switch is configured as the super root.

The super root device acts as the originator of all WSTP hello messages. Other RAPs initiate hello messages only after they receive messages from the super root. This approach establishes proper topology formation and prevents loops.

You can configure the super root from either the wireless controller or the AP.

Procedure

	1.	Use the ap nameap-name mesh rap-eth-daisychain super-root command to configure a super root from the controller. Example: `Device# ap name ap-1 mesh rap-eth-daisychain super-root`
	2.	Use the capwap ap mesh wstp super-root command to configure a super root from the AP. Example: `Device# capwap ap mesh wstp super-root`
	3.	(Optional) Use the show ap name mesh config general command from the controller to display the general mesh configuration parameters for a specific access point (AP). Example: `Device# show ap name ap-1 mesh config general … RAP ethernet daisychain : Enabled Super Root : Enabled`
	4.	(Optional) Use the show mesh config command from the AP to display the general mesh configuration parameters. Example: `Device# show mesh config … RAP Ethernet Daisy Chain: Enabled Daisy Chain Root: Enabled`

Configure primary Ethernet port

This procedure ensures that the super root access point establishes its uplink to the upstream switch through the designated primary Ethernet port.

For the IW9167EH, Ethernet port 0 is the default primary port and must be used to maintain proper topology formation and WSTP operation.

Procedure

	1.	Use the ap nameap-name mesh backhaul ethernetethernet-num command to configure the primary Ethernet port from the controller. Example: `Device# ap name ap-1 mesh backhaul ethernet 1`
	2.	(Optional) Use the show ap name mesh config general command from the controller to display the general mesh configuration parameters for a specific access point (AP). Example: `Device# show ap name ap-1 config general … AP Primary Ethernet port : 1 RAP ethernet daisychain : Enabled Super Root : Disabled`
	3.	(Optional) Use the show mesh config command from the AP to display the general mesh configuration parameters. Example: `Device# show mesh config … RAP Ethernet Daisy Chain: Enabled Daisy Chain Root: Enabled AP Primary ethernet backhaul interface: 1`
	4.	(Optional) Use the show mesh adjacency parent command from the AP to verify the parent-child relationship in a mesh topology. Example: `Device# show mesh adjacency parent AdjInfo: Wired Backhaul: 1 [xx:xx:xx:xx:xx:xx]`

Configuring Ethernet Bridging and Ethernet Port

Configure Ethernet bridging from CLI

This procedure ensures that Ethernet connectivity is enabled on Mesh Access Points (MAPs) by configuring Ethernet bridging on the Root AP and the corresponding MAPs. Enabling Ethernet bridging activates the MAP Ethernet ports, allowing wired devices to connect and communicate through the mesh network.

To enable Ethernet bridging on the AP, complete these steps:

Procedure

	1.	Use the configure terminal command to enter global configuration mode. Example: `Device# configure terminal`
	2.	Use the wireless profile meshprofile-name command to create a mesh profile and enter the mesh configuration mode. Example: `Device(config)# wireless profile mesh rap-eth-daisy`
	3.	Use the ethernet-bridging command to connect remote wired networks to each other. Example: `Device(config-wireless-mesh-profile)# wireless profile mesh rap-eth-daisy`
	4.	Use the no ethernet-vlan-transparent command to disable VLAN transparency to ensure that the bridge is VLAN aware. Example: `Device(config-wireless-mesh-profile)# no ethernet-vlan-transparent`
	5.	Use the end command to return to privileged EXEC mode. Example: `Device(config-wireless-mesh-profile)# end`
	6.	(Optional) Use the show wireless profile mesh detailed rap-eth-daisy command to verify the configuration. Example: `Device# show wireless profile mesh detailed rap-eth-daisy Mesh Profile Name : rap-eth-daisy -------------------------------------- Description : Bridge Group Name : unconfigured Strict match BGN : DISABLED Amsdu : ENABLED Background Scan : DISABLED Channel Change Notification : DISABLED Backhaul client access : DISABLED Ethernet Bridging : ENABLED Ethernet Vlan Transparent : DISABLED Daisy Chain SP Redundancy : DISABLED Full Sector DFS : ENABLED`

Configure Ethernet bridging from GUI

This procedure enables Ethernet bridging on the Root AP and associated MAPs, allowing Ethernet traffic to be forwarded across the mesh network.

Follow these steps to configure Ethernet Bridging from wireless controller GUI:

Procedure

	1.	Choose Configuration > Wireless > Mesh > Profiles .
	2.	Click Add .
	3.	In General tab, enter the Name of the mesh profile.
	4.	In Advanced tab, uncheck the VLAN Transparent check box to disable VLAN transparency.
	5.	In Advanced tab, check the Ethernet Bridging check box.
	6.	Click Apply to Device .

Configure the Ethernet port from the CLI

This procedure describes how to configure the Ethernet port on a RAP.

The secondary Ethernet port on the RAP supports Access mode and Trunk mode..

Procedure

Use the ap nameap-name mesh ethernet ethernet mode access vlan-ID command to configure the Ethernet port in Access mode.

Example:

Device# ap name ap-1 mesh ethernet 1 mode access 4

Configure the Ethernet port in Trunk mode.

VLAN support must be enabled, and VLAN transparency must be disabled in your mesh profile.

Use the ap nameap-name mesh vlan-trunking native vlan-ID command to configure the Ethernet port in Trunk mode.
Example:
```
Device# ap name ap-1 mesh vlan-trunking native 4
```
Use the ap nameap-name mesh ethernet ethernet mode trunk vlan native vlan-ID command to configure the Ethernet port in Trunk mode.
Example:
```
Device# ap name ap-1 mesh ethernet 1 mode trunk vlan native 4
```
Use the ap nameap-name mesh ethernet ethernet mode trunk allowed vlan-ID command to configure the allowed VLANs for the trunk port.
Example:
```
Device# ap name ap-1 mesh ethernet 1 mode trunk allowed 4
```
VLAN filtering is permitted on an Ethernet port of any Mesh or Root Access Point. This setting is active only when VLAN transparency is disabled in the mesh profile.

Configure Ethernet port from GUI

This procedure describes how to configure Ethernet port from wireless controller GUI:

Procedure

	1.	Choose Configuration > Wireless > Access Points. The All Access Points section, which lists all the configured APs in the network, is displayed with their corresponding details.
	2.	Click the configured mesh AP. The Edit AP window is displayed.
	3.	Choose the Mesh tab.
	4.	In the Ethernet Port Configuration section, from the Port drop-down list, choose the port to configure.
	5.	From the Mode drop-down list, choose access mode or trunk mode.
	6.	In the Native VLAN ID field, enter the native VLAN for the trunk port.
	7.	Click Update and Apply to Device.

Debug and verify WSTP

This procedure describes how to use CLI commands to debug the Wireless Termination Point (WTP) and to display Wireless Spanning Tree Protocol (WSTP) statistics.

Procedure

Use the debug mesh wstp command to debug WTP.

Example:

AP# debug mesh wstp

error    Mesh wstp error debugs
events   Mesh wstp events debugs
packets  Mesh wstp packet debugs

Use the show mesh stats command to display the WSTP statistics.

Example:

AP# show mesh stats

WSTP stats:
Attach-Cnt Hello-TX Hello-Rx TCN-TX TCN-RX SR-Chg-Cnt ST-Roam-Cnt
	0       58       58      0      0          0           0

Need help?

Open a support case

(Requires a Cisco Service Contract)

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.