PVST Alcatel Cisco
PVST Alcatel Cisco
PVST Alcatel Cisco
Cisco uses the standard IEEE BPDU format for the native VLAN (VLAN 1) over an 802.1Q trunk. Thus,
by default the Common Spanning Tree (CST) instance of the native VLAN 1 for all Cisco switches and
the STP instance for the default VLAN of a port on an OmniSwitch interoperates and successfully creates
a loop-free topology.
For 802.1Q tagged VLANs, Cisco uses a proprietary frame format which differs from the standard IEEE
BPDU format used by Alcatel-Lucent per-VLAN mode, thus preventing Spanning Tree topologies for
tagged VLANs from interoperating over the 802.1Q trunk.
In order to interoperate with Cisco PVST+ mode, the current Alcatel-Lucent per-VLAN mode has an
option to recognize Cisco's proprietary PVST+ BPDUs. This allows any user port on an OmniSwitch to
send and receive PVST+ BPDUs, so that loop-free topologies for the tagged VLANs can be created
between OmniSwitch and Cisco switches.
The spantree pvst+compatibility command is used to enable or disable the PVST+ interoperability mode
globally for all switch ports and link aggregates or on a per-port/link aggregate basis. By default, PVST+
compatibility is disabled.
To globally enable or disable PVST+ interoperability, enter the following commands:
-> spantree pvst+compatibility enable
-> spantree pvst+compatibility disable
To enable or disable PVST+ interoperability for a specific port or link aggregate, use the spantree
pvst+compatibility command with the port or linkagg parameter. For example:
-> spantree pvst+compatibility port 1/3 enable
-> spantree pvst+compatibility port 2/24 disable
-> spantree pvst+compatibility linkagg 3 enable
-> spantree pvst+compatibility linkagg 10 disable
OmniSwitch AOS Release 8 Network Configuration Guide September 2016 page 6-23
Configuring Spanning Tree Parameters Spanning Tree Operating Modes
It is mandatory that all the Cisco switches have the MAC Reduction Mode feature enabled in order to
interoperate with an OmniSwitch in PVST+ mode. This avoids any unexpected election of a root
bridge.
You can assign the priority value only in the multiples of 4096 to be compatible with the Cisco MAC
Reduction mode; any other values result in an error message. Also, the existing per vlan priority values
are restored when changing from PVST+ mode back to per-VLAN mode. For more information on
priority, refer Configuring the Bridge Priority on page 6-28.
In a mixed OmniSwitch and Cisco environment, it is highly recommended to enable PVST+ mode on
all OmniSwitches in order to maintain the same root bridge for the topology. It is possible that the new
root bridge might be elected as a result of inconsistencies of MAC reduction mode when connecting an
OmniSwitch that does not support Cisco PVST+ mode to an OmniSwitch with the PVST+ mode
enabled. In this case, the root bridge priority must be changed manually to maintain the same root
bridge. For more information on priority, refer Configuring the Bridge Priority on page 6-28.
A Cisco switch running in PVST mode (another Cisco proprietary mode prior to 802.1q standard) is
not compatible with an OmniSwitch running in per-VLAN PVST+ mode.
Both Cisco and OmniSwitch support two default path cost modes; long or short. It is recommended
that the same default path cost mode be configured in the same way on all switches so that the path
costs for similar interface types are consistent when connecting ports between OmniSwitch and Cisco
Switches. For more information on path cost mode, refer Configuring the Path Cost Mode on
page 6-31.
OmniSwitch AOS Release 8 Network Configuration Guide September 2016 page 6-24
Configuring Spanning Tree Parameters Spanning Tree Operating Modes
Dynamic aggregate link (LACP) functions properly between OmniSwitch and Cisco switches. The
Cisco switches send the BPDUs only on one physical link of the aggregate, similar to the OmniSwitch
Primary port functionality. The path cost assigned to the aggregate link is not the same between
OmniSwitch and Cisco switches since vendor-specific formulas are used to derive the path cost.
Manual configuration is recommended to match the Cisco path cost assignment for an aggregate link.
For more information on the configuration of path cost for aggregate links, refer Path Cost for Link
Aggregate Ports on page 6-38.
The table below shows the default Spanning Tree values.
OmniSwitch AOS Release 8 Network Configuration Guide September 2016 page 6-25