From: Aaron T. Woland (aaron.woland@ins.com)
Date: Thu Mar 23 2006 - 14:09:47 GMT-3
Foundry does not support MST/MIST (same thing, different acronym) until
their next release of code.
Both Cisco and Foundry understand rapid spanning tree (802.1w) and will use
pvst for 802.1w...
I have a mixture of Foundry & Cisco gear @ quite a few customer locations.
-Aaron
Aaron T. Woland | Consultant | INS | Email: aaron.woland@ins.com |
Website: www.ins.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Godswill Oletu
Sent: Thursday, March 23, 2006 8:07 AM
To: Godswill Oletu; Venkatesh Palani; Henk de Tombe
Cc: CCIE LAB
Subject: Re: SPT between CISCO and FOUNDRY
Ven,
These might help, also some typos on the first list, Venkatesh started the
typo by using SPT instead of STP, however I believe that no one was
confused.
PVST uses ISL and Foundary will use dot1q.
PVST+ uses dot1q but it is Cisco proprietary
MIST might be the way out.
Put a spot light on this and your research will point you the way to go.
I got these from another forum:
****
Here is the list of STP family protocols supported by cisco switches:
Spanning Tree Protocol (STP) / 802.1D
Common Spanning Tree (CST or CSTP) * Actually STP and CST is the same.
Rapid STP (RSTP) / 802.1w
Multiple Instance STP (MISTP or MSTP) / 802.1s
Per VLAN Spanning Tree (PVST) * Cisco Proprietary
Per VLAN Spanning Tree Plus (PVST+) * Cisco Proprietary
Here is a list of STP family protocols supported by HP 9304M (actually
Foundry)
Common Spanning Tree (CST or CSTP)
Rapid STP (RSTP) / 802.1w
Multiple Instance STP (MISTP or MSTP) / 802.1s * In the roadmap, next
release
Per VLAN Spanning Tree (PVST) * Cisco Proprietary, via patent
Per VLAN Group STP PVGST * Foundry Proprietary (based on IEEE 802.1s)
SuperSpan * Foundry Proprietary
Metro Ring Protocol MRP * Foundry Proprietary
*****
Visit that thread @
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1000349
HTH
----- Original Message -----
From: "Godswill Oletu" <oletu@inbox.lv>
To: "Venkatesh Palani" <kvpalani@gmail.com>; "Henk de Tombe"
<henk.de.tombe@qi.nl>
Cc: "CCIE LAB" <ccielab@groupstudy.com>
Sent: Thursday, March 23, 2006 7:39 AM
Subject: Re: SPT between CISCO and FOUNDRY
> I thought PVST is the CISCO way of doing thing (SPT), since you want to
> connect to a third party switch, why not look into the industrial standard
> method of implementing SPT ie MST or MIST (depending on which text you are
> reading).
>
> All VLANs can just be a member of one instance.
>
> ----- Original Message -----
> From: "Venkatesh Palani" <kvpalani@gmail.com>
> To: "Henk de Tombe" <henk.de.tombe@qi.nl>
> Cc: "CCIE LAB" <ccielab@groupstudy.com>
> Sent: Thursday, March 23, 2006 6:33 AM
> Subject: Re: SPT between CISCO and FOUNDRY
>
>
> > Hi Henk,
> >
> > Thanks a lot for your reply, it surely helps me a lot, I am planning to
do
> > PVST as I want to split traffic between two MAN connections.
> > Thank you,
> > venkatesh
> >
> >
> > On 3/23/06, Henk de Tombe <henk.de.tombe@qi.nl> wrote:
> > >
> > > Hi Venkatesh,
> > >
> > > Do you mean 802.1D With STP? It will work just fine, the only thing
you
> > > have
> > > to take care of is the native VLAN behaviour of both devices.
> > >
> > > Foundry tags all VLANS, cisco switch can be configured to tag (vlan
> dot1q
> > > tag native) native vlan or not. So the native VLAN on the cisco
doesn't
> > > make
> > > it throughout the foundry network. You can either tag the native vlan
on
> > > the
> > > cisco, OR.....
> > >
> > > You can enable dual-mode port config on the foundry's interface to the
> > > cisco, see example below
> > >
> > > Vlan 10
> > > Tag eth 1
> > > !
> > > Vlan 11
> > > Tag eth 1
> > > !
> > > Int e 1
> > > Dual-mode 10
> > >
> > >
> > > With this configuration you tell the foundry to accept tagged and
> untagged
> > > ports on ethernet 1.
> > >
> > >
> > > One option regarding STP you have to look out for is the command
> > > "pvst-mode"
> > > under the interface:
> > >
> > >
> > >
> >
>
http://www.foundrynet.com/services/documentation/srcli/Interface_cmds.html#w
> > > p126004
> > >
> > > Per default the foundry reverts to cisco PVST BPDU when it receives
one.
> > > If
> > > you already know that PVST will be "offered" to the foundry just
> hard-code
> > > it in, you never know!
> > >
> > > Regards,
> > > Henk
> > >
> > >
> > > Met vriendelijke groet,
> > >
> > > Q&I
> > >
> > > Henk de Tombe
> > > Network Engineer
> > > Q&I NEDERLAND BV
> > > Delftech Park 35 - 37
> > > P.O. Box 402 - 2600 AK DELFT
> > > Phone [+31] 15-8880444 - Fax [+31] 15-8880445
> > > info@qi.nl - www.qi.nl
> > >
> > > Bezoek Q&I op de Intertraffic in de RAI te Amsterdam op 4 tm 7 april
> 2006
> > > -----Oorspronkelijk bericht-----
> > > Van: nobody@groupstudy.com [mailto:nobody@groupstudy.com] Namens
> Venkatesh
> > > Palani
> > > Verzonden: donderdag 23 maart 2006 10:45
> > > Aan: CCIE LAB
> > > Onderwerp: OT: SPT between CISCO and FOUNDRY
> > >
> > > Hi Guys,
> > >
> > > I wonder if you guys have come across any starnge behavior/issues when
> > > running SPT between Cisco and Foundry devices. I am about to deploy
few
> > > cisco 6500 switches into a pure foundry network that runs STP and so
> > > trying
> > > to get prepared for any unexpected surprises :-).
> > >
> > > Thank you,
> > > Venkatesh
> > >
> > >
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:40 GMT-3