How about this one: We used to provide troubleshooting support for a forces network which included some large sites and a few very minor (one or two user) sites. There had been problems with one of these small sites intermittently for a few weeks, but things got worse until it was dropping three or 4 times per day.
The router seemed to be rebooting every time there was a problem. We found no relevant bugs, and though the site wasn't on UPS, site services didn't believe there was any problem with power and assured us that the power to the cabinet was an unswitched fused spur. We initially upgraded the image and then swapped the router out, leaving the old router in the cabinet powered up as well, but not connected. The new router rebooted as well, and when we went back to site with the intention of putting a small UPS in the cabinet, the old router had rebooted at exactly the same time, which seemed to support our idea. The previous 2 times on site I had just carried out the work and left. This time I accepted the offer of a coffee while I fitted the UPS in. All of a sudden the power went off to the whole cabinet. What a relief. What a laugh. Next to the kettle in the room next door was a double socket, one of them labelled "Do not unplug", the other connected to a radio. The cable ran through trunking, and through the wall, then trunking all the way around the room to the comms cabinet. Experience had taught the caretaker that nothing seemed to go wrong when the plug was taken out, but he always plugged it back in just in case. It was either that or his radio. Doh! Gaz While ""Chuck"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > my favorite story was the company whose network went down every morning for > a few minutes just about the time the work force was sitting down, turning > on their PC's, and getting ready for the day. Now the obvious conclusion is > "it's just busy that time of day" Except that it didn't necessarily happen > every day. > > To make a long story short, a couple of power users had decided they needed > more data jacks in their area, had purchased some switch or other at one of > the chain stores, and dual homed it into the LAN infrastructure. Being > conservation conscious folks, they powered down all their equipment when > they went home for the day, and turned it on every morning when they came > in. > > the result was a campus wide spanning tree recalculation every time they > brought their switch on line. > > I forget how the customer told me this was discovered. > > > ""Priscilla Oppenheimer"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > And add to that cranky users who are entirely dependent on the network but > > won't tell you the whole story when reporting problems. ;-) > > > > Priscilla > > > > At 09:52 PM 5/12/02, Michael L. Williams wrote: > > >"Larry Letterman" wrote in message > > >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > A 40 router lab is nice, but its not the same as troubleshooting a > > > > production network with 20,000 + users at multiple sites. > > > > > >Here here.... and to add to that..... "... a production network with > > >20,000+ users at multiple sites..." running a variety of multiprotocol, > > >quirky, sometimes custom-written (read: homemade) applications that are > > >trying to do whatever on the network.... coupled with devices from > whatever > > >manufacturers that don't play nice ("oh, you need this device in it's own > > >VLAN because broadcast traffic makes it crash"), etc, etc.... > > > > > >Mike W. > > ________________________ > > > > Priscilla Oppenheimer > > http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=44270&t=43969 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
