Hello Erman, The configured spanning tree is RSTP. There is no MSTP config name, there are no mappings. The BPDU in wireshark shows no MSTP extension. Personally I'm used to Cisco, they don't display this behaviour. I did some more digging on another network with Dell switches and RSTP. It turns out every Dell switch in an RSTP environment shows itself as the regional root.
In a network I've had to inventory recently I found an interesting fact which I couldn't explain. There were 2 switches, both configured for RSTP, yet both were convinced they were in different regions. The switches are a HPE 5710 48XGT 6QS+/2QS28 and a Dell N1108T-ON. There weren't any other STP aware switches at the moment of inventory. The HPE is a stack and supposed to be the core of this network. Due to some oversight of the person installing the devices, STP priorities were default and due to its lower MAC-address, the Dell became root. The HPE reported the Dell as root, but it also stated it was a regional root itself. After lowering the priority of the HPE to 4096 it became root, the Dell agreed on the HPE being root, but also the Dell sees itself as a regional root. In the new situation I also did some capturing. Wireshark does not show any regional information in the BPDUs. So why do these switches keep reporting they are in different regions? Following are some show and display outputs of the new situation, the old situation is no longer possible to recreate as this is a live environment. Basic RSTP info for HPE Port towards the Dell (notice the Boundary) Basic RSTP info for Dell (notice the regional root) Port towards the HPE (Dell shows the designated port ID from the HPE, but the designated bridge priority and address are its own)
RSTP switches reporting they're in different regions