Validation of bridge domain-L3out association for communication outside a network
Disclosed are systems, methods, and computer-readable media for assuring tenant forwarding in a network environment. Network assurance can be determined in layer 1, layer 2 and layer 3 of the networked environment including, internal-internal (e.g., inter-fabric) forwarding and internal-external (e.g., outside the fabric) forwarding in the networked environment. The network assurance can be performed using logical configurations, software configurations and/or hardware configurations
1. A system for performing a network assurance check of proper deployment of a configuration in a fabric, comprising:
at least one memory configured to store data; and
at least one processor operable to execute instructions associated with the data, which when executed by the at least one processor, causes the processor to:
receive, from a controller, a global logical model in a first format, the global logical model containing instructions on how endpoints connected to a network fabric communicate within the fabric;
identify bridge domain (BD) subnets in the global logical model that are designated as public; and
validate, in response to a positive result of the identification, that the identified BDs are associated with an Layer 3 out (L3out);
wherein a negative outcome of the identification at least partially represents proper configuration a BD-L3out relationship;
wherein a positive result of the validation at least partially represents proper configuration a BD-L3out relationship.
2. The system of claim 1 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to determine whether any of the identified BDs has a different endpoint group (EPG) from its corresponding L3out.
3. The system of claim 2 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to confirm, in response to a positive result of the determination, a presence of a contract between any of the identified BDs having a different endpoint group (EPG) from its corresponding L3out.
4. The system of claim 3 , wherein a positive result of the confirmation at least partially represents proper configuration of the BD-L3out relationship.
5. The system of claim 1 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to generate an error event in response to a positive outcome of the identification.
6. The system of claim 1 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to generate an error event in response to a negative result of the validation.
7. The system of claim 4 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to generate an error event in response to a negative result of the confirmation.
8. A method for performing a network assurance check of proper deployment of a configuration in a fabric, comprising:
receiving from a controller, a global logical model in a first format, the global logical model containing instructions on how endpoints connected to a network fabric communicate within the fabric;
identifying BD subnets in the global logical model that are designated as public; and
validating, in response to a positive result of the identifying, that each of the identified BDs are associated with an Layer 3 out (L3out);
wherein a negative outcome of the identifying represents proper configuration a BD-L3out relationship;
wherein a positive result of the validation at least partially represents proper configuration a BD-L3 out relationship.
9. The method of claim 8 , further comprising determining whether any of the identified BDs has a different endpoint group (EPG) from its corresponding L3out.
10. The method of claim 9 , further comprising confirming, in response to a positive result of the determining, a presence of a contract between any of the identified BDs having a different endpoint group (EPG) from its corresponding L3out.
11. The method of claim 10 , wherein a positive result of the confirming at least partially represents proper configuration of the BD-L3out relationship.
12. The method of claim 9 , further comprising generating an error event in response to a positive outcome of the identification.
13. The method of claim 9 , further comprising generating an error event in response to a negative result of the validation.
14. The method of claim 10 , further comprising generating an error event in response to a negative result of the confirmation.
15. At least one non-transitory computer readable medium storing instructions, which when executed by a processor causes the processor to perform operations comprising:
receive, from a controller, a global logical model in a first format, the global logical model containing instructions on how endpoints connected to a network fabric communicate within the fabric;
identify BD subnets in the global logical model that are designated as public; and
validate, in response to a positive result of the identification, that the identified BDs are associated with an Layer 3 out (L3out);
wherein a negative outcome of the identification at least partially represents proper configuration a BD-L3out relationship;
wherein a positive result of the validation at least partially represents proper configuration a BD-L3out relationship.
16. The at least one non-transitory computer readable medium of claim 15 , further comprising instructions to determine whether any of the identified BDs has a different endpoint group (EPG) from its corresponding L3out.
17. The at least one non-transitory computer readable medium of claim 15 , further comprising instructions to confirm, in response to a positive result of the determining, a presence of a contract between any of the identified BDs having a different endpoint group (EPG) from its corresponding L3out.
18. The at least one non-transitory computer readable medium of claim 17 , wherein a positive result of the confirming at least partially represents proper configuration of the BD-L3out relationship.
19. The at least one non-transitory computer readable medium of claim 15 , further comprising instructions to generate an error event in response to a positive outcome of the identification.
20. The at least one non-transitory computer readable medium of claim 15 , further comprising instructions to generate an error event in response to a negative result of the validation.