ImplementingACIv2
ImplementingACIv2
Authored By:
Khawar Butt
CCIE # 12353
Hepta CCIE#12353 Fabric Discovery
CCDE # 20110020
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Log into you APIC using the Username and Password provided.
➢ Click Update.
➢ Click Update.
➢ Repeat the process for the second Spine switch. Assign it the
parameters from the above table for SPINE-02.
➢ Click Update.
Spine-1 Spine-2
Leaf-1 Leaf-2
Authored By:
Khawar Butt
CCIE # 12353
Hepta CCIE#12353
CCDE # 20110020 Access Provisioning – Topology I
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ You are planning on configuring the above topology for ACI. Besides
the devices displayed above, the Servers & Clients will be connected to
the following ports on the 2 Leaf switches.
o Clients
▪ LEAF-01 – Ports 1/1 – 15
▪ LEAF-02 – Ports 1/1 – 20
o Servers
▪ LEAF-01 – Ports 1/16 – 25
▪ LEAF-02 – Ports 1/21 – 28
➢ The port properties for the Devices will be based on the following
table:
➢ Click Fabric -> Access Policies -> Policies -> Interface -> CDP
Interface -> Right-click -> Create CDP Interface Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> LLDP
Interface -> Right-click -> Create LLDP Interface Policy
➢ Click Click Fabric -> Access Policies -> Policies -> Interface -> Link
Level -> Right-click -> Create Link Level Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Port
Security -> Right-click -> Create Port Security Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Storm
Control -> Right-click -> Create Storm Control Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Spanning
Tree -> Right-click -> Create Spanning Tree Policy
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Port
Channel -> Right-click -> Create Port Channel Policy
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> PC Interface -> Right-click -> Create PC Interface
Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> PC Interface -> Right-click -> Create PC Interface
Policy Group
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Policies -> Switch -> Virtual Port
Channel Default -> Right-click -> Create vPC Explicit Protection
Group
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> VPC Interface -> Right-click -> Create VPC
Interface Policy Group
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Profiles -> Right-click -> Create Leaf Interface Profile
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Switches -> Leaf Switches ->
Profiles -> Right-click -> Create Leaf Profile
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Pools -> VLANS -> Right-click ->
Create VLAN Pool
➢ Create a Pool of VLANs that will be used within ACI for Physical ACI
Ports:
o Name: VLAN-POOL-ACI
o Leaf Name: Static Allocation
o Range: 1-500
➢ Create a Pool of VLANs that will be used within ACI for External
Bridged Ports ACI Ports:
o Name: VLAN-POOL-L2
o Leaf Name: Static Allocation
o Range: 400-500
➢ Create a Pool of VLANs that will be used within ACI for External
Routed Ports ACI Ports:
o Name: VLAN-POOL-L3
o Leaf Name: Static Allocation
o Range: 1-400
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Physical and External Domains -
> Physical Domains -> Right-click -> Create Physical domain
➢ Create a Physical Domain and link it to the VLAN Pool based on the
following:
o Name: ACI-PORTS
o VLAN Pool: VLAN-POOL-ACI
➢ Click Fabric -> Access Policies -> Physical and External Domains -
> External Bridged Domain -> Right-click -> Create L2 domain
➢ Create an External Bridge Domain and link it to the VLAN Pool based
on the following:
o Name: EXT-L2-PORTS
o VLAN Pool: VLAN-POOL-L2
➢ Click Fabric -> Access Policies -> Physical and External Domains -
> L3 Domain -> Right-click -> Create L3 Domain
➢ Create an External Routed Domain and link it to the VLAN Pool based
on the following:
o Name: EXT-L3-PORTS
o VLAN Pool: VLAN-POOL-L3
Physical Topology
Spine-1 Spine-2
SW-1
Leaf-1 Leaf-2
28
29-30 35 39 31-32
26 29
➢ Click Fabric -> Access Policies -> Policies -> Global -> Attachable
Access Entity Profile -> Right-click -> Create Attachable Access
Entity Profile
➢ Create an AAEP for ACI Ports and link it to the Domain & IPGs based
on the following:
o Name: AAEP-ACI
o Domain: ACI-PORTS
o IPGs: IPG-CLIENTS & IPG-SERVERS
➢ Click Fabric -> Access Policies -> Policies -> Global -> Attachable
Access Entity Profile -> Right-click -> Create Attachable Access
Entity Profile
➢ Create an AAEP for ACI Ports and link it to the Domain & IPGs based
on the following:
o Name: AAEP-L2-PORTS
o Domain: EXT-L2-PORTS
o IPGs: IPG-SW1, IPG-SW2-PC, IPG-SW3-PC & IPG-SW4-vPC
➢ Click Fabric -> Access Policies -> Policies -> Global -> Attachable
Access Entity Profile -> Right-click -> Create Attachable Access
Entity Profile
➢ Create an AAEP for ACI Ports and link it to the Domain & IPGs based
on the following:
o Name: AAEP-L3-PORTS
o Domain: EXT-L3-PORTS
o IPGs: IPG-ROUTERS
This completes the Access Provisioning Process. The next set of labs
will repeat it for a different physical topology.
Authored By:
Khawar Butt
CCIE # 12353
Hepta CCIE#12353
CCDE # 20110020 Access Provisioning – Topology II
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ You are planning on configuring the above topology for ACI. Besides
the devices displayed above, the Servers & Clients will be connected to
the following ports on the 2 Leaf switches.
o Clients
▪ LEAF-01 – Ports 1/1 – 20
▪ LEAF-02 – Ports 1/1 – 30
o Servers
▪ LEAF-01 – Ports 1/21 – 30
▪ LEAF-02 – Ports 1/31 – 40
➢ The port properties for the Devices will be based on the following
table:
➢ Click Fabric -> Access Policies -> Policies -> Interface -> CDP
Interface -> Right-click -> Create CDP Interface Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> LLDP
Interface -> Right-click -> Create LLDP Interface Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Link
Level -> Right-click -> Create Link Level Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Port
Security -> Right-click -> Create Port Security Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Storm
Control -> Right-click -> Create Storm Control Policy
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Spanning
Tree -> Right-click -> Create Spanning Tree Policy
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Policies -> Interface -> Port
Channel -> Right-click -> Create Port Channel Policy
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> Leaf Access Port -> Right-click -> Create Leaf
Access Port Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> PC Interface -> Right-click -> Create PC Interface
Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> PC Interface -> Right-click -> Create PC Interface
Policy Group
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> PC Interface -> Right-click -> Create PC Interface
Policy Group
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Policies -> Switch -> Virtual Port
Channel Default -> Right-click -> Create vPC Explicit Protection
Group
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Policy Groups -> VPC Interface -> Right-click -> Create VPC
Interface Policy Group
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Interfaces -> Leaf Interfaces ->
Profiles -> Right-click -> Create Leaf Interface Profile
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Switches -> Leaf Switches ->
Profiles -> Right-click -> Create Leaf Profile
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Pools -> VLANS -> Right-click ->
Create VLAN Pool
➢ Create a Pool of VLANs that will be used within ACI for Physical ACI
Ports:
o Name: VLAN-POOL-ACI
o Leaf Name: Static Allocation
o Range: 1-500
➢ Create a Pool of VLANs that will be used within ACI for External
Bridged Ports ACI Ports:
o Name: VLAN-POOL-L2
o Leaf Name: Static Allocation
o Range: 400-500
➢ Create a Pool of VLANs that will be used within ACI for External
Routed Ports ACI Ports:
o Name: VLAN-POOL-L3
o Leaf Name: Static Allocation
o Range: 1-400
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Physical and External Domains -
> Physical Domains -> Right-click -> Create Physical domain
➢ Create a Physical Domain and link it to the VLAN Pool based on the
following:
o Name: ACI-PORTS
o VLAN Pool: VLAN-POOL-ACI
➢ Click Fabric -> Access Policies -> Physical and External Domains -
> External Bridged Domains -> Right-click -> Create L2 Domain
➢ Create an External Brige Domain and link it to the VLAN Pool based
on the following:
o Name: EXT-L2-PORTS
o VLAN Pool: VLAN-POOL-L2
➢ Click Fabric -> Access Policies -> Physical and External Domains -
> External L3 Domains -> Right-click -> Create L3 Domain
➢ Create an External Routed Domain and link it to the VLAN Pool based
on the following:
o Name: EXT-L3-PORTS
o VLAN Pool: VLAN-POOL-L3
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
SW-2 R1 SW-3 R2
➢ Click Fabric -> Access Policies -> Policies -> Global -> Attachable
Access Entity Profile -> Right-click -> Create Attachable Access
Entity Profile
➢ Create an AAEP for ACI Ports and link it to the Domain & IPGs based
on the following:
o Name: AAEP-ACI
o Domain: ACI-PORTS
o IPGs: IPG-CLIENTS, IPG-SERVERS, IPG-SALES-BE-PC & IPG-
MARK-BE-PC
➢ Click Fabric -> Access Policies -> Policies -> Global -> Attachable
Access Entity Profile -> Right-click -> Create Attachable Access
Entity Profile
➢ Create an AAEP for ACI Ports and link it to the Domain & IPGs based
on the following:
o Name: AAEP-L2-PORTS
o Domain: EXT-L2-PORTS
o IPGs: IPG-SW1, IPG-SW2-PC & IPG-SW3-vPC
➢ Click Fabric -> Access Policies -> Policies -> Global -> Attachable
Access Entity Profile -> Right-click -> Create Attachable Access
Entity Profile
➢ Create an AAEP for ACI Ports and link it to the Domain & IPGs based
on the following:
o Name: AAEP-L3-PORTS
o Domain: EXT-L3-PORTS
o IPGs: IPG-ROUTERS
Authored By:
Khawar Butt
CCIE # 12353
Hepta CCIE#12353
CCDE # 20110020 Tenant Provisioning
Logical Topology
Tenant : KBITS
VRF : GRT
Subnets:
10.1.1.0/24
10.1.2.0/24
10.1.3.0/24
➢ Click Tenant -> KBITS -> Networking -> VRF -> Right-click ->
Create VRF
Logical Topology
Tenant : KBITS
VRF : GRT
Subnets:
10.1.1.0/24
10.1.2.0/24
10.1.3.0/24
➢ Click Tenant -> KBITS -> Networking -> Bridge Domain -> Right-
click -> Create Bridge Domain
Authored By:
Khawar Butt
CCIE # 12353
Hepta CCIE#12353
CCDE # 20110020 Application Provisioning
Sales Application
➢ Click Tenant -> KBITS -> Application Profiles -> Right-click ->
Create Application Profile
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EGPs -> Right-click -> Create Application EPG
o Name: SALES-FE
o Bridge domain: BD1
o Name: SALES-BE
o Bridge domain: BD1
Sales Application
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EPGs -> SALES-CLIENTS -> Static Ports -> Right-click
-> Deploy Static EPG on PC, VPC or Interface
Sales Application
➢ Click Tenant -> KBITS -> Contracts -> Filters -> Create Filter
o Name: Web-Access
o Policy#1:
▪ Name: HTTP
▪ Ethertype: IP
▪ Protocol: TCP
▪ Destination Port Range: HTTP To HTTP
o Policy#2:
▪ Name: HTTPS
▪ Ethertype: IP
▪ Protocol: TCP
▪ Destination Port Range: HTTPS To HTTPS
➢ Click Tenant -> KBITS -> Contracts -> Filters -> Create Filter
o Name: ICMP-PING
o Policy#1:
▪ Name: PING
▪ Ethertype: IP
▪ Protocol: ICMP
➢ Click Tenant -> KBITS -> Contracts -> Filters -> Create Filter
o Name: ORACLE-DB-ACCESS
o Policy#1:
▪ Name: ORACLE-DB
▪ Ethertype: IP
▪ Protocol: TCP
▪ Destination Port Range: 1521 To 1521
Sales Application
➢ Click Tenant -> KBITS -> Contracts -> Standard -> Create Contract
➢ Click Tenant -> KBITS -> Contracts -> Standard -> Create Contract
Sales Application
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EPGs -> SALES-CLIENTS -> Contracts -> Right-click ->
Add Consumed Contract
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EPGs -> SALES-FE -> Contracts -> Right-click -> Add
Provided Contract
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EPGs -> SALES-FE -> Contracts -> Right-click -> Add
Consumed Contract
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EPGs -> SALES-BE -> Contracts -> Right-click -> Add
Provided Contract
Mark Application
➢ Click Tenant -> KBITS -> Application Profiles -> Right-click ->
Create Application Profile
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EGPs -> Right-click -> Create Application EPG
o Name: MARK-FE
o Bridge domain: BD1
o Name: MARK-BE
o Bridge domain: BD1
Mark Application
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-CLIENTS -> Static Ports -> Right-click
-> Deploy Static EPG on PC, VPC or Interface
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-FE -> Static Ports -> Right-click ->
Deploy Static EPG on PC, VPC or Interface
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-BE -> Static Ports -> Right-click ->
Deploy Static EPG on PC, VPC or Interface
Mark Application
➢ Click Tenant -> KBITS -> Contracts -> Filters -> Create Filter
o Name: IMAP
o Policy#1:
▪ Name: IMAP4
▪ Ethertype: IP
▪ Protocol: TCP
▪ Destination Port Range: 143 To 143
➢ Click Tenant -> KBITS -> Contracts -> Filters -> Create Filter
o Name: MS-SQL-DB-ACCESS
o Policy#1:
▪ Name: MS-SQL-DB-TCP
▪ Ethertype: IP
▪ Protocol: TCP
▪ Destination Port Range: 1433 To 1433
o Policy#2:
▪ Name: MS-SQL-DB-UDP
▪ Ethertype: IP
▪ Protocol: UDP
▪ Destination Port Range: 1434 To 1434
Mark Application
➢ Click Tenant -> KBITS -> Contracts -> Standard -> Create Contract
➢ Click Tenant -> KBITS -> Contracts -> Standard -> Create Contract
Mark Application
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-CLIENTS -> Contracts-> Right-click ->
Add Consumed Contract
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-FE -> Contracts-> Right-click -> Add
Provided Contract
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-FE -> Contracts-> Right-click -> Add
Consumed Contract
➢ Click Tenant -> KBITS -> Application Profiles -> MARK-APPS ->
Application EPGs -> MARK-BE -> Contracts-> Right-click -> Add
Provided Contract
Authored By:
Khawar Butt
CCIE # 12353
Hepta CCIE#12353
CCDE # 20110020 External Domains – L2OUT &
L3OUT
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
➢ The VLAN 10 & 20 are stretched between ACI & Non-ACI Domains.
➢ Devices connected to VLAN 10 are located on Non-ACI Switches SW1
& SW2. Sales Clients are allocated to this VLAN.
➢ Devices connected to VLAN 20 are located on Non-ACI Switches SW2
& SW3. Sales FE are allocated to this VLAN.
➢ Click Tenant -> ABC -> Networking -> External Bridge Networks
-> Right-click -> Create Bridged Outside
o Name: L2OUT-SALES-CLIENTS-VLAN-10
o External Bridge Domain: EXT-L2-PORTS
o Bridge Domain: BD1
o VLAN: 10
o External L2 Connection:
▪ Port: Leaf-1 - 101/1/41
▪ PC: IPG-SW2-PC
o External L2OUT Network EPG: L2OUT-SALES-CLIENTS
➢ Click Tenant -> ABC -> Networking -> External Bridge Networks
-> Right-click -> Create Bridged Outside
o Name: L2OUT-SALES-CLIENTS-VLAN-20
o External Bridge Domain: EXT-L2-PORTS
o Bridge Domain: BD1
o VLAN: 20
o External L2 Connection:
▪ PC: IPG-SW2-PC
▪ vPC: IPG-SW3-vPC
o External L2OUT Network EPG: L2OUT-SALES-FE
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
Sales-C-2-FE
Sales-FE-2-BE
ICMP
Web Access (80,443) ICMP
SALES-CLIENTS SALES-FE Oracle DB (1521) SALES-BE
Sales-C-2-Int
Permit Any
➢ Click Tenant -> ABC -> Networking -> External Bridge Networks ->
L2OUT-SALES-CLIENTS-VLAN-10 -> Networks -> SALES-CLIENTS-
L2OUT -> Contracts
➢ Click Tenant -> ABC -> Networking -> External Bridge Networks ->
L2OUT-SALES-FE-VLAN-20 -> Networks -> SALES-FE-L2OUT ->
Contracts
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
➢ Click Fabric -> Fabric Policies -> Pods -> Policy Group -> Right-
click -> Create Pod Policy Group
o Name: MY-POD-POLICY-GROUP
o BGP Route Reflector Policy: default (Click the Edit Link)
o AS: 65001
o Route Reflectors: Spine1(103) & Spine2(104)
➢ Click Submit.
➢ The Profile links to the POD Policy Group created in the previous step.
➢ Click Fabric -> Fabric Policies -> Pods -> Profiles -> Pod Profile
Default -> default
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
➢ Click Tenant -> KBITS -> Networking -> L3Outs -> Create L3OUT
Main Page:
Name: L3OUT-EIGRP
Protocol: EIGRP
AS # : 111
VRF: GRT
External Routed Domain: EXT-L3-PORTS
Node Profile:
Name: LEAF-01-EIGRP
LEAF-1 - Node ID : 101
Router-ID: 11.11.11.11
Interface Profile:
Name: L3OUT-EIGRP
EIGRP Policy: default
Routed Interface: Leaf-01/1/44
IP Address: 192.1.100.11/24
EPG:
Name: L3OUT-SALES-CLIENTS
Networks: 10.11.11.0/24 & 10.12.12.0/24
Name: L3OUT-SALES-FE
Networks: 10.13.13.0/24 & 10.14.14.0/24
➢ Click Submit.
➢ Click Tenant -> KBITS -> Networking -> Bridge Domains -> BD1 ->
L3 Configurations -> Associated L3OUT
➢ Click Submit.
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
Sales-C-2-FE
Sales-FE-2-BE
ICMP
Web Access (80,443) ICMP
SALES-CLIENTS SALES-FE Oracle DB (1521) SALES-BE
Sales-C-2-Int
Permit Any
➢ Click Tenant -> KBITS -> Networking -> External Routed Networks
-> L3OUT-EIGRP -> Networks -> L3OUT-SALES-CLIENTS ->
Contracts
➢ Click Tenant -> KBITS -> Networking -> External Routed Networks
-> L3OUT-EIGRP -> Networks -> L3OUT-SALES-FE -> Contracts
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
➢ Click Tenant -> KBITS -> Networking -> L3Outs -> Create L3OUT
Main Page:
Name: L3OUT-OSPF
Protocol: OSPF
Area # : 0
Area Type: Regular
VRF: GRT
External Routed Domain: EXT-L3-PORTS
Node Profile:
Name: LEAF-02-OSPF
LEAF-1 - Node ID : 102
Router-ID: 22.22.22.22
Interface Profile:
Name: L3OUT-OSPF
OSPF Policy: default
Routed Interface: Leaf-02/1/48
IP Address: 192.1.200.22/24
EPG:
Name: Internet
Networks: 0.0.0.0/0
➢ Click Submit.
➢ Click Tenant -> KBITS -> Networking -> Bridge Domains -> BD1 ->
L3 Configurations -> Associated L3OUT
➢ Click Submit.
Physical Topology
Spine-1 Spine-2
SW-1 SALES-BE-
SERVER
Leaf-1 Leaf-2
41-42
41
42-43 47 47
44 43-44
48 MARK-BE-
SERVER
R1 R2
SW-2 SW-3
Internet
MPLS
VPN
Sales-C-2-FE
Sales-FE-2-BE
ICMP
Web Access (80,443) ICMP
SALES-CLIENTS SALES-FE Oracle DB (1521) SALES-BE
Sales-C-2-Int
Permit Any
➢ Click Tenant -> KBITS -> Contracts -> Filters -> Create Filter
o Name: Internet
o Policy#1:
▪ Name: Internet
▪ Ethertype: IP
▪ Protocol: Any
▪ Destination Port Range: Unspecified to Unspecified
Creating Contracts
Task 1 – Create a Contract for traffic from SALES-CLIENTS EPG
towards the Internet
➢ Click Tenant -> KBITS -> Contracts -> Standard -> Create
➢ Click Tenant -> KBITS -> Networking -> External Routed Networks
-> L3OUT-OSPF -> Networks -> Internet -> Contracts
➢ Click Tenant -> KBITS -> Application Profiles -> SALES-APPS ->
Application EPGs -> SALES-CLIENTS -> Contracts -> Right-click ->
Add Consumed Contract