Network automation \u2014 as crucial as it is to network resilience<\/a> \u2014 is a daunting task, and it\u2019s no wonder why IT professionals are reluctant to adopt it. One typo, one wrong command, or one coding error is all it takes to lose control of your network. In the movie, it was poor instructions in the HAL machine (e.g. your network) that gave way to a catastrophic sequence of events. Despite the computer\u2019s explicit intentions to be a helpful asset, its actions proved counterintuitive and led to the demise of Discovery One\u2019s entire crew (e.g. your job).<\/p>\n So what does any of this have to do with network automation?<\/p>\n With a little help from the movie, this post will cover:<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” header_3_text_color=”#214C64″ header_4_text_color=”#358AAF” global_colors_info=”{}”]<\/p>\n <\/p>\n It\u2019s no secret that human error is the biggest threat<\/a> to network resilience. In fact, the Uptime Institute reports that as many as 75% of data center outages are caused by human error.<\/p>\n Errors can come from any number of causes. These include anything from minor typos, to significant configuration shifts. With a sprawling number of network sites and devices, it can become incredibly difficult even for experienced IT teams to manually maintain their infrastructure.<\/p>\n This is exactly why companies adopt automation. Rather than manage individually unique devices or environments, automation allows teams to focus on processes and achieve their desired goals.<\/p>\n For technical teams, automation reduces the risk of errors, shrinks their workload, and improves scaling, all of which play a part in increasing resilience. This plays into the business case for automation, which revolves around decreasing outages and revenue losses.<\/p>\n The bottom line: Automation comes with plenty of benefits<\/a>. So why aren\u2019t more IT teams jumping to automate their networks?<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” header_3_text_color=”#214C64″ header_4_text_color=”#358AAF” global_colors_info=”{}”]<\/p>\n <\/p>\n The movie predicted that by the year 2001, we\u2019d all be reaping the benefits of space travel and advanced technology. One of these technologies was the HAL 9000 supercomputer, described in the movie as being \u201cfool-proof\u201d and \u201cincapable of error\u201d. But as anyone knows, a computer designed and instructed by humans is never incapable of error \u2014 and that\u2019s exactly why network automation scares IT teams.<\/p>\n In the movie, the five-man space crew aboard the ship Discovery One is on a mission to Jupiter. The ship is mostly controlled by HAL, the 9000-series supercomputer. HAL observes the crew using glowing red lenses built into the walls and consoles in the ship. HAL takes direct commands from the crew when a door needs to be opened, a communication broadcasted, an EVA (extravehicular activity) pod launched, etc.<\/p>\n The crew has a brief discussion with HAL regarding a similar computer\u2019s malfunction, which HAL then concludes is the result of human error. After this, HAL experiences his own malfunction, which leads to the gradual breakdown of his helpfulness to the crew. HAL sends Frank Poole to his death, locks Dave Bowman out of the ship, and cuts life support measures to the remaining crew who were in cryosleep.<\/p>\n Automation presents such a dichotomy between asset and liability. On one hand, it\u2019s capable of advancing us into our wildest dreams where we can accomplish incredible feats with little effort. On the other hand, a simple human error is all it takes to turn the same automated machine against us, making it capable of tearing down everything we\u2019ve worked for and uprooting life as we know it.<\/p>\n For network engineers, automating IT can mean less downtime, more revenues, and job promotions. But it can also mean catastrophic outages, millions in losses, and a lengthy job search.<\/p>\n Simply put, network automation can be unforgiving, much like losing control of your ship in deep space.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” header_3_text_color=”#214C64″ header_4_text_color=”#358AAF” global_colors_info=”{}”]<\/p>\n <\/p>\n In the movie, Bowman has no option for stopping HAL other than manually pulling the plug. It\u2019s a tedious and dangerous process, but it\u2019s the only way Bowman can contain the damage caused by his artificial counterpart.<\/p>\n This is the same scenario that plays out in IT, albeit with much less drama, when something goes wrong in the automation chain. So how do you overcome this scenario? Can you even overcome it? The big tech companies can, but that\u2019s only because they have the money and resources for it, right?<\/p>\n The reality is, many companies attempt to automate but inevitably fail because they don\u2019t have the proper infrastructure in place. This is the differentiator \u2014 tech giants have focused their attention on implementing the right infrastructure over the past decade, and it\u2019s why they\u2019re able to successfully automate for more resilience.<\/p>\n The secret: their infrastructure has a safety net built into it. Their environments are forgiving. So when things don\u2019t go as planned, whether due to mistakes or rogue machines, they have a lifeline that brings them back to safety.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.19.5″ _module_preset=”default” header_3_text_color=”#214C64″ header_4_text_color=”#358AAF” global_colors_info=”{}”]<\/p>\n <\/p>\n The Network Automation Blueprint is key to overcoming automation anxiety. This architecture incorporates out-of-band management<\/a> as well as dedicated orchestration and automation infrastructure. These allow you to test workflows and configurations for integrity before pushing them live. They also help you build an isolated recovery environment, which you can use to undo mistakes, such as if you unknowingly upgrade to a vulnerable configuration.<\/p>\n This architecture has been developed in direct collaboration with tech giants, and was recently validated by ONUG’s Hyperautomation Working Group.<\/p>\n\n
The biggest threat to network resilience<\/h2>\n
Why network automation scares IT teams<\/h2>\n
![\"Dave](\"https:\/\/zpesystems.com\/wp-content\/uploads\/2022\/05\/Space-Odyssey-Bowman-1024x576.jpeg\")
<\/p>\n![\"Frank](\"https:\/\/zpesystems.com\/wp-content\/uploads\/2022\/05\/Space-Odyssey-Frank-Poole.jpeg\")
<\/p>\nHow to overcome network automation anxiety<\/h2>\n
![\"Bowman](\"https:\/\/zpesystems.com\/wp-content\/uploads\/2022\/05\/Space-Odyssey-Pulling-the-plug-1024x576.jpeg\")
<\/p>\nHow the Network Automation Blueprint brings you back to safety<\/h2>\n
![\"Blueprint](\"https:\/\/zpesystems.com\/wp-content\/uploads\/2022\/11\/Blueprint-Automation-A2.webp\")
<\/a><\/p>\n