Copy tftp start?????

[kb2001]

We have a problem. We have multiple devices deployed across 500 miles that are running spanning tree protocol. We need to get this disabled. The obvious problem when you disable it on one, the others go into infinite loops and we can't access them remotely anymore. I don't really want to spend an entire weekend driving around to console into all these devices.

Is it possible to copy a config to the startup-config file? This would make my life easier, as I could just schedule reloads and load the new configs into the startup config file. Like magic, everything comes up, hopefully. Is this possible to do? If not, does anybody have any other ideas?

I know its unorthodox, but if can save me two days of driving, and 48 hours of production downtime, I'll do it.

 

[vipergg]

Can't imagine why you would want to do this . Can you elaborate on the problem ? Why would spanning tree have anything to do with a problem with devices that are that far apart normally you would route between sites like this and spanning tree becomes irrelevant between sites . Are you bridging between the sites ? the answer to your other question is yes is needed (though highly ill advised) you could shut off spanning tree by modifying the config files and copying them to start up . I don't know what the problem is but just by disabling it on one should not put the network in some kind of loop , that is what spanning tree is designed for to keep layer 2 loops out of the network . Maybe if you elaborate we could help more .

 

[kb2001]

vipergg-

Thanks for replying. I'll try to provide some more insight into this.

The sites are either fibered, or tunnel through the backbone. But, they are "directly" connected (as far as config goes). Each site just has a L3 switch and a handful of machines. I don't why spanning tree was used in the first place, but it is causing problems for us now. When we tried to take an older unused concentrator out a few months ago, the network went crazy and brought everything down. All or none is what it has come down to. I'm just looking for a way to disable it on all the devices remotely at the same time. When we pull one off, we lose connectivity with the others. If you have any other suggestions I would be happy to hear them.

The idea behind copying to the startup config is that we can schedule reboots for 60 minutes or so, change the startup on the devices, then when they reboot the new config comes up. We can't change the run config and copy run start b/c as soon as we change the run config to disable spanning tree, we lose connectivity with others. It was a jerry-rig setup when it was done, and now we're running into the problems that resulted. I would love to hear some better suggestions, I know my idea is ill-advised. That's how desperate we're becoming.

 

[globalchicken]

How many vlans do you have, and is the same switch root for all vlans? If this is the case, all ports will be forwarding on your root switch. Can you possibly start from your root switch and work your way from the outside back towards the root disabling STP at every hop? Does each switch have multiple links out over your backbone? And if not, then STP would not be your issue. If you have only one link out from each switch then how are loops induced? I agree with viper, it is ill-advised to disable STP.

You mentioned L3 switches at each site, why are you not using that functionality? Take the current topology to the drawing board, and design a functioning L3 configuration, then roll it out to production. If you post a drawing, we could probably give you much more assistance!