Forward Signed Validated with airSlate SignNow

Forward signed validated

Hello and welcome to our Getting to Know Batfish series where we showcase key capabilities of Batfish and how they can be used as part of your network automation workflow My name is Matt. In this video I'll show you how to validate network forwarding changes using Batfish Network engineers frequently make changes that impact forwarding behavior adding new routes Opening or closing flows routing traffic through different devices, etc These changes are often hard to get right and hard to validate the risks of deploying a bad change can be huge potentially causing outages or security breaches For these reasons having a powerful change validation process is crucial for modern networks This video will show you how Batfish can help get your changes right with Batfish change validation can be proactive Meaning you can validate your changes offline before you deploy them to the network It's also Network scale batfish analyzes full end-to-end network behavior allowing it to find bugs caused by interactions between devices far away from each other and it's Comprehensive Batfish can validate the forwarding behavior for all possible flows. This allows it to find bugs You may never have thought to test all of this makes batfish the ideal tool for your change validation workflow let's get started As usual we'll begin by initializing the current snapshot of our network in Batfish Batfish will parse the configuration files build the model of the network and automatically compute the ribs and fibs We're going to validate two different changes to our network The network has two host devices connected to leaf 1 a web server and a database server The other end we have border routers that connect to the external network The network is provisioned with failover redundancy for the core routers All traffic is normally routed through core 1 but will automatically switch to core 2 in case of a failure or during maintenance in This scenario. We want to service core 1 so we're going to shift traffic to core 2 We'll implement a change to cost out core 1 and verify that it does not affect reachability to the hosts from the external Network First let's test the current forwarding behavior using the traceroute question. We want to see how external to host traffic is routed So we'll use the destinations parameter to specifi traffic destined to the host devices and the start location Parameter to specify traffic entering through the border routers external interfaces The results include a flow from each border router and all possible paths of each flow as we can see in the traces column Both flows are routed through core one, which is all we're concerned with here For more information about the trace route question see our previous video in this series Introduction to Forwarding Analysis For now having confirmed that traffic is being routed through core 1 as expected. Let's go ahead with our change to cost it out So that traffic is routed through...