Forward Byline Verification with airSlate SignNow

Forward byline verification

in this demonstration we are going to show the importance of integrating network verification with any network automation platform or project specifically we're going to show a demo of forward Enterprise with Cisco network services Orchestrator to show how these two technologies can work together to accelerate and de-risk network updates verification is a new technology for analyzing Network configurations and designs to mathematically prove network behavior it's based on an understanding of the network details not looking at traffic or log events by verifying Network designs you can detect errors and potential policy violations before they happen not reacting to issues after the fact network automation has greatly increased Network flexibility and eases IT workloads but if there's ever an error in orchestration or service description you can rapidly propagate errors across the network at warp speed verification can intervene and check each configuration to ensure that resulting network behavior will still be compliant with intended policies and application requirements a network verification process would simply follow each time the orchestration engine pushes changes to the network because verification itself is automated usually only taking a couple of minutes there's no tedious testing or manual network checks required so agility is not compromised as you deploy error-free updates there are a number of automation solutions such as ansible and napalm in this demo we're going to show how forward Enterprise works with Cisco NSO or originally tail eff in any forward enterprise integration a new network service description can be pushed to the orchestration engine and pushed out to reconfigure portions of the network simultaneously a set of policy checks will be updated to forward enterprise essentially requesting a verification that the resulting changes are correct and even that all other policy requirements for the network in general are still valid in this demo we're deploying a simple spine leaf Network with initially two pods a pair of redundant f5 application delivery controllers and two cisco aasa firewalls behind the internet gateway we will use cisco NSO to automate setting up proper routes into the topology from the internet open some ports in the firewall and configure network address translation on the f5 boxes to ensure traffic flows equally to both pods although the orchestration appears to complete correctly forward Enterprise will identify some issues and how to isolate and repair them then we will manually add a third pod but with a change the black holes all routes and takes everything offline again forward Enterprise will immediately flag this issue isolate the root cause and how to repair the problem and with that I'm going to turn it over to our se Scott O'Donnell to take you through the demo in our demo environment we have a stripped down data center composed of a simple infrastructure allowing internal hosts to provide web applications to our internet-based customers we currently have two pods online pot one and pot two pod 3 has not been turned up yet and the...