[e-nsp] Problem with MST cisco and extreme switches

Ramón Alvarez Rayo ramon.alvarez at alfanumeric.com.ni
Wed Dec 13 15:29:51 EST 2006 

Right now we are in testing environment, but in production the number of
vlans will grow.

Follow with the subject, when I enable rapid stp on cisco, with vlan native
1 on ports, I see a loop on the network, the cisco switchs put in fwd mode
both ports, and the extreme switches put both ports in fwd.

If I shutdown a port on cisco switch every thing is normal and I can reach
the hosts on vlan 500.

Any idea?


-----Mensaje original-----
De: Roger Wiklund [mailto:copse at xy.org] 
Enviado el: Miércoles, 13 de Diciembre de 2006 01:18 p.m.
Para: Ramón Alvarez Rayo
CC: extreme-nsp at puck.nether.net
Asunto: RE: [e-nsp] Problem with MST cisco and extreme switches

Yes EAPS is propetary, but you can use it with non-eaps if you close the 
ring with the same eaps-switch that started.

Why are you using tagged vlan when you only have one? Try untagged.

On Wed, 13 Dec 2006, Ramón Alvarez Rayo wrote:

> I´m not clear about use eaps with other devices, i think it is propetary.
>
> I see stp for vlan 1 and vlan 500 but I can´t ping from extreme to cisco
> switch.
>
> Any idea?
>
> Thanks,
>
> -----Mensaje original-----
> De: Roger Wiklund [mailto:copse at xy.org]
> Enviado el: Miércoles, 13 de Diciembre de 2006 02:56 a.m.
> Para: Ramón Alvarez Rayo
> CC: extreme-nsp at puck.nether.net
> Asunto: Re: [e-nsp] Problem with MST cisco and extreme switches
>
> Hey
>
> Stupid question maybe, but why dont you use EAPS? You can use it with
> non-eaps-devices.
>
> Sorry, I don´t have an answer to you question, are you sure it´s a STP
> problem? And not some trunk/native vlan problem. I know i´ve had
> some problems with Ciscos bloody native VLAN.
>
> //Roger
>
> On Tue, 12 Dec 2006, Ramón Alvarez Rayo wrote:
>
>>
>> John,
>>
>> Thanks, but i have some questions:
>>
>> a. how long time take to recover from a link fail using this scheme?
>> b. I did the changes and it is not working, it seems that stpd is working
>> but I can´t ping between switches using vlan 500 interface. Any ideay why
> is
>> it?
>>
>> Here is the config:
´>>
>> enable stpd ALFA1 rapid-root-failover
>> configure stpd ALFA1 tag 500
>> configure stpd ALFA1 mode dot1w
>> configure stpd ALFA1 port mode pvst-plus 49 configure stpd ALFA1 port
>> link-type point-to-point 49 configure stpd ALFA1 port mode pvst-plus 50
>> configure stpd ALFA1 port link-type point-to-point 50 enable stpd ALFA1
>>
>> KNITWEAR:9 # show stpd ALFA1
>> Stpd: ALFA1             Stp: ENABLED            Number of Ports: 2
>> Rapid Root Failover: Enabled
>> Operational Mode: 802.1W
>> 802.1Q Tag: 500
>> Ports: 49(KNITWEAR-HMILIT),50(KNITWEAR-ALFANU)
>> Active Vlans:  BACKBONE
>> Bridge Priority: 32768
>> BridgeID:               80:00:00:04:96:22:cf:60
>> Designated root:        80:00:00:04:96:22:cf:60
>> RootPathCost: 0         Root Port: ----
>> MaxAge: 20s             HelloTime: 2s           ForwardDelay: 15s
>> CfgBrMaxAge: 20s        CfgBrHelloTime: 2s      CfgBrForwardDelay: 15s
>> Topology Change Time: 35s                       Hold time: 1s
>> Topology Change Detected: FALSE                 Topology Change: FALSE
>> Number of Topology Changes: 5
>> Time Since Last Topology Change: 1688s
>>
>> KNITWEAR:10 # show stpd ALFA1 ports detail
>> Stpd: ALFA1     Port: 49(KNITWEAR-HMILIT)       PortId: 4031    Stp:
> ENABLED
>> Path Cost: 4
>> Port Mode: PVST+
>> Port State: FORWARDING          Topology Change Ack: FALSE
>> Port Priority: 16               Loopback Port: FALSE
>> Designated Root:   80:00:00:04:96:22:cf:60      Designated Cost: 0
>> Designated Bridge: 80:00:00:04:96:22:cf:60      Designated Port Id: 4031
>>
>>
>> Partner STP version: Dot1w
>> Stpd: ALFA1     Port: 50(KNITWEAR-ALFANU)       PortId: 4032    Stp:
> ENABLED
>> Path Cost: 4
>> Port Mode: PVST+
>> Port State: FORWARDING          Topology Change Ack: FALSE
>> Port Priority: 16               Loopback Port: FALSE
>> Designated Root:   80:00:00:04:96:22:cf:60      Designated Cost: 0
>> Designated Bridge: 80:00:00:04:96:22:cf:60      Designated Port Id: 4032
>>
>>
>> Partner STP version: Dot1w
>>
>> THANKS,
>>
>>
>> -----Mensaje original-----
>> De: john.center at villanova.edu [mailto:john.center at villanova.edu]
>> Enviado el: Martes, 12 de Diciembre de 2006 03:20 p.m.
>> Para: Ramón Alvarez Rayo
>> Asunto: Re: [e-nsp] Problem with MST cisco and extreme switches
>>
>> Hi Ramón,
>>
>> ExtremeWare 7.4 does not support 802.1s.  Version 7.6 supports it.  You
>> could make this work with EW 7.4 if you use PVST+.  Change the cisco
>> config from:
>>
>> 	spanning-tree mode mst
>> to
>> 	spanning-tree mode rapid-pvst
>>
>> On the extreme switch add:
>>
>> 	configure stpd ALFA1 port mode pvst-plus 49
>> 		...
>> to indicate the type of BPDU that will be seen on the port.  We do this
>> & it works well.
>>
>> HTH
>>
>> 	-John
>>
>>
>> Ramón Alvarez Rayo wrote:
>>> Hello,
>>>
>>>
>>>
>>> I am closing a fibre ring with 2 extreme summit 48si/Full L3 and a cisco
>>> 2960, i´m tryng to connect using MSTP but I can´t see any packets
>>> between extreme switches and catalyst switch, this is the configuration:
>>>
>>>
>>>
>>> NODO 2
>>>
>>>
>>>
>>> configure vlan "BACKBONE" tag 500     # VLAN-ID=0x1f4  Global Tag 3
>>>
>>> configure stpd ALFA1 add vlan "BACKBONE"
>>>
>>> configure vlan "BACKBONE" ipaddress 10.240.0.2 255.255.255.224
>>>
>>> configure vlan "BACKBONE" add port 49 tagged
>>>
>>> configure vlan "BACKBONE" add port 50 tagged
>>>
>>>
>>>
>>> enable stpd ALFA1 rapid-root-failover
>>>
>>> configure stpd ALFA1 tag 500
>>>
>>> configure stpd ALFA1 mode dot1w
>>>
>>> configure stpd ALFA1 port link-type point-to-point 49
>>>
>>> configure stpd ALFA1 port link-type point-to-point 50
>>>
>>> enable stpd ALFA1
>>>
>>>
>>>
>>> NODO 3
>>>
>>>
>>>
>>> configure vlan "BACKBONE" tag 500     # VLAN-ID=0x1f4  Global Tag 3
>>>
>>> configure stpd ALFA1 add vlan "BACKBONE"
>>>
>>> configure vlan "BACKBONE" ipaddress 10.240.0.3 255.255.255.224
>>>
>>> configure vlan "BACKBONE" add port 49 tagged
>>>
>>> configure vlan "BACKBONE" add port 50 tagged
>>>
>>>
>>>
>>> enable stpd ALFA1 rapid-root-failover
>>>
>>> configure stpd ALFA1 tag 500
>>>
>>> configure stpd ALFA1 mode dot1w
>>>
>>> configure stpd ALFA1 port link-type point-to-point 49
>>>
>>> configure stpd ALFA1 port link-type point-to-point 50
>>>
>>> enable stpd ALFA1
>>>
>>>
>>>
>>> On cisco switch this is the configuration:
>>>
>>>
>>>
>>> spanning-tree mode mst
>>>
>>> spanning-tree extend system-id
>>>
>>> !
>>>
>>> spanning-tree mst configuration
>>>
>>>  name ALFA1
>>>
>>>  revision 7
>>>
>>>  instance 1 vlan 500
>>>
>>> !
>>>
>>> vlan internal allocation policy ascending
>>>
>>>
>>>
>>> interface GigabitEthernet0/1
>>>
>>>  description !!! NODO1-TO-NODO2 !!!
>>>
>>>  switchport trunk native vlan 500
>>>
>>>  switchport trunk allowed vlan 500
>>>
>>>  switchport mode trunk
>>>
>>>  switchport nonegotiate
>>>
>>>  spanning-tree link-type point-to-point
>>>
>>> !
>>>
>>> interface GigabitEthernet0/2
>>>
>>>  description !!! NODO1-TO-NODO3 !!!
>>>
>>>  switchport trunk native vlan 500
>>>
>>>  switchport trunk allowed vlan 500
>>>
>>>  switchport mode trunk
>>>
>>>  switchport nonegotiate
>>>
>>>  spanning-tree link-type point-to-point
>>>
>>>
>>>
>>> interface Vlan500
>>>
>>>  ip address 10.240.0.1 255.255.255.224
>>>
>>>
>>>
>>> Extreme Version: Image : Extremeware  Version 7.4.4.9
>>>
>>> Cisco Catalyst: Version 12.2(25)SEE2
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> extreme-nsp mailing list
>>> extreme-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/extreme-nsp
>> --
>> John Center
>> Villanova University
>>
>>
>>
>>
>> _______________________________________________
>> extreme-nsp mailing list
>> extreme-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/extreme-nsp
>>
>
>
>

More information about the extreme-nsp mailing list