Shared Layer 3 Outside

Agenda – Shared Layer3 Outside Overview & Description Configuration Troubleshooting Other Related Documents

Overview and Description

Overview This presentation is focusing on explaining the user configuration needed for enabling shared service with Layer3 Outside (L3Out). It does not focus on switching constructs and packet processing details. Shared service with Layer3 Outside (L3Out) enables EPGs to do cross VRF communications with L3Out. The EPG and L3Out can be configured under any tenant and shared service can be enabled using normal contract configuration.

Software and Hardware Requirements No new hardware requirement. Feature will be supported in release 1.2.

Configuration

User Configuration The EPG and L3Out can be defined in any tenant and shared service can be enabled using normal contract configuration. The contract configuration will program the following: Access control rules Export public BD or EPG subnets to the L3Out Leak shared BD and EPG subnets to the L3Out’s VRF Leak shared external subnets to the EPG’s VRF

Configuration Info On top of contracts, “scope” property of the external subnets (represented by model class l3ext::Subnet) defined under the Layer3 Instance Profile (represented by model class l3ext::InstP), would have to get marked properly: For leaking the route in the other VRF −API: Add "shared-rtctrl" bit in the “scope” property of the subnet. −GUI: Add “Shared Route Control Subnet” bit in the “scope” property of the subnet. To leak aggregated route: −API: Add “shared-rtctrl” bit in the “aggregate” property of the subnet, otherwise only exact subnet will be leaked. −GUI: Add “Aggregate Shared Routes” bit in the “aggregate” property of the subnet. For enabling security on the route in the other VRF: −API: Add "shared-security" bit in the “scope” property of the subnet. −GUI: Add “Shared Security Import Subnet” bit in the “scope” property of the subnet. −The bits which are already present in the “scope” property will function as they used to function in previous releases.

Example: Scope set to “shared-rtctrl”: Route will get leaked into the other private network, but no ACLs will be installed for the route in the other network. Such a use-case is possible when the route getting leaked (or shared) is a bigger subnet and security is applied on a separate smaller subnet. For instance: −Route: /16, Scope: shared-rtctrl, aggregate=“shared-rtctrl” −Route: /24, Scope: shared-security −Route: /24, Scope: shared-security In this example, aggregated /16 will be included in the route map of leaked subnets and it covers /24 and /24 as well, but no ACLs will be installed for it. For /24 and /24 user can specify contracts and ACLs will be installed in the other private network for these subnets. Scope set to “shared-rtctrl, shared-security”: Route will get leaked and ACLs will also get installed for this route in the other network.

User Configuration Example Tenant-A EPG-B InstP-1 BD-A CTX-A Subnet-A shared,public Subnet-A shared,public Consumer Inter-Context Contract Provider Ctx-B L3Out A AP External Subnet-A shsred-security,shared- rtctrl,import-security External Subnet-A shsred-security,shared- rtctrl,import-security External Subnet-B shared-rtctrl External Subnet-B shared-rtctrl

Troubleshooting

Troubleshooting Steps Check user configuration and make sure its correct. Check faults raised on the L3Out and on the Application EPG or BD or Ctx. Troubleshooting Border leaf (i.e the leaf with L3Out): −Check that static routes for the “shared” BD or EPG subnets are installed in the L3Out’s VRF. Represented by model class ip::Route −Check that the “public” BD or EPG subnets are included in the “export” route map. Represented by model class rtpfx::Entry and rtmap::Rule −Troubleshooting Non-Border leaf (i.e the leaf with Application EPG): −Check that actrl prefix entry is installed for the external subnets whose scope property is marked with “shared-security”. Represented by model class “actrl::PfxEntry” −Check that the external subnets whose scoper property is marked with “shared-rtctrl” are configured to leaked into the EPGs VRF i.e. are present in the shared route map. −Check that actrl rules are installed in the EPGs VRF for the filters defined in the contract. Represented by model class “actrl::Rule”

Other Related Documents Shared_L3_Outside: EDCS & EDCS