Please enable JavaScript.

Coggle requires JavaScript to display documents.

M2 -contract - Coggle Diagram

- - - - the Navigation pane choose Tenant_Name > Networking > Private Networks >
      - Private_Network_Name > EPG Collection for Context.
      - In the Work pane, click + next to either Add Provided Contract or Add Consumed Contract.
      - https://www.cisco.com/c/en/us/support/docs/cloud-systems-management/application-policy-infrastructure-controller-apic/211625-How-To-vzAny-Usage.html
  - - - 1.Admin burden is high because each EPG must be configured separately to consume the contract.
      - 2., the number of hardware resources increases each time an EPG associates with a contract
      - refer to without aZany diagram
- - - - means same VRF
- - - - Deny (taboo): This could be for a specific use case, such as during a migration
      - from legacy networks to ACI. In this case, you may specify to allow all traffic in a
      - contract but set up taboos to deny certain traffic.
      - ■ Redirect: This may be useful for sending traffic from an EPG to a Layer 4 thorugh L7 devcice such as FW, LB or IPS/IDS
      - ■ Mark: You might want to mark traffic for quality of service reasons.
- - - - conclusion: need to enable both
      - if both enabled, either the consumer or the provider can initiate communication.