Answer the question
In order to leave comments, you need to log in
RSTP on Ubiqiti, how to set it up?
Hello comrades.
I still can’t figure out how to force ubiquity so that he does not consider himself a root switch?
There are 2 switches, the Tsisk Catalyst 3750, it is the core of the network and, accordingly, the root switch in the STP topology, the Ubiqiti EdgeSwitch 8-Port 150W access switch for access points is plugged into it. I can't figure out what's wrong? Why do tsiska and ubiquity consider themselves root?. Below are the configs of the hardware.
I need help you.
Enis_Core3750#sis | i Ubi
Gi3/0/4 UbiquintiSW_AP connected trunk a-full a-1000 10/100/1000BaseTX SFP
Gi4/0/4 UbiquintiSW_AP connected trunk a-full a-1000 10/100/1000BaseTX SFP
Po3 UbiquintiSW_AP connected trunk a-full a-1000
Enis_Core3750#
description UbiquintiSW_AP
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100,1000
switchport mode trunk
switchport nonegotiate
ip dhcp snooping trust
spanning-tree mode rapid-pvst
spanning-tree extend system-id
spanning-tree vlan 1-1000 priority 4096
(WiFi Switch) #show run
!Current Configuration:
!
!System Description "EdgeSwitch 8-Port 150W, 1.8.1.5145168, Linux 3.6.5-1b505fb7, 1.0.0.4827685"
!System Software Version "1.8.1.5145168"
!System Up Time "6 days 14 hrs 0 mins 0 secs"
!Additional Packages QOS,IPv6 Management,Routing
!Current SNTP Synchronized Time: Apr 28 23:23:49 2019 UTC
!
hostname "WiFi Switch"
no network ipv6 enable
vlan database
vlan 100,1000
vlan name 100 "Data"
vlan name 1000 "Guest"
vlan routing 100 1
exit
configure
sntp server "83.162.149.224"
sntp server "133.243.238.164"
line console
exit
line telnet
exit
line ssh
exit
spanning-tree configuration name "STP"
spanning-tree mode rstp
interface 0/7
addport 3/1
exit
interface 0/8
addport 3/1
exit
snmp-server sysname "WiFi Switch"
!
interface 0/1
description 'AP_ENIS_001'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan pvid 100
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
poe opmode passive24v
exit
interface 0/2
description 'AP_ENIS_002'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan pvid 100
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
poe opmode passive24v
exit
interface 0/3
description 'AP_ENIS_003'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
poe opmode passive24v
exit
interface 0/4
description 'AP_ENIS_004'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
poe opmode passive24v
exit
......................
interface 0/7
description 'UP_TO_CORE'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
lacp actor admin state passive
exit
interface 0/8
description 'UP_TO_CORE'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
lacp actor admin state passive
exit
.......................................
interface lag 1
description 'UP_TO_CORE'
switchport mode trunk
switchport trunk allowed vlan 100,1000
vlan participation exclude 1
vlan participation include 100,1000
vlan tagging 100,1000
exit
.........
(WiFi Switch) #
VLAN0100
Spanning tree enabled protocol rstp
Root ID Priority 4196
Address 001e.7a64.xxxx
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 4196 (priority 4096 sys-id-ext 100)
Address 001e.7a64.xxxx
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Fa1/0/1 Desg FWD 19 128.3 P2p Edge
Fa1/0/2 Desg FWD 19 128.4 P2p Edge
....................
Spanning Tree Protocol......................... rstp
Bridge Max Age................................. 20
Bridge Max Hops................................ 20
Bridge Tx Hold Count........................... 6
Bridge Forwarding Delay........................ 15
Hello Time..................................... 2
Bridge Hold Time............................... 6
CST Regional Root.............................. 80:00:78:8A:20:45:24:xx
Regional Root Path Cost........................ 0
Bridge Priority................................ 32768
Bridge Identifier.............................. 80:00:78:8A:20:45:24:xx
Time Since Topology Change..................... 2 day 15 hr 37 min 31 sec
Topology Change Count.......................... 102
Topology Change in progress.................... False
Designated Root................................ 80:00:78:8A:20:45:24:xx
This bridge is the root
Interface State Role
--------- ----------------- ----------
0/1 Forwarding Designated
0/2 Forwarding Designated
0/3 Forwarding Designated
0/4 Forwarding Designated
Answer the question
In order to leave comments, you need to log in
I see that RSTP just doesn't work between two devices. They live in different instances, if Cisco received a BPDU from Ubiquity, then we would see a non-edge port type. The reason is that rapid-pvst is not the same as rstp.
Cisco's "classic" RSTP lives in an untagged wealan, so the solution is either native vlan 100 on Cisco's ports or adding the first wealan to Ubiquity's ports. It is necessary to fulfill the rule RSTP = untagged traffic.
I didn't find it for edgeswitch, but for UniFi there is this document https://help.ubnt.com/hc/en-us/articles/3600068367... and I quote:
Interoperability with PVST , PVST+, and Rapid Variants (Cisco)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question