How to avoid STP loop on RAP deployment wired ports IAP 4.0

Aruba Employee
Aruba Employee

Introduction :



Hotel customers who deploy RAP3 in hotel rooms want to allow their guests to use both the eth1 and eth2 ports on the AP, but are worried that a guest could accidentally connect the ports together, causing a loop that could bring do​wn their wired network.



Feature Notes :


  1. This feature is only supported by IAP with more than three Ethernet ports--RAP3 and RAP155.

  2. IAPv4.0 enabled the AOS feature STP for IAP to detect and avoid loops



Environment : Typically scenario of rap deployment in customer hotel rooms. This will be the common scenario of connecting two ports together by mistake causing loop on the wired ports on the RAP itself. This guide and configuration of enabling STP on IAP will help us to detect and avoid loop.


Configuration Steps :



Go to wired setting -->Select  Spanning tree and make sure it is enabled.



From CLI

wired-port-profile STP
 switchport-mode trunk
 allowed-vlan all
 native-vlan guest
 no shutdown
 access-rule-name STP
 speed auto
 duplex auto
 type employee
 auth-server InternalServer
 captive-portal disable
 no dot1x

enet0-port-profile default_wired_port_profile
enet1-port-profile STP
enet2-port-profile STP
enet3-port-profile STP
enet4-port-profile STP

Answer : From below, we could notice from show port status the stp-status shows forwarding state.



Troubleshooting : From CLI, when we run show ap debug spanning tree will help us to troubleshoot and understand for bridge priortity/port status/cost and state details as shown below.

IAP uplink packet-captures also will also help to understand the STP traffic.




User-added image

Version history
Revision #:
1 of 1
Last update:
‎07-04-2014 02:19 AM
Updated by:
Labels (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: