I'm just curious where other people are putting their contracts, in the specific tenant or in the common tenant? I've been working in our lab environment and I can seem some advantages to putting them all in the common tenant with the proper scope. I understand the value of re-use by putting them there, but it actually feels more cumbersome as i build a contract between EPGs within the same tenant. Today I'm a single tenant and that could change and then there would be re-use for shared services stuff. Which makes me wonder if a hybrid approach would be better...if it's shared services, put them in the common, but if it's a specific contract between EPGs within the same tenant, keep it in that tenant. Especially given there are some contracts (l4-l7 stuff) that has to be in the tenant (I think anyway).
I know there are many right ways to do the same thing. Just looking for some examples of what you're doing and what is working well (or what you regret doing).
I'd also be curious how you build your contracts...are you building specific EPG to EPG contracts with all of the filters you need within the same contract? Or are you building more "generic" contracts and applying multiple contracts to the EPGs?
for example, let's say you have ssh, https, telnet, and icmp required between EPG1 (provide) and EPG2 (consume).
and then the EPGs provide and consume multiple contracts? b/c it's highly likely you'll need to use those well known services between other EPGs too? I suppose there may be a resource thing that makes #1 more efficient, but #2 almost seems like it'd be easier to look at.
Cisco® Nexus® Dashboard revolutionizes operations in today’s modern data-center environments. Join us to learn about the operational efficiencies realized from the seamless user experience of the dashboard and the powerful capabilities of Cisco Nexus Insi...
The HTML5 plug installation is successful. But I get the following error while I click on AVE. The other icons are showing up the results except AVE. Please let me know your SME thoughts on this error.
No VmmDomains Found
This session will help administrators and architects leverage SAN Insights Discovery to help understand the current status of their SAN fabric and help identify areas of opportunity for improvement. The attendees will learn the process, architecture, and ...
Join us to learn about the operational efficiencies realized from the seamless user experience of the dashboard and the powerful capabilities of Cisco Nexus Insights (NI), Cisco Network Assurance Engine (NAE), and Cisco Multi-Site Orchestrator (MSO). The ...
Cisco Intersight's Terraform Provider is now available in the Terraform Registry at https://registry.terraform.io/providers/CiscoDevNet/intersight/latest. The provider has Terraform resource and data source support for the wide range of Inters...