I got clarification on his suggestion, and I will proceed with that. I am aware of the risks, the question was how do I mitigate those risks.. your comment on leaving it alone doesn't help. if you don't have anything good to say; then don't. Im sure the forum doesn't need your attitude, I know I don't.
James Urwiller Lead Internet Services Technician / Network Engineer CCNA 11567125 American Broadband 402-426-6257 - Office 402-278-1875 - Cell 402-426-6273 - Fax [email protected] -----Original Message----- From: Pete Templin [mailto:[email protected]] Sent: Thursday, August 02, 2012 10:40 AM To: James Urwiller Cc: [email protected] Subject: Re: [c-nsp] remove spanning-tree without being service effecting On 8/2/12 8:18 AM, James Urwiller wrote: > That kind of defeats the whole "not service effecting" issue.. thanks > anyway. He clearly said 'just as a backup'. You clearly said "without driving to each site". What do you want? Get over it, there's risk involved in what you want to do (that risk entered as soon as you chose to remove STP, maybe as soon as you thought of it), you might want to implement a safety net. > -----Original Message----- > From: Chuck Church [mailto:[email protected]] > Sent: Thursday, August 02, 2012 9:49 AM > To: James Urwiller; [email protected] > Subject: RE: [c-nsp] remove spanning-tree without being service > effecting > > Figure out all the commands you need to enter for everything, put it > in a text file, and tftp that into the running config. Obviously test > it well before hand, and schedule a reload on the device just as a backup. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
