[c-nsp] spanning tree on me3600x

[Reuben Farrelly]

Hi Aaron

See:

http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swevc.html#wp1002521

•When STP mode is PVST+ or PVRST, EFP information is not passed to the 
protocol. EVC only supports only MSTP.

We're running Rapid-PVST but it only operates on normal trunk and access 
ports, and not via EVCs.

I had a TAC case going where there was suspicions that STP was the cause 
of a problem we were seeing, advice from the BU engineer at the time was 
that Rapid-PVST would and could never be supported across EFP.  It's MST 
or nothing.

Reuben

On 27/12/2012 2:02 AM, Aaron wrote:
> I don't see any instances of spanning tree running for various efp's I've
> created in my ME3600.
>
>
>
> Is there something different with spanning tree and the Me3600x that is much
> different than older cisco switches ?
>
>
>
> voice-3600#sh spanning-tree interface g0/4 efp 336
>
> no spanning tree info available for GigabitEthernet0/4
>
>
>
> voice-3600#sh run | in span
>
> spanning-tree mode rapid-pvst
>
> spanning-tree extend system-id
>
> spanning-tree vlan 336 priority 24576
>
>
>
> voice-3600#sh spann vl 336
>
> Spanning tree instance(s) for vlan 336 does not exist.
>
>
>
> voice-3600#sh run in g0/4
>
>
>
> interface GigabitEthernet0/4
>
> description ring 3 - 3y6 vlans
>
> switchport trunk allowed vlan none
>
> switchport mode trunk
>
> load-interval 30
>
> service instance 316 ethernet
>
>    encapsulation dot1q 316
>
>    rewrite ingress tag pop 1 symmetric
>
>    bridge-domain 316
>
> !
>
> service instance 336 ethernet
>
>    encapsulation dot1q 336
>
>    rewrite ingress tag pop 1 symmetric
>
>    l2protocol peer stp
>
>    bridge-domain 336
>
> !
>
> End