Between the team and the engineers at Cisco (how did you guess?) we've learnt the supervisor engine in the 4006 chassis is experiencing problems; it takes 6 hours to find this out when the first piece of evidence is a separate stack of switches suddenly disconnecting from the network, then reconnecting, then intermittently... Then the Internet starts going really slowly, then stops - packet loss through the firewall reaches 80%... As the admin staff and teachers could still access the internal network services they needed we left the "let's try restarting the core switch" for 2 hours after we deduced it was having problems; as a last step we reloaded the layer module, which promptly came back up with the righthand third inoperable, along with every other module in the chassis... Ooops. We spent the next hour finding ways of repatching the 8 servers into other switches, then this morning moved some fibres to bring the entire network up to full hobble! The replacement engine is on its way, although to quote "due to a part shortage, there may be a delay". Somehow these three paragraphs doesn't really bring to life the anxiety levels experienced during the process! Cheers Chris PS Where should I type the rm -Rf *? -----Original Message----- From: Christopher Dawkins To: 'suse-linux-uk-schools@suse.com' Sent: 9/26/03 1:20 PM Subject: Re: [suse-linux-uk-schools] This list

--- Chris Puttick <chris@centralmanclc.com> wrote:

...

As a result of a core network failure on a scale I hope none of you ever have to face,

We'd all be very interested to know the details. Power cuts? Floods? Loose SCSI cable? rm -Rf *? Or just Cisco? -- Christopher Dawkins, Felsted School, Dunmow, Essex CM6 3JG 01371-822698, mobile 07816 821659 cchd@felsted.essex.sch.uk -- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com