Spanning tree on XOS, is 802.1s and EMISTP the same thing?


Userlevel 3
Spanning tree on XOS, is 802.1s and EMISTP the same thing ?

4 replies

Userlevel 1
Hi ,

EMISTP mode is proprietary to Extreme Networks and is an extension of STP that allows a physicalport to belong to multiple STPDs by assigning the port to multiple VLANs.
BPDUs are sent with an 802.1Q tag having an STPD instanceIdentifier (STPD ID) in the VLAN ID field.

This encapsulation mode supports the following STPD modes of operation: 802.1D and 802.1w.
Userlevel 3
Aleixo Gomes wrote:

Hi ,

EMISTP mode is proprietary to Extreme Networks and is an extension of STP that allows a physicalport to belong to multiple STPDs by assigning the port to multiple VLANs.
BPDUs are sent with an 802.1Q tag having an STPD instanceIdentifier (STPD ID) in the VLAN ID field.

This encapsulation mode supports the following STPD modes of operation: 802.1D and 802.1w.

thankyou, appolgies for the delay I don't seem to get emails from the "hub" anymore
Userlevel 7
Aleixo Gomes wrote:

Hi ,

EMISTP mode is proprietary to Extreme Networks and is an extension of STP that allows a physicalport to belong to multiple STPDs by assigning the port to multiple VLANs.
BPDUs are sent with an 802.1Q tag having an STPD instanceIdentifier (STPD ID) in the VLAN ID field.

This encapsulation mode supports the following STPD modes of operation: 802.1D and 802.1w.

Hi Simon,
I opened a ticket with our community platform provider to check into this for you. Meanwhile, can you please ensure your mail server isn't rejecting email from@getsatisfaction.com?
Userlevel 7
Aleixo Gomes wrote:

Hi ,

EMISTP mode is proprietary to Extreme Networks and is an extension of STP that allows a physicalport to belong to multiple STPDs by assigning the port to multiple VLANs.
BPDUs are sent with an 802.1Q tag having an STPD instanceIdentifier (STPD ID) in the VLAN ID field.

This encapsulation mode supports the following STPD modes of operation: 802.1D and 802.1w.

Another update - I'm told that your email address was on the bounce list and has now been removed. You should start receiving emails again 🙂

Reply