Reset Search
 

 

Article

Why are inactive ports showing blocked when using default configuration in EXOS 22.2?

« Go Back

Information

 
TitleWhy are inactive ports showing blocked when using default configuration in EXOS 22.2?
Question

Why are inactive ports showing blocked when using default configuration in EXOS 22.2?

 X460G2-24t-G4.6 # show vlan "Default"
VLAN Interface with name Default created by user
    Admin State:         Enabled     Tagging:   802.1Q Tag 1
    Description:         None
    Virtual router:      VR-Default
    IPv4 Forwarding:     Disabled
    IPv4 MC Forwarding:  Disabled
    IPv6 Forwarding:     Disabled
    IPv6 MC Forwarding:  Disabled
    IPv6:                None
    STPD:                s0(Enabled,Auto-bind)
    Protocol:            Match all unfiltered protocols
    Loopback:            Disabled
    NetLogin:            Disabled
    OpenFlow:            Disabled
    QosProfile:          None configured
    Egress Rate Limit Designated Port: None configured
    Flood Rate Limit QosProfile:       None configured
    Ports:   34.          (Number of active ports=0)
       Untag:      1b,     2b,     3b,     4b,     5b,     6b,     7b,
                   8b,     9b,    10b,    11b,    12b,    13b,    14b,
                  15b,    16b,    17b,    18b,    19b,    20b,    21b,
                  22b,    23b,    24b,    25b,    26b,    27b,    28b,
                  29b,    30b,    31b,    32b,    33b,    34b
        Flags:    (*) Active, (!) Disabled, (g) Load Sharing port
                  (b) Port blocked on the vlan, (m) Mac-Based port
                  (i) Port inactivated on the vlan due to VXLAN configuration
                  (a) Egress traffic allowed for NetLogin
                  (u) Egress traffic unallowed for NetLogin
                  (t) Translate VLAN tag for Private-VLAN
                  (s) Private-VLAN System Port, (L) Loopback port
                  (x) VMAN Tag Translated port
                  (G) Multi-switch LAG Group port
                  (H) Dynamically added by MVRP
                  (I) Dynamically added by IDM
                  (U) Dynamically added uplink port
                  (V) Dynamically added by VM Tracking



 
Environment

EXOS 22.2


 
Answer

STP is blocking those ports.
Starting in EXOS 22.2, STP is enabled by default.

Additional notes

There are other protocols such as EAPS that could cause ports to be blocked, and that is expected behavior.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255