Forward Byline Confirmation with airSlate SignNow

Forward countersign confirmation

hi I'm Gary King horn marketing director at forward networks in this webinar I'm going to give an overview of forward Enterprise our full-featured intent-based networking solution this video is part of a series of portfolio webinars that covers various features and use cases of the forward platform - make sure to check out our other videos on our YouTube channel or our website for more information in this video we're going to focus on the verify and predict capabilities which can ensure that your network is configured properly end to end in alignment with your network intent policies and other requirements verifying network content is the first step towards an intent based network a key capability of next-generation networks to automatically support high-level business and technical requirements forward enterprise may be best described as an intent based verification platform our customers are using that to quickly isolate and identify potential configuration errors that could lead to costly outages as well as ensure that policy and compliance requirements are met to see how forward enterprise can help you on your networking IT efforts let's take a look at how we verify intent rules and policy checks to determine Network behavior in this demo we are analyzing a network of two data centers connected by an MPLS backbone in the verify tab I can see that there are some policy violations that need to be addressed inside this tab we see a list of all the policy checks that the system is evaluating including both predefined checks as well as user defined rules we have built for this specific network predefined checks include there being no forwarding loops in the network checks for duplicate IP addresses as well as consistency across links for a number of network parameters the specific check we are interested in is the one that specifies there should be no traffic from ATL Internet which is the name of our external gateway with the destination of one of our web application servers that gets delivered while not using port 443 for HTTPS it's our intent that all such traffic other than secure HTTP should be dropped by clicking on the failure link we immediately go to where this violation is occurring we can see a number of pass through the network that violate our criteria and we begin to explore for a common root cause issue but we quickly are able to focus our attention to a few paths in the larger network and specific devices that are involved in configuring this network policy in this scenario we can see that in all paths traffic is going through a firewall that is providing a CL as well as NAT services we can drill down on that device and see key configuration details as well as drill down into the device state and configuration files here we see that the firewall is allowed to let traffic through on port 443 80 and 22 with a few mouse clicks...