BOFHs to blame for LAN downtime after all
Guns don't kill people - routers do
Note: this email contains traces of irony, which may cause small children to choke.
I have just read your article regarding the Top 10 reasons for LAN downtime. I personally think it could be modified to look like so below...
2nd line Support, resolving the below because of....
1 Crap Network Team:-) Misconfigured routers: devices installed incorrectly in the first instance
2 Crap Network Team:-) Faulty Ethernet cards: poor quality cards that fail soon after installation, but take some time to detect
3 Crap Network Team:-) Broadcast storms: caused by legacy applications on legacy servers, which should have been taken out of commission
4 Crap Network Team:-) Unwanted protocols: many networks suffer from having had Windows terminals, printers and other peripherals installed along with extra protocols, but these are left on the network when they are no longer in regular use
5 Crap Network Team:-) Poor switch allocation: LAN bottlenecks caused by too many devices being allocated to run through one overloaded switch
6 Crap Network Team:-) Server overloading: poor ongoing maintenance of file servers causing slow spots on the network
7 Crap Network Team:-) Faulty devices: fundamental faults with devices attached to the network, which can be difficult to detect initially
8 Crap Network Team:-) SNMP management tools: the design of Simple Network Management Protocol (SNMP) is such that it can impact the performance of the devices being managed and adds to the traffic burden on the network.
9 Crap Network Team:-) Rogue equipment: unauthorised connection of illegitimate or inappropriate devices to the network
10 Crap Network Team:-) Power outage: the total failure of power supplies to networked devices
This week's mailbag
Sponsored: Benefits from the lessons learned in HPC