[f-nsp] FESX spanning-tree path cost success?

[Jonathan Brashear]

Our DC has had intermittent issues over the past year with spanning-tree loops with customers who have multiple uplinks to our switch fabric.  We've explored a few different options with limited to no success(such as bpdu guard, stp-protect, etc.), but currently we're considering setting manual path costs on ports as a way to help avoid the loops & subsequent cpu spikes we've dealt with.  Has anyone deployed manual path costs for customers with multiple uplinks(either to the same switch or multiple switches), and if so what success/problems have you had with its implementation?  I'd prefer the info be from the FastIron environment, but any Foundry-related discussion would be appreciated.

Network Engineer
> 214-981-1954 (office)
> 214-642-4075 (cell)
> jbrashear at hq.speakeasy.net
http://www.speakeasy.net