extreme_networks:switch:why_are_inactive_ports_showing_blocked_when_using_default_configuration_in_exos_22.2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| extreme_networks:switch:why_are_inactive_ports_showing_blocked_when_using_default_configuration_in_exos_22.2 [2020/11/03 20:28] – aperez | extreme_networks:switch:why_are_inactive_ports_showing_blocked_when_using_default_configuration_in_exos_22.2 [2020/11/03 20:31] (current) – aperez | ||
|---|---|---|---|
| Line 42: | Line 42: | ||
| (U) Dynamically added uplink port | (U) Dynamically added uplink port | ||
| (V) Dynamically added by VM Tracking | (V) Dynamically added by VM Tracking | ||
| + | | ||
| + | |||
| + | Environment: | ||
| + | EXOS 22.2 | ||
| + | |||
| + | Answer: | ||
| + | -Starting in EXOS 22.2, STP is enabled by default. | ||
| + | -With STP enabled all ports start in the blocked state. | ||
| + | -once the ports become active the ports then go through the rest of the STP process of listening, Learning, and | ||
| + | then start forwarding the traffic. | ||
extreme_networks/switch/why_are_inactive_ports_showing_blocked_when_using_default_configuration_in_exos_22.2.1604453327.txt.gz · Last modified: 2020/11/03 20:28 by aperez