Skip to content
rule 11 reader
  • about
    • about me
    • mailing list
    • author page
    • rss feeds
  • reading
    • technology books
    • skills books
    • fiction books
    • philosophy & culture books
    • christian books
    • papers
    • worth reading
  • categories
    • career
      • career
      • design skills
      • communication skills
      • education
      • soft skills
      • troubleshooting skills
    • coding
    • complexity
    • culture
    • ddos
    • ipv6
    • other technologies
    • research
    • reviews
    • routing
      • bgp
      • bgp security
      • eigrp
      • is-is
      • ospf
      • mpls
      • other routing
    • security
    • standards
    • worth reading
    • content type
      • long video
      • long audio
      • short video
      • written
    • other
      • governance
      • humor
    • archive
  • the hedge
  • history
  • resources
    • my goodreads
    • my feedly
    • network icons
  • photos

On the ‘net: RFC1925 Rule 9a

Everyone is aware that it always takes longer to find a problem in a network than it should. Moving through the troubleshooting process often feels like swimming in molasses—you’re pulling hard, and progress is being made, but never fast enough or far enough to get the application back up and running before that crucial deadline. The “swimming in molasses effect” doesn’t end when the problem is found either—repairing the problem requires juggling a thousand variables, most of which are unknown, combined with the wit and sagacity of a soothsayer to work with vendors, code releases, and unintended consequences.

Related

Posted in ON THE NET
← The Hedge 34: Andrew Alston and the IETFWeekend Reads 050820 →
© 2023 rule 11 reader | Powered by Beaver Builder
Scroll To Top