This is the blog of Ronald Bartels that wanders on and off the subject of problem management (that is how it started). Mostly now the topics are about IoT and SD-WAN.
Search This Blog
How to dramatically reduce the time to troubleshoot
When I worked for Madge Networks (read about the company here)
I encountered a difficult problem. A bank had bought a large number of
RAMs (token-ring networking hubs). These hubs were randomly rebooting. I
started diagnosing the problem using a rudimentary checklist I had an
failed to find a resolution. Eventually, two engineers from the UK
arrived to assist on the problem. They had a head start on me as the
problem had already been reported at a few other sites world wide. It
eventually turned out to be oxidization on the power connectors to the
power switching supply. The wrong tool and materials had been used to
crimp and attach the connectors which had resulted in the oxidization
and hence the intermittent resetting of the network equipment. However,
the engineers provided a valuable hint in how to dramatically reduce the
time to troubleshoot. They said a problem with networking equipment is
either hardware or software and when it doubt it is most probably
hardware.
Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall
When building a DDoS mitigation service it’s incredibly tempting to think that the solution is scrubbing centers or scrubbing servers. I, too, thought that was a good idea in the beginning, but experience has shown that there are serious pitfalls to this approach. Read the post of at Cloudflare's blog: N o Scrubs: The Architecture That Made Unmetered Mitigation Possible
Comments
Post a Comment