L-Plate
asked on
The same VLAN across two or more switches
I have two L2 switches which I look to deploy the same VLAN to.
For example, i'm looking to deploy ports 3 and 4 on SW1 to VLAN 30 but I would also like to assign ports 6 and 8 on SW2 to VLAN 30 too.
Is it just a matter of setting up VLAN 30 on both switches and then configuring a trunk port so they can see each other ?
For example, i'm looking to deploy ports 3 and 4 on SW1 to VLAN 30 but I would also like to assign ports 6 and 8 on SW2 to VLAN 30 too.
Is it just a matter of setting up VLAN 30 on both switches and then configuring a trunk port so they can see each other ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@noci
that is cases for Cisco RSTP and STP implementation (per VLAN), not for HP. There is no per VLAN in HP implementation if MSTP is not implemented.
MSTP is IEEE 802.1s standard (widespread) and it aligns STP per MSTP instance (group of VLANs in one instance). MSTP is actually based on RSTP, not STP.
that is cases for Cisco RSTP and STP implementation (per VLAN), not for HP. There is no per VLAN in HP implementation if MSTP is not implemented.
MSTP is IEEE 802.1s standard (widespread) and it aligns STP per MSTP instance (group of VLANs in one instance). MSTP is actually based on RSTP, not STP.
I always used RSTP/STP on (also) HP Switches as there were other equipment in that network that only support STP.
and that network had about 13 VLAN's accross various switches. (Not all 13 on all switches).
So my experience differs... (Note I used ProCurve...)
and that network had about 13 VLAN's accross various switches. (Not all 13 on all switches).
So my experience differs... (Note I used ProCurve...)
MSTP is actually based on RSTP, not STP.
Not sure how about that since MSTP predates RSTP. (S comes before W)
No. 802.1s was part of 802.1q. The first draft of 802.1s was in 1998.
But whatever.
But whatever.
AFAIK RSTP was created to get a faster but compatible STP. MSTP was a bridge too far for many large existing networks, as it provided no compatibility. (and putting a "non-STP switch inbetween networks doesn't help, as BDPU's are transmitted transparantly through such switches.
which i found the hard way 30 years ago).
which i found the hard way 30 years ago).
Looks like letters are not assigning letters in order of appearance.
:)
ieee802.org What's new - draft 0 for 802.1v is published after, for example, 802.1t draft 3 published.
I can't find dates of the first drafts for both 802.1s and 802.1w, but looks like both appeared at the similar time (1998 or 1999).
21 Feb 2000:
802.1s draft 4 published.
8 Jan 2000:
802.1w draft 3 published
I found that newer versions of HP devices do support per-vlan spanning-tree operations (not sure if only high end or all devices), but option is available at least on some devices (so, my information is outdated). At least some HP devices support per VLAN configuration which makes DOn's solution applicable to some HP devices.
MSTP is compatible with both RSTP and STP.
MSTP - RSTP compatibility
But, all of this is not really relevant to original question which was already answered properly by Andy Bartkiewicz. There could be others potential solutions too, depending on devices and switch OS's which are in use.
:)
ieee802.org What's new - draft 0 for 802.1v is published after, for example, 802.1t draft 3 published.
I can't find dates of the first drafts for both 802.1s and 802.1w, but looks like both appeared at the similar time (1998 or 1999).
21 Feb 2000:
802.1s draft 4 published.
8 Jan 2000:
802.1w draft 3 published
I found that newer versions of HP devices do support per-vlan spanning-tree operations (not sure if only high end or all devices), but option is available at least on some devices (so, my information is outdated). At least some HP devices support per VLAN configuration which makes DOn's solution applicable to some HP devices.
MSTP is compatible with both RSTP and STP.
MSTP - RSTP compatibility
MSTP is designed to be STP and RSTP compatible and interoperable without additional operational management practice, this is due to a set of measurements based on RSTP (Clause 17 of IEEE Std 802.1D, 2004 Edition) intending to provide the capability for frames assigned to different VLANs, to be transmitted along different paths within MST Regions.
But, all of this is not really relevant to original question which was already answered properly by Andy Bartkiewicz. There could be others potential solutions too, depending on devices and switch OS's which are in use.
But, all of this is not really relevant to original question which was already answered properly by Andy Bartkiewicz.
And yet you made this post.
ASKER
thanks guys
MSTP consolidates ALL STP in one table...
RSTP/STP has a spanning tree Per VLAN..., they don't need to align but most probably will.
There is No problem if you have a loop in the network which (assume on this switch port 1 & 2 are involved)...
Then there is NO problem if VLAN x uses port 1 and VLAN y uses port 2. The only is a problem if one of the VLAN's uses both ports....
(Which ANY STP will prevent...)
Now: MSTP is a Cisco special which is also support by HP, but is not widespread.
STP is the officeial standard STP, (and like MSTP) might be helpd up up to ~45 second before stabelizing. (Polling is used).
RSTP is a rapdid version that propagates changes when they occur, not by polling. RSTP & STP are compatible.
When you have 10 VLAN's THEN you have 10 STP/RSTP trees and 1 (slightly more complex) MSTP tree...